>> exregion-0185 [36] ex_system_memory_space: system_memory 0
>(32 width) Address=0000000023FDFFC0
>> exregion-0185 [36] ex_system_memory_space: system_memory 1
>(32 width) Address=0000000023FDFFC0
>> exregion-0290 [36] ex_system_io_space_han: system_iO 1 (8
>width) Address=00000000000000B2
>>
>> repeated endlessly.
Hmm.. interesting. This looks like same error with TP600X.
>
>This sounds like the problem Daniel had on his Samsung P35 recently.
>He could fix it by getting rid of some asus_unhide_smbus stuff or the
>otherway around, adding asus_unhide_smbus quirks in the S3 resume code.
>
>This thread was recently posted on lkml:
>Re: [patch] smbus unhiding kills thermal management
>
>Here are some more details, for me that sounds related...:
>https://bugzilla.novell.com/show_bug.cgi?id=173420
>
But this Samsung P35 don't have _GLK. So, I think TP 600x has
a different problem with Samsung P35.
Actually, Sanjoy has a workaround to solve TP 600X S3 issue.
What we need to do is to come up with a clean patch.
It is on to-do list.
Thanks,
Luming
[Trimmed lists that seemed unrelated: [email protected],
[email protected], [email protected],
[email protected], [email protected]]
> But this Samsung P35 don't have _GLK. So, I think TP 600x has
> a different problem with Samsung P35.
You're right. I tried 2.6.16.18, which has the smbus patch, but it
didn't help the resume. I need to test more whether it helps the fan,
but I doubt it will.
2.6.17-rc4 (with vanilla DSDT) does strange things to the fan. At
boot, the fan is often on. The trip point is 37 C (the DSDT default)
and temperature, say, 40 C. That's fine and the fan should be on.
But if I set the trip point to 45 C and the poll interval to 100
seconds, the fan remains on. I have to set the trip point and polling
interval a second time for the fan to turn off. With 2.6.16-rc5, it
would turn off after the first setting.
Also, and I need to check which kernel it is (either 2.6.16.18 or
2.6.17-rc4), during S3 sleep, the right speaker made a quiet hiss. I
imagine that will run down the battery pretty quickly. It's a new
behavior since 2.6.16-rc5.
-Sanjoy
`Never underestimate the evil of which men of power are capable.'
--Bertrand Russell, _War Crimes in Vietnam_, chapter 1.