Arch Linux

alexdw

Member

Registered: 2013-03-25

Posts: 46

Bluetooth causes Kernel Panic

Hi all,

I've just recently moved to Arch Linux after using Fedora for several years because I felt Fedora was getting overly bloated with GNOMEShell and the like. So far my first impressions have been good - more or less everything has worked easily enough and xfce4 does the job in being a fully functional but not too resource-heavy desktop environment.

The only thing I'm having trouble with is Bluetooth (which is via a USB device/dongle as my laptop doesn't have it built-in). I've read the Wiki article and start the Bluetooth service using systemctl, and I'm using blueman as the user interface. It can successfully search for devices, and appears to pair OK (it asks for and accepts the PIN for pairing my Bluetooth headset). However, almost immediately after connecting, and certainly if I try to activate one of the services it either freezes the interface (the cursor can be moved but nothing responds to keyboard or mouse activity) or causes a kernel panic (see photos below).

I'm not sure if the above is very helpful but I don't know how to get the log from a previous session (if I use dmesg once I've rebooted it only seems to have the current session's log).

Thanks in advance for any suggestions, and also on how to provide more useful information to diagnose this.

drhill1

Member

Registered: 2013-03-27

Posts: 31

Re: Bluetooth causes Kernel Panic

Hi,
I've been having similar problems with a cheap Bluetooth adapter that I've just tried installing.  lsusb gives an ID of 0a12:0001 for this dongle and there must be known problems with it as the btusb module has an option to ignore devices with this ID, as seen via modinfo.  One suggestion that I found involved adding "reset=1" to the options for this module, but this still causes panics for me, you may have more luck though.  As my adapter was only £1.19 from eBay, I'll just be buying a different model for under £2 and hope to get more luck with that one.

In response to your query about getting logs from your previous sessions, try running "journalctl" as root.  This'll take you to the start of the logs and you'll be able to page down or search as it uses "less" as a pager.

Hopefully, this'll at least provide some helpful suggestions as my first post on the Arch forums.

alexdw

Member

Registered: 2013-03-25

Posts: 46

Re: Bluetooth causes Kernel Panic

Hi,
I've been having similar problems with a cheap Bluetooth adapter that I've just tried installing.  lsusb gives an ID of 0a12:0001 for this dongle and there must be known problems with it as the btusb module has an option to ignore devices with this ID, as seen via modinfo.  One suggestion that I found involved adding "reset=1" to the options for this module, but this still causes panics for me, you may have more luck though.  As my adapter was only £1.19 from eBay, I'll just be buying a different model for under £2 and hope to get more luck with that one.

In response to your query about getting logs from your previous sessions, try running "journalctl" as root.  This'll take you to the start of the logs and you'll be able to page down or search as it uses "less" as a pager.

Hopefully, this'll at least provide some helpful suggestions as my first post on the Arch forums.

Thanks for the response. It looks like I've got the same cheap Bluetooth adapter:

Bus 005 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

I'll have a look at adding that option and also getting the full logs using journalctl. Useful to learn about that - thanks again.

alexdw

Member

Registered: 2013-03-25

Posts: 46

Re: Bluetooth causes Kernel Panic

Log of error using journalctl:

Mar 28 17:40:00 AlexPC sudo[15818]: alexdw : TTY=pts/1 ; PWD=/home/alexdw/Temp ; USER=root ; COMMAND=/usr/bin/systemctl start bluetooth
Mar 28 17:40:00 AlexPC sudo[15818]: pam_unix(sudo:session): session opened for user root by alexdw(uid=0)
Mar 28 17:40:00 AlexPC systemd[1]: Starting Bluetooth service...
Mar 28 17:40:00 AlexPC bluetoothd[15821]: bluetoothd[15821]: Bluetooth daemon 4.101
Mar 28 17:40:00 AlexPC bluetoothd[15821]: Bluetooth daemon 4.101
Mar 28 17:40:00 AlexPC systemd[1]: Started Bluetooth service.
Mar 28 17:40:00 AlexPC bluetoothd[15821]: bluetoothd[15821]: Starting SDP server
Mar 28 17:40:00 AlexPC bluetoothd[15821]: Starting SDP server
Mar 28 17:40:00 AlexPC sudo[15818]: pam_unix(sudo:session): session closed for user root
Mar 28 17:40:00 AlexPC kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Mar 28 17:40:00 AlexPC kernel: Bluetooth: BNEP socket layer initialized
Mar 28 17:40:00 AlexPC bluetoothd[15821]: bluetoothd[15821]: Bluetooth Management interface initialized
Mar 28 17:40:00 AlexPC bluetoothd[15821]: Bluetooth Management interface initialized
Mar 28 17:40:00 AlexPC kernel: Bluetooth: RFCOMM TTY layer initialized
Mar 28 17:40:00 AlexPC kernel: Bluetooth: RFCOMM socket layer initialized
Mar 28 17:40:00 AlexPC kernel: Bluetooth: RFCOMM ver 1.11
Mar 28 17:40:01 AlexPC bluetoothd[15821]: bluetoothd[15821]: Adapter /org/bluez/15821/hci0 has been enabled
Mar 28 17:40:01 AlexPC bluetoothd[15821]: Adapter /org/bluez/15821/hci0 has been enabled
Mar 28 17:40:10 AlexPC dbus-daemon[432]: dbus[432]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper)
Mar 28 17:40:10 AlexPC dbus[432]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper)
Mar 28 17:40:10 AlexPC dbus-daemon[432]: /usr/lib/python2.7/site-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
Mar 28 17:40:10 AlexPC dbus-daemon[432]: warnings.warn(str(e), _gtk.Warning)
Mar 28 17:40:10 AlexPC blueman-mechanism[16130]: Starting blueman-mechanism
Mar 28 17:40:10 AlexPC dbus-daemon[432]: dbus[432]: [system] Successfully activated service 'org.blueman.Mechanism'
Mar 28 17:40:10 AlexPC dbus[432]: [system] Successfully activated service 'org.blueman.Mechanism'
Mar 28 17:40:10 AlexPC blueman-mechanism[16130]: loading Config
Mar 28 17:40:10 AlexPC blueman-mechanism[16130]: loading RfKill
Mar 28 17:40:10 AlexPC blueman-mechanism[16130]: loading Network
Mar 28 17:40:10 AlexPC blueman-mechanism[16130]: loading Ppp
Mar 28 17:40:25 AlexPC bluetoothd[15821]: bluetoothd[15821]: Discovery session 0x7f2548702100 with :1.21 activated
Mar 28 17:40:25 AlexPC bluetoothd[15821]: Discovery session 0x7f2548702100 with :1.21 activated
Mar 28 17:40:35 AlexPC bluetoothd[15821]: bluetoothd[15821]: Stopping discovery
Mar 28 17:40:35 AlexPC bluetoothd[15821]: Stopping discovery
Mar 28 17:40:40 AlexPC blueman-mechanism[16130]: Exiting
Mar 28 17:40:40 AlexPC dbus-daemon[432]: Starting blueman-mechanism
Mar 28 17:40:40 AlexPC dbus-daemon[432]: loading Config
Mar 28 17:40:40 AlexPC dbus-daemon[432]: loading RfKill
Mar 28 17:40:40 AlexPC dbus-daemon[432]: loading Network
Mar 28 17:40:40 AlexPC dbus-daemon[432]: loading Ppp
Mar 28 17:40:40 AlexPC dbus-daemon[432]: Exiting
Mar 28 17:40:53 AlexPC dbus-daemon[432]: dbus[432]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.19" (uid=1000 pid=16089 comm="/usr/bin/python2 /usr/bin/blueman-applet ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.18" (uid=0 pid=15821 comm="/usr/sbin/bluetoothd -n ")
Mar 28 17:40:53 AlexPC dbus[432]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.19" (uid=1000 pid=16089 comm="/usr/bin/python2 /usr/bin/blueman-applet ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.18" (uid=0 pid=15821 comm="/usr/sbin/bluetoothd -n ")
Mar 28 17:41:17 AlexPC bluetoothd[15821]: bluetoothd[15821]: Unable to select SEP
Mar 28 17:41:17 AlexPC bluetoothd[15821]: Unable to select SEP
Mar 28 17:41:17 AlexPC kernel: input: 00:18:91:51:EB:24 as /devices/virtual/input/input14
Mar 28 17:41:28 AlexPC kernel: general protection fault: 0000 [#1] PREEMPT SMP 
Mar 28 17:41:28 AlexPC kernel: Modules linked in: uinput rfcomm bnep fuse snd_hda_codec_idt snd_hda_codec_hdmi arc4 iTCO_wdt iTCO_vendor_support gpio_i
Mar 28 17:41:28 AlexPC kernel:  pata_acpi ahci ata_piix libahci sdhci_pci sdhci mmc_core libata ehci_pci uhci_hcd ehci_hcd firewire_ohci scsi_mod firewire_core crc_itu_t usbcore usb_common
Mar 28 17:41:28 AlexPC kernel: CPU 1 
Mar 28 17:41:28 AlexPC kernel: Pid: 499, comm: X Tainted: G           O 3.8.4-1-ARCH #1 Dell Inc. Inspiron 1525                   /0U990C
Mar 28 17:41:28 AlexPC kernel: RIP: 0010:[<ffffffff81174cdf>]  [<ffffffff81174cdf>] __kmalloc+0x6f/0x220
Mar 28 17:41:28 AlexPC kernel: RSP: 0018:ffff88011048dcf8  EFLAGS: 00010206
Mar 28 17:41:28 AlexPC kernel: RAX: 0000000000000000 RBX: ffff880113d1b000 RCX: 000000000007a081
Mar 28 17:41:28 AlexPC kernel: RDX: 000000000007a041 RSI: 0000000000000000 RDI: 0000000000000427
Mar 28 17:41:28 AlexPC kernel: RBP: ffff88011048dd38 R08: 0000000000016dc0 R09: ffffffffa05dde38
Mar 28 17:41:28 AlexPC kernel: R10: 0000000000864bf0 R11: 0000000000003246 R12: 00000000000012d0
Mar 28 17:41:28 AlexPC kernel: R13: 00013c000018dc00 R14: ffff88011b001c00 R15: ffff88011b001c00
Mar 28 17:41:28 AlexPC kernel: FS:  00007feef3eb3880(0000) GS:ffff88011fd00000(0000) knlGS:0000000000000000
Mar 28 17:41:28 AlexPC kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 28 17:41:28 AlexPC kernel: CR2: 00007f4d015bb760 CR3: 0000000110447000 CR4: 00000000000007e0
Mar 28 17:41:28 AlexPC kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Mar 28 17:41:28 AlexPC kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Mar 28 17:41:28 AlexPC kernel: Process X (pid: 499, threadinfo ffff88011048c000, task ffff880113c6a9e0)
Mar 28 17:41:28 AlexPC kernel: Stack:
Mar 28 17:41:28 AlexPC kernel:  ffff880118937200 0000000000000428 ffff880118ecc000 ffff880113d1b000
Mar 28 17:41:28 AlexPC kernel:  ffff88011048dde0 ffff880113d1b000 ffff880118a63c00 fffffffffffffff2
Mar 28 17:41:28 AlexPC kernel:  ffff88011048dd78 ffffffffa05dde38 ffff880118a63c00 ffff880113d1b000
Mar 28 17:41:28 AlexPC kernel: Call Trace:
Mar 28 17:41:28 AlexPC kernel:  [<ffffffffa05dde38>] i915_gem_execbuffer2+0x58/0x280 [i915]
Mar 28 17:41:28 AlexPC kernel:  [<ffffffffa04943f3>] drm_ioctl+0x4c3/0x570 [drm]
Mar 28 17:41:28 AlexPC kernel:  [<ffffffffa05ddde0>] ? i915_gem_execbuffer+0x480/0x480 [i915]
Mar 28 17:41:28 AlexPC kernel:  [<ffffffff81014829>] ? __switch_to+0x3d9/0x4e0
Mar 28 17:41:28 AlexPC kernel:  [<ffffffff814d1745>] ? __schedule+0x435/0x920
Mar 28 17:41:28 AlexPC kernel:  [<ffffffff8119eb17>] do_vfs_ioctl+0x97/0x530
Mar 28 17:41:28 AlexPC kernel:  [<ffffffff8118e42e>] ? ____fput+0xe/0x10
Mar 28 17:41:28 AlexPC kernel:  [<ffffffff8119f041>] sys_ioctl+0x91/0xb0
Mar 28 17:41:28 AlexPC kernel:  [<ffffffff814da81d>] system_call_fastpath+0x1a/0x1f
Mar 28 17:41:28 AlexPC kernel: Code: 90 4d 89 f7 49 8b 07 65 48 03 04 25 c8 db 00 00 48 8b 50 08 4c 8b 28 4d 85 ed 0f 84 41 01 00 00 49 63 47 20 4d 8b 07 48 8d 4a 40 <49> 8b 5c 05 00 4c 89 e8 65 49 0f c7 08 0f 94 c0 84 c0 74 c5 49 
Mar 28 17:41:28 AlexPC kernel: RIP  [<ffffffff81174cdf>] __kmalloc+0x6f/0x220
Mar 28 17:41:28 AlexPC kernel:  RSP <ffff88011048dcf8>
Mar 28 17:41:28 AlexPC kernel: ---[ end trace 0655369d3b538885 ]---
Mar 28 17:41:28 AlexPC kernel: [drm:drm_release] *ERROR* Device busy: 1
Mar 28 17:41:28 AlexPC lxdm-binary[437]: pam_unix(lxdm:session): session closed for user alexdw
Mar 28 17:41:28 AlexPC polkitd[736]: Unregistered Authentication Agent for unix-session:1 (system bus name :1.16, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_GB.utf8) (disconnected from bus)
Mar 28 17:41:28 AlexPC kernel: general protection fault: 0000 [#2] PREEMPT SMP 
Mar 28 17:41:28 AlexPC kernel: Modules linked in: uinput rfcomm bnep fuse snd_hda_codec_idt snd_hda_codec_hdmi arc4 iTCO_wdt iTCO_vendor_support gpio_i
Mar 28 17:41:28 AlexPC kernel:  pata_acpi ahci ata_piix libahci sdhci_pci sdhci mmc_core libata ehci_pci uhci_hcd ehci_hcd firewire_ohci scsi_mod firewire_core crc_itu_t usbcore usb_common
Mar 28 17:41:28 AlexPC kernel: CPU 1 
Mar 28 17:41:28 AlexPC kernel: Pid: 18630, comm: X Tainted: G      D    O 3.8.4-1-ARCH #1 Dell Inc. Inspiron 1525                   /0U990C
Mar 28 17:41:28 AlexPC kernel: RIP: 0010:[<ffffffff8117505b>]  [<ffffffff8117505b>] kmem_cache_alloc_node_trace+0x1cb/0x230
Mar 28 17:41:28 AlexPC kernel: RSP: 0018:ffff880119249e28  EFLAGS: 00010246
Mar 28 17:41:28 AlexPC kernel: RAX: 0000000000000000 RBX: 0000000000000001 RCX: 000000000007a101
Mar 28 17:41:28 AlexPC kernel: RDX: 000000000007a0c1 RSI: 00000000000080d0 RDI: ffff88011b001c00
Mar 28 17:41:28 AlexPC kernel: RBP: ffff880119249e88 R08: 0000000000016dc0 R09: ffff88011b001c00
Mar 28 17:41:28 AlexPC kernel: R10: ffff88011b001c00 R11: ffffffff8109b11f R12: 00013c000018dc00
Mar 28 17:41:28 AlexPC kernel: R13: 0000000000000000 R14: 00000000000080d0 R15: 00000000000006d0
Mar 28 17:41:28 AlexPC kernel: FS:  00007fc3d752e880(0000) GS:ffff88011fd00000(0000) knlGS:0000000000000000
Mar 28 17:41:28 AlexPC kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 28 17:41:28 AlexPC kernel: CR2: 00007fc3d4273d90 CR3: 0000000110530000 CR4: 00000000000007e0
Mar 28 17:41:28 AlexPC kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Mar 28 17:41:28 AlexPC kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Mar 28 17:41:28 AlexPC kernel: Process X (pid: 18630, threadinfo ffff880119248000, task ffff8800379ca180)
Mar 28 17:41:28 AlexPC kernel: Stack:
Mar 28 17:41:28 AlexPC kernel:  ffff880119249e98 ffffffff81175099 ffff880119249e88 ffff88011b001700
Mar 28 17:41:28 AlexPC kernel:  ffff8800d8f85080 ffffffff8109b15c ffff8800d8f85000 0000000000000001
Mar 28 17:41:28 AlexPC kernel:  0000000000000001 ffff8800d8f85000 ffff880117cc2000 ffffffff81a4d560
Mar 28 17:41:28 AlexPC kernel: Call Trace:
Mar 28 17:41:28 AlexPC kernel:  [<ffffffff81175099>] ? kmem_cache_alloc_node_trace+0x209/0x230
Mar 28 17:41:28 AlexPC kernel:  [<ffffffff8109b15c>] ? alloc_rt_sched_group+0xec/0x1d0
Mar 28 17:41:28 AlexPC kernel:  [<ffffffff8109b11f>] alloc_rt_sched_group+0xaf/0x1d0
Mar 28 17:41:28 AlexPC kernel:  [<ffffffff8108f38b>] sched_create_group+0x7b/0x190
Mar 28 17:41:28 AlexPC kernel:  [<ffffffff8109ba8c>] sched_autogroup_create_attach+0x4c/0x180
Mar 28 17:41:28 AlexPC kernel:  [<ffffffff81070344>] sys_setsid+0xd4/0xf0
Mar 28 17:41:28 AlexPC kernel:  [<ffffffff814da81d>] system_call_fastpath+0x1a/0x1f
Mar 28 17:41:28 AlexPC kernel: Code: 48 8b 80 38 e0 ff ff a8 08 0f 84 fa fe ff ff e8 7c cc 35 00 e9 f0 fe ff ff 0f 1f 80 00 00 00 00 49 63 41 20 4d 8b 01 48 8d 4a 40 <49> 8b 1c 04 4c 89 e0 65 49 0f c7 08 0f 94 c0 84 c0 0f 84 4c fe 
Mar 28 17:41:28 AlexPC kernel: RIP  [<ffffffff8117505b>] kmem_cache_alloc_node_trace+0x1cb/0x230
Mar 28 17:41:28 AlexPC kernel:  RSP <ffff880119249e28>
Mar 28 17:41:28 AlexPC kernel: ---[ end trace 0655369d3b538886 ]---

It starts with activating Bluetooth using "sudo systemctl start bluetooth", goes through a 'successful' pairing, fails to connect to a Bluetooth 'service' (e.g. "Audio Sink", "Headset") for the device then crashes out (looks like this happens at Mar 28 17:41:28).

Sometimes it will crash even before trying to connect to a Bluetooth service.

alexdw

Member

Registered: 2013-03-25

Posts: 46

Re: Bluetooth causes Kernel Panic

Hi,
I've been having similar problems with a cheap Bluetooth adapter that I've just tried installing.  lsusb gives an ID of 0a12:0001 for this dongle and there must be known problems with it as the btusb module has an option to ignore devices with this ID, as seen via modinfo.  One suggestion that I found involved adding "reset=1" to the options for this module, but this still causes panics for me, you may have more luck though.  As my adapter was only £1.19 from eBay, I'll just be buying a different model for under £2 and hope to get more luck with that one.

In response to your query about getting logs from your previous sessions, try running "journalctl" as root.  This'll take you to the start of the logs and you'll be able to page down or search as it uses "less" as a pager.

Hopefully, this'll at least provide some helpful suggestions as my first post on the Arch forums.

I finally got round to trying the "reset=1" option, but it had no effect for me either.

Have you had better luck with your new Bluetooth adapter?