[radeon, savage] Starwars screensaver locks X

Checked again. The bug is always triggered at the same point in the text. If I wait until the story starting with:

"Jonathan Riddell: No Kubuntu Release Candidate Tonight"

the crash happens about two lines into the main text.

Which graphics driver (and graphics card) are you using for X?

Video card:

ATI Radeon RV200 QW [Radeon 7500]

Device section from xorg.conf:

Section "Device"
        Identifier "ATI Technologies, Inc. Radeon 7500 (RV200 QW)"
        Driver "ati"
        BusID "PCI:1:0:0"
EndSection

Any other info I should add?

Thanks for your bug report. Would you please test if this bug is still happening with an up-to-date Dapper?

and if it still happens, could you pleasel try with the radeon driver instead of ati and see if it happens there as well ?

Hi.

I updated my machine to current dapper. I tried both the ATI and Radeon drivers:

Section "Device"
        Identifier "ATI Technologies, Inc. Radeon 7500 (RV200 QW)"
# Driver "ati"
        Driver "radeon"
        BusID "PCI:1:0:0"
EndSection

by changing the commented line.

The crash persists with both drivers in Dapper. Running the starwars screensaver in the screensaver-preview window is enough to trigger the crash. It usually takes several minutes before it crashes.

Is there no way I can provide more detailed logging/information to help?

Brick, can you try the ants gl screensavers? There are some issues with screensavers and ati video boards...

Ants work fine. Ran all three variations (Antinspect, Antmaze, Ant Spotlight) for more than 30 mins each. The starwars screensaver still locks after about 5 minutes.

please attach Xorg.0.log and xorg.conf. Thanks

Jerome

Jerome,

I'm afraid I no longer have this hardware, so am unable to replicate the
fault.

Sorry,

Chris.

On 30/06/06, Jerome S. Gotangco <email address hidden> wrote:
>
> please attach Xorg.0.log and xorg.conf. Thanks
>
> Jerome
>
> ** Changed in: xserver-xorg (Ubuntu)
> Assignee: Oliver Grawert => (unassigned)
>
> --
> [ati radeon] Starwars screensaver locks X
> https://launchpad.net/bugs/3198
>

Config file for crashing system

Crash log

See title :)

Neilen, which screensaver are you running, x or gnome-?

reassigning this against xserver-xorg-video-ati for now.

not getting requested info, so marking as rejected. Reopen if this issue is still valid.

sorry for acting a bit too hastily (duplicates to show this issue is real).. reopening myself. I can try to reproduce it on my home machine which has edgy and an ATI-board.

Hi

I've updated to Edgy now. The crash happens with both gnome-screensaver and plain x-. In fact, it will crash even if you just directly execute /usr/lib/xscreensaver/starwars and maximise the window.

Hi

I did some more testing. I ran the xscreensaver package from Hoary on my Edgy system with no crash. Hoary shipped xscreensaver v4.16. Breezy (the version where crashes started happening) ships xscreensaver v4.21. If you look at the xscreensaver changelog entry for v4.20 http://www.jwz.org/xscreensaver/changelog.html you will see:

* starwars uses texture-mapped fonts now.

It seems likely that this is what is causing the problem. What is strange is that no other GL screensavers cause a crash though.
I would like to try and run a v4.20 or newer xscreensaver on a Hoary system to see if the xscreensaver update merely exposed a latent Xorg bug or if the Xorg crashing is also a newer bug.

BTW, I see this bug is marked as need info. Is there any more info I can provide? I'm willing to run debug-testing code or whatever it takes on my machine to get to the bottom of this.

Setting to confirmed based on Neilen's comment.

I could reproduce this on my thinkpad T23 which uses a savage display driver, so this is not just an ATI-issue (in fact, I can't reproduce it on my desktop which has a Radeon 8500, at least not yet).

but on my laptop it hung the computer completely when I chose the Starwars from the prefs dialog.

reassigning against xscreensaver

I tried to reproduce this again, but only after a suspend/resume cycle was I able to get it hung again, running the screensaver directly from the console and without maximizing the window. After hanging the machine, the window got closed. Nothing worked, I had to power off to get it back to life.

maybe this needs to be reported upstream as well.

If X freezes and never comes back then it's not an xscreensaver bug. Regular user programs should never be able to do that to X.

Sitsofe, sorry, but did you ever tried playing with dri/opengl? Things like this are not that uncommon...

Alexandre:
Half of dri lives in kernel space. If you lock up your machine using accelerated opengl with open source drivers then the fault lies in the kernel porition of dri. It might be common but that doesn't mean the fault lies in the userspace program - it lies with X or the kernel.

Let's try punting this from xscreensaver -> xorg ...

and let's toss this around some more -> mesa :)

Does this still happen in Gutsy or Hardy?

Tormod,

Interestingly enough, this screensaver doesn't appear to be available
in Gutsy. I don't have Hardy installed.

Hope this helps.

Chris.

On 16/11/2007, Tormod Volden <email address hidden> wrote:
> Does this still happen in Gutsy or Hardy?
>
> ** Changed in: mesa (Ubuntu)
> Assignee: (unassigned) => Tormod Volden (tormodvolden)
> Status: Confirmed => Incomplete
>
> --
> [radeon, savage] Starwars screensaver locks X
> https://bugs.launchpad.net/bugs/3198
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Reasons why you may want to try GNU/Linux:

http://www.getgnulinux.org/

A great GNU/Linux distro:

http://wiki.gnewsense.org/

Thanks, I'll close the bug then. Please reopen if you see this issue with another screensaver, or if Starwars comes back :)

Tormod,

Thanks for that. That starts your weekend in a positive way :-).

Cheers,

Chris.

On 16/11/2007, Tormod Volden <email address hidden> wrote:
> Thanks, I'll close the bug then. Please reopen if you see this issue
> with another screensaver, or if Starwars comes back :)
>
> ** Changed in: mesa (Ubuntu)
> Status: Incomplete => Invalid
>
> ** Changed in: mesa (Ubuntu)
> Assignee: Tormod Volden (tormodvolden) => (unassigned)
>
> --
> [radeon, savage] Starwars screensaver locks X
> https://bugs.launchpad.net/bugs/3198
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Reasons why you may want to try GNU/Linux:

http://www.getgnulinux.org/

A great GNU/Linux distro:

http://wiki.gnewsense.org/

Well well, I have good news and bad news.

Good news: The demise of starwars in gutsy was greatly exagerated; It's still in xscreensaver-gl-extra where it's always been
http://packages.ubuntu.com/cgi-bin/search_contents.pl?searchmode=filelist&word=xscreensaver-gl-extra&version=gutsy&arch=i386

Bad news: Still crashes as hard as ever ;(((

I'm getting really frusrated for several reasons:

1) I like the starwars screensaver
2) the hard crashes undermine my confidence in general
3) It's been more than 2 years since I first reported the bug with no apparent progress
4) I don't know how to contribute to finding the problem in a more meaningful way.

Anyway, given the hard-crash nature it seems clear cut to me that it is a problem in DRI or Xorg that is just brought to light by the starwars screensaver. Presumably not only ubuntu users should be seeing it unless it's some long standing ubuntu divergence from upstream that is causing the issue; that seems unlikely though. I.O.W. should we not be taking this upstream? By the way, specific suggestions regarding 4) would be appreciated!

Perhaps you could post this message on the -devel list, to get some
attention to it...

2007/11/18, Neilen Marais <email address hidden>:
> Well well, I have good news and bad news.
>
> Good news: The demise of starwars in gutsy was greatly exagerated; It's still in xscreensaver-gl-extra where it's always been
> http://packages.ubuntu.com/cgi-bin/search_contents.pl?searchmode=filelist&word=xscreensaver-gl-extra&version=gutsy&arch=i386
>
> Bad news: Still crashes as hard as ever ;(((
>
> I'm getting really frusrated for several reasons:
>
> 1) I like the starwars screensaver
> 2) the hard crashes undermine my confidence in general
> 3) It's been more than 2 years since I first reported the bug with no apparent progress
> 4) I don't know how to contribute to finding the problem in a more meaningful way.
>
> Anyway, given the hard-crash nature it seems clear cut to me that it is
> a problem in DRI or Xorg that is just brought to light by the starwars
> screensaver. Presumably not only ubuntu users should be seeing it unless
> it's some long standing ubuntu divergence from upstream that is causing
> the issue; that seems unlikely though. I.O.W. should we not be taking
> this upstream? By the way, specific suggestions regarding 4) would be
> appreciated!
>
> ** Changed in: mesa (Ubuntu)
> Status: Invalid => Confirmed
>
> --
> [radeon, savage] Starwars screensaver locks X
> https://bugs.launchpad.net/bugs/3198
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
[]
Alexandre Strube
<email address hidden>

Can you please try:
 Option "BusType" "PCI"
in xorg.conf?

SImilar issues are reported upstream. For savage suspend/resume trouble, see for instance bug #37218. For ati, there is bug #114520 about PCI cards but with many (off-topic, I would say) comments from AGP card owners.

Tried BusType PCI. Still crashes, though it seemed to last a bit longer. Might be coincidence though.

Timo (or anyone else) can you reproduce on savage?

> 4) I don't know how to contribute to finding the problem in a more meaningful way.

There is some information on debugging such problems on https://wiki.ubuntu.com/X/Debugging https://wiki.ubuntu.com/DebuggingXorg and https://wiki.ubuntu.com/Bugs/AtiDriver
It would also be good if you search bugs.freedesktop.org for similar reports and file a new bug there if there is no bug matching exactly your issue. Please try the newest upstream drivers (packages on https://wiki.ubuntu.com/XorgOnTheEdge) before commenting there.

Hi,

I've been trying with the packages from

deb http://ppa.launchpad.net/tormodvolden/ubuntu gutsy main

Still get the crash. I also tried enabling DRM logging, i.e.

echo 1 | sudo tee /sys/module/drm/parameters/debug

but my hard drive filled up before a crash happened. It did seem to get progressively slower the longer the screensaver ran.

Please also try Hardy alpha 2 (or alpha 3 which should be released later this week).

I can reproduce this on current intrepid and savage. Will try to get a proper backtrace. My laptop does not have enough memory to use DRI, so that should narrow down the list of things to go wrong (ie. not the DRI driver).

[Setting to Incomplete since backtrace is needed]

[This is an automatic notification.]

Hi Neilen,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 3198

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 3198 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/3198

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".