mxcfb framebuffer driver crashes the board hard on attempt to use a different resolution than the one specified on cmdline
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-fsl-imx51 (Ubuntu) |
Invalid
|
Low
|
Unassigned | ||
Karmic |
Won't Fix
|
Low
|
Unassigned | ||
Lucid |
Won't Fix
|
Low
|
Unassigned |
Bug Description
on imx51 hardware that uses mxcfb if you do the following it crashes the machine into a halt:
switch to tty1
run: usplash -c
this is caused by the fact that usplash if no resolution is specified either in usplash.conf or as commandline args will default to display the smallest theme possible and adjust itself to the size of this theme. the smallest theme possible it finds is usually 640x480, so the above tries to display a 640x480 screen on the 1024x768 (default setting for mxcfb in our images and setup). the mxcfb driver should not hardlock the device but either properly scale up the usplash screen like all other frambuffer drivers do or at least fail gracefully and properly switch back to its former console if 640x480 can not be displayed. it should definately not halt the system.
just to proof the concept, running the following on a tty in the current karmic live images for babbage will work fine:
usplash -c -x 1024 -y 768
ProblemType: Bug
Architecture: armel
Date: Fri Aug 28 14:01:25 2009
DistroRelease: Ubuntu 9.10
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha armel+imx51 (20090828.2)
Package: linux-image-
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: linux-fsl-imx51
Uname: Linux 2.6.31-100-imx51 armv7l
tags: | added: iso-testing |
Changed in linux-fsl-imx51 (Ubuntu Lucid): | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in linux-fsl-imx51 (Ubuntu): | |
status: | Triaged → Invalid |
I think it also hangs on shutdown (even with the workaround) if you have console=ttymxc0 last on your kernel cmdline.