From: Borislav Petkov <bp@alien8.de>
To: Andy Furniss <andyqos@ukfsn.org>
Cc: Alex Deucher <alexdeucher@gmail.com>,
Alex Deucher <alexander.deucher@amd.com>,
dri-devel@lists.freedesktop.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec
Date: Sun, 23 Dec 2012 12:31:53 +0100 [thread overview]
Message-ID: <20121223113153.GA8918@liondog.tnic> (raw)
In-Reply-To: <50D6E8A4.1030204@ukfsn.org>
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.
Btw, there's a typo in the param list, if anyone wants to write a patch
for it :-):
parm: lockup_timeout:GPU lockup timeout in ms (defaul 10000 = 10 seconds, 0 = disable) (int)
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2012-12-23 11:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 20:35 radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec Borislav Petkov
2012-12-23 0:01 ` Alex Deucher
2012-12-23 0:25 ` Borislav Petkov
2012-12-23 0:42 ` Alex Deucher
2012-12-23 10:55 ` Borislav Petkov
2012-12-23 11:01 ` Andy Furniss
2012-12-23 11:07 ` Borislav Petkov
2012-12-23 11:19 ` Andy Furniss
2012-12-23 11:31 ` Borislav Petkov [this message]
2012-12-23 11:51 ` Markus Trippelsdorf
2012-12-23 12:22 ` Borislav Petkov
2012-12-23 13:31 ` Borislav Petkov
2012-12-25 4:50 ` Shuah Khan
2012-12-25 10:54 ` Borislav Petkov
2013-01-02 1:42 ` Antti Palosaari
2013-01-02 12:02 ` Borislav Petkov
2013-01-02 17:19 ` Jerome Glisse
2013-01-02 17:58 ` Antti Palosaari
2013-01-02 22:31 ` Jerome Glisse
2013-01-02 22:38 ` Markus Trippelsdorf
2013-01-02 23:37 ` Alex Deucher
2013-01-02 23:58 ` Shuah Khan
2013-01-02 23:59 ` Alex Deucher
2013-01-03 1:03 ` Antti Palosaari
2013-01-03 1:05 ` Shuah Khan
2013-01-03 8:33 ` Markus Trippelsdorf
2013-01-03 11:37 ` Boszormenyi Zoltan
2013-01-03 14:12 ` Deucher, Alexander
2013-01-03 15:30 ` Shuah Khan
2013-01-04 7:40 ` Borislav Petkov
2013-01-04 11:16 ` Boszormenyi Zoltan
2013-01-04 14:06 ` Alex Deucher
2012-12-23 11:52 ` Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2013-01-10 9:38 Borislav Petkov
2013-01-10 16:21 ` Alex Deucher
2013-01-10 20:32 ` Borislav Petkov
2013-01-10 20:47 ` Alex Deucher
2013-01-11 11:43 ` Borislav Petkov
2013-01-15 12:19 ` Borislav Petkov
2013-01-15 14:04 ` Alex Deucher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121223113153.GA8918@liondog.tnic \
--to=bp@alien8.de \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=andyqos@ukfsn.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox