From owner-cvs-src@FreeBSD.ORG Fri Feb 11 19:27:52 2005 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FDD316A4CE; Fri, 11 Feb 2005 19:27:52 +0000 (GMT) Received: from visp.engelschall.com (visp.engelschall.com [195.27.176.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83E3743D3F; Fri, 11 Feb 2005 19:27:51 +0000 (GMT) (envelope-from rse@engelschall.com) Received: by visp.engelschall.com (Postfix, from userid 1005) id 432A74CE56C; Fri, 11 Feb 2005 20:28:10 +0100 (CET) Received: by en1.engelschall.com (Postfix, from userid 10000) id BE045A17D5; Fri, 11 Feb 2005 20:26:59 +0100 (CET) Date: Fri, 11 Feb 2005 20:26:59 +0100 From: "Ralf S. Engelschall" To: Vinod Kashyap Message-ID: <20050211192659.GA81719@engelschall.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Organization: FreeBSD cc: cvs-src@freebsd.org cc: src-committers@freebsd.org Subject: Re: [FreeBSD-CVS] cvs commit: src/sys/dev/twa twa_cam.c twa_globals.c twa_ioctl.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Ralf S. Engelschall" List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Feb 2005 19:27:52 -0000 On Fri, Feb 11, 2005, Vinod Kashyap wrote: > > The same problem (3ware controller found, but device /dev/daX not > > discovered on booting and hence no root mount point) popped up for > > me yesterday under RELENG_5, too. The problem can be traced back to > > changes between 2005-02-03 (date of my old still working kernel) and > > 2005-02-10 (date of my new broken kernel). The whole diff to sys/ > > of RELENG_5 is about 350 KB (I used "cvs diff -jRELENG_5:2005-02-03 > > -jRELENG_5:2005-02-10") and I was at least able to reduce the > > origin of > > the problem to the appended 29 KB change set. > > > > With the latest RELENG_5 as of 2005-02-11 (today) but with > > this appended > > patch again backed out, the twa(4) problem is solved, too. Similarily, > > if I do not back out those changes and just use plain RELENG_5 as of > > 2005-02-11 with your patch above applied it is also solved. > > > > I guess your patch workarounds the problem, but the real origin of the > > problem is somewhere in the changes we can see in the appended patch. > > Unfortunately I do not understand the side-effects of those > > changes so I > > was not able to figure out myself which part of the change is actually > > causing the trouble for the twa(4) driver. > > > > Perhaps someone else can jump in and fix the origin of the problem... > > But the problem was first reported with RELENG_5 on Jan 12th, '05. > And I couldn't find any CAM related changes in the patch you sent. Yes, I know. Even the CAM related change between 2005-02-03 and 2005-02-11 had no effect on the problem. And I also recognized that people started to see problems before 2005-02-03. > The thing is, the occurrence of this seems to be pretty inconsistent. > I have never seen the problem myself at boot time, although I have > seen CAM not send down inquiries some times, on doing a kldload of > the driver (without my latest patch). My twa(4) was static in the kernel, btw. The question for me now mainly is: why do the backing out of the changes I sent also fix the problem... -- rse@FreeBSD.org Ralf S. Engelschall FreeBSD.org/~rse rse@engelschall.com FreeBSD committer www.engelschall.com