| View previous topic :: View next topic |
| Author |
Message |
Dikkiedik2
n00b
Joined: 14 Jan 2008
Posts: 12
|
 Posted: Fri Mar 07, 2008 6:27 pm Post subject: mplayer signal 11 in module decode_video |
 |
|
I have just updated to the latest mplayer version on a global world update.
Now, I have problems playing AVI files, the latest error report I could find about this dates from a couple of years back and wasn't helpful. Also, the forums contain no extra information when I search for 'signal 11 mplayer'.
Can anyone help me with this? I don't know why it's doing this.
These are the useflags activated:
| Code: |
media-video/mplayer X a52 aac aalib alsa arts cdparanoia cpudetection dga dvd ftp gif iconv ipv6 jpeg libcaca mmx mp3 opengl oss png quicktime rar rtc samba sse -sse2 -ssse3 truetype unicode v4l vorbis win32codecs xinerama xvid gtk
|
it also says that it's possible because of an incorrect use of CPU/FPU or RAM.
Maybe people have some experience with this, else I'll have to fix it the annoying way... generating a gdb backtrace and do stuff for myself -_-''' (I don't quite like that!!)
Thanks!!
_________________
Calling atheism a religion, is like calling bald a hair colour. |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54308
Location: 56N 3W
|
| Posted: Fri Mar 07, 2008 7:05 pm Post subject: |
|
|
Dikkiedik2,
Signal 11 is a segment violation. mplayer is trying to access memory it doesn't own.
Paste the FLAGS line from /proc/cpuino and the information that mplayer shows when you run it in a terminal with no parameters.
Its worth running memtest from the liveCD but at the moment, I doubt its a hardware issue.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
rlittle
Apprentice
Joined: 17 Dec 2003
Posts: 200
|
| Posted: Mon Mar 10, 2008 8:02 am Post subject: |
|
|
I have the same sudden-out-of-the-blue (after an update) problem. I read your post and things look ok:
| Code: | ~ $ mplayer
MPlayer dev-SVN-rUNKNOWN-4.1.2 (C) 2000-2008 MPlayer Team
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ (Family: 15, Model: 75, Stepping: 2)
CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1
Compiled with runtime CPU detection. |
| Code: | ~ $ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 75
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4600+
<snip>
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy
^ ^ ^ ^ ^ ^ |
current version is media-video/mplayer-1.0_rc2_p25993
No problems anywhere else, so it's unlikely it's hardware here also.
Anyone have a suggestion before I >shudder< try downgrading?
(pokes around a bit before hitting "Submit")
Heeeeyyyyyy.... look what shows up in /var/log/messages whenever mplayer crashes:
| Code: | Mar 10 03:57:41 myhost kernel: NVRM: API mismatch: the client has the version 169.09, but
Mar 10 03:57:41 myhost kernel: NVRM: this kernel module has the version 100.14.19. Please
Mar 10 03:57:41 myhost kernel: NVRM: make sure that this kernel module and all NVIDIA driver
Mar 10 03:57:41 myhost kernel: NVRM: components have the same version. |
I have to crash (I mean sleep) right now, but this is likely the problem. I don't think I did anything special this update though, I wonder what I screwed up?
Thanks,
_________________
I need a better signature... |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54308
Location: 56N 3W
|
| Posted: Mon Mar 10, 2008 6:36 pm Post subject: |
|
|
rlittle,
It looks like you have mplayer compiled with the xvmc USE flag. Your error comes from the nvidia driver and xvmc is only useful for nVidia cards.
There was some discussion about nvidia dropping xvmc support but I don't know the outcome.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
beandog
Bodhisattva
Joined: 04 May 2003
Posts: 2072
Location: /usa/utah
|
| Posted: Mon Mar 10, 2008 8:36 pm Post subject: |
|
|
| NeddySeagoon wrote: | | It looks like you have mplayer compiled with the xvmc USE flag. Your error comes from the nvidia driver and xvmc is only useful for nVidia cards. |
MPlayer would probably never default to XvMC for the output method. It'd use xv, then x11, then probably break.
Also, don't use cpudetection.
_________________
If it ain't broke, tweak it. dvds | blurays | blog | wiki |
|
| Back to top |
|
|
rlittle
Apprentice
Joined: 17 Dec 2003
Posts: 200
|
| Posted: Tue Mar 11, 2008 4:35 am Post subject: |
|
|
Umm err..  In my case, the newer version of nvidia-drivers is particularly picky about the modules you have *loaded* and the module that you have on your disk (or something close to that. I read it in the Changelog). I had just updated, but not rebooted, and nvidia-drivers was upset that the running module disagreed with the version I had just build.
| Code: | Mar 10 03:36:03 myhost kernel: NVRM: API mismatch: the client has the version 169.09, but
Mar 10 03:36:03 myhost kernel: NVRM: this kernel module has the version 100.14.19. Please
Mar 10 03:36:03 myhost kernel: NVRM: make sure that this kernel module and all NVIDIA driver
Mar 10 03:36:03 myhost kernel: NVRM: components have the same version. |
Seems obvious now, but, boy, at 3:00am it was SUPER confusing. 
Now that I've rebooted (or, more specifically, I've unloaded and reloaded nvidia.ko), everything seems fine again.
The link to my mplayer problems is probably the fact that I'd chosen "opengl" as my driver.
Thanks everyone,
Rich
_________________
I need a better signature... |
|
| Back to top |
|
|
|
Multimedia
