From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 31 00:59:09 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F04B16A4CE; Mon, 31 Jan 2005 00:59:09 +0000 (GMT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C66443D1D; Mon, 31 Jan 2005 00:59:09 +0000 (GMT) (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; Sun, 30 Jan 2005 16:59:08 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id DE9475D07; Sun, 30 Jan 2005 16:59:06 -0800 (PST) To: Gleb Smirnoff In-reply-to: Your message of "Sun, 30 Jan 2005 15:37:13 +0300." <20050130123713.GA6433@cell.sick.ru> Date: Sun, 30 Jan 2005 16:59:06 -0800 From: "Kevin Oberman" Message-Id: <20050131005906.DE9475D07@ptavv.es.net> cc: Andrew Belashov cc: Dave Walton cc: freebsd-mobile@freebsd.org Subject: Re: Trouble with APM suspend in 5.3-R X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2005 00:59:09 -0000 > Date: Sun, 30 Jan 2005 15:37:13 +0300 > From: Gleb Smirnoff > Sender: owner-freebsd-mobile@freebsd.org > > On Sun, Jan 30, 2005 at 04:29:54AM -0800, Dave Walton wrote: > D> Gleb Smirnoff wrote: > D> >On Thu, Jan 27, 2005 at 12:31:38PM -0800, Dave Walton wrote: > D> >D> It was on, now that you mention it. Why do you ask? > D> > > D> >Can you try the attached patch? > D> > D> Ah, we've come full circle, back to this patch, but this time with the > D> pcm panic out of the way. > D> > D> Well, with this patch added, it still locks up without an error message, > D> but now the HDD LED is OFF when it happens. What's the next step? > > Well, at this point I don't have more advices, sorry. Need the same hardware > to tell anything else. Well, on my T30 with this patch, I no longer lock up. Suspend and resume work, but I do get a disturbing error message: pir0: ROUTE_INTERRUPT on resume for link 0x68 failed. I know pir is the interrupt routing, but I have no idea what link 0x68 might be. Perhaps a verbose boot would provide a clue. After a few hours of running on the resumed system, I am not seeing any problems, though. -- 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