Date: Tue, 26 May 2009 11:39:15 -0400 From: Glen Barber <glen.j.barber@gmail.com> To: =?ISO-8859-1?Q?Fernando_Herrero_Carr=F3n?= <fhcarron@terra.es> Cc: freebsd-hackers@freebsd.org Subject: Re: Help debugging kernel together with X Message-ID: <4ad871310905260839u24ce71e9wbaa637712480c390@mail.gmail.com> In-Reply-To: <1243345847.1007.11.camel@nebet.ii.uam.es> References: <1243345847.1007.11.camel@nebet.ii.uam.es>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Fernando 2009/5/26 Fernando Herrero Carr=F3n <fhcarron@terra.es>: > Hi list, > > I would like to ask for some help debugging the kernel. > > Here is the problem: > > I have a computer about five years old with an on-board graphics card > (SiS 661). I am trying to install an ATI Radeon 128 on the AGP port. > FreeBSD (FreeBSD 7.2-STABLE #10: Tue May 26 15:08:39 CEST 2009) is able > to start DRM and AGP without trouble. However, whenever I start X (X.Org > X Server 1.6.1; Release Date: 2009-4-14; Build Date: 11 May 2009 > 12:03:27PM) the system freezes with a blank screen with some apparent > noisy green dots on it (reproducible, however). It does not panic, nor > reboot. > > Now I suspect there is some problem on the AGP bridge driver since linux > can run X without trouble (i.e. hardware and BIOS are ok). I have found > someone reporting problems with this bridge long time ago with no > answers (http://www.nabble.com/agp-on-sis-661-td1446998.html). > > So here I am trying to figure out where the system freezes. I have > recompiled my kernel adding the following options: > > options =A0 =A0 =A0 =A0 KDB > options =A0 =A0 =A0 =A0 DDB > options =A0 =A0 =A0 =A0 MP_WATCHDOG > options =A0 =A0 =A0 =A0 SW_WATCHDOG > > I am able to enter the debugger with ctrl+alt+esc from a console. So > what I am trying to do is to have watchdogd time out and the debugger > make a dump: > > ddb script kern.enter.watchdog=3Dcall doadump; reboot > > However, when I start X no timeout occurs, and the system stays freezed. > Am I missing something on the workings of watchdogd? > What you're describing does not appear to be a kernel problem; it sounds like the typical 'Xorg update from hell' problem most experienced a while back. Have a look at /usr/ports/UPDATING, and search for 'AllowEmptyInput'. Adding the following to xorg.conf should correct the problem: Section "ServerFlags" option "AllowEmptyInput" "off" option "AutoAddDevices" "off" EndSection HTH --=20 Glen Barber
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ad871310905260839u24ce71e9wbaa637712480c390>