From: Linus Torvalds <torvalds@linux-foundation.org>
To: Marco Gatti <marco@pianoinflames.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Bug: get EXT3-fs error Allocating block in system zone
Date: Sat, 8 Dec 2007 16:47:17 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.0.9999.0712081644560.12046@woody.linux-foundation.org> (raw)
In-Reply-To: <475B0AD7.10500@pianoinflames.de>
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
next prev parent reply other threads:[~2007-12-09 0:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 20:54 Marco Gatti
2007-12-07 0:25 ` Andrew Morton
2007-12-07 0:42 ` Linus Torvalds
2007-12-07 7:24 ` Marco Gatti
2007-12-08 21:21 ` Marco Gatti
2007-12-09 0:47 ` Linus Torvalds [this message]
2007-12-09 16:59 ` Marco Gatti
2007-12-07 7:11 ` Marco Gatti
[not found] <fa.Fg53DJSEh/kZhf/uRCv9FYZsaSQ@ifi.uio.no>
[not found] ` <fa.nPzIjJ2SchPb1LOa/dRWb/WyEZU@ifi.uio.no>
[not found] ` <fa.LkmHGN+Fx6H930bfeCDU6pGdBKM@ifi.uio.no>
[not found] ` <fa.oSqMiIX7WubypXrhZGaRKU5wNGU@ifi.uio.no>
[not found] ` <fa.0pc9/nNmTq+eWIU9rADRn0xYGdI@ifi.uio.no>
[not found] ` <fa.hqM73i24f6G31R5F3sKL8+3H8Ww@ifi.uio.no>
2007-12-09 17:55 ` Robert Hancock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.0.9999.0712081644560.12046@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco@pianoinflames.de \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®