Date: Thu, 9 Oct 2014 06:04:30 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Koop Mast <kwm@rainbow-runner.nl> Cc: Konstantin Belousov <kostikbel@gmail.com>, x11@freebsd.org, current@freebsd.org Subject: Re: i915 driver update testing Message-ID: <20141009060430.46fc9b47.ohartman@zedat.fu-berlin.de> In-Reply-To: <1412538862.1608.2.camel@rainbow-runner.nl> References: <20141003170258.GG26076@kib.kiev.ua> <1412538862.1608.2.camel@rainbow-runner.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/xQ4P+S9Rp/CrAgehyQBVaoM Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Sun, 05 Oct 2014 21:54:22 +0200 Koop Mast <kwm@rainbow-runner.nl> schrieb: > On Fri, 2014-10-03 at 20:02 +0300, Konstantin Belousov wrote: > > Please find at the > > https://kib.kiev.ua/kib/drm/i915.1.patch > > a patch which provides some updates to the i915 driver. At large, this > > is import of the batch of Linux commits, and as such, it is interesting > > mostly as attempt to restart the race to get us more up to date Linux c= ode > > imported. It might provide some bug fixes, most likely for IvyBridge. > > Interesting from the development PoV is the update of the GEM i/o ioctl > > code path to mimic Linux code structure. > >=20 > > I am asking _only_ for reports of regressions with the patch applied, > > comparing with the code which is currently in HEAD. I will not debug > > any existing bugs, my goal right now is to commit this update, which is > > needed for further work. I.e., only when you get an issue with the patch > > applied, but cannot reproduce the problem without the patch, please > > prepare a bug report. > >=20 > > FYI, the driver will attach to haswell gfx, but I am not interested in > > reports about this (see above paragraph). On my test box, which is Core > > i7 4770S, the mode-setting and front-buffer rendering works, but Mesa > > immediately cause renderer to bug out. > >=20 > > Work was sponsored by The FreeBSD Foundation, both by time and hardware, > > and Intel provided access to the documentation. >=20 > Hi, I got a working X-server and framebuffer console on my Sandybridge > system. The only regression I noticed so far is the line below, where > the number after 'expected' changes per time the line is printed.=20 >=20 > Oct 5 21:50:12 crashalot kernel: error: [drm:pid1049:gen6_sanitize_pm] > *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected > 160d0000, was 16000000 > Oct 5 21:51:04 crashalot kernel: error: [drm:pid1049:gen6_sanitize_pm] > *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected > 160d0000, was 16000000 > Oct 5 21:53:14 crashalot kernel: error: [drm:pid1170:gen6_sanitize_pm] > *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected > 160d0000, was 16000000 >=20 > _______________________________________________ > 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" Is this patch supposed to work also with IvyBridge type iGPUs, i.w. P4600 (= the iGPU of some XEONs of the i5-122Xv2 series)? When I load drm2 and i915kms via loader.conf, the box gets black screen and= then dies. Oliver=20 --Sig_/xQ4P+S9Rp/CrAgehyQBVaoM Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJUNglSAAoJEOgBcD7A/5N8N7QH/04Ci1mH3BgAB5LCNhYpCK4D 260xmc20mcbxsHm0dlTDMS2D8Do5N0GeJJjCtA7azOwzr3rIL8L7KKg9e014c3cZ VattGKhXH2tz6Cd5g9DDGIvd8nYR4ox7cYGt6zeKQxY24Qywijk6PKm1uaPn/bXW vE7t9s7YJLaLXfXOofqN4wayiVg2KXBbizgdfla0fNGNJflTvO2sbk1AD1g4awU5 UPAyT+2iOblAnGVIWdoo/fLxss5fVYPBb9zru6WWwFVzhgn2VuVsdLXBIbC949+0 LaJNwvE1DLtdyCykSbGqLkxgjhjHphrse1vAqc80e1KMlQ4aOGJgd+KJ9Sw3akU= =osiG -----END PGP SIGNATURE----- --Sig_/xQ4P+S9Rp/CrAgehyQBVaoM--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141009060430.46fc9b47.ohartman>