Martin Bochnig wrote: > Hi Leonard, > > first of all thank you for having reported this issue, secondly congrats for > having discovered a real driver related crash (radeonhd_drv.so) :: > Thanks! I don't deserve it, really. ;-)
> START HERE: > http://blogs.sun.com/comand/entry/learn_mdb_in_30_minutes > http://solaristhings.blogspot.com/2006/08/dont-be-afraid-of-mdb.html . > I'll look into it. > A few comments regarding your (other) log files in general: > > 0) http://www.onebeam.net/xwin/Xorg-autoprobe.log > --->> the vesa_drv.so driver has been chosen for use. Therefore X11 boots up > and you don't get above crash. > I see. Thanks. > > FYI: There is a readability problem of your log files if they are being > opened up inside Firefox2 on Indiana x86 (the only thing I tested, as I'm > currently sitting in front of this). I see you're running Sun Java System > Application Server 9.1, probably on Solaris. At first I thought this is a > typical dos2unix related problem. But after I downloaded your log-files to my > (Solaris-) hdd, everything looked corerct again, whether with a pager, or > gedit. This must be a bug either In the FF-copile shipping as part of > Indiana, or it is related to Sun Java System Application Server 9.1 (rather > unlikely). > My website is on Mac OS X. I moved the files from Solaris over there to serve them up. > Can you provide ssh access to your Xorg box? > I'd rather not unless it becomes more necessary. > Or could you please send this list a more detailed backtrace? > Sure, I'll look into mdb. > p.s. As interim Solution I recommend you that you create a /etc/X11/xorg.conf > where you define "vesa" as driver to use, and set the screen settings > correspondingly (to what your monitor works best with). I recommend you do > this with xorgconfig again. Or just take a copy from xorg.conf.new and > replace "radeonhd" with "vesa" and manually adjust the resolution. > Thanks, that works! ==Leonard
