Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 31 Mar 2000 18:19:46 +0200
From:      Wilko Bulte <wilko@yedi.iaf.nl>
To:        Andrew Gallatin <gallatin@cs.duke.edu>
Cc:        wilko@freebsd.org, Dave Haney <dave@engg.ksu.edu>, freebsd-alpha@freebsd.org
Subject:   Re: Unexpected machine check
Message-ID:  <20000331181946.D1351@yedi.iaf.nl>
In-Reply-To: <14563.49235.18765.586441@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Mar 30, 2000 at 04:07:40PM -0500
References:  <Pine.SO4.4.00.10003291814390.21551-100000@phobos.engg.ksu.edu> <20000330201513.A1750@yedi.iaf.nl> <14563.40742.553401.107502@grasshopper.cs.duke.edu> <20000330225247.C3785@yedi.iaf.nl> <14563.49235.18765.586441@grasshopper.cs.duke.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 30, 2000 at 04:07:40PM -0500, Andrew Gallatin wrote:

> Wilko Bulte writes:
>  > 
>  > I'll try doing that next week. Is there anything special to do when
>  > building the port? 
> 
> You'll need to mess with cflags to switch -O for -g.  You do that in
> one of the xc/config/cf files.   I'm not terribly good at building X,
> so I don't want to lead you astray by suggesting a particular file &
> being wrong.

OK, I'll see if I can make some time to mess around.

>  > Would that be back-traceable to if it is the X server or the kernel?
> 
> Its the X server; running X doesn't change the kernel's behaviour very 
> much.  The X server is what's groping around in device memory.

OK.

>  > > In fact, I wonder if we couldn't hack up a kernel to send a sigbus to
>  > > the offending X server & get a core dump rather than panicing.
>  > 
>  > Sounds reasonable.. a panic is a bit drastic ;)
> 
> No, a panic is the correct behaviour.  A unexpected, uncorrectable
> machine check is a sign that something very, very, very bad has

Let me clarify: drastic from the average user's perspective. If there is a
way to nuke the offending process without taking down the machine with it
(??? here) than that would be preferable. I have no idea if one can
selectively do this, and if it is worth doing in the first place. X servers
are 'special' in the sense that they are very intimate with the hardware
(right?).

> happened.  In 99.44% of the cases, you want the machine to panic on a
> machine check.  I'm just suggesting a temporary, never-to-be-committed
> hack to allow you to debug the X server.

Sure.

-- 
Wilko Bulte 			Arnhem, The Netherlands	  
http://www.tcja.nl  		The FreeBSD Project: http://www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000331181946.D1351>