From: Greg KH <greg@kroah.com>
To: "John D. Davis" <jddavis@triad.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possible problems with khub in current 2.4.15-2.4.16 kernels
Date: Mon, 26 Nov 2001 13:51:42 -0800 [thread overview]
Message-ID: <20011126135142.A4675@kroah.com> (raw)
In-Reply-To: <3C029D3F.E43B4E9C@triad.rr.com>
In-Reply-To: <3C029D3F.E43B4E9C@triad.rr.com>
On Mon, Nov 26, 2001 at 02:51:27PM -0500, John D. Davis wrote:
> I've noticed an odd occurance with the 2.4.15 and 2.4.16 kernels during
> testing.
>
> There seems to be a problem with khub.c or it could be my hardware but
> I keep getting the following oops and ptrace about 50% of the time
> during boot. The following snip is from the boot log of the 2.4.16
> kernel compliled this afternoon.
Does this happen when you plug in your device after Linux is booted?
Can you send the output of /proc/bus/usb/devices with the device plugged
in (if it doesn't always cause an oops)?
Can you run that oops through ksymoops and post it?
thanks,
greg k-h
next prev parent reply other threads:[~2001-11-26 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 19:51 Possible problems with khub in current 2.4.15-2.4.16 kernels John D. Davis
2001-11-26 21:51 ` Greg KH [this message]
2001-11-27 4:23 ` John D. Davis
2001-11-27 5:30 ` Greg KH
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=20011126135142.A4675@kroah.com \
--to=greg@kroah.com \
--cc=jddavis@triad.rr.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox