Re: Memory corruption starting in i915 code, in 3.2-rc5

2011-12-16 Thread Ben Widawsky
On 12/16/2011 11:22 AM, Keith Packard wrote: > On Tue, 13 Dec 2011 19:26:50 +0100, Daniel Vetter wrote: >> On Tue, Dec 13, 2011 at 10:14:46AM -0800, Keith Packard wrote: >>> On Tue, 13 Dec 2011 10:14:15 -0500, Alex Villací­s Lasso >>> wrote: >>> By using a bootable USB stick, I could check

Re: Memory corruption starting in i915 code, in 3.2-rc5

2011-12-16 Thread Keith Packard
On Tue, 13 Dec 2011 19:26:50 +0100, Daniel Vetter wrote: > On Tue, Dec 13, 2011 at 10:14:46AM -0800, Keith Packard wrote: > > On Tue, 13 Dec 2011 10:14:15 -0500, Alex Villací­s Lasso > > wrote: > > > > > By using a bootable USB stick, I could check the logs, which > > > showed many segfaults at

Re: Memory corruption starting in i915 code, in 3.2-rc5

2011-12-13 Thread Alex Villací­s Lasso
El 12/12/11 11:41, Keith Packard escribió: On Mon, 12 Dec 2011 09:51:19 -0500, Alex Villací­s Lasso wrote: Ran kernel with reverted patch for 6 hours without issues so far. Will keep testing after work (issue happens with my home machine). Thanks much. Let me know if it's still stable this e

Re: Memory corruption starting in i915 code, in 3.2-rc5

2011-12-13 Thread Daniel Vetter
On Tue, Dec 13, 2011 at 10:14:46AM -0800, Keith Packard wrote: > On Tue, 13 Dec 2011 10:14:15 -0500, Alex Villací­s Lasso > wrote: > > > By using a bootable USB stick, I could check the logs, which > > showed many segfaults at /lib64/ld-2.14.90.so . > > Ouch! > > Please let me know if you find

Re: Memory corruption starting in i915 code, in 3.2-rc5

2011-12-13 Thread Daniel Vetter
On Tue, Dec 13, 2011 at 10:14:46AM -0800, Keith Packard wrote: > On Tue, 13 Dec 2011 10:14:15 -0500, Alex Villací­s Lasso > wrote: > > > By using a bootable USB stick, I could check the logs, which > > showed many segfaults at /lib64/ld-2.14.90.so . > > Ouch! > > Please let me know if you find

Re: Memory corruption starting in i915 code, in 3.2-rc5

2011-12-13 Thread Keith Packard
On Tue, 13 Dec 2011 10:14:15 -0500, Alex Villací­s Lasso wrote: > By using a bootable USB stick, I could check the logs, which > showed many segfaults at /lib64/ld-2.14.90.so . Ouch! Please let me know if you find anything further; I'd like to get a revert sent upstream in the next day or so.

Re: Memory corruption starting in i915 code, in 3.2-rc5

2011-12-12 Thread Alex Villací­s Lasso
El 11/12/11 16:29, Alex Villacís Lasso escribió: El 11/12/11 15:46, Keith Packard escribió: On Sun, 11 Dec 2011 13:36:30 -0500, Alex Villacís Lasso wrote: My system is a Fedora 16 x86_64 running self-compiled vanilla kernel (.config attached for -rc5). I am getting an apparent memory corrupti

Re: Memory corruption starting in i915 code, in 3.2-rc5

2011-12-12 Thread Keith Packard
On Mon, 12 Dec 2011 09:51:19 -0500, Alex Villací­s Lasso wrote: > Ran kernel with reverted patch for 6 hours without issues so far. Will > keep testing after work (issue happens with my home machine). Thanks much. Let me know if it's still stable this evening; I can send a revert along if you d

Re: Memory corruption starting in i915 code, in 3.2-rc5

2011-12-11 Thread Alex Villacís Lasso
El 11/12/11 15:46, Keith Packard escribió: On Sun, 11 Dec 2011 13:36:30 -0500, Alex Villacís Lasso wrote: My system is a Fedora 16 x86_64 running self-compiled vanilla kernel (.config attached for -rc5). I am getting an apparent memory corruption that starts since linux 3.2-rc5. No such corrup

Re: Memory corruption starting in i915 code, in 3.2-rc5

2011-12-11 Thread Keith Packard
On Sun, 11 Dec 2011 13:36:30 -0500, Alex Villacís Lasso wrote: > My system is a Fedora 16 x86_64 running self-compiled vanilla kernel > (.config attached for -rc5). I am getting an apparent memory corruption > that starts since linux 3.2-rc5. No such corruption was noticed in > 3.2-rc4. On the