| 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: <Pine.LNX.4.64.0712171540040.6503@blonde.wat.veritas.com> Date: Mon, 17 Dec 2007 15:47:20 +0000 (GMT) From: Hugh Dickins <hugh@...itas.com> To: "Hemmann, Volker Armin" <volker.armin.hemmann@...clausthal.de> cc: linux-kernel@...r.kernel.org Subject: Re: almost daily Kernel oops with 2.6.23.9 - and now 2.6.23.11 as well On Mon, 17 Dec 2007, Hemmann, Volker Armin wrote: > > I got another crash, now with 2.6.23.11 on logout from KDE (two differences, > new kernel, 4gb ram instead of 2gb): > > [ 1771.063731] Unable to handle kernel paging request at 0000040000000000 RIP: > also I got some strange message yesterday before increasing ramsize: > [19546.639528] swap_free: Bad swap offset entry 04000000 > [27999.370777] swap_free: Bad swap offset entry 04000000 > [27999.434282] swap_free: Bad swap offset entry 04000000 > [27999.466035] swap_free: Bad swap offset entry 04000000 > [27999.521132] swap_free: Bad swap offset entry 04000000 > [27999.561621] VM: killing process ld-linux-x86-64 > [27999.561719] swap_free: Bad swap offset entry 04000000 You're seeing a single bit set where it shouldn't be: please give memtest86+ a good try; if it's not actually your memory that's bad, then I'd guess it's something like overheating (please correct me, ye who know better). Hugh -- 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