From owner-freebsd-questions@FreeBSD.ORG Wed May 27 23:13:26 2009 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B82B9106566C for ; Wed, 27 May 2009 23:13:26 +0000 (UTC) (envelope-from gnemmi@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id 6D0F98FC08 for ; Wed, 27 May 2009 23:13:26 +0000 (UTC) (envelope-from gnemmi@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so2714335ywe.13 for ; Wed, 27 May 2009 16:13:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:mime-version:content-type:content-transfer-encoding :content-disposition:message-id; bh=u+SyxGtw3kdlw3dukD39+WeO81uKrGfzaq02UTOkyJk=; b=Y99SSDroyyOMynBJ+MSEguSN9gV9wF+PPVFkSleqHS+4/LHRCFHs48nuNCkmFk2f6Y XXn/UPuaRcdiW3zMjPe6L12aeMpiYtEazq6SCp+u0bNp62qZ6pxbPk3pHdZJa9vguqsN 6sJO6Ct2Def5InAOzFcaK+3431lczyh0X4h2U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; b=J4Vp67WKpyNTlR1G0jn/9ZKxMnxwmQsgIFpqaIwm8KEKh9Z511feOreonevYRelqYA 0TXI0UPR73nlOW+brglXbchqt4haiAUytfRF+dEGlmLLdswqHUy/We9SvgpObrzoxvzj 0wt3uYSsonq38YIMj+Z1h23oyX9elD09y+LqE= Received: by 10.100.12.1 with SMTP id 1mr947799anl.107.1243464234136; Wed, 27 May 2009 15:43:54 -0700 (PDT) Received: from ?192.168.1.100? ([190.177.209.75]) by mx.google.com with ESMTPS id 9sm662485ywf.22.2009.05.27.15.43.53 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 27 May 2009 15:43:53 -0700 (PDT) From: Gonzalo Nemmi To: questions@freebsd.org Date: Wed, 27 May 2009 19:43:56 -0300 User-Agent: KMail/1.9.10 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905271943.56052.gnemmi@gmail.com> Cc: Subject: Help logging kernel messages after failed resume X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 23:13:27 -0000 OK, it goes like this: Dell Inspiron 1318, "boot -v" can be found in here: http://pastebin.com/f3a1c204a sysctl -a | grep hw.acpi | sort can be found in here: http://pastebin.com/fcfc0035 First shot: Try the "Livefs CD", "myhost# acpiconf -s 3" WORKS !!! The machine goes into suspend state and resumes_from_it_without_any_problems !! Second shot: Install ... "myhost# acpiconf -s 3" does not work anymore ... I issue a "myhost# acpiconf -s 3" and then I get a kernel message: "fwohci0: fwohci_acpi_suspend" ... The machine enters suspend state ... so far so good. Now, when I try yo resume from suspend, the machine spouts a plethora of kernel errors .. most notable ones beign "bge0" errors, "fwohci0" errors and the following ...: ad4: WARNING - SETFEATURES SET TRANSFERMODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES SET TRANSFERMODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly ata3: port not implemented ad4: WARNING - SETFEATURES SET TRANSFERMODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES SET TRANSFERMODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly ad4: TIMEOUT - WRITE_DMA48 retryng (1 retry left) LBA=272675445 As you can tell by now, the machine never recovers from "-s 3" (or suspend to ram). The thing is, ad4 never gets back to life ... as a consecuence, even if the kernel trows its messages to stdout, they never get logged ! Is there a way to record those messages so I can post them on the corresponding list and file all the PRs I'm about to file?? Note: I can ssh into the notebook, then "su -" and issue "acpiconf -s 3", but I can't get the notebook to WOL .. so .. I have to press the power button on the notebook to get it to resume and as a consecuence, those messages are sent to stdout (notebook screen) and I can't get them on the ssh client. SCRIPT(1) it's not a solution either .. because ad4 never gets back to life .. so script can't record a thing after it went into suspend :( Any help will be greatly appreciated. Just in case you are wondering what happens if I boot with ACPI disabled: Fatal trap 9 http://lists.freebsd.org/pipermail/freebsd-acpi/2009-May/005734.html Best Regards -- Blessings Gonzalo Nemmi