linux-kernel - Re: i915 regression in 2.6.29-rc5

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 19 Feb 2009 11:55:43 +0800
From:	Zhang Rui <rui.zhang@...el.com>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>,
	"jbarnes@...tuousgeek.org" <jbarnes@...tuousgeek.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: i915 regression in 2.6.29-rc5

On Thu, 2009-02-19 at 03:33 +0800, Yinghai Lu wrote:
> On Tue, Feb 17, 2009 at 7:24 PM, ZhangRui <rui.zhang@...el.com> wrote:
> > Hi, all,
> >
> > I got an i915 failure in 2.6.29-rc5.
> >
> > problem description: the screen doesn't come back after suspend/resume.
> > A workaround is to boot with "nomodesetting".
> >
> > I got this error message during i915 driver load time,
> > [   22.606749] mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining
> > [   22.606752] [drm] MTRR allocation failed
> > [   22.606753] .  Graphics performance may suffer.
> 
> CONFIG_MTRR_SANITIZER=y
> CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
> CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
> 
> may help this one.
> 
hah, it helps.
the screen is back with this, while my previous kernel option is same
except that CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0.

Btw: with jesse's patch applied, the symptom is exactly the same as the
one I stated in the previous email.

thanks,
rui

--
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/