From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-kernel@vger.kernel.org
Cc: Chuansheng Liu <chuansheng.liu@intel.com>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: Re: [REGRESSION] 3.7-rc3+git hard lockup on CPU after inserting/removing USB stick
Date: Sat, 10 Nov 2012 17:51:19 +0100 [thread overview]
Message-ID: <201211101751.20314.Martin@lichtvoll.de> (raw)
In-Reply-To: <201211101734.07084.Martin@lichtvoll.de>
[-- Attachment #1: Type: Text/Plain, Size: 2887 bytes --]
Am Samstag, 10. November 2012 schrieb Martin Steigerwald:
> CC´d bad patch author Chuansheng as well as Ingo and Thomas as the
> issue seems to be thread irqs related.
>
> Am Mittwoch, 7. November 2012 schrieb Martin Steigerwald:
> > 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 bisected this after having made a backup:
[… bisect log and some explainations …]
> The first bad commit is:
>
> commit 73d4066055e0e2830533041f4b91df8e6e5976ff
> Author: Chuansheng Liu <chuansheng.liu@intel.com>
> Date: Tue Sep 11 16:00:30 2012 +0800
>
> USB/host: Cleanup unneccessary irq disable code
>
> Because the IRQF_DISABLED as the flag is now a NOOP and has been
> deprecated and in hardirq context the interrupt is disabled.
>
> so in usb/host code:
> Removing the usage of flag IRQF_DISABLED;
> Removing the calling local_irq save/restore actions in irq
> handler usb_hcd_irq();
>
> Signed-off-by: liu chuansheng <chuansheng.liu@intel.com>
> Acked-by: Alan Stern <stern@rowland.harvard.edu>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
>
> But:
>
> This ony happens with threadirqs option!
Just another note:
irq/16-ehci_hcd was taking >99% CPU. It had PR -51 in top and I think this
was the task that made the CPU core stuck.
I have a short dmesg piece from the bad commit kernel. Attached.
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
[-- Attachment #2: dmesg-on-bad-commit-kernel.txt.xz --]
[-- Type: application/x-xz, Size: 15620 bytes --]
next prev parent reply other threads:[~2012-11-10 16:51 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
2012-11-10 16:34 ` Martin Steigerwald
2012-11-10 16:51 ` Martin Steigerwald [this message]
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=201211101751.20314.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=chuansheng.liu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).