From owner-freebsd-current@FreeBSD.ORG Tue Sep 2 01:55:11 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A005416A4BF for ; Tue, 2 Sep 2003 01:55:11 -0700 (PDT) Received: from student.uci.agh.edu.pl (student.uci.agh.edu.pl [149.156.98.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05AFF43F85 for ; Tue, 2 Sep 2003 01:55:11 -0700 (PDT) (envelope-from winfried@student.uci.agh.edu.pl) Received: by student.uci.agh.edu.pl (Postfix, from userid 25828) id 3906264659; Tue, 2 Sep 2003 10:55:09 +0200 (CEST) Date: Tue, 2 Sep 2003 10:55:09 +0200 From: Jan Srzednicki To: current@freebsd.org Message-ID: <20030902085509.GG6853@student.agh.edu.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: Re: ATAng probe updated please test X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: w@dream.vg List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Sep 2003 08:55:11 -0000 On Tue, Sep 02, 2003 at 10:23:02AM +0200, Jan Srzednicki wrote: > > I've gone over the probe code once again. > > > > Please test, and in case it fails to detect or misdetects anything, > > mail me the output of dmesg from a verbose boot, and state what > > devices actually are there. > > Hello, > > The new stuff still failed to detect properly my hardware. Whole dmesg is > attached. But, mysteriously, after two reboots the problem vanished, and > I can see my HW as I should: OK, the drive did not get detected once again. This seems to be pretty random. > Anyway, > On the new kernel, reboot (after waiting for all the fsck's to finish) > resulted in panic when syncer was called to flush everything. This has > happened only once, I cannot reproduce it, yet the syncer problem > (giving up on 1 buffer) persist. It is not a problem with the aio > module, as I have removed it, and it still happens. Willing to provide > more feedback, if I knew how.. I've found this thing is related to ext2fs, as I stated in different thread. -- -- wrzask --= v =-- Winfried --===-- GG# 3838383 --- -- w@dream.vg --- w@303.krakow.pl --===-- http://violent.dream.vg/ --- --=< Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! >=-- Queen --