Ticket #236 (new defect)
White screen after Swap orientation was turned on
| Reported by: | vladare | Owned by: | ppronchery |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | build | Version: | trunk |
| Severity: | major | Keywords: | |
| Cc: |
Description
Hello,
I get white screen after turning on the swap orientation from AUX menu. How can I get my phone menu back?
My Regards,
Vlad
Change History
comment:2 Changed 2 years ago by prahal
Adding history:
openmoko devel discusssion :
http://kerneltrap.org/mailarchive/openmoko-devel/2009/1/11/4692434/thread
which provides insights on the register values meanings. But nothing close to what s wrong.
http://projects.linuxtogo.org/pipermail/smartphones-userland/2009-February/001114.html
provides the kernel error (I confirm): *glamofb cmd_queue never got empty*
and way to get back to normal (I confirm too): Setting "xrandr -o 0" and suspending after that seems to cure the WSOD. (though this requires a connection to the phone, I used usb ethernet)
comment:3 Changed 2 years ago by Deubeuliou
I can swap orientation w/o problem on the daily.
Can someone else confirm that this one is fixed ? however, I don't know what could have fixed that.
comment:4 Changed 2 years ago by vladare
It works for me but you will get white screen if you perform next steps:
Main menu.
Swap screen - OK
Start xterm
Swap screen - OK
Swap screen - White screen
comment:6 Changed 2 years ago by ati
Main menu: Swap orientation OK
xterm: WSOD(not death actually, more of faint)
cube(the game): WSOD
comment:7 Changed 2 years ago by tzwenn
I got the WSOD in tangoGPS
but not always, it is just sometimes...
comment:8 Changed 2 years ago by Tha_Man
I'm now using Timo's new kernel (as described on the OM Community mailinglist) with rev5 which seems to solve he WSOD issue for me. I can swap orientation when having different applications running in the background or foreground without my FR crashing. A nice side effect is the improved overall speed, the UI is more responsive and programs start quicker :-)

I've noticed this too. This is certainly a bug from Xglamo or the kernel, so it will be tough to fix ourselves. It is maybe already documented and patched somewhere though, so we will investigate.
Moreover, currently I know no other way than rebooting to get rid of it.