Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#907217: linux-image-4.17.0-3-amd64: crash on suspend/resume with network over bluetooth

6 views
Skip to first unread message

Philipp Marek

unread,
Aug 24, 2018, 4:00:02 PM8/24/18
to
Package: src:linux
Version: 4.17.17-1
Severity: normal

Over the last few kernel images (I believe since 4.14 or so, didn't test
with older kernels) doing suspend/resume with an active bluetooth network
connection can cause the kernel to do this:

ACPI: Low-level resume complete
sysfs group 'byte_queue_limits' not found for kobject 'tx-0'
...
BUG: unable to handle kernel paging request at ffffffffba385620
Call Trace:
_raw_spin_lock+0x1d/0x20
klist_next+0x1d/0xd0
? __rpm_get_callback+0x80/0x80
device_for_each_child+0x3e/0x90
pm_runtime_set_memalloc_noio+0x89/0xa0

which means that the network is dead - no new TCP connections (not even
local), no WIFI, no loading/unloading modules, etc.
Basically, you can (try to) close your open files, and reboot.

It doesn't happen every time; perhaps some packets need to be actively
transferred at that time?


-- Package-specific info:
** Version:
Linux version 4.17.0-3-amd64 (debian...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-28)) #1 SMP Debian 4.17.17-1 (2018-08-18)

** Command line:
BOOT_IMAGE=/vmlinuz-4.17.0-3-amd64 root=/dev/mapper/n555--vg-root ro initrd=/install/initrd.gz quiet

** Tainted: C (1024)
* Module from drivers/staging has been loaded.

-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT:de (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-4.17.0-3-amd64 depends on:
ii initramfs-tools [linux-initramfs-tool] 0.132
ii kmod 25-1
ii linux-base 4.5

Versions of packages linux-image-4.17.0-3-amd64 recommends:
ii apparmor 2.13-8
ii firmware-linux-free 3.4
ii irqbalance 1.3.0-0.1+b1

Versions of packages linux-image-4.17.0-3-amd64 suggests:
pn debian-kernel-handbook <none>
ii grub-pc 2.02+dfsg1-5
pn linux-doc-4.17 <none>

Versions of packages linux-image-4.17.0-3-amd64 is related to:
ii firmware-amd-graphics 20180518-1
ii firmware-atheros 20180518-1
ii firmware-bnx2 20180518-1
ii firmware-bnx2x 20180518-1
ii firmware-brcm80211 20180518-1
pn firmware-cavium <none>
pn firmware-intel-sound <none>
ii firmware-intelwimax 20180518-1
ii firmware-ipw2x00 20180518-1
ii firmware-ivtv 20180518-1
ii firmware-iwlwifi 20180518-1
ii firmware-libertas 20180518-1
ii firmware-linux-nonfree 20180518-1
ii firmware-misc-nonfree 20180518-1
ii firmware-myricom 20180518-1
ii firmware-netxen 20180518-1
ii firmware-qlogic 20180518-1
ii firmware-realtek 20180518-1
ii firmware-samsung 20180518-1
pn firmware-siano <none>
ii firmware-ti-connectivity 20180518-1
pn xen-hypervisor <none>

-- no debconf information

--
kern.log

Debian Bug Tracking System

unread,
Oct 22, 2021, 2:50:04 PM10/22/21
to
Your message dated Fri, 22 Oct 2021 11:45:52 -0700 (PDT)
with message-id <617306e0.1c69f...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #907217,
regarding linux-image-4.17.0-3-amd64: crash on suspend/resume with network over bluetooth
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 ow...@bugs.debian.org
immediately.)


--
907217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
kern.log
0 new messages