soft errors on wakeup

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

soft errors on wakeup

J. Hart
I have noticed the occasional soft error from the hard drive on waking
up after a long suspend.  I have also noticed that after such a suspend,
the Zaurus occasionally, but not always, thinks the hard drive has been
improperly dismounted.

Just now, I have experienced an unrecoverable hard drive corruption
resulting in a kernel panic on booting up.  I have had to completely
reformat it, reinstall OpenBSD, and reload the hard drive.  The hard
drive itself appears to be functioning properly when I test it.  This is
the first time I have encountered an unrecoverable corruption of this
nature.

Any ideas would be much appreciated.

J. Hart

Reply | Threaded
Open this post in threaded view
|

Re: soft errors on wakeup

Sam Hart-2
On 8 Dec 2005, at 13:30, J. Hart wrote:

> I have noticed the occasional soft error from the hard drive on  
> waking up after a long suspend.

I consistently get the same thing on the console, when running X it  
must mask the messages.

> I have also noticed that after such a suspend, the Zaurus  
> occasionally, but not always, thinks the hard drive has been  
> improperly dismounted.

I haven't noticed that

> Just now, I have experienced an unrecoverable hard drive corruption  
> resulting in a kernel panic on booting up.

I haven't had that happen to me

> I have had to completely reformat it, reinstall OpenBSD, and reload  
> the hard drive.  The hard drive itself appears to be functioning  
> properly when I test it.  This is the first time I have encountered  
> an unrecoverable corruption of this nature.

I haven't had that happen to me either

> Any ideas would be much appreciated.

you could include a dmesg

I wonder ( but I have no idea, ) if others don't get the same thing  
on the console wether it might be a problem with HD geometry.

Anyone ?


S a m

Reply | Threaded
Open this post in threaded view
|

Re: soft errors on wakeup

Simon Ironside-2
Sam Hart wrote:
> On 8 Dec 2005, at 13:30, J. Hart wrote:
>
>> I have noticed the occasional soft error from the hard drive on  
>> waking up after a long suspend.
>
> I consistently get the same thing on the console, when running X it  
> must mask the messages.

Same thing here, when running X too if I monitor console messages in Eterm.

>> Just now, I have experienced an unrecoverable hard drive corruption  
>> resulting in a kernel panic on booting up.
>
> I haven't had that happen to me

Not yet for me either.

> you could include a dmesg
>
> I wonder ( but I have no idea, ) if others don't get the same thing  on
> the console wether it might be a problem with HD geometry.
>
> Anyone ?

What are you after? wd0 bits of dmesg? Mine reads:

wdc0 at pcmcia0 function 0 "HITACHI, microdrive" port 0x0/16: irq 138
wd0 at wdc0 channel 0 drive 0: <HMS360604D5CF00>
wd0: 32-sector PIO, LBA, 3906MB, 7999488 sectors
wd0(wdc0:0:0): using BIOS timings

And I do get the soft errors after resuming from almost every suspend.

Cheers,
Simon

Reply | Threaded
Open this post in threaded view
|

Re: soft errors on wakeup

Sam Hart-2
On 12 Dec 2005, at 10:19, Simon Ironside wrote:

> Sam Hart wrote:
>> On 8 Dec 2005, at 13:30, J. Hart wrote:
>>> I have noticed the occasional soft error from the hard drive on  
>>> waking up after a long suspend.
>> I consistently get the same thing on the console, when running X  
>> it  must mask the messages.
>
> Same thing here, when running X too if I monitor console messages  
> in Eterm.

yeah, I thought as much, I just hadn't ever checked

>> you could include a dmesg
>> I wonder ( but I have no idea, ) if others don't get the same  
>> thing  on the console wether it might be a problem with HD geometry.
>> Anyone ?
> What are you after? wd0 bits of dmesg? Mine reads:
> wdc0 at pcmcia0 function 0 "HITACHI, microdrive" port 0x0/16: irq 138
> wd0 at wdc0 channel 0 drive 0: <HMS360604D5CF00>
> wd0: 32-sector PIO, LBA, 3906MB, 7999488 sectors
> wd0(wdc0:0:0): using BIOS timings

for straight diagnosis a full dmesg is generally a good idea ( though  
I doubt they differ greatly from zaurus to zaurus but you never know )

I was actually thinking about the actual layout set up by fdisk(8)  
for the start and endpoints etc.

i.e.

# fdisk wd0

and obviously checking /etc/fstab against the output of mount(8) and  
df(1)

> And I do get the soft errors after resuming from almost every suspend.

as do I.

With them being soft errors I have not worried too much ( though  
there is clearly a problem, )
the only other time I have seen this was with a HD I installed in a  
laptop, it wasn't long before the HD became unusable,
or rather the HD was on it's way out and the soft errors being  
reported were the beginning of the end.

As I said, I don't think it is THAT severe, but it is a problem.


S a m

Reply | Threaded
Open this post in threaded view
|

Re: soft errors on wakeup

Simon Ironside-2
Sam Hart wrote:

> for straight diagnosis a full dmesg is generally a good idea ( though  I
> doubt they differ greatly from zaurus to zaurus but you never know )

Ok - mine as at the end of the message.

> I was actually thinking about the actual layout set up by fdisk(8)  for
> the start and endpoints etc.
>
> i.e.
>
> # fdisk wd0
Disk: wd0       geometry: 7936/16/63 [7999488 Sectors]
Offset: 0       Signature: 0xAA55
          Starting       Ending       LBA Info:
  #: id    C   H  S -    C   H  S [       start:      size   ]
------------------------------------------------------------------------
  0: 00    0   0  0 -    0   0  0 [           0:           0 ] unused
  1: 00    0   0  0 -    0   0  0 [           0:           0 ] unused
  2: 00    0   0  0 -    0   0  0 [           0:           0 ] unused
*3: A6    0   1  1 - 7935  15 63 [          63:     7999425 ] OpenBSD

> and obviously checking /etc/fstab against the output of mount(8) and  df(1)

Mine is very straight forward, I use the whole disk and have everything
in one / partition.

# mount
/dev/wd0a on / type ffs (local)
# df
Filesystem  512-blocks      Used     Avail Capacity  Mounted on
/dev/wd0a      7612188   3862736   3368844    53%    /
# cat /etc/fstab
/dev/wd0a / ffs rw 1 1

Cheers,
Simon

# dmesg
OpenBSD 3.8 (GENERIC) #149: Sat Sep 10 17:23:43 MDT 2005
     [hidden email]:/usr/src/sys/arch/zaurus/compile/GENERIC
real mem  = 67108864 (65536K)
avail mem = 53383168 (52132K)
using 844 buffers containing 3457024 bytes (3376K) of memory
mainbus0 (root)
cpu0 at mainbus0: PXA27x rev 7 (XScale core)
cpu0: DC enabled IC enabled WB enabled LABT branch prediction enabled
cpu0: 32KB(32b/l,32way) I-cache, 32KB(32b/l,32way) wr-back-lock D-cache
pxaip0 at mainbus0: CPU clock = 415.995 MHz
pxaintc0 at pxaip0 addr 0x40d00000: Interrupt Controller
pxagpio0 at pxaip0 addr 0x40e00000: GPIO Controller
pxadmac0 at pxaip0 addr 0x40000000 intr 25: DMA Controller
saost0 at pxaip0 addr 0x40a00000
saost0: SA-11x0 OS Timer
com0 at pxaip0 addr 0x40100000 intr 22: pxa2x0, 32 byte fifo
com1 at pxaip0 addr 0x40200000 intr 21: pxa2x0, 32 byte fifo
com2 at pxaip0 addr 0x40700000 intr 20: pxa2x0, 32 byte fifo (SIR)
pxaudc0 at pxaip0: USB Device Controller
ohci0 at pxaip0, version 1.0
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: PXA27x OHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
lcd_pxaip0 at pxaip0
wsdisplay0 at lcd_pxaip0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1 added (std, vt100 emulation)
zkbd0 at pxaip0
wskbd0 at zkbd0: console keyboard, using wsdisplay0
scoop0 at pxaip0: PCMCIA/GPIO controller
scoop1 at pxaip0: PCMCIA/GPIO controller
pxapcic0 at pxaip0: 2 slots
pcmcia0 at pxapcic0
pcmcia1 at pxapcic0
zssp0 at pxaip0
apm0 at pxaip0
zts0 at pxaip0
wsmouse0 at zts0 mux 0
zaudio0 at pxaip0: I2C, I2S, WM8750 Audio
audio0 at zaudio0
clock: hz=100 stathz=64
wdc0 at pcmcia0 function 0 "HITACHI, microdrive" port 0x0/16: irq 138
wd0 at wdc0 channel 0 drive 0: <HMS360604D5CF00>
wd0: 32-sector PIO, LBA, 3906MB, 7999488 sectors
wd0(wdc0:0:0): using BIOS timings
wi0 at pcmcia1 function 0 "D-Link, DCF-660W, " port 0x0/64, irq 137
wi0: PRISM2.5 ISL3873 (0x800c), Firmware 1.1.1 (primary), 1.7.4
(station), address 00:80:c8:2f:ab:1e
boot_file: 'bsd'
boot device: wd0.
rootdev=0x1000 rrootdev=0x1000 rawdev=0x1002
WARNING: using filesystem date -- CHECK AND RESET THE DATE!

Reply | Threaded
Open this post in threaded view
|

Re: soft errors on wakeup

Sam Hart-2
On 12 Dec 2005, at 10:57, Simon Ironside wrote:

>> # fdisk wd0
> Disk: wd0       geometry: 7936/16/63 [7999488 Sectors]
> Offset: 0       Signature: 0xAA55
>          Starting       Ending       LBA Info:
>  #: id    C   H  S -    C   H  S [       start:      size   ]
> ----------------------------------------------------------------------
> --
>  0: 00    0   0  0 -    0   0  0 [           0:           0 ] unused
>  1: 00    0   0  0 -    0   0  0 [           0:           0 ] unused
>  2: 00    0   0  0 -    0   0  0 [           0:           0 ] unused
> *3: A6    0   1  1 - 7935  15 63 [          63:     7999425 ] OpenBSD

you are using a 3100 ?

I am assuming you just took the default options and used all of the  
disk ?

>> and obviously checking /etc/fstab against the output of mount(8)  
>> and  df(1)
>
> Mine is very straight forward, I use the whole disk and have  
> everything in one / partition.

as is mine.

I am starting to think this is probably a problem common to all  
zaurus installs.


S a m

Reply | Threaded
Open this post in threaded view
|

Re: soft errors on wakeup

Stuart Henderson
In reply to this post by Sam Hart-2
--On 12 December 2005 10:43 +0000, Sam Hart wrote:

> On 12 Dec 2005, at 10:19, Simon Ironside wrote:
>
>> Sam Hart wrote:
>>> On 8 Dec 2005, at 13:30, J. Hart wrote:
>>>> I have noticed the occasional soft error from the hard drive on
>>>> waking up after a long suspend.
>>> I consistently get the same thing on the console, when running X
>>> it  must mask the messages.
>>
>> Same thing here, when running X too if I monitor console messages
>> in Eterm.
>
> yeah, I thought as much, I just hadn't ever checked

They probably end up in xconsole if it's running. Or of course the
system log.

Since it's come up, I'll mention seeing it too, almost every
resume...it hasn't really caused a problem here (yet!). Happens with or
without wi0 connected (senao nl2511cf etsi).

I sometimes get these instead, also when resuming.

wd0d:  aborted command writing fsbn 64 of 64-91 (wd0 bn 712720; cn 707
tn 1 sn 1), retrying
wd0: soft error (corrected)
wd0d:  aborted command writing fsbn 11520 of 11520-11523 (wd0 bn
724176; cn 718 tn 6 sn 54), retrying
wd0: soft error (corrected)

Maybe the drive hasn't finished spinning up when the command times-out?

I do sometimes also have a problem where the backlight won't come back
on after resuming (the text on-screen is visible and updated, but too
dark to read). Manually poking display.backlight doesn't help, either.
I haven't found a way to replicate it on-demand, I think it maybe
related to low-battery forced suspend, but not sure yet. Has anyone
else seen that happen?

> for straight diagnosis a full dmesg is generally a good idea ( though
> I doubt they differ greatly from zaurus to zaurus but you never know )

It's always useful to know the date of the OS, if nothing else.

># fdisk wd0

Seems correct on mine (the no. of blocks matches disk geometry).

> With them being soft errors I have not worried too much ( though
> there is clearly a problem, )
> the only other time I have seen this was with a HD I installed in a
> laptop, it wasn't long before the HD became unusable,
> or rather the HD was on it's way out and the soft errors being
> reported were the beginning of the end.
>
> As I said, I don't think it is THAT severe, but it is a problem.

If they are bogus, it does make it difficult to know whether any real
disk errors are appearing (unless you know the times when the box was
resumed to filter them out..)

dmesg from my sl-c3100..:

OpenBSD 3.8-current (GENERIC) #189: Sun Dec  4 14:24:25 MST 2005
    [hidden email]:/usr/src/sys/arch/zaurus/compile/GENERIC
real mem  = 67108864 (65536K)
avail mem = 53313536 (52064K)
using 844 buffers containing 3457024 bytes (3376K) of memory
mainbus0 (root)
cpu0 at mainbus0: PXA27x rev 4 (XScale core)
cpu0: DC enabled IC enabled WB enabled LABT branch prediction enabled
cpu0: 32KB(32b/l,32way) I-cache, 32KB(32b/l,32way) wr-back-lock D-cache
pxaip0 at mainbus0: CPU clock = 416.000 MHz
pxaintc0 at pxaip0 addr 0x40d00000: Interrupt Controller
pxagpio0 at pxaip0 addr 0x40e00000: GPIO Controller
pxadmac0 at pxaip0 addr 0x40000000 intr 25: DMA Controller
saost0 at pxaip0 addr 0x40a00000
saost0: SA-11x0 OS Timer
com0 at pxaip0 addr 0x40100000 intr 22: pxa2x0, 32 byte fifo
com1 at pxaip0 addr 0x40200000 intr 21: pxa2x0, 32 byte fifo
com2 at pxaip0 addr 0x40700000 intr 20: pxa2x0, 32 byte fifo (SIR)
pxaudc0 at pxaip0: USB Device Controller
ohci0 at pxaip0, version 1.0
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: PXA27x OHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
lcd_pxaip0 at pxaip0
wsdisplay0 at lcd_pxaip0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1 added (std, vt100 emulation)
zkbd0 at pxaip0
wskbd0 at zkbd0: console keyboard, using wsdisplay0
scoop0 at pxaip0: PCMCIA/GPIO controller
scoop1 at pxaip0: PCMCIA/GPIO controller
pxapcic0 at pxaip0: 2 slots
pcmcia0 at pxapcic0
pcmcia1 at pxapcic0
zssp0 at pxaip0
apm0 at pxaip0
zts0 at pxaip0
wsmouse0 at zts0 mux 0
zaudio0 at pxaip0: I2C, I2S, WM8750 Audio
audio0 at zaudio0
zrc0 at pxaip0: CE-RH2 remote control
wskbd1 at zrc0 mux 1
wskbd1: connecting to wsdisplay0
clock: hz=100 stathz=64
wdc0 at pcmcia0 function 0 "HITACHI, microdrive" port 0x0/16: irq 138
wd0 at wdc0 channel 0 drive 0: <HMS360604D5CF00>
wd0: 32-sector PIO, LBA, 3906MB, 7999488 sectors
wd0(wdc0:0:0): using BIOS timings
wi0 at pcmcia1 function 0 "INTERSIL, HFA384x/IEEE, Version 01.02" port
0x0/64, irq 137
wi0: PRISM2.5 ISL3873 (0x800c), Firmware 1.1.0 (primary), 1.4.9
(station), address 00:02:6f:32:37:aa
boot device: wd0.
rootdev=0x1000 rrootdev=0x1000 rawdev=0x1002
WARNING: / was not properly unmounted
WARNING: using filesystem date -- CHECK AND RESET THE DATE!
wd0e: device timeout reading fsbn 2545748 of 2545748-2545751 (wd0 bn
3520484; cn 3492 tn 8 sn 44), retrying
wd0: soft error (corrected)

Reply | Threaded
Open this post in threaded view
|

Re: soft errors on wakeup

Sam Hart-2
On 12 Dec 2005, at 11:12, Stuart Henderson wrote:

> --On 12 December 2005 10:43 +0000, Sam Hart wrote:
>> On 12 Dec 2005, at 10:19, Simon Ironside wrote:
>>
>>> Sam Hart wrote:
>>>> I consistently get the same thing on the console, when running X
>>>> it  must mask the messages.
>>> Same thing here, when running X too if I monitor console messages
>>> in Eterm.
>> yeah, I thought as much, I just hadn't ever checked
>
> They probably end up in xconsole if it's running. Or of course the  
> system log.

I just assumed thats where they were getting written, and that most  
people were using X and hadn't ever noticed.

> Since it's come up, I'll mention seeing it too, almost every  
> resume...it hasn't really caused a problem here (yet!). Happens  
> with or without wi0 connected (senao nl2511cf etsi).

interesting, I hadn't thought wi0 would have any effect on wd0,  
though it should be noted the CF can be used for microdrives.

I was recently trying to fix a bug in the linux/booter code which  
would prevent me from booting when my WiFi card was active.
Unfortunately I have had to put it on the backburner for the time  
being, I have a workaround so it doesn't bother me.
If anyone would like to discuss it in the new year, I'll get some  
patches rustled up.

> I sometimes get these instead, also when resuming.
>
> wd0d:  aborted command writing fsbn 64 of 64-91 (wd0 bn 712720; cn  
> 707 tn 1 sn 1), retrying
> wd0: soft error (corrected)
> wd0d:  aborted command writing fsbn 11520 of 11520-11523 (wd0 bn  
> 724176; cn 718 tn 6 sn 54), retrying
> wd0: soft error (corrected)
>
> Maybe the drive hasn't finished spinning up when the command times-
> out?

possibly, I don't know enough about the reported error to know

> I do sometimes also have a problem where the backlight won't come  
> back on after resuming (the text on-screen is visible and updated,  
> but too dark to read). Manually poking display.backlight doesn't  
> help, either. I haven't found a way to replicate it on-demand, I  
> think it maybe related to low-battery forced suspend, but not sure  
> yet. Has anyone else seen that happen?

sorry, I haven't

> It's always useful to know the date of the OS, if nothing else.

true

> Seems correct on mine (the no. of blocks matches disk geometry).

I was looking for an incorrect layout, fdisk catches some of the  
common errors but you can still bugger it up

I know this because I've done it  (#'_'# )

>> As I said, I don't think it is THAT severe, but it is a problem.
>
> If they are bogus, it does make it difficult to know whether any  
> real disk errors are appearing (unless you know the times when the  
> box was resumed to filter them out..)

I certainly don't think they are bogus, there is a problem, I  
personally don't think it is severe and I think it can be fixed.
I've seen a HD descend into oblivion, when you have real problems you  
know about it.


S a m

Reply | Threaded
Open this post in threaded view
|

Re: soft errors on wakeup

Simon Ironside-2
In reply to this post by Sam Hart-2
Sam Hart wrote:
> On 12 Dec 2005, at 10:57, Simon Ironside wrote:
>
> you are using a 3100 ?
>
> I am assuming you just took the default options and used all of the  disk ?

Yes and yes.

Simon

Reply | Threaded
Open this post in threaded view
|

Re: soft errors on wakeup

Simon Ironside-2
In reply to this post by Stuart Henderson
Stuart Henderson wrote:

> I do sometimes also have a problem where the backlight won't come back
> on after resuming (the text on-screen is visible and updated, but too
> dark to read). Manually poking display.backlight doesn't help, either. I
> haven't found a way to replicate it on-demand, I think it maybe related
> to low-battery forced suspend, but not sure yet. Has anyone else seen
> that happen?

No, I've not had that happen. I don't think I've ever had a low battery
condition force a suspend.

I have the battery suddenly going flat problem that has been mentioned
before (apm battery meter means nothing.) When I reconnect to the mains
and turn the zaurus back on again it boots and complains about
improperly dismounted file systems rather than resuming.

Cheers,
Simon

Reply | Threaded
Open this post in threaded view
|

Re: soft errors on wakeup

Stuart Henderson
In reply to this post by Sam Hart-2
--On 12 December 2005 11:31 +0000, Sam Hart wrote:

> interesting, I hadn't thought wi0 would have any effect on wd0,
> though it should be noted the CF can be used for microdrives.

I though I'd better test it since it would increase power drain, and
HDs need a lot more power to spin-up than under normal use. Pulling
more power than is available can cause odd effects sometimes. (Though,
thinking about it more, Microdrives spin up and down quite a lot in
normal use, and I've only noticed errors when resuming, so it's not
very likely to be a power problem).

Reply | Threaded
Open this post in threaded view
|

Re: soft errors on wakeup

Simon Ironside-2
Stuart Henderson wrote:

> I though I'd better test it since it would increase power drain, and HDs
> need a lot more power to spin-up than under normal use. Pulling more
> power than is available can cause odd effects sometimes. (Though,
> thinking about it more, Microdrives spin up and down quite a lot in
> normal use, and I've only noticed errors when resuming, so it's not very
> likely to be a power problem).

I've just tested a quick suspend/resume with the power adapter (and wi0
fwiw) in throughout and got these:

Dec 12 11:54:27 zaurus /bsd: wd0a:  aborted command reading fsbn 2325984
of 2325984-2326015 (wd0 bn 2326047; cn 2307 tn 9 sn 24), retrying
Dec 12 11:54:28 zaurus /bsd: wd0: soft error (corrected)

Cheers,
Simon.

Reply | Threaded
Open this post in threaded view
|

Re: soft errors on wakeup

Sam Hart-2
In reply to this post by Simon Ironside-2
On 12 Dec 2005, at 11:45, Simon Ironside wrote:

> I don't think I've ever had a low battery condition force a suspend.
> I have the battery suddenly going flat problem that has been  
> mentioned before (apm battery meter means nothing.)

I'm confused, if the battery suddenly goes flat does it not suspend ?

Hmmm.....

The system should suspend if battery level is at about 10% ( I  
think, ) if the power level drops from, say 25% to 0%
then it would be the same as removing power all together. This  
assumes that the level does not pass through  0% - 10%

The battery power level is hard to gauge, I don't envy anyone having  
to deal with that code.
I looked at the linux code for it a while back, as it seems to work  
well for them, but made little progress.
That code was probably written by Sharp engineers.

> When I reconnect to the mains and turn the zaurus back on again it  
> boots and complains about improperly dismounted file systems rather  
> than resuming.

In the situation described above, it would be like total power  
removal, so it does what it would do normally in that situation.

Just out of interest, I currently set up my partition to use  
softupdates.


S a m

Reply | Threaded
Open this post in threaded view
|

Re: soft errors on wakeup

Stuart Henderson
--On 12 December 2005 12:04 +0000, Sam Hart wrote:

> On 12 Dec 2005, at 11:45, Simon Ironside wrote:
>
>> I don't think I've ever had a low battery condition force a suspend.
>> I have the battery suddenly going flat problem that has been
>> mentioned before (apm battery meter means nothing.)
>
> I'm confused, if the battery suddenly goes flat does it not suspend ?
>
> Hmmm.....
>
> The system should suspend if battery level is at about 10% ( I
> think, ) if the power level drops from, say 25% to 0%
> then it would be the same as removing power all together. This
> assumes that the level does not pass through  0% - 10%
>
> The battery power level is hard to gauge, I don't envy anyone having
> to deal with that code.
> I looked at the linux code for it a while back, as it seems to work
> well for them, but made little progress.
> That code was probably written by Sharp engineers.
>
>> When I reconnect to the mains and turn the zaurus back on again it
>> boots and complains about improperly dismounted file systems rather
>> than resuming.
>
> In the situation described above, it would be like total power
> removal, so it does what it would do normally in that situation.
>
> Just out of interest, I currently set up my partition to use
> softupdates.

If this is to reduce problems after an unclean shutdown, think about
carving the disk into multiple partitions. Mounting / and /usr
read-only, and only /home and /var rw, might save a few fscks..

Reply | Threaded
Open this post in threaded view
|

Re: soft errors on wakeup

Simon Ironside-2
In reply to this post by Sam Hart-2
Sam Hart wrote:
> On 12 Dec 2005, at 11:45, Simon Ironside wrote:
>
>> I don't think I've ever had a low battery condition force a suspend.
>> I have the battery suddenly going flat problem that has been  
>> mentioned before (apm battery meter means nothing.)
>
>
> I'm confused, if the battery suddenly goes flat does it not suspend ?

I'm not the only one to experience this:

http://www.oesf.org/forums/index.php?showtopic=16392

Cheers,
Simon

Reply | Threaded
Open this post in threaded view
|

Re: soft errors on wakeup

Sam Hart-2
In reply to this post by Stuart Henderson
On 12 Dec 2005, at 12:12, Stuart Henderson wrote:

>> Just out of interest, I currently set up my partition to use
>> softupdates.
>
> If this is to reduce problems after an unclean shutdown

partly, but mainly to reduce the problems that can be caused by an  
unclean shutdown

my distinction here might be too subtle

> think about carving the disk into multiple partitions.

I do, I found the zaurus to be a steep learning curve compared to  
other OpenBSD platforms,
once I had it working consistently I wasn't looking to rock the boat  
too much.
It has been solid for me for a while now, so I might go back to it.

> Mounting / and /usr read-only, and only /home and /var rw, might  
> save a few fscks..

Not a bad idea, thanks


S a m

Reply | Threaded
Open this post in threaded view
|

Re: soft errors on wakeup

Uwe Stuehler
In reply to this post by J. Hart
On Thu, Dec 08, 2005 at 10:30:39PM +0900, J. Hart wrote:
> I have noticed the occasional soft error from the hard drive on waking
> up after a long suspend.  I have also noticed that after such a suspend,

oh, that would be an interrupted transfer that gets restarted.

transfers in progress need to be completed and further transfers
held off before suspending.  however, this requires changes in ata
code which aren't trivial.

> the Zaurus occasionally, but not always, thinks the hard drive has been
> improperly dismounted.

battery draining is another problem.  if you can reproduce it,
i really urge you to tell me how.