Ticket #1621 (new defect)

Opened 6 years ago

Last modified 6 years ago

it will show white screen when press power button from suspend time(it only happens specific phone(no.51))

Reported by: regina_kim Owned by: openmoko-kernel
Priority: high Milestone: Om2008.9
Component: kernel Version:
Severity: blocker Keywords: must have?
Cc: testing@… Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: PatchReviewResult:
Reproducible:

Description

kernel : 200807017-asu.stable-uImage.bin
rootfs : 200807017-asu.stable-rootfs.jffs2

summary :it will show white screen when press power button from suspend time (it only happens specific phone(no.51))

step :

  1. flash new image (date 16th and 17th )
  2. it go into suspend time
  3. press power button

current result : appear white screen

expected result : it should show previous screen

Attachments

Unsaved Document 1 (7.5 KB) - added by regina_kim 6 years ago.
dmesg-suspend-resume-ok.txt (15.1 KB) - added by Karrde 6 years ago.
dmesg-suspend-resume-fail.txt (15.1 KB) - added by Karrde 6 years ago.

Change History

Changed 6 years ago by regina_kim

comment:1 Changed 6 years ago by will

  • Keywords must have? added

did you try re-flashing and trying again?

comment:2 Changed 6 years ago by will

  • Owner changed from openmoko-devel to openmoko-kernel
  • Component changed from unknown to System Software

comment:3 Changed 6 years ago by regina_kim

not yet. should i re-flash ?

actually i have try to flash 16th image

then re-flashing with 17th image both. and it happens both of images for only specific phone(No.51)

comment:4 Changed 6 years ago by andy

Try latest kernel anyway, since it has a patch for Glamo init after suspend that was missed out of recent big update to stable.

comment:5 Changed 6 years ago by Karrde

I have the same problem with my FR. When I suspend with "apm -s" and resume with the power button within a minute or two it resumes normally. But if I wait longer than that, it shows the white screen.

The problem isn't restricted to ASU, it also appears in 2007.2 and in Qtopia 4.3.2 with the kernel from http://moko.mwester.net/ or with a self build kernel from the andy tree. I have also tested this with a kernel that works in an another FR with no problems. Unfortunately, it didn't work with mine.

Yesterday I suspected the SD card as a prime candidate but I have tested this with two cards and with no card at all. Also it doesn't matter if the wlan is on or off.

Changed 6 years ago by Karrde

Changed 6 years ago by Karrde

comment:6 Changed 6 years ago by andy

Yes this seems to be some resume race with Glamo, I am working in this area yesterday and today. It's not MMC but some fault of the race vs Glamo making it fail MMC and LCD init the same.

You might like to turn off GSM and see if you get same results.

comment:7 Changed 6 years ago by Karrde

Apparently it seems to work with the gsm antenna and the modem turned off. I'm not sure if it worked the first time but from that point on I haven't seen the white screen.

comment:8 Changed 6 years ago by andy

Thanks for the testing. As I said I am working in this area and have a dozen or so patches lined up, a couple of them should impact around this. But none of them yet directly attack the GSM ingredient of it. Post if any new info comes otherwise for the next day or two try current kernels and let me know the impact.

comment:9 Changed 6 years ago by regina_kim

20080723-asu.stable-uImage.bin
20080724-asu.stable-rootfs.jffs2

i tested with above image for turn GSM off. but i could not check that because it does not enter the suspend (happen to two phones)

and i also tried to test with below image.but it can not launch to exposure.
20080723-asu.stable-uImage.bin
20080725-asu.stable-rootfs.jffs2

so i will test with Monday's image again.

thanks.


comment:10 Changed 6 years ago by regina_kim

20080723-asu.stable-uImage.bin
20080729-asu.stable-rootfs.jffs2

i tested with above image for turn GSM off. but still it happens.

comment:11 follow-up: ↓ 12 Changed 6 years ago by andy

Hi Regina, late last night I tracked down why this happens. I am working on a workaround more directly.

comment:12 in reply to: ↑ 11 Changed 6 years ago by tfm

It happens with the Om2008.8 release too. Sometimes after resuming it only shows a white screen. It then sometimes takes some seconds until the screen recovers, sometimes it takes minutes, sometimes I lose patience first and turn it off. ;)

The white screen predominantly appears after long suspend; e.g. 8h over night. When I wake it up in the morning it takes really long until the white disappears. But then almost every subsequent suspend/resume creates the white screen, no matter how long suspend was. After reboot the probability for white screen is significantly lower.

comment:13 Changed 6 years ago by Rorschach

For me the white screen never disappears again no matter how long I have to wait I have to reboot my phone. Om 2008.8

comment:14 follow-up: ↓ 16 Changed 6 years ago by andy

There seem to be two issues going on... one is that the LCM reinit is somehow delayed but does happen, the other is either that the deferred LCM reinit never happens or the Glamo was reset / is holding down nWAIT.

comment:15 Changed 6 years ago by regina_kim

  • Milestone changed from Om2008.8 to Om2008.9

comment:16 in reply to: ↑ 14 Changed 6 years ago by tfm

Replying to andy:

There seem to be two issues going on... one is that the LCM reinit is somehow delayed but does happen

Just wanted to emphasize that this delay can be as long as several minutes.

I also observed for the last few days that when I am outside moving around being in different places, I almost never get WSOD. When the phone is just lying around on my desk at home, it happens very frequently.

Are there any advanced debug options to make dmesg more verbose? Since the FR is still responding, ssh still working, it would be easy to provide logs.

Note: See TracTickets for help on using tickets.