From: Greg KH <greg@kroah.com>
To: Alex Walker <alex@x3ja.co.uk>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.10: 2 OOPs - "BUG at usb.c" and "unable to handle kernel paging request"
Date: Thu, 25 Apr 2002 08:13:52 -0700 [thread overview]
Message-ID: <20020425151352.GD19161@kroah.com> (raw)
In-Reply-To: <20020424142132.K23497@x3ja.co.uk> <20020425074651.GA17368@kroah.com> <20020425133703.Q23497@x3ja.co.uk> <20020425145450.GA19161@kroah.com> <20020425170413.V23497@x3ja.co.uk>
On Thu, Apr 25, 2002 at 05:04:13PM +0100, Alex Walker wrote:
> Look! It's Greg!
>
> On Thu, Apr 25, 2002 at 07:54:50AM -0700, Greg KH wrote:
> > On Thu, Apr 25, 2002 at 01:37:03PM +0100, Alex Walker wrote:
> > > 'ello Greg On Thu, Apr 25, 2002 at 12:46:51AM -0700, Greg KH wrote:
> > > > > Hi, I'm not subscribed - please CC me in any replies. Two OOps
> > > > > when running 2.5.10, as attached. With attatched config. First
> > > > > occurs on boot, but doesn't stop the whole system. The second
> > > > > occurs as I was rebooting - see the attached log to see where
> > > > > they happen. Any more info required? Just ask.
> > > > Known problem with the uhci driver right now, just use usb-uhci
> > > > instead (not the ALT UHCI driver) for now until things get
> > > > straightend out.
> > > Yes, that's solved the first oops. Is the second one related?
> > Probably, does the second one still happen now?
>
> Sorry, that would have been useful for me to say wouldn't it? yes it
> does still happen.
Ah, I have no idea. The ksymoops report doesn't give very much to go
by, so I'll guess that it's not a USB problem :)
thanks,
greg k-h
next prev parent reply other threads:[~2002-04-25 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 13:21 2.5.10: 2 OOPs - "BUG at usb.c" and "unable to handle kernel paging request" Alex Walker
2002-04-25 7:46 ` Greg KH
2002-04-25 12:37 ` Alex Walker
2002-04-25 14:54 ` Greg KH
2002-04-25 16:04 ` Alex Walker
2002-04-25 15:13 ` Greg KH [this message]
2002-04-25 18:04 ` Johannes Erdfelt
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=20020425151352.GD19161@kroah.com \
--to=greg@kroah.com \
--cc=alex@x3ja.co.uk \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.