[PATCH 2.6.38-10-generic] device driver: fix oops in radeon driver due to incorrect value from hardware

2011-09-08 Thread Michel Dänzer
On Mit, 2011-08-10 at 09:27 -0400, Alex Deucher wrote: > 2011/8/10 Michel D?nzer : > > On Die, 2011-08-09 at 23:52 +0530, Mayank Rungta wrote: > >> Added a check for the radeon ring buffer write index in r600.c which > >> reads 0x on resume. This results in an Oops during > >>

Re: [PATCH 2.6.38-10-generic] device driver: fix oops in radeon driver due to incorrect value from hardware

2011-09-08 Thread Michel Dänzer
On Mit, 2011-08-10 at 09:27 -0400, Alex Deucher wrote: 2011/8/10 Michel Dänzer mic...@daenzer.net: On Die, 2011-08-09 at 23:52 +0530, Mayank Rungta wrote: Added a check for the radeon ring buffer write index in r600.c which reads 0x on resume. This results in an Oops during

[PATCH 2.6.38-10-generic] device driver: fix oops in radeon driver due to incorrect value from hardware

2011-08-10 Thread Mayank Rungta
On 08/10/2011 02:54 PM, Michel D?nzer wrote: > On Die, 2011-08-09 at 23:52 +0530, Mayank Rungta wrote: >> Added a check for the radeon ring buffer write index in r600.c which >> reads 0x on resume. This results in an Oops during >> radeon_ring_write. Masking the value averts this. >> >>

[PATCH 2.6.38-10-generic] device driver: fix oops in radeon driver due to incorrect value from hardware

2011-08-10 Thread Michel Dänzer
On Die, 2011-08-09 at 23:52 +0530, Mayank Rungta wrote: > Added a check for the radeon ring buffer write index in r600.c which > reads 0x on resume. This results in an Oops during > radeon_ring_write. Masking the value averts this. > > This problem is not seen to be fixed in 3.0 r600.c

[PATCH 2.6.38-10-generic] device driver: fix oops in radeon driver due to incorrect value from hardware

2011-08-10 Thread Mayank Rungta
Added a check for the radeon ring buffer write index in r600.c which reads 0x on resume. This results in an Oops during radeon_ring_write. Masking the value averts this. This problem is not seen to be fixed in 3.0 r600.c as well. Detailed analysis of the problem can be found at -

[PATCH 2.6.38-10-generic] device driver: fix oops in radeon driver due to incorrect value from hardware

2011-08-10 Thread Mayank Rungta
Added a check for the radeon ring buffer write index in r600.c which reads 0x on resume. This results in an Oops during radeon_ring_write. Masking the value averts this. This problem is not seen to be fixed in 3.0 r600.c as well. Detailed analysis of the problem can be found at -

Re: [PATCH 2.6.38-10-generic] device driver: fix oops in radeon driver due to incorrect value from hardware

2011-08-10 Thread Michel Dänzer
On Die, 2011-08-09 at 23:52 +0530, Mayank Rungta wrote: Added a check for the radeon ring buffer write index in r600.c which reads 0x on resume. This results in an Oops during radeon_ring_write. Masking the value averts this. This problem is not seen to be fixed in 3.0 r600.c as

Re: [PATCH 2.6.38-10-generic] device driver: fix oops in radeon driver due to incorrect value from hardware

2011-08-10 Thread Alex Deucher
2011/8/10 Michel Dänzer mic...@daenzer.net: On Die, 2011-08-09 at 23:52 +0530, Mayank Rungta wrote: Added a check for the radeon ring buffer write index in r600.c which reads 0x on resume. This results in an Oops during radeon_ring_write. Masking the value averts this. This problem

Re: [PATCH 2.6.38-10-generic] device driver: fix oops in radeon driver due to incorrect value from hardware

2011-08-10 Thread Mayank Rungta
On 08/10/2011 02:54 PM, Michel Dänzer wrote: On Die, 2011-08-09 at 23:52 +0530, Mayank Rungta wrote: Added a check for the radeon ring buffer write index in r600.c which reads 0x on resume. This results in an Oops during radeon_ring_write. Masking the value averts this. This problem