[LINUX] XBMC crash at startup after nvidia driver update

  Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Post Reply
sberk Offline
Junior Member
Posts: 3
Joined: Jun 2009
Reputation: 0
Sad  [LINUX] XBMC crash at startup after nvidia driver update
Post: #1
hi,

I performed an update on my Fedora 13 box. with this update the nvidia driver version 260.19.12 was installed. since the new drivers are installed xbmc crashes directly at the start - see this crashlog:

Quote:############## XBMC CRASH LOG ###############

################ SYSTEM INFO ################
Date: Sun Oct 24 14:40:47 CEST 2010
XBMC Options:
Arch: i686
Kernel: Linux 2.6.34.7-61.fc13.i686.PAE #1 SMP Tue Oct 19 04:24:06 UTC 2010
Release:
LSB Version: :core-4.0-ia32:core-4.0-noarch
Distributor ID: Fedora
Description: Fedora release 13 (Goddard)
Release: 13
Codename: Goddard
############## END SYSTEM INFO ##############

############### STACK TRACE #################
=====> Core file: /home/mc/core.8428 (2010-10-24 14:40:46.386265558 +0200)
=========================================
[New Thread 8458]
[New Thread 8428]
[New Thread 8457]
Core was generated by `/home/mc/XBMC_101025/lib/xbmc/xbmc.bin'.
Program terminated with signal 11, Segmentation fault.
#0 0x007a758e in ?? () from /usr/lib/nvidia/libGL.so.1

Thread 3 (Thread 8457):
#0 0x00e5e424 in __kernel_vsyscall ()
#1 0x0627adf6 in poll () from /lib/libc.so.6
#2 0x01710ce3 in ?? () from /usr/lib/libpulse.so.0
#3 0x016fd4ca in pa_mainloop_poll () from /usr/lib/libpulse.so.0
#4 0x016fed54 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#5 0x016fee34 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#6 0x01710a84 in ?? () from /usr/lib/libpulse.so.0
#7 0x01763863 in ?? () from /usr/lib/libpulsecommon-0.9.21.so
#8 0x007acc38 in ?? () from /usr/lib/nvidia/libGL.so.1

Thread 2 (Thread 8428):
#0 0x00e5e424 in __kernel_vsyscall ()
#1 0x001ac1fd in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2 0x0176244d in pa_cond_wait () from /usr/lib/libpulsecommon-0.9.21.so
#3 0x017103b1 in pa_threaded_mainloop_wait () from /usr/lib/libpulse.so.0
#4 0x00d621f0 in pa_simple_new () from /usr/lib/libpulse-simple.so.0
#5 0x064b7791 in ?? () from /usr/lib/libSDL-1.2.so.0
#6 0x06485821 in SDL_AudioInit () from /usr/lib/libSDL-1.2.so.0
#7 0x0648457f in SDL_InitSubSystem () from /usr/lib/libSDL-1.2.so.0
#8 0x06484668 in SDL_Init () from /usr/lib/libSDL-1.2.so.0
#9 0x082f1749 in CApplication::Create (this=0x8ba30a0) at Application.cpp:564
#10 0x08532352 in main (argc=1, argv=0xbfac2684) at xbmc.cpp:153

Thread 1 (Thread 8458):
#0 0x007a758e in ?? () from /usr/lib/nvidia/libGL.so.1
############# END STACK TRACE ###############

################# LOG FILE ##################

<U+FEFF>14:40:45 T:3077863392 M:2967015424 NOTICE: -----------------------------------------------------------------------
14:40:46 T:3077863392 M:2966618112 NOTICE: Starting XBMC, Platform: Linux (Fedora release 13 (Goddard), 2.6.34.7-61.fc13.i686.PAE i686). Built on Oct 24 2010 (SVN:34977)
14:40:46 T:3077863392 M:2966618112 NOTICE: special://xbmc/ is mapped to: /home/mc/XBMC_101025/share/xbmc
14:40:46 T:3077863392 M:2966618112 NOTICE: special://xbmcbin/ is mapped to: /home/mc/XBMC_101025/lib/xbmc
14:40:46 T:3077863392 M:2966618112 NOTICE: special://masterprofile/ is mapped to: /home/mc/.xbmc/userdata
14:40:46 T:3077863392 M:2966618112 NOTICE: special://home/ is mapped to: /home/mc/.xbmc
14:40:46 T:3077863392 M:2966618112 NOTICE: special://temp/ is mapped to: /home/mc/.xbmc/temp
14:40:46 T:3077863392 M:2966618112 NOTICE: The executable running is: /home/mc/XBMC_101025/lib/xbmc/xbmc.bin
14:40:46 T:3077863392 M:2966618112 NOTICE: Log File is located: /home/mc/.xbmc/temp/xbmc.log
14:40:46 T:3077863392 M:2966618112 NOTICE: -----------------------------------------------------------------------
14:40:46 T:3077863392 M:2966618112 NOTICE: Setup SDL


############### END LOG FILE ################

############ END XBMC CRASH LOG #############

at first I tried building xbmc again using the latest version available in the svn - same result Sad.

than I tried running xbmc from within gdb - now the crash is not occurring :confused2:.
I also tried to open xbmc in the gdb using the core file, but since the crash occurred directly within the libGL thread this also did not give me any clues.

any suggestions how to figure out what is wrong? does somebody else have this problem?

cheers,
sberk
find quote
opdenkamp Offline
Team-XBMC PVR Developer
Posts: 2,221
Joined: Feb 2009
Reputation: 29
Location: Heerlen, The Netherlands
Post: #2
apparently there is a problem when calling /usr/lib/nvidia/libGL.so.1, which is installed by the nvidia driver. try reinstalling the driver or install the previous driver you had.

opdenkamp / dushmaniac

xbmc-pvr [Eden-PVR builds] [now included in mainline XBMC, so no more source link here :)]
personal website: [link]

Found a problem with PVR? Report it on Trac, under "PVR - core components". Please attach the full debug log.

If you like my work, please consider donating to me and/or Team XBMC.
find quote
sberk Offline
Junior Member
Posts: 3
Joined: Jun 2009
Reputation: 0
Post: #3
I already figured out that it's a problem of the nvidia driver - going back to the old version may fix my problem temporarily, but I rather prefer to figure out why XBMC is no longer working with the current driver (and get this fixed).

any idea why XBMC is running if started from within gdb, but crashing if started normally?
find quote
opdenkamp Offline
Team-XBMC PVR Developer
Posts: 2,221
Joined: Feb 2009
Reputation: 29
Location: Heerlen, The Netherlands
Post: #4
sberk Wrote:I already figured out that it's a problem of the nvidia driver - going back to the old version may fix my problem temporarily, but I rather prefer to figure out why XBMC is no longer working with the current driver (and get this fixed).

any idea why XBMC is running if started from within gdb, but crashing if started normally?
it's failing here:
Code:
      if (SDL_Init(sdlFlags) != 0)
      {
        CLog::Log(LOGFATAL, "XBAppEx: Unable to initialize SDL: %s", SDL_GetError());
        return false;
      }
maybe your new nvidia driver doesn't work correctly with the version of libsdl on your system. check if there's an update for that too.

opdenkamp / dushmaniac

xbmc-pvr [Eden-PVR builds] [now included in mainline XBMC, so no more source link here :)]
personal website: [link]

Found a problem with PVR? Report it on Trac, under "PVR - core components". Please attach the full debug log.

If you like my work, please consider donating to me and/or Team XBMC.
find quote
Anssi Offline
Team-XBMC Developer
Posts: 133
Joined: Dec 2009
Reputation: 4
Location: Tampere, Finland
Post: #5
I'm investigating this issue since yesterday. It is definitely a non-XBMC issue, though.

You can workaround it by running
Code:
export __GL_SINGLE_THREADED=1
before running XBMC. However, this will reduce performance and VDPAU will still crash.

Alternatively you can downgrade your NVIDIA driver to 256.x. This issue only exists with 260.x.

I'll post more information once I have it.
find quote
Anssi Offline
Team-XBMC Developer
Posts: 133
Joined: Dec 2009
Reputation: 4
Location: Tampere, Finland
Post: #6
I've reported this at NVIDIA forums with more background information:
http://www.nvnews.net/vbulletin/showthread.php?t=156665
find quote
Flomaster Offline
Posting Freak
Posts: 1,287
Joined: Jun 2010
Reputation: 6
Location: East Texas
Post: #7
for me it seems to be a Dharma beta4 problem...

I have downgraded my Nvida to 260.19.04 and it still crashing , I found this thread so I downgraded to 256.53 and its still crashing when trying to play a movie or tv show.

here is a crash log with 256.53
http://flomaster.pastebin.com/BRd3q0gX

also when trying to access audio mixer via addons > audio mixer I only get a screen that looks like this.
[Image: ZDn6p.png]


-=Jason=-
find quote
X3lectric Offline
Closed Account
Posts: 1,756
Joined: Feb 2006
Location: in a Dropbox
Post: #8
I have no issue with this and I am running 260.19.12 final the version you guys are using is not final, I was previously running 256.53, also from a ppa (I never recommend installing the nvidia drivers from the run package)

All I did was use aptitude (type aptitude in terminal) selected the 260.19.12 from the ppa use and it did the job. (it removed all dkms from previous driver and inserted new ones as well as building the module for the kernel).

So this is not video driver related but I bet is your OS version instead, since I am using xbmcbuntu style install and running karmic.

Also I notice a PAE kernel at the top post, I have noticed over 2 years now, that many issues also come from using these crappy kernels, there is no valid reason to use a PAE (physical address extension) kernel, if you have 4gb of ram or more use 64bit instead.
(This post was last modified: 2010-10-31 10:56 by X3lectric.)
find quote
Anssi Offline
Team-XBMC Developer
Posts: 133
Joined: Dec 2009
Reputation: 4
Location: Tampere, Finland
Post: #9
Flomaster Wrote:for me it seems to be a Dharma beta4 problem...

I have downgraded my Nvida to 260.19.04 and it still crashing , I found this thread so I downgraded to 256.53 and its still crashing when trying to play a movie or tv show.
The topic of this thread is "crash at startup after nvidia driver update". Since your crash didn't happen after a driver update, and it doesn't even happen on startup, your issue is not relevant to this thread. Could you repost it as a new thread? Smile

X3lectric Wrote:I have no issue with this and I am running 260.19.12 final the version you guys are using is not final, I was previously running 256.53, also from a ppa (I never recommend installing the nvidia drivers from the run package)
You can see from the log file of the first poster that he didn't install the drivers through the .run package (look at the location of the NVIDIA libs).
Also, I've confirmed this issue with 260.19.12 as well.

X3lectric Wrote:All I did was use aptitude (type aptitude in terminal) selected the 260.19.12 from the ppa use and it did the job. (it removed all dkms from previous driver and inserted new ones as well as building the module for the kernel).

So this is not video driver related but I bet is your OS version instead, since I am using xbmcbuntu style install and running karmic.
So either this doesn't affect Ubuntu, or you do not have the exact same conditions that I've listed in the NVIDIA forum post (pulse installed but disabled, etc). Thus far I've gotten reports of this issue on Fedora 13 and Mandriva 2010.1 and Mandriva Cooker.
And yes, it is not yet confirmed whether the actual bug is in the video driver, gcc, glibc (or something else). But as downgrading to 256.x fixes it, it makes the video driver a suspect. Smile

X3lectric Wrote:Also I notice a PAE kernel at the top post, I have noticed over 2 years now, that many issues also come from using these crappy kernels, there is no valid reason to use a PAE (physical address extension) kernel, if you have 4gb of ram or more use 64bit instead.
I've confirmed the issue with a 64bit kernel.
find quote
kickit2 Offline
Junior Member
Posts: 9
Joined: Oct 2010
Reputation: 0
Post: #10
I'm having the same issue here. Any word on this. 256.53 seems to have other issues that while rare, are still there (random blocking and tyling or random hanging of picture for 2-3 seconds every hour or so).
find quote
Anssi Offline
Team-XBMC Developer
Posts: 133
Joined: Dec 2009
Reputation: 4
Location: Tampere, Finland
Post: #11
kickit2 Wrote:I'm having the same issue here. Any word on this.

No news from NVIDIA yet on a possible fix.

In the meantime, you can workaround the issue by using
Code:
export SDL_AUDIODRIVER=alsa
before starting XBMC.
find quote
X3lectric Offline
Closed Account
Posts: 1,756
Joined: Feb 2006
Location: in a Dropbox
Post: #12
@ Ansii

I run xbmcbuntu VERY custom install (see my sig) and suffer none of these issues, perhaps its related to other distros only.

I have tested xbmclive beta4 and upgraded the video driver to 260 with no issues. Obviously went back to my imaged setup which works WAY better which is based on karmic minimal running on asrock ion 330 HT.

good find on that fix perhaps it can be made more permanent, cant it not be modeprobed?
(This post was last modified: 2010-11-02 20:02 by X3lectric.)
find quote
kickit2 Offline
Junior Member
Posts: 9
Joined: Oct 2010
Reputation: 0
Post: #13
Anssi Wrote:No news from NVIDIA yet on a possible fix.

In the meantime, you can workaround the issue by using
Code:
export SDL_AUDIODRIVER=alsa
before starting XBMC.

Thanks for the workaround - I can second this as a functional approach. However, with this workaround in place, I have no navigation sounds (simple click and such xbmc makes when navigating menus and such). Is this just me or is this a side effect of forcing alsa?

Shawn
find quote
popelheini Offline
Junior Member
Posts: 10
Joined: Apr 2010
Reputation: 0
Post: #14
I had exactly the same issue with xbmc on FC13 after upgrade of libGL.so
Today I made an upgrade to FC14 and ... xbmc is working. Nvidia is still on 260.19.12 but it's not crashing (only sound doesn't work for now)

Fingers crossed

Popel
find quote
Anssi Offline
Team-XBMC Developer
Posts: 133
Joined: Dec 2009
Reputation: 4
Location: Tampere, Finland
Post: #15
This issue is fixed in NVIDIA driver version 260.19.21 Smile

Changelog says:
Quote:Fixed a race condition in OpenGL that could cause crashes with multithreaded applications.

kickit2, sorry for missing your question. Don't really know about the nav sounds, I don't use them. I guess it doesn't matter anymore as the workaround become unnecessary.
find quote
Post Reply