From: Pete Zaitcev <zaitcev@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Chrissie <x.chrissie.x@t-online.de>
Subject: Re: Oops with usb-mass-storage
Date: Fri, 10 Jan 2003 11:13:25 -0500 [thread overview]
Message-ID: <200301101613.h0AGDP427356@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1042201321.19067.linux-kernel2news@redhat.com>
>> i get an kernel oops after following additional output to the console
>
> An oops? This is *the* first oops, please decode and post it to USB folks.
> Subsequent oopses are of much less help...
I got him to send the decoded oops, but it's the usual
uhci_free_dev => ... => usb_destroy_configuration => kfree
May be fixed in pre3, may be not...
-- Pete
prev parent reply other threads:[~2003-01-10 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 16:50 Oops with usb-mass-storage Chrissie
2003-01-10 12:09 ` Denis Vlasenko
[not found] ` <mailman.1042201321.19067.linux-kernel2news@redhat.com>
2003-01-10 16:13 ` Pete Zaitcev [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=200301101613.h0AGDP427356@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x.chrissie.x@t-online.de \
/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