Bug 41632
Summary: | kernel oops after cannot create duplicate filename /class/bluetooth error | ||
---|---|---|---|
Product: | Drivers | Reporter: | rocko (rockorequin) |
Component: | Bluetooth | Assignee: | drivers_bluetooth (drivers_bluetooth) |
Status: | NEW --- | ||
Severity: | normal | CC: | alan, james, xerofoify |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.5 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
syslog from bluetooth crash
another bluetooth crash syslog |
Created attachment 71682 [details]
another bluetooth crash syslog
Bluetooth crashed this morning after I resumed my laptop. The syslog says first
that it could not create the duplicate filename '/class/bluetooth/hci0:36',
shortly after which there was a null pointer dereference.
Restarting bluetooth didn't fix the problem; I had to reboot.
I have a similar problem with kernel version 2.6.39.4. My kernel includes the tuxonice patch, but I think that tuxonice has nothing to do with the problem since the kernel crashed shortly after its first boot when the bluetooth mouse was being activated. I don't have a well-defined set of steps to reproduce the kernel oops. It occurs from time to time.
[7.] Environment
[7.1.] Software (add the output of the ver_linux script here)
$ ./ver_linux
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux aida 2.6.39-4-tuxonice #1 SMP PREEMPT Sun Sep 4 16:50:08 CEST 2011 x86_64 x86_64 x86_64 GNU/Linux
Gnu C 4.5.2
Gnu make 3.81
binutils 2.21.0.20110327
util-linux 2.17.2
mount support
module-init-tools 3.12
e2fsprogs 1.41.14
reiserfsprogs 3.6.21
pcmciautils 015
Linux C Library 2.13
Dynamic linker (ldd) 2.13
Procps 3.2.8
Net-tools 1.60
Kbd 1.15
Sh-utils 8.5
wireless-tools 30
Modules Loaded hidp binfmt_misc rfcomm bnep kvm_intel kvm fuse dm_crypt dm_mod btusb bluetooth snd_hda_codec_conexant snd_hda_intel thinkpad_acpi snd_hda_codec hwmon snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer arc4 ecb snd_seq_device uvcvideo iwlagn mac80211 snd psmouse cfg80211 snd_page_alloc serio_raw soundcore videodev ac battery wmi nvram v4l2_compat_ioctl32 rfkill evdev lzo lzf usbhid hid sg fbcon i915 tileblit font bitblit softcursor drm_kms_helper drm fb fbdev i2c_algo_bit cfbcopyarea intel_agp intel_gtt i2c_core e1000e ehci_hcd video button agpgart backlight cfbimgblt cfbfillrect uhci_hcd
[7.2.] Processor information (from /proc/cpuinfo):
model name : Intel(R) Core(TM)2 Duo CPU U9600 @ 1.60GHz
Any movement on this bug? This -- or something similar -- seems to still be around in kernel-3.3.5-2.fc17.x86_64 (see [1], includes links to dmesg logs). I can provoke a duplicate-sysfs-entry OOPS by *quickly* turning a bluetooth mouse off and back on again. [1] https://bugzilla.redhat.com/show_bug.cgi?id=820321 Currently not able to reproduce this any more with a kernel from 3.4.2 sources. It's back with kernel 3.5 with BT power status reporting enabled. This bug needs to be tested on newer kernels to see if it's applicable as a kernel bug. Nick |
Created attachment 69822 [details] syslog from bluetooth crash Bluetooth crashed this morning after I resumed my laptop. The syslog says first that it could not create the duplicate filename '/class/bluetooth/hci0:36', shortly after which there was a null pointer dereference. Restarting bluetooth didn't fix the problem; I had to reboot.