From: Jiri Slaby <jirislaby@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: linux-usb-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: usb related oops after resume
Date: Tue, 01 Aug 2006 09:48:33 +0159 [thread overview]
Message-ID: <44CF0768.3050507@gmail.com> (raw)
In-Reply-To: <20060801051446.GA23206@kroah.com>
Greg KH wrote:
> On Tue, Aug 01, 2006 at 01:47:22AM +0159, Jiri Slaby wrote:
>> Hello,
>>
>> during resume I got this oops in 2.6.18-rc1-mm2 kernel:
>
> Does the 2.6.18-rc3 kernel work properly for you?
>
> How about a newer -mm release?
The problem is, I can't reproduce it easily, I don't know what was the matter,
it oopsed only once, while I was using 2.6.18-rc1-mm2. Now, I have
2.6.18-rc2-mm1 and no oops in the time being :(.
regards,
--
<a href="http://www.fi.muni.cz/~xslaby/">Jiri Slaby</a>
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
prev parent reply other threads:[~2006-08-01 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 23:48 usb related oops after resume Jiri Slaby
2006-08-01 5:14 ` Greg KH
2006-08-01 7:49 ` Jiri Slaby [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=44CF0768.3050507@gmail.com \
--to=jirislaby@gmail.com \
--cc=greg@kroah.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