<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Neverball: a workaround for Mesa crash</title>
	<atom:link href="http://helllabs.org/blog/20071001/neverball-a-workaround-for-mesa-crash/feed/" rel="self" type="application/rss+xml" />
	<link>http://helllabs.org/blog/20071001/neverball-a-workaround-for-mesa-crash/</link>
	<description></description>
	<pubDate>Tue, 06 Jan 2009 04:32:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: iorga</title>
		<link>http://helllabs.org/blog/20071001/neverball-a-workaround-for-mesa-crash/#comment-3529</link>
		<dc:creator>iorga</dc:creator>
		<pubDate>Thu, 03 Jan 2008 14:11:19 +0000</pubDate>
		<guid isPermaLink="false">http://helllabs.org/blog/20071001/neverball-a-workaround-for-mesa-crash/#comment-3529</guid>
		<description>Hi guys,

I m not sure I have the same problem. But neverball crashes systematically. Pacmanarena too. I suspected my graphics card (still actually) but I tried different distros (a new gentoo, freshly installed, with an automated genkernel as I suspected a bug in the kernel configuration as was suggested by daniel robbins) and it crashed everytime. With both games. Actually it crashes regularly with other video apps, but it takes longer. Ubuntu gusty freshly installed, updated, with latest nvidia restricted and stable drivers, compizfusion, same again: it crashes. It s not with Intel or Ati though but it crashes. Now comes the interesting part. The one which should help you or just make you conclude my problem is different than yours: I installed neverball in windows, and it crashed too. So OS independent... So maybe something else than  mesa problem? Can t say too much here. Just thought you should know.
Does this happen with pacmarena too in your case?</description>
		<content:encoded><![CDATA[<p>Hi guys,</p>
<p>I m not sure I have the same problem. But neverball crashes systematically. Pacmanarena too. I suspected my graphics card (still actually) but I tried different distros (a new gentoo, freshly installed, with an automated genkernel as I suspected a bug in the kernel configuration as was suggested by daniel robbins) and it crashed everytime. With both games. Actually it crashes regularly with other video apps, but it takes longer. Ubuntu gusty freshly installed, updated, with latest nvidia restricted and stable drivers, compizfusion, same again: it crashes. It s not with Intel or Ati though but it crashes. Now comes the interesting part. The one which should help you or just make you conclude my problem is different than yours: I installed neverball in windows, and it crashed too. So OS independent&#8230; So maybe something else than  mesa problem? Can t say too much here. Just thought you should know.<br />
Does this happen with pacmarena too in your case?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hell Labs » Mesa quiz: spot the bug (with patch)</title>
		<link>http://helllabs.org/blog/20071001/neverball-a-workaround-for-mesa-crash/#comment-1182</link>
		<dc:creator>Hell Labs » Mesa quiz: spot the bug (with patch)</dc:creator>
		<pubDate>Tue, 02 Oct 2007 19:43:31 +0000</pubDate>
		<guid isPermaLink="false">http://helllabs.org/blog/20071001/neverball-a-workaround-for-mesa-crash/#comment-1182</guid>
		<description>[...] Neverball: a workaround for Mesa crash       02 10 [...]</description>
		<content:encoded><![CDATA[<p>[...] Neverball: a workaround for Mesa crash       02 10 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ademar</title>
		<link>http://helllabs.org/blog/20071001/neverball-a-workaround-for-mesa-crash/#comment-1157</link>
		<dc:creator>Ademar</dc:creator>
		<pubDate>Mon, 01 Oct 2007 21:42:28 +0000</pubDate>
		<guid isPermaLink="false">http://helllabs.org/blog/20071001/neverball-a-workaround-for-mesa-crash/#comment-1157</guid>
		<description>Notice the workaround is not effective with at least ATI 9250 boards, where we now have a crash at a different place. Still under investigation. :-)</description>
		<content:encoded><![CDATA[<p>Notice the workaround is not effective with at least ATI 9250 boards, where we now have a crash at a different place. Still under investigation. :-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
