From owner-freebsd-alpha Wed Oct 23 10: 6: 6 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3690437B401 for ; Wed, 23 Oct 2002 10:06:05 -0700 (PDT) Received: from gatekeeper.oremut01.us.wh.verio.net (gatekeeper.oremut01.us.wh.verio.net [198.65.168.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9519743E6E for ; Wed, 23 Oct 2002 10:06:04 -0700 (PDT) (envelope-from fclift@verio.net) Received: from mx.dmz.orem.verio.net (mx.dmz.orem.verio.net [10.1.1.10]) by gatekeeper.oremut01.us.wh.verio.net (Postfix) with ESMTP id 9B97A3BF125 for ; Wed, 23 Oct 2002 11:05:58 -0600 (MDT) Received: from vespa.dmz.orem.verio.net (vespa.dmz.orem.verio.net [10.1.1.59]) by mx.dmz.orem.verio.net (8.11.6/8.11.6) with ESMTP id g9NH5w321908 for ; Wed, 23 Oct 2002 11:05:58 -0600 (MDT) Date: Wed, 23 Oct 2002 11:12:19 -0600 (MDT) From: Fred Clift X-X-Sender: To: Subject: debugging around machine-checks... Message-ID: <20021023110134.Q98807-100000@vespa.dmz.orem.verio.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Ok -- I'm not terribly alpha proficitent - in fact, the one alpha that I run is just a home-server - little more than a toy (mp3 server, print server and relatively secure ssh enpoint from the outside world). Could someone explain exactly what is going on when a machine-check happens? Is this done by the machine firmware or something? It seems that FreeBSD is instantenously interrupted when a machine check happens and that I dont get crash-dumps. Some of you may recall that I've been playing around with XFree86 V4 on this box - it would be exceptionally helpful if I got usable crash-dumps instead of machine checks when things got wierd. As it is, debugging the X server is pretty much impossible (for me) because of this. What I've done is build all of the X distribution with debugging symbols in and then I start the X server from gdb and put in 10 break points near where I think things will be happening. Eventually, I get a machine check and if I'm lucky, I remember where the last breakpoint that I hit was so that after a reboot, I can kind of start back in that neighborhood. X is hard enough to debug by itself without this inconvienence. It seems that whatever is making it machine-check should be things that could be fixed in the kernel, at which point, my debugging of the X server could then continue.Then when X dumps core I can just restart X rather than wait for a reboot/fsck. Am I way off here? I seem to have read somewhere that there is something you can do to fend off machine-checks so that you can get a proper crash-dump? What is the mechanism that causes the checks and how bad would it be for the system to do something equivalent to maksing these events out (or whatever you'd do to get them to not happen?). Is there somewhere I can read about this? Fred -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message