login
Header Space

 
 

Re: atl1 64-bit => 32-bit DMA borkage (reproducible, bisected)

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Alexey Dobriyan <adobriyan@...>
Cc: Luca Tettamanti <kronos.it@...>, Chris Snook <csnook@...>, Jeff Garzik <jeff@...>, Pekka Enberg <penberg@...>, Andrew Morton <akpm@...>, <linux-kernel@...>, <netdev@...>, Christoph Lameter <clameter@...>, <torvalds@...>
Date: Tuesday, May 6, 2008 - 12:02 pm

On Mon, 5 May 2008 01:15:07 +0400
Alexey Dobriyan <adobriyan@gmail.com> wrote:


I've tried all the stuff you mentioned above, and more, to prevent the
memory corruption, all to no avail.

I booted with mem=4000M and didn't hit the bug.  I diffed dmesg between
booting with mem=4000M and booting without it, and found that iommu
was being disabled when booting with full memory:

--- dmesg-4000.txt      2008-05-06 10:14:07.000000000 -0500
+++ dmesg-4096.txt      2008-05-06 10:09:19.000000000 -0500
@@ -1,5 +1,5 @@
 Linux version 2.6.26-rc1 (jcliburn@finch.hogchain.net) (gcc version 4.1.2 20070
925 (Red Hat 4.1.2-27)) #4 SMP Mon May 5 18:03:48 CDT 2008
-Command line: ro root=LABEL=/1 console=ttyS0,38400 console=tty0 slub_debug=FZPU mem=4000M
+Command line: ro root=LABEL=/1 console=ttyS0,38400 console=tty0 slub_debug=FZPU
[...]
+Looks like a VIA chipset. Disabling IOMMU. Override with iommu=allowed
[...]

So I then booted with iommu=allowed.  No errors.  Can't hit the bug to
save my life.

Why would disabling iommu cause the atl1 driver to write over poisoned
memory?

Alexey, can you please try booting with iommu=allowed and see if you
avoid the problem?

Thanks,
Jay
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
2.6.25-rc8-mm2, Andrew Morton, (Thu Apr 10, 11:33 pm)
BUG at __dentry_open [Was: 2.6.25-rc8-mm2], Jiri Slaby, (Mon Apr 14, 4:07 am)
2.6.25-rc8-mm2, , (Sat Apr 12, 5:41 am)
Re: 2.6.25-rc8-mm2: IP: [&lt;ffffffff802868f9&gt;] __kmalloc..., Christoph Lameter, (Mon Apr 14, 1:53 pm)
Re: 2.6.25-rc8-mm2: IP: [&lt;ffffffff802868f9&gt;] __kmalloc..., Christoph Lameter, (Mon Apr 14, 1:57 pm)
Re: 2.6.25-rc8-mm2: FIX kmalloc-2048 (was Re: 2.6.25-rc8-mm2..., Christoph Lameter, (Mon Apr 14, 4:05 pm)
atl1 64-bit =&gt; 32-bit DMA borkage (reproducible, bisected), Alexey Dobriyan, (Sat Apr 19, 10:45 am)
Re: atl1 64-bit => 32-bit DMA borkage (reproducible, bisected), Jay Cliburn, (Tue May 6, 12:02 pm)
Re: 2.6.25-rc8-mm2: IP: [&lt;ffffffff802868f9&gt;] __kmalloc..., Christoph Lameter, (Mon Apr 14, 2:00 pm)
[mm patch] select ATA_SFF, Adrian Bunk, (Sat Apr 12, 8:51 pm)
Re: 2.6.25-rc8-mm2, KAMEZAWA Hiroyuki, (Fri Apr 11, 5:57 am)
Re: 2.6.25-rc8-mm2, KAMEZAWA Hiroyuki, (Fri Apr 11, 6:23 am)
Re: 2.6.25-rc8-mm2, Pekka Enberg, (Fri Apr 11, 6:34 am)
Re: 2.6.25-rc8-mm2, KAMEZAWA Hiroyuki, (Fri Apr 11, 6:57 am)
Re: 2.6.25-rc8-mm2, KAMEZAWA Hiroyuki, (Fri Apr 11, 7:17 am)
Re: 2.6.25-rc8-mm2, KAMEZAWA Hiroyuki, (Fri Apr 11, 9:17 am)
Re: 2.6.25-rc8-mm2, Pekka Enberg, (Fri Apr 11, 10:24 am)
Re: 2.6.25-rc8-mm2, KAMEZAWA Hiroyuki, (Sun Apr 13, 11:13 pm)
Re: 2.6.25-rc8-mm2, Adrian Bunk, (Fri Apr 11, 9:40 am)
Re: 2.6.25-rc8-mm2, Andrew Morton, (Sat Apr 12, 12:22 am)
Re: 2.6.25-rc8-mm2, Aneesh Kumar K.V, (Sat Apr 12, 2:43 pm)
Re: 2.6.25-rc8-mm2, Michael Schmitz, (Sun Apr 13, 3:45 am)
Re: 2.6.25-rc8-mm2, Geert Uytterhoeven, (Sun Apr 13, 4:11 am)
Re: 2.6.25-rc8-mm2, , (Sat Apr 12, 1:53 am)
Re: 2.6.25-rc8-mm2, Andrew Morton, (Sat Apr 12, 2:07 am)
Re: 2.6.25-rc8-mm2: Observed problems: Not a detailed bug re..., Rafael J. Wysocki, (Tue Apr 15, 4:12 pm)
speck-geostationary