lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 21 Mar 2010 16:30:20 +0100 From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com> To: Zhenyu Wang <zhenyuw@...ux.intel.com>, Miguel Ojeda <miguel.ojeda.sandonis@...il.com>, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, David.Woodhouse@...el.com, dwmw2@...radead.org, eric@...olt.net, ben@...adent.org.uk, gregkh@...e.de Subject: Re: [PATCH] intel-agp.c: Fix crash when accessing nonexistent GTT entries in i915 On Sun, Mar 21, 2010 at 2:58 PM, Zhenyu Wang <zhenyuw@...ux.intel.com> wrote: > On 2010.03.20 14:04:56 +0100, Miguel Ojeda wrote: >> On Fri, Mar 19, 2010 at 9:27 PM, Andrew Morton >> <akpm@...ux-foundation.org> wrote: >> > On Thu, 11 Mar 2010 16:54:26 +0100 >> > Miguel Ojeda <miguel.ojeda.sandonis@...il.com> wrote: >> > >> >> Attached dmesg, lspci -vv, config and xorg. >> >> >> >> When the X server crashes, the kernel does not report anything >> > >> > This seems to have gone all quiet? >> >> It seems so, I was about to ping Zhenyu. > > Could you try recent X.org intel driver release? Your failure X log > showed some pretty old UMS driver's render flush time out message, > I think whose version never has been well tested with new kms/gem stuff. > Sure. Debian Stable got version 2.3. >> >> > >> > As this was a 2.6.32->2.6.32.4 regression, I assume that it's also a >> > 2.6.32->2.6.33 regression? >> >> Yep. All kernels I tested since 2.6.32.4 crash, including 2.6.32.10, >> 2.6.33 and 2.6.34-rc1. See my original message for more details about >> the crash. >> > > Could you bisect? I doubt it's caused by David's patch, as if it is, you > will have trouble at early agp init time, instead of current problem looks > like something causing rendering hang..and I can't think of how mapping GTT > to a scratch page could cause problem in case GTT bar is truely 256K. I bisected in order to find the commit 5877960869333e42ebeb733e8d9d5630ff96d350. I don't know if such commit is really the true problem (does not seem so if you are right); however, it is the commit that breaks the X server as I stated in the original message. > > -- > Open Source Technology Center, Intel ltd. > > $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827 > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAkumJgwACgkQsQQaM014GCe2cgCbB8LJnqn7n7J++lA8Pd+TfBQb > 2BQAn2sYv0DZuSniLTcf9F3cX+cGIgVl > =gQHY > -----END PGP SIGNATURE----- > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists