[Openchrome-users] What shall we do about this bug

[Jon Nettleton]

On Sun, 2006-09-24 at 18:18 +0200, Thomas Hellstr?m wrote: 
> Jon Nettleton wrote:
> 
> >So the problem with Trac bug #42 is an invalid pointer being referenced
> >for the RefreshRate that is setup.  After a bunch of debugging I finally
> >noticed in the logs the real problem.
> >
> >(II) VIA(0): Monitor0: Using default hsync range of 28.00-33.00 kHz 
> >(II) VIA(0): Monitor0: Using default vrefresh range of 43.00-72.00 Hz
> >
> >The hsync setup for the monitor isn't high enough so VBE isn't setting
> >up any refresh rates for the modes it sets.  Changing the hsync in the
> >xorg.conf fixes this problem.
> >
> >My question is should this be filed as an upstream bug, or should it be
> >handles in via_vbe.c?  We should be able to fail a bit more gracefully
> >than a crashed X server and a stack trace.  
> >  
> >
> Indeed. What's the value of the refreshrate pointer when you get a segfault?
> Why does it work in 32-bit mode?

Sorry I didn't clarify this before.  This problem exists for both 64-bit
and 32-bit platforms.  You can see it yourself by changing your monitors
HorizSync to something low 30-33...then for remove 640x480 as a
resolution option and enable VBEmodes for your via driver.  Restart X
and you should see the stack trace.

I haven't been able to see what the value of refreshrate is because as
soon as you try to do anything with it it causes a stack trace.  It is
actually the X server message that is supposed to print out the mode and
refresh rate that is causing the stack trace.  It is all very strange.


> 
> /Thomas
> 
> >I will leave the bug open until we decide if we fix it in openchrome, or
> >in vbe in xorg.
> >
> >Jon
> >
> >
> >_______________________________________________
> >openchrome-users mailing list
> >openchrome-users at openchrome.org
> >http://wiki.openchrome.org/mailman/listinfo/openchrome-users
> >Main page:
> >http://www.openchrome.org
> >Wiki:
> >http://wiki.openchrome.org
> >User Forum:
> >http://wiki.openchrome.org/tikiwiki/tiki-view_forum.php?forumId=1
> >
> >
> >  
> >
>