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: <alpine.LFD.0.9999.0712081644560.12046@woody.linux-foundation.org>
Date:	Sat, 8 Dec 2007 16:47:17 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Marco Gatti <marco@...noinflames.de>
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



On Sat, 8 Dec 2007, Marco Gatti wrote:
> 
> Today, I tested with different amounts of RAM:
> 
> 2 GB: everything works fine
> 4 GB: same issue as described before with allocating block in system zone
> 
> So what to do, in order to use more than 2 Gigs of RAM?

Was there a dmesg out there somewhere?

With 4G of RAM, you probably have some of it above the 4GB mark (because 
of RAM remapping etc, and the PCI decode hole in the low 4GB). It does 
sound like this is a DMA problem, and your controller cannot correctly DMA 
to the upper 4GB.

So what controller/driver, what's the dmesg, and let's see if we can fix 
it by adding a DMA mask to it to limit it to the low 32 bits.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ