| 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
| ||
|
Message-ID: <alpine.DEB.2.02.1105201210030.19553@p34.internal.lan> Date: Fri, 20 May 2011 12:10:49 -0400 (EDT) From: Justin Piszcz <jpiszcz@...idpixels.com> To: Thomas Gleixner <tglx@...utronix.de> cc: linux-kernel@...r.kernel.org, Alan Piszcz <ap@...arrain.com> 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: >>> 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. 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