Arch Linux

ntony

Member

Registered: 2010-11-17

Posts: 32

[Solved] Kernel Stack Trace during shutdown if bluetoothd is start

Kernel stack trace shows up on my screen when I try to shutdown with bluetoothd started. If I don't have bluetoothd started, my machine shutdowns regularly.

This is the stack trace copied from /var/log/message.log

Apr 25 17:46:12 localhost shutdown[6798]: shutting down for system reboot
Apr 25 17:46:12 localhost init: Switching to runlevel: 6
Apr 25 17:46:13 localhost acpid: client 1301[0:0] has disconnected
Apr 25 17:46:13 localhost acpid: client connected from 6824[0:0]
Apr 25 17:46:13 localhost acpid: 1 client rule loaded
Apr 25 17:46:13 localhost bluetoothd[3416]: Terminating
Apr 25 17:46:13 localhost laptop-mode: Laptop mode 
Apr 25 17:46:13 localhost laptop-mode: disabled, not active
Apr 25 17:46:13 localhost kernel: [ 3144.642159] PGD 0 
Apr 25 17:46:13 localhost kernel: [ 3144.642169] Oops: 0010 [#1] PREEMPT SMP 
Apr 25 17:46:13 localhost kernel: [ 3144.642190] CPU 3 
Apr 25 17:46:13 localhost kernel: [ 3144.642199] Modules linked in: hidp hid rfcomm bnep ppp_deflate zlib_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc option usb_wwan usbserial usb_storage uas joydev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev v4l2_compat_ioctl32 media snd_hda_codec_hdmi snd_hda_codec_conexant btusb bluetooth i915 arc4 serio_raw psmouse evdev thinkpad_acpi iTCO_wdt i2c_i801 iTCO_vendor_support nvram ac battery snd_hda_intel snd_hda_codec iwlwifi sdhci_pci i2c_algo_bit sdhci snd_hwdep drm_kms_helper snd_pcm mmc_core tpm_tis tpm mac80211 tpm_bios snd_page_alloc snd_timer drm intel_agp cfg80211 snd wmi soundcore rfkill mei(C) i2c_core video intel_gtt thermal button e1000e vboxdrv(O) tp_smapi(O) thinkpad_ec(O) fuse acpi_cpufreq mperf processor ext4 crc16 jbd2 mbcache xhci_hcd ehci_hcd usbcore usb_common sd_mod ahci libahci libata scsi_mod
Apr 25 17:46:13 localhost kernel: [ 3144.642596] 
Apr 25 17:46:13 localhost kernel: [ 3144.642605] Pid: 3416, comm: bluetoothd Tainted: G         C O 3.3.3-1-ARCH #1 LENOVO 4290NL5/4290NL5
Apr 25 17:46:13 localhost kernel: [ 3144.642644] RIP: 0010:[<0000000068736162>]  [<0000000068736162>] 0x68736161
Apr 25 17:46:13 localhost kernel: [ 3144.642674] RSP: 0018:ffff8801d75bbd70  EFLAGS: 00010202
Apr 25 17:46:13 localhost kernel: [ 3144.642694] RAX: 0000000068736162 RBX: ffff8801f0482000 RCX: 0000000180100008
Apr 25 17:46:13 localhost kernel: [ 3144.642721] RDX: 0000000180100009 RSI: 0000000000000016 RDI: ffff8801f0482000
Apr 25 17:46:13 localhost kernel: [ 3144.642748] RBP: ffff8801d75bbd98 R08: 0000000080100008 R09: ffff8801d75bbfd8
Apr 25 17:46:13 localhost kernel: [ 3144.642774] R10: 0000000000000000 R11: ffffffffa064d54c R12: ffff88021016e658
Apr 25 17:46:13 localhost kernel: [ 3144.642801] R13: ffff88021016e5e0 R14: 0000000000000000 R15: 0000000000000000
Apr 25 17:46:13 localhost kernel: [ 3144.642830] FS:  00007ffca97cc700(0000) GS:ffff88021e2c0000(0000) knlGS:0000000000000000
Apr 25 17:46:13 localhost kernel: [ 3144.642860] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 25 17:46:13 localhost kernel: [ 3144.642882] CR2: 0000000068736162 CR3: 00000001d75b0000 CR4: 00000000000406e0
Apr 25 17:46:13 localhost kernel: [ 3144.642908] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 25 17:46:13 localhost kernel: [ 3144.642934] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Apr 25 17:46:13 localhost kernel: [ 3144.642961] Process bluetoothd (pid: 3416, threadinfo ffff8801d75ba000, task ffff8801f0483800)
Apr 25 17:46:13 localhost kernel: [ 3144.642993] Stack:
Apr 25 17:46:13 localhost kernel: [ 3144.643001]  ffffffffa06331c5 ffff8801d75bbd98 ffff8801f0482000 ffff88021016e000
Apr 25 17:46:13 localhost kernel: [ 3144.643036]  ffff88021016e010 ffff8801d75bbdc8 ffffffffa062ec41 ffff88021016e000
Apr 25 17:46:13 localhost kernel: [ 3144.643069]  0000000000000000 ffff880206c02c00 0000000000000000 ffff8801d75bbde8
Apr 25 17:46:13 localhost kernel: [ 3144.643104] Call Trace:
Apr 25 17:46:13 localhost kernel: [ 3144.643120]  [<ffffffffa06331c5>] ? hci_conn_hash_flush+0x65/0xc0 [bluetooth]
Apr 25 17:46:13 localhost kernel: [ 3144.643150]  [<ffffffffa062ec41>] hci_dev_do_close+0xa1/0x2c0 [bluetooth]
Apr 25 17:46:13 localhost kernel: [ 3144.643179]  [<ffffffffa062febd>] hci_dev_close+0x2d/0x70 [bluetooth]
Apr 25 17:46:13 localhost kernel: [ 3144.643207]  [<ffffffffa063e493>] hci_sock_ioctl+0x193/0x380 [bluetooth]
Apr 25 17:46:13 localhost kernel: [ 3144.643237]  [<ffffffff8115733d>] ? kmem_cache_free+0x10d/0x120
Apr 25 17:46:13 localhost kernel: [ 3144.643265]  [<ffffffff8134b850>] sock_do_ioctl+0x30/0x70
Apr 25 17:46:13 localhost kernel: [ 3144.643290]  [<ffffffff8134bb26>] sock_ioctl+0x76/0x2a0
Apr 25 17:46:13 localhost kernel: [ 3144.643312]  [<ffffffff8117e787>] do_vfs_ioctl+0x97/0x530
Apr 25 17:46:13 localhost kernel: [ 3144.643334]  [<ffffffff8118ae14>] ? mntput+0x24/0x40
Apr 25 17:46:13 localhost kernel: [ 3144.643355]  [<ffffffff8116dfeb>] ? fput+0x16b/0x210
Apr 25 17:46:13 localhost kernel: [ 3144.643376]  [<ffffffff811b7729>] ? locks_remove_posix+0x19/0x30
Apr 25 17:46:13 localhost kernel: [ 3144.643399]  [<ffffffff8117ecb9>] sys_ioctl+0x99/0xa0
Apr 25 17:46:13 localhost kernel: [ 3144.643421]  [<ffffffff8145ff29>] system_call_fastpath+0x16/0x1b
Apr 25 17:46:13 localhost kernel: [ 3144.643446] Code:  Bad RIP value.
Apr 25 17:46:13 localhost kernel: [ 3144.644492]  RSP <ffff8801d75bbd70>
Apr 25 17:46:13 localhost kernel: [ 3144.645512] CR2: 0000000068736162
Apr 25 17:46:13 localhost kernel: [ 3145.050400] ---[ end trace d95f1a6e42d9179e ]---
Apr 25 17:46:13 localhost acpid: exiting

Sorry, I don't know how to read this stack trace. What problem is the bluetoothd causing?

Last edited by ntony (2012-04-26 19:31:54)

pigiron

Member

From: USA

Registered: 2009-07-14

Posts: 150

Re: [Solved] Kernel Stack Trace during shutdown if bluetoothd is start

What problem is the bluetoothd causing?

Possibly none. Since the entire kernel, along with all the drivers, run in the same address space it's all too easy for one kernel component to "step on" another.

That's why I drilled in on these lines from your log:

Apr 25 17:46:13 localhost kernel: [ 3144.642199] Modules linked in: (Snipped...) mei(C) (Snipped...) vboxdrv(O) tp_smapi(O) thinkpad_ec(O) (Snipped...)
Apr 25 17:46:13 localhost kernel: [ 3144.642596]
Apr 25 17:46:13 localhost kernel: [ 3144.642605] Pid: 3416, comm: bluetoothd Tainted: G         C O 3.3.3-1-ARCH (Snipped...)

Starting with the bottom line, the Tainted: means that you're running a "non-clean" kernel, while the G says that the taint comes from GPL licensed module(s).

The top line shows the tainted modules:

mei(C): the "(C)" means that the mei driver is from the staging tree, and you should have noticed the following in your logs:

"mei: module is from the staging directory, the quality is unknown, you have been warned."

The other drivers with the "(O)" mean that they are "out of tree" drivers (drivers that are not maintained by the Linux kernel developers).

Some poking around shows that the tp_smapi and thinkpad_ec drivers are probably from the AUR.

So... the first question is... did you recompile the "out of tree" drivers after updating your kernel?

The next question is, does this problem occur without those tainted modules ever being loaded (loading and then unloading the tainted driver(s) will not remove the "taint" flag... for a very good reason)?

anespo

Member

From: Europe

Registered: 2007-07-17

Posts: 39

Re: [Solved] Kernel Stack Trace during shutdown if bluetoothd is start

I have a similar problem.
Propably https://bugzilla.kernel.org/show_bug.cgi?id=43070

ntony

Member

Registered: 2010-11-17

Posts: 32

Re: [Solved] Kernel Stack Trace during shutdown if bluetoothd is start

Thanks pigiron!

Yes, I have tp_smapi compiled from AUR. That should be out of tree module compiled after kernel update. And I have VirtualBox installed but I don't think it causes this problem.

I have blacklisted tp_smapi and the problem has been suppressed. I'm looking forward on update for TP SMAPI. Thank you very much!