From owner-freebsd-current@FreeBSD.ORG Sat Apr 10 14:27:53 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 ADB6B16A4CE for ; Sat, 10 Apr 2004 14:27:53 -0700 (PDT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E92343D1F for ; Sat, 10 Apr 2004 14:27:53 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Sat, 10 Apr 2004 14:27:53 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id A996B5D07; Sat, 10 Apr 2004 14:27:52 -0700 (PDT) To: "M. Warner Losh" In-reply-to: Your message of "Fri, 09 Apr 2004 09:56:35 MDT." <20040409.095635.32718566.imp@bsdimp.com> Date: Sat, 10 Apr 2004 14:27:52 -0700 From: "Kevin Oberman" Message-Id: <20040410212752.A996B5D07@ptavv.es.net> cc: current@freebsd.org Subject: Re: HEADS UP: PCI Chnages 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: Sat, 10 Apr 2004 21:27:53 -0000 > Date: Fri, 09 Apr 2004 09:56:35 -0600 (MDT) > From: "M. Warner Losh" > Sender: owner-freebsd-current@freebsd.org > > I just committed some rather extensive changes to the pci bus layer. > These changes should help people that need better suspend/resume > support, better resource allocation and resource collision avoidance. > > There's only one known issue with this code, which I'll address > shortly. If you detach a pci device, the BARs are still live, so > there can be interference. > > I'm especially interested in people who have no pci bridges in them, > but whose BIOSes don't assign resources correctly and don't have > ACPI. > > Let me know how well/poorly this works. 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. Here are the differences I see relating to the ATA device: -atapci0: port 0x1860-0x186f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 31.1 on pci0 -ata0: reset tp1 mask=03 ostat0=50 ostat1=00 -ata0-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 -ata0-slave: stat=0x00 err=0x01 lsb=0x00 msb=0x00 -ata0: reset tp2 mask=03 stat0=50 stat1=00 devices=0x1 -ata0: at 0x1f0 irq 14 on atapci0 -ata0: [MPSAFE] -ata1: reset tp1 mask=03 ostat0=50 ostat1=00 -ata1-master: stat=0x00 err=0x01 lsb=0x14 msb=0xeb -ata1-slave: stat=0x00 err=0x00 lsb=0x00 msb=0x00 -ata1: reset tp2 mask=03 stat0=00 stat1=00 devices=0x4 -ata1: at 0x170 irq 15 on atapci0 -ata1: [MPSAFE] +atapci0: port 0x1860-0x186f,0x170-0x177,0x1f0-0x1f7 at device 31.1 on pci0 +atapci0: Bus reserved 0x10 bytes for rid 0x20 type 4 at 0x1860 Any other information I can provide? -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634