Tejun Heo wrote:
Robert Hancock wrote:
And you're quite right in your comment that we are often too quick to
blacklist hardware instead of looking into why it really is failing.
ACPI is one of those areas where we often just need to figure out how to
be bug-to-bug compatibile with what Windows is doing..
In the spirit of not blacklisting without looking deep into ACPI code,
can somebody familiar with ASL take a look at comment 11 of bug 9320?
http://bugzilla.kernel.org/show_bug.cgi?id=9320#c11
This is libata calling _GTM to find out how the BIOS configured the
device to determine cable type.
Thanks.
I suspect it's somewhat similar (though perhaps a different cause), the
code is trying to lookup a value (presumably register contents) in a
table using Match, gets a value that's not in the table (which makes
Match return the ONES value FFFFFFFF meaning not found) and so the
lookup of the corresponding output value with that index fails. We'd
need the full ASL dump to know exactly what's going on there.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@xxxxxxxxxxxxx
Home Page: http://www.roberthancock.com/
-
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
