| 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: <200801230430.m0N4UmpU029430@turbo.physics.adelaide.edu.au> Date: Wed, 23 Jan 2008 15:00:48 +1030 (CST) From: Jonathan Woithe <jwoithe@...sics.adelaide.edu.au> To: linux-kernel@...r.kernel.org Cc: jwoithe@...sics.adelaide.edu.au (Jonathan Woithe) Subject: XFS oops under 2.6.23.9 Last night my laptop suffered an oops during closedown. The full oops reports can be downloaded from http://www.atrad.com.au/~jwoithe/xfs_oops/ as photos of the screen. Since the laptop was unusable at this point I wasn't able to cut and paste the details, and they weren't in the logs when the machine was rebooted. The initial complaint claims to be an "invalid opcode". Is this possibly a memory fault developing or does it ring any bells for anyone? memtest86 finds no fault with the memory. Kernel version was kernel.org 2.6.23.9 compiled as a low latency desktop. The RT patches were not applied. Regards jonathan -- 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