From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 09:47:21 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5A8F16A41A for ; Wed, 22 Aug 2007 09:47:21 +0000 (UTC) (envelope-from uwe@grohnwaldt.eu) Received: from server02.lando.cc (server02.lando.cc [87.106.141.202]) by mx1.freebsd.org (Postfix) with ESMTP id 0FF3613C46C for ; Wed, 22 Aug 2007 09:47:20 +0000 (UTC) (envelope-from uwe@grohnwaldt.eu) Received: (qmail 31422 invoked from network); 22 Aug 2007 11:20:38 +0200 Received: from wlan033082.uni-rostock.de (HELO Winter) (139.30.33.82) by server02.lando.cc with (DHE-RSA-AES256-SHA encrypted) SMTP; 22 Aug 2007 11:20:37 +0200 Date: Wed, 22 Aug 2007 11:20:19 +0200 From: Uwe Grohnwaldt To: freebsd-current@freebsd.org Message-ID: <20070822112019.4151b937@Winter> In-Reply-To: <46CBED98.8060107@cisco.com> References: <46CBED98.8060107@cisco.com> X-Mailer: Claws Mail 2.10.0 (GTK+ 2.10.14; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: IBM T43 sleep issue X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 22 Aug 2007 09:47:21 -0000 Am Wed, 22 Aug 2007 04:02:32 -0400 schrieb Randall Stewart : > Hi all: > > I just updated current last Sunday and now I have an issue > with sleeping my T43. > > It used to work as a one-shot.. i.e. I can sleep > once.. and wake up.. but it will never sleep again (I guess > some driver had/has a flag hung to say wake-back-up)... > > But now, when it comes out of sleep it panics.. something > about apic or something... Has anyone seen this? I can > reproduce it quite regular.. but I cannot get a kernel > dump (I guess the disk system is not initialized).. > > If someone is interested I can reproduce it and write down > the stack trace from DDB ... > > Oh, and a .. update now and try again is also a fine > answer.. :-D > > R Hi, I have the problem on my T43p since an update some weeks ago. It worked quite well unitl this Update. Sending it to sleep more than one time worked again. It would be nice if it will work again. :) Cheers, Uwe