Skip to contentSkip to conversation

Thinkpad R40 freezes after swsusp resume

DISCUSSION John M Flinchbaugh 3 participants 7 messages Feb 10, 2005 – Feb 16, 2005

lore
Share & tools
lore
#0 lore raw

I can suspend my R40 with swsusp, then boot it and resume fine most of the time.

I'd say nearly 50$ of the time though, the machine will freeze within 5 minutes of resuming.

SysRq doesn't work, no oops when in console mode, no network, no disk activity, just frozen. Occassionally, I've seen a line or 2 of pixels on my X screen get corrupted.

Here are some of the things I've tried adjusting:
pci=routeirq.
pci=noacpi (or whatever it is).
shutting down hotplug over suspend to disable USB. disabling cpudynd and CPU frequency scaling. ...and probably a few other things i'm forgetting. enabling lapic seemed to almost make it worse.

is any common hardware or subsystems on these machines known to not suspend and resume properly? i never see these freezes on a clean boot, and if the machine survives 10 minutes after a resume, i'll not see it freeze either. i've witnessed this with every kernel, since i got the machine in september (2.6.8.1, 2.6.9, 2.6.10, 2.6.11-rc3).

and finally, i know no one's had answers for me on this yet, so what can i do to locate the problem and debug this myself? is there a way to get past these lockups to at least get a call trace to see where i'm stuck?

thank you everyone.

Signature · 2 lines
John M Flinchbaugh
[email protected]
#1 lore raw

Hi!

Quoted 10 lines

I can suspend my R40 with swsusp, then boot it and resume fine most of the time.

I'd say nearly 50$ of the time though, the machine will freeze within 5 minutes of resuming.

SysRq doesn't work, no oops when in console mode, no network, no disk activity, just frozen. Occassionally, I've seen a line or 2 of pixels on my X screen get corrupted.

Quoted 7 lines

Here are some of the things I've tried adjusting:
pci=routeirq.
pci=noacpi (or whatever it is).
shutting down hotplug over suspend to disable USB. disabling cpudynd and CPU frequency scaling. ...and probably a few other things i'm forgetting. enabling lapic seemed to almost make it worse.

Try also acpi=off.
Pavel

Signature · 2 lines
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
#2 lore raw
Quoted 1 line · Pavel Machek

Try also acpi=off.

i was hoping for a test that's a bit more granular. might it be possible to disable suspect bits of the acpi code instead of all of it? i'm open to applying and testing patches.

disabling all of acpi for a week or 2 (sometimes my notebook will go 4 days of daily suspending and resuming without trouble, now) doesn't sound like fun. i like acpi events and information.

my latest test is to trim my suspend script. from earlier versions of the swsusp code, i had been disabling laptop-mode, turning swappiness up to 100%, saving the hwclock, etc. having taken all that out, i find it unnecessary anymore.

Signature · 2 lines
John M Flinchbaugh
[email protected]
#3 lore raw

Hi!

Quoted 5 lines
Quoted 1 line

Try also acpi=off.

i was hoping for a test that's a bit more granular. might it be possible to disable suspect bits of the acpi code instead of all of it? i'm open to applying and testing patches.

Well, you'd have to write that code, I'd guess.

And I do not think you can really turn off thermal managment once you enter ACPI mode.
Pavel

Signature · 2 lines
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
#4 lore raw
Quoted 11 lines · Pavel Machek
Quoted 6 lines
Quoted 1 line

Try also acpi=off.

i was hoping for a test that's a bit more granular. might it be possible to disable suspect bits of the acpi code instead of all of it?
i'm open to applying and testing patches.

Well, you'd have to write that code, I'd guess.
And I do not think you can really turn off thermal managment once you
enter ACPI mode.

I've gotten 2.6.11-rc4 to freeze after a swsusp, so I'm testing acpi=off now.

As Murphy's Law would have it, I usually get these lockups at inopportune times when I really don't want to have to punch the power button, like when I'm in a hurry trying to find something or during long-running network backups. It also does it when sitting idle, so this isn't a rule.

I've run most of a backup from an NFS mount to the local drive (for about 10 minutes), stopped it, swsusp, ran another backup, and it's looking fine so far.

To be sure that it's not going to freeze, I'd almost have to let it go for a week, though, because sometimes I had just gotten lucky and not seen the issue for upto 4 days at a time.

Assuming disabling ACPI causes my trouble to go away, what's my next step in debugging this issue? I'd hate to just leave it at "Don't use ACPI."

Thanks for your time.

Signature · 2 lines
John M Flinchbaugh
[email protected]
#5 lore raw
In reply to John M Flinchbaugh
Quoted 9 lines · John M Flinchbaugh

I can suspend my R40 with swsusp, then boot it and resume fine most of the time.

I'd say nearly 50$ of the time though, the machine will freeze within 5 minutes of resuming.

SysRq doesn't work, no oops when in console mode, no network, no disk=20 activity, just frozen. Occassionally, I've seen a line or 2 of=20 pixels on my X screen get corrupted.

Do you happen to use the madwifi drivers? If you are you might be affected by bad interaction from madwifi with laptop mode patches. This has been reported to ubuntu in
https://bugzilla.ubuntu.com/show_bug.cgi?id=6108

Unfortunatly, the only known fix up to now is to disable either madwifi oder laptop-mode. :(

I'm also affected by this bug, and find this very annoying. Please CC:
when replying.

Greetings,
Reinhard

#6 lore raw
Quoted 16 lines · Reinhard Tartler
Quoted 10 lines

I can suspend my R40 with swsusp, then boot it and resume fine most of
the time.
I'd say nearly 50$ of the time though, the machine will freeze within 5
minutes of resuming.
SysRq doesn't work, no oops when in console mode, no network, no disk
activity, just frozen. Occassionally, I've seen a line or 2 of pixels on my X screen get corrupted.

Do you happen to use the madwifi drivers? If you are you might be affected by bad interaction from madwifi with laptop mode patches. This
has been reported to ubuntu in
https://bugzilla.ubuntu.com/show_bug.cgi?id=6108

Quoted 3 lines

Unfortunatly, the only known fix up to now is to disable either madwifi
oder laptop-mode. :(

I use the ipw2100.sf.net drivers, and I've gotten the freeze without even having those modules loaded, so I doubt that's it.

I'm currently testing booting with acpi=off. While, I've not had a freeze yet (nearly 2 days), I may take your advice and test with laptop-mode disabled as well, since I could definitely tolerate the loss of laptop-mode better than the loss of my ACPI events and info.

Signature · 2 lines
John M Flinchbaugh
[email protected]