From owner-freebsd-current  Fri May 17  4:14: 1 2002
Delivered-To: freebsd-current@freebsd.org
Received: from pump3.york.ac.uk (pump3.york.ac.uk [144.32.128.131])
	by hub.freebsd.org (Postfix) with ESMTP id A4E0237B406
	for <current@FreeBSD.ORG>; Fri, 17 May 2002 04:13:56 -0700 (PDT)
Received: from ury.york.ac.uk (ury.york.ac.uk [144.32.108.81])
	by pump3.york.ac.uk (8.10.2/8.10.2) with ESMTP id g4HBDtU12225
	for <current@FreeBSD.ORG>; Fri, 17 May 2002 12:13:55 +0100 (BST)
Received: from ury.york.ac.uk (localhost.york.ac.uk [127.0.0.1])
	by ury.york.ac.uk (8.12.3/8.12.3) with ESMTP id g4HBDt4D018159
	for <current@FreeBSD.ORG>; Fri, 17 May 2002 12:13:55 +0100 (BST)
	(envelope-from gavin.atkinson@ury.york.ac.uk)
Received: from localhost (gavin@localhost)
	by ury.york.ac.uk (8.12.3/8.12.3/Submit) with ESMTP id g4HBDtUn018156
	for <current@FreeBSD.ORG>; Fri, 17 May 2002 12:13:55 +0100 (BST)
X-Authentication-Warning: ury.york.ac.uk: gavin owned process doing -bs
Date: Fri, 17 May 2002 12:13:55 +0100 (BST)
From: Gavin Atkinson <gavin@ury.york.ac.uk>
To: <current@FreeBSD.ORG>
Subject: Re: Strange panic while dumping userspace core file
In-Reply-To: <Pine.BSF.4.33.0205171033260.14490-200000@ury.york.ac.uk>
Message-ID: <Pine.BSF.4.33.0205171211250.17319-100000@ury.york.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

On Fri, 17 May 2002, Gavin Atkinson wrote:
> Panic while writing a core file for a
> program that died on signal 11. Toshiba laptop, usually perfectly stable,
> resumed from suspend about two minutes before and was in the process of
> loading KDE... This panic has only ever happened once. there were lots of
> errors about calcru being negetive on the console and ATA interrupts
> arriving early, immediately before the panic.

I should probablt also point out that the messages about being unable to
read the hard drive were a one-off. I suspect that they were a symptom of
the overall problems (whatever it is), rather than a cause, although I
realise that ultimately they could be responsible for the panic.

Gavin


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