From: Kalin KOZHUHAROV <kalin@ThinRope.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.7 and rfcomm Oops (BlueTooth)
Date: Wed, 23 Jun 2004 08:38:38 +0900 [thread overview]
Message-ID: <40D8C2FE.3060901@ThinRope.net> (raw)
In-Reply-To: <1087942737.4209.49.camel@pegasus>
Marcel Holtmann wrote:
> 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:
[snip oops]
>
> what the hell is causing this? I didn't changed anything in the RFCOMM
> TTY layer. Please disable preempt support and try again.
Well, no idea. The keyword here is "sometimes"...
I'll try to find a better way to reproduce this and report again with/without preempt.
AFAIR, last time I got this when I "abruptly" stopped the BT stack on my phone, while using rfcomm for ppp.
Just in case, I updated to bluez-{libs,utils}-2.7, but still got one Oops (essentially the same).
These days I'll have to use the phone and a laptop, but will be away. If I found out something more will post it.
Kalin.
--
||///_ o *****************************
||//'_/> WWW: http://ThinRope.net/
prev parent reply other threads:[~2004-06-22 23:38 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
2004-06-22 23:38 ` Kalin KOZHUHAROV [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=40D8C2FE.3060901@ThinRope.net \
--to=kalin@thinrope.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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