Date: Wed, 2 Nov 2005 20:33:39 -0800 (PST) From: =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= <mbsd@pacbell.net> To: Scott Long <scottl@samsco.org> Cc: Felipe openglx <openglx@StarByte.net>, Yar Tikhiy <yar@comp.chem.msu.su>, current@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming Message-ID: <20051102203028.T20004@inspiron.home> In-Reply-To: <4367A6AF.7030805@samsco.org> References: <436116D3.908@samsco.org> <621b657f0510280654j56d4a823n5237f89ccc96b1e9@mail.gmail.com> <436246C1.3030108@samsco.org> <20051101165534.GB56709@comp.chem.msu.su> <43679F3C.4040702@samsco.org> <621b657f0511010925t578a5df7nd82040b71e104478@mail.gmail.com> <4367A6AF.7030805@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 1 Nov 2005, Scott Long wrote: > Felipe openglx wrote: >> In fact I agree with Scott. There isn't much the OS can do. >> >> As for that bug, I'm already in contact with the X.org developers and >> trying to do a deeper debugging on what's going on. The driver >> developer himself said he cannot test that on FreeBSD, thus not >> assuring it full functionality. So it looks much more to be a X.org >> problem than FreeBSD one. >> >> On 11/1/05, Scott Long <scottl@samsco.org> wrote: >> >>> Yar Tikhiy wrote: >>> >>>> When a 3rd party package crashes our OS, we should care about the >>>> issue, too. However, this case seems to require more investigation >>>> by developers who have similar hardware. >>>> >>> >>> The fact that X has access to /dev/io means that it can do whatever it >>> wants to corrupt the machine, and there isn't much the OS can do about >>> it. >>> >>> Scott >>> >> >> >> >> -- >> openglx@StarByte.net > > One caveat that I forgot is that there are SiS AGP and DRI/DRM modules > that operate in the kernel and come with the stock FreeBSD sources. > You should isolate these out before looking any further. For AGP, > make sure that 'device agp' is not in your kernel or loaded as a > module, and for DRM make sure that your X config file omits the DRI/DRM > options. If it still fails then it's almost certainly an X bug and not > a FreeBSD bug. If it's a DRM problem then you'll still want to contact > the X folks since that code is maintained outside of the FreeBSD > project. If it's an AGP problem then we'll mark is as something that > needs fixing for 6.1. I had this problem. Making X not reboot the machine required removing the "sis" module, as it would be unconditionally loaded by the X server even without drm configured. I no longer have the hardware, and so can't do any further experiments. $.02, /Mikko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051102203028.T20004>