From owner-freebsd-current@FreeBSD.ORG Thu Apr 22 09:34:52 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 D4B2816A4CE for ; Thu, 22 Apr 2004 09:34:52 -0700 (PDT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F35443D60 for ; Thu, 22 Apr 2004 09:34:52 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Thu, 22 Apr 2004 09:34:51 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id C1D365D07; Thu, 22 Apr 2004 09:34:51 -0700 (PDT) In-reply-to: Your message of "Sat, 10 Apr 2004 14:27:52 PDT." <20040410212752.A996B5D07@ptavv.es.net> Date: Thu, 22 Apr 2004 09:34:51 -0700 From: "Kevin Oberman" Message-Id: <20040422163451.C1D365D07@ptavv.es.net> cc: current@freebsd.org cc: "M. Warner Losh" cc: nate@root.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: Thu, 22 Apr 2004 16:34:52 -0000 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øren! 2. USB still works and recovers after a resume! 3. Sound is again playing too fast after resume. ICH audio is reverting 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 when Warner gets a few rough edges off of the PCI code. 4. After a resume, the shared PCI interrupt stops being delivered after 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 hours. vmstat -i looks completely normal except that the count for irq 11 never increases. All other interrupts and devices are fine. Is this a locking problem? Should I put WITNESS back in my kernel? I can't find any sign 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 fine. 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 might not have shown up for most people. (Or, it might be unique to the IBM T30.) Thanks, -- 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