public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Marco Gatti <marco@pianoinflames.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	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: Sun, 09 Dec 2007 11:55:14 -0600	[thread overview]
Message-ID: <475C2C02.70001@shaw.ca> (raw)
In-Reply-To: <fa.hqM73i24f6G31R5F3sKL8+3H8Ww@ifi.uio.no>

Marco Gatti wrote:
> Linus Torvalds schrieb:
>> 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.
> 
> Controller / drivers:
> it's a board with intel Q35 chipset. The southbridge has an ICH9
> Intel Gigabit 82566DM-2 => e1000
> Intel matrix storage SATA => ahci.c
> Intel graphics media accelerator => not added to kernel
> Intel Audio => Intel HD Audio AC97
> 
> I just got "EXT3-fs error Allocating block in system zone" in dmesg with 
> 4 or more GBs of RAM. I listed boot up dmesg to get an idea of dma 
> config with different amount of RAM.
> 
> Thanks for your help.

The obvious suspect with a filesystem problem would be the disk 
controller driver, AHCI here. However, the controller appears to set the 
flag to indicate that it supports 64-bit DMA, so it should be fine, 
unless it lies of course (which we know that ATI SB600 chipset does, but 
I don't believe Intel is known to).

Could still be a DMA mapping bug that only shows up when IOMMU is used. 
However, AHCI is a pretty well tested driver..

> 
> dmesg with 2GB:

..

> 
> ahci 0000:00:1f.2: version 2.3
> ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
> ahci 0000:00:1f.2: nr_ports (6) and implemented port map (0xf) don't match
> ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0xf impl SATA 
> mode
> ahci 0000:00:1f.2: flags: 64bit ncq sntf led clo pmp pio slum part
> PCI: Setting latency timer of device 0000:00:1f.2 to 64
> scsi0 : ahci
> scsi1 : ahci
> scsi2 : ahci
> scsi3 : ahci
> ata1: SATA max UDMA/133 cmd 0xffffc20000334100 ctl 0x0000000000000000 
> bmdma 0x0000000000000000 irq 316
> ata2: SATA max UDMA/133 cmd 0xffffc20000334180 ctl 0x0000000000000000 
> bmdma 0x0000000000000000 irq 316
> ata3: SATA max UDMA/133 cmd 0xffffc20000334200 ctl 0x0000000000000000 
> bmdma 0x0000000000000000 irq 316
> ata4: SATA max UDMA/133 cmd 0xffffc20000334280 ctl 0x0000000000000000 
> bmdma 0x0000000000000000 irq 316

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-12-09 17:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2007-12-04 20:54 Bug: get EXT3-fs error Allocating block in system zone 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
2007-12-09 16:59         ` Marco Gatti
2007-12-07  7:11   ` Marco Gatti

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=475C2C02.70001@shaw.ca \
    --to=hancockr@shaw.ca \
    --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 \
    --cc=torvalds@linux-foundation.org \
    /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