| 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
| ||
|
Date: Mon, 10 Dec 2007 17:37:55 +0200 From: Tarkan Erimer <tarkan@...one.net.tr> To: Arjan van de Ven <arjan@...radead.org> CC: Jerry Geis <geisj@...estation.com>, linux-kernel@...r.kernel.org Subject: Re: Kernel BUG in 2.6.23.9 Arjan van de Ven wrote: > well... try to get the oops message out; for many causes of crash that's a good way to find out what happened... > (not always, but it allows us to find patterns if nothing else) > > Unfortunately, I couldn't get the oops message. Because when this behavior happens, the machine hardly freezes and the SysRq combinations do not work. Also, I checked the logs (message,syslog,kern.log etc.) to see something suspicious. Unfortunately, there was none. Just one thing I noticed when investigating on the logs: the kernel is doing its regular jobs. Like cron etc. So, the kernel is not really dieing. Next time, I will try to ssh to my machine to check what's going on, when this behavior occurred. -- 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