Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1279220 > unrolled thread
| Started by | Pavel Machek <pavel@ucw.cz> |
|---|---|
| First post | 2015-11-28 22:00 +0100 |
| Last post | 2015-12-02 04:20 +0100 |
| Articles | 5 — 3 participants |
Back to article view | Back to linux.kernel
[radeon r100] when ring test fails, provide users with option to test Pavel Machek <pavel@ucw.cz> - 2015-11-28 22:00 +0100
Re: [radeon r100] when ring test fails, provide users with option to test Pavel Machek <pavel@ucw.cz> - 2015-11-29 23:30 +0100
Re: [radeon r100] when ring test fails, provide users with option to test Christian König <christian.koenig@amd.com> - 2015-11-30 09:50 +0100
Re: [radeon r100] when ring test fails, provide users with option to test Pavel Machek <pavel@ucw.cz> - 2015-12-01 11:10 +0100
Re: [radeon r100] when ring test fails, provide users with option to test Michel Dänzer <michel@daenzer.net> - 2015-12-02 04:20 +0100
| From | Pavel Machek <pavel@ucw.cz> |
|---|---|
| Date | 2015-11-28 22:00 +0100 |
| Subject | [radeon r100] when ring test fails, provide users with option to test |
| Message-ID | <qzUL7-5iU-5@gated-at.bofh.it> |
Ring test failure is often caused by too high agpmode. Tell the user
what to try.
Signed-off-by: Pavel Machek <pavel@ucw.cz>
diff --git a/drivers/gpu/drm/radeon/r100.c b/drivers/gpu/drm/radeon/r100.c
index 238b13f..32b1917 100644
--- a/drivers/gpu/drm/radeon/r100.c
+++ b/drivers/gpu/drm/radeon/r100.c
@@ -3665,7 +3665,7 @@ int r100_ring_test(struct radeon_device *rdev, struct radeon_ring *ring)
if (i < rdev->usec_timeout) {
DRM_INFO("ring test succeeded in %d usecs\n", i);
} else {
- DRM_ERROR("radeon: ring test failed (scratch(0x%04X)=0x%08X)\n",
+ DRM_ERROR("radeon: ring test failed (scratch(0x%04X)=0x%08X), try radeon.agpmode=1?\n",
scratch, tmp);
r = -EINVAL;
}
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[toc] | [next] | [standalone]
| From | Pavel Machek <pavel@ucw.cz> |
|---|---|
| Date | 2015-11-29 23:30 +0100 |
| Subject | Re: [radeon r100] when ring test fails, provide users with option to test |
| Message-ID | <qAiDM-3uF-5@gated-at.bofh.it> |
| In reply to | #1279220 |
On Sun 2015-11-29 20:48:53, Christian König wrote:
> On 28.11.2015 21:58, Pavel Machek wrote:
> >Ring test failure is often caused by too high agpmode. Tell the user
> >what to try.
> >
> >Signed-off-by: Pavel Machek <pavel@ucw.cz>
>
> NAK, the ring test can fail for any number of reasons and the agpmode is
> actually rather unlikely to be the cause.
Well, when I asked on the list "why this is happened" I got "umm,
noone knows" response that was not exactly helpful. And then someone
told me about agpmode.
If you know about the reasons it can fail, could you list them near
the DRM_ERROR, at least as a comment?
Thanks,
Pavel
> Regards,
> Christian.
>
> >
> >diff --git a/drivers/gpu/drm/radeon/r100.c b/drivers/gpu/drm/radeon/r100.c
> >index 238b13f..32b1917 100644
> >--- a/drivers/gpu/drm/radeon/r100.c
> >+++ b/drivers/gpu/drm/radeon/r100.c
> >@@ -3665,7 +3665,7 @@ int r100_ring_test(struct radeon_device *rdev, struct radeon_ring *ring)
> > if (i < rdev->usec_timeout) {
> > DRM_INFO("ring test succeeded in %d usecs\n", i);
> > } else {
> >- DRM_ERROR("radeon: ring test failed (scratch(0x%04X)=0x%08X)\n",
> >+ DRM_ERROR("radeon: ring test failed (scratch(0x%04X)=0x%08X), try radeon.agpmode=1?\n",
> > scratch, tmp);
> > r = -EINVAL;
> > }
> >
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | Christian König <christian.koenig@amd.com> |
|---|---|
| Date | 2015-11-30 09:50 +0100 |
| Subject | Re: [radeon r100] when ring test fails, provide users with option to test |
| Message-ID | <qAsjM-1hf-23@gated-at.bofh.it> |
| In reply to | #1279470 |
On 29.11.2015 23:22, Pavel Machek wrote:
> On Sun 2015-11-29 20:48:53, Christian König wrote:
>> On 28.11.2015 21:58, Pavel Machek wrote:
>>> Ring test failure is often caused by too high agpmode. Tell the user
>>> what to try.
>>>
>>> Signed-off-by: Pavel Machek <pavel@ucw.cz>
>> NAK, the ring test can fail for any number of reasons and the agpmode is
>> actually rather unlikely to be the cause.
> Well, when I asked on the list "why this is happened" I got "umm,
> noone knows" response that was not exactly helpful. And then someone
> told me about agpmode.
>
> If you know about the reasons it can fail, could you list them near
> the DRM_ERROR, at least as a comment?
Well as I said, that could be any number of reasons. Some of them even
completely unrelated to the driver itself.
E.g. BIOS setting, faulty hardware, problems with the writeback etc...
There is really not a list you could give here.
Lowering the agpmode usually helps more to prevent random corruptions
and problems under load.
Regards,
Christian.
>
> Thanks,
> Pavel
>
>> Regards,
>> Christian.
>>
>>> diff --git a/drivers/gpu/drm/radeon/r100.c b/drivers/gpu/drm/radeon/r100.c
>>> index 238b13f..32b1917 100644
>>> --- a/drivers/gpu/drm/radeon/r100.c
>>> +++ b/drivers/gpu/drm/radeon/r100.c
>>> @@ -3665,7 +3665,7 @@ int r100_ring_test(struct radeon_device *rdev, struct radeon_ring *ring)
>>> if (i < rdev->usec_timeout) {
>>> DRM_INFO("ring test succeeded in %d usecs\n", i);
>>> } else {
>>> - DRM_ERROR("radeon: ring test failed (scratch(0x%04X)=0x%08X)\n",
>>> + DRM_ERROR("radeon: ring test failed (scratch(0x%04X)=0x%08X), try radeon.agpmode=1?\n",
>>> scratch, tmp);
>>> r = -EINVAL;
>>> }
>>>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | Pavel Machek <pavel@ucw.cz> |
|---|---|
| Date | 2015-12-01 11:10 +0100 |
| Subject | Re: [radeon r100] when ring test fails, provide users with option to test |
| Message-ID | <qAQ2K-8fo-21@gated-at.bofh.it> |
| In reply to | #1279692 |
On Mon 2015-11-30 09:39:54, Christian König wrote:
> On 29.11.2015 23:22, Pavel Machek wrote:
> >On Sun 2015-11-29 20:48:53, Christian König wrote:
> >>On 28.11.2015 21:58, Pavel Machek wrote:
> >>>Ring test failure is often caused by too high agpmode. Tell the user
> >>>what to try.
> >>>
> >>>Signed-off-by: Pavel Machek <pavel@ucw.cz>
> >>NAK, the ring test can fail for any number of reasons and the agpmode is
> >>actually rather unlikely to be the cause.
> >Well, when I asked on the list "why this is happened" I got "umm,
> >noone knows" response that was not exactly helpful. And then someone
> >told me about agpmode.
> >
> >If you know about the reasons it can fail, could you list them near
> >the DRM_ERROR, at least as a comment?
>
> Well as I said, that could be any number of reasons. Some of them even
> completely unrelated to the driver itself.
>
> E.g. BIOS setting, faulty hardware, problems with the writeback etc... There
> is really not a list you could give here.
>
> Lowering the agpmode usually helps more to prevent random corruptions and
> problems under load.
Take a look at
http://www.gossamer-threads.com/lists/linux/kernel/2197183
. I had a problem, you did not know how to debug it, but it already
happened to pebolle at tiscali ... and yes, it was agpmode. That
problem is clearly more common then you realize... So this should go
in.
Pavel
> >>>--- a/drivers/gpu/drm/radeon/r100.c
> >>>+++ b/drivers/gpu/drm/radeon/r100.c
> >>>@@ -3665,7 +3665,7 @@ int r100_ring_test(struct radeon_device *rdev, struct radeon_ring *ring)
> >>> if (i < rdev->usec_timeout) {
> >>> DRM_INFO("ring test succeeded in %d usecs\n", i);
> >>> } else {
> >>>- DRM_ERROR("radeon: ring test failed (scratch(0x%04X)=0x%08X)\n",
> >>>+ DRM_ERROR("radeon: ring test failed (scratch(0x%04X)=0x%08X), try radeon.agpmode=1?\n",
> >>> scratch, tmp);
> >>> r = -EINVAL;
> >>> }
> >>>
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | Michel Dänzer <michel@daenzer.net> |
|---|---|
| Date | 2015-12-02 04:20 +0100 |
| Subject | Re: [radeon r100] when ring test fails, provide users with option to test |
| Message-ID | <qB67v-1EX-5@gated-at.bofh.it> |
| In reply to | #1280721 |
On 01.12.2015 19:01, Pavel Machek wrote: > On Mon 2015-11-30 09:39:54, Christian König wrote: >> On 29.11.2015 23:22, Pavel Machek wrote: >>> On Sun 2015-11-29 20:48:53, Christian König wrote: >>>> On 28.11.2015 21:58, Pavel Machek wrote: >>>>> Ring test failure is often caused by too high agpmode. Tell the user >>>>> what to try. >>>>> >>>>> Signed-off-by: Pavel Machek <pavel@ucw.cz> >>>> NAK, the ring test can fail for any number of reasons and the agpmode is >>>> actually rather unlikely to be the cause. >>> Well, when I asked on the list "why this is happened" I got "umm, >>> noone knows" response that was not exactly helpful. And then someone >>> told me about agpmode. >>> >>> If you know about the reasons it can fail, could you list them near >>> the DRM_ERROR, at least as a comment? >> >> Well as I said, that could be any number of reasons. Some of them even >> completely unrelated to the driver itself. >> >> E.g. BIOS setting, faulty hardware, problems with the writeback etc... There >> is really not a list you could give here. >> >> Lowering the agpmode usually helps more to prevent random corruptions and >> problems under load. > > Take a look at > > http://www.gossamer-threads.com/lists/linux/kernel/2197183 > > . I had a problem, you did not know how to debug it, but it already > happened to pebolle at tiscali ... and yes, it was agpmode. That > problem is clearly more common then you realize... So this should go > in. I agree with Christian, but at the very least, agpmode must not be mentioned if AGP isn't being used in the first place, i.e. either the GPU isn't AGP or is being forced to PCI(e) mode. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web