[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1106100854250.23139@p34.internal.lan>
Date: Fri, 10 Jun 2011 09:07:16 -0400 (EDT)
From: Justin Piszcz <jpiszcz@...idpixels.com>
To: Thomas Gleixner <tglx@...utronix.de>
cc: LKML <linux-kernel@...r.kernel.org>,
Alan Piszcz <ap@...arrain.com>, Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: 2.6.39: crash w/threadirqs option enabled
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists