Messages in this thread | | | Date | Thu, 4 Mar 2004 09:10:32 +0100 | From | Jurriaan <> | Subject | Re: 2.6.3-mm4 / 2.5 Gb memory / sym53c8xx_2 won't boot |
| |
From: Andrew Morton <akpm@osdl.org> Date: Wed, Mar 03, 2004 at 03:38:30PM -0800 > Jurriaan <thunder7@xs4all.nl> wrote: > > > > > Could you test Linus's current tree? The first link at > > > http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/. > > > > > > If this bug hasn't hit Linus's tree yet, it will soon do so... > > > > > It probably will, since it's not in Linus's tree as of > > > > cset-20040303_0509.txt > > > > ie 2.6.4-rc1-mm1 + cset-20040303_0509 does boot with > > You meant 2.6.4-rc1, I assume? > > > CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1, and 2.6.3-mm4 doesn't. > > I continue to be stumped. Could you please test a Linus tree, plus > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.4-rc1/2.6.4-rc1-mm2/broken-out/bk-scsi.patch > > and > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.4-rc1/2.6.4-rc1-mm2/broken-out/dma_sync_for_device-cpu.patch > I'm now stumped also. I tested
2.6.4-rc2 CONFIG.*DMA.*MODE=1: ok 2.6.4-rc2+bk-scsi CONFIG.*DMA.*MODE=1: ok 2.6.4-rc2+bk-scsi+dma_sync CONFIG.*DMA.*MODE=1: ok
then I recompiled a fresh 2.6.3-mm4 kernel from source with CONFIG.*DMA.*MODE=1, and it booted also.
So it appears to (have) be(en) a Heisenbug. It was there, when I recompiled, it was gone.
Oh well, Jurriaan -- You aren't going to do anything about it then? Of course I am. What? I'm going to ignore it. David Eddings - The Sapphire Rose Debian (Unstable) GNU/Linux 2.6.3-mm4 3940 bogomips 1.91 0.84 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |