From owner-freebsd-i386@FreeBSD.ORG Sat Feb 23 16:40:05 2008 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C062816A400 for ; Sat, 23 Feb 2008 16:40:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B361D13C45D for ; Sat, 23 Feb 2008 16:40:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m1NGe56D014433 for ; Sat, 23 Feb 2008 16:40:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m1NGe5QP014432; Sat, 23 Feb 2008 16:40:05 GMT (envelope-from gnats) Date: Sat, 23 Feb 2008 16:40:05 GMT Message-Id: <200802231640.m1NGe5QP014432@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: Volker Cc: Subject: Re: i386/74650: System Reboot with umount command X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Volker List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Feb 2008 16:40:05 -0000 The following reply was made to PR i386/74650; it has been noted by GNATS. From: Volker To: bug-followup@FreeBSD.org, kbyrdPM@yahoo.com Cc: Subject: Re: i386/74650: System Reboot with umount command Date: Sat, 23 Feb 2008 17:37:33 +0100 Kemp, I've found your PR untouched for quite a while. I'm wondering if you're still able to reproduce the problem? Even with later releases? If this is the case, please give us complete details: a kernel backtrace (see handbook for instructions) `uname -a' `dmesg' or content of /var/run/dmesg.boot `devinfo -v' Have you checked that issue using different floppy disk media? I'm sorry your problem hasn't been analyzed such a long time but we need those infos to check what has been wrong on your machine. Thanks!