linux-kernel - Re: [2/6] 2.6.21-rc2: known regressions

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: <Pine.LNX.4.64.0703090949140.10832@woody.linux-foundation.org>
Date:	Fri, 9 Mar 2007 10:00:49 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	"Michael S. Tsirkin" <mst@...lanox.co.il>,
	Adrian Bunk <bunk@...sta.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jens Axboe <jens.axboe@...cle.com>,
	Jeff Chua <jeff.chua.linux@...il.com>, pavel@...e.cz,
	linux-pm@...ts.osdl.org, lenb@...nel.org,
	linux-acpi@...r.kernel.org, luming.yu@...el.com,
	Arkadiusz Miskiewicz <arekm@...en.pl>,
	Konstantin Karasyov <konstantin.a.karasyov@...el.com>,
	Greg KH <greg@...ah.com>,
	linux-usb-devel@...ts.sourceforge.net,
	Thomas Meyer <thomas.mey@....de>, Meelis Roos <mroos@...ux.ee>,
	Alexey Starikovskiy <alexey.y.starikovskiy@...ux.intel.com>,
	Janosch Machowinski <jmachowinski@....de>,
	vladimir.p.lebedev@...el.com,
	Ash Milsted <thatistosayiseenem@...ab.com>,
	dmitry.torokhov@...il.com, linux-input@...ey.karlin.mff.cuni.cz,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [2/6] 2.6.21-rc2: known regressions



On Fri, 9 Mar 2007, Ingo Molnar wrote:
> > Some day we may have modesetting support in the kernel for some 
> > graphics hw, right now it's pretty damn spotty.
> 
> having no video is what i'd have expected - but getting a /hang/ is not 
> what i'd have expected.

I debugged a case exactly like this (with the TRACE_RESUME() thing) back 
last November on my laptop.

The problem is that radeonfb actually *tries* to re-initialize the 
graphics chips, but because it doesn't know all the details, it does it 
wrong, and hangs the whole chip.

I forget exactly where it happened, and it might well be different for 
you. But this is exactly what TRACE_RESUME can be used to pinpoint if you 
want to try to debug it. 

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