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

Bug#863641: marked as done (4.9.0-3-amd64: bcm43235 wireless adapter crashes usb hub at the kernel level. when hub crashes can't detect more usb devices. confirmed on more than one computer running same kernel.)



Your message dated Mon, 24 May 2021 19:16:17 +0200
with message-id <E1llEBU-0009ft-Fl@hullmann.westfalen.local>
and subject line Closing this bug
has caused the Debian Bug report #863641,
regarding 4.9.0-3-amd64: bcm43235 wireless adapter crashes usb hub at the kernel level.  when hub crashes can't detect more usb devices.  confirmed on more than one computer running same kernel.
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.)


-- 
863641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863641
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: 4.9.0-3-amd64
Version: debian stretch latest kernel release
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Inserting usb wireless adapter BCM43235 into usb ports crashes kernel usb hub.
when adapter is taken out it is still listed when lsusb is executed.
reinsertion and removal several times crashes the usb hub at the kernel level
and no more usb devices work.  Have confirmed on several computers using the
same kernel (latest release in stretch 64 bit.)  Wireless adapter works on
other kernel versions.
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
Wireless mouse and primary usb adapter were already plugged in and working.
Other wireless cards when plugged in could not be read after hub crash.

Causes the following system errors as seen in log:

May 28 18:05:33 stack kernel: [  220.088558] usb 1-3: new high-speed USB device
number 8 using xhci_hcd
May 28 18:05:33 stack kernel: [  220.232539] usb 1-3: New USB device found,
idVendor=13b1, idProduct=0039
May 28 18:05:33 stack kernel: [  220.232546] usb 1-3: New USB device strings:
Mfr=1, Product=2, SerialNumber=3
May 28 18:05:33 stack kernel: [  220.232551] usb 1-3: Product: Linksys AE1200
May 28 18:05:33 stack kernel: [  220.232555] usb 1-3: Manufacturer: Cisco
May 28 18:05:33 stack kernel: [  220.232559] usb 1-3: SerialNumber:
000000000001
May 28 18:05:33 stack mtp-probe: checking bus 1, device 8:
"/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3"
May 28 18:05:33 stack mtp-probe: bus: 1, device: 8 was not an MTP device
May 28 18:05:33 stack kernel: [  220.392143] usbcore: registered new interface
driver brcmfmac
May 28 18:05:33 stack kernel: [  220.392293] usb 1-3: firmware: failed to load
brcm/brcmfmac43236b.bin (-2)
May 28 18:05:33 stack kernel: [  220.392311] usb 1-3: Direct firmware load for
brcm/brcmfmac43236b.bin failed with error -2
May 28 18:05:58 stack kernel: [  245.482231] usb 1-3: USB disconnect, device
number 8
May 28 18:07:34 stack /usr/lib/gdm3/gdm-x-session[1247]: (II) config/udev:
removing device Logitech USB Receiver
May 28 18:07:34 stack /usr/lib/gdm3/gdm-x-session[1247]: (**) Option "fd" "25"
May 28 18:07:34 stack /usr/lib/gdm3/gdm-x-session[1247]: (II) UnloadModule:
"libinput"
May 28 18:07:34 stack /usr/lib/gdm3/gdm-x-session[1247]: (II) systemd-logind:
releasing fd for 13:65
May 28 18:07:34 stack /usr/lib/gdm3/gdm-x-session[1247]: (II) config/udev:
removing device Logitech USB Receiver
May 28 18:07:34 stack /usr/lib/gdm3/gdm-x-session[1247]: (**) Option "fd" "26"
May 28 18:07:34 stack /usr/lib/gdm3/gdm-x-session[1247]: (II) UnloadModule:
"libinput"
May 28 18:07:34 stack /usr/lib/gdm3/gdm-x-session[1247]: (II) systemd-logind:
not releasing fd for 13:66, still in use
May 28 18:07:34 stack /usr/lib/gdm3/gdm-x-session[1247]: (II) config/udev:
removing device Logitech USB Receiver
May 28 18:07:34 stack /usr/lib/gdm3/gdm-x-session[1247]: (**) Option "fd" "26"
May 28 18:07:34 stack /usr/lib/gdm3/gdm-x-session[1247]: (II) UnloadModule:
"libinput"
May 28 18:07:34 stack /usr/lib/gdm3/gdm-x-session[1247]: (II) systemd-logind:
releasing fd for 13:66
May 28 18:07:57 stack kernel: [  363.480261] INFO: task kworker/0:1:37 blocked
for more than 120 seconds.
May 28 18:07:57 stack kernel: [  363.480274]       Tainted: G           O
4.9.0-3-amd64 #1
May 28 18:07:57 stack kernel: [  363.480279] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 28 18:07:57 stack kernel: [  363.480285] kworker/0:1     D    0    37
2 0x00000000
May 28 18:07:57 stack kernel: [  363.480304] Workqueue: events
request_firmware_work_func
May 28 18:07:57 stack kernel: [  363.480310]  ffff90c7e0771c00 0000000000000000
ffff90c7e4f14000 ffff90c7eec18240
May 28 18:07:57 stack kernel: [  363.480320]  ffff90c7df6c7040 ffffb56fc0de3b28
ffffffffbe9ff483 ffffffffbe9ff952
May 28 18:07:57 stack kernel: [  363.480328]  0000000000000000 ffff90c7eec18240
ffffffffbe4c05c4 ffff90c7e4f14000
May 28 18:07:57 stack kernel: [  363.480336] Call Trace:
May 28 18:07:57 stack kernel: [  363.480350]  [<ffffffffbe9ff483>] ?
__schedule+0x233/0x6d0
May 28 18:07:57 stack kernel: [  363.480357]  [<ffffffffbe9ff952>] ?
schedule+0x32/0x80
May 28 18:07:57 stack kernel: [  363.480366]  [<ffffffffbe4c05c4>] ?
mutex_optimistic_spin+0x164/0x1b0
May 28 18:07:57 stack kernel: [  363.480372]  [<ffffffffbe9ff952>] ?
schedule+0x32/0x80
May 28 18:07:57 stack kernel: [  363.480379]  [<ffffffffbe9ffbea>] ?
schedule_preempt_disabled+0xa/0x10
May 28 18:07:57 stack kernel: [  363.480385]  [<ffffffffbea01634>] ?
__mutex_lock_slowpath+0xb4/0x130
May 28 18:07:57 stack kernel: [  363.480397]  [<ffffffffbea016cb>] ?
mutex_lock+0x1b/0x30
May 28 18:07:57 stack kernel: [  363.480429]  [<ffffffffc0eff802>] ?
brcmf_usb_disconnect+0x22/0x60 [brcmfmac]
May 28 18:07:57 stack kernel: [  363.480467]  [<ffffffffc0112671>] ?
usb_unbind_interface+0x71/0x270 [usbcore]
May 28 18:07:57 stack kernel: [  363.480480]  [<ffffffffbe87338a>] ?
__device_release_driver+0x9a/0x150
May 28 18:07:57 stack kernel: [  363.480488]  [<ffffffffbe87345e>] ?
device_release_driver+0x1e/0x30
May 28 18:07:57 stack kernel: [  363.480496]  [<ffffffffbe872ab5>] ?
bus_remove_device+0xf5/0x160
May 28 18:07:57 stack kernel: [  363.480502]  [<ffffffffbe86ef47>] ?
device_del+0x127/0x260
May 28 18:07:57 stack kernel: [  363.480532]  [<ffffffffc011701b>] ?
usb_remove_ep_devs+0x1b/0x30 [usbcore]
May 28 18:07:57 stack kernel: [  363.480562]  [<ffffffffc01100e3>] ?
usb_disable_device+0x93/0x250 [usbcore]
May 28 18:07:57 stack kernel: [  363.480589]  [<ffffffffc0110a88>] ?
usb_set_configuration+0xe8/0x8c0 [usbcore]
May 28 18:07:57 stack kernel: [  363.480616]  [<ffffffffc0117963>] ?
usbdev_notify+0x13/0x20 [usbcore]
May 28 18:07:57 stack kernel: [  363.480628]  [<ffffffffbe497f4b>] ?
__blocking_notifier_call_chain+0x4b/0x60
May 28 18:07:57 stack kernel: [  363.480656]  [<ffffffffc01120ab>] ?
usb_unbind_device+0x1b/0x50 [usbcore]
May 28 18:07:57 stack kernel: [  363.480664]  [<ffffffffbe87338a>] ?
__device_release_driver+0x9a/0x150
May 28 18:07:57 stack kernel: [  363.480672]  [<ffffffffbe87345e>] ?
device_release_driver+0x1e/0x30
May 28 18:07:57 stack kernel: [  363.480700]  [<ffffffffc0ef2af0>] ?
brcmf_fw_request_code_done+0x80/0x90 [brcmfmac]
May 28 18:07:57 stack kernel: [  363.480705]  [<ffffffffbe8887a1>] ?
request_firmware_work_func+0x41/0x80
May 28 18:07:57 stack kernel: [  363.480711]  [<ffffffffbe490374>] ?
process_one_work+0x184/0x410
May 28 18:07:57 stack kernel: [  363.480716]  [<ffffffffbe49064d>] ?
worker_thread+0x4d/0x480
May 28 18:07:57 stack kernel: [  363.480721]  [<ffffffffbe490600>] ?
process_one_work+0x410/0x410
May 28 18:07:57 stack kernel: [  363.480729]  [<ffffffffbe4965c7>] ?
kthread+0xd7/0xf0
May 28 18:07:57 stack kernel: [  363.480736]  [<ffffffffbe4964f0>] ?
kthread_park+0x60/0x60
May 28 18:07:57 stack kernel: [  363.480745]  [<ffffffffbea043b5>] ?
ret_from_fork+0x25/0x30
May 28 18:09:57 stack kernel: [  484.424089] INFO: task kworker/0:1:37 blocked
for more than 120 seconds.
May 28 18:09:57 stack kernel: [  484.424102]       Tainted: G           O
4.9.0-3-amd64 #1
May 28 18:09:57 stack kernel: [  484.424107] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 28 18:09:57 stack kernel: [  484.424113] kworker/0:1     D    0    37
2 0x00000000
May 28 18:09:57 stack kernel: [  484.424132] Workqueue: events
request_firmware_work_func
May 28 18:09:57 stack kernel: [  484.424138]  ffff90c7e0771c00 0000000000000000
ffff90c7e4f14000 ffff90c7eec18240
May 28 18:09:57 stack kernel: [  484.424148]  ffff90c7df6c7040 ffffb56fc0de3b28
ffffffffbe9ff483 ffffffffbe9ff952
May 28 18:09:57 stack kernel: [  484.424157]  0000000000000000 ffff90c7eec18240
ffffffffbe4c05c4 ffff90c7e4f14000
May 28 18:09:57 stack kernel: [  484.424165] Call Trace:
May 28 18:09:57 stack kernel: [  484.424179]  [<ffffffffbe9ff483>] ?
__schedule+0x233/0x6d0
May 28 18:09:57 stack kernel: [  484.424185]  [<ffffffffbe9ff952>] ?
schedule+0x32/0x80
May 28 18:09:57 stack kernel: [  484.424195]  [<ffffffffbe4c05c4>] ?
mutex_optimistic_spin+0x164/0x1b0
May 28 18:09:57 stack kernel: [  484.424201]  [<ffffffffbe9ff952>] ?
schedule+0x32/0x80
May 28 18:09:57 stack kernel: [  484.424207]  [<ffffffffbe9ffbea>] ?
schedule_preempt_disabled+0xa/0x10
May 28 18:09:57 stack kernel: [  484.424214]  [<ffffffffbea01634>] ?
__mutex_lock_slowpath+0xb4/0x130
May 28 18:09:57 stack kernel: [  484.424226]  [<ffffffffbea016cb>] ?
mutex_lock+0x1b/0x30
May 28 18:09:57 stack kernel: [  484.424258]  [<ffffffffc0eff802>] ?
brcmf_usb_disconnect+0x22/0x60 [brcmfmac]
May 28 18:09:57 stack kernel: [  484.424297]  [<ffffffffc0112671>] ?
usb_unbind_interface+0x71/0x270 [usbcore]
May 28 18:09:57 stack kernel: [  484.424308]  [<ffffffffbe87338a>] ?
__device_release_driver+0x9a/0x150
May 28 18:09:57 stack kernel: [  484.424317]  [<ffffffffbe87345e>] ?
device_release_driver+0x1e/0x30
May 28 18:09:57 stack kernel: [  484.424325]  [<ffffffffbe872ab5>] ?
bus_remove_device+0xf5/0x160
May 28 18:09:57 stack kernel: [  484.424331]  [<ffffffffbe86ef47>] ?
device_del+0x127/0x260
May 28 18:09:57 stack kernel: [  484.424361]  [<ffffffffc011701b>] ?
usb_remove_ep_devs+0x1b/0x30 [usbcore]
May 28 18:09:57 stack kernel: [  484.424390]  [<ffffffffc01100e3>] ?
usb_disable_device+0x93/0x250 [usbcore]
May 28 18:09:57 stack kernel: [  484.424417]  [<ffffffffc0110a88>] ?
usb_set_configuration+0xe8/0x8c0 [usbcore]
May 28 18:09:57 stack kernel: [  484.424444]  [<ffffffffc0117963>] ?
usbdev_notify+0x13/0x20 [usbcore]
May 28 18:09:57 stack kernel: [  484.424455]  [<ffffffffbe497f4b>] ?
__blocking_notifier_call_chain+0x4b/0x60
May 28 18:09:57 stack kernel: [  484.424483]  [<ffffffffc01120ab>] ?
usb_unbind_device+0x1b/0x50 [usbcore]
May 28 18:09:57 stack kernel: [  484.424491]  [<ffffffffbe87338a>] ?
__device_release_driver+0x9a/0x150
May 28 18:09:57 stack kernel: [  484.424499]  [<ffffffffbe87345e>] ?
device_release_driver+0x1e/0x30
May 28 18:09:57 stack kernel: [  484.424527]  [<ffffffffc0ef2af0>] ?
brcmf_fw_request_code_done+0x80/0x90 [brcmfmac]
May 28 18:09:57 stack kernel: [  484.424532]  [<ffffffffbe8887a1>] ?
request_firmware_work_func+0x41/0x80
May 28 18:09:57 stack kernel: [  484.424538]  [<ffffffffbe490374>] ?
process_one_work+0x184/0x410
May 28 18:09:57 stack kernel: [  484.424544]  [<ffffffffbe49064d>] ?
worker_thread+0x4d/0x480
May 28 18:09:57 stack kernel: [  484.424548]  [<ffffffffbe490600>] ?
process_one_work+0x410/0x410
May 28 18:09:57 stack kernel: [  484.424555]  [<ffffffffbe4965c7>] ?
kthread+0xd7/0xf0
May 28 18:09:57 stack kernel: [  484.424563]  [<ffffffffbe4964f0>] ?
kthread_park+0x60/0x60
May 28 18:09:57 stack kernel: [  484.424572]  [<ffffffffbea043b5>] ?
ret_from_fork+0x25/0x30
May 28 18:09:57 stack kernel: [  484.424581] INFO: task kworker/3:1:45 blocked
for more than 120 seconds.
May 28 18:09:57 stack kernel: [  484.424588]       Tainted: G           O
4.9.0-3-amd64 #1
May 28 18:09:57 stack kernel: [  484.424592] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 28 18:09:57 stack kernel: [  484.424596] kworker/3:1     D    0    45
2 0x00000000
May 28 18:09:57 stack kernel: [  484.424629] Workqueue: usb_hub_wq hub_event
[usbcore]
May 28 18:09:57 stack kernel: [  484.424634]  ffff90c7e2077c00 0000000000000000
ffff90c7e4909000 ffff90c7eed98240
May 28 18:09:57 stack kernel: [  484.424642]  ffff90c7e52cf080 ffffb56fc0e23c78
ffffffffbe9ff483 ffffffffbe86f4ae
May 28 18:09:57 stack kernel: [  484.424651]  00ff90c700000030 ffff90c7eed98240
ffffb56fc0e23c58 ffff90c7e4909000
May 28 18:09:57 stack kernel: [  484.424659] Call Trace:
May 28 18:09:57 stack kernel: [  484.424666]  [<ffffffffbe9ff483>] ?
__schedule+0x233/0x6d0
May 28 18:09:57 stack kernel: [  484.424673]  [<ffffffffbe86f4ae>] ?
dev_printk_emit+0x4e/0x70
May 28 18:09:57 stack kernel: [  484.424679]  [<ffffffffbe9ff952>] ?
schedule+0x32/0x80
May 28 18:09:57 stack kernel: [  484.424685]  [<ffffffffbe9ffbea>] ?
schedule_preempt_disabled+0xa/0x10
May 28 18:09:57 stack kernel: [  484.424691]  [<ffffffffbea01634>] ?
__mutex_lock_slowpath+0xb4/0x130
May 28 18:09:57 stack kernel: [  484.424697]  [<ffffffffbea016cb>] ?
mutex_lock+0x1b/0x30
May 28 18:09:57 stack kernel: [  484.424722]  [<ffffffffc0105caf>] ?
usb_disconnect+0x4f/0x260 [usbcore]
May 28 18:09:57 stack kernel: [  484.424747]  [<ffffffffc0108056>] ?
hub_event+0x9b6/0x14d0 [usbcore]
May 28 18:09:57 stack kernel: [  484.424754]  [<ffffffffbe490374>] ?
process_one_work+0x184/0x410
May 28 18:09:57 stack kernel: [  484.424758]  [<ffffffffbe49064d>] ?
worker_thread+0x4d/0x480
May 28 18:09:57 stack kernel: [  484.424763]  [<ffffffffbe490600>] ?
process_one_work+0x410/0x410
May 28 18:09:57 stack kernel: [  484.424770]  [<ffffffffbe4965c7>] ?
kthread+0xd7/0xf0
May 28 18:09:57 stack kernel: [  484.424777]  [<ffffffffbe4964f0>] ?
kthread_park+0x60/0x60
May 28 18:09:57 stack kernel: [  484.424785]  [<ffffffffbea043b5>] ?
ret_from_fork+0x25/0x30
May 28 18:10:14 stack dbus-daemon[1418]: Activating via systemd: service
name='org.gnome.Terminal' unit='gnome-terminal-server.service'
May 28 18:10:14 stack systemd[1237]: Starting GNOME Terminal Server...
May 28 18:10:14 stack dbus-daemon[1418]: Successfully activated service
'org.gnome.Terminal'
May 28 18:10:14 stack systemd[1237]: Started GNOME Terminal Server.
\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00M


   * What was the outcome of this action?
reboot and all was fine.

   * What outcome did you expect instead?
I expected the system to crash and not reboot, but it did reboot and recover.

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64
 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message ---
This bug was filed for a very old kernel. If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from buster.backports
please reopen the bug, see https://www.debian.org/Bugs/server-control

--- End Message ---

Reply to: