From: Martin Steigerwald <Martin@lichtvoll.de>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] 3.7-rc3+git hard lockup on CPU after inserting/removing USB stick
Date: Wed, 7 Nov 2012 19:52:24 +0100 [thread overview]
Message-ID: <201211071952.24509.Martin@lichtvoll.de> (raw)
In-Reply-To: <20121107143800.GA14146@kroah.com>
[-- Attachment #1: Type: Text/Plain, Size: 2212 bytes --]
Am Mittwoch, 7. November 2012 schrieb Greg Kroah-Hartman:
> On Wed, Nov 07, 2012 at 03:01:38PM +0100, Martin Steigerwald wrote:
> > Hi!
> >
> > I had this with something in between 3.7-rc3 und 3.7-rc4 after
> > inserting and removing an USB stick. This example is with a kernel +
> > f2fs patches v3, but I had this with 3.7-rc3 as well.
>
> Ok, so it's not a new thing introduced in 3.7-rc4 (which is good, as
> there wasn't any USB patches added between -rc3 and -rc4.)
>
> Does it also happen on -rc2? Anything older? Can you run 'git bisect'
> to try to track it down?
It appears to be worse with 3.7-rc1. The machine basically locked up a few
moments after inserting the stick.
First time I was on some tty and I saw lots of backtraces flowing by the
process of which the BTRFS on /, which resides on an unrelated internal
Intel SSD 320, was switched to read only. There have been pauses between
backtraces. Second I was in KDE session which basically locked up soon as
well. No mouse pointer movements where possible, no switching to tty1.
I only have the last part of the backtrace of the first occurence as photo.
Nothing was saved on SSD.
I do not want to go an earlier 3.7 version than rc1 on this production
machine.
I can try rc2 tomorrow.
How to proceed? With 3.7-rc3+somegit I was at least able to save out some
dmesg output to the SSD before I rebooted the machine. I can try to get
some longer backtrace this way.
Oh, I see I have a dmesg > file that actually made it to SSD. This one is a
tiny bit longer than the first one. Attached. The screenshot of shortly
before I rebooted the machine is in [1]. That was some seconds after the
BTRFS read only part slipped by. These are from the same, first occurence.
I wonder that this apparently hasn´t been reported already. It may be
configuration specific. I attached config file. It was same for plain rc3 and
just with some f2fs options added for the f2fs kernel in my first post.
[1] http://martin-steigerwald.de/tmp/kernel/usb-hang/IMG_0685.JPG
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
[-- Attachment #2: config-3.7.0-rc1-tp520.xz --]
[-- Type: application/x-xz, Size: 25292 bytes --]
[-- Attachment #3: 3.7-rc1-usb-hang.txt.xz --]
[-- Type: application/x-xz, Size: 16300 bytes --]
next prev parent reply other threads:[~2012-11-07 18:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 14:01 [REGRESSION] 3.7-rc3+git hard lockup on CPU after inserting/removing USB stick Martin Steigerwald
2012-11-07 14:38 ` Greg Kroah-Hartman
2012-11-07 18:52 ` Martin Steigerwald [this message]
2012-11-10 16:34 ` Martin Steigerwald
2012-11-10 16:51 ` Martin Steigerwald
2012-11-11 0:53 ` Liu, Chuansheng
2012-11-12 14:27 ` Martin Steigerwald
2012-11-12 19:31 ` Thomas Gleixner
2012-11-13 0:47 ` Liu, Chuansheng
2012-11-13 18:52 ` Greg Kroah-Hartman
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=201211071952.24509.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=gregkh@linuxfoundation.org \
--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.