From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Tejun Heo <tj@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [BUG] lockup with the latest kernel
Date: Tue, 08 Sep 2009 22:29:13 -0400 [thread overview]
Message-ID: <1252463353.11070.12.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0908281428180.3647@gandalf.stny.rr.com>
On Fri, 2009-08-28 at 14:33 -0400, Steven Rostedt wrote:
> On Fri, 28 Aug 2009, Steven Rostedt wrote:
> > On Thu, 27 Aug 2009, Linus Torvalds wrote:
> > > > ...
> > > > >> [13288.222084] EIP: 0060:[<c0110821>] EFLAGS: 00000002 CPU: 0
> > > > >> [13288.222084] EIP is at default_send_IPI_mask_logical+0x53/0x92
> > >
> > > Is this one perhaps fixed by b04e6373d694 ("x86: don't call
> > > '->send_IPI_mask()' with an empty mask")
> > >
> > > It sounds a _lot_ like that bug. Older dual-cpu x86 box, and APIC getting
> > > confused by the occasional empty CPU mask, and then subsequent IPI's will
> > > hang.
> >
> > I'll update my box to that kernel and see what happens and let you know.
>
> I checked out the commit at b04e6373d694, compiled and booted that kernel.
> So far, so good. It survived logging into a gnome session (sometimes locks
> up there), and a full kernel compile (usually locks up there too). But
> there's been rare times that it would take days before hitting the bug.
>
> I'll keep it in this kernel for a while and if it lasts the week, I'll
> consider it fixed. This box acts as my email, dhcp and web server, as well
> as one of the boxes in my distcc farm, thus it gets a bit of use. It will
> not be idle during this time period.
Just an update.
The box currently has an uptime of 11 days. I have not hit the bug at
all, and it has survived numerous compiles (both locally and as a distcc
server). It has been serving up my email and web pages without a hitch.
I'd say that commit fixed the bug. (knock on wood).
-- Steve
(or it could have been the penguins:
http://rostedt.homelinux.com/gallery2/main.php?g2_itemId=7860 )
prev parent reply other threads:[~2009-09-09 2:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 15:49 Steven Rostedt
2009-08-19 15:50 ` Steven Rostedt
2009-08-19 16:18 ` Andrew Morton
2009-08-27 22:41 ` Steven Rostedt
2009-08-27 22:45 ` Steven Rostedt
2009-08-28 2:46 ` Tejun Heo
2009-08-28 2:52 ` Tejun Heo
2009-08-28 6:36 ` Ingo Molnar
2009-08-28 6:59 ` Tejun Heo
2009-08-28 4:05 ` Linus Torvalds
2009-08-28 16:15 ` Steven Rostedt
2009-08-28 18:33 ` Steven Rostedt
2009-09-09 2:29 ` Steven Rostedt [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=1252463353.11070.12.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®