Debian Bug report logs - #637240
[regression] Compaq Mini CQ10 hangs after soft reset

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Camaleón <noelamac@gmail.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: linux-image-3.0.0-1-686-pae: Several problems after updating to kernel 3.0

Date: Tue, 09 Aug 2011 21:59:15 +0200

[Message part 1 (text/plain, inline)]

Package: linux-2.6
Version: 3.0.0-1
Severity: important
Tags: wheezy

After updating to latest kernel I faced these problems:

1. NetworkManager seems non-operative (meaning that no wireless network is
available anymore)
2. System hangs at rebooting, which requires me to hard reset the computer

I am attaching full dmesg and an image for the hanging at reboot.

This is a Compaq Mini CQ10 netbook (Atom).

This system is currently running 2.6.39 kernel.

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
not available

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation N10 Family DMI Bridge [8086:a010]
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort+ >SERR- <PERR- INTx-
        Latency: 0
        Capabilities: <access denied>
        Kernel driver in use: agpgart-intel

00:02.0 VGA compatible controller [0300]: Intel Corporation N10 Family
Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller])
        Subsystem: Hewlett-Packard Company Device [103c:148a]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 43
        Region 0: Memory at 94180000 (32-bit, non-prefetchable) [size=512K]
        Region 1: I/O ports at 30c0 [size=8]
        Region 2: Memory at 80000000 (32-bit, prefetchable) [size=256M]
        Region 3: Memory at 94000000 (32-bit, non-prefetchable) [size=1M]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: <access denied>
        Kernel driver in use: i915

00:02.1 Display controller [0380]: Intel Corporation N10 Family Integrated
Graphics Controller [8086:a012]
        Subsystem: Hewlett-Packard Company Device [103c:148a]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Region 0: Memory at 94100000 (32-bit, non-prefetchable) [size=512K]
        Capabilities: <access denied>

00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition
Audio Controller [8086:27d8] (rev 02)
        Subsystem: Hewlett-Packard Company Device [103c:148a]
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 45
        Region 0: Memory at 94200000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: HDA Intel

00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port
1 [8086:27d0] (rev 02) (prog-if 00 [Normal decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 00002000-00002fff
        Memory behind bridge: 93000000-93ffffff
        Prefetchable memory behind bridge: 0000000090000000-0000000090ffffff
        Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- <SERR- <PERR-
        BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
                PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
        Capabilities: <access denied>
        Kernel driver in use: pcieport

00:1c.1 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port
2 [8086:27d2] (rev 02) (prog-if 00 [Normal decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
        I/O behind bridge: 00001000-00001fff
        Memory behind bridge: 92000000-92ffffff
        Prefetchable memory behind bridge: 0000000091000000-0000000091ffffff
        Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- <SERR- <PERR-
        BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
                PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
        Capabilities: <access denied>
        Kernel driver in use: pcieport

00:1d.0 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI
Controller #1 [8086:27c8] (rev 02) (prog-if 00 [UHCI])
        Subsystem: Hewlett-Packard Company Device [103c:148a]
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 16
        Region 4: I/O ports at 3080 [size=32]
        Kernel driver in use: uhci_hcd

00:1d.1 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI
Controller #2 [8086:27c9] (rev 02) (prog-if 00 [UHCI])
        Subsystem: Hewlett-Packard Company Device [103c:148a]
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin C routed to IRQ 18
        Region 4: I/O ports at 3060 [size=32]
        Kernel driver in use: uhci_hcd

00:1d.2 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI
Controller #3 [8086:27ca] (rev 02) (prog-if 00 [UHCI])
        Subsystem: Hewlett-Packard Company Device [103c:148a]
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin B routed to IRQ 17
        Region 4: I/O ports at 3040 [size=32]
        Kernel driver in use: uhci_hcd

00:1d.3 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI
Controller #4 [8086:27cb] (rev 02) (prog-if 00 [UHCI])
        Subsystem: Hewlett-Packard Company Device [103c:148a]
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin D routed to IRQ 19
        Region 4: I/O ports at 3020 [size=32]
        Kernel driver in use: uhci_hcd

00:1d.7 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB2 EHCI
Controller [8086:27cc] (rev 02) (prog-if 20 [EHCI])
        Subsystem: Hewlett-Packard Company Device [103c:148a]
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at 94204400 (32-bit, non-prefetchable) [size=1K]
        Capabilities: <access denied>
        Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge
[8086:2448] (rev e2) (prog-if 01 [Subtractive decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Bus: primary=00, secondary=03, subordinate=03, sec-latency=32
        Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ <SERR- <PERR-
        BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
                PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
        Capabilities: <access denied>

00:1f.0 ISA bridge [0601]: Intel Corporation NM10 Family LPC Controller
[8086:27bc] (rev 02)
        Subsystem: Hewlett-Packard Company Device [103c:148a]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Capabilities: <access denied>

00:1f.2 SATA controller [0106]: Intel Corporation N10/ICH7 Family SATA AHCI
Controller [8086:27c1] (rev 02) (prog-if 01 [AHCI 1.0])
        Subsystem: Hewlett-Packard Company Device [103c:148a]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin B routed to IRQ 42
        Region 0: I/O ports at 30b8 [size=8]
        Region 1: I/O ports at 30cc [size=4]
        Region 2: I/O ports at 30b0 [size=8]
        Region 3: I/O ports at 30c8 [size=4]
        Region 4: I/O ports at 30a0 [size=16]
        Region 5: Memory at 94204000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: <access denied>
        Kernel driver in use: ahci

00:1f.3 SMBus [0c05]: Intel Corporation N10/ICH 7 Family SMBus Controller
[8086:27da] (rev 02)
        Subsystem: Hewlett-Packard Company Device [103c:148a]
        Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin B routed to IRQ 17
        Region 4: I/O ports at 3000 [size=32]
        Kernel driver in use: i801_smbus

01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 04)
        Subsystem: Hewlett-Packard Company Device [103c:148a]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 44
        Region 0: I/O ports at 2000 [size=256]
        Region 2: Memory at 90004000 (64-bit, prefetchable) [size=4K]
        Region 4: Memory at 90000000 (64-bit, prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: r8169

01:00.1 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5288] (rev 01)
        Subsystem: Hewlett-Packard Company Device [103c:148a]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin B routed to IRQ 10
        Region 0: Memory at 93000000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: <access denied>

02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n
Wireless LAN Controller [14e4:4727] (rev 01)
        Subsystem: Hewlett-Packard Company Device [103c:145c]
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 17
        Region 0: Memory at 92000000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: brcmsmac



** USB devices:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 174f:1122 Syntek 


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.39-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-3.0.0-1-686-pae depends on:
ii  debconf [debconf-2.0]         1.5.40     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.99       tools for generating an initramfs
ii  linux-base                    3.3        Linux image base package
ii  module-init-tools             3.16-1     tools for managing Linux kernel mo

Versions of packages linux-image-3.0.0-1-686-pae recommends:
ii  firmware-linux-free           3          Binary firmware for various driver
ii  libc6-i686                    2.13-10    Embedded GNU C Library: Shared lib

Versions of packages linux-image-3.0.0-1-686-pae suggests:
ii  grub-pc                       1.99-9     GRand Unified Bootloader, version 
pn  linux-doc-3.0.0               <none>     (no description available)

Versions of packages linux-image-3.0.0-1-686-pae is related to:
pn  firmware-bnx2                 <none>     (no description available)
pn  firmware-bnx2x                <none>     (no description available)
pn  firmware-ipw2x00              <none>     (no description available)
pn  firmware-ivtv                 <none>     (no description available)
pn  firmware-iwlwifi              <none>     (no description available)
pn  firmware-linux                <none>     (no description available)
pn  firmware-linux-nonfree        <none>     (no description available)
pn  firmware-qlogic               <none>     (no description available)
ii  firmware-ralink               0.33       Binary firmware for Ralink wireles
pn  xen-hypervisor                <none>     (no description available)

-- debconf information excluded

[reboot_hangs.JPG (image/jpeg, attachment)]

[dmesg.0 (text/x-c++, attachment)]

Message #10 received at 637240@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: Camaleón <noelamac@gmail.com>

Cc: 637240@bugs.debian.org

Subject: Re: linux-image-3.0.0-1-686-pae: Several problems after updating to kernel 3.0

Date: Tue, 9 Aug 2011 17:08:21 -0500

# bug likely applies to sid, too
tags 637240 - wheezy
retitle 637240 [regression] Compaq Mini CQ10 hangs after soft reset
quit

Hi,

Camaleón wrote:

> After updating to latest kernel I faced these problems:
>
> 1. NetworkManager seems non-operative (meaning that no wireless network is
> available anymore)
> 2. System hangs at rebooting, which requires me to hard reset the computer
>
> I am attaching full dmesg and an image for the hanging at reboot.

Thanks for testing.  Re (2), the first question is where it is
hanging.  Does booting without the broadcom and bluetooth drivers work
any better?  If you can get into a rescue shell with the
"break=modules" commandline parameter, it might be possible to get a
backtrace during the hang, like so:

	echo 1 >/proc/sys/kernel/sysrq
	... trigger the hang ...
	alt+sysrq, C (or D, or T, whatever makes sense)

initramfs-tools(8) and Documentation/sysrq.txt have details.

Let's make this bug about (2).  Could you file a separate bug for (1)?

Regards,
Jonathan

Message #19 received at 637240@bugs.debian.org (full text, mbox, reply):

From: Camaleón <noelamac@gmail.com>

To: Jonathan Nieder <jrnieder@gmail.com>

Cc: 637240@bugs.debian.org

Subject: Re: linux-image-3.0.0-1-686-pae: Several problems after updating to kernel 3.0

Date: Wed, 10 Aug 2011 09:47:09 +0200

El 2011-08-09 a las 17:08 -0500, Jonathan Nieder escribió:

> Thanks for testing.  Re (2), the first question is where it is
> hanging.  Does booting without the broadcom and bluetooth drivers work
> any better?  If you can get into a rescue shell with the
> "break=modules" commandline parameter, it might be possible to get a
> backtrace during the hang, like so:
> 
> 	echo 1 >/proc/sys/kernel/sysrq
> 	... trigger the hang ...
> 	alt+sysrq, C (or D, or T, whatever makes sense)
> 
> initramfs-tools(8) and Documentation/sysrq.txt have details.

I hate to say this but after a cold start the error/hang is not 
reproducible anymore... and I did nothing. Now the system 
restarts/shutdowns fine, with no delay nor errors on the screen.

> Let's make this bug about (2).  Could you file a separate bug for (1)?

Sure, I'm still facing the NM problem, will write a new bug for that.

Thanks. I think you can close now this report.

Greetings,

-- 
Camaleón 

Message #24 received at 637240@bugs.debian.org (full text, mbox, reply):

From: Camaleón <noelamac@gmail.com>

To: Jonathan Nieder <jrnieder@gmail.com>

Cc: 637240@bugs.debian.org

Subject: Re: linux-image-3.0.0-1-686-pae: Several problems after updating to kernel 3.0

Date: Wed, 10 Aug 2011 10:56:33 +0200

[Message part 1 (text/plain, inline)]

2011/8/10 Camaleón <noelamac@gmail.com>:

> I hate to say this but after a cold start the error/hang is not
> reproducible anymore... and I did nothing. Now the system
> restarts/shutdowns fine, with no delay nor errors on the screen.

I spoke too soon.

While the system still restarts with no issues, if I force an unload
of the wireless card module (modprobe -r brcmsmac) I can reproduce the
hang... and this time with a call trace (see attached document).

I think this is what makes NM to malfunction (it does not detect the
broadcom wifi card) :-?

Greetings,

-- 
Camaleón

[calltrace.txt (text/plain, attachment)]

Message #29 received at 637240@bugs.debian.org (full text, mbox, reply):

From: Camaleón <noelamac@gmail.com>

To: 637240@bugs.debian.org

Cc: Jonathan Nieder <jrnieder@gmail.com>

Subject: Additional info

Date: Sat, 13 Aug 2011 17:25:00 +0200

Hi,

This is what I get when I force NM to connect to the AP:

Aug 13 17:09:05 stt300 kernel: [11545.044034] pci 0000:01:00.1: vpd
r/w failed.  This is likely a firmware bug on this device.  Contact
the card vendor for a firmware update.

OTHO, using another wifi adapter (RT2870) works fine and NM can
establish a connection with the AP. It seems the problem is only with
"brcmsmac" module.

Greetings,

-- 
Camaleón

Message #34 received at 637240@bugs.debian.org (full text, mbox, reply):

From: Camaleón <noelamac@gmail.com>

To: 637240@bugs.debian.org

Cc: Jonathan Nieder <jrnieder@gmail.com>

Subject: Final info...

Date: Sat, 13 Aug 2011 19:16:25 +0200

I don't know what's going on here but this has started working as soon
as I brought the netbook next to the AP:

root@stt300:~# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"WLAN_B5"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:23:F8:9D:AD:11
          Bit Rate=54 Mb/s   Tx-Power=19 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=70/70  Signal level=-35 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:26   Missed beacon:0

Aug 13 19:00:04 stt300 kernel: [ 1347.536793] wlan0: associated
Aug 13 19:00:04 stt300 wpa_supplicant[1089]: Associated with 00:23:f8:9d:ad:11
Aug 13 19:00:04 stt300 kernel: [ 1347.545284] ieee80211 phy0:
brcmsmac: wl_ops_bss_info_changed: associated
Aug 13 19:00:04 stt300 NetworkManager[1066]: <info> (wlan0):
supplicant connection state:  associating -> associated
Aug 13 19:00:05 stt300 NetworkManager[1066]: <info> (wlan0):
supplicant connection state:  associated -> 4-way handshake

I think this bug can be closed, I know the brcmsmac is a stage driver
and so we can experience some problems with it. Anyway, I will keep an
eye on it.

Greetings,

-- 
Camaleón

Message #39 received at 637240@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: Camaleón <noelamac@gmail.com>

Cc: 637240@bugs.debian.org

Subject: Re: brcmsmac: "firmware bug" warning when connecting, hang when unloading brcmsmac driver unless near AP

Date: Sat, 13 Aug 2011 12:23:31 -0500

Camaleón wrote:

> I don't know what's going on here but this has started working as soon
> as I brought the netbook next to the AP:
[...]
> I think this bug can be closed, I know the brcmsmac is a stage driver
> and so we can experience some problems with it. Anyway, I will keep an
> eye on it.

What is staging for, if not for finding bugs like this before they
affect more people?  Please send a summary of your findings to
linux-wireless@vger.kernel.org, cc-ing devel@driverdev.osuosl.org
and

M:      Brett Rudley <brudley@broadcom.com>
M:      Henry Ptasinski <henryp@broadcom.com>
M:      Roland Vossen <rvossen@broadcom.com>
M:      Arend van Spriel <arend@broadcom.com>
M:      Franky (Zhenhui) Lin <frankyl@broadcom.com>
M:      Kan Yan <kanyan@broadcom.com>

(list taken from MAINTAINERS in the source tree), and this bug log.

Thanks very much for your work, and I hope it can result in a fix
soon.

Message #44 received at 637240@bugs.debian.org (full text, mbox, reply):

From: Camaleón <noelamac@gmail.com>

To: Jonathan Nieder <jrnieder@gmail.com>

Cc: 637240@bugs.debian.org

Subject: Re: brcmsmac: "firmware bug" warning when connecting, hang when unloading brcmsmac driver unless near AP

Date: Sun, 14 Aug 2011 13:36:07 +0200

2011/8/13 Jonathan Nieder <jrnieder@gmail.com>:
> Camaleón wrote:
>
>> I don't know what's going on here but this has started working as soon
>> as I brought the netbook next to the AP:
> [...]
>> I think this bug can be closed, I know the brcmsmac is a stage driver
>> and so we can experience some problems with it. Anyway, I will keep an
>> eye on it.
>
> What is staging for, if not for finding bugs like this before they
> affect more people?  Please send a summary of your findings to
> linux-wireless@vger.kernel.org, cc-ing devel@driverdev.osuosl.org
> and
>
> M:      Brett Rudley <brudley@broadcom.com>
> M:      Henry Ptasinski <henryp@broadcom.com>
> M:      Roland Vossen <rvossen@broadcom.com>
> M:      Arend van Spriel <arend@broadcom.com>
> M:      Franky (Zhenhui) Lin <frankyl@broadcom.com>
> M:      Kan Yan <kanyan@broadcom.com>
>
> (list taken from MAINTAINERS in the source tree), and this bug log.
>
> Thanks very much for your work, and I hope it can result in a fix
> soon.

I would really like to test this further but I dunno from where to start.

What I've find out is that the wireless card starts working as soon as
I put the netbook next to the AP, then NetworkManager starts its
detection routine and associates fine with the AP. After that, wifi
connection keeps stable and available regardless I possition the
netbook.

I will write to the suggested mailing lists (thanks for that!) and
also to the mentioned devels and hope this can be solved soon.

Greetings,

-- 
Camaleón

Message #51 received at 637240@bugs.debian.org (full text, mbox, reply):

From: Camaleón <noelamac@gmail.com>

To: 637240@bugs.debian.org, Jonathan Nieder <jrnieder@gmail.com>

Subject: (Solved) Re: brcmsmac: "firmware bug" warning when connecting, hang when unloading brcmsmac driver unless near AP

Date: Sat, 11 Feb 2012 12:24:09 +0100

Just an update for this issue.

I tried kernel 3.3-rc3 and brcmsmac has started working, it can see
the AP regardless the netbook location and network-manager does not
hang.

Greetings,

-- 
Camaleón

Message #56 received at 637240@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: Camaleón <noelamac@gmail.com>

Cc: 637240@bugs.debian.org

Subject: Re: (Solved) Re: brcmsmac: "firmware bug" warning when connecting, hang when unloading brcmsmac driver unless near AP

Date: Sat, 11 Feb 2012 05:39:38 -0600

tags 637240 + fixed-upstream
quit

Hi,

Camaleón wrote:

> Just an update for this issue.
>
> I tried kernel 3.3-rc3 and brcmsmac has started working, it can see
> the AP regardless the netbook location and network-manager does not
> hang.

Nice.

What's the newest broken kernel version you know of?  If someone
suggests versions to test or a patch to apply, would you be able to
run tests in order to help get a patch for sid (which is a 3.2.y
kernel) ready?

Thanks,
Jonathan

Message #63 received at 637240@bugs.debian.org (full text, mbox, reply):

From: Camaleón <noelamac@gmail.com>

To: Jonathan Nieder <jrnieder@gmail.com>

Cc: 637240@bugs.debian.org

Subject: Re: (Solved) Re: brcmsmac: "firmware bug" warning when connecting, hang when unloading brcmsmac driver unless near AP

Date: Sat, 11 Feb 2012 12:59:03 +0100

El 2012-02-11 a las 05:39 -0600, Jonathan Nieder escribió:

> > I tried kernel 3.3-rc3 and brcmsmac has started working, it can see
> > the AP regardless the netbook location and network-manager does not
> > hang.
> 
> Nice.
> 
> What's the newest broken kernel version you know of?  If someone
> suggests versions to test or a patch to apply, would you be able to
> run tests in order to help get a patch for sid (which is a 3.2.y
> kernel) ready?

The last kernel I compiled and still was not working was 3.2-rc3 
(from upstream kernel sources).

Yes, I can install whatever kernel version you require or run any 
tests/patches you need.

My current wheezy install has Debian's stock kernel 3.1 and here I 
have to use the "wl" closed source driver to get the wireless card 
working :-(

Greetings,

-- 
Camaleón 

Message #68 received at 637240@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: Camaleón <noelamac@gmail.com>

Cc: 637240@bugs.debian.org

Subject: Re: (Solved) Re: brcmsmac: "firmware bug" warning when connecting, hang when unloading brcmsmac driver unless near AP

Date: Sat, 11 Feb 2012 06:08:48 -0600

Camaleón wrote:

> Yes, I can install whatever kernel version you require or run any 
> tests/patches you need.

Excellent.  Please test v3.2.4 from unstable.  (It includes the
following patch.)

Thanks,
Jonathan

commit 4bc34a5c5c4e
Author: Stanislaw Gruszka <sgruszka@redhat.com>
Date:   Tue Jan 17 12:38:50 2012 +0100

    brcmsmac: fix tx queue flush infinite loop

    commit f96b08a7e6f69c0f0a576554df3df5b1b519c479 upstream.

    This patch workaround live deadlock problem caused by infinite loop
    in brcms_c_wait_for_tx_completion(). I do not consider the patch as
    the proper fix, which should fix the real reason of tx queue flush
    failure, but patch helps with system lockup.

    Reference:
    https://bugzilla.kernel.org/show_bug.cgi?id=42576

    Reported-and-tested-by: Patrick <ragamuffin@datacomm.ch>
    Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

diff --git a/drivers/net/wireless/brcm80211/brcmsmac/main.c b/drivers/net/wireless/brcm80211/brcmsmac/main.c
index 510e9bb52287..453f58e5667f 100644
--- a/drivers/net/wireless/brcm80211/brcmsmac/main.c
+++ b/drivers/net/wireless/brcm80211/brcmsmac/main.c
@@ -8217,13 +8217,21 @@ int brcms_c_get_curband(struct brcms_c_info *wlc)
 
 void brcms_c_wait_for_tx_completion(struct brcms_c_info *wlc, bool drop)
 {
+	int timeout = 20;
+
 	/* flush packet queue when requested */
 	if (drop)
 		brcmu_pktq_flush(&wlc->pkt_queue->q, false, NULL, NULL);
 
 	/* wait for queue and DMA fifos to run dry */
-	while (!pktq_empty(&wlc->pkt_queue->q) || brcms_txpktpendtot(wlc) > 0)
+	while (!pktq_empty(&wlc->pkt_queue->q) || brcms_txpktpendtot(wlc) > 0) {
 		brcms_msleep(wlc->wl, 1);
+
+		if (--timeout == 0)
+			break;
+	}
+
+	WARN_ON_ONCE(timeout == 0);
 }
 
 void brcms_c_set_beacon_listen_interval(struct brcms_c_info *wlc, u8 interval)

Message #73 received at 637240@bugs.debian.org (full text, mbox, reply):

From: Camaleón <noelamac@gmail.com>

To: Jonathan Nieder <jrnieder@gmail.com>

Cc: 637240@bugs.debian.org

Subject: Re: (Solved) Re: brcmsmac: "firmware bug" warning when connecting, hang when unloading brcmsmac driver unless near AP

Date: Sat, 11 Feb 2012 16:01:58 +0100

2012/2/11 Jonathan Nieder <jrnieder@gmail.com>:
> Camaleón wrote:
>
>> Yes, I can install whatever kernel version you require or run any
>> tests/patches you need.
>
> Excellent.  Please test v3.2.4 from unstable.  (It includes the
> following patch.)
>
> Thanks,
> Jonathan
>
> commit 4bc34a5c5c4e
> Author: Stanislaw Gruszka <sgruszka@redhat.com>
> Date:   Tue Jan 17 12:38:50 2012 +0100
>
>    brcmsmac: fix tx queue flush infinite loop
>
>    commit f96b08a7e6f69c0f0a576554df3df5b1b519c479 upstream.

(...)

It works! :-)

root@stt300:~# uname -a
Linux stt300 3.2.0-1-686-pae #1 SMP Sun Feb 5 23:52:49 UTC 2012 i686 GNU/Linux

root@stt300:~# dpkg -l | grep -i -e linux-image-3.2
ii  linux-image-3.2.0-1-686-pae          3.2.4-1
 Linux 3.2 for modern PCs

root@stt300:~# cat /etc/debian_version
wheezy/sid

Greetings,

-- 
Camaleón

Message #78 received at 637240-done@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: Camaleón <noelamac@gmail.com>

Cc: 637240-done@bugs.debian.org

Subject: Re: (Solved) Re: brcmsmac: "firmware bug" warning when connecting, hang when unloading brcmsmac driver unless near AP

Date: Sat, 11 Feb 2012 14:09:01 -0600

Version: 3.2.4-1

Camaleón wrote:

> It works! :-)
>
> root@stt300:~# uname -a
> Linux stt300 3.2.0-1-686-pae #1 SMP Sun Feb 5 23:52:49 UTC 2012 i686 GNU/Linux
>
> root@stt300:~# dpkg -l | grep -i -e linux-image-3.2
> ii  linux-image-3.2.0-1-686-pae          3.2.4-1
>  Linux 3.2 for modern PCs

Nice to hear.  Thanks for testing.

Send a report that this bug log contains spam.