linux-kernel - Re: [Bug #37752] Kernel Panic in drm_vblank_put+0x13/0x50 on P4 HT machine with 82915G/GV/910GL Integrated Graphics Controller

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 for Android: free password hash cracker in your pocket

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

Message-Id: <201106282346.17074.rjw@sisk.pl>
Date:	Tue, 28 Jun 2011 23:46:16 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Martin <marogge@...inehome.de>
Cc:	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 #37752] Kernel Panic in drm_vblank_put+0x13/0x50 on P4 HT machine with 82915G/GV/910GL Integrated Graphics Controller

On Tuesday, June 28, 2011, Martin wrote:
> On Monday 27 June 2011 00:35:16 Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.38 and 2.6.39.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.38 and 2.6.39.  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=37752
> > Subject		: Kernel Panic in drm_vblank_put+0x13/0x50 on P4 HT machine 
> with
> > 82915G/GV/910GL Integrated Graphics Controller Submitter	: Martin Rogge
> > <marogge@...inehome.de>
> > Date		: 2011-06-17 13:02 (10 days old)
> 
> As far as I can see the bug is still present in the 2.6.39 line. However. I 
> have good news. Out of a whim I've been trying 3.0-rc4 and the panic has not 
> occurred in a few days.
> 
> I can try and bisect which commit fixed the issue. I guess I have to reverse 
> the semantics of good and bad for this one. Don't tell the clergy.
> 
> Anyway, since it takes a while to establish the absence of a panic, don't 
> expect any results soon.

Well, we have a policy to close regression bugs that have been fixed in the
Linus' tree or don't appear in there at all, so I'll close this one too.

I you're able to identify the fix, please let the -stable maintainers know
about it.

Thanks,
Rafael
--
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/