public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Mate Soos <mate@srlabs.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Kernel Oops when unplugging USB
Date: Wed, 21 Mar 2012 13:59:08 -0700	[thread overview]
Message-ID: <20120321205908.GA8456@kroah.com> (raw)
In-Reply-To: <4F6A3155.30603@srlabs.de>

On Wed, Mar 21, 2012 at 08:51:49PM +0100, Mate Soos wrote:
> 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

Look at the patches from 3.2.0 to 3.2.12, a number of them might have
fixed this, previous reporters say that this problem is now gone, hence
me asking if this is true here as well.

thanks,

greg k-h

      reply	other threads:[~2012-03-21 20:59 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
2012-03-21 20:59     ` Greg KH [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=20120321205908.GA8456@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mate@srlabs.de \
    /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