From owner-freebsd-current@FreeBSD.ORG Fri Apr 23 13:43:20 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 81DAB16A4CE; Fri, 23 Apr 2004 13:43:20 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7CE643D54; Fri, 23 Apr 2004 13:43:19 -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 i3NKhEgr088933; Fri, 23 Apr 2004 14:43:15 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 23 Apr 2004 14:43:22 -0600 (MDT) Message-Id: <20040423.144322.115909342.imp@bsdimp.com> To: jhb@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <200404231118.11833.jhb@FreeBSD.org> References: <20040422163451.C1D365D07@ptavv.es.net> <200404231118.11833.jhb@FreeBSD.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable cc: freebsd-current@FreeBSD.org cc: nate@root.org 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: Fri, 23 Apr 2004 20:43:20 -0000 In message: <200404231118.11833.jhb@FreeBSD.org> John Baldwin writes: : On Thursday 22 April 2004 12:34 pm, Kevin Oberman wrote: : > Well, things seem to have deteriorated slightly with Warner's recen= t PCI : > changes (backing out much of the PCI power stuff). : > : > 1. I have both my hard disks and floppies. Thanks Warner and S=F8re= n! : > : > 2. USB still works and recovers after a resume! : > : > 3. Sound is again playing too fast after resume. ICH audio is rever= ting : > to its native speed. With the PCI power stuff in there, it worke= d just : > fine. (It was nice while it lasted.) I suspect this will return = when : > Warner gets a few rough edges off of the PCI code. : > : > 4. After a resume, the shared PCI interrupt stops being delivered a= fter : > a LONG time interval. I've had it fail in 10 minutes, but it is = more : > likely to die after about an hour. It always dies in under 2 hou= rs. : > : > vmstat -i looks completely normal except that the count for irq 11 = never : > increases. All other interrupts and devices are fine. Is this a loc= king : > problem? Should I put WITNESS back in my kernel? I can't find any s= ign : > of any significant resource being exhausted. If you ignore the fact= that : > all devices on irq 11 are dead, the system continues to run just fi= ne. X : > is alive and the box seems completely normal. (Of course, USB, the : > network cards, and sound are completely gone.) System has neither = SMP : > or APIC in the kernel. : > : > I'd love to track this down. I have no idea how common it is, : > either. Since most people running CURRENT are not using suspend on = their : > laptops because of various problems except to test things, this mig= ht : > not have shown up for most people. (Or, it might be unique to the I= BM : > T30.) : > : > Thanks, : = : We probably just need to reprogram the PCI link devices on resume. A= re you = : using ACPI? The non-ACPI case I know doesn't do this yet. We aren't doing that at the moment. I have some changes in my tree, but there are issues with ndis not working quite right yet :-( Warner