© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Random comments:
The resource conflict _message_ is new in openSuse 11.0, not the conflict itself. If the conflict wasn't causing trouble in 10.3, I doubt it will in 11.0. According to comment #6, preventing the native SMBus driver to load didn't help Michele, which would confirm that the freeze isn't caused by the conflict.
I've looked at Richard machine's DSDT and it gets its temperature from a device at address 0x4c on the SMBus (presumably an LM90 or ADM1032 or compatible chip), from register 0x01. This means that you should really only use either ACPI or lm-sensors to get the temperature, but not both. Booting with acpi_enforce_
This DSDT is pretty confusing, BTW... Many things are declared twice, for example the RBYT and WBYT methods.
Another thing I've noticed is that the DSDT initializes the temperature value to 60 degrees C:
Which is the value reported by Richard. The RTMP method is supposed to overwrite it with a temperature value read from the thermal sensor chip, but I suspect that it doesn't happen. That would explain why the values reported by ACPI and sensors are different. I have no idea why RTMP fails to overwrite the value of LTMP though... The code looks OK to me (but then again I am no expert.)
But anyway, at this point we have no reason to believe that the problem is related to thermal management or ACPI, do we? This might as well be a problem with any other part of the kernel, or even outside the kernel. For example the X server could be responsible for the lockup. Does the lockup happen if you boot in runlevel 3 (no X server)?
It would be useful to find out where the freeze is happening, by enabling the magic SysRq mechanism and hitting SysRq+p and SysRq+t when the system is frozen. If we know where it freezes, this would at least give us something to start from.