On 6/24/09, Frédéric Boiteux <[email protected]> wrote: > Le Wed, 24 Jun 2009 10:55:00 +0100, > Alan Jenkins <[email protected]> a écrit : > >> That would make sense. The next post says it should be fixed in >> 2.6.30 without the option though. >> >> <http://www.mail-archive.com/debian-eeepc-devel%40lists.alioth.debian.org/msg01759.html> > > I've tried, but the proposed workaround doesn't work here :-( > I've booted with 'initcall_debug' option to have some more messages, > look at dmesg's file joined to this e-mail.
Weird. You said earlier that acpi_enforce_resources=strict solved your problem on 2.6.29, so this looks like a regression in 2.6.30. [ 0.000000] Kernel command line: root=LABEL=racine ro vga=788 acpi_enforce_resources=strict init=/sbin/bootchartd initcall_debug [ 11.795501] i801_smbus 0000:00:1f.3: PCI INT B -> GSI 19 (level, low) -> IRQ 19 The point of acpi_enforce_resources=strict was to prevent drivers like i801_smbus binding to devices already handled by an ACPI BIOS. It was this conflict that was believed to cause the delay. What we want to see, which you should see on 2.6.29 with the "strict" boot option, is something like this: [ 0.881441] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 0.881441] ACPI: I/O resource 0000:00:1f.3 [0x400-0x41f] conflicts with ACPI region SMRG [0x400-0x40f] [ 0.881441] ACPI: Device needs an ACPI driver [ 0.881441] i801_smbus: probe of 0000:00:1f.3 failed with error -16 As a workaround / sanity check, can you avoid the delay on 2.6.30 if you blacklist the i801_smbus module? Thanks Alan _______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
