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

Message-id: <475C2C02.70001@shaw.ca>
Date:	Sun, 09 Dec 2007 11:55:14 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	Marco Gatti <marco@...noinflames.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	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

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@...pamshaw.ca
Home Page: http://www.roberthancock.com/

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