[Lenovo ThinkPad T400] linux kernel panic on bluetooth DUN disconnect

Bug #1256811 reported by Georg Altmann
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux-lts-raring (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Steps to reproduce: Establish a bluetooth DUN connection using a mobile phone/tablet/etc., and then disconnect the DUN connection, and the kernel panics:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1256811/+attachment/3921449/+files/kmsg-crash-0.txt

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-32-generic 3.8.0-32.47~precise1
ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10
Uname: Linux 3.8.0-32-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-32-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: georg 1607 F.... xfce4-volumed
                      georg 1622 F.... pulseaudio
 /dev/snd/controlC29: georg 1607 F.... xfce4-volumed
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc620000 irq 50'
   Mixer name : 'Conexant CX20561 (Hermosa)'
   Components : 'HDA:14f15051,17aa211c,00100000 HDA:14f12c06,17aa2122,00100000'
   Controls : 31
   Simple ctrls : 14
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7VHT16WW-1.06'
   Mixer name : 'ThinkPad EC 7VHT16WW-1.06'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Mon Dec 2 09:25:07 2013
HibernationDevice: RESUME=UUID=d0854b61-5204-4213-98a1-28d75d8935cb
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.2)
MachineType: LENOVO 2768WJ2
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/zsh
ProcFB:
 0 radeondrmfb
 1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-32-generic root=/dev/mapper/ubuntu-root ro
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-32-generic N/A
 linux-backports-modules-3.8.0-32-generic N/A
 linux-firmware 1.79.7
SourcePackage: linux-lts-raring
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/15/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 7UET93WW (3.23 )
dmi.board.name: 2768WJ2
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7UET93WW(3.23):bd12/15/2011:svnLENOVO:pn2768WJ2:pvrThinkPadT400:rvnLENOVO:rn2768WJ2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2768WJ2
dmi.product.version: ThinkPad T400
dmi.sys.vendor: LENOVO

Revision history for this message
Georg Altmann (george-george-net) wrote :
Revision history for this message
Georg Altmann (george-george-net) wrote :

Struggling to get a kernel crash dump as described here:
https://help.ubuntu.com/12.04/serverguide/kernel-crash-dump.html

Configuration done as described, but
echo c > /proc/sysrq-trigger
only causes a crash without any dump being captured: system hangs with blinking capslock.

% dmesg |grep crash
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.8.0-32-generic root=/dev/mapper/ubuntu-root ro crashkernel=384M-2G:64M,2G-:128M
[ 0.000000] Reserving 128MB of memory at 720MB for crashkernel (System RAM: 3989MB)
[ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.8.0-32-generic root=/dev/mapper/ubuntu-root ro crashkernel=384M-2G:64M,2G-:128M

I did '/etc/init.d/kdump start' and sysrq is working as expected. /var/crash is empty. Any Hints?

Revision history for this message
Georg Altmann (george-george-net) wrote :

Root fs is mounted from LUKS encrypted device, see
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.8.0-32-generic root=/dev/mapper/ubuntu-root ro

Could this cause kdump to fail?

Revision history for this message
penalvch (penalvch) wrote :

Georg Altmann, you may find better success using the methods of crash logging noted in https://help.ubuntu.com/community/DebuggingSystemCrash .

summary: - linux kernel panic on bluetooth DUN disconnect
+ [Lenovo ThinkPad T400] linux kernel panic on bluetooth DUN disconnect
tags: added: bios-outdated-3.24 needs-crash-log needs-upstream-testing regression-potential
Changed in linux-lts-raring (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Georg Altmann (george-george-net) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Georg Altmann (george-george-net) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Georg Altmann (george-george-net) wrote : IwConfig.txt

apport information

Revision history for this message
Georg Altmann (george-george-net) wrote : Lspci.txt

apport information

Revision history for this message
Georg Altmann (george-george-net) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Georg Altmann (george-george-net) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Georg Altmann (george-george-net) wrote : ProcModules.txt

apport information

Revision history for this message
Georg Altmann (george-george-net) wrote : RfKill.txt

apport information

Revision history for this message
Georg Altmann (george-george-net) wrote : UdevDb.txt

apport information

Revision history for this message
Georg Altmann (george-george-net) wrote : UdevLog.txt

apport information

Revision history for this message
Georg Altmann (george-george-net) wrote :

OK, the above apport info doesn't seem to contain anything valueable.

Attached is "kmsg-crash-0.txt" which contains what I could sniff from /proc/kmsg using ssh.

I followed
https://help.ubuntu.com/community/DebuggingSystemCrash
and
https://wiki.ubuntu.com/Kernel/CrashdumpRecipe
but I can still not produce a crash dump. I also tried to adjust the crashkernel parameter without success:
% cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.8.0-32-generic root=/dev/mapper/ubuntu-root ro crashkernel=128M

Revision history for this message
Georg Altmann (george-george-net) wrote :

Removed [Lenovo ThinkPad T400] from subject since this is _not_ specific to the machine, see related bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433

summary: - [Lenovo ThinkPad T400] linux kernel panic on bluetooth DUN disconnect
+ linux kernel panic on bluetooth DUN disconnect
Revision history for this message
penalvch (penalvch) wrote : Re: linux kernel panic on bluetooth DUN disconnect

Georg Altmann, please do not mark this a duplicate of another bug or vice versa.

Revision history for this message
penalvch (penalvch) wrote :

Georg Altmann, please do not adjust the title as this helps to track hardware.

summary: - linux kernel panic on bluetooth DUN disconnect
+ [Lenovo ThinkPad T400] linux kernel panic on bluetooth DUN disconnect
description: updated
description: updated
Revision history for this message
penalvch (penalvch) wrote :

Georg Altmann, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Revision history for this message
eccerr0r (blc+launchpad) wrote :

This will be good to test a new upstream kernel.

I know that Kernel 3.12-release contains the proposed fix to BT DUN, however its interaction with blueman/networkmanager is broken. Anyone who has this bug on Ubuntu (or RH/Fedora), please report back, I am interested to hear any success with it. On my Gentoo system I can no longer reproduce the crash on my box but BT DUN no longer works properly with NetworkManager. I may have configured my kernel incorrectly - that's what I want to rule out...

Revision history for this message
penalvch (penalvch) wrote :

eccerr0r, please do not solicit others to post comments here as "Me too!" comments wouldn't be helpful at this point. If you are using Gentoo, it would be best to report a bug to their bug tracker -> https://bugs.gentoo.org . Despite this, so your hardware may be tracked, using Ubuntu, could you please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux-lts-raring (Ubuntu) because there has been no activity for 60 days.]

Changed in linux-lts-raring (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Jussi Saarinen (jussaar) wrote :

There are at least four similar bug reports (including this one) here in Launchpad on this problem:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189998

https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1256811

Anyway, if these are about the same bug that I think they are, the bug has now been completely fixed in kernel version 3.14, though kernel version 3.12 included some of the fix. Also there was one previous fix that is also needed that I think was backported to stable before 3.12. And there was also one fix applied between 3.12 and 3.14.

I think I manged to list all the necessary commits, Here are links to the commits, in case they need to be backported:

The first fix (pre 3.12?):
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1d9e689c934bd5ecb0f273c6c65e0655c5cfee5f

The fixes in 3.12:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=396dc223dd36edd218650d042a07c5e61f022c5b

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ebe937f74b8a72cf3ceeae5c2194a160bb092901

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=54b926a1434e817ca84cb090f36b56763e192470

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=cad348a17e170451ea8688b532a6ca3e98c63b60

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ece3150dea382c7c961fe2604332ed3474960d25

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ffe6b68cc5999a3f91a15b6667e69e14186e337d

One fix between 3.12 and 3.14:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=29cd718beba999bda4bdbbf59b5a4d25c07e1547

And finally the fixes in 3.14:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5b899241874dcc1a2b932a668731c80a3a869575

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e228b63390536f5b737056059a9a04ea016b1abf

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4a2fb3ecc7467c775b154813861f25a0ddc11aa0

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f86772af6a0f643d3e13eb3f4f9213ae0c333ee4

Revision history for this message
Jussi Saarinen (jussaar) wrote :

Just one correction to my previous post: It turns out that the following fix:

One fix between 3.12 and 3.14:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=29cd718beba999bda4bdbbf59b5a4d25c07e1547

was indeed included in 3.12.

To post a comment you must log in.