From owner-cvs-src@FreeBSD.ORG Fri Feb 11 19:05:40 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 9277716A4CE; Fri, 11 Feb 2005 19:05:40 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B2CE43D45; Fri, 11 Feb 2005 19:05:40 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost02.amcc.com ([192.195.69.49]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IBRH1K02.I76; Fri, 11 Feb 2005 11:05:44 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost02.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005021111090929102 ; Fri, 11 Feb 2005 11:09:09 -0800 From: "Vinod Kashyap" To: "Ralf S. Engelschall" Date: Fri, 11 Feb 2005 11:05:21 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: cc: cvs-src@freebsd.org cc: src-committers@freebsd.org Subject: RE: [FreeBSD-CVS] cvs commit: src/sys/dev/twa twa_cam.ctwa_globals.c twa_ioctl.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list 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:05:40 -0000 > 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. 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).