From owner-freebsd-stable@FreeBSD.ORG Mon Jun 12 12:33:18 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3800016A418 for ; Mon, 12 Jun 2006 12:33:18 +0000 (UTC) (envelope-from msoulier@digitaltorque.ca) Received: from mail.storm.ca (mail.storm.ca [209.87.239.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id B47BB43D4C for ; Mon, 12 Jun 2006 12:33:17 +0000 (GMT) (envelope-from msoulier@digitaltorque.ca) Received: from tigger.digitaltorque.ca (ppp-216-106-108-230.storm.ca [216.106.108.230]) by mail.storm.ca (8.13.6+Sun/8.13.6) with ESMTP id k5CCXGvY003684; Mon, 12 Jun 2006 08:33:16 -0400 (EDT) Received: by tigger.digitaltorque.ca (Postfix, from userid 500) id 68E1E240A0; Mon, 12 Jun 2006 08:33:10 -0400 (EDT) Date: Mon, 12 Jun 2006 08:33:10 -0400 From: "Michael P. Soulier" To: freebsd-stable@FreeBSD.ORG, greg.lane@internode.on.net Message-ID: <20060612123310.GA25618@tigger.digitaltorque.ca> Mail-Followup-To: freebsd-stable@FreeBSD.ORG, greg.lane@internode.on.net References: <20060612115933.GB10678@router.lane.family> <200606121213.k5CCD6K8062882@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VS++wcV0S1rZb1Fb" Content-Disposition: inline In-Reply-To: <200606121213.k5CCD6K8062882@lurza.secnetix.de> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: kernel panic(?) trying to copy data off failed drive with dd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jun 2006 12:33:18 -0000 --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 12/06/06 Oliver Fromme said: > So, if your panic is caused purely by software error, and > it's not already known and documented, filing a PR might be > a good idea. But if faulty hardware is involved, sending > a PR is probably useless. I would think that it would depend on how the hardware is being used. If the disk with errors happens to hold the swap partition, then it's difficult to blame the kernel for crashing. If it's simply reading data, I don't think t= hat a kernel panic is acceptable. Mike --=20 Michael P. Soulier "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein --VS++wcV0S1rZb1Fb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEjV8GKGqCc1vIvggRAlu+AJ9UDQDvXp83RNKtU2VrVRv6RoZzYQCeNP5U c0ij3F3sLb+7zRkUk/0rz5Y= =x7Vc -----END PGP SIGNATURE----- --VS++wcV0S1rZb1Fb--