Date: Tue, 24 Mar 2009 18:31:17 -0500 From: Brandon Gooch <jamesbrandongooch@gmail.com> To: Adam McDougall <mcdouga9@egr.msu.edu> Cc: freebsd-current@freebsd.org, Jung-uk Kim <jkim@freebsd.org> Subject: Re: [HEADSUP] amd64 suspend/resume code to be comitted Message-ID: <179b97fb0903241631h76e8758dxd87900597a5cba4a@mail.gmail.com> In-Reply-To: <49C94D4C.5050104@egr.msu.edu> References: <1236802980.00085518.1236789602@10.7.7.3> <200903162053.28614.jkim@FreeBSD.org> <179b97fb0903231416j4659101eu88dcc5ecf578167b@mail.gmail.com> <200903231728.46911.jkim@FreeBSD.org> <179b97fb0903232306y548144dx94836b534d9441dd@mail.gmail.com> <49C94D4C.5050104@egr.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 24, 2009 at 4:14 PM, Adam McDougall <mcdouga9@egr.msu.edu> wrot= e: > Brandon Gooch wrote: >> >> On Mon, Mar 23, 2009 at 4:28 PM, Jung-uk Kim <jkim@freebsd.org> wrote: >> >>> >>> On Monday 23 March 2009 05:16 pm, Brandon Gooch wrote: >>> >>>> >>>> The committed version is working well, I am suspending and resuming >>>> on my Lenovo X300. Thanks for your work on this, it is one of the >>>> major things I needed to work so I could run FreeBSD primarily on >>>> my notebook. >>>> >> >> I just finished a kernel build and it seems as though your >> recent commits have fixed the clock (at least for me)! >> >> I feel sorry for all the i386 folks on ACPI notebooks... >> >> Thanks! >> >> -Brandon >> > > Picking a semi-random message here.. > > Thanks for your work on this! =A0In the past (months ago) I tried the pat= ch > set which didn't work, but the code in -current lets me suspend and resum= e > successfully on my Dell Latitude E6500 (acpiconf -s 3)! =A0I think this i= s a > first for me, of all the laptops I've had, none have ever been able to > suspend and resume in a successful or useful way, and I've been jealous o= f > the Thinkpad users that could claim otherwise. =A0I could suspend and res= ume > fine while in the console, then I ran startx and the suspend and resume > worked while I was in X with intel graphics, however my system was slow > after that resume. =A0I didn't spend much time looking at it since I was = at > work, and I didn't see any obvious reasons for the slowness (cpu frequenc= y > was fine, cx states were C2 or lower (C1), top showed mostly idle, no > evidence of an IRQ storm) yet processes ran fairly sluggish (not the mous= e > or typing though). =A0I didn't go back to console, I just shut down witho= ut > trying any other situations yet. > > A tip I want to note for any users who may not have success with their > screen on resume: =A0In the past it seemed to help me to have a power-on > password set in my BIOS since the BIOS will turn on the screen on resume = to > ask me for my password. =A0I don't know if it is still helping me, but I'= ve > seen in the past where it has. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > The sluggish response in X on Intel video has been an issue the past couple of days, triggered by suspend/resume or simply switching to VTY and back. See this thread: http://lists.freebsd.org/pipermail/freebsd-current/2009-March/004968.html Firefox is unusable, but xterms are still usable. I have to reboot to get back to "normal" -Brandon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?179b97fb0903241631h76e8758dxd87900597a5cba4a>