| 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: <200612210308_MC3-1-D5D4-3328@compuserve.com> Date: Thu, 21 Dec 2006 03:05:23 -0500 From: Chuck Ebbert <76306.1226@...puserve.com> To: Alistair John Strachan <s0348365@....ed.ac.uk> Cc: linux-kernel@...r.kernel.org Subject: Re: Oops in 2.6.19.1 In-Reply-To: <200612202215.50315.s0348365@....ed.ac.uk> On Wed, 20 Dec 2006 22:15:50 +0000, Alistair John Strachan wrote: > > I'd guess you have some kind of hardware problem. It could also be > > a kernel problem where the saved address was corrupted during an > > interrupt, but that's not likely. > > Seems pretty unlikely on a 4 year old Via Epia. Never had any problems with it > before now. > > Maybe a cosmic ray event? ;-) The low byte of eip should be 5f and it changed to 60, so that's probably not it. And the oops report is consistent with that being the instruction that was really executed, so it's not the kernel misreporting the address after it happened. You weren't trying kprobes or something, were you? Have you ever had another unexplained oops with this machine? -- MBTI: IXTP - 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