Date: Fri, 27 Mar 2009 02:59:28 -0500 From: Robert Noland <rnoland@FreeBSD.org> To: Brandon Gooch <jamesbrandongooch@gmail.com> Cc: Michiel Boland <michiel@boland.org>, FreeBSD Current <freebsd-current@freebsd.org>, Mattia Rossi <mrossi@swin.edu.au> Subject: Re: still problems with intel video Message-ID: <1238140768.8491.180.camel@balrog.2hip.net> In-Reply-To: <179b97fb0903270014u12e5fd10w46a18c36efa9ddf8@mail.gmail.com> References: <49CB70BD.3040607@boland.org> <1238086577.1792.30.camel@balrog.2hip.net> <49CC43C4.7030905@swin.edu.au> <1238126285.8491.2.camel@balrog.2hip.net> <179b97fb0903262114i511ec294ief17475d673e70c9@mail.gmail.com> <1238136987.8491.173.camel@balrog.2hip.net> <179b97fb0903270014u12e5fd10w46a18c36efa9ddf8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-CCQG4pzXVicppDRHYc/O Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2009-03-27 at 02:14 -0500, Brandon Gooch wrote: > On Fri, Mar 27, 2009 at 1:56 AM, Robert Noland <rnoland@freebsd.org> wrot= e: > > On Thu, 2009-03-26 at 23:14 -0500, Brandon Gooch wrote: > >> On Thu, Mar 26, 2009 at 10:58 PM, Robert Noland <rnoland@freebsd.org> = wrote: > >> > On Fri, 2009-03-27 at 14:11 +1100, Mattia Rossi wrote: > >> >> Robert Noland wrote: > >> >> > On Thu, 2009-03-26 at 13:10 +0100, Michiel Boland wrote: > >> >> > > >> >> >> Hi. I still have problems with a very slow display after logging= out of an X > >> >> >> session and/or switching VTYs. The problem goes away if I add > >> >> >> hw.pci.enable_msi=3D0 to /boot/loader.conf. > >> >> >> > >> >> >> Last csupped Mar 26 09:49 CET. > >> >> >> > >> >> >> System is Dell optiplex 745. Has built-in Intel Graphics Media A= ccelerator 950 > >> >> >> > >> >> >> Anything I can do to help solve this problem? > >> >> >> > >> >> > > >> >> > I'm going to try and work on getting better debugging info from t= he > >> >> > intel driver. I don't have access to any newer Intel hardware at= the > >> >> > moment, so testing is tricky. > >> >> > > >> >> > There is a tuneable for just msi on drm hw.drm.msi. > >> >> > > >> >> > robert. > >> >> > > >> >> > > >> >> Yep, correct - here it is again - just had to log out of KDE, and a= fter > >> >> logging in again, everything was slow as hell. > >> >> I didn't fiddle with the msi settings, just rebooted the machine, a= nd > >> >> everything is fine again. > >> >> So there must be something that works the first time X is started, = but > >> >> upon restart stuffs up. Like some lock or reference which is not fr= eed. > >> > > >> > There is a problem with restarting X on at least some Intel chips... > >> > This is a different issue, I was trying to look into that a little b= it > >> > yesterday, but it kinda works on this 915 that I have, so I haven't > >> > isolated what is getting messed up. Again, vt switch, suspend/resum= e > >> > are in the same ballpark, restart is not. > >> > > >> > robert. > >> > > >> >> Mat > >> >> >> _______________________________________________ > >> >> >> freebsd-current@freebsd.org mailing list > >> >> >> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >> >> >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@fr= eebsd.org" > >> >> >> > >> >> > >> > -- > >> > Robert Noland <rnoland@FreeBSD.org> > >> > FreeBSD > >> > > >> > >> I have been switching to the vty at which I started X in order to > >> terminate X. If I try to terminate X while I'm in it, it just "hangs" > >> -- I have to switch to the vty, ctrl-c it, wait, then blindly key in a > >> reboot to get my system back up. IIRC, this started happening after I > >> upgraded to Xorg 7.4. > >> > >> I thought that Mattia might be doing the same thing as a work-around > >> for the freezing intel-driven display thing, thus the X-to-vty switch > >> "fix" of disabling msi... > > > > Hrm, ok... So, vt switching on the I915 that I'm using to test(which > > doesn't support msi) works pretty much perfectly. Console is not > > corrupted, (unless I've restarted X at least once). Shutdown/reboot > > from gnome also works as expected. > > > > I did most of the msi development on an i965gm, which did support msi > > and vt switch also worked with msi at that time. Restart was > > problematic on the 965 then as well, which I believed to be an agp, or > > agp/drm interaction issue. So, unless some of the recent changes other > > than msi, have broken 965, they should be mostly working ok as long as > > you don't restart. > > > > The g31 and g45 are slightly different and all of my work for those has > > been based on what Intel has released for linux and the small amount of > > documentation that is available at this point. > > > > BTW, you debug output looks strange to me, did you also capture the drm > > debug log from hw.dri.0.debug=3D1? > > > > robert. > > > >> -Brandon > > -- > > Robert Noland <rnoland@FreeBSD.org> > > FreeBSD > > >=20 > I've attached a copy of my /var/log/messages file after enabling > hw.dri.0.debug, suspending, and then resuming. I disable it shortly > after resume is complete. Ok, this is somewhat enlightening... I'll have a closer look tomorrow, but it is most disturbing to see it continuing to render after the suspend call, especially after the interrupt handler is yanked out. robert. > -Brandon --=20 Robert Noland <rnoland@FreeBSD.org> FreeBSD --=-CCQG4pzXVicppDRHYc/O 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) iEYEABECAAYFAknMh2AACgkQM4TrQ4qfROOcUgCeJfkLrdviYg1KTDTzKIRYwfME Q7IAnj6LBqoZmkVq81Z6I29P1zIRrQqA =6tvK -----END PGP SIGNATURE----- --=-CCQG4pzXVicppDRHYc/O--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1238140768.8491.180.camel>