| 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: <44E7369D.2010707@xs4all.nl> Date: Sat, 19 Aug 2006 18:04:45 +0200 From: Udo van den Heuvel <udovdh@...all.nl> To: linux-kernel@...r.kernel.org CC: Mike Galbraith <efault@....de>, Folkert van Heusden <folkert@...heusden.com> Subject: Re: And another Oops / BUG? (2.6.17.8 on VIA Epia CL6000) Mike Galbraith wrote: > On Wed, 2006-08-16 at 05:42 +0200, Udo van den Heuvel wrote: >> Again my CL6000 Oopsed. >> >> How can I proceed to find the cause? >> > (these oopsen would be a heck of a lot easier to look at if the > timestamp junk was stripped off) Will try to do that next time. > The oops doesn't help much. Once again, eip is in lala land, not the > kernel. Hmm. At least that is consistent, as is the named involvement and the rest of the effects. > Given that you're the only person posting this kind of explosion, I > would cast a very skeptical glance toward my hardware. I'd suggest > reverting to a known good kernel first, to verify that you really don't > have a hardware problem cropping up. How long should I run a 2.6.16.* kernel to be sure enough it is not my hardware? > After I did that, I'd enable stack check thingies under kernel hacking, > and if that didn't turn up anything, I'd try slab and page allocator > debugging options and hope to catch someone scribbling where they're not > supposed to. OK, will try that. - 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