From owner-freebsd-current@FreeBSD.ORG Wed May 6 23:37:18 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB009106566B; Wed, 6 May 2009 23:37:18 +0000 (UTC) (envelope-from mav@mavhome.dp.ua) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id EF8F88FC12; Wed, 6 May 2009 23:37:17 +0000 (UTC) (envelope-from mav@mavhome.dp.ua) X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona-2.1.0 Received: from [137.122.72.187] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 242134781; Thu, 07 May 2009 01:37:16 +0300 Message-ID: <4A021118.2030106@mavhome.dp.ua> Date: Thu, 07 May 2009 01:37:12 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.21 (X11/20090405) MIME-Version: 1.0 To: Guy Brand , current References: In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 06 May 2009 23:41:59 +0000 Cc: sbruno@FreeBSD.org Subject: Re: amd64 suspend/resume broken on current 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, 06 May 2009 23:37:18 -0000 Guy Brand wrote: > Suspend/resume (S3) was working like a charm and it is now broken with > FreeBSD 8.0-CURRENT #1: Wed May 6 18:27:21 CEST 2009 GENERIC amd64. > > I can suspend the laptop, but when resuming it I'm in a console which > gets a lot of "fwohci0: device physically ejected?" messages and the > system is dead. Looking onto the message, problem may be FireWire related. We have tested FireWire with Sean Bruno on my laptop, and even as system resumed successfully, FireWire was not working after resume, until we reloaded the driver. So there are definitely some problems exist. We can try to check it more, but could you try to unload FireWire drivers and try again? -- Alexander Motin