2.6.19-rc <-> ThinkPads, summary

From: Adrian Bunk
Date: Fri Nov 03 2006 - 22:49:39 EST


As far as I can see, the 2.6.19-rc ThinkPad situation is still
confusing and we don't even know how many different bugs we are
chasing...

Below is all the information I have found, plus some questions for the
four people who reported problems that might hopefully bring us nearer
to solutions.


Michael S. Tsirkin:
- ThinkPad T60 not coming out of suspend to RAM
- broken by commit cf4c6a2f27f5db810b69dcb1da7f194489e8ff88
("i386: Factor out common io apic routing entry access")
- question: Did the post -rc4 arch/i386/kernel/io_apic.c changes fix it?


Ernst Herzberg:
- ThinkPad R50p: boot fail with (lapic && on_battery)
- kernel compiled without cardbus support works
- question: Does reverting the bisected
commit 1fbbac4bcb03033d325c71fc7273aa0b9c1d9a03
("serial_cs: convert multi-port table to quirk table")
fix the problem?
- question: Does reverting commit cf4c6a2f27f5db810b69dcb1da7f194489e8ff88
("i386: Factor out common io apic routing entry access") help?
- question: If yes, did the post -rc4 arch/i386/kernel/io_apic.c changes
fix it?


Hugh Dickins:
- ThinkPad T43p
- booting with "noapic nolapic" didn't make any difference
- reverting commit cf4c6a2f27f5db810b69dcb1da7f194489e8ff88
("i386: Factor out common io apic routing entry access") didn't help
- question: Was your bisecting successful?


Martin Lorenz:
- ThinkPad X60: lose ACPI events after suspend/resume
not every time, but roughly 3 out of 4 times
- question: Does reverting commit cf4c6a2f27f5db810b69dcb1da7f194489e8ff88
("i386: Factor out common io apic routing entry access")
in -rc4 help?
- question: If yes, did the post -rc4 arch/i386/kernel/io_apic.c changes
fix it?


cu
Adrian

--

"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/