All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mate Soos <mate@srlabs.de>
To: Greg KH <greg@kroah.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: Kernel Oops when unplugging USB
Date: Wed, 21 Mar 2012 20:51:49 +0100	[thread overview]
Message-ID: <4F6A3155.30603@srlabs.de> (raw)
In-Reply-To: <20120320135637.GA4634@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]

Dear Greg,

On 03/20/2012 02:56 PM, Greg KH wrote:
> On Mon, Mar 19, 2012 at 03:51:43PM +0100, Mate Soos wrote:
>> [2.] Full description of the problem/report:
>> The kernel oops-ed when I pulled out an umounted 8GB USB key. This seems
>> to be visible in the "messages" file. All the data attached, except for
>> the "messages" has been produced after a reboot, since the system
>> hanged. Luckily, the "messages" got saved. The system after restart
>> should have exactly the same modules loaded as before.
>>
>> [3.] Keywords (i.e., modules, networking, kernel):
>> USB, Kernel Ooops, Watchdog
>>
>> [4.] Kernel version (from /proc/version):
>> $ cat
>>  /proc/version
>> Linux version 3.2.0-1-amd64 (Debian 3.2.4-1) (waldi@debian.org) (gcc
>> version 4.6.2 (Debian 4.6.2-12) ) #1 SMP Sun Feb 5 15:17:15 UTC 2012
> 
> Can you please try the 3.2.12 release, this should be resolved there
> already.
> 
> Or can you try 3.3?

Can you please indicate what you are suspecting to have fixed the
problem? Once verified, I could add it to the bugzilla entries at

https://bugzilla.kernel.org/show_bug.cgi?id=42963
http://ati.cchtml.com/show_bug.cgi?id=465

and we could close them as FIXED.

Thanks,

Mate

-- 
Mate Soos
Security Research Labs
http://www.srlabs.de


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 6252 bytes --]

  reply	other threads:[~2012-03-21 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 14:51 PROBLEM: Kernel Oops when unplugging USB Mate Soos
2012-03-20 13:56 ` Greg KH
2012-03-21 19:51   ` Mate Soos [this message]
2012-03-21 20:59     ` 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=4F6A3155.30603@srlabs.de \
    --to=mate@srlabs.de \
    --cc=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 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.