From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Zdenek Kabelac <zdenek.kabelac@gmail.com>,
USB list <linux-usb@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-bluetooth@vger.kernel.org
Subject: Re: Endless print of uhci_result_common: failed with status 440000
Date: Tue, 12 Apr 2011 15:26:18 -0300 [thread overview]
Message-ID: <20110412182618.GB2836@joana> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1104121210250.2000-100000@iolanthe.rowland.org>
* Alan Stern <stern@rowland.harvard.edu> [2011-04-12 12:10:56 -0400]:
> On Tue, 12 Apr 2011, Zdenek Kabelac wrote:
>
> > 2011/4/11 Alan Stern <stern@rowland.harvard.edu>:
> > > On Mon, 11 Apr 2011, Zdenek Kabelac wrote:
> > >
> > >> > I've created:
> > >> >
> > >> > https://bugzilla.kernel.org/show_bug.cgi?id=33062
> > >> >
> > >> > and I'm cc-ing linux-bluetooth.
> > >> >
> > >>
> > >> In fact this Ooops might be related to:
> > >>
> > >> http://marc.info/?l=linux-kernel&m=130207593728273&w=2
> > >
> > > It might be. ?Did you try reverting the patch mentioned in that email?
> > >
> >
> > Yep - it looks like the patch
> > http://marc.info/?l=linux-bluetooth&m=130230770920378&w=2
> > solved my problem with weird deadlocks.
I pushed a patch that fixes this in a better way, it's on the bluetooth-2.6
tree (should arrive to linus tree in some days).
--
Gustavo F. Padovan
http://profusion.mobi
next prev parent reply other threads:[~2011-04-12 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTin3Qg1dHqAVXfZR1g_AK2JuSKLmdg@mail.gmail.com>
[not found] ` <Pine.LNX.4.44L0.1104111217560.1975-100000@iolanthe.rowland.org>
2011-04-11 17:24 ` Endless print of uhci_result_common: failed with status 440000 Zdenek Kabelac
2011-04-11 17:32 ` Zdenek Kabelac
2011-04-11 18:38 ` Alan Stern
2011-04-12 9:33 ` Zdenek Kabelac
2011-04-12 16:10 ` Alan Stern
2011-04-12 18:26 ` Gustavo F. Padovan [this message]
2011-04-18 10:54 ` Zdenek Kabelac
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=20110412182618.GB2836@joana \
--to=padovan@profusion.mobi \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
--cc=zdenek.kabelac@gmail.com \
/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