linux-kernel - Re: Bug: get EXT3-fs error Allocating block in system zone

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4758F53E.6010505@pianoinflames.de>
Date:	Fri, 07 Dec 2007 08:24:46 +0100
From:	Marco Gatti <marco@...noinflames.de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Greg KH <greg@...ah.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: Bug: get EXT3-fs error Allocating block in system zone

Linus Torvalds schrieb:
> 
> But the disk errors are something else, doesn't ring a bell. Sounds like 
> IO corruption on the group descriptor block or something like that. Might 
> be worth testing to see if the problem goes away with less than 4GB of 
> RAM..
> 

Thanks, I'll try this, to see if there's a dependency on that. But it's 
not a really solution for a virtualization system to work with less 
memory ;-). I also read that there's maybe a problem with intel graphics 
media accelerator driver in conjunction with more than 4GB RAM and 
kernel will hang on boot, but I think this is fixed, I can boot. So 
securly, I put out i915 series drivers and frame buffer support in 
kernel config. The grahpics adapter onboard works with shared memory 
technology. I configured 128M in BIOS...
--
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/