From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Re: 2.6.0-test5 usbserial oops
Date: Wed, 17 Sep 2003 21:09:55 -0700 [thread overview]
Message-ID: <20030918040955.GB2849@kroah.com> (raw)
In-Reply-To: <20030911223224.GA1345@glitch.localdomain>
On Thu, Sep 11, 2003 at 05:32:24PM -0500, Greg Norris wrote:
> On Thu, Sep 11, 2003 at 10:57:56AM -0700, Greg KH wrote:
> > Hm, can you try the following patch and let me know if it fixes the
> > problem for you?
> >
> > thanks,
> >
> > greg k-h
>
> I'm still getting an (apparently) identical oops. I've attached the
> ksymoops output (your patch was applied for this one), along with the
> debugging messages you requested previously. Let me know if I can
> provide any additional info.
Does this happen on 2.6.0-test5-bk3?
thanks,
greg k-h
next prev parent reply other threads:[~2003-09-18 4:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F60B4AB.7060109@kmlinux.fjfi.cvut.cz>
2003-09-11 17:57 ` Re: 2.6.0-test5 usbserial oops Greg KH
2003-09-11 22:32 ` Greg Norris
2003-09-18 4:09 ` Greg KH [this message]
2003-09-19 1:39 ` Greg Norris
2003-09-11 3:30 Greg Norris
2003-09-11 4:46 ` Greg KH
2003-09-12 21:20 ` Cliff White
2003-10-11 19:35 ` 2.6.0-test7 " Greg Norris
2003-10-23 2:43 ` Greg Norris
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=20030918040955.GB2849@kroah.com \
--to=greg@kroah.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