From owner-freebsd-current@FreeBSD.ORG Sun Apr 11 08:27:25 2004 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 B953316A4CE for ; Sun, 11 Apr 2004 08:27:25 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21A6D43D48 for ; Sun, 11 Apr 2004 08:27:25 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i3BFRKkj071159; Sun, 11 Apr 2004 09:27:21 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 11 Apr 2004 09:28:05 -0600 (MDT) Message-Id: <20040411.092805.69023985.imp@bsdimp.com> To: stijn@win.tue.nl From: "M. Warner Losh" In-Reply-To: <20040411104731.GA51116@pcwin002.win.tue.nl> References: <20040410212752.A996B5D07@ptavv.es.net> <3320000.1081643496@lerlaptop.lerctr.org> <20040411104731.GA51116@pcwin002.win.tue.nl> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: ler@lerctr.org cc: current@freebsd.org Subject: Re: HEADS UP: PCI Changes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Apr 2004 15:27:25 -0000 In message: <20040411104731.GA51116@pcwin002.win.tue.nl> Stijn Hoop writes: : On Sat, Apr 10, 2004 at 07:31:36PM -0500, Larry Rosenman wrote: : > --On Saturday, April 10, 2004 14:27:52 -0700 Kevin Oberman : > wrote: : > : > s. Thanks : > > : > > I can now confirm that this one breaks my laptop. It's an IBM T30 (1.8 : > > GHz P4M). If I back out this set of commits (and a few since this one), : > > things work. With the commit, the ATA disk is not seen and I can't boot : > > up. : > > : > > I already posted the output of the boot in response to another current : > > post with the subject "Re: Recent -CURRENT doesn't find ata : > > controller". It actually odes, but it does not manage to talk to it (or : > > even seem to try to.) The ports are the significant difference I see. : > : > I see a similar failure on my Fujitsu C6651 (interestingly, also a ICH3). : : Although I haven't confirmed that this commit is the culprit, booting a : -CURRENT kernel halts with the same symptoms on my Dell D600, which has : an ICH4. No root device found (which is supposed to be on ad0s2a). : Unfortunately I do not have a serial cable here so no dmesg of the failed : boot :( Interesting... I have a ICH4 in my Sony: atapci0: port 0x1860-0x186f at device 31.1 on pci0 atapci0: Bus reserved 0x10 bytes for rid 0x20 type 4 at 0x1860 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] I'm not running the latest in the tree because I'm having a geom crash that I'm trying to get data for phk. I too have no com ports. Warner