Ubuntu do_wait: drmWaitVBlank crash

Problems and solutions for installing or running FreeOrion, including discussion of bugs if needed before posting a bug report on GitHub. For problems building from source, post in Compile.

Moderator: Oberlus

Post Reply
Message
Author
User avatar
Nagilum
Release Manager, Design
Posts: 212
Joined: Thu Dec 31, 2009 3:25 pm
Location: Germany

Ubuntu do_wait: drmWaitVBlank crash

#1 Post by Nagilum »

I'm running Ubuntu Karmic(9.10) i386, I just checked out the latest version from svn, compiled it and run it. Unfortunately I get a black window for a sec and then this:

do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.
Try adjusting the vblank_mode configuration parameter.
BuildDesignatorWnd::BuildSelector::Refresh()
Segmentation fault

I tried putting an ".drirc" in my $HOME:
<driconf>
<device screen="0" driver="i965">
<application name="Default">
<option name="vblank_mode" value="1" />
</application>
</device>
</driconf>

but it didn't make any difference.
I've attached my Xorg.log, not sure if it's helpful.
Attachments
Xorg.0.log
(83.2 KiB) Downloaded 235 times

User avatar
Geoff the Medio
Programming, Design, Admin
Posts: 13587
Joined: Wed Oct 08, 2003 1:33 am
Location: Munich

Re: vblank_mode crash

#2 Post by Geoff the Medio »

This has been reported before, including here: https://sourceforge.net/tracker/?func=d ... tid=544942

I don't have a solution, unfortunately...

There are a few other references to similar issues on the web, such as: https://bugs.freedesktop.org/show_bug.cgi?id=19988

But there's not much help there. It may be a driver issue.

Are you (attempting to) run FreeOrion in windowed or fullscreen mode? I'm not sure what the default is on Linux.

User avatar
Nagilum
Release Manager, Design
Posts: 212
Joined: Thu Dec 31, 2009 3:25 pm
Location: Germany

Re: vblank_mode crash

#3 Post by Nagilum »

Default is windowed mode, but I also tried running with "-f" for fullscreen mode.

Masternetra
Space Krill
Posts: 3
Joined: Sun Jan 17, 2010 10:53 pm

Re: vblank_mode crash

#4 Post by Masternetra »

I have the same issue. Except my terminal output was:

Code: Select all

do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.
Try adjusting the vblank_mode configuration parameter.
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
Segmentation fault
Using Ubuntu 9.10 also. 32bit. Installed via Getdeb though.

User avatar
Geoff the Medio
Programming, Design, Admin
Posts: 13587
Joined: Wed Oct 08, 2003 1:33 am
Location: Munich

Re: vblank_mode crash

#5 Post by Geoff the Medio »

Masternetra wrote:

Code: Select all

bt_audio_service_open: connect() failed: Connection refused (111)
Googling the audio service error turned up some results that suggest it may be an unrelated problem. This thread looks promising, but I suggest googling for yourself if it isn't. I'm going to guess that this is also not a FreeOrion-specific problem.

I'm also wondering if the vblank crash isn't actually related to the vblank error message... a number of reports in forums about that seem to list it as an odd warning, but not always the cause of a crash. Naglium's crash was apparently after BuildDesignatorWnd::BuildSelector::Refresh() which presumably shouldn't have anything to do with rendering itself, although wherever it is crashing could be, I suppose.

Regardless, if anyone else has this issue, please attach, zipped, your freeorion.log from after the crash. This file will be in ~/.freeorion on Linux after running freeorion.

Masternetra
Space Krill
Posts: 3
Joined: Sun Jan 17, 2010 10:53 pm

Re: vblank_mode crash

#6 Post by Masternetra »

Geoff the Medio wrote:
Masternetra wrote:

Code: Select all

bt_audio_service_open: connect() failed: Connection refused (111)
Googling the audio service error turned up some results that suggest it may be an unrelated problem. This thread looks promising, but I suggest googling for yourself if it isn't. I'm going to guess that this is also not a FreeOrion-specific problem.

I'm also wondering if the vblank crash isn't actually related to the vblank error message... a number of reports in forums about that seem to list it as an odd warning, but not always the cause of a crash. Naglium's crash was apparently after BuildDesignatorWnd::BuildSelector::Refresh() which presumably shouldn't have anything to do with rendering itself, although wherever it is crashing could be, I suppose.

Regardless, if anyone else has this issue, please attach, zipped, your freeorion.log from after the crash. This file will be in ~/.freeorion on Linux after running freeorion.
Here is my log. Don't say anything about audio... The lines I had posted came from Terminal.
freeorion.log
(663 Bytes) Downloaded 210 times

User avatar
Geoff the Medio
Programming, Design, Admin
Posts: 13587
Joined: Wed Oct 08, 2003 1:33 am
Location: Munich

Re: vblank_mode crash

#7 Post by Geoff the Medio »

I suspect the audio lines are just warings or notifications, and not related to the cause of the crash. It's outputting directly to standard output or standard error, rather than throwing an exception which would be caught and noted in the log file, or at least wrapped with some "main caught exception" text.

Unfortunately the log doesn't reveal much about what the actual cause of the crash is.

doobiest
Space Krill
Posts: 2
Joined: Mon Jan 25, 2010 4:36 am

Re: vblank_mode crash

#8 Post by doobiest »

Install an older binary from their sourceforge page. I installed 0.3.9-2 (listed as 0.3.1) and it worked.

User avatar
Geoff the Medio
Programming, Design, Admin
Posts: 13587
Joined: Wed Oct 08, 2003 1:33 am
Location: Munich

Re: vblank_mode crash

#9 Post by Geoff the Medio »

v0.3.9 is from before OGRE was used as the main rendering / input engine. Using v0.3.10 or v0.3.11 would presumably also work, assuming that's related to the problem, which I suspect it is.

doobiest
Space Krill
Posts: 2
Joined: Mon Jan 25, 2010 4:36 am

Re: vblank_mode crash

#10 Post by doobiest »

.11 works. .12 does not so there we have it.

Is the game playable at .11? Like I enjoyed the original game so if freeorion of that version is mostly complete then I'll just play it on my netbook.

User avatar
Geoff the Medio
Programming, Design, Admin
Posts: 13587
Joined: Wed Oct 08, 2003 1:33 am
Location: Munich

Re: vblank_mode crash

#11 Post by Geoff the Medio »

FreeOrion is not a complete or balanced game in v0.3.13, and wasn't before then either... although some people seem to enjoy playing these early releases anyway.

Masternetra
Space Krill
Posts: 3
Joined: Sun Jan 17, 2010 10:53 pm

Re: vblank_mode crash

#12 Post by Masternetra »

Curious does version .13 work for anyone??

User avatar
Geoff the Medio
Programming, Design, Admin
Posts: 13587
Joined: Wed Oct 08, 2003 1:33 am
Location: Munich

Re: vblank_mode crash

#13 Post by Geoff the Medio »

v0.3.13 works for many people, on all three supported platforms.

oldtopman
Space Krill
Posts: 8
Joined: Fri Apr 02, 2010 1:12 pm

Re: vblank_mode crash

#14 Post by oldtopman »

Would it be possible to use the old engine in the new game to get it to work?
In the beginning there was Master of Orion
Or something like that.

User avatar
Geoff the Medio
Programming, Design, Admin
Posts: 13587
Joined: Wed Oct 08, 2003 1:33 am
Location: Munich

Re: vblank_mode crash

#15 Post by Geoff the Medio »

Removing Ogre would require disabling all the 3D combat stuff, which isn't that significant in v0.3.13, but will become more so in later versions, and rewriting a bunch of window and rendering setup code, and a few scatters bits of stuff that have become ogre-intertwined out of convenience. So, it's probably possible, but won't be happening unless someone new decides they want to do it and support it themselves.

Post Reply