Bug 14451 - b44 BCM4401 immediate disconnect and power down after ip assignment
Summary: b44 BCM4401 immediate disconnect and power down after ip assignment
Status: RESOLVED DUPLICATE of bug 7696
Alias: None
Product: Drivers
Classification: Unclassified
Component: Network (show other bugs)
Hardware: All Linux
: P1 high
Assignee: drivers_network@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-21 07:38 UTC by Andreas Schipplock
Modified: 2012-06-13 20:32 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.31.4
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Andreas Schipplock 2009-10-21 07:38:13 UTC
Hi,
I compiled the linux kernel 2.6.31.4 and after "dhcpcd" wanted to assign an ip, it worked for 500ms and I then got the following message being repeated a _lot_ in dmesg:

b44: eth0: powering down PHY
b44: eth0: Link is down.
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is off for TX and off for RX.
b44: eth0: powering down PHY
b44: eth0: Link is down.
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is off for TX and off for RX.

These messages repeat endlessly and I can't establish a connection. 

The exact name of the ethernet controller is: "08:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)" regarding lspci output.

When I execute "ifconfig" every 500ms I can see that the device "eth0" gets a valid ip but the next time I execute ifconfig the ip is already "gone" and I again get the the messages posted above in dmesg. 

I first thought was that I have a media problem so I replaced all my wires but the problem still exists and the problem doesn't appear on the 2.6.28.x kernel which I ran before. I even installed linux mint in a hurry to see if it's really not a hardware issue and it worked there without a problem (using kernel 2.6.28-11, that's how they call it).

I've got no further idea. I created three different config files from scratch using menuconfig. In the end I even thought other modules are conflicting and I adapted the config so it only fits for my specific hardware which gave me some good boot time but no success regarding the bcm4401 issue. 

Any help is appreciated. 

Thanks!

Andreas Schipplock.
Comment 1 Andrew Morton 2009-11-03 23:23:44 UTC
(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Wed, 21 Oct 2009 07:38:13 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=14451
> 
>            Summary: b44 BCM4401 immediate disconnect and power down after
>                     ip assignment
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 2.6.31.4
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: high
>           Priority: P1
>          Component: Network
>         AssignedTo: drivers_network@kernel-bugs.osdl.org
>         ReportedBy: andreas@schipplock.de
>         Regression: No
> 
> 
> Hi,
> I compiled the linux kernel 2.6.31.4 and after "dhcpcd" wanted to assign an
> ip,
> it worked for 500ms and I then got the following message being repeated a
> _lot_
> in dmesg:
> 
> b44: eth0: powering down PHY
> b44: eth0: Link is down.
> b44: eth0: Link is up at 100 Mbps, full duplex.
> b44: eth0: Flow control is off for TX and off for RX.
> b44: eth0: powering down PHY
> b44: eth0: Link is down.
> b44: eth0: Link is up at 100 Mbps, full duplex.
> b44: eth0: Flow control is off for TX and off for RX.
> 
> These messages repeat endlessly and I can't establish a connection. 
> 
> The exact name of the ethernet controller is: "08:00.0 Ethernet controller:
> Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)" regarding lspci output.
> 
> When I execute "ifconfig" every 500ms I can see that the device "eth0" gets a
> valid ip but the next time I execute ifconfig the ip is already "gone" and I
> again get the the messages posted above in dmesg. 
> 
> I first thought was that I have a media problem so I replaced all my wires
> but
> the problem still exists and the problem doesn't appear on the 2.6.28.x
> kernel
> which I ran before. I even installed linux mint in a hurry to see if it's
> really not a hardware issue and it worked there without a problem (using
> kernel
> 2.6.28-11, that's how they call it).
> 
> I've got no further idea. I created three different config files from scratch
> using menuconfig. In the end I even thought other modules are conflicting and
> I
> adapted the config so it only fits for my specific hardware which gave me
> some
> good boot time but no success regarding the bcm4401 issue. 
> 
> Any help is appreciated. 
>
Comment 2 Bojan Smojver 2009-11-18 22:35:21 UTC
Do we know what is happening with this bug?
Comment 3 Bojan Smojver 2009-12-17 00:24:11 UTC
Shouldn't bugs #7696, #11056 and this one be merged? Looks like a very similar problem.
Comment 4 Marc 2010-08-14 03:06:57 UTC
Well, my apologies for responding via the bugzilla interface, but I have no clue how else to respond. I agree with Bojan that bug 7696 and bug 11056 seem like dups.

This problem still affects me with kernel 2.6.35.1 on a Dell Inspiron B130 laptop. I am completely unable to establish a connection using dhcpcd 5.2.7. If I assign a static IP, I am at least able to surf the net.

# uname -a
Linux archbox 2.6.35-ARCH #1 SMP PREEMPT Wed Aug 11 01:08:23 CEST 2010 i686 Intel(R) Celeron(R) M processor 1.40GHz GenuineIntel GNU/Linux

# lspci -v
02:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
	Subsystem: Dell Device 01c9
	Flags: bus master, fast devsel, latency 64, IRQ 18
	Memory at dfbfc000 (32-bit, non-prefetchable) [size=8K]
	Capabilities: [40] Power Management version 2
	Kernel driver in use: b44
	Kernel modules: b44

/var/log/messages.log (snippet repeats until dhcpcd is killed)
Aug  9 00:56:14 archbox dhcpcd: eth0: carrier lost
Aug  9 00:56:14 archbox dhcpcd: eth0: MTU restored to 1500
Aug  9 00:56:14 archbox kernel: b44: eth0: powering down PHY
Aug  9 00:56:17 archbox kernel: b44: eth0: Link is up at 100 Mbps, full duplex.
Aug  9 00:56:17 archbox kernel: b44: eth0: Flow control is off for TX and off for RX.
Aug  9 00:56:17 archbox dhcpcd: eth0: carrier acquired
Aug  9 00:56:17 archbox dhcpcd: eth0: rebinding lease of 192.168.15.2
Aug  9 00:56:17 archbox dhcpcd: eth0: acknowledged 192.168.15.2 from 192.168.15.1
Aug  9 00:56:17 archbox dhcpcd: eth0: checking for 192.168.15.2
Aug  9 00:56:22 archbox dhcpcd: eth0: leased 192.168.15.2 for 86400 seconds
Aug  9 00:56:22 archbox kernel: b44: eth0: powering down PHY
Aug  9 00:56:22 archbox dhcpcd: eth0: MTU set to 1400
Aug  9 00:56:22 archbox kernel: b44: eth0: Link is down.
Comment 5 Alan 2012-06-13 20:32:25 UTC

*** This bug has been marked as a duplicate of bug 7696 ***

Note You need to log in before you can comment on or make changes to this bug.