linux-kernel - Re: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec

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 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:	Sun, 23 Dec 2012 12:51:33 +0100
From:	Markus Trippelsdorf <markus@...ppelsdorf.de>
To:	Borislav Petkov <bp@...en8.de>, Andy Furniss <andyqos@...sn.org>,
	Alex Deucher <alexdeucher@...il.com>,
	Alex Deucher <alexander.deucher@....com>,
	dri-devel@...ts.freedesktop.org,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec

On 2012.12.23 at 12:31 +0100, Borislav Petkov wrote:
> On Sun, Dec 23, 2012 at 11:19:00AM +0000, Andy Furniss wrote:
> > modinfo radeon
> > 
> > will give a list assuming you use modules, I think all of them need =<num>.
> 
> Yep, that is one way of getting that info, thanks. I always go and look
> at Documentation/kernel-parameters.txt and forget about modinfo.
> 
> As you say 'radeon' needs to be module but since this is the case with
> the distros, the majority of Linux installations out there have it this
> way so we're fine.

(If you don't use modules:
 git grep MODULE_PARM_DESC -- drivers/gpu/drm/radeon/
)

You may have hit the same issue as I, see:
http://thread.gmane.org/gmane.comp.video.dri.devel/78328

Reverting commit 2d6cc729 fixes the problem for me, setting
radeon.no_wb=1 doesn't help.

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