linux-kernel - Re: [Bug #28102] New display errors in 2.6.38-rc2-00175-g6fb1b30

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]

Message-ID: <20110203105319.2711b1db@jbarnes-desktop>
Date:	Thu, 3 Feb 2011 10:53:19 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Nico Schottelius <nico-kernel-20110117@...ottelius.org>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Maciej Rutecki <maciej.rutecki@...il.com>,
	Florian Mickler <florian@...kler.org>
Subject: Re: [Bug #28102] New display errors in 2.6.38-rc2-00175-g6fb1b30

On Thu, 3 Feb 2011 19:44:12 +0100
Nico Schottelius <nico-kernel-20110117@...ottelius.org> wrote:

> Jesse Barnes [Thu, Feb 03, 2011 at 10:11:11AM -0800]:
> > On Thu,  3 Feb 2011 00:31:29 +0100 (CET)
> > "Rafael J. Wysocki" <rjw@...k.pl> wrote:
> > 
> > > This message has been generated automatically as a part of a summary report
> > > of recent regressions.
> > > 
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.37.  Please verify if it still should be listed and let the tracking team
> > > know (either way).
> > > 
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=28102
> > > Subject		: New display errors in 2.6.38-rc2-00175-g6fb1b30
> > > Submitter	: Nico Schottelius <nico-kernel-20110117@...ottelius.org>
> > > Date		: 2011-01-28 20:29 (6 days old)
> > > Message-ID	: <20110128202905.GB3395@...ottelius.org>
> > > References	: http://marc.info/?l=linux-kernel&m=129624657425949&w=2
> > 
> > Does this also occur with the drm-intel-next branch? 
> 
> Didn't try this one, went back to 2.6.37-rc4-00292-g3c8cdf9 now.
> 
> I thought about following the bisect way, should I go a different
> one better?

Bisect would also be fine.

> > Do you have a picture of the corruption?
> 
> Not yet, can do one next time. Though I found one that looks
> very similar to my corruption:
> 
> http://i759.photobucket.com/albums/xx239/ericfx1984/DSCF2469.jpg

Interesting, ok.

-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/