On Fri, 19 Oct 2007, Luca Capello wrote: > I tested 2.6.23.1 + 0.18-20071013, oops still there. Should I test it > with the latest linux-acpi-2.6 git tree, also? I don't think it's > necessary, but I can do it in case (but please read below).
It is probably not liking something in 2.6.23. I will test that and get back to you as soon as I have an answer (might take a few days). > Sorry, I'm quite lost with the git tree: in release/ there's nothing > about the latest linux-acpi-2.6 tree, what I can see is the different That tree is just for thinkpad-acpi, it usually has nothing related to other linux-acpi changes, unless they actually are required for something thinkpad-acpi needs to do. > Is it OK to wait to upgrade the BIOS until the bug has been fixed? > Because if the bug won't be present anymore with the new BIOS, we > don't have a way to be sure it's fixed. Sure, it is OK to wait to upgrade the BIOS. As I said, I am certain there is a driver bug somewhere, regardless of any possible BIOS problems. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
