[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 --- Comment #10 from Alex Deucher 2010-06-22 22:51:41 PDT --- (In reply to comment #7) > Ah, I had tried NoAccel previously with limited success, however with your > patch applied it works much better. The window manager and apps are visible > and > there is no lockup when I switch VT's. > > However, X does seg fault when I quit the wm. I have attached the backtrace > found the Xorg.log from that seg fault in case it is useful and the lspci > output you requested. > That might be fixed in xf86-video-ati from git master. As to the GPU lockup, You might try disabling EXA accel routines to see if you can narrow down the problem. E.g., Option "EXANoComposite" Option "EXANoDownloadFromScreen" Option "EXANoUploadToScreen" in the device section of your xorg config. > The connectors on the card are quite different from the generic connector > table > the driver seems to use. The connectors are DVI + ADC (Apple Display Connector > DVI+USB for Cinema Displays; it was available prior to 2005). In case it is > relevant, I am currently using the DVI outpt with a VGA adaptor since I ran > out > of DVI cables. > > Please let me know if I can provide anything else. We'll need to come up with a custom connector table. I will need your help testing to make sure I got the encoder and ddc line routing correct. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH] drm/radeon/kms: avoid oops on mac r4xx cards
They don't have an atombios so don't attempt to use it for
eng/mem clocks.
Reported by spoonb on #radeon
fixes:
https://bugs.freedesktop.org/show_bug.cgi?id=28671
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/radeon_asic.c |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_asic.c
b/drivers/gpu/drm/radeon/radeon_asic.c
index 87f7e2c..646f96f 100644
--- a/drivers/gpu/drm/radeon/radeon_asic.c
+++ b/drivers/gpu/drm/radeon/radeon_asic.c
@@ -780,6 +780,13 @@ int radeon_asic_init(struct radeon_device *rdev)
case CHIP_R423:
case CHIP_RV410:
rdev->asic = _asic;
+ /* handle macs */
+ if (rdev->bios == NULL) {
+ rdev->asic->get_engine_clock =
_legacy_get_engine_clock;
+ rdev->asic->set_engine_clock =
_legacy_set_engine_clock;
+ rdev->asic->get_memory_clock =
_legacy_get_memory_clock;
+ rdev->asic->set_memory_clock = NULL;
+ }
break;
case CHIP_RS400:
case CHIP_RS480:
--
1.7.0.1
[Bug 28655] [r300g] Regression caused by commit 9b2ebcaf4b94bfc8756f6b216e0e452013616f2c
https://bugs.freedesktop.org/show_bug.cgi?id=28655 Marek Ol??k changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
EDID checksum errors
Alex Deucher wrote: > On Tue, Jun 22, 2010 at 12:39 PM, Corbin Simpson > wrote: >> On Tue, Jun 22, 2010 at 9:05 AM, Octoploid >> wrote: >>> Octoploid wrote: >>> The following EDID checksum errors are spamming my syslog. (Everything is working fine and there are no other problems except these somewhat annoying messages): drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 >>> >>> This patch helps: >>> http://lists.freedesktop.org/archives/dri-devel/2010-April/000255.html >> >> Your monitor sucks. Don't take it personally; lots of monitors suck. >> That patch just gives you the option to forcibly use monitors with >> EDIDs that have bad checksums, in case the checksum is the only bad >> part of an otherwise valid EDID. > > IIRC, ajax sent a patch a while back to just ignore bad checksums > since they are so common. Yes, that is the patch I've linked to above. But it just papers over the problem. Where do the changing (corrupted) raw EDID blocks in my first message come from?
[Bug 28655] [r300g] Regression caused by commit 9b2ebcaf4b94bfc8756f6b216e0e452013616f2c
https://bugs.freedesktop.org/show_bug.cgi?id=28655 --- Comment #10 from Rub?n Fern?ndez 2010-06-22 19:19:12 PDT --- (In reply to comment #9) > I've committed a workaround, could you try current mesa git? It works perfectly again now! -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
EDID checksum errors
On Tue, Jun 22, 2010 at 7:07 PM, Alex Deucher wrote: > On Tue, Jun 22, 2010 at 12:39 PM, Corbin Simpson > wrote: >> On Tue, Jun 22, 2010 at 9:05 AM, Octoploid >> wrote: >>> Octoploid wrote: >>> The following EDID checksum errors are spamming my syslog. (Everything is working fine and there are no other problems except these somewhat annoying messages): drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 >>> >>> This patch helps: >>> http://lists.freedesktop.org/archives/dri-devel/2010-April/000255.html >> >> Your monitor sucks. Don't take it personally; lots of monitors suck. >> That patch just gives you the option to forcibly use ?monitors with >> EDIDs that have bad checksums, in case the checksum is the only bad >> part of an otherwise valid EDID. > > IIRC, ajax sent a patch a while back to just ignore bad checksums > since they are so common. Yes, that is the patch I've linked to above. But it just papers over the problem. Where do the changing (corrupted) raw EDID blocks in my first message come from?
Problems with alpha/pci + radeon/ttm
On Tue, Jun 22, 2010 at 3:59 PM, FUJITA Tomonori
wrote:
> On Mon, 21 Jun 2010 17:19:43 -0400
> Matt Turner wrote:
>
>> Michael Cree and I have been debugging FDO bug 26403 [1]. I tried
>> booting with `radeon.test=1` and found this, which I think is related:
>>
>> > [drm] Tested GTT->VRAM and VRAM->GTT copy for GTT offset 0x202000
>> > [drm] Tested GTT->VRAM and VRAM->GTT copy for GTT offset 0x302000
>> [snip]
>> > [drm] Tested GTT->VRAM and VRAM->GTT copy for GTT offset 0xfd02000
>> > [drm] Tested GTT->VRAM and VRAM->GTT copy for GTT offset 0xfe02000
>> > pci_map_single failed: could not allocate dma page tables
>> > [drm:radeon_ttm_backend_bind] *ERROR* failed to bind 128 pages at
>> > 0x0FF02000
>> > [TTM] Couldn't bind backend.
>> > radeon :00:07.0: object_init failed for (1048576, 0x0002)
>> > [drm:radeon_test_moves] *ERROR* Failed to create GTT object 253
>> > Error while testing BO move.
>>
>> From what I can see, the call chain is
>> radeon_test_moves
>> ?(radeon_ttm_backend_bind called through callback function)
>> ?- radeon_ttm.c:radeon_ttm_backend_bind calls radeon_gart_bind
>> ? - radeon_gart.c:radeon_gart_bind calls pci_map_page
>> ? ?- pci_map_page is alpha_pci_map_page, which calls...
>> ? ? - alpha_pci_map_page calls pci_iommu.c:pci_map_single_1
>> ? ? ?- pci_map_single_1 calls iommu_arena_alloc
>> ? ? ? - iommu_arena_alloc calls iommu_arena_find_pages
>> ? ? ? ?- iommu_arena_find_pages returns non-0
>> ? ? ? - iommu_arena_alloc returns non-0
>> ? ? ?- pci_map_single_1 returns 0 after printing
>> ? ? ? ?"could not allocate dma page tables" error
>> ? ? - alpha_pci_map_page returns 0 from pci_map_single_1
>> ? - radeon_gart_bind returns non-0, error path prints
>> ? ? "*ERROR* failed to bind 128 pages at 0x0FF02000"
>
> This happens in the latest git, right?
>
> Is this a regression (what kernel version worked)?
>
>
> Seems that the IOMMU can't find 128 pages. It's likely due to:
>
> - out of the IOMMU space (possibly someone doesn't free the IOMMU
> ?space).
>
> or
>
> - the mapping parameters (such as align) aren't appropriate so the
> ?IOMMU can't find space.
I don't think KMS drivers have ever worked on alpha so its not a
regression, they are working fine on x86 + powerpc and sparc has been
run at least once.
I suspect we are simply hitting the limits of the iommu, how big an
address space does it handle? since generally graphics drivers try to
bind a lot of things to the GART.
It might be worth limiting the PCIGART in radeon to 32MB to see if the
lower limit helps.
Dave.
>
>
>> Is this the cause of the bug we're seeing in the report [1]?
>>
>> Anyone know what's going wrong here?
>
>
> I've attached a patch to print the debug info about the mapping
> parameters.
>
>
> diff --git a/arch/alpha/kernel/pci_iommu.c b/arch/alpha/kernel/pci_iommu.c
> index d1dbd9a..17cf0d8 100644
> --- a/arch/alpha/kernel/pci_iommu.c
> +++ b/arch/alpha/kernel/pci_iommu.c
> @@ -187,6 +187,10 @@ iommu_arena_alloc(struct device *dev, struct
> pci_iommu_arena *arena, long n,
> ? ? ? ?/* Search for N empty ptes */
> ? ? ? ?ptes = arena->ptes;
> ? ? ? ?mask = max(align, arena->align_entry) - 1;
> +
> + ? ? ? printk("%s: %p, %p, %d, %ld, %lx, %u\n", __func__, dev, arena,
> arena->size,
> + ? ? ? ? ? ? ?n, mask, align);
> +
> ? ? ? ?p = iommu_arena_find_pages(dev, arena, n, mask);
> ? ? ? ?if (p < 0) {
> ? ? ? ? ? ? ? ?spin_unlock_irqrestore(>lock, flags);
>
>
EDID checksum errors
Octoploid wrote: > The following EDID checksum errors are spamming my syslog. > (Everything is working fine and there are no other problems > except these somewhat annoying messages): > > drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is > 128 This patch helps: http://lists.freedesktop.org/archives/dri-devel/2010-April/000255.html
EDID checksum errors
The following EDID checksum errors are spamming my syslog. (Everything is working fine and there are no other problems except these somewhat annoying messages): drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 [drm:drm_edid_block_valid] *ERROR* Raw EDID: <3>00 ff ff ff ff ff ff 00 1e 6d 48 4e 16 44 02 00 .mHN.D.. <3>08 10 01 03 ea 2b 1b 78 ea d1 05 a6 55 47 9d 25 .+.xUG.% <3>15 50 54 a7 6b 80 01 01 81 80 81 40 71 4f 01 01 .PT.k.. at qO.. <3>01 01 01 01 01 01 21 39 90 30 62 1a 27 40 68 b0 ..!9.0b.'@h. <3>36 00 b2 0e 11 00 00 1c 00 00 00 fd 00 38 4b 1c 68K. <3>53 0f 00 0a 20 20 20 20 20 20 00 00 00 fc 00 4c S... .L <3>32 30 34 57 54 0a 20 20 20 20 20 20 00 00 00 fc 204WT. <3>00 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 51 ...Q [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 188 [drm:drm_edid_block_valid] *ERROR* Raw EDID: <3>00 ff ff ff ff ff ff 00 1e 6d 48 4e 16 44 02 00 .mHN.D.. <3>08 10 01 03 ea 2b 1b 78 ea d1 01 a2 51 43 99 21 .+.xQC.! <3>11 50 50 a3 6b 80 01 01 81 80 81 40 71 4b 01 01 .PP.k.. at qK.. <3>01 01 01 01 01 01 21 39 90 30 62 1a 23 40 68 b0 ..!9.0b.#@h. <3>32 00 b2 0a 11 00 00 18 00 00 00 f9 00 38 4b 18 28K. <3>53 0b 00 0a 20 20 20 20 20 20 00 00 00 fc 00 4c S... .L <3>32 30 34 57 54 0a 20 20 20 20 20 20 00 00 00 fc 204WT. <3>00 0a 20 20 20 20 20 20 20 20 20 20 20 20 00 51 ...Q [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 104 [drm:drm_edid_block_valid] *ERROR* Raw EDID: <3>00 ff ff ff ff ff ff 00 1e 6d 48 4e 16 44 02 00 .mHN.D.. <3>08 10 01 03 e2 23 13 70 e2 d1 05 a6 55 47 95 25 .#.pUG.% <3>15 50 54 a7 63 80 01 01 81 80 81 40 71 47 01 01 .PT.c.. at qG.. <3>01 01 01 01 01 01 21 31 90 30 62 12 27 40 60 b0 ..!1.0b.'@`. <3>36 00 b2 06 11 00 00 14 00 00 00 f5 00 30 43 14 60C. <3>53 07 00 02 20 20 20 20 20 20 00 00 00 fc 00 4c S... .L <3>32 30 34 57 54 0a 20 20 20 20 20 20 00 00 00 fc 204WT. <3>00 0a 20 20 20 20 20 20 20 20 20 20 20 20 00 51 ...Q [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 38 [drm:drm_edid_block_valid] *ERROR* Raw EDID: <3>00 ff ff ff ff ff ff 00 1e 6d 48 4e 16 44 02 00 .mHN.D.. <3>08 10 01 03 ea 2b 1b 78 ea d1 05 a6 55 47 9d 25 .+.xUG.% <3>15 50 54 a7 6b 80 01 01 81 80 81 40 71 4f 01 01 .PT.k.. at qO.. <3>01 01 01 01 01 00 20 00 00 00 00 00 00 00 00 00 .. . <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <3>00 00 00 00 00 00 00 20 20 20 20 20 20 20 00 51 ... .Q
No subject
[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 --- Comment #9 from Brett Witherspoon 2010-06-22 17:17:41 PDT --- Created an attachment (id=36429) --> (https://bugs.freedesktop.org/attachment.cgi?id=36429) lscpi -vnn for video card. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 --- Comment #8 from Brett Witherspoon 2010-06-22 17:17:03 PDT --- Created an attachment (id=36428) --> (https://bugs.freedesktop.org/attachment.cgi?id=36428) Xorg.log seg fault after quiting wm with patch and noaccel enabled. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 --- Comment #7 from Brett Witherspoon 2010-06-22 17:12:29 PDT --- Ah, I had tried NoAccel previously with limited success, however with your patch applied it works much better. The window manager and apps are visible and there is no lockup when I switch VT's. However, X does seg fault when I quit the wm. I have attached the backtrace found the Xorg.log from that seg fault in case it is useful and the lspci output you requested. The connectors on the card are quite different from the generic connector table the driver seems to use. The connectors are DVI + ADC (Apple Display Connector DVI+USB for Cinema Displays; it was available prior to 2005). In case it is relevant, I am currently using the DVI outpt with a VGA adaptor since I ran out of DVI cables. Please let me know if I can provide anything else. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28628] [r300g] ARB_vp: error: relative address offset too large (163)
https://bugs.freedesktop.org/show_bug.cgi?id=28628 Marek Ol??k changed: What|Removed |Added Summary|GLSL Shader Error on R300g |[r300g] ARB_vp: error: ||relative address offset too ||large (163) --- Comment #2 from Marek Ol??k 2010-06-22 16:52:58 PDT --- This looks like a parser bug in ARB_vertex_program. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28628] GLSL Shader Error on R300g
https://bugs.freedesktop.org/show_bug.cgi?id=28628 Marek Ol??k changed: What|Removed |Added Attachment #36394|application/octet-stream|text/plain mime type|| -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28623] [r300g] enemy territory: quake wars crashes
https://bugs.freedesktop.org/show_bug.cgi?id=28623 --- Comment #4 from Marek Ol??k 2010-06-22 16:44:46 PDT --- Could you try current mesa git? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28655] [r300g] Regression caused by commit 9b2ebcaf4b94bfc8756f6b216e0e452013616f2c
https://bugs.freedesktop.org/show_bug.cgi?id=28655 --- Comment #9 from Marek Ol??k 2010-06-22 16:44:01 PDT --- I've committed a workaround, could you try current mesa git? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Problems with alpha/pci + radeon/ttm
On Mon, 21 Jun 2010 17:19:43 -0400
Matt Turner wrote:
> Michael Cree and I have been debugging FDO bug 26403 [1]. I tried
> booting with `radeon.test=1` and found this, which I think is related:
>
> > [drm] Tested GTT->VRAM and VRAM->GTT copy for GTT offset 0x202000
> > [drm] Tested GTT->VRAM and VRAM->GTT copy for GTT offset 0x302000
> [snip]
> > [drm] Tested GTT->VRAM and VRAM->GTT copy for GTT offset 0xfd02000
> > [drm] Tested GTT->VRAM and VRAM->GTT copy for GTT offset 0xfe02000
> > pci_map_single failed: could not allocate dma page tables
> > [drm:radeon_ttm_backend_bind] *ERROR* failed to bind 128 pages at 0x0FF02000
> > [TTM] Couldn't bind backend.
> > radeon :00:07.0: object_init failed for (1048576, 0x0002)
> > [drm:radeon_test_moves] *ERROR* Failed to create GTT object 253
> > Error while testing BO move.
>
> From what I can see, the call chain is
> radeon_test_moves
> (radeon_ttm_backend_bind called through callback function)
> - radeon_ttm.c:radeon_ttm_backend_bind calls radeon_gart_bind
> - radeon_gart.c:radeon_gart_bind calls pci_map_page
>- pci_map_page is alpha_pci_map_page, which calls...
> - alpha_pci_map_page calls pci_iommu.c:pci_map_single_1
> - pci_map_single_1 calls iommu_arena_alloc
> - iommu_arena_alloc calls iommu_arena_find_pages
>- iommu_arena_find_pages returns non-0
> - iommu_arena_alloc returns non-0
> - pci_map_single_1 returns 0 after printing
>"could not allocate dma page tables" error
> - alpha_pci_map_page returns 0 from pci_map_single_1
> - radeon_gart_bind returns non-0, error path prints
> "*ERROR* failed to bind 128 pages at 0x0FF02000"
This happens in the latest git, right?
Is this a regression (what kernel version worked)?
Seems that the IOMMU can't find 128 pages. It's likely due to:
- out of the IOMMU space (possibly someone doesn't free the IOMMU
space).
or
- the mapping parameters (such as align) aren't appropriate so the
IOMMU can't find space.
> Is this the cause of the bug we're seeing in the report [1]?
>
> Anyone know what's going wrong here?
I've attached a patch to print the debug info about the mapping
parameters.
diff --git a/arch/alpha/kernel/pci_iommu.c b/arch/alpha/kernel/pci_iommu.c
index d1dbd9a..17cf0d8 100644
--- a/arch/alpha/kernel/pci_iommu.c
+++ b/arch/alpha/kernel/pci_iommu.c
@@ -187,6 +187,10 @@ iommu_arena_alloc(struct device *dev, struct
pci_iommu_arena *arena, long n,
/* Search for N empty ptes */
ptes = arena->ptes;
mask = max(align, arena->align_entry) - 1;
+
+ printk("%s: %p, %p, %d, %ld, %lx, %u\n", __func__, dev, arena,
arena->size,
+ n, mask, align);
+
p = iommu_arena_find_pages(dev, arena, n, mask);
if (p < 0) {
spin_unlock_irqrestore(>lock, flags);
[Bug 28656] [Gallium/Draw][r300g] xscreensaver hack "endgame" crashes
https://bugs.freedesktop.org/show_bug.cgi?id=28656 Marek Ol??k changed: What|Removed |Added Summary|[r300g] xscreensaver hack |[Gallium/Draw][r300g] |"endgame" crashes |xscreensaver hack "endgame" ||crashes --- Comment #3 from Marek Ol??k 2010-06-22 14:20:57 PDT --- Another bug in Draw. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28674] [Gallium/Draw][r300g] Blender crash (Segmentation fault)
https://bugs.freedesktop.org/show_bug.cgi?id=28674 Marek Ol??k changed: What|Removed |Added Summary|[r300g] Blender crash |[Gallium/Draw][r300g] |(Segmentation fault)|Blender crash (Segmentation ||fault) --- Comment #1 from Marek Ol??k 2010-06-22 14:18:52 PDT --- It looks like there is a bug in Draw. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
EDID checksum errors
On Tue, Jun 22, 2010 at 1:11 PM, Octoploid wrote: > On Tue, Jun 22, 2010 at 7:07 PM, Alex Deucher > wrote: >> On Tue, Jun 22, 2010 at 12:39 PM, Corbin Simpson >> wrote: >>> On Tue, Jun 22, 2010 at 9:05 AM, Octoploid >>> wrote: Octoploid wrote: > The following EDID checksum errors are spamming my syslog. > (Everything is working fine and there are no other problems > except these somewhat annoying messages): > > drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is > 128 This patch helps: http://lists.freedesktop.org/archives/dri-devel/2010-April/000255.html >>> >>> Your monitor sucks. Don't take it personally; lots of monitors suck. >>> That patch just gives you the option to forcibly use ?monitors with >>> EDIDs that have bad checksums, in case the checksum is the only bad >>> part of an otherwise valid EDID. >> >> IIRC, ajax sent a patch a while back to just ignore bad checksums >> since they are so common. > > Yes, that is the patch I've linked to above. > But it just papers over the problem. Where do the changing > (corrupted) raw EDID blocks in my first message come from? > From my monitor? Yes. Older versions of the drm code weren't as pedantic. Alex
[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 --- Comment #6 from Alex Deucher 2010-06-22 13:42:55 PDT --- Also, what connectors does the card actually have on it? DVI + VGA + TV? DVI + DVI + TV? We probably need a custom connector table for it. Finally, can you attach the output of lspci -vnn for the card? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 --- Comment #5 from Alex Deucher 2010-06-22 13:39:41 PDT --- You are getting a GPU lockup. You might try: Option "NoAccel" "True" in the device section of your xorg.conf as a work around for the time being. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 Alex Deucher changed: What|Removed |Added Attachment #36423|application/octet-stream|text/plain mime type|| Attachment #36423|0 |1 is patch|| -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
EDID checksum errors
On Tue, Jun 22, 2010 at 12:39 PM, Corbin Simpson wrote: > On Tue, Jun 22, 2010 at 9:05 AM, Octoploid > wrote: >> Octoploid wrote: >> >>> The following EDID checksum errors are spamming my syslog. >>> (Everything is working fine and there are no other problems >>> except these somewhat annoying messages): >>> >>> drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is >>> 128 >> >> This patch helps: >> http://lists.freedesktop.org/archives/dri-devel/2010-April/000255.html > > Your monitor sucks. Don't take it personally; lots of monitors suck. > That patch just gives you the option to forcibly use ?monitors with > EDIDs that have bad checksums, in case the checksum is the only bad > part of an otherwise valid EDID. IIRC, ajax sent a patch a while back to just ignore bad checksums since they are so common. Alex
[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 --- Comment #4 from Brett Witherspoon 2010-06-22 12:36:00 PDT --- Created an attachment (id=36424) --> (https://bugs.freedesktop.org/attachment.cgi?id=36424) Xorg log with KMS patch applied. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 --- Comment #3 from Brett Witherspoon 2010-06-22 12:32:13 PDT --- Yes, this does avoids the oops. Thank you. The fb console works just it should. As you expected there are still some issues with X. The issue is very much like what I experienced without KMS and X when I was testing. I am not sure if this is separate issue and another bug report should be filed or not. If so let me know, but I will report what I have so far here. Using: libdrm-2.4.21 mesa-7.8.2 xorg-1.8.1.901 ati-drivers-6.13.0 After starting X I get a cursor and multi-color lines in the background. The window manager and other apps are started, but are not visible. Attempting to switch VT will cause the machine to lockup. It also seems that it will also lockup after a few min even if nothing is done. Xorg.log doesn't have any errors i can see but dmesg after X is started does have some *ERROR*. I have attached both. The *ERROR*'s in dmesg are repeated until the machine eventually locks. I was in a bit of a hurry to get the messages before it locked, so it only occurs once or twice here. Without KMS the issue is almost the same, but I get a nasty race condition prior to the lockup. I will also attempt to get some sort of backtrace if it is helpful. I will need to re-compile with debuging symbols. libdrm, mesa, xorg, ati-drivers should be enough? I am not sure if gdb is going to be useful in this case but I am happy to give it a run tonight. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 --- Comment #2 from Brett Witherspoon 2010-06-22 12:30:57 PDT --- Created an attachment (id=36423) --> (https://bugs.freedesktop.org/attachment.cgi?id=36423) dmesg after starting X -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28612] [r300g] View isn't permanent, menus/controls are corrupted in Blender
https://bugs.freedesktop.org/show_bug.cgi?id=28612 --- Comment #6 from Niels Clemmensen 2010-06-22 12:30:46 PDT --- The segfault fix in 59df6725afd9c0d50cd962dd01db868be13284db don't work. Blender still crash with a segmentatin fault. I have add a new bug (see bug 28674). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28656] [r300g] xscreensaver hack "endgame" crashes
https://bugs.freedesktop.org/show_bug.cgi?id=28656 --- Comment #2 from Chris Rankin 2010-06-22 12:24:20 PDT --- Created an attachment (id=36422) --> (https://bugs.freedesktop.org/attachment.cgi?id=36422) Output from valgrind This looks like the important part: ==10496== Invalid write of size 8 ==10496==at 0x5005289: ??? ==10496==by 0x4667387: fetch_pipeline_generic (draw_pt_fetch_shade_pipeline.c:188) ==10496==by 0x4667577: fetch_pipeline_run (draw_pt_fetch_shade_pipeline.c:312) ==10496==by 0x46692E0: vcache_run_extras (draw_pt_vcache.c:80) ==10496==by 0x4665EAC: draw_arrays_instanced (draw_pt.c:127) ==10496==by 0x4666025: draw_arrays (draw_pt.c:310) ==10496==by 0x4649C20: st_feedback_draw_vbo (st_draw_feedback.c:257) ==10496==by 0x464430C: st_RasterPos (st_cb_rasterpos.c:254) ==10496==by 0x4596C37: rasterpos (rastpos.c:63) ==10496==by 0x4597168: _mesa_RasterPos2f (rastpos.c:76) ==10496==by 0x80513E5: get_gl_visual (visual-gl.c:65) ==10496==by 0x8051FD0: make_random_colormap (colors.c:649) ==10496== Address 0x4d819e0 is not stack'd, malloc'd or (recently) free'd -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28674] New: [r300g] Blender crash (Segmentation fault)
https://bugs.freedesktop.org/show_bug.cgi?id=28674 Summary: [r300g] Blender crash (Segmentation fault) Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r300 AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: ncl at privat.dk In the last days both Blender 2.49a and Blender 2.5 (latest svn) crash with a segmentation fault. This have never happen before and Blender only crash with the Gallium driver. Also this crash don't happen with other programs. I'm running the latest mesa from git (22-6-2010) and my card is an Ati Radeon x1250 (rs690). I'm not sure about this help, but here are the bug/backtrace running gdb: Program received signal SIGSEGV, Segmentation fault. 0x7fffe95f1864 in clip_tri (stage=0x229d8e0, header=0x7fffd250) at draw/draw_pipe_clip.c:434 434header->v[1]->clipmask | (gdb) bt #0 0x7fffe95f1864 in clip_tri (stage=0x229d8e0, header=0x7fffd250) at draw/draw_pipe_clip.c:434 #1 0x7fffe95ef70c in do_triangle (draw=, flags=, v0=0x3bbc096 "", v1=0x6 , v2=0x3bbc090 "\340\264)\002") at draw/draw_pipe.c:165 #2 0x7fffe95eff76 in pipe_run (draw=0x229b4e0, vert_info=, prim_info=) at draw/draw_pt_decompose.h:114 #3 draw_pipeline_run (draw=0x229b4e0, vert_info=, prim_info=) at draw/draw_pipe.c:274 #4 0x7fffe95f644f in pipeline (middle=0x22a91e0, fetch_info=, prim_info=0x7fffd430) at draw/draw_pt_fetch_shade_pipeline.c:158 #5 fetch_pipeline_generic (middle=0x22a91e0, fetch_info=, prim_info=0x7fffd430) at draw/draw_pt_fetch_shade_pipeline.c:277 #6 0x7fffe95f65be in fetch_pipeline_run (middle=0x229d8e0, fetch_elts=, fetch_count=, draw_elts=0x6, draw_count=62636176) at draw/draw_pt_fetch_shade_pipeline.c:312 #7 0x7fffe95f83fd in vcache_flush (frontend=0x229fb50, get_elt=0x18, elts=0x17, elt_bias=21, count=22) at draw/draw_pt_vcache.c:80 #8 vcache_run_extras (frontend=0x229fb50, get_elt=0x18, elts=0x17, elt_bias=21, count=22) at draw/draw_pt_vcache_tmp.h:190 #9 0x7fffe95f5077 in draw_pt_arrays (draw=0x229b4e0, mode=, start=, count=24, startInstance=, instanceCount=) at draw/draw_pt.c:127 #10 draw_arrays_instanced (draw=0x229b4e0, mode=, start=, count=24, startInstance=, instanceCount=) at draw/draw_pt.c:355 #11 0x7fffe94aa4dc in r300_swtcl_draw_arrays (pipe=0x229a910, mode=, start=, count=24) at r300_render.c:672 #12 0x7fffe95998d7 in st_draw_vbo (ctx=, arrays=, prims=, nr_prims=1, ib=, index_bounds_valid=, min_index=0, max_index=23) at state_tracker/st_draw.c:717 #13 0x7fffe95c1d75 in vbo_exec_vtx_flush (exec=0x2386130, unmap=1 '\001') at vbo/vbo_exec_draw.c:384 #14 0x7fffe95bbe1c in vbo_exec_FlushVertices_internal (ctx=, unmap=80 'P') at vbo/vbo_exec_api.c:876 #15 0x7fffe95bbf22 in vbo_exec_FlushVertices (ctx=0x229d8e0, flags=1) at vbo/vbo_exec_api.c:910 #16 0x7fffe94fe872 in _mesa_set_enable (ctx=0x229d8e0, cap=2896, state=150 '\226') at main/enable.c:396 #17 0x008cb643 in draw_mesh_fancy (scene=0x2338048, ar=0x2309fc8, v3d=0x230a4e8, rv3d=0x230a138, base=0x2338908, dt=3, flag=0) at source/blender/editors/space_view3d/drawobject.c:2598 #18 0x008cc081 in draw_mesh_object (scene=0x2338048, ar=0x2309fc8, v3d=0x230a4e8, rv3d=0x230a138, base=0x2338908, dt=3, flag=0) at source/blender/editors/space_view3d/drawobject.c:2786 #19 0x008d64da in draw_object (scene=0x2338048, ar=0x2309fc8, v3d=0x230a4e8, base=0x2338908, flag=0) at source/blender/editors/space_view3d/drawobject.c:5772 #20 0x008e49ad in view3d_main_area_draw (C=0x1ed4f28, ar=0x2309fc8) at source/blender/editors/space_view3d/view3d_draw.c:2316 #21 0x00abcb4a in ED_region_do_draw (C=0x1ed4f28, ar=0x2309fc8) at source/blender/editors/screen/area.c:346 #22 0x0085e462 in wm_method_draw_triple (C=0x1ed4f28, win=0x22e10f8) at source/blender/windowmanager/intern/wm_draw.c:578 #23 0x0085ea6d in wm_draw_update (C=0x1ed4f28) at source/blender/windowmanager/intern/wm_draw.c:729 #24 0x0085cec0 in WM_main (C=0x1ed4f28) at source/blender/windowmanager/intern/wm.c:342 #25 0x008588d0 in main (argc=1, argv=0x7fffe308) at source/creator/creator.c:1141 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 Alex Deucher changed: What|Removed |Added Attachment #36419|application/octet-stream|text/plain mime type|| Attachment #36419|0 |1 is patch|| -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 --- Comment #1 from Alex Deucher 2010-06-22 10:03:59 PDT --- Created an attachment (id=36421) View: https://bugs.freedesktop.org/attachment.cgi?id=36421 Review: https://bugs.freedesktop.org/review?bug=28671=36421 possible fix try this patch. It should avoid this oops, but there may be other changes required for that card. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28671] New: Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 Summary: Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH. Product: DRI Version: unspecified Platform: PowerPC OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: brett.witherspoon at comcast.net Created an attachment (id=36419) --> (https://bugs.freedesktop.org/attachment.cgi?id=36419) Dmesg with call trace. Mentioned on #radeon: Hello, I have recently adopted a PowerMac G5 (machine7,3 circa 2003-04) with a ATI Radeon x800 XT Mac edition (AGP chipset R420 JH). When attempting to use the new KMS Radeon drivers (kernel v. 2.4.34) I get a seg. fault and kernel Oops. I am using PPC gentoo linux with 64bit kernel and 32bit userland. I have collected the call trace that is given after inserting the module with modesetting enabled. Attached is my entire dmesg with the call trace at the bottom. Inserting the module was done via SSH with no other fb or video drivers enabled in the kernel. Let me know if I can provide any additional information that would be useful and I am happy to do any testing. Thanks, B. Witherspoon -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
EDID checksum errors
On Tue, Jun 22, 2010 at 9:05 AM, Octoploid wrote: > Octoploid wrote: > >> The following EDID checksum errors are spamming my syslog. >> (Everything is working fine and there are no other problems >> except these somewhat annoying messages): >> >> drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is >> 128 > > This patch helps: > http://lists.freedesktop.org/archives/dri-devel/2010-April/000255.html Your monitor sucks. Don't take it personally; lots of monitors suck. That patch just gives you the option to forcibly use monitors with EDIDs that have bad checksums, in case the checksum is the only bad part of an otherwise valid EDID. -- When the facts change, I change my mind. What do you do, sir? ~ Keynes Corbin Simpson
[Bug 28655] [r300g] Regression caused by commit 9b2ebcaf4b94bfc8756f6b216e0e452013616f2c
https://bugs.freedesktop.org/show_bug.cgi?id=28655 --- Comment #8 from Rub?n Fern?ndez 2010-06-22 09:00:52 PDT --- (In reply to comment #7) > Does disabling colortiling help? > Option "ColorTiling" "False" > in the device section of your xorg.conf No change, I'm afraid -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28655] [r300g] Regression caused by commit 9b2ebcaf4b94bfc8756f6b216e0e452013616f2c
https://bugs.freedesktop.org/show_bug.cgi?id=28655 --- Comment #7 from Alex Deucher 2010-06-22 08:14:04 PDT --- Does disabling colortiling help? Option "ColorTiling" "False" in the device section of your xorg.conf -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28655] [r300g] Regression caused by commit 9b2ebcaf4b94bfc8756f6b216e0e452013616f2c
https://bugs.freedesktop.org/show_bug.cgi?id=28655 --- Comment #6 from Rub?n Fern?ndez 2010-06-22 07:54:14 PDT --- > > Does the attached patch help? > > It doesn't improve anything, but it changed something: now the five-pointed > star looks like a square; the new screenshot called "same star, with patch" > shows the exact same white star from the other screenshots, as it looks with > the patch applied Actually, I realised I loaded the wrong saved game; that square wasn't the same star from the previous screenshots (sorry for the confusion). In sum, the patch changed nothing at all. As before, all textures in the game look tiled, like a jigsaw puzzle (problem with texture coordinates, perhaps? putting pieces of the texture in the wrong places?) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28655] [r300g] Regression caused by commit 9b2ebcaf4b94bfc8756f6b216e0e452013616f2c
https://bugs.freedesktop.org/show_bug.cgi?id=28655 --- Comment #5 from Rub?n Fern?ndez 2010-06-22 07:12:11 PDT --- Created an attachment (id=36418) --> (https://bugs.freedesktop.org/attachment.cgi?id=36418) the same star, with patch applied -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28655] [r300g] Regression caused by commit 9b2ebcaf4b94bfc8756f6b216e0e452013616f2c
https://bugs.freedesktop.org/show_bug.cgi?id=28655 --- Comment #4 from Rub?n Fern?ndez 2010-06-22 07:10:54 PDT --- (In reply to comment #3) > Created an attachment (id=36412) View: https://bugs.freedesktop.org/attachment.cgi?id=36412 Review: https://bugs.freedesktop.org/review?bug=28655=36412 > WAIT_DMA_GUI_IDLE patch > > Does the attached patch help? It doesn't improve anything, but it changed something: now the five-pointed star looks like a square; the new screenshot called "same star, with patch" shows the exact same white star from the other screenshots, as it looks with the patch applied -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 27576] NWN text is only partially rendered (KMS only)
https://bugs.freedesktop.org/show_bug.cgi?id=27576 Stephen E. Baker changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #3 from Stephen E. Baker 2010-06-22 05:29:22 PDT --- Tested with xorg-server 1.8.1.902 and kernel 2.6.34. The issue is gone. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
No subject
radeon_test_moves (radeon_ttm_backend_bind called through callback function) - radeon_ttm.c:radeon_ttm_backend_bind calls radeon_gart_bind - radeon_gart.c:radeon_gart_bind calls pci_map_page - pci_map_page is alpha_pci_map_page, which calls... - alpha_pci_map_page calls pci_iommu.c:pci_map_single_1 - pci_map_single_1 calls iommu_arena_alloc - iommu_arena_alloc calls iommu_arena_find_pages - iommu_arena_find_pages returns non-0 - iommu_arena_alloc returns non-0 - pci_map_single_1 returns 0 after printing "could not allocate dma page tables" error - alpha_pci_map_page returns 0 from pci_map_single_1 - radeon_gart_bind returns non-0, error path prints "*ERROR* failed to bind 128 pages at 0x0FF02000" Is this the cause of the bug we're seeing in the report [1]? Anyone know what's going wrong here? Thanks! Matt Turner [1] https://bugs.freedesktop.org/show_bug.cgi?id=26403
[Bug 28623] [r300g] enemy territory: quake wars crashes
https://bugs.freedesktop.org/show_bug.cgi?id=28623 --- Comment #3 from Marek Ol??k 2010-06-22 04:38:49 PDT --- It doesn't add up. The "start" parameter in draw_elements is 117825309, it's impossible for the index buffer to be so large. I might add some validation in the draw function for it not to crash, but that would just hide problems elsewhere. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28612] [r300g] View isn't permanent, menus/controls are corrupted in Blender
https://bugs.freedesktop.org/show_bug.cgi?id=28612 --- Comment #5 from Marek Ol??k 2010-06-22 02:32:40 PDT --- There is a segfault fix in 59df6725afd9c0d50cd962dd01db868be13284db. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28612] [r300g] View isn't permanent, menus/controls are corrupted in Blender
https://bugs.freedesktop.org/show_bug.cgi?id=28612 --- Comment #4 from Niels Clemmensen 2010-06-22 02:28:59 PDT --- I have exactly the same problem (ati radeon x1250) with Blender 2.49a but not with Blender 2.5 (latest svn). But after the latest 2-3 upgrades from xorg-edgers/lucid I now got an segmentation fault with r300g (error 4 in r300_dri.so) and Blender just close. This happen both with Blender 2.49a and 2.5. I'm not sure this have something to do with commit 9b2ebcaf4b94bfc8756f6b216e0e452013616f2c but the segmentation fault happen around that time. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH] drm/radeon: optimize default 3D state for r6xx/r7xx blits
Re-organize emit order to reduce the number of dwords in the default 3D state. This change reduces the default state size from 514 dwords to 282. Signed-off-by: Alex Deucher --- drivers/gpu/drm/radeon/r600_blit_shaders.c | 677 +--- 1 files changed, 111 insertions(+), 566 deletions(-) diff --git a/drivers/gpu/drm/radeon/r600_blit_shaders.c b/drivers/gpu/drm/radeon/r600_blit_shaders.c index 0271b53..8338d43 100644 --- a/drivers/gpu/drm/radeon/r600_blit_shaders.c +++ b/drivers/gpu/drm/radeon/r600_blit_shaders.c @@ -45,11 +45,8 @@ const u32 r6xx_default_state[] = 0x8000, 0x8000, 0xc0016800, - 0x0010, - 0x8000, - 0xc0016800, 0x0542, - 0x0703, + 0xf903, 0xc0016800, 0x05c5, 0x, @@ -62,11 +59,9 @@ const u32 r6xx_default_state[] = 0xc0016800, 0x060e, 0x01020204, - 0xc0016f00, + 0xc0026f00, 0x, 0x, - 0xc0016f00, - 0x0001, 0x, 0xc0096900, 0x022a, @@ -83,43 +78,24 @@ const u32 r6xx_default_state[] = 0x0004, 0x, 0xc0016900, - 0x000a, - 0x, - 0xc0016900, - 0x000b, - 0x, - 0xc0016900, - 0x010c, - 0x, - 0xc0016900, - 0x010d, - 0x, - 0xc0016900, 0x0200, 0x, - 0xc0016900, + 0xc0026900, 0x0343, 0x0060, - 0xc0016900, - 0x0344, 0x0040, 0xc0016900, 0x0351, 0xaa00, 0xc0016900, - 0x0104, - 0x, - 0xc0016900, - 0x010e, - 0x, - 0xc0046900, - 0x0105, - 0x, - 0x, + 0x0203, + 0x0210, + 0xc0026900, + 0x000a, 0x, 0x, 0xc0036900, - 0x0109, + 0x010c, 0x, 0x, 0x, @@ -129,302 +105,149 @@ const u32 r6xx_default_state[] = 0x, 0x, 0x, - 0xc0046900, - 0x0048, - 0x3f80, - 0x, - 0x3f80, - 0x3f80, 0xc0016900, - 0x008e, + 0x008f, 0x000f, 0xc0016900, + 0x01e8, + 0x0001, + 0xc0056900, + 0x0104, + 0x, + 0x, + 0x, + 0x, + 0x, + 0xc0016900, 0x0080, 0x, 0xc0016900, + 0x008c, + 0x, + 0xc0016900, 0x0083, 0x, - 0xc0016900, + 0xc0026900, 0x0084, 0x, - 0xc0016900, - 0x0085, 0x20002000, - 0xc0016900, + 0xc0026900, 0x0086, 0x, - 0xc0016900, - 0x0087, 0x20002000, - 0xc0016900, + 0xc0026900, 0x0088, 0x, - 0xc0016900, - 0x0089, 0x20002000, - 0xc0016900, + 0xc0026900, 0x008a, 0x, - 0xc0016900, - 0x008b, 0x20002000, - 0xc0016900, - 0x008c, - 0x, - 0xc0016900, + 0xc0026900, 0x0094, 0x8000, - 0xc0016900, - 0x0095, 0x20002000, 0xc0026900, - 0x00b4, - 0x, - 0x3f80, - 0xc0016900, 0x0096, 0x8000, - 0xc0016900, - 0x0097, 0x20002000, 0xc0026900, - 0x00b6, - 0x, - 0x3f80, - 0xc0016900, 0x0098, 0x8000, - 0xc0016900, - 0x0099, 0x20002000, 0xc0026900, - 0x00b8, - 0x, - 0x3f80, - 0xc0016900, 0x009a, 0x8000, - 0xc0016900, - 0x009b, 0x20002000, 0xc0026900, - 0x00ba, - 0x, - 0x3f80, - 0xc0016900, 0x009c, 0x8000, - 0xc0016900, - 0x009d, 0x20002000, 0xc0026900, - 0x00bc, - 0x, - 0x3f80, - 0xc0016900, 0x009e, 0x8000, - 0xc0016900, - 0x009f, 0x20002000, 0xc0026900, - 0x00be, - 0x, - 0x3f80, - 0xc0016900, 0x00a0, 0x8000, - 0xc0016900, - 0x00a1, 0x20002000, 0xc0026900, - 0x00c0, - 0x, - 0x3f80, - 0xc0016900, 0x00a2, 0x8000, - 0xc0016900, -
[Bug 28649] Stellarium font and icon problems
https://bugs.freedesktop.org/show_bug.cgi?id=28649 Michel D?nzer changed: What|Removed |Added Product|DRI |Mesa Component|DRM/Radeon |Drivers/DRI/R600 --- Comment #7 from Michel D?nzer 2010-06-21 23:45:12 PDT --- Most likely a Mesa driver issue. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Problems with alpha/pci + radeon/ttm
Michael Cree and I have been debugging FDO bug 26403 [1]. I tried booting with `radeon.test=1` and found this, which I think is related: [drm] Tested GTT-VRAM and VRAM-GTT copy for GTT offset 0x202000 [drm] Tested GTT-VRAM and VRAM-GTT copy for GTT offset 0x302000 [snip] [drm] Tested GTT-VRAM and VRAM-GTT copy for GTT offset 0xfd02000 [drm] Tested GTT-VRAM and VRAM-GTT copy for GTT offset 0xfe02000 pci_map_single failed: could not allocate dma page tables [drm:radeon_ttm_backend_bind] *ERROR* failed to bind 128 pages at 0x0FF02000 [TTM] Couldn't bind backend. radeon :00:07.0: object_init failed for (1048576, 0x0002) [drm:radeon_test_moves] *ERROR* Failed to create GTT object 253 Error while testing BO move. From what I can see, the call chain is radeon_test_moves (radeon_ttm_backend_bind called through callback function) - radeon_ttm.c:radeon_ttm_backend_bind calls radeon_gart_bind - radeon_gart.c:radeon_gart_bind calls pci_map_page - pci_map_page is alpha_pci_map_page, which calls... - alpha_pci_map_page calls pci_iommu.c:pci_map_single_1 - pci_map_single_1 calls iommu_arena_alloc - iommu_arena_alloc calls iommu_arena_find_pages - iommu_arena_find_pages returns non-0 - iommu_arena_alloc returns non-0 - pci_map_single_1 returns 0 after printing could not allocate dma page tables error - alpha_pci_map_page returns 0 from pci_map_single_1 - radeon_gart_bind returns non-0, error path prints *ERROR* failed to bind 128 pages at 0x0FF02000 Is this the cause of the bug we're seeing in the report [1]? Anyone know what's going wrong here? Thanks! Matt Turner [1] https://bugs.freedesktop.org/show_bug.cgi?id=26403 ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Problems with alpha/pci + radeon/ttm
On Mon, 21 Jun 2010 17:19:43 -0400
Matt Turner matts...@gmail.com wrote:
Michael Cree and I have been debugging FDO bug 26403 [1]. I tried
booting with `radeon.test=1` and found this, which I think is related:
[drm] Tested GTT-VRAM and VRAM-GTT copy for GTT offset 0x202000
[drm] Tested GTT-VRAM and VRAM-GTT copy for GTT offset 0x302000
[snip]
[drm] Tested GTT-VRAM and VRAM-GTT copy for GTT offset 0xfd02000
[drm] Tested GTT-VRAM and VRAM-GTT copy for GTT offset 0xfe02000
pci_map_single failed: could not allocate dma page tables
[drm:radeon_ttm_backend_bind] *ERROR* failed to bind 128 pages at 0x0FF02000
[TTM] Couldn't bind backend.
radeon :00:07.0: object_init failed for (1048576, 0x0002)
[drm:radeon_test_moves] *ERROR* Failed to create GTT object 253
Error while testing BO move.
From what I can see, the call chain is
radeon_test_moves
(radeon_ttm_backend_bind called through callback function)
- radeon_ttm.c:radeon_ttm_backend_bind calls radeon_gart_bind
- radeon_gart.c:radeon_gart_bind calls pci_map_page
- pci_map_page is alpha_pci_map_page, which calls...
- alpha_pci_map_page calls pci_iommu.c:pci_map_single_1
- pci_map_single_1 calls iommu_arena_alloc
- iommu_arena_alloc calls iommu_arena_find_pages
- iommu_arena_find_pages returns non-0
- iommu_arena_alloc returns non-0
- pci_map_single_1 returns 0 after printing
could not allocate dma page tables error
- alpha_pci_map_page returns 0 from pci_map_single_1
- radeon_gart_bind returns non-0, error path prints
*ERROR* failed to bind 128 pages at 0x0FF02000
This happens in the latest git, right?
Is this a regression (what kernel version worked)?
Seems that the IOMMU can't find 128 pages. It's likely due to:
- out of the IOMMU space (possibly someone doesn't free the IOMMU
space).
or
- the mapping parameters (such as align) aren't appropriate so the
IOMMU can't find space.
Is this the cause of the bug we're seeing in the report [1]?
Anyone know what's going wrong here?
I've attached a patch to print the debug info about the mapping
parameters.
diff --git a/arch/alpha/kernel/pci_iommu.c b/arch/alpha/kernel/pci_iommu.c
index d1dbd9a..17cf0d8 100644
--- a/arch/alpha/kernel/pci_iommu.c
+++ b/arch/alpha/kernel/pci_iommu.c
@@ -187,6 +187,10 @@ iommu_arena_alloc(struct device *dev, struct
pci_iommu_arena *arena, long n,
/* Search for N empty ptes */
ptes = arena-ptes;
mask = max(align, arena-align_entry) - 1;
+
+ printk(%s: %p, %p, %d, %ld, %lx, %u\n, __func__, dev, arena,
arena-size,
+ n, mask, align);
+
p = iommu_arena_find_pages(dev, arena, n, mask);
if (p 0) {
spin_unlock_irqrestore(arena-lock, flags);
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28612] [r300g] View isn't permanent, menus/controls are corrupted in Blender
https://bugs.freedesktop.org/show_bug.cgi?id=28612 --- Comment #4 from Niels Clemmensen n...@privat.dk 2010-06-22 02:28:59 PDT --- I have exactly the same problem (ati radeon x1250) with Blender 2.49a but not with Blender 2.5 (latest svn). But after the latest 2-3 upgrades from xorg-edgers/lucid I now got an segmentation fault with r300g (error 4 in r300_dri.so) and Blender just close. This happen both with Blender 2.49a and 2.5. I'm not sure this have something to do with commit 9b2ebcaf4b94bfc8756f6b216e0e452013616f2c but the segmentation fault happen around that time. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28612] [r300g] View isn't permanent, menus/controls are corrupted in Blender
https://bugs.freedesktop.org/show_bug.cgi?id=28612 --- Comment #5 from Marek Olšák mar...@gmail.com 2010-06-22 02:32:40 PDT --- There is a segfault fix in 59df6725afd9c0d50cd962dd01db868be13284db. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28623] [r300g] enemy territory: quake wars crashes
https://bugs.freedesktop.org/show_bug.cgi?id=28623 --- Comment #3 from Marek Olšák mar...@gmail.com 2010-06-22 04:38:49 PDT --- It doesn't add up. The start parameter in draw_elements is 117825309, it's impossible for the index buffer to be so large. I might add some validation in the draw function for it not to crash, but that would just hide problems elsewhere. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28655] [r300g] Regression caused by commit 9b2ebcaf4b94bfc8756f6b216e0e452013616f2c
https://bugs.freedesktop.org/show_bug.cgi?id=28655 --- Comment #4 from Rubén Fernández rubenf3...@gmail.com 2010-06-22 07:10:54 PDT --- (In reply to comment #3) Created an attachment (id=36412) View: https://bugs.freedesktop.org/attachment.cgi?id=36412 Review: https://bugs.freedesktop.org/review?bug=28655attachment=36412 WAIT_DMA_GUI_IDLE patch Does the attached patch help? It doesn't improve anything, but it changed something: now the five-pointed star looks like a square; the new screenshot called same star, with patch shows the exact same white star from the other screenshots, as it looks with the patch applied -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
EDID checksum errors
The following EDID checksum errors are spamming my syslog. (Everything is working fine and there are no other problems except these somewhat annoying messages): drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 [drm:drm_edid_block_valid] *ERROR* Raw EDID: 300 ff ff ff ff ff ff 00 1e 6d 48 4e 16 44 02 00 .mHN.D.. 308 10 01 03 ea 2b 1b 78 ea d1 05 a6 55 47 9d 25 .+.xUG.% 315 50 54 a7 6b 80 01 01 81 80 81 40 71 4f 01 01 .pt.k..@qo.. 301 01 01 01 01 01 21 39 90 30 62 1a 27 40 68 b0 ..!9.0b.'@h. 336 00 b2 0e 11 00 00 1c 00 00 00 fd 00 38 4b 1c 68K. 353 0f 00 0a 20 20 20 20 20 20 00 00 00 fc 00 4c S... .L 332 30 34 57 54 0a 20 20 20 20 20 20 00 00 00 fc 204WT. 300 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 51 ...Q [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 188 [drm:drm_edid_block_valid] *ERROR* Raw EDID: 300 ff ff ff ff ff ff 00 1e 6d 48 4e 16 44 02 00 .mHN.D.. 308 10 01 03 ea 2b 1b 78 ea d1 01 a2 51 43 99 21 .+.xQC.! 311 50 50 a3 6b 80 01 01 81 80 81 40 71 4b 01 01 .pp.k..@qk.. 301 01 01 01 01 01 21 39 90 30 62 1a 23 40 68 b0 ..!9.0...@h. 332 00 b2 0a 11 00 00 18 00 00 00 f9 00 38 4b 18 28K. 353 0b 00 0a 20 20 20 20 20 20 00 00 00 fc 00 4c S... .L 332 30 34 57 54 0a 20 20 20 20 20 20 00 00 00 fc 204WT. 300 0a 20 20 20 20 20 20 20 20 20 20 20 20 00 51 ...Q [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 104 [drm:drm_edid_block_valid] *ERROR* Raw EDID: 300 ff ff ff ff ff ff 00 1e 6d 48 4e 16 44 02 00 .mHN.D.. 308 10 01 03 e2 23 13 70 e2 d1 05 a6 55 47 95 25 .#.pUG.% 315 50 54 a7 63 80 01 01 81 80 81 40 71 47 01 01 .pt.c..@qg.. 301 01 01 01 01 01 21 31 90 30 62 12 27 40 60 b0 ..!1.0b.'@`. 336 00 b2 06 11 00 00 14 00 00 00 f5 00 30 43 14 60C. 353 07 00 02 20 20 20 20 20 20 00 00 00 fc 00 4c S... .L 332 30 34 57 54 0a 20 20 20 20 20 20 00 00 00 fc 204WT. 300 0a 20 20 20 20 20 20 20 20 20 20 20 20 00 51 ...Q [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 38 [drm:drm_edid_block_valid] *ERROR* Raw EDID: 300 ff ff ff ff ff ff 00 1e 6d 48 4e 16 44 02 00 .mHN.D.. 308 10 01 03 ea 2b 1b 78 ea d1 05 a6 55 47 9d 25 .+.xUG.% 315 50 54 a7 6b 80 01 01 81 80 81 40 71 4f 01 01 .pt.k..@qo.. 301 01 01 01 01 00 20 00 00 00 00 00 00 00 00 00 .. . 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 300 00 00 00 00 00 00 20 20 20 20 20 20 20 00 51 ... .Q ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28655] [r300g] Regression caused by commit 9b2ebcaf4b94bfc8756f6b216e0e452013616f2c
https://bugs.freedesktop.org/show_bug.cgi?id=28655 --- Comment #8 from Rubén Fernández rubenf3...@gmail.com 2010-06-22 09:00:52 PDT --- (In reply to comment #7) Does disabling colortiling help? Option ColorTiling False in the device section of your xorg.conf No change, I'm afraid -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: EDID checksum errors
On Tue, Jun 22, 2010 at 9:05 AM, Octoploid cryptooctopl...@gmail.com wrote: Octoploid wrote: The following EDID checksum errors are spamming my syslog. (Everything is working fine and there are no other problems except these somewhat annoying messages): drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 This patch helps: http://lists.freedesktop.org/archives/dri-devel/2010-April/000255.html Your monitor sucks. Don't take it personally; lots of monitors suck. That patch just gives you the option to forcibly use monitors with EDIDs that have bad checksums, in case the checksum is the only bad part of an otherwise valid EDID. -- When the facts change, I change my mind. What do you do, sir? ~ Keynes Corbin Simpson mostawesomed...@gmail.com ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 Alex Deucher ag...@yahoo.com changed: What|Removed |Added Attachment #36419|application/octet-stream|text/plain mime type|| Attachment #36419|0 |1 is patch|| -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 --- Comment #5 from Alex Deucher ag...@yahoo.com 2010-06-22 13:39:41 PDT --- You are getting a GPU lockup. You might try: Option NoAccel True in the device section of your xorg.conf as a work around for the time being. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 --- Comment #6 from Alex Deucher ag...@yahoo.com 2010-06-22 13:42:55 PDT --- Also, what connectors does the card actually have on it? DVI + VGA + TV? DVI + DVI + TV? We probably need a custom connector table for it. Finally, can you attach the output of lspci -vnn for the card? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28674] [Gallium/Draw][r300g] Blender crash (Segmentation fault)
https://bugs.freedesktop.org/show_bug.cgi?id=28674 Marek Olšák mar...@gmail.com changed: What|Removed |Added Summary|[r300g] Blender crash |[Gallium/Draw][r300g] |(Segmentation fault)|Blender crash (Segmentation ||fault) --- Comment #1 from Marek Olšák mar...@gmail.com 2010-06-22 14:18:52 PDT --- It looks like there is a bug in Draw. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28656] [Gallium/Draw][r300g] xscreensaver hack endgame crashes
https://bugs.freedesktop.org/show_bug.cgi?id=28656 Marek Olšák mar...@gmail.com changed: What|Removed |Added Summary|[r300g] xscreensaver hack |[Gallium/Draw][r300g] |endgame crashes |xscreensaver hack endgame ||crashes --- Comment #3 from Marek Olšák mar...@gmail.com 2010-06-22 14:20:57 PDT --- Another bug in Draw. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28623] [r300g] enemy territory: quake wars crashes
https://bugs.freedesktop.org/show_bug.cgi?id=28623 --- Comment #4 from Marek Olšák mar...@gmail.com 2010-06-22 16:44:46 PDT --- Could you try current mesa git? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28628] GLSL Shader Error on R300g
https://bugs.freedesktop.org/show_bug.cgi?id=28628 Marek Olšák mar...@gmail.com changed: What|Removed |Added Attachment #36394|application/octet-stream|text/plain mime type|| -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28628] [r300g] ARB_vp: error: relative address offset too large (163)
https://bugs.freedesktop.org/show_bug.cgi?id=28628 Marek Olšák mar...@gmail.com changed: What|Removed |Added Summary|GLSL Shader Error on R300g |[r300g] ARB_vp: error: ||relative address offset too ||large (163) --- Comment #2 from Marek Olšák mar...@gmail.com 2010-06-22 16:52:58 PDT --- This looks like a parser bug in ARB_vertex_program. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 --- Comment #8 from Brett Witherspoon brett.withersp...@comcast.net 2010-06-22 17:17:03 PDT --- Created an attachment (id=36428) -- (https://bugs.freedesktop.org/attachment.cgi?id=36428) Xorg.log seg fault after quiting wm with patch and noaccel enabled. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.
https://bugs.freedesktop.org/show_bug.cgi?id=28671 --- Comment #9 from Brett Witherspoon brett.withersp...@comcast.net 2010-06-22 17:17:41 PDT --- Created an attachment (id=36429) -- (https://bugs.freedesktop.org/attachment.cgi?id=36429) lscpi -vnn for video card. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] drm/radeon/kms: avoid oops on mac r4xx cards
They don't have an atombios so don't attempt to use it for
eng/mem clocks.
Reported by spoonb on #radeon
fixes:
https://bugs.freedesktop.org/show_bug.cgi?id=28671
Signed-off-by: Alex Deucher alexdeuc...@gmail.com
---
drivers/gpu/drm/radeon/radeon_asic.c |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_asic.c
b/drivers/gpu/drm/radeon/radeon_asic.c
index 87f7e2c..646f96f 100644
--- a/drivers/gpu/drm/radeon/radeon_asic.c
+++ b/drivers/gpu/drm/radeon/radeon_asic.c
@@ -780,6 +780,13 @@ int radeon_asic_init(struct radeon_device *rdev)
case CHIP_R423:
case CHIP_RV410:
rdev-asic = r420_asic;
+ /* handle macs */
+ if (rdev-bios == NULL) {
+ rdev-asic-get_engine_clock =
radeon_legacy_get_engine_clock;
+ rdev-asic-set_engine_clock =
radeon_legacy_set_engine_clock;
+ rdev-asic-get_memory_clock =
radeon_legacy_get_memory_clock;
+ rdev-asic-set_memory_clock = NULL;
+ }
break;
case CHIP_RS400:
case CHIP_RS480:
--
1.7.0.1
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28655] [r300g] Regression caused by commit 9b2ebcaf4b94bfc8756f6b216e0e452013616f2c
https://bugs.freedesktop.org/show_bug.cgi?id=28655 Marek Olšák mar...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
