← previous next →
Pages: [1] 2 3 ... 5

Author Topic: Suspend Crashes  (Read 70250 times)

fquindos

  • Newbie
  • *
  • Posts: 7
    • View Profile
Suspend Crashes
« on: May 20, 2006, 03:20:15 pm »
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
Logged

TronDD

  • Jr. Member
  • **
  • Posts: 55
    • View Profile
Suspend Crashes
« Reply #1 on: May 20, 2006, 08:36:23 pm »
Same here on a 3000 with 3.9 snapshot.  I've been leaving the Z running all the time.
Logged

iamasmith

  • Hero Member
  • *****
  • Posts: 1248
    • View Profile
Suspend Crashes
« Reply #2 on: May 21, 2006, 03:24:54 pm »
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
Logged
OpenBSD 4.2 -current on full 4Gb of SL-C3000
Microdrive replaced with 4Gb SanDisk Extreme III card

Sequethin

  • Jr. Member
  • **
  • Posts: 72
    • View Profile
Suspend Crashes
« Reply #3 on: May 24, 2006, 02:28:50 pm »
Quote
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
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127986\"][{POST_SNAPBACK}][/a][/div]


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

iamasmith

  • Hero Member
  • *****
  • Posts: 1248
    • View Profile
Suspend Crashes
« Reply #4 on: May 24, 2006, 04:44:50 pm »
Quote
Quote
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
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127986\"][{POST_SNAPBACK}][/a][/div]


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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128320\"][{POST_SNAPBACK}][/a][/div]

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
Logged
OpenBSD 4.2 -current on full 4Gb of SL-C3000
Microdrive replaced with 4Gb SanDisk Extreme III card

Sequethin

  • Jr. Member
  • **
  • Posts: 72
    • View Profile
Suspend Crashes
« Reply #5 on: May 25, 2006, 03:33:47 pm »
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?
Logged

TronDD

  • Jr. Member
  • **
  • Posts: 55
    • View Profile
Suspend Crashes
« Reply #6 on: May 25, 2006, 05:09:20 pm »
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.
Logged

Sequethin

  • Jr. Member
  • **
  • Posts: 72
    • View Profile
Suspend Crashes
« Reply #7 on: May 26, 2006, 11:26:36 am »
Quote
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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128436\"][{POST_SNAPBACK}][/a][/div]


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

fquindos

  • Newbie
  • *
  • Posts: 7
    • View Profile
Suspend Crashes
« Reply #8 on: May 26, 2006, 11:56:01 am »
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?

Quote
Quote
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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128436\"][{POST_SNAPBACK}][/a][/div]


right...except that it will take an hour go from from 100% to 90% and then 10 minutes to go from 75% to 0%  
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128499\"][{POST_SNAPBACK}][/a][/div]
Logged

ddpbsd

  • Newbie
  • *
  • Posts: 7
    • View Profile
Suspend Crashes
« Reply #9 on: May 27, 2006, 11:54:01 am »
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.
Logged

sylvain

  • Newbie
  • *
  • Posts: 17
    • View Profile
Suspend Crashes
« Reply #10 on: June 16, 2006, 12:49:20 pm »
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)
Logged

ddpbsd

  • Newbie
  • *
  • Posts: 7
    • View Profile
Suspend Crashes
« Reply #11 on: June 20, 2006, 08:31:33 am »
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.
Logged

ddpbsd

  • Newbie
  • *
  • Posts: 7
    • View Profile
Suspend Crashes
« Reply #12 on: June 20, 2006, 03:12:29 pm »
Logged

sylvain

  • Newbie
  • *
  • Posts: 17
    • View Profile
Suspend Crashes
« Reply #13 on: June 21, 2006, 01:45:46 pm »
Quote
http://marc.theaimsgroup.com/?l=openbsd-cv...82806831678&w=2

Looks like it's been fixed...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=132074\"][{POST_SNAPBACK}][/a][/div]
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
Logged

jpmatrix

  • Hero Member
  • *****
  • Posts: 1014
    • View Profile
    • http://matrixmen.free.fr
Suspend Crashes
« Reply #14 on: October 19, 2006, 08:53:26 am »
Quote
Yep, it seems fixed in the 3.9 stable. But it looks like there is a new bug introduced in snapshot.


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!
Logged
**Fujitsu U1010 !!!  
**ex-Zaurus SL-C3000 owner with Debian kernel 2.6.24-yonggun
Pages: [1] 2 3 ... 5
← previous next →