From owner-freebsd-bugs@FreeBSD.ORG Thu Sep 18 08:00:37 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C75416A4B3 for ; Thu, 18 Sep 2003 08:00:37 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88A2743FB1 for ; Thu, 18 Sep 2003 08:00:36 -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 h8IF0aFY082276 for ; Thu, 18 Sep 2003 08:00:36 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h8IF0a2W082275; Thu, 18 Sep 2003 08:00:36 -0700 (PDT) (envelope-from gnats) Date: Thu, 18 Sep 2003 08:00:36 -0700 (PDT) Message-Id: <200309181500.h8IF0a2W082275@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Pawel Malachowski Subject: Re: kern/56975: Write to a Compact Flash (CF) card freezes the whole system X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Pawel Malachowski List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2003 15:00:37 -0000 The following reply was made to PR kern/56975; it has been noted by GNATS. From: Pawel Malachowski To: S?ren Schmidt Cc: alo@iki.fi, FreeBSD-gnats-submit@FreeBSD.org Subject: Re: kern/56975: Write to a Compact Flash (CF) card freezes the whole system Date: Thu, 18 Sep 2003 16:53:08 +0200 On Thu, Sep 18, 2003 at 01:20:29AM -0700, S?ren Schmidt wrote: > State-Changed-From-To: open->closed > State-Changed-By: sos > State-Changed-When: Thu Sep 18 01:12:29 PDT 2003 > State-Changed-Why: > You are on the right track, I've just yesterday fixed the problem on > a system donated by servicefactory.se, just a bit differently from > your patch and under 4.x. I'll commit my patch in a few days when I'm > sure it has no ill effects.. So why not to reopen this PR with proper responsible, put it in patched state after commiting your fix and close after MFC to 4.x? It makes PR database consistent and PR tracking easier. cheers, -- Paweł Małachowski