From owner-freebsd-acpi@FreeBSD.ORG Mon May 5 19:55:32 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 954E0B11; Mon, 5 May 2014 19:55:32 +0000 (UTC) Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47FBCBB; Mon, 5 May 2014 19:55:32 +0000 (UTC) Received: by mail-qa0-f48.google.com with SMTP id i13so2901811qae.35 for ; Mon, 05 May 2014 12:55:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Z5IY+HlZ3PmTBaYceXcE/qNUIOQUkZ4jK/APrJNbIJM=; b=KvCF9hrE1Pe96dXvIkUy63hJcQwqTEFVIvIMNbXCoRVZCLyEnxDlisV30g4+BQeWZA G2AHo8D6Od8z1aTwItAvPdM55Gu3zOy6fhnVW7NJMTs+Kh+L7RucK0bmtr48B+e5VagC HD6gdtlg7Q6EOfxc1OwgLiaalAidKPdJoIWGxBfCqUq5oWRxjGuAP+AGOSkAFfM6z0vK oK6ZTPCwcDA9dnemwYYGzc655NcIB9WNnPDPxPKSB3aUW2UDdpiauK+WB3ukHiW+RA1f USWx2HpWXjunbirLWy/3akeATZSVIu8YVlVJpxvXHN7UIlE+r4tMLSwNocm3UZlerqbZ f/IQ== MIME-Version: 1.0 X-Received: by 10.140.22.209 with SMTP id 75mr44839242qgn.4.1399319731448; Mon, 05 May 2014 12:55:31 -0700 (PDT) Received: by 10.224.191.201 with HTTP; Mon, 5 May 2014 12:55:31 -0700 (PDT) In-Reply-To: <5367EBBE.2020602@FreeBSD.org> References: <5367EBBE.2020602@FreeBSD.org> Date: Mon, 5 May 2014 12:55:31 -0700 Message-ID: Subject: Re: suspend issues with latest -HEAD, ahci failing to complete something? From: Adrian Chadd To: Alexander Motin Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-acpi@freebsd.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 May 2014 19:55:32 -0000 Hi, Would you mind testing the latest -HEAD out? It worked a couple weeks ago with my last rebuild on this particular laptop. -a On 5 May 2014 12:51, Alexander Motin wrote: > On 05.05.2014 20:37, Adrian Chadd wrote: >> >> (I know, I just emailed out asking about setting S3 for the default >> lid suspend state, however I just updated to the very latest head and >> things went a little backwards.) >> >> Suspend no longer works for me: >> >> May 5 10:33:10 lucy-11i386 acpi: suspend at 20140505 10:33:10 >> May 5 10:33:47 lucy-11i386 kernel: ahcich0: Timeout on slot 19 port 0 >> May 5 10:33:47 lucy-11i386 kernel: ahcich0: is 00000000 cs fff80fff >> ss fff80fff rs fff80fff tfd d0 serr 00000000 cmd 0000d317 >> May 5 10:33:47 lucy-11i386 kernel: (ada0:ahcich0:0:0:0): >> WRITE_FPDMA_QUEUED. ACB: 61 08 e0 b0 fa 40 42 00 00 00 00 00 >> May 5 10:33:47 lucy-11i386 kernel: (ada0:ahcich0:0:0:0): CAM status: >> Command timeout >> May 5 10:33:47 lucy-11i386 kernel: (ada0:ahcich0:0:0:0): Retrying command >> May 5 10:33:13 lucy-11i386 acpi: resumed at 20140505 10:33:13 >> >> May 5 10:33:59 lucy-11i386 acpi: suspend at 20140505 10:33:59 >> May 5 10:34:37 lucy-11i386 kernel: ahcich0: Timeout on slot 9 port 0 >> May 5 10:34:37 lucy-11i386 kernel: ahcich0: is 00000000 cs ffffff83 >> ss ffffff83 rs ffffff83 tfd d0 serr 00000000 cmd 0000c717 >> May 5 10:34:37 lucy-11i386 kernel: (ada0:ahcich0:0:0:0): >> WRITE_FPDMA_QUEUED. ACB: 61 08 18 5c f7 40 42 00 00 00 00 00 >> May 5 10:34:37 lucy-11i386 kernel: (ada0:ahcich0:0:0:0): CAM status: >> Command timeout >> May 5 10:34:37 lucy-11i386 kernel: (ada0:ahcich0:0:0:0): Retrying command >> May 5 10:34:03 lucy-11i386 acpi: resumed at 20140505 10:34:03 >> >> What has recently changed that'd possibly break ahci's ability to >> correctly suspend? > > > When I tested it last time (awhile ago), it was working for me. > ahci_ch_suspend() should block all I/O on the channel and wait until all > active commands complete. On resume channel should be reinitialized, device > reset and only then I/Os should be released. Do you see those timeouts on > suspend or resume? > > Do you have kern.cam.ada.spindown_suspend enabled? Can you try to disable > it? > > -- > Alexander Motin