[MPlayer-users] Signal 11 when mplayer connect to Helix Server 11.

Ryo Murakawa FZZ01471 at nifty.ne.jp
Mon Jun 5 14:52:40 CEST 2006


Hi, All.
Now we have already installed mplayer-1.0-0.20.pre7.2.el4.rf package  
on CentOS 4.3.
And we have already set up helix server in my office.
But when we try to play mpeg-4 content with this mplayer, we get the  
error below.


[izumi at localhost ~]$ mplayer rtsp://blue.sgi.co.jp:554/mpg4video.mp4
Using GNU internationalization
Original domain: messages
Original dirname: /usr/share/locale
Current domain: mplayer
Current dirname: /usr/share/locale

MPlayer 1.0pre7-3.4.4 (C) 2000-2005 MPlayer Team
CPU: Intel  (Family: 8, Stepping: 9)
Detected cache-line size is 64 bytes
CPUflags:  MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1

Linux RTC init error in ioctl (rtc_irqp_set 1024): Permission denied
Try adding "echo 1024 > /proc/sys/dev/rtc/max-user-freq" to your  
system startup scripts.
Opening joystick device /dev/input/js0
Can't open joystick device /dev/input/js0 : No such file or directory
Can't init input joystick
Setting up LIRC support...
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support.
You will not be able to use your remote control.
Playing rtsp://blue.sgi.co.jp:554/mpg4video.mp4.
Resolving blue.sgi.co.jp for AF_INET6...
Couldn't resolve name for AF_INET6: blue.sgi.co.jp
Resolving blue.sgi.co.jp for AF_INET...
Connecting to server blue.sgi.co.jp[192.82.185.117]:554 ...


MPlayer interrupted by signal 11 in module: open_stream
- MPlayer crashed by bad usage of CPU/FPU/RAM.
   Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
   disassembly. Details in DOCS/HTML/en/ 
bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen.
   It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
   gcc version. If you think it's MPlayer's fault, please read
   DOCS/HTML/en/bugreports.html and follow the instructions there. We  
can't and
   won't help unless you provide this information when reporting a  
possible bug.

I want to know the resolved method for this problem.
So could anyoune advice me?

Best Regards.

Ryo Murakawa



More information about the MPlayer-users mailing list