linux-kernel - Re: kernel panic w/ 2.6.22.1, VIA EPIA Mini ITX

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200707282041.l6SKfgM8000387@wildsau.enemy.org>
Date:	Sat, 28 Jul 2007 22:41:39 +0200 (MET DST)
From:	Herbert Rosmanith <kernel@...dsau.enemy.org>
To:	linux-kernel@...r.kernel.org
Subject: Re: kernel panic w/ 2.6.22.1, VIA EPIA Mini ITX

> Checked the RAM on the box? Kinda weird if you're getting VRAM corruption, I 
> wonder if this is due to the RAM failing at the point where the framebuffer 
> is mapped?

you are probably right... I removed one of the RAMs, no crash
anymore. This is not ... nice. The manual says, that the board can
handle up to 1GB (2x512MB). I don't think the RAM itself is damaged --
these are brandnew Kingston "ValueRam" PC133 SD-RAMs with lifelong 
guarantee. I wonder if this behaviour only apperas with my particular
board, or if all VIA EPIA Mini ITX 500 are affected (I've run out
of boards to test ...)

thanks,
herp

> Try running memtest86 on it.

good idea.

-
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/