2008.8 screen blanks and refuses to wakeup

[billk]

I have had the FR go into blank screen a number of times and refuse to wakeup. Its not suspended as usb networking still works. Trying to restart the xserver hangs. If I press the power button briefly, nothing happens. Same if I hold it for a second or two. At ~ 10 seconds it will shutdown - sometimes.

[montgoss]

I can confirm this bug. It happened to me earlier today.

[zecke]

This also happens with images from asu.dev. So something in the system (ompower, illume) get confused about what state the backlight should have.

Making sure raster sees it and removing the milestone as this is used by our ProductManager?.

[queen6]

Same problem here. Most of the times I just need to remove the battery and restart the phone.

[octavsly]

I just had the same problem with the releases at:
I need to remove the battery :-(

http://downloads.openmoko.org/releases/Om2008.8-update/
Om2008.8-gta02-20080903.uImage.bin    16-Sep-2008 00:31  1.8M  
Om2008.8-gta02-20080916.rootfs.jffs2  16-Sep-2008 00:31   68M  
gta02v5_and_up-u-boot.bin             16-Sep-2008 00:31  211K  

[zecke]

#1884 and #1991 might be related. This looks a lot like a duplicate of #1991.

[regina_kim]

hey billk ~

could you check it still happen ?

also check weather related what holger mention tickets.

[BillK]

It does, but only very occasionally, and usually when the phone has not registered (a separate problem? - bug #2012)

Can sometimes happen if I pull usb power soon after the desktop dsplay shows up on bootup, or if I suspend the phone (power button pressed) when not registered, the screen wont wake up - not sure if its even suspended. Killing apm brings it back, but must reboot immediately anyway as it always crashes messily within a few minutes.

However, if the phone boots up properly and registers there is no problem.

Along with my other issues, its all starting to sound like race conditions dependent on the GSM area.

BillK

[john_lee]

(In #1991) I will add similiar bugs here so it's easier to track.

[andy]

Is this issue still seen with recent 2.6.29 kernels?

[queen6]

Since the time I've switched to andy-tracking (2.6.28-rcX) which was few months ago - I can no longer reproduce this issue.

[andy]

Great, thanks for the feedback.