Mailinglist Archive: opensuse-bugs (13486 mails)

< Previous Next >
[Bug 332859] kbluetooth crashes after kernel-update 2.6.22.9
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 16 Oct 2007 08:15:10 -0600 (MDT)
  • Message-id: <20071016141510.509DB24526A@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=332859#c5





--- Comment #5 from Dieter Schroeder <dschr@xxxxxx> 2007-10-16 08:15:09 MST ---
Yes, that's my opinion, too. Normally the card won't be removed, but stays in
the slot all the time. I've removed it and got the following messages from the
kernel:
--snip--
Oct 16 16:01:02 nucleus kernel: pccard: PCMCIA card inserted into slot 1
Oct 16 16:01:02 nucleus kernel: cs: memory probe 0xe8000000-0xefffffff:
excluding 0xe8000000-0xefffffff
Oct 16 16:01:02 nucleus kernel: cs: memory probe 0xc0200000-0xcfffffff:
excluding 0xc0200000-0xc11fffff 0xc1a00000-0xc21fffff 0xc2a00000-0xc31fffff
0xc3a00000-0xcc1fffff 0xcca00000-0xcd1fffff 0xcda00000-0xce1fffff
0xcea00000-0xcf1fffff 0xcfa00000-0xd01fffff
Oct 16 16:01:02 nucleus kernel: pcmcia: registering new device pcmcia1.0
Oct 16 16:01:03 nucleus kernel: Bluetooth: Core ver 2.11
Oct 16 16:01:03 nucleus kernel: NET: Registered protocol family 31
Oct 16 16:01:03 nucleus kernel: Bluetooth: HCI device and connection manager
initialized
Oct 16 16:01:03 nucleus kernel: Bluetooth: HCI socket layer initialized
Oct 16 16:01:03 nucleus kernel: Bluetooth: Nokia control data = 0f 00
--snap--

Followed by the bluetooth stuff:
--snip--
Oct 16 16:01:06 nucleus hcid[18125]: Bluetooth HCI daemon
Oct 16 16:01:07 nucleus hcid[18125]: HCI dev 0 registered
Oct 16 16:01:07 nucleus hcid[18125]: Starting SDP server
Oct 16 16:01:07 nucleus opd[18133]: OBEX Push Daemon - version 0.2 started
Oct 16 16:01:07 nucleus opd[18133]: Failed to connect to SDP server.
Oct 16 16:01:07 nucleus kernel: Bluetooth: L2CAP ver 2.8
Oct 16 16:01:07 nucleus kernel: Bluetooth: L2CAP socket layer initialized
Oct 16 16:01:07 nucleus hcid[18125]: Created local server at
unix:abstract=/var/run/dbus-DMHjNi2Zfm,guid=4cf3a5273636ca29826e3b004714c423
Oct 16 16:01:07 nucleus input[18141]: Bluetooth Input daemon
Oct 16 16:01:07 nucleus input[18141]: Registered input manager
path:/org/bluez/input
Oct 16 16:01:07 nucleus hcid[18125]: HCI dev 0 up
Oct 16 16:01:07 nucleus hcid[18125]: Device hci0 has been added
Oct 16 16:01:07 nucleus hcid[18125]: Starting security manager 0
Oct 16 16:01:07 nucleus kernel: Bluetooth: RFCOMM socket layer initialized
Oct 16 16:01:07 nucleus kernel: Bluetooth: RFCOMM TTY layer initialized
Oct 16 16:01:07 nucleus kernel: Bluetooth: RFCOMM ver 1.8
Oct 16 16:01:07 nucleus hcid[18125]: Device hci0 has been activated
Oct 16 16:01:07 nucleus opd[18133]: OBEX server listening on channel 10
Oct 16 16:01:11 nucleus hcid[18125]: Default passkey agent (:1.92,
/org/kde/kbluetooth_1234) registered
Oct 16 16:01:11 nucleus hcid[18125]: Default authorization agent (:1.92,
/org/kde/kbluetooth_auth_1234) registered
--snap--

And kbluetooth started.
Maybe the card gets too hot in the laptop, so it won't get initialized properly
on reboot.
Normally the card is in its slot at boot time.


--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
References