From: Peter Osterlund <petero2@telia.com>
To: Johannes Erdfelt <johannes@erdfelt.com>
Cc: David Brownell <david-b@pacbell.net>, Greg KH <greg@kroah.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] 2.5.40 panic in uhci-hcd
Date: 16 Oct 2002 20:28:22 +0200 [thread overview]
Message-ID: <m2ptuatf09.fsf@p4.localdomain> (raw)
In-Reply-To: <20021016133443.U32760@sventech.com>
Johannes Erdfelt <johannes@erdfelt.com> writes:
> On Wed, Oct 16, 2002, Peter Osterlund <petero2@telia.com> wrote:
> >
> > The problem is back in 2.5.43, although it doesn't happen on every
> > boot. I think I first saw this problem in 2.5.35.
> >
> > The oops looks the same as usual. The oops happens because urb->hcpriv
> > is NULL in uhci_result_control() so the list_empty() check oopses.
> >
> > At the end of uhci_urb_enqueue() this code
> >
> > if (ret != -EINPROGRESS) {
> > uhci_destroy_urb_priv (uhci, urb);
> > return ret;
> > }
> >
> > appears to be calling uhci_destroy_urb_priv() without having acquired
> > the urb_list_lock. Can this be the cause of my problem?
>
> Have you tried this patch? It's in Greg's BK tree, but hasn't been
> picked up by Linus yet.
I applied it to 2.5.39 (which always died at boot before this patch)
and now it boots without problems, so this looks like the correct fix
for my problem. Thanks.
--
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340
prev parent reply other threads:[~2002-10-16 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021008071351.GQ1780@kroah.com>
2002-10-08 18:01 ` [linux-usb-devel] 2.5.40 panic in uhci-hcd Peter Osterlund
2002-10-08 18:19 ` Greg KH
2002-10-08 18:30 ` Peter Osterlund
2002-10-08 20:37 ` David Brownell
2002-10-16 17:32 ` Peter Osterlund
2002-10-16 17:34 ` Johannes Erdfelt
2002-10-16 18:28 ` Peter Osterlund [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=m2ptuatf09.fsf@p4.localdomain \
--to=petero2@telia.com \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=johannes@erdfelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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