From: Uwe Bugla <uwe.bugla@gmx.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michael Buesch <mb@bu3sch.de>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)
Date: Fri, 25 May 2007 20:42:17 +0200 [thread overview]
Message-ID: <200705252042.17680.uwe.bugla@gmx.de> (raw)
In-Reply-To: <20070525095618.1cd86672.akpm@linux-foundation.org>
Am Freitag, 25. Mai 2007 18:56 schrieben Sie:
> On Fri, 25 May 2007 16:52:19 +0200 Michael Buesch <mb@bu3sch.de> wrote:
> > I bet your bug is _not_ caused by ssb, but by some other breakage
> > in another subsystem. Maybe ACPI or APIC is broken? Try to boot
> > the machine without ACPI and/or APIC.
>
> It wouldn't be the first time.
>
> Uwe, please generate the `dmesg -s 1000000' output for 2.6.22-rc2 and for
> 2.6.22-rc2-mm1, feed them through `diff -u' and see if you can spot any
> interesting-looking differences in the PCI/ACPI/IRQ area. Send both the
> files to me and I'll stick them on a server and then I'll see if we can
> hunt down the perpetrator.
>
> Thanks.
Hi everybody,
unfortunately Andrew's path can be proven to be wrong:
There is no bug in the ACPI area at all.
I reverted the following modules in 2.6.22-rc2-mm1:
--- linux-2.6.22-rc2/drivers/net/b44.c 2007-05-19 02:24:07.000000000 -0700
+++ devel/drivers/net/b44.c 2007-05-22 21:55:36.000000000 -0700
AND:
--- linux-2.6.22-rc2/drivers/net/b44.h 2007-04-25 23:42:17.000000000 -0700
+++ devel/drivers/net/b44.h 2007-05-22 21:55:36.000000000 -0700
AND:
--- linux-2.6.22-rc2/drivers/usb/host/ohci-hcd.c 2007-05-19
02:24:07.000000000 -0700
+++ devel/drivers/usb/host/ohci-hcd.c 2007-05-22 21:55:36.000000000 -0700
AND:
--- /dev/null 2007-05-07 19:14:32.301975000 -0700
+++ devel/drivers/usb/host/ohci-ssb.c 2007-05-22 21:55:36.000000000 -0700
RESULT:
Broadcom 4401 is working purrfectly! YUP!
Apart from that the kernel configuration menu of 2.6.22-rc2-mm1 is highly
confusing:
Kernel Config differences:
In kernel 2.6.21.2 you are bound to go:
EISA, VLB, PCI and onboard controllers Y
Broadcom 4400 ethernet support m
Whereas in Kernel 2.6.22-rc2-mm1 is completely confusing:
1. There is a menu called Sonics Silicon Backplane, which does not
exist in 2.6.21.2.
2. In Section Network device support Y
Ethernet (10 or 100Mbit) Y
you got 2 confusing choices:
Option A:
EISA, VLB, PCI and onboard controllers Y
Broadcom 4400 ethernet support m
Broadcom 4400 PCI device support y
This enables "Sonic Silicon Backplane support m"
OR, and this is in fact confusing:
Option B:
Leave OUT (!!!) EISA, VLB, PCI and onboard controllers Y
Simply: Broadcom 4400 ethernet support m
This enables "Sonic Silicon Backplane support m"
Option B is proved to be working with the patch against the b44.c module
reverted in 2.6.22-rc2-mm1.
If it is NOT reverted, Option B fails, but the confusion stays:
You do not get the idea whether
"Support for SSB on PCI bus host m" is necessary or not!
And above that, THIS ONE:
"Broadcom 4400 ethernet support m"
should never appear when THIS one:
"EISA, VLB, PCI and onboard controllers Y"
is DESELECTED, should it??
And that's it exactly what I meant when I mentioned that the ATTACHMENT of ssb
to b44 is highly buggy!
I hope, Michael, that you believe that now.
If you need lspci -v or / and dmesg to prove that I am right and you are
wrong:
Pleasure for me, just ask please!
Cheers
Uwe
P. S.: In clear words:
I higly suspect that simply the kernel config bindings are highly buggy and
chaotic.
next prev parent reply other threads:[~2007-05-25 18:47 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070524195616.234280@gmx.net>
2007-05-24 20:06 ` BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400) Andrew Morton
2007-05-24 21:16 ` Uwe Bugla
2007-05-25 13:16 ` Michael Buesch
2007-05-25 13:12 ` Michael Buesch
2007-05-25 13:20 ` Michael Buesch
2007-05-25 13:59 ` Uwe Bugla
2007-05-25 14:52 ` Michael Buesch
2007-05-25 15:59 ` Uwe Bugla
2007-05-25 16:23 ` Michael Buesch
2007-05-25 18:48 ` Maximilian Engelhardt
2007-05-25 19:40 ` Uwe Bugla
2007-05-26 5:00 ` Michael Buesch
2007-05-26 9:39 ` Maximilian Engelhardt
2007-05-26 10:40 ` Uwe Bugla
2007-05-26 15:36 ` Michael Buesch
2007-05-26 15:52 ` Uwe Bugla
2007-05-26 15:50 ` Michael Buesch
2007-05-26 16:13 ` Andrew Morton
2007-05-26 16:20 ` Uwe Bugla
2007-05-26 16:46 ` Francois Romieu
2007-05-26 16:21 ` Michael Buesch
2007-05-26 16:26 ` Uwe Bugla
2007-05-26 16:40 ` Michael Buesch
2007-05-26 17:04 ` Uwe Bugla
2007-05-26 17:18 ` Michael Buesch
2007-05-26 17:24 ` Uwe Bugla
2007-05-26 18:03 ` Michael Buesch
2007-05-26 18:19 ` Andrew Morton
2007-05-26 19:38 ` Uwe Bugla
2007-05-26 19:57 ` Larry Finger
2007-05-26 20:22 ` Francois Romieu
2007-05-26 20:33 ` Uwe Bugla
2007-05-26 21:00 ` Michael Buesch
2007-05-26 18:41 ` Benoit Boissinot
2007-05-26 18:46 ` Michael Buesch
2007-05-26 18:58 ` Uwe Bugla
2007-05-26 19:14 ` Michael Buesch
2007-05-26 19:19 ` Michael Buesch
2007-05-26 19:39 ` Uwe Bugla
2007-05-26 19:49 ` Michael Buesch
2007-05-26 21:32 ` Uwe Bugla
2007-05-26 21:52 ` Dan Williams
2007-05-26 22:16 ` Uwe Bugla
2007-05-26 21:58 ` Michael Buesch
2007-05-26 19:04 ` Michael Buesch
2007-05-28 12:12 ` Michael Buesch
2007-05-26 16:14 ` Uwe Bugla
2007-05-26 22:42 ` David Miller
2007-05-25 16:56 ` Andrew Morton
2007-05-25 18:42 ` Uwe Bugla [this message]
2007-05-27 10:46 Uwe Bugla
2007-05-27 13:41 ` Kyle Moffett
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=200705252042.17680.uwe.bugla@gmx.de \
--to=uwe.bugla@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
/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).