Bug 14628 - drm/ksm -> s2disk -> resume -> [drm:r100_ring_test] *ERROR* radeon: ring test failed
Summary: drm/ksm -> s2disk -> resume -> [drm:r100_ring_test] *ERROR* radeon: ring test...
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks: 7216
  Show dependency tree
 
Reported: 2009-11-16 22:13 UTC by Rafael J. Wysocki
Modified: 2011-01-16 22:08 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.32-rc6
Subsystem:
Regression: No
Bisected commit-id:

Attachments
lspci (5.47 KB, text/plain)
2009-11-17 10:27 UTC, Christian Hartmann 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Rafael J. Wysocki 2009-11-16 22:13:13 UTC 
Subject    : drm/ksm -> s2disk -> resume -> [drm:r100_ring_test] *ERROR* radeon: ring test failed (sracth(0x15E4)=0xCAFEDEAD)
Submitter  : Christian Hartmann <cornogle@googlemail.com>
Date       : 2009-11-06 15:46
References : http://marc.info/?l=linux-kernel&m=125752241331067&w=4
Handled-By : Jerome Glisse <glisse@freedesktop.org>

This entry is being used for tracking a regression from 2.6.31.  Please don't
close it until the problem is fixed in the mainline.
Comment 1 Jérôme Glisse 2009-11-17 09:05:14 UTC 
I don't think we can call this a regression, KMS + AGP likely never worked properly on this particular platform. Nevertheless it's a bug.
Comment 2 Christian Hartmann 2009-11-17 10:27:12 UTC 
Created attachment 23813 [details]
lspci 

Linux oddysseus 2.6.32-rc7 #1 Mon Nov 16 16:24:25 CET 2009 i686 GNU/Linux

lspci (after resume)
Comment 3 Rafael J. Wysocki 2009-11-17 21:53:56 UTC 
(In reply to comment #1)
> I don't think we can call this a regression, KMS + AGP likely never worked
> properly on this particular platform. Nevertheless it's a bug.

OK, dropping from the list of recent regressions.
Comment 4 Rafael J. Wysocki 2011-01-16 22:08:21 UTC 
Well, I think we can say there's not enough information to fix this one.
Note You need to log in before you can comment on or make changes to this bug.