registry team mailing list archive

[Bug Watch Updater <602267@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 17 comments from the remote bug at
http://bugs.freedesktop.org/show_bug.cgi?id=29066.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2010-07-14T14:01:06+00:00 Bugzi09-fdo-tormod wrote:

Created an attachment (id=37056)
full backtrace (classic driver from git)

Originally reported on Ubuntu 10.04 in
https://bugs.launchpad.net/bugs/602267 and the user has also tested
latest git, classic and gallium.

Running "pipes" from xscreensaver crashes on RS482 with this message:
pipes: ../../radeon/radeon_cs_gem.c:129: cs_gem_write_reloc: Assertion `boi->space_accounted' failed.
(see attached backtrace)

With gallium, it does not crash but this message is seen:
radeon: The kernel rejected CS, see dmesg for more information.
dmesg contains:
[drm:r100_cs_packet_parse] *ERROR* Packet (351:3:16383) end after CS buffer (1020) !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !

Hardware:
01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS482 [Radeon Xpress 200M] [1002:5975]
	Subsystem: NEC Corporation Device [1033:8800]

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/28

------------------------------------------------------------------------
On 2010-07-14T14:02:37+00:00 Bugzi09-fdo-tormod wrote:

Created an attachment (id=37057)
dmesg output including gallium run

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/29

------------------------------------------------------------------------
On 2010-07-14T23:39:03+00:00 Marek Olšák wrote:

Bad news. It works for me on RV530 and RV350 with both TCL turned on and
off.

RS482 is RV350-based IIRC.

Kernel 2.6.35-rc3, libdrm from git.

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/31

------------------------------------------------------------------------
On 2010-07-15T13:26:35+00:00 Bugzi09-fdo-tormod wrote:

Yes, I don't know if they are closer to RV350 or to RV370. One
difference from those is that RS4xx have only two render output units,
but that's irrelevant for the driver, right? All I know is that these
Xpress IGP have all kind of problems.

Would it be important to try latest libdrm? Ubuntu 10.04 has only
2.4.18.

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/36

------------------------------------------------------------------------
On 2010-07-15T19:04:32+00:00 Marek Olšák wrote:

(In reply to comment #3)
> Yes, I don't know if they are closer to RV350 or to RV370. One difference from
> those is that RS4xx have only two render output units, but that's irrelevant
> for the driver, right?

It should be.

> Would it be important to try latest libdrm? Ubuntu 10.04 has only
2.4.18.

I can't tell for sure, though there are a few fixes since 2.4.18.

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/37

------------------------------------------------------------------------
On 2010-07-16T06:57:20+00:00 YannUbuntu wrote:

Dear all, 
I am the Launchpad bug reporter.

I tried kernel 2.6.35-020635rc5-generic , and I see no change when running /usr/lib/xscreensaver/pipes :
I get the same error message ("radeon: The kernel rejected CS, see dmesg for more information.") in terminal and the screensaver does not crash (like with the normal Lucid kernel).

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/38

------------------------------------------------------------------------
On 2010-07-26T06:11:41+00:00 Marek Olšák wrote:

Yann> Is the error in dmesg still the same, i.e. "Packet (351:3:16383)
end after CS buffer"?

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/40

------------------------------------------------------------------------
On 2010-07-27T00:01:16+00:00 YannUbuntu wrote:

(In reply to comment #6)
> Yann> Is the error in dmesg still the same, i.e. "Packet (351:3:16383) end
> after CS buffer"?

Yes, I tried again with rc6, and I get the following error :

[  288.532079] [drm:r100_cs_packet_parse] *ERROR* Packet (354:3:16383) end after CS buffer (1026) !
[  288.532086] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/41

------------------------------------------------------------------------
On 2010-07-27T01:07:30+00:00 Marek Olšák wrote:

Have you compiled mesa with --enable-debug? It might give you some nice
assertion failures hopefully.

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/42

------------------------------------------------------------------------
On 2010-07-27T01:36:26+00:00 YannUbuntu wrote:

(In reply to comment #8)
> Have you compiled mesa with --enable-debug? It might give you some nice
> assertion failures hopefully.

i am not fan of compilation, but i can try it if it is necessary and if
you explain me step-by-step :)

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/43

------------------------------------------------------------------------
On 2010-07-27T03:06:40+00:00 Marek Olšák wrote:

git clone git://anongit.freedesktop.org/mesa/mesa
cd mesa
./autogen.sh --with-dri-drivers= --with-state-trackers=dri --enable-debug --enable-glx-tls --enable-gallium-radeon --disable-gallium-swrast --disable-egl --disable-glu --disable-glut --disable-glw
make
cd lib/gallium
ln -s radeong_dri.so r300_dri.so
LIBGL_DRIVERS_PATH=. glxinfo|grep renderer # it should say Gallium 0.4 on R*
LIBGL_DRIVERS_PATH=. /usr/lib/xscreensaver/pipes

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/44

------------------------------------------------------------------------
On 2010-07-27T03:22:31+00:00 YannUbuntu wrote:

Thank you. Please how can I revert those changes after I test ? (I save
my data, but this is my production PC so I would like to keep it as
stable as possible)

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/45

------------------------------------------------------------------------
On 2010-07-27T03:43:29+00:00 Marek Olšák wrote:

It doesn't install anything, so there is nothing to revert. Your system
will be untouched.

LIBGL_DRIVERS_PATH=some_path program

says that the 3D driver for the "program" is loaded from "some_path".

If you don't type "LIBGL_DRIVERS_PATH=some_path", the driver will be
loaded from your default system location.

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/46

------------------------------------------------------------------------
On 2010-07-27T05:05:44+00:00 YannUbuntu wrote:


> LIBGL_DRIVERS_PATH=. glxinfo|grep renderer # it should say Gallium 0.4 on R*

it said "OpenGL renderer string: Gallium 0.4 on RS482"

> LIBGL_DRIVERS_PATH=. /usr/lib/xscreensaver/pipes

works without crashing. Here is the terminal output :

yyy@yyy-laptop:~/mesa/lib/gallium$ LIBGL_DRIVERS_PATH=. /usr/lib/xscreensaver/pipes
radeon: Successfully grabbed chipset info from kernel!
radeon: DRM version: 2.5.0 ID: 0x5975 GB: 1 Z: 1
radeon: GART size: 29 MB VRAM size: 128 MB
debug_get_flags_option: RADEON_DEBUG = 0x0
debug_get_bool_option: RADEON_NO_TCL = FALSE
couldn't open libtxc_dxtn.so, software DXTn compression/decompression unavailable
debug_get_bool_option: GALLIUM_RBUG = FALSE
debug_get_option: GALLIUM_TRACE = (null)
debug_get_bool_option: GALLIUM_GALAHAD = FALSE
debug_get_bool_option: DRAW_FSE = FALSE
debug_get_bool_option: DRAW_NO_FSE = FALSE
debug_get_bool_option: GALLIUM_DUMP_VS = FALSE
debug_get_bool_option: GALLIUM_NOSSE = FALSE
Mesa: CPU vendor: AuthenticAMD
Mesa: CPU name: Mobile AMD Sempron(tm) Processor 3200+
Mesa: Mesa 7.9-devel DEBUG build Jul 27 2010 20:48:56
Mesa warning: couldn't open libtxc_dxtn.so, software DXTn compression/decompression unavailable
debug_get_bool_option: MESA_MVP_DP4 = FALSE
debug_get_flags_option: ST_DEBUG = 0x0
^C


Do you need some more log ?

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/47

------------------------------------------------------------------------
On 2010-07-27T05:18:52+00:00 Marek Olšák wrote:

If I understand this correctly, the gallium driver from the PPA prints
"radeon: The kernel rejected CS, see dmesg for more information.", but
the driver from git works like a charm. Is that correct?

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/48

------------------------------------------------------------------------
On 2010-08-05T16:57:15+00:00 Marek Olšák wrote:

According to the last feedback, this issue seems to be resolved by using
the driver from git instead of the PPA. Closing..

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/49

------------------------------------------------------------------------
On 2010-08-13T14:21:38+00:00 YannUbuntu wrote:

Does it mean it will be solved in Ubuntu 10.10 ?
Or is there something Ubuntu developpers have to do ? 
Do I need to add something in https://bugs.launchpad.net/bugs/602267 ?

Reply at: https://bugs.launchpad.net/mesa/+bug/602267/comments/50


** Changed in: mesa
       Status: Unknown => Won't Fix

** Changed in: mesa
   Importance: Unknown => Medium

-- 
[RS482] pipes assert failure: pipes: ../../radeon/radeon_cs_gem.c:129: cs_gem_write_reloc: Assertion `boi->space_accounted' failed.
https://bugs.launchpad.net/bugs/602267
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Mesa.