Excellent!!! After
git checkout 6936fb
and building and starting applications as in comment #42 the problem is
gone.
Tested with running stellarium and resizing glxgears.
--
[radeon][r200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
To clarify: I have only built and tested r200_dri.so on
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250
[Mobility FireGL 9000] (rev 02)
The comment says that the fix is for r200.
No idea whether it helps also for the different card driver mentioned
in #45
--
Now I've built both radeon_dri.so and r200_dri.so for the benfit of
those who are not so familiar with git and building. (or those who just
want to save the time to do it)
1. Extract the attached file.
tar xf mesafix-6936fb.tbz
2, go to the newly created directory
cd mesafix-6936fb
3. run
The problem also affects this card
ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]
which uses /usr/lib/dri/radeon_dri.so
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
As already mentioned in
https://bugs.freedesktop.org/show_bug.cgi?id=29367#c5 the patch in
https://bugs.freedesktop.org/show_bug.cgi?id=21374#c5 does not apply to
current mesa. I searched a bit in the git history and it applies cleanly
e. g. to commit 57f55a. However, this commit is 150 commits
Before reporting upstream, we probably have to try their newest version. In
order to get at all started with that code I first built
the Ubuntu source.
The Maverick debian package builds mesa obviously in 9 configurations
mesa-7.9~git20100924/build/osmesa32-static/config.status
Oops, my investigations obviously took some time. So I posted #39
without reading #38, which had come in the meantime.
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received this bug
I built the latest libdrm from
git clone git://anongit.freedesktop.org/git/mesa/drm
with these options:
./autogen.sh \
'--build=i686-linux-gnu' \
'--enable-udev' \
'--enable-libkms' \
'--enable-vmwgfx-experimental-api' \
'--enable-nouveau-experimental-api' \
'--enable-radeon' \
oops sorry: I meant it works on my ATI Technologies Inc Radeon RV250
[Mobility FireGL 9000] rev 2, cannot speak for others.
--
[M7 LW] [RV250] resolution incorrectly detected on various radeon cards
https://bugs.launchpad.net/bugs/645377
You received this bug notification because you are a
Yes, it works after applying the latest updates. There was no update to
xorg-xserver-video-ati though, so it must have been a bug somewhere
else. I had too many updates at once, cannot guess which one could have
fixed this issue.
--
[M7 LW] [RV250] resolution incorrectly detected on various
I get the same assertio on i386 with ATI Technologies Inc Radeon RV250
[Mobility FireGL 9000] (rev 02) when trying to start stellar
** Summary changed:
- [R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
+ [R200] [RV250]
Architecture: i386
DRM.card0.DVI.D.1:
status: disconnected
enabled: disabled
dpms: On
modes:
edid-base64:
DRM.card0.LVDS.1:
status: connected
enabled: enabled
dpms: On
modes: 1400x1050 1280x1024 1280x960 1280x854 1280x800 1280x720 1152x768
1024x768 800x600 848x480 720x480 640x480
apport information
** Attachment added: BootDmesg.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676861/+files/BootDmesg.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676862/+files/CurrentDmesg.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
apport information
** Attachment added: DRM.card0.SVIDEO.1.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676863/+files/DRM.card0.SVIDEO.1.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
apport information
** Attachment added: GdmLog.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676864/+files/GdmLog.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
apport information
** Attachment added: GdmLog1.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676865/+files/GdmLog1.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
apport information
** Attachment added: GdmLog2.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676866/+files/GdmLog2.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676867/+files/Lspci.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
apport information
** Attachment added: PciDisplay.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676868/+files/PciDisplay.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676869/+files/ProcCpuinfo.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676870/+files/ProcInterrupts.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676872/+files/RelatedPackageVersions.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676871/+files/ProcModules.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676873/+files/UdevDb.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676874/+files/UdevLog.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
apport information
** Attachment added: XorgLog.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676875/+files/XorgLog.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
apport information
** Attachment added: XorgLogOld.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676876/+files/XorgLogOld.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
apport information
** Attachment added: Xrandr.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676877/+files/Xrandr.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
apport information
** Attachment added: peripherals.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676878/+files/peripherals.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
apport information
** Attachment added: setxkbmap.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676879/+files/setxkbmap.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
apport information
** Attachment added: xdpyinfo.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676880/+files/xdpyinfo.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You
Oops sorry, I start the program with stellarTAB, but it's of course
called stellarium.
** Summary changed:
- [R200] [RV250] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc:
Assertion `boi-space_accounted' failed.
+ [R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
apport information
** Attachment added: xkbcomp.txt
https://bugs.edge.launchpad.net/bugs/656100/+attachment/1676881/+files/xkbcomp.txt
--
[R200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi-space_accounted' failed.
https://bugs.launchpad.net/bugs/656100
You received
Sorry, I have no idea what is Gallium or the classic driver. Google lead
me to http://www.x.org/wiki/RadeonFeature.
I'm not sure whether I understand the page, but it appears to me that
Gallium applies only to R300 or higher. (#602267 was on R300). However,
here we are talking about R200.
--
Happens also on my IBM Thinkpad T40.
ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] rev 2,
Reproduced with http://cdimage.ubuntu.com/daily-live/current/
24-Sep-2010
Work-around: xrandr --output LVDS --mode 1400x1050
--
[M7 LW] [RV250] resolution incorrectly detected on various
** Summary changed:
- resolution incorrectly detected on radeon 7500
+ [M7 LW] [RV250] resolution incorrectly detected on various radeon cards
--
[M7 LW] [RV250] resolution incorrectly detected on various radeon cards
https://bugs.launchpad.net/bugs/645377
You received this bug notification
*** This bug is a duplicate of bug 539772 ***
https://bugs.launchpad.net/bugs/539772
Fix to https://bugs.launchpad.net/bugs/539772 solves this problem.
Report marked as duplicate of #539772
** This bug has been marked a duplicate of bug 539772
[MASTER] Lucid 2.6.32-16 crashed to login
Hmm, my stack looks pretty much like the one in
https://bugs.launchpad.net/bugs/539772. But after installing xorg-server
- 2:1.7.6-2ubuntu7.1, which is supposed to fix #539772 I can still
easily reproduce the crash. Either I'm seeing a different problem here
or the fix does not work.
Not marking
ooops, please ignore my previous comment. I had a package pin left over
from my investigations and not all packages were updated now. So there
are still chances that the correction actually works. It's too late now,
I'll investigate this tomorrow.
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
Retested on the original machine with Ubuntu Lucid 10.04 LTS. No log
writings in /var/log/gdm/\:0.log anymore.
** Changed in: mesa (Ubuntu)
Status: Incomplete = Fix Released
--
continuous [driAllocateTexture:636] even when idle
https://bugs.launchpad.net/bugs/305586
You received this bug
Fixed in Lucid 10.04 LTS (or possibly even earlier)
--
continuous [driAllocateTexture:636] even when idle
https://bugs.launchpad.net/bugs/305586
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
** Tags added: verification-done
** Tags removed: needs-retested-on-lucid-by-june needs-verification
--
continuous [driAllocateTexture:636] even when idle
https://bugs.launchpad.net/bugs/305586
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa
The 800x600 issue has also been observed with this chip in Lucid. I have
received this report by email and cannot access the machine in question
to capture logs. So this is only FYI, I'm aware that for doing something
real we would need logs.
--
sis671/672 resolution 800x600
Hi Bryce,
[This is an automatic notification.]
This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?
Did your script fail here? The bug has been report against a very recent
version of Lucid and I have run apport-collect as you can see from all
Hi Bryce,
With Lucid I have switched to Kubuntu on that machine. I'm not sure
whether it is possible to retest the original problem in Kubuntu,
because the visual effects are probably quite differently implemtned. I
cannot promise that I have time to install Ubuntu until June, but I'll
try to
FYI: the same problem has also been observed in Arch Linux with a slightly
different model of Radeon graphics adapter.
http://bbs.archlinux.org/viewtopic.php?id=95549
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you
I was somehow guessing that EXA could be the culprit and tried to verify
my guess by disabling EXA.
How could I do that?
Simply renaming /usr/lib/xorg/modules/libexa.so did not work, the server
gets a fatal error when it cannot locate the file.
I googled around and understood that XAA is a
attachment 4/4 gdb session log without trap handlers
** Attachment added: Xorg.0.log.crash5noTrap
http://launchpadlibrarian.net/47793397/Xorg.0.log.crash5noTrap
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are
attachment 3/4 Xorg.log without trap handlers
** Attachment added: Xorg.0.log.crash5noTrap
http://launchpadlibrarian.net/47793361/Xorg.0.log.crash5noTrap
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a
attachment 2/4, gdb session with trap handlers
** Attachment added: crash4trapped
http://launchpadlibrarian.net/47793325/crash4trapped
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
Forgot to mention: I did all investigations twice. First with the
default Xorg trap handlers. After that with disabled Xorg trap handlers.
The stack did no look different in gdb.
(attachment 1/4, Xorg.log with trap handlers)
** Attachment added: Xorg.0.log.crash4trapped
apport information
** Attachment added: xdpyinfo.txt
http://launchpadlibrarian.net/47793149/xdpyinfo.txt
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: xkbcomp.txt
http://launchpadlibrarian.net/47793150/xkbcomp.txt
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: Xrandr.txt
http://launchpadlibrarian.net/47793145/Xrandr.txt
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: setxkbmap.txt
http://launchpadlibrarian.net/47793146/setxkbmap.txt
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: XorgLogOld.txt
http://launchpadlibrarian.net/47793144/XorgLogOld.txt
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: XorgLog.txt
http://launchpadlibrarian.net/47793143/XorgLog.txt
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/47793141/UdevDb.txt
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/47793142/UdevLog.txt
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/47793139/ProcModules.txt
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: RelatedPackageVersions.txt
http://launchpadlibrarian.net/47793140/RelatedPackageVersions.txt
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
which
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/47793135/ProcCpuinfo.txt
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/47793137/ProcInterrupts.txt
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: PciDisplay.txt
http://launchpadlibrarian.net/47793134/PciDisplay.txt
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/47793133/Lspci.txt
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/47793132/Dependencies.txt
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/47793125/CurrentDmesg.txt
--
[RV250] Kubuntu Lucid: Xorg gets SEGV
https://bugs.launchpad.net/bugs/575140
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: xserver-xorg-video-radeon
In Lucid Kubuntu Xorg crashes from time to time. Before Lucid this
machine had Intrepid Ubuntu and as far as I remember Xorg has not
crashed for more than a year.
Public bug reported:
Binary package hint: xserver-xorg-video-radeon
In Lucid Kubuntu Xorg crashes from time to time. Before Lucid this
machine had Intrepid Ubuntu and as far as I remember Xorg has not
crashed for more than a year.
According to /var/log/Xorg.0.log the call stack looks like this
In the current version xserver-xorg-core 2:1.7.6-2ubuntu7 Option NoTrapSignals
works correctly.
I use Kubuntu and I have created a file /usr/lib/X11/xorg.conf.d/01-server.conf
to give the option (but there are of course many other possible places)
In /var/log/Xorg.0.log you can see the
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 10.04 LTS
Release:10.04
Codename: lucid
I believe I'm affected by the bug. When trying to debug Xorg I get the
CRC mismatch warnings mentioned in the original bug description.
So I thought
Oops sorry, I guess the answer is in the bug description:
Produces empty ddebs and broken debug links ...
, when being built on Soyuz (not locally).
Not sure what Soyuz stands for here, but I guess the problem affects only
Ubuntu build infrastructure.
If I build locally on my own machine I
Sorry about the delay, too many things ongoing...
Tried with Karmic Alpha 5 LiveCD. There are no continuous log writings
with normal desktop effects.
(Is logging active in LiveCD enviroment???)
Double checked with my current Intrepid installation: continuous log
writings do still occur as
Hi Bryce,
Tanks for your message. I'm about to leave to holidays and unfortunately
I won't be able to investigate the issue right now. I should be be able
to look into again in mid-August at the latest.
--
continuous [driAllocateTexture:636] even when idle
https://bugs.launchpad.net/bugs/305586
75 matches
Mail list logo
