[Sorry to reply to my own email thread] Srihari Vijayaraghavan <sriharivijayaraghavan@xxxxxxxxxxxx> wrote: ... > No problems. Here's the log of unworking kernel with IOMMU turned on. > Basically it goes on reseting the SATA ports throwing many errors (none are > present in 2.6.23 or on 2.6.24-rc with mem=3500M) for many minutes at which > point I do a power reset :-(. > > Also the log of the working kernel with IOMMU but with mem=3500M is also > attached for the record. It's basically the same above kernel just with the > added parameter. Gentlemen, This changeset has introduced a regression in 2.6.24-rc, such that my machine boots no more: http://www.kernel.org/hg/linux-2.6/rev/ddf8804136fb changeset: 72064:ddf8804136fb user: Andi Kleen <ak@xxxxxxx> date: Fri Oct 19 20:35:03 2007 +0200 files: arch/x86/kernel/pci-dma_64.c description: x86: enable iommu_merge by default [ tglx: arch/x86 adaptation ] Signed-off-by: Andi Kleen <ak@xxxxxxx> Signed-off-by: Ingo Molnar <mingo@xxxxxxx> Signed-off-by: Thomas Gleixner <tglx@xxxxxxxxxxxxx> committer: Thomas Gleixner <tglx@xxxxxxxxxxxxx> diff -r 8c8683cbdc05 -r ddf8804136fb arch/x86/kernel/pci-dma_64.c --- a/arch/x86/kernel/pci-dma_64.c Fri Oct 19 20:35:03 2007 +0200 +++ b/arch/x86/kernel/pci-dma_64.c Fri Oct 19 20:35:03 2007 +0200 @@ -11,7 +11,7 @@ #include <asm/iommu.h> #include <asm/calgary.h> -int iommu_merge __read_mostly = 0; +int iommu_merge __read_mostly = 1; EXPORT_SYMBOL(iommu_merge); dma_addr_t bad_dma_address __read_mostly; As a work-around, I can get it to boot with mem=3500M, but then it's ugly ;-) & I lose some valuable memory I have. Here's my email thread on linux-ide capturing the good & bad kernel behaviour for reference: http://marc.info/?t=119456213200005&r=1&w=2 Thanks Hari PS: Here's hoping for a kernel mem= parameter free bootable 2.6.24 ;-). Feel safe with award winning spam protection on Yahoo!7 Mail. www.yahoo.com.au/mail - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
