From owner-freebsd-i386@FreeBSD.ORG Sun Jul 6 14:10:18 2003 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCF5137B401 for ; Sun, 6 Jul 2003 14:10:18 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7021543FAF for ; Sun, 6 Jul 2003 14:10:18 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h66LAIUp054095 for ; Sun, 6 Jul 2003 14:10:18 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h66LAIQA054094; Sun, 6 Jul 2003 14:10:18 -0700 (PDT) Date: Sun, 6 Jul 2003 14:10:18 -0700 (PDT) Message-Id: <200307062110.h66LAIQA054094@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: "KAREN THODE" Subject: Re: i386/53620: Kernel panics / reboots during install of 5.1 to 40GB disk on 44 X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: KAREN THODE List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2003 21:10:19 -0000 The following reply was made to PR i386/53620; it has been noted by GNATS. From: "KAREN THODE" To: , Cc: Subject: Re: i386/53620: Kernel panics / reboots during install of 5.1 to 40GB disk on 44 Date: Sun, 6 Jul 2003 16:07:27 -0500 ------=_NextPart_001_0000_01C343D8.B1C43A50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Do you think that you could build a debugging kernel with crashdumps enab= led and then replicate the kernel panic? If you can, post a panic messag= e and gdb backtrace as a follow-up. Lucas ------=_NextPart_001_0000_01C343D8.B1C43A50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Do you think t= hat you could build a debugging kernel with crashdumps enabled and then&n= bsp;replicate the kernel panic? If you can, post a panic message an= d gdb backtrace as a follow-up.

Lucas

------=_NextPart_001_0000_01C343D8.B1C43A50--