Rafael, I don't see what is wrong with failure log, do you? If only audit init number looks too big, did you try to disable it (audit)? < audit(1162401734.092:1): initialized --- > audit(18446744012389200479.076:1): initialized 289,290c291,292 < ata1: SATA max UDMA/100 cmd 0xFFFFC2000000C080 ctl 0xFFFFC2000000C08A bmdma 0xFFFFC2000000C000 irq 16 < ata2: SATA max UDMA/100 cmd 0xFFFFC2000000C0C0 ctl 0xFFFFC2000000C0CA bmdma 0xFFFFC2000000C008 irq 16 --- > ata1: SATA max UDMA/100 cmd 0xFFFFC20000020080 ctl 0xFFFFC2000002008A bmdma 0xFFFFC20000020000 irq 16 > ata2: SATA max UDMA/100 cmd 0xFFFFC200000200C0 ctl 0xFFFFC200000200CA bmdma 0xFFFFC20000020008 irq 16 Addresses for disk seem to be different too... Regards, Alex. Rafael J. Wysocki wrote: > Hi, > > On Wednesday, 1 November 2006 14:03, Alexey Starikovskiy wrote: >> Rafael, >> >> Is it possible to get any log from failed and normal boot? > > Attached are dmesg outputs for both cases. > > The good one is 2.6.19-rc3 with > http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/test/2.6.19/acpi-test-20060707-2.6.19-rc3.diff.gz > applied. > > The failing one is 2.6.19-rc3 with > http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/test/2.6.19/acpi-acpica-20061011-2.6.19-rc3.diff.gz > applied. > > Greetings, > Rafael > > - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
