linux-kernel - Re: [DRM] Lower the severity of the radeon lockup messages.

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] [day] [month] [year] [list]

Message-ID: <alpine.LRH.2.00.1110220317580.30600@kibblesnbits.boston.devel.redhat.com>
Date:	Sat, 22 Oct 2011 03:19:37 -0400 (EDT)
From:	David Airlie <airlied@...hat.com>
To:	Robert Hancock <hancockrwd@...il.com>
cc:	Dave Jones <davej@...hat.com>, airlied@...hat.com,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [DRM] Lower the severity of the radeon lockup messages.

>
> At the risk of sounding obvious, wouldn't it be better to enhance the driver 
> to dump out more useful debugging info in this case rather than just 
> suppressing the ABRT report?

In theory yes, in practice that is non-trivial. The amount of data you 
need to keep track off is in the MBs, it can range from any previous GPU 
command stream sent to the GPU, to the contents of any of the vertex 
buffers etc.

the problem with GPU lockups is you don't notice them until after you've 
queued up a tonne more stuff since they are such deep pipelines.

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