...
I can confirm that this bug exists. Not all the time but whenever it has been swithced off for a while.
Everything flashed okay as far as I know.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=75346\"][{POST_SNAPBACK}][/a][/div]
Ok, after my first post on this yesterday I am now seeing this every time I suspend. Not sure what the issue is. OZ 3.5.3 32-32 zImage w/Opie, md5sums checked out fine.
-- sojourner
[div align=\"right\"][a href=\"index.php?act=findpost&pid=75358\"][{POST_SNAPBACK}][/a][/div]
Yup. I can also confirm that this bug exists. I just flashed my Zaurus last night, and since then, this has happened to me about 6 times. It's also probably woke up successfully about 6 times too. I'm using the Opie image and a 32/32 kernel.
If this only happens with the Opie image, could this really be an issue with the kernel build? If it is in fact, occurring only the Opie image, it's probably some other issue. Not that I know, I'm just suggesting...
I've had other instabilities with the Opie image in OZ before too. In OZ 3.5.2 and now in OZ 3.5.3, the entire desktop will die (processes go bye-bye - not running anymore) and leave the VT useless, assumedly after some program crash. Restarting Opie via remote login works fine at these points, but this is not an option at work. SysAdmin no-likey install software and USB networking on these boxen.
Anyhow, does anyone have a guess as to what is causing this On/Off button problem yet?