Running 2.6.37-rc2-git7 on x86_64, wine fails to start. I get the following error in the kernel logs:
radeon 0000:07:00.0: r600_cs_track_validate_cb offset[0] 0 2095360 4096 too big radeon 0000:07:00.0: r600_packet3_check:1331 invalid cmd stream 484 [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
Hardware is: 07:00.0 VGA compatible controller: ATI Technologies Inc RV710 [Radeon HD 4350] 07:00.1 Audio device: ATI Technologies Inc RV710/730
X.org version is 7.5.
With kernel 2.6.36, wine works just fine on the same system. Does it ring a bell to anyone? Any clue how to investigate this bug? If not, I can start a bisection.
I can also provide any additional data you need for investigation.
On Sun, Nov 21, 2010 at 9:38 AM, Jean Delvare khali@linux-fr.org wrote:
Running 2.6.37-rc2-git7 on x86_64, wine fails to start. I get the following error in the kernel logs:
radeon 0000:07:00.0: r600_cs_track_validate_cb offset[0] 0 2095360 4096 too big radeon 0000:07:00.0: r600_packet3_check:1331 invalid cmd stream 484 [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
Hardware is: 07:00.0 VGA compatible controller: ATI Technologies Inc RV710 [Radeon HD 4350] 07:00.1 Audio device: ATI Technologies Inc RV710/730
X.org version is 7.5.
With kernel 2.6.36, wine works just fine on the same system. Does it ring a bell to anyone? Any clue how to investigate this bug? If not, I can start a bisection.
I can also provide any additional data you need for investigation.
It's probably this patch: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdif...
Which exposes a bug in the 3D driver in certain cases. For some reason we get a cb height of 8192 or greater in some cases in the 3D driver. I haven't had time to look into why. You might try r600g for comparison.
Alex
-- Jean Delvare _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Hi Alex,
Thanks for your fast answer.
On Sun, 21 Nov 2010 11:12:32 -0500, Alex Deucher wrote:
On Sun, Nov 21, 2010 at 9:38 AM, Jean Delvare khali@linux-fr.org wrote:
Running 2.6.37-rc2-git7 on x86_64, wine fails to start. I get the following error in the kernel logs:
radeon 0000:07:00.0: r600_cs_track_validate_cb offset[0] 0 2095360 4096 too big radeon 0000:07:00.0: r600_packet3_check:1331 invalid cmd stream 484 [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
Hardware is: 07:00.0 VGA compatible controller: ATI Technologies Inc RV710 [Radeon HD 4350] 07:00.1 Audio device: ATI Technologies Inc RV710/730
X.org version is 7.5.
With kernel 2.6.36, wine works just fine on the same system. Does it ring a bell to anyone? Any clue how to investigate this bug? If not, I can start a bisection.
I can also provide any additional data you need for investigation.
It's probably this patch: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdif...
Your guess was correct: after applying the above patch to kernel 2.6.36, I get the same problem.
Which exposes a bug in the 3D driver in certain cases. For some reason we get a cb height of 8192 or greater in some cases in the 3D driver. I haven't had time to look into why. You might try r600g for comparison.
Not sure how to "try r600g"?
On Sun, Nov 21, 2010 at 1:51 PM, Jean Delvare khali@linux-fr.org wrote:
Hi Alex,
Thanks for your fast answer.
On Sun, 21 Nov 2010 11:12:32 -0500, Alex Deucher wrote:
On Sun, Nov 21, 2010 at 9:38 AM, Jean Delvare khali@linux-fr.org wrote:
Running 2.6.37-rc2-git7 on x86_64, wine fails to start. I get the following error in the kernel logs:
radeon 0000:07:00.0: r600_cs_track_validate_cb offset[0] 0 2095360 4096 too big radeon 0000:07:00.0: r600_packet3_check:1331 invalid cmd stream 484 [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
Hardware is: 07:00.0 VGA compatible controller: ATI Technologies Inc RV710 [Radeon HD 4350] 07:00.1 Audio device: ATI Technologies Inc RV710/730
X.org version is 7.5.
With kernel 2.6.36, wine works just fine on the same system. Does it ring a bell to anyone? Any clue how to investigate this bug? If not, I can start a bisection.
I can also provide any additional data you need for investigation.
It's probably this patch: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdif...
Your guess was correct: after applying the above patch to kernel 2.6.36, I get the same problem.
Which exposes a bug in the 3D driver in certain cases. For some reason we get a cb height of 8192 or greater in some cases in the 3D driver. I haven't had time to look into why. You might try r600g for comparison.
Not sure how to "try r600g"?
It's a newer driver for r6xx+ hardware. Configure mesa (http://cgit.freedesktop.org/mesa/mesa) with --enable-gallium-r600.
I actually talked to Dave earlier today, and the problem is more likely a command buffer getting flushed at the wrong time leading to a buffer without cb info in it.
Alex
-- Jean Delvare
Hi Alex,
On Sun, 21 Nov 2010 19:57:23 -0500, Alex Deucher wrote:
On Sun, Nov 21, 2010 at 1:51 PM, Jean Delvare khali@linux-fr.org wrote:
On Sun, 21 Nov 2010 11:12:32 -0500, Alex Deucher wrote:
It's probably this patch: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdif...
Your guess was correct: after applying the above patch to kernel 2.6.36, I get the same problem.
Which exposes a bug in the 3D driver in certain cases. For some reason we get a cb height of 8192 or greater in some cases in the 3D driver. I haven't had time to look into why. You might try r600g for comparison.
Not sure how to "try r600g"?
It's a newer driver for r6xx+ hardware. Configure mesa (http://cgit.freedesktop.org/mesa/mesa) with --enable-gallium-r600.
Unfortunately the thing doesn't seem to be willing to build on my system :( It won't find talloc even though it is installed. I don't have more time to spend on this.
I actually talked to Dave earlier today, and the problem is more likely a command buffer getting flushed at the wrong time leading to a buffer without cb info in it.
I think I'll just wait for you to come up with a fix :) I am in no hurry, I only use wine once in a while. Let me know if I can help with testing.
Hi Alex, David,
On Sun, 21 Nov 2010 11:12:32 -0500, Alex Deucher wrote:
On Sun, Nov 21, 2010 at 9:38 AM, Jean Delvare khali@linux-fr.org wrote:
Running 2.6.37-rc2-git7 on x86_64, wine fails to start. I get the following error in the kernel logs:
radeon 0000:07:00.0: r600_cs_track_validate_cb offset[0] 0 2095360 4096 too big radeon 0000:07:00.0: r600_packet3_check:1331 invalid cmd stream 484 [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
Hardware is: 07:00.0 VGA compatible controller: ATI Technologies Inc RV710 [Radeon HD 4350] 07:00.1 Audio device: ATI Technologies Inc RV710/730
X.org version is 7.5.
With kernel 2.6.36, wine works just fine on the same system. Does it ring a bell to anyone? Any clue how to investigate this bug? If not, I can start a bisection.
I can also provide any additional data you need for investigation.
It's probably this patch: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdif...
Which exposes a bug in the 3D driver in certain cases. For some reason we get a cb height of 8192 or greater in some cases in the 3D driver. I haven't had time to look into why. You might try r600g for comparison.
Any progress on this? Linus' latest kernel (2.6.37-rc5-git3) still has the problem. And this is a regression, so I don't think you can just ignore it.
Is there a bug opened to track this bug already? I couldn't find one on bugzilla.kernel.org, but maybe I missed it. If there is none, I'll create one.
On Fri, Dec 10, 2010 at 7:01 AM, Jean Delvare khali@linux-fr.org wrote:
Hi Alex, David,
On Sun, 21 Nov 2010 11:12:32 -0500, Alex Deucher wrote:
On Sun, Nov 21, 2010 at 9:38 AM, Jean Delvare khali@linux-fr.org wrote:
Running 2.6.37-rc2-git7 on x86_64, wine fails to start. I get the following error in the kernel logs:
radeon 0000:07:00.0: r600_cs_track_validate_cb offset[0] 0 2095360 4096 too big radeon 0000:07:00.0: r600_packet3_check:1331 invalid cmd stream 484 [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
Hardware is: 07:00.0 VGA compatible controller: ATI Technologies Inc RV710 [Radeon HD 4350] 07:00.1 Audio device: ATI Technologies Inc RV710/730
X.org version is 7.5.
With kernel 2.6.36, wine works just fine on the same system. Does it ring a bell to anyone? Any clue how to investigate this bug? If not, I can start a bisection.
I can also provide any additional data you need for investigation.
It's probably this patch: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdif...
Which exposes a bug in the 3D driver in certain cases. For some reason we get a cb height of 8192 or greater in some cases in the 3D driver. I haven't had time to look into why. You might try r600g for comparison.
Any progress on this? Linus' latest kernel (2.6.37-rc5-git3) still has the problem. And this is a regression, so I don't think you can just ignore it.
Is there a bug opened to track this bug already? I couldn't find one on bugzilla.kernel.org, but maybe I missed it. If there is none, I'll create one.
Was it not fixed by this commit? http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdif... If not, open a bug and attach the dmesg with the error messages.
Alex
On Sun, Dec 12, 2010 at 7:31 PM, Alex Deucher alexdeucher@gmail.com wrote:
On Fri, Dec 10, 2010 at 7:01 AM, Jean Delvare khali@linux-fr.org wrote:
Hi Alex, David,
On Sun, 21 Nov 2010 11:12:32 -0500, Alex Deucher wrote:
On Sun, Nov 21, 2010 at 9:38 AM, Jean Delvare khali@linux-fr.org wrote:
Running 2.6.37-rc2-git7 on x86_64, wine fails to start. I get the following error in the kernel logs:
radeon 0000:07:00.0: r600_cs_track_validate_cb offset[0] 0 2095360 4096 too big radeon 0000:07:00.0: r600_packet3_check:1331 invalid cmd stream 484 [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
Hardware is: 07:00.0 VGA compatible controller: ATI Technologies Inc RV710 [Radeon HD 4350] 07:00.1 Audio device: ATI Technologies Inc RV710/730
X.org version is 7.5.
With kernel 2.6.36, wine works just fine on the same system. Does it ring a bell to anyone? Any clue how to investigate this bug? If not, I can start a bisection.
I can also provide any additional data you need for investigation.
It's probably this patch: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdif...
Which exposes a bug in the 3D driver in certain cases. For some reason we get a cb height of 8192 or greater in some cases in the 3D driver. I haven't had time to look into why. You might try r600g for comparison.
Any progress on this? Linus' latest kernel (2.6.37-rc5-git3) still has the problem. And this is a regression, so I don't think you can just ignore it.
Is there a bug opened to track this bug already? I couldn't find one on bugzilla.kernel.org, but maybe I missed it. If there is none, I'll create one.
Was it not fixed by this commit? http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdif... If not, open a bug and attach the dmesg with the error messages.
Does the attached patch fix it?
Alex
Alex
Hi Alex,
On Sun, 12 Dec 2010 23:33:42 -0500, Alex Deucher wrote:
On Sun, Dec 12, 2010 at 7:31 PM, Alex Deucher alexdeucher@gmail.com wrote:
On Fri, Dec 10, 2010 at 7:01 AM, Jean Delvare khali@linux-fr.org wrote:
Any progress on this? Linus' latest kernel (2.6.37-rc5-git3) still has the problem. And this is a regression, so I don't think you can just ignore it.
Is there a bug opened to track this bug already? I couldn't find one on bugzilla.kernel.org, but maybe I missed it. If there is none, I'll create one.
Was it not fixed by this commit? http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdif...
Not, it wasn't.
If not, open a bug and attach the dmesg with the error messages.
Does the attached patch fix it?
Yes it does, thanks!
If you consider that user-space applications failing these tests are broken, maybe you could use printk_once() to let them know? Otherwise I suspect they will never get fixed. I think there's a way to get the name of the faulty process and include it in the message.
On Mon, Dec 13, 2010 at 7:12 PM, Jean Delvare khali@linux-fr.org wrote:
Hi Alex,
On Sun, 12 Dec 2010 23:33:42 -0500, Alex Deucher wrote:
On Sun, Dec 12, 2010 at 7:31 PM, Alex Deucher alexdeucher@gmail.com wrote:
On Fri, Dec 10, 2010 at 7:01 AM, Jean Delvare khali@linux-fr.org wrote:
Any progress on this? Linus' latest kernel (2.6.37-rc5-git3) still has the problem. And this is a regression, so I don't think you can just ignore it.
Is there a bug opened to track this bug already? I couldn't find one on bugzilla.kernel.org, but maybe I missed it. If there is none, I'll create one.
Was it not fixed by this commit? http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdif...
Not, it wasn't.
If not, open a bug and attach the dmesg with the error messages.
Does the attached patch fix it?
Yes it does, thanks!
If you consider that user-space applications failing these tests are broken, maybe you could use printk_once() to let them know? Otherwise I suspect they will never get fixed. I think there's a way to get the name of the faulty process and include it in the message.
No its a problem with developing GPU drivers, you write some code in userspace that seems correct, it gets rolled out, you later add a new feature like tiling, find a bug in the kernel checker code, realise the userspace code is wrong, and give up and become a farmer.
Dave.
On Mon, 13 Dec 2010 19:37:27 +1000, Dave Airlie wrote:
No its a problem with developing GPU drivers, you write some code in userspace that seems correct, it gets rolled out, you later add a new feature like tiling, find a bug in the kernel checker code, realise the userspace code is wrong, and give up and become a farmer.
I wish you success in you upcoming endeavour! :D
I know what you mean. The kernel/user-space interface is sometimes very difficult to live with.
dri-devel@lists.freedesktop.org
-
Alex Deucher -
Dave Airlie -
Jean Delvare