From owner-freebsd-current@FreeBSD.ORG Wed Mar 25 20:53:52 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FA73106566C; Wed, 25 Mar 2009 20:53:52 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id 064338FC15; Wed, 25 Mar 2009 20:53:51 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from [192.168.1.156] (adsl-156-31-142.bna.bellsouth.net [70.156.31.142]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id n2PKqTrd031082 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 25 Mar 2009 16:52:30 -0400 (EDT) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: Brandon Gooch In-Reply-To: <179b97fb0903250821g44aa9aceq7568abc90f0d5cf9@mail.gmail.com> 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> <179b97fb0903241631h76e8758dxd87900597a5cba4a@mail.gmail.com> <1237950378.1829.13.camel@balrog.2hip.net> <179b97fb0903250821g44aa9aceq7568abc90f0d5cf9@mail.gmail.com> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-D8o92gBuUEIuqDLztgWV" Organization: FreeBSD Date: Wed, 25 Mar 2009 15:53:24 -0500 Message-Id: <1238014404.1828.27.camel@balrog.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.24.5 FreeBSD GNOME Team Port X-Spam-Status: No, score=-3.2 required=5.0 tests=AWL,BAYES_00,RDNS_DYNAMIC autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: freebsd-current@freebsd.org, Jung-uk Kim Subject: Re: [HEADSUP] amd64 suspend/resume code to be comitted X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Mar 2009 20:53:52 -0000 --=-D8o92gBuUEIuqDLztgWV Content-Type: multipart/mixed; boundary="=-R4F87V/cUFXsZbQ+idcN" --=-R4F87V/cUFXsZbQ+idcN Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2009-03-25 at 10:21 -0500, Brandon Gooch wrote: > On Tue, Mar 24, 2009 at 10:06 PM, Robert Noland wro= te: > > On Tue, 2009-03-24 at 18:31 -0500, Brandon Gooch wrote: > >> On Tue, Mar 24, 2009 at 4:14 PM, Adam McDougall = wrote: > >> > Brandon Gooch wrote: > >> >> > >> >> On Mon, Mar 23, 2009 at 4:28 PM, Jung-uk Kim wro= te: > >> >> > >> >>> > >> >>> On Monday 23 March 2009 05:16 pm, Brandon Gooch wrote: > >> >>> > >> >>>> > >> >>>> The committed version is working well, I am suspending and resumi= ng > >> >>>> 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! In the past (months ago) I tried the = patch > >> > set which didn't work, but the code in -current lets me suspend and = resume > >> > successfully on my Dell Latitude E6500 (acpiconf -s 3)! I think thi= s is 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 jeal= ous of > >> > the Thinkpad users that could claim otherwise. I could suspend and = resume > >> > fine while in the console, then I ran startx and the suspend and res= ume > >> > worked while I was in X with intel graphics, however my system was s= low > >> > after that resume. I didn't spend much time looking at it since I w= as at > >> > work, and I didn't see any obvious reasons for the slowness (cpu fre= quency > >> > was fine, cx states were C2 or lower (C1), top showed mostly idle, n= o > >> > evidence of an IRQ storm) yet processes ran fairly sluggish (not the= mouse > >> > or typing though). I didn't go back to console, I just shut down wi= thout > >> > trying any other situations yet. > >> > > >> > A tip I want to note for any users who may not have success with the= ir > >> > screen on resume: In 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 re= sume to > >> > ask me for my password. I 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@freebs= d.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. > > > > I just committed code that should fix this... > > > > robert. > > > >> See this thread: > >> http://lists.freebsd.org/pipermail/freebsd-current/2009-March/004968.h= tml > >> > >> Firefox is unusable, but xterms are still usable. I have to reboot to > >> get back to "normal" > >> > >> -Brandon > >> _______________________________________________ > >> 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" > > -- > > Robert Noland > > FreeBSD > > >=20 > It seems to have helped -- slightly. Firefox is still too laggy when > interacting with interface elements (scrollbar, toolbars, menus), and > typing within HTML textboxes. XTerm, xpdf, xcalc, etc are still OK to > use, perhaps because they're not as graphically intensive :) >=20 > Also, it seems to have broken the suspend/resume. The machine does > wake up, but X is no longer there (I'm at the VTY from which I started > X) and I can't switch to another VTY. The machine still "works" for a > period, but attempts to switch VTY or enter commands from the keyboard > eventually lock it up, resulting in a continuous beep tone and > requiring a hard power-off (holding down the power button). Can you try the attached patch? This was a last minute change that I made and I don't know why it seems to be upsetting things so, but it looks like it causes things to not shutdown properly. It looks like it isn't safe to suspend with / on usb2, so I can't really test s/r still... robert. > -Brandon --=20 Robert Noland FreeBSD --=-R4F87V/cUFXsZbQ+idcN Content-Disposition: attachment; filename="drm_irq.patch" Content-Transfer-Encoding: base64 Content-Type: text/x-patch; name="drm_irq.patch"; charset="us-ascii" SW5kZXg6IGRldi9kcm0vZHJtX2lycS5jDQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQotLS0gZGV2L2RybS9kcm1faXJx LmMJKHJldmlzaW9uIDE5MDQyMCkNCisrKyBkZXYvZHJtL2RybV9pcnEuYwkod29ya2luZyBjb3B5 KQ0KQEAgLTQ2MywxNiArNDYzLDE5IEBADQogCX0gZWxzZSB7DQogCQlEUk1fREVCVUcoIndhaXRp bmcgb24gdmJsYW5rIGNvdW50ICVkLCBjcnRjICVkXG4iLA0KIAkJICAgIHZibHdhaXQtPnJlcXVl c3Quc2VxdWVuY2UsIGNydGMpOw0KLQkJbXR4X2xvY2soJmRldi0+aXJxX2xvY2spOw0KIAkJZGV2 LT52YmxhbmtbY3J0Y10ubGFzdCA9IHZibHdhaXQtPnJlcXVlc3Quc2VxdWVuY2U7DQogCQlmb3Ig KCByZXQgPSAwIDsgIXJldCAmJiAhKCgoZHJtX3ZibGFua19jb3VudChkZXYsIGNydGMpIC0NCiAJ CSAgICB2Ymx3YWl0LT5yZXF1ZXN0LnNlcXVlbmNlKSA8PSAoMSA8PCAyMykpIHx8DQogCQkgICAg IWRldi0+aXJxX2VuYWJsZWQpIDsgKSB7DQotCQkJcmV0ID0gbXR4X3NsZWVwKCZkZXYtPnZibGFu a1tjcnRjXS5xdWV1ZSwNCi0JCQkgICAgJmRldi0+aXJxX2xvY2ssIFBDQVRDSCwgInZibHd0cSIs DQotCQkJICAgIDMgKiBEUk1fSFopOw0KKwkJCW10eF9sb2NrKCZkZXYtPmlycV9sb2NrKTsNCisJ CQlpZiAoISgoKGRybV92YmxhbmtfY291bnQoZGV2LCBjcnRjKSAtDQorCQkJICAgIHZibHdhaXQt PnJlcXVlc3Quc2VxdWVuY2UpIDw9ICgxIDw8IDIzKSkgfHwNCisJCQkgICAgIWRldi0+aXJxX2Vu YWJsZWQpKQ0KKwkJCQlyZXQgPSBtdHhfc2xlZXAoJmRldi0+dmJsYW5rW2NydGNdLnF1ZXVlLA0K KwkJCQkgICAgJmRldi0+aXJxX2xvY2ssIFBDQVRDSCwgInZibHd0cSIsDQorCQkJCSAgICAzICog RFJNX0haKTsNCisJCQltdHhfdW5sb2NrKCZkZXYtPmlycV9sb2NrKTsNCiAJCX0NCi0JCW10eF91 bmxvY2soJmRldi0+aXJxX2xvY2spOw0KIA0KIAkJaWYgKHJldCAhPSBFSU5UUiAmJiByZXQgIT0g RVJFU1RBUlQpIHsNCiAJCQlzdHJ1Y3QgdGltZXZhbCBub3c7DQo= --=-R4F87V/cUFXsZbQ+idcN-- --=-D8o92gBuUEIuqDLztgWV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEABECAAYFAknKmcQACgkQM4TrQ4qfRON6HACfUp9rkDNC1jBzgDkcCMbOymvQ iSoAnjS+LVK2L3t5yvDHDY50chZPIjxV =GZsb -----END PGP SIGNATURE----- --=-D8o92gBuUEIuqDLztgWV--