From: Pierre-Yves Paulus <py@idlum.be>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Kernel Oops while transmitting data on several RFCOMMlinks
Date: Fri, 14 Sep 2007 19:04:47 +0200 [thread overview]
Message-ID: <46EABF2F.6040302@idlum.be> (raw)
In-Reply-To: <1185460255.7111.140.camel@violet>
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
Hi Marcel,
> that is not the latest upstream kernel. Try 2.6.23-rc1.
I got a kernel panic running 2.6.23-rc6 a few minutes ago.
2 files attached:
-relevant part of /var/log/messages
-screenshot after the kernel panic
Don't know if I can supply more information about that case? Just ask.
Best Regards,
Pierre-Yves
[-- Attachment #2: panic.jpg --]
[-- Type: image/jpeg, Size: 52084 bytes --]
[-- Attachment #3: kernel_crash --]
[-- Type: text/plain, Size: 2492 bytes --]
Sep 14 16:41:38 p2a kernel: [<c0223b48>] device_move+0x13/0xe2
Sep 14 16:41:38 p2a kernel: [<c01c537b>] kref_get+0x34/0x3d
Sep 14 16:41:38 p2a kernel: [<c01c484b>] kobject_get+0xf/0x13
Sep 14 16:41:38 p2a kernel: [<c0223b2f>] get_device+0xe/0x14
Sep 14 16:41:38 p2a kernel: [<c0223b48>] device_move+0x13/0xe2
Sep 14 16:41:38 p2a kernel: [<d02f3b78>] rfcomm_tty_close+0x23/0x61 [rfcomm]
Sep 14 16:41:38 p2a kernel: [<c020e0a4>] release_dev+0x1c0/0x54a
Sep 14 16:41:38 p2a kernel: [<d02f30c9>] rfcomm_dev_destruct+0x59/0x65 [rfcomm]
Sep 14 16:41:38 p2a kernel: [<d02f370c>] rfcomm_dev_ioctl+0x328/0x4e6 [rfcomm]
Sep 14 16:41:38 p2a kernel: [<c012a3a8>] autoremove_wake_function+0x0/0x35
Sep 14 16:41:38 p2a kernel: [<c02460bc>] release_sock+0xc/0x74
Sep 14 16:41:38 p2a kernel: [<c0243f4e>] sock_ioctl+0x19f/0x1be
Sep 14 16:41:38 p2a kernel: [<c020e435>] tty_release+0x7/0xa
Sep 14 16:41:38 p2a kernel: [<c015be91>] __fput+0x93/0x147
Sep 14 16:41:38 p2a kernel: [<c0159a39>] filp_close+0x51/0x58
Sep 14 16:41:38 p2a kernel: [<c015aad1>] sys_close+0x54/0x83
Sep 14 16:41:38 p2a kernel: [<c0103c72>] syscall_call+0x7/0xb
Sep 14 16:41:38 p2a kernel: =======================
Sep 14 16:42:25 p2a kernel: hcidump[3103]: segfault at 0809db3a eip 0805f3c7 esp bfb4fae0 error 4
Sep 14 16:43:42 p2a kernel: [<c01c537b>] kref_get+0x34/0x3d
Sep 14 16:43:42 p2a t()
Sep 14 16:43:42 p2a kernel: [<c01c537b>] kref_get+0x34/0x3d
Sep 14 16:43:42 p2a kernel: [<c01c484b>] kobject_get+0xf/0x13
Sep 14 16:43:42 p2a kernel: [<c0223b2f>] get_device+0xe/0x14
Sep 14 16:43:42 p2a kernel: [<c0223b48>] device_move+0x13/0xe2
Sep 14 16:43:42 p2a kernel: [<d02f3b78>] rfcomm_tty_close+0x23/0x61 [rfcomm]
Sep 14 16:43:42 p2a kernel: [<c020e0a4>] release_dev+0x1c0/0x54a
Sep 14 16:43:42 p2a kernel: [<d02f30c9>] rfcomm_dev_destruct+0x59/0x65 [rfcomm]
Sep 14 16:43:42 p2a kernel: [<d02f370c>] rfcomm_dev_ioctl+0x328/0x4e6 [rfcomm]
Sep 14 16:43:42 p2a kernel: [<c012a3a8>] autoremove_wake_function+0x0/0x35
Sep 14 16:43:42 p2a kernel: [<c02460bc>] release_sock+0xc/0x74
Sep 14 16:43:42 p2a kernel: [<c0243f4e>] sock_ioctl+0x19f/0x1be
Sep 14 16:43:42 p2a kernel: [<c020e435>] tty_release+0x7/0xa
Sep 14 16:43:42 p2a kernel: [<c015be91>] __fput+0x93/0x147
Sep 14 16:43:42 p2a kernel: [<c015aad1>] sys_close+0x54/0x83
Sep 14 16:43:42 p2a kernel: [<c015aad1>] sys_close+0x54/0x83
Sep 14 16:43:42 p2a kernel: [<c0103c72>] syscall_call+0x7/0xb
Sep 14 16:43:42 p2a kernel: =======================
[-- Attachment #4: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- Attachment #5: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-09-14 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070709093602.A2C6B58D565@mailflip16.edt02.net>
2007-07-10 10:15 ` [Bluez-devel] Kernel Oops while transmitting data on several RFCOMM links Pierre-Yves Paulus
2007-07-10 11:54 ` [Bluez-devel] Kernel Oops while transmitting data on several RFCOMMlinks Williams, Richard
2007-07-11 9:36 ` Pierre-Yves Paulus
2007-07-26 13:55 ` Pierre-Yves Paulus
2007-07-26 14:30 ` Marcel Holtmann
2007-09-14 17:04 ` Pierre-Yves Paulus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46EABF2F.6040302@idlum.be \
--to=py@idlum.be \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.