From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Alan Piszcz <ap@solarrain.com>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: 2.6.39: crash w/threadirqs option enabled
Date: Fri, 10 Jun 2011 09:07:16 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1106100854250.23139@p34.internal.lan> (raw)
In-Reply-To: <alpine.LFD.2.02.1106101450030.11814@ionos>
On Fri, 10 Jun 2011, Thomas Gleixner wrote:
> On Fri, 10 Jun 2011, Justin Piszcz wrote:
>> On Fri, 20 May 2011, Thomas Gleixner wrote:
>> Crashed again and it rebooted too:
>>
>> reboot system boot 2.6.39 Thu Jun 9 23:58 - 04:05 (04:06)
>> user1 pts/0 X Thu Jun 9 19:25 - 19:30 (00:04)
>> user1 pts/10 X Thu Jun 9 18:23 - crash (05:35)
>>
>> Any thoughts on what could be causing this?
>> Should I go back to 2.6.38?
>
> If you remove the threadirqs option from the commandline it does not
> happen, right?
Yes, most often anyhow (still using that option)
>
> Can you try the following patch ?
Yup, patched:
# patch -p1 < ../patch-for-cpu
patching file arch/x86/kernel/smpboot.c
#
New kernel running now, I also plugged in my USB devices back in as well, we'll see what happens.
Justin.
next prev parent reply other threads:[~2011-06-10 13:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 8:39 Justin Piszcz
2011-05-20 12:48 ` Thomas Gleixner
2011-05-20 12:51 ` Justin Piszcz
2011-05-20 13:30 ` Thomas Gleixner
2011-05-20 13:49 ` Justin Piszcz
2011-05-20 15:17 ` Thomas Gleixner
2011-05-20 16:10 ` Justin Piszcz
2011-05-20 16:22 ` Thomas Gleixner
2011-05-21 0:00 ` Uwaysi Bin Kareem
2011-06-10 8:17 ` Justin Piszcz
2011-06-10 8:24 ` Justin Piszcz
2011-06-10 12:52 ` Thomas Gleixner
2011-06-10 13:07 ` Justin Piszcz [this message]
2011-06-10 13:10 ` Thomas Gleixner
2011-06-12 12:04 ` Justin Piszcz
2012-09-16 20:34 ` Low os-jitter operating system Uwaysi Bin Kareem
2011-05-26 16:30 ` 2.6.39: crash w/threadirqs option enabled Justin Piszcz
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=alpine.DEB.2.02.1106100854250.23139@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®