From owner-freebsd-acpi@freebsd.org Fri Jul 10 18:10:31 2015 Return-Path: Delivered-To: freebsd-acpi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83DCC3C78; Fri, 10 Jul 2015 18:10:31 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A0569B9; Fri, 10 Jul 2015 18:10:31 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by igoe12 with SMTP id e12so40615599igo.1; Fri, 10 Jul 2015 11:10:30 -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=fmaUxA3a/qBRPKi9Ueb0KtfZZv81rkVJZhaL2r12EVg=; b=ADpgCn9EZs1QkJ8CsVSdV1TeoagvJW4IW+7UT0JimbDXmYINic2U/kPommtr+upqsM Hji8XNrNN9zpGP8oDPfY4mMMYk8IYlHm6CLgzx88iTo/b0Ao7BvnO2+ogIiHAvANMQrc RasKk0+luRZnJwqrQXQVpjYYFYarHRua8ZP0ogugueFQlJufoqm3nXuXg1xocNhE3k5M sWsNOGbt7ybV8AQUFThq1fPVP5MXwmbaeAGXM5Kstk6WP3BhOOGmJ6E2FZ79DXtuBpMV mSeTqFFPIlhEl4J7j6GM7O5Q2vVeKpssw/rqe7CRTxpcjwTBVA79UgKCqNdDiyUGHVSj wCkQ== MIME-Version: 1.0 X-Received: by 10.107.27.195 with SMTP id b186mr5897659iob.140.1436551830536; Fri, 10 Jul 2015 11:10:30 -0700 (PDT) Received: by 10.36.38.133 with HTTP; Fri, 10 Jul 2015 11:10:30 -0700 (PDT) In-Reply-To: <559F4B70.8060402@metricspace.net> References: <559F4B70.8060402@metricspace.net> Date: Fri, 10 Jul 2015 11:10:30 -0700 Message-ID: Subject: Re: Attempting to diagnose suspend/resume issue From: Adrian Chadd To: Eric McCorkle Cc: "freebsd-mobile@freebsd.org" , "freebsd-acpi@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jul 2015 18:10:31 -0000 Hi, can you post some more debugging showing that the VGA driver is restoring the VGA state before the power is applied? Thanks! -a On 9 July 2015 at 21:34, Eric McCorkle wrote: > A long while ago, I reported my screen not coming back on after resume, > shortly after r274386 went in. Unfortunately, the follow-on patch > didn't seem to work for me. > > (r274386 changed the way devices get powered down/up, and r274397 fixed > a typo in r274386 that tried to power down/up the wrong devices.) > > I finally found the time to try and track this thing down, and I got > some information that might prove useful in tracking it down. > > > * The screen comes back up only for syscons in pixel mode up to r274835. > As far as I can tell, it doesn't work for vt in any revision (not as > sure about text-mode syscons, but there is at least one revision where > it works for pixel mode, but not text mode) > > * Comparing logs from r274385 and r274397, it seems the likely cause is > that the changes in r274386 reordered things so that the VGA driver > attempts to restore the state of the card before its power has been > turned back on (you can clearly see this happening, and you can see the > attempt to restore the state failing). > > * Suspend/resume works fine in Linux (I'm not sure how to get linux to > printout a debug trace similar to debug.bootverbose), so the hardware > can't be /that/ broken. > > * The order in which things happen during resume seems to be different > between vt and syscons resumes, though I can't tell where vt restores > the state of the card (or the efifb device) > > My guess as to the likely cause is that vt also tries to restore the > state of the card before its power has been turned back on similar to > what syscons does after r274386, or else the dual happens during suspend > (it tries to save the state after the device is powered down). It does > seem a little wierd that syscons would behave differently in that > respect for pixel mode vs text mode, though. > > I'm open to suggestions as to what to look at next, or theories as to > what might be the culprit. I also have dmesg logs for the various > revisions and drivers. > > Best, > Eric >