From owner-freebsd-current@FreeBSD.ORG Fri Apr 23 14:01: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 433DC16A4CE for ; Fri, 23 Apr 2004 14:01:20 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 1F57443D39 for ; Fri, 23 Apr 2004 14:01:20 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 53539 invoked by uid 1000); 23 Apr 2004 21:01:21 -0000 Date: Fri, 23 Apr 2004 14:01:21 -0700 (PDT) From: Nate Lawson To: "M. Warner Losh" In-Reply-To: <20040423.144322.115909342.imp@bsdimp.com> Message-ID: <20040423140023.S53535@root.org> References: <20040422163451.C1D365D07@ptavv.es.net> <200404231118.11833.jhb@FreeBSD.org> <20040423.144322.115909342.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE cc: freebsd-current@FreeBSD.org cc: jhb@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 21:01:20 -0000 On Fri, 23 Apr 2004, M. Warner Losh wrote: > 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 recent = PCI > : > changes (backing out much of the PCI power stuff). > : > > : > 1. I have both my hard disks and floppies. Thanks Warner and S=F8ren! > : > > : > 2. USB still works and recovers after a resume! > : > > : > 3. Sound is again playing too fast after resume. ICH audio is reverti= ng > : > to its native speed. With the PCI power stuff in there, it worked = just > : > fine. (It was nice while it lasted.) I suspect this will return wh= en > : > Warner gets a few rough edges off of the PCI code. > : > > : > 4. After a resume, the shared PCI interrupt stops being delivered aft= er > : > a LONG time interval. I've had it fail in 10 minutes, but it is mo= re > : > likely to die after about an hour. It always dies in under 2 hours= =2E > : > > : > vmstat -i looks completely normal except that the count for irq 11 ne= ver > : > increases. All other interrupts and devices are fine. Is this a locki= ng > : > problem? Should I put WITNESS back in my kernel? I can't find any sig= n > : > of any significant resource being exhausted. If you ignore the fact t= hat > : > all devices on irq 11 are dead, the system continues to run just fine= =2E X > : > is alive and the box seems completely normal. (Of course, USB, the > : > network cards, and sound are completely gone.) System has neither SM= P > : > 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 th= eir > : > laptops because of various problems except to test things, this might > : > not have shown up for most people. (Or, it might be unique to the IBM > : > T30.) > : > > : > Thanks, > : > : We probably just need to reprogram the PCI link devices on resume. Are= 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 :-( I thought that was enabled in the ACPI-PCI bridge driver. At least my latest version seems to do it (added by iwasaki@ a while ago). Did you disable that again? Or are your comments just for the !acpi case? -Nate