Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
I'm implementing a framebuffer device driver on top
of Sigma Designs EM84xx OSD engine.
It works nicely usually, and since our kernel module
supports multiple boards we can enable /dev/fb0, /dev/fb1 and so
I have a crash situation I reproduced inside kgdb:
- enable the first EM84xx framebuffer: /dev/fb0. All consoles jump
- enable the second EM84xx framebuffer: /dev/fb1. No consoles jumps
there by itself.
- move all the consoles 0,1,2,3,4,5 from /dev/fb0 to /dev/fb1 using
- release /dev/fb0 happens gently
- insmod rivafb.o enables /dev/fb0 (it does not use /dev/fb2 as
I would have thought).
- move all the consoles 0,1,2,3,4,5 from /dev/fb1 to /dev/fb0 again.
The last manipulation freezes the scheduler at some point; however it's still
possible to break in using kgdb and the machine is stuck in:
Is rivafb stable or do you have some hint here?
Note: if this can be of any help, at the point of this test,
the ``NVdriver'' nvidia X helper kernel module was not loaded.
Chef de projet
REALmagic France SAS
Mobile: 0614372733 GPGkeyID: D2997E42