From: Andrew Morton <akpm@linux-foundation.org>
To: Gary Zambrano <zambrano@broadcom.com>
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org,
ck.accounts@gmx.de
Subject: Re: [Bugme-new] [Bug 29562] New: Kernel Panic with b44 eth-module (Kernel 2.6.37) | Dell Vostro 1500
Date: Wed, 23 Feb 2011 16:12:01 -0800 [thread overview]
Message-ID: <20110223161201.f49f51e4.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-29562-10286@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Mon, 21 Feb 2011 09:35:59 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=29562
>
> Summary: Kernel Panic with b44 eth-module (Kernel 2.6.37) |
> Dell Vostro 1500
> Product: Networking
> Version: 2.5
> Kernel Version: 2.6.37.1 (ArchLinux latest)
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: high
> Priority: P1
> Component: Other
> AssignedTo: acme@ghostprotocols.net
> ReportedBy: ck.accounts@gmx.de
> Regression: No
>
>
> Hey,
>
> I have a problem with my network card (b44 driver). It's almost the same
> problem described here:
> https://bugzilla.redhat.com/show_bug.cgi?id=668088
>
> I think it's a common Dell problem. I found several Dell users with the same
> problem. The problem occured first with the kernel update to 2.6.37 (2.6.36.x
> -> 2.6.37)
>
> I have taken a picture of the panic-log:
> http://www.pic-upload.de/view-8728232/DSC00735.jpg.html
>
> The workaround for this issue is to block the module !b44 (-> network card
> doesn't work anymore).
>
> Some additional information:
> Laptop: Dell Vostro 1500
> Distro: ArchLinux x86_64
> Ethernet controler: 03:00.0 Ethernet controller: Broadcom Corporation
> BCM4401-B0 100Base-TX (rev 02)
>
> 1. boot PC without b44
> 2. # modprobe b44
> 3. kernel panic!
>
> I am not sure, whether it is a ArchLinux problem or a general kernel problem?
>
parent reply other threads:[~2011-02-24 0:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-29562-10286@https.bugzilla.kernel.org/>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110223161201.f49f51e4.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=ck.accounts@gmx.de \
--cc=netdev@vger.kernel.org \
--cc=zambrano@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).