Suspend Crashes, Does suspend work for you on OpenBSD? Options

[jpmatrix]

5) And of course, what is the source of the suspend trouble? Frankly, I have already tested a few dozen times (believe me) trying to exhaust all the possibilities: with/without memory cards mounted, with/without cards inserted, with/without AC, with/without disk cache, with/without turning on mechdep.lidsuspend in /etc/sysctl.conf ...

well well,
i only use the button to suspend and resume (as i'm compiling a lot under the console), and it seems i've less troubles than you... by the way which zaurus model do you have ?

[ZDevil]

well well,
i only use the button to suspend and resume (as i'm compiling a lot under the console), and it seems i've less troubles than you... by the way which zaurus model do you have ?

Mine is 3200.
Do you mean using the On/Off button to suspend only? I cannot resume when suspending this way.
Which version (snapshots or official release or your own build) do you use?
How do you partition the space?
What are your settings with respect to the harddrive(/etc/fstab, /etc/sysctl.conf, /etc/rc.local. etc)?
Sorry for asking so many questions. I tried mathemajikan's advice but the same story.
How can i use a machine which cannot suspend and resume properly?

[ZDevil]

Thanks again.

1) Which version is actually more preferred? The snapshots (which I've been trying to get working but always got errors) or the "official" releases (from the 4.1 dir)?

Releases are generally preferred. Snapshots = -current which is the bleeding edge, and as stated before there can be a lot of bleeding involved!

But iirc somewhere in the documentatiopn says snapshots are better ...

2) What should I put in /etc/fstab about wd0 if I install the snaphot in one big partition?

If your swap file is on this partition then you can't put in softdep. Other than that you should be fine.

I only add noatime to wd0 and not softdep. Didn't notice anything different.

Try this:
use zzz -z suspend and see if it still fails to resume, if so then try zzz -S standby and see what happens.
zzz -z suspend puts the Z in a deep sleep whereas zzz -S standby puts the Z in a light sleep.

If that doesn't work then use shutdown -hp now until the problem is corrected. If you can't wait then convert back to a penguin distribution.

Tried both zzz -z suspend and zzz -S standby. Resume still fails.

[jpmatrix]

well well,
i only use the button to suspend and resume (as i'm compiling a lot under the console), and it seems i've less troubles than you... by the way which zaurus model do you have ?

Mine is 3200.
Do you mean using the On/Off button to suspend only? I cannot resume when suspending this way.
Which version (snapshots or official release or your own build) do you use?
How do you partition the space?
What are your settings with respect to the harddrive(/etc/fstab, /etc/sysctl.conf, /etc/rc.local. etc)?
Sorry for asking so many questions. I tried mathemajikan's advice but the same story.
How can i use a machine which cannot suspend and resume properly?

yes i always suspend using the on/off button. most of the times it works well, although i had some strange resume problems like you some times : same wd0 errors, or resume flashing the screen...
i think developpers will find what is happenning bad, i remember on my initial openbsd installation years ago suspend/resume was not working at all !! (see firsts messages of this post so let's wait, report and see

my partition layout is from pdaxii13 install process, so 2GB/128MB/2GB, but i only use the first partition for openbsd which i cut into 1.8MB BSD and 0.2MB for swap. however it is not a very good layout because my bsd partition appears to be too small...

in sysctl.conf i didn't put suspend on lit.

i cannot tell you more because i haven't my Z with me : i let it home compiling kdepim and it was compiling mysql when i left

hope this helps
JP

[ZDevil]

Thanks. Now I will reinstall the whole thing with the 4.1 release version and see if things get any better...

[jpmatrix]

well well,
i think we still have some resume troubles: this morning i hit the ON button, then the screen resume with hard drive error messages like this one :

wdc0 channel 0: reset failed for drive 0

wd0a: device timeout reading fsbn 1595200 of 1595200-0 (wd0 bn 1595201; cn 1582 tn 8 sn 41), retrying

wdc0:0:0: not ready,st=0x88<BSY,DRQ>, err=0x00

and the harddrive green light stays on.........


i'll google search for this messages

[ZDevil]

well well,
i think we still have some resume troubles: this morning i hit the ON button, then the screen resume with hard drive error messages like this one :

wdc0 channel 0: reset failed for drive 0

wd0a: device timeout reading fsbn 1595200 of 1595200-0 (wd0 bn 1595201; cn 1582 tn 8 sn 41), retrying

wdc0:0:0: not ready,st=0x88<BSY,DRQ>, err=0x00

and the harddrive green light stays on.........


i'll google search for this messages

Hey, this is exactly what i've run into almost all the time! So i am not the only one...
The constantly lit green light seems to indicate that the system is trying desparately to get the harddrive resumed, but keep failing ...
So now i am quite sure that there is something wrong with apm in the builds.
Yet I've installed the 4.1 release version. It seems zzz works again. Perhaps the release version is more stable? Will test further.
One difference i notice in the 4.1 release build: the green LED is always on even though the hard drive is not spinning.
Haven't tried "lidsuspend", which doesn't seem to work at all, i'm afraid.
(But see my next post below... )

This post has been edited by ZDevil: May 12 2007, 04:20 AM

[jpmatrix]

the release version seems to be rather old on
ftp://ftp.openbsd.org/pub/OpenBSD/4.1/zaurus : march 2007

latest snapshot is may 08

i wonder if i wait for the next snapshot...

[mathemajikian]

the release version seems to be rather old on
ftp://ftp.openbsd.org/pub/OpenBSD/4.1/zaurus  : march 2007

latest snapshot is may 08

i wonder if i wait for the next snapshot...

or better yet why not update your sources and rebuild the kernel and user world? Then you wont have to wait for the next snapshot.

[ZDevil]

the release version seems to be rather old on
ftp://ftp.openbsd.org/pub/OpenBSD/4.1/zaurus  : march 2007

latest snapshot is may 08

i wonder if i wait for the next snapshot...

True. But interestingly the release version does seem more stable than the snapshots: it is my very first time that i get zzz, lidsuspend and the power off button ALL working!
Still let me see if things are really stable during the weekend.

[gen2]

To add another data point here, these errors

CODE

wdc0:0:0:  not ready, st = 0x88<BSD,DRQ>, err = 0x00
wdc0 channel 0: reset failed for drive 0
wd0f : device timeout reading fsbn 156672 of 156672-0 (wd0 bn 7791264 cn 7729 tn 6 sn 54)

are not exclusive to the 6 partition setup. I don't know the precise sequence of commands which wake the drive and start addressing the hardware, but I'd like to know if multiple partitions is truly the issue...seems like something else changed which has lowered a threshold somewhere.

Problem is persistent since at least 3.8, however I never saw any errors of any kind on 4.0, with a 6 partition setup. Smells like beta buglets...

Discussion of the issue dates back at least here:
http://archive.netbsd.se/?ml=openbsd-arm&a=2005-12&t=1551843

I get this using todays snapshot, one / partition and one swap, no config edits of any kind anywhere after booting (other than adding apmd):

CODE

wd0a: aborted command reading fsbn 5397260 of 5397260-0 (wd0 bn 5397323; cn 5354 tn 7 sn 50), retrying
wd0: soft error corrected

However it seems to work.

I get this using todays snapshot, using the 6 partition setup, no config edits of any kind anywhere after booting (other than adding apmd):

CODE

wd0a: aborted command reading fsbn 4982464 of 4982464-0 (wd0 bn 6002560; cn 5954 tn 14 sn 46), retrying
wd0: soft error corrected

And this too seems to work. zzz -S is causing sleep, and it wakes up, gives that error, but works.

Investigation continues...

[mathemajikian]

True. But interestingly the release version does seem more stable than the snapshots: it is my very first time that i get zzz, lidsuspend and the power off button ALL working! 
Still let me see if things are really stable during the weekend.

Last night I suspended my Z from within X using the lidsuspend option and when I resumed the device this morning the only problem was that the back light failed to turn back on. I saw a half second white flash on the screen, as if it was attempting to turn on, then a blank/black screen. I ssh'd into the Zaurus and issued wsconsctl display.back light=100 and everything returned to normal. I also used lidsuspend outside of X and got similar results. (The back light failed to turn back on) However, if I used the power on/off button in X or from the console the back light never failed to turn back on. So there is an issue with lidsuspend, but it dosn't result in complete catastrophic device lockup. Though out the day I've suspended and resumed the device via the on/off button and lidsuspend multiple times and never once had the Z lock up or produce the error you describe below:

wdc0 channel 0: reset failed for drive 0
wd0a: device timeout reading fsbn 1595200 of 1595200-0 (wd0 bn 1595201; cn 1582 tn 8 sn 41), retrying
wdc0:0:0: not ready,st=0x88<BSY,DRQ>, err=0x00.

Finally, in regards to your battery status concerns:

From the apmd manual

 
            -t seconds
            apmd periodically polls the APM driver for the current power
            state.  If the battery charge level changes substantially or the
            external power status changes, the new status is logged.  The
            polling rate defaults to once per 10 minutes, but may be speci-
            fied using the -t command-line flag.

Therefore to get better battery status reports add the following to rc.conf.local

apmd_flags="-t 300"

This changes the polling rate to once every 5 minutes instead of once every 10 minutes.

You might also want to check out: http://ports.openbsd.nu/x11/asapm

[mathemajikian]

CODE

wd0a: aborted command reading fsbn 5397260 of 5397260-0 (wd0 bn 5397323; cn 5354 tn 7 sn 50), retrying
wd0: soft error corrected

This is normal. If you don't want to see these messages then redirect the output.

[gen2]

CODE

wd0a: aborted command reading fsbn 5397260 of 5397260-0 (wd0 bn 5397323; cn 5354 tn 7 sn 50), retrying
wd0: soft error corrected

This is normal. If you don't want to see these messages then redirect the output.

Perhaps normal for 4.1, I never saw them on 4.0.

[mathemajikian]

So there is an issue with lidsuspend, but it dosn't result in complete catastrophic device lockup.

Just noticed the following from 3.9 changes located here: http://www.openbsd.org/plus39.html

On Zaurus, allow sysctl machdep.lidsuspend=1 to cause suspend on screen closure. Opening does not yet wake it up though.

The Z wakes up it just fails to turn the back light back on.