From: Marcel Holtmann <marcel@holtmann.org>
To: Kalin KOZHUHAROV <kalin@ThinRope.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.7 and rfcomm Oops (BlueTooth)
Date: Wed, 23 Jun 2004 00:18:58 +0200 [thread overview]
Message-ID: <1087942737.4209.49.camel@pegasus> (raw)
In-Reply-To: <40D8AB57.5040206@ThinRope.net>
Hi Kalin,
> I just managed to start using my phone for ppp via BlueTooth with 2.6.7 (stock + kmsgdump patch).
>
> Sometimes I get the foolowing Oops though:
>
> Bluetooth: RFCOMM ver 1.3
> Bluetooth: RFCOMM socket layer initialized
> Bluetooth: RFCOMM TTY layer initialized
> Unable to handle kernel NULL pointer dereference at virtual address 00000000
> printing eip:
> 00000000
> *pde = 00000000
> Oops: 0000 [#1]
> PREEMPT
> Modules linked in: rfcomm l2cap hci_usb bluetooth usbhid 3c59x nvidia ehci_hcd ohci_hcd usbcore ipv6
> CPU: 0
> EIP: 0060:[<00000000>] Tainted: P
> EFLAGS: 00210202 (2.6.7-KK1_sata)
> EIP is at 0x0
> eax: 00000000 ebx: d5500000 ecx: e0c7f5c0 edx: 00000000
> esi: da66cf58 edi: c0000000 ebp: 00000000 esp: d5501eb4
> ds: 007b es: 007b ss: 0068
> Process rfcomm (pid: 9368, threadinfo=d5500000 task=dd5f6830)
> Stack: e0c7654e da66cf58 00000000 d5500000 e0c7f5c0 e0c76617 da66cf58 00000000
> da66c3d8 d210b000 cfdac7e0 e0c7ade7 da66cf58 00000000 d210b000 00000000
> c0259dcb d210b000 cfdac7e0 00000000 00200286 00000000 026524f0 026524f0
> Call Trace:
> [<e0c7654e>] __rfcomm_dlc_close+0x4e/0xd0 [rfcomm]
> [<e0c76617>] rfcomm_dlc_close+0x47/0x70 [rfcomm]
> [<e0c7ade7>] rfcomm_tty_close+0x67/0xb0 [rfcomm]
> [<c0259dcb>] release_dev+0x60b/0x620
> [<c016552f>] do_pollfd+0x4f/0x90
> [<c01655da>] do_poll+0x6a/0xd0
> [<c025a140>] tty_release+0x0/0x60
> [<c025a16a>] tty_release+0x2a/0x60
> [<c0152d64>] __fput+0x114/0x130
> [<c0151429>] filp_close+0x59/0x90
> [<c01514c1>] sys_close+0x61/0xa0
> [<c0106087>] syscall_call+0x7/0xb
>
> Code: Bad EIP value.
> <6>note: rfcomm[9368] exited with preempt_count 2
what the hell is causing this? I didn't changed anything in the RFCOMM
TTY layer. Please disable preempt support and try again.
Regards
Marcel
next prev parent reply other threads:[~2004-06-22 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 21:57 2.6.7 and rfcomm Oops (BlueTooth) Kalin KOZHUHAROV
2004-06-22 22:18 ` Marcel Holtmann [this message]
2004-06-22 23:38 ` Kalin KOZHUHAROV
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=1087942737.4209.49.camel@pegasus \
--to=marcel@holtmann.org \
--cc=kalin@ThinRope.net \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox