From owner-freebsd-acpi@FreeBSD.ORG Sun Jul 8 23:01:09 2012 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E6DFB106566B for ; Sun, 8 Jul 2012 23:01:09 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id A93FE8FC0A for ; Sun, 8 Jul 2012 23:01:09 +0000 (UTC) Received: by obbun3 with SMTP id un3so23504473obb.13 for ; Sun, 08 Jul 2012 16:01:09 -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:content-transfer-encoding; bh=revkr+NJpi+i/cX/mAbCUSrQ5kZNLObmjBvUGpJsygg=; b=CPiCTU3EaOO0XR1MF0PfrUYoOM67oZUlG1n3NVwC4/5/UXA8ms8jPPnNnhhV6UnMBI +vxqt6IH8lU4f9nViph0LqkMCproAslSU4MufZfaIFV/pqV0/IMR0lBMUsEaXcyLxZEW 0ACTg+b3BInE3UmuPrO4e/hRoDN6WQxwDpTEa9QYGK/Qg3l8ciwINZZNId9ihJmvx3SU odQ7hWdpg1kumyV5NIx74+mX3mG2eEdXQTGQjni3vdzYUy/2DzeywPZJ2EhBkBt0xFq7 OwPT4xYf591e8JCAmFzhAzFMNJwjKBM+cA5C4gxKvW9nT35J/UqOpW2nZZ/vzsU57MAd otDQ== MIME-Version: 1.0 Received: by 10.60.6.73 with SMTP id y9mr39304214oey.17.1341788469300; Sun, 08 Jul 2012 16:01:09 -0700 (PDT) Received: by 10.60.61.38 with HTTP; Sun, 8 Jul 2012 16:01:09 -0700 (PDT) In-Reply-To: References: <201207021729413382845@gmail.com> <4FF2599B.6050409@gmail.com> <201207031411248300207@gmail.com> <1341437029.4017.5.camel@localhost> Date: Sun, 8 Jul 2012 18:01:09 -0500 Message-ID: From: Brandon Gooch To: mbsd , honestqiao@gmail.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-acpi@freebsd.org Subject: Re: Re: Resume failed after Suspend on Thinkpad x201i X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jul 2012 23:01:10 -0000 On Sat, Jul 7, 2012 at 10:40 AM, Brandon Gooch wrote: > On Wed, Jul 4, 2012 at 4:23 PM, mbsd wrote: >> On Tue, 2012-07-03 at 14:11 +0800, =E4=B9=94=E6=A5=9A/HonestQiao wrote: > [SNIP] >>> >>> In All the test, the screen is light and black, system is hangup, nothi= ng can be done. >>> The only thing can be done, is push power button, to force it shutdown. >> >> Which graphic card have you used? If you have had nvidia, it's normal, >> I've had the same problem "the screen is light and black". > > Can both of you show the output of `devinfo -v` from your systems? > > I was able to solve my suspend/resume issue with my nvidia-equipped > notebook by forcing the module load ordering of vgapm in > sys/isa/vga_isa.c: > > Index: sys/isa/vga_isa.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- sys/isa/vga_isa.c (revision 237779) > +++ sys/isa/vga_isa.c (working copy) > @@ -379,4 +379,4 @@ > 0 > }; > > -DRIVER_MODULE(vgapm, vgapci, vgapm_driver, vgapm_devclass, 0, 0); > +DRIVER_MODULE(vgapm, vgapci, vgapm_driver, vgapm_devclass, 0, SI_ORDER_A= NY); > > > The system requires however that I load the nvidia module in > /boot/loader.conf (as opposed to loading it after system is up and > running). > > -Brandon Oops, the patch above should instead be: Index: sys/isa/vga_isa.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- sys/isa/vga_isa.c (revision 238266) +++ sys/isa/vga_isa.c (working copy) @@ -379,4 +379,4 @@ 0 }; -DRIVER_MODULE(vgapm, vgapci, vgapm_driver, vgapm_devclass, 0, 0); +DRIVER_MODULE_ORDERED(vgapm, vgapci, vgapm_driver, vgapm_devclass, NULL, NULL, SI_ORDER_ANY); I made the edit for the diff on a clean tree, but I'm actually building from another :) The above is correct. However, I'm still not sure this pertains to your Intel video problem. -Brandon