[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#617962: marked as done (Network module b44 gets disconnected frequently)

Your message dated Wed, 19 Jun 2013 19:19:41 +0200
with message-id <20130619171941.GA7254@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #617962,
regarding Network module b44 gets disconnected frequently
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
617962: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617962
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image 
Version: 2.6.37-2-686

Every now and then, my ethernet connection gets disconnected in kernel 
2.6.37-2. After few seconds, the link re-establishes itself and I can connect 
to internet just fine. I am using b44 for the following card:

03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 
02)

The problem is severe when I use VPN connection using tun module. Since b44 
goes on and off, sometimes there is kernel panic, so I have to hard reboot.

I read somewhere else that using dhclient instead of dhcp fixes this problem. 
But debian doesn't have this client? When I have downgrade the kernel to 
2.6.32-5-686. I don't see this problem.

Lots of following messages are present in the logs:

[ 3110.988111] b44 ssb0:0: eth0: Link is down
[ 3113.988198] b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex
[ 3113.988202] b44 ssb0:0: eth0: Flow control is off for TX and off for RX
[ 3134.988154] b44 ssb0:0: eth0: Link is down
[ 3137.988244] b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex
[ 3137.988249] b44 ssb0:0: eth0: Flow control is off for TX and off for RX
[ 3183.988130] b44 ssb0:0: eth0: Link is down
[ 3186.988206] b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex
[ 3186.988214] b44 ssb0:0: eth0: Flow control is off for TX and off for RX
[ 3231.988107] b44 ssb0:0: eth0: Link is down
[ 3385.944270] b44 ssb0:0: eth0: powering down PHY
[ 3387.252244] b44 0000:03:00.0: PCI INT A disabled
[ 3401.788072] b44 0000:03:00.0: BAR 0: set to [mem 0xef9fe000-0xef9fffff] 
(PCI address [0xef9fe000-0xef9fffff])
[ 3401.788089] b44 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 3401.848205] ssb: Sonics Silicon Backplane found on PCI device 0000:03:00.0
[ 3401.848317] b44: b44.c:v2.0
[ 3401.869448] b44 ssb0:0: eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet 
00:18:8b:a2:31:e0
[ 3402.073367] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3538.000197] b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex
[ 3538.000201] b44 ssb0:0: eth0: Flow control is off for TX and off for RX
[ 3538.000435] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 3641.732247] b44 ssb0:0: eth0: powering down PHY
[ 3644.412951] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3647.988244] b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex
[ 3647.988252] b44 ssb0:0: eth0: Flow control is off for TX and off for RX
[ 3647.988500] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 4020.988136] b44 ssb0:0: eth0: Link is down
[ 4023.988199] b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex
[ 4023.988205] b44 ssb0:0: eth0: Flow control is off for TX and off for RX
[ 4396.988122] b44 ssb0:0: eth0: Link is down
[ 4399.988197] b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex
[ 4399.988202] b44 ssb0:0: eth0: Flow control is off for TX and off for RX


lsmod |grep b44
b44                    18472  0 
ssb                    33714  1 b44
mii                     2714  1 b44

Thanks,
Vivek.

--- End Message ---
--- Begin Message --- 
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---
Reply to: