From owner-freebsd-bugs  Sun Dec 26 14:34:57 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from assaris.sics.se (assaris.sics.se [193.10.66.234])
	by hub.freebsd.org (Postfix) with ESMTP
	id C9B6714FF2; Sun, 26 Dec 1999 14:34:53 -0800 (PST)
	(envelope-from assar@assaris.sics.se)
Received: (from assar@localhost)
	by assaris.sics.se (8.9.3/8.9.3) id XAA62086;
	Sun, 26 Dec 1999 23:35:05 +0100 (CET)
	(envelope-from assar)
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Cc: bugs@freebsd.org, sos@freebsd.org
Subject: Re: kern/15689: gdb on core-dump does not work on current-19991225
References: <199912252350.SAA17183@skynet.ctr.columbia.edu>
From: Assar Westerlund <assar@sics.se>
Date: 26 Dec 1999 23:35:02 +0100
In-Reply-To: Bill Paul's message of "Sat, 25 Dec 1999 18:50:28 -0500 (EST)"
Message-ID: <5lln6hfi09.fsf@assaris.sics.se>
Lines: 15
User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Bill Paul <wpaul@skynet.ctr.columbia.edu> writes:
> This is your problem. Crash dumps are broken with the ata driver.
> Again. No, it's not a gdb problem: gdb -k /kernel /dev/mem still
> works fine. I just tested it on my Dec. 21st snapshot on my laptop
> (I'm still trying to track down some bugs in the USB code) and had
> the same problem. I changed to using a kernel with the wd driver and
> it worked again. Basically, the crash dump generated by the ata driver
> is corrupt somehow. Unfortunately, I can't offer a fix: I have no
> ATA clues. I'm cc'ing this to sos@freebsd.org; hopefully he'll be
> able to track the problem down.

I did cvsup a new kernel, rebuild and then I managed to get a working
crash dump (the one in kern/15707).

/assar


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