Date: Sat, 13 Mar 2010 18:33:40 +1100 (EST) From: Ian Smith <smithi@nimnet.asn.au> To: Tim Matthews <tim.matthews7@gmail.com> Cc: freebsd-acpi@freebsd.org Subject: Re: Cannot suspend system. Message-ID: <20100313182152.G85436@sola.nimnet.asn.au> In-Reply-To: <3f1d93451003101702j1fa4dd56g6c49788c3c7ad70d@mail.gmail.com> References: <3f1d93451002271530j2fdc90b9rdec7555829d99f1b@mail.gmail.com> <3f1d93451002280240k7e261562m2375c72326298f1a@mail.gmail.com> <3f1d93451003011425t1bb37a1br27f2bf633d229670@mail.gmail.com> <201003011800.30623.jkim@FreeBSD.org> <3f1d93451003101702j1fa4dd56g6c49788c3c7ad70d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 11 Mar 2010, Tim Matthews wrote: > On Tue, Mar 2, 2010 at 12:00 PM, Jung-uk Kim <jkim@freebsd.org> wrote: > > > > > The error message says one of the device drivers failed to suspend > > properly. When that happens, acpi(4) refuses to suspend for "better > > safer than sorry" reason. You can try one thing, though. Remove all > > non-essential device drivers from kernel configuration and build a > > bare minimum kernel, which is just enough to boot your machine. > > > > I have removed just about everything and made sure there wasn't anything > lying around in loader.conf too. The suspend still fails. > > Is there anything else that can be done? You could try turning on hw.acpi.verbose in sysctl.conf (I noticed it was off), booting with verbose messages on, then looking at the messages before, during and after attempting to suspend. This may show something about some particular device that won't or can't suspend, that you could then show us. /var/run/dmesg.boot (verbose) may also contain some related clues. cheers, Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100313182152.G85436>