linux-kernel - Re: 2.6.39: crash w/threadirqs option enabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.02.1106100414550.32450@p34.internal.lan>
Date:	Fri, 10 Jun 2011 04:17:31 -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, 20 May 2011, Thomas Gleixner wrote:

> On Fri, 20 May 2011, Justin Piszcz wrote:
>> On Fri, 20 May 2011, Thomas Gleixner wrote:
>>
>>> On Fri, 20 May 2011, Justin Piszcz wrote:
>>>> On Fri, 20 May 2011, Thomas Gleixner wrote:
>>>>> Does it crash right away or just when doing something particular?
>>>> It crashed at 2100, this is when I run a few I/O intensive processes:
>>>> - backup (dump ext4 filesystem -> to a separate raid device)
>>>> - backup (dump ext4 on remote host -> to separate raid device)
>>>> - backup (dump xfs on remote host -> to separate raid device)
>>>>
>>>> This looks like it is what caused it to crash.
>>>
>>> That narrows it down somewhat, but does not give us a clue at all :(
>>>
>>>>> Is the box fully dead after the crash ?
>>>> The host was online and I went away for awhile, when I came back the
>>>> system
>>>> had rebooted on its own (as I lost all of my X windows/etc).
>>>
>>> Hmm. Did you have panic_timeout set ?
>>
>> Hi,
>>
>> No, I do not use panic_timeout or any type of watchdog that would reboot
>> the system upon a lockup/crash.
>
> Yuck, that means it ran into a triple fault. Nasty. I have no idea how
> to debug that at the moment and I was not able to reproduce on one of
> my test systems. Maybe I need to try harder.
>
> Thanks,
>
> 	tglx
>
>
>
>

Hi,

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?

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/