b44.ko driver does not work in Ubuntu 6.06 and Dell laptop

Bug #78330 reported by Blaisorblade
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.15 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6-amd64-xeon

On a 64-bit dell Inspiron 6400, the integrated broadcom BCM4401 Ethernet card does not work - the card is recognized, the driver loaded and the eth1 interface appears , but almost no packet is ever trasmitted. I happen to get some packet passing through the card at times, and only one time ever DHCP completed successfully; even with a manually assigned IP not even arp packets can pass the interface. This has happened with all sorts of known-good network cables, and the interface works perfectly under Windows.

However, carrier is correctly recognized, mii-tool show that autonegotiation has completed.

I've rebooted with a custom-built 2.6.18.6 kernel and the card works perfectly there; the firewall setup is the same (iptables-restore, which I use, either fully succeeds or fully fails). So it is definitely a kernel problem.

Looking into git history, no enormous changes have happened.
I cannot find related commits; 639b421b911bbde1e3fb5ed037a4f8c85a5bffcb mentions a fix which probably affects boxes with more than 1Gb of RAM.

The only commit which seems related is d9e2d185bf01e20339158f77c3fca00b02014912, but it seems it is applied on 2.6.15 and all ubuntu 6.06 kernels.

I do kernel development on UserModeLinux so I can test patches and even do bisection search, but currently I'm too busy and I may be so for a time. Please suggest the best action to take. I'll try if I can rebuild the original package with make-kpkg and with changes only to the b44 driver.

Additional info:
Reproduced on a laptop inspiron 6400, with Core 2 Duo T7200, 2Gb of RAM, linux-image-2.6.15-27-amd64-xeon kernel (and I think with linux-image-2.6.15-26-amd64-xeon).

# lspci
0000:00:00.0 Host bridge: Intel Corporation Mobile Memory Controller Hub (rev 03)
0000:00:01.0 PCI bridge: Intel Corporation Mobile PCI Express Graphics Port (rev 03)
0000:00:1b.0 0403: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
0000:00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)
0000:00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 01)
0000:00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 01)
0000:00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 01)
0000:00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 01)
0000:00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 01)
0000:00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
0000:00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1)
0000:00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)
0000:00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controllers cc=IDE (rev 01)
0000:00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 7149
0000:03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
0000:03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd: Unknown device 0832
0000:03:01.1 0805: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
0000:03:01.2 System peripheral: Ricoh Co Ltd: Unknown device 0843 (rev 01)
0000:03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
0000:03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)
0000:0b:00.0 Network controller: Intel Corporation: Unknown device 4222 (rev 02)

Revision history for this message
Blaisorblade (p-giarrusso) wrote :

Today I've downloaded the Ubuntu kernel source, replaced b44.[ch] with the copy from 2.6.18.6, undone a single API change by running the following command on a recent git repository (>= 2.6.18):

$ cg diff -pr 1fb9df5d3069064c037c81c0ab8bf783ffa5e373 drivers/net/b44.c \
 |patch -R ../linux-source-2.6.15-2.6.15/drivers/net/b44.c

 and rebuilt the resulting kernel with make-kpkg. The ethernet card, then, worked flawlessly. Do you need a bisection search for the exact patch solving the bug or it is ok for you to backport all changes as I did?

Thanks.

Changed in linux-source-2.6.15:
status: Unconfirmed → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Blaisorblade (p-giarrusso) wrote :

As I wrote in this comment:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/78330/comments/1

the bug was solved since 2.6.18.6, has not reappeared until 2.6.23 (the last kernel I tested), and I think it won't reappear. I just requested to do a backport of the solution to 6.06, since it's an LTS release.

However, after some experience with Ubuntu bugtracking, I must say that I always got either no answer or pseudo-automated/mass answers (like the above one) or answers from people which are less competent than me, or that didn't even read the bug report. How are you going to call 6.06 LTS if you do not even read bug reports against it?

About my complains, also look at:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/86778
which is in a similar situation as this bug.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Blaisorblade,

As you already know, the previous call for testing the 2.6.27 kernel was an automated response. We needed to reach as many bug reporters as quickly as possible and updating thousands of bugs manually was just inefficient. But we have been monitoring the feedback we've been getting.

I'm glad to hear this appears to be working with the an updated kernel. Per your previous comment, I'm marking this "Fix Released" against the newer kernels. Unfortunately as you've also noted, this will not likely qualify for a stable release update for Dapper - http://wiki.ubuntu.com/StableReleaseUpdates . I do however feel the other bug 86778 you pointed to will qualify for SRU and will notify the kernel team accordingly. Thanks.

Changed in linux:
status: Confirmed → Fix Released
Changed in linux-source-2.6.15:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.