From: Johannes Berg <johannes@sipsolutions.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: HCI crash after tearing down ppp connection
Date: Wed, 28 Jan 2009 10:53:32 +0100 [thread overview]
Message-ID: <1233136412.4151.3.camel@johannes.local> (raw)
In-Reply-To: <1233124538.18259.30.camel@violet>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
Hi Marcel,
> > I use /dev/rfcomm0 to connect to my cell phone, and then to the internet
> > with ppp. Occasionally (two out of the three times I used it today)
> > after I poff the connection the machine locks up. The second time I got
> > a log, but because my display resolution is bad it mostly scrolled off,
> > so I only got to see that hci was involved somehow :/
> >
> > Anyone aware of any such issue? This is on
> > 2.6.29-rc2-wl-11979-gc32422d-dirty (-rc2 + wireless bits).
>
> I was assuming we fixed these, but we might ended with a new one since
> the TTY is changing a little bit and the Bluetooth TTYs are special
> since they are pure virtual TTYs. Can you reproduce this crash every
> time or is it happening only now and then?
Well, it's not happening every time, but fairly often.
> During the last weeks, I am chasing an USB issue with the USB anchors
> and how we use it. You might be hitting the one.
Yeah, I wish I could capture more information here. Can't seem to figure
out how to get more VT resolution. I'll try again. :/
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2009-01-28 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 19:01 HCI crash after tearing down ppp connection Johannes Berg
2009-01-28 6:35 ` Marcel Holtmann
2009-01-28 9:53 ` Johannes Berg [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=1233136412.4151.3.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=marcel@holtmann.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).