radeon error on resume: cp failed to get scratch reg - anyone interested?

2012-09-18 Thread Simon Kitching
Hi, I've noticed that on resume from suspend, dmesg reports: [21895.997536] [drm] radeon: 1 quad pipes, 2 z pipes initialized. [21896.012072] [drm] PCIE GART of 512M enabled (table at 0x0004). [21896.012082] radeon :01:00.0: WB enabled [21896.012085] radeon :01:00.0: fence

Re: radeon error on resume: cp failed to get scratch reg - anyone interested?

2012-09-20 Thread Simon Kitching
On 19/09/12 11:12, Michel Dänzer wrote: On Mon, 2012-09-17 at 15:06 +0200, Simon Kitching wrote: Hi, I've noticed that on resume from suspend, dmesg reports: [21895.997536] [drm] radeon: 1 quad pipes, 2 z pipes initialized. [21896.012072] [drm] PCIE GART of 512M enabled (table

[PATCH] Prevent leak of scratch register on resume from suspend.

2012-09-20 Thread Simon Kitching
in radeon_driver_load_kms, and zero is not a valid registerid, zero safely implies not-yet-allocated. This issue appears to have been introduced in c7eff978 (3.6.0-rcN) Signed-off-by: Simon Kitching skitch...@vonos.net --- drivers/gpu/drm/radeon/r100.c |3 ++- 1 file changed, 2 insertions

radeon error on resume: "cp failed to get scratch reg" - anyone interested?

2012-09-17 Thread Simon Kitching
Hi, I've noticed that on resume from suspend, dmesg reports: [21895.997536] [drm] radeon: 1 quad pipes, 2 z pipes initialized. [21896.012072] [drm] PCIE GART of 512M enabled (table at 0x0004). [21896.012082] radeon :01:00.0: WB enabled [21896.012085] radeon :01:00.0: fence

radeon error on resume: "cp failed to get scratch reg" - anyone interested?

2012-09-20 Thread Simon Kitching
On 19/09/12 11:12, Michel D?nzer wrote: > On Mon, 2012-09-17 at 15:06 +0200, Simon Kitching wrote: >> Hi, >> >> I've noticed that on resume from suspend, dmesg reports: >> >> [21895.997536] [drm] radeon: 1 quad pipes, 2 z pipes initialized. >> [21896.012072]

[PATCH] Prevent leak of scratch register on resume from suspend.

2012-09-20 Thread Simon Kitching
tructure is allocated via kzalloc in radeon_driver_load_kms, and zero is not a valid registerid, zero safely implies not-yet-allocated. This issue appears to have been introduced in c7eff978 (3.6.0-rcN) Signed-off-by: Simon Kitching --- drivers/gpu/drm/radeon/r100.c |3 ++- 1 file change