Hello. I have consistent crashes when suspending for more than a few minutes. It doesn't matter if I click the power button, use "apm -S", "zzz" or close the lid with lidsuspend=1. Pressing the power button after it has been suspended for a short while works, but I get console messages saying, for example

wd0e: aborted command writing fsbn 5248 of 5248-5251 (wd0 bn 1562608; cn ...
wd0: soft error (corrected)

However, if I let the Zaurus sleep for 15 - 30 minutes, after pressing the power button the disk drive (green led) comes up, but the display remains black and the keyboard doesn't work. I need to do a reset.

Does anyone have any suggestion? Does it work for you?

By the way, I have a 3200 and an OpenBSD 3.9 snapshot. It also happened with 3.9-release and a prerelease snapshot.

Thank you,
Francisco

Same here on a 3000 with 3.9 snapshot. I've been leaving the Z running all the time.

I have only had the problem with suspending where it doesn't resume once. There is a seperate suspend issue where it won't resume after being charged if it has gone into a 'panic suspend' state due to low battery which may be resolved by resuming the unit a couple of times after plugging in the charger though.

The error that you receive is normal on the Zaurus and it just reflects that OpenBSD is writing the unflushed data that it needed to write but that was interrupted by the suspend sequence.

-Andy

I've also had the "panic suspend" issue on my 3000 where even after a charging the z wont turn on. eventually it did turn on after removing the battery, plugging/unplugging the power. I wish the z didn't lose charge so fast. I try to keep it plugged in when possible but it seems wrong that it would lose it's charge after a day of not being plugged in.

I would suggest cycling the unit at least once a month... full charge and let it run to panic suspend.

This helps to condition the battery. I do this and can reliably get 3 hours runtime (remember the hd is constantly active) and charge every 3 days or so if I'm using the unit infrequently.

-Andy

now in regards to a full charge... there's an orange led when the unit is charging, which is normal... my powerbook does the same. orange for charging, green for charged. there are times that apm will report the unit as 100% charged, but the light remains on. In fact, if I listened to apm's stats I'd probably never have a fully charged zaurus because it will report 100% charged after an hour or so when the light will actually remain orange for much longer - never timed it but 3-5 hours?

is this just my z or is it across the board?

Yes, I see that, too. Apm almost always tells me it's 100% charge. I've had the Zaurus off the charger for as long as an hour and apm tells me it's 90% I guess I get kickin' battery life.

right...except that it will take an hour go from from 100% to 90% and then 10 minutes to go from 75% to 0%

Yes, apm charge not 100% means the battery is almost empty

I get more than 3 h, and that would be good enough if I could suspend.
But I can't. I need to shutdown because it is faster to restart with clean
filesystems. I was wondering what could be different between my setup,
that crashes always on suspend, and the setup of some of you, that only
crashes from time to time.

Any idea?

Suspend was working VERY well for me until recently. I'm not sure if it was something that has changed in recentish snapshots or just the face I've been running on the "cool" apm setting.
I haven't been in a convenient place to record the ddb info though.

I'm reinstalling with the latest snapshot today to see if that helps.

Does anyone have some news about this crash ? or knows a way to avoid it (other than never suspending) ?

The two latests snapshots works worst on this issue and seems not to be able to resume after a suspend (the bug is systematic).

(my zaurus is a C3100)

I've got it working on my C3000, mostly. I'm using a recent snapshot (June 12). apmd is NOT running, and I use the power button (hold it in for 2s) to suspend. I haven't done extensive testing, but I remember having issues when running at 90mhz, but 208 has been working just fine.

http://marc.theaimsgroup.com/?l=openbsd-cv...82806831678&w=2

Looks like it's been fixed...

Yep, it seems fixed in the 3.9 stable. But it looks like there is a new bug introduced in snapshot.

However, hugs to the guy that fixed it

yes,
i've installed latest snapshot and the suspend bug is still there...
did someone find a proper method to suspend ?

mine for now is to boot qtopia then suspend.........

except from that i'm totally happy about OpenBSD on my Z ! keep up the good work!

The latest snapshot totally bails for me (booting bsd.rd). Looks like it may (and I don't know what I'm doing ) be related to recent disklabel work.

well,
i've just tried to suspend with my 4.0beta-slc3000 and :
-apm -S : does nothing (!!)
-zzz : error message = cannot connect to apmd
-power button : works! then i waited for 1 minute then i tried to switch on the Z and i 'd the same wd0 error messsage like you but it worked! right now i'm trying to suspend it for 1 hour and i'll see if it switchs on again

see you soon
(hope!)

ps: apm tells me "91% batt remaining" .... the zaurus is not power connected.

If apmd is not running the zzz command will not work. I haven't tried apmd with the snap I'm running, but after reinstalling (3.9 then updating to the latest snap) suspend is finally working for me again...

I had the same problem booting the 4.0 snap bsd.rd. I ended up going to 3.9 release. Guess I'll try 4.0 again now.

hello again
i woke up my 4.0 openbsd zaurus this morning and it sent me en error message then it felt into debug mode !!!
i found a "boot reboot" command to reboot, i didn't find a 'quit' command...

hi
yesterday night i started some compilation and i turned off the screen via this command:

wsconsctl display.backlight=0

this morning i could not find any way to resume the Zaurus... it ended up with hard battery removal...any idea?

I also run into issues of apm:
-- closing the lid (with the setting in /etc/sysctl.conf): fails to resume; screen remains dark; but it is surely on because Ctrl-Alt-BS will kill X.
-- pressing the power button to suspend: [EDITED: just tested again. it seems to work now. need more testing ... ]
-- It seems running apmd and suspending with "zzz" works fine so far, although it did fail a couple of times also.

About apm:
How can i check the exact percentage of battery power? i type apm and it keeps saying the battery is 100% all the time both with and without AC.

Thanks!

Did you reissue the following command?

wsconsctl display.backlight=100

do you mean i've to type that command each type i typed the =0 one ??? isn't it automatic as you type any key or use the stylus?

wsconsctl display.backlight=0 turns the LCD back light off. To turn the back light back on you'll have to issue the inverse command wsconsctl display.backlight=100. Pressing random keys or tapping the LCD screen with the stylus will not result in the LCD back light turning back on.

okay!
so that should be specified in that tip&tricks pages :

http://exit3.i-55.com/%7Exikon/zaurustipsandtricks.html
http://planetofidiots.com/zaurus/#afterboot

that makes sense, it sounds logical, but isn't very user friendly

Done.

Here is what i got more than once when the Z fails to resume:



It seems that resuming in X works better than in console. Maybe i am wrong.

Also does the close-lip-to-suspend thing involve both suspend and turning off the lcd?

What does your /etc/fstab look like? Have you enable the microdrives cache?

This is my /etc/fstab. Thanks!


And i have harddisk cache enabled, following the suggestions in http://exit3.i-55.com/%7Exikon/zaurustipsandtricks.html

well
it seems today i felt into a resume bug too......i suspend this morning (in X under fluxbox) and this afternoon it was impossible to resume............ i had to remove the battery...
i wonder if it could be linked to my old zbsdmod.o/zboot in my flash...i'm updating to see if it helps...

This is what mathemajikian told me today:


I am using 6 partitions following the advice here: http://www.planetofidiots.com/zaurus/#install

So there seem to be two solutions:
1) Use one big partitions for everything + one swap partition (or simply one partition with swapfile -- which one is better?)
2) Swap the internal MD with a hi-speed CF

Anyway i will install the system again in one big partition and see if the problem persists.

What's the output of the following two commands:

# fdisk wd0

# disklabel wd0

If you created the partitions outside the bounds of the disk, then you would be attempting to read beyond the disk and this could cause these errors. I would try and use the one big partition wd0a + swap. Remember not to change wd0c.

Also, I just noticed that you have softdep in your fstab. This will not work with the snapshot GENERIC kernel! In order to utilize softdep you'll have to rebuild the kernel from source with the following option:

option FFS_SOFTUPDATES

Here are the results of both:

Thanks. But I am not yet familiar with obsd, let alone compiling the kernel. So would it be possible for you to upload the new kernel somewhere? Thanks in advance!

ok for the softdep, but since i put noatime in /, now the boot process is much much longer: after the "/dev/rwd0a: file system is clean; not checking", the zaurus is doing something with the harddrive for a long time before the boot continue.....
what is happenning there???

EDITED:
after the long wait, i finally have this message:
/dev/rwd0j: Invalid signature in fsinfo block/dev/dwd0j: 74237 files, 887368 free (221842 clusters)

what does it mean??

It's compiled in GENERIC now, so you should be fine with softdep in your fstab:

it seems i went again into an mission impossible to resume ! ... even the charge light didn't lit... only way was to remove battery....

any clue about that ??

The suspend problem doesn't go away, and actually becomes even worse, since I reinstalled the system from the latest snapshots in one partition last night (i did absolutely nothing else apart from following the Afterboot suggestions religiously.

zzz suspend can be resumed sometimes, but fails sometimes as well;

closing lid to suspend fails to resume *100%* of the time.

Is it really that there is nothing broken in the apm, or i go wrong somewhere?

Suspend/resume is such a basic thing that must work out of the box for a healthy distro, isn't it?

Now i am really confused about what to do with the setup ...

Also can someone kindly tell me explicitly how to use apm or other means to show accurate remaining power?

I've tried all the options possible with apm and only have 100% or 180 minutes all the time. Even though the battery is actually running low (when i boot into cacko and check).

Okay, just to be more precise to the symptoms:

When suspending in console (both zzz and closing the lid), resume will produce a very short white flash on the screen, followed by screen black out. Typing "wsconsctl display.backlight=100" doesn't work at all.
After waiting a while i see the green light on, which i guess is the system trying desparately to resume the microdrive, but keeps failing (sometimes i see the error message of failing to reset wdc0 blah, but most of the time just everything in the dark).

When suspending in X, resume usually can bring the screen back, but then the system freezes. After a while the screen goes dark and the green LED turns on, which probably also indicate the harddrive reset failure ...


***

So here i would really appreciate clear answers to the questions ( the more i read the documentation and the tips pages, the more i seem to get confused, just because things do not work as described )
Sorry for getting a bit paranoid now because i am beginning to get a bit frustrated after spending two weeks without getting a stable enough system working.

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)?

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

3) Should writecacheenable be enabled or not?

4) About swapfile: is it fine to set up swapfile after installing *everything* (including all the distribution sets) in one big partition?

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 ...

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



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



Your choice.



I don't see any problems with this, but thats just me.



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.

The apm battery monitor doesn't work all that great. Here's a list of known problems which are currently being worked on:

* Repair pcmcia issues that are causing "white-out" problems with some devices.
* Fix the odd suspend crashing bugs and RTC skew.
* C860/C1000 support.
* Support the I2C GPIO controller (C3100 and C3200) using the machine-independent i2c code.
* Internal flash memory support as a sd(4) device.
* Fix battery drain during suspend.
* Fix remaining issues in SDIO support.

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?

Thanks again.



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



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




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

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

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