From: Chuck Ebbert <cebbert@redhat.com>
To: Andrew Ruthven <puck@catalyst.net.nz>
Cc: linux-kernel@vger.kernel.org, Marcel Holtmann <marcel@holtmann.org>
Subject: Re: [oops] in bluetooth
Date: Thu, 31 May 2007 13:49:31 -0400 [thread overview]
Message-ID: <465F0AAB.5080807@redhat.com> (raw)
In-Reply-To: <1180345089.819.28.camel@lamb>
On 05/28/2007 05:38 AM, Andrew Ruthven wrote:
> Just a follow-up to Marcel regarding Pavel's bluetooth oops. I've had
> the same issue with both 2.6.21 and 2.6.21.2 (skipped .1). I'm able to
> reproduce the oops.
>
> My scenario is connecting from a Treo650 via bluetooth to access the
> Internet by my ADSL link.
>
> The first connection after booting worked just fine, but every attempt
> after that failed with a oops.
>
> Changing to 2.6.22-rc3 as suggested by Marcel however works just fine.
>
So the latest bug fix to net/bluetooth/rfcomm/tty.c should be applied
to 2.6.21-stable, apparently.
next prev parent reply other threads:[~2007-05-31 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-28 9:38 [oops] in bluetooth Andrew Ruthven
2007-05-31 17:49 ` Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-18 14:13 Pavel Machek
2007-05-18 14:19 ` Marcel Holtmann
2007-05-18 15:01 ` Pavel Machek
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=465F0AAB.5080807@redhat.com \
--to=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=puck@catalyst.net.nz \
/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