We are trying to use gstreamer for accessing of a MPEG4 video stream
via RTSP/RTP. We use rtspsrc gstreamer element to get RTP video stream
from the video server.
But it doesn't work correctly. We found that the problem concerns
about the network interface being used (eth0) (RTP packets doen't
received correctly).
Also we noted wierd message about ethernet interface driver that is
thrown out during the kernel booting:
[ 19.072418] smsc911x: Driver version 2008-10-21.
[ 19.758392] irq 336: nobody cared (try booting with the "irqpoll"
option)
[ 19.765258] [<c003ab54>] (unwind_backtrace+0x0/0xdc) from
[<c009b9c4>] (__report_bad_irq+0x30/0x88)
[ 19.774383] [<c009b9c4>] (__report_bad_irq+0x30/0x88) from
[<c009bb68>] (note_interrupt+0x14c/0x1d0)
[ 19.783569] [<c009bb68>] (note_interrupt+0x14c/0x1d0) from
[<c009c5bc>] (handle_level_irq+0xe0/0x150)
[ 19.792877] [<c009c5bc>] (handle_level_irq+0xe0/0x150) from
[<c004cf98>] (gpio_irq_handler+0xfc/0x12c)
[ 19.802246] [<c004cf98>] (gpio_irq_handler+0xfc/0x12c) from
[<c0035070>] (asm_do_IRQ+0x70/0x90)
[ 19.811004] [<c0035070>] (asm_do_IRQ+0x70/0x90) from [<c0035ac4>]
(__irq_svc+0x44/0xa8)
[ 19.819061] Exception stack(0xcf81fe38 to 0xcf81fe80)
[ 19.824157]
fe20: 00000000
00010000
[ 19.832397] fe40: 00000000 00000000 c0613adc cfa09540 00000000
00000150 60000013 00000040
[ 19.840606] fe60: c0613afc 00000000 fb058000 cf81fe80 c009bdfc
c009b098 60000013 ffffffff
[ 19.848846] [<c0035ac4>] (__irq_svc+0x44/0xa8) from [<c009b098>]
(__setup_irq+0x234/0x340)
[ 19.857177] [<c009b098>] (__setup_irq+0x234/0x340) from
[<c009b318>] (request_threaded_irq+0x174/0x1c4)
[ 19.866668] [<c009b318>] (request_threaded_irq+0x174/0x1c4) from
[<c045f944>] (smsc911x_drv_probe+0x6e8/0x1520)
[ 19.876831] [<c045f944>] (smsc911x_drv_probe+0x6e8/0x1520) from
[<c02a7760>] (platform_drv_probe+0x18/0x1c)
[ 19.886657] [<c02a7760>] (platform_drv_probe+0x18/0x1c) from
[<c02a6720>] (driver_probe_device+0xc0/0x178)
[ 19.896362] [<c02a6720>] (driver_probe_device+0xc0/0x178) from
[<c02a6838>] (__driver_attach+0x60/0x84)
[ 19.905822] [<c02a6838>] (__driver_attach+0x60/0x84) from
[<c02a5ea8>] (bus_for_each_dev+0x44/0x74)
[ 19.914947] [<c02a5ea8>] (bus_for_each_dev+0x44/0x74) from
[<c02a5800>] (bus_add_driver+0x140/0x2cc)
[ 19.924163] [<c02a5800>] (bus_add_driver+0x140/0x2cc) from
[<c02a6b2c>] (driver_register+0xa8/0x130)
[ 19.933349] [<c02a6b2c>] (driver_register+0xa8/0x130) from
[<c0035364>] (do_one_initcall+0x5c/0x1b4)
[ 19.942535] [<c0035364>] (do_one_initcall+0x5c/0x1b4) from
[<c0008408>] (kernel_init+0xa0/0x124)
[ 19.951385] [<c0008408>] (kernel_init+0xa0/0x124) from [<c0036960>]
(kernel_thread_exit+0x0/0x8)
[ 19.960235] handlers:
[ 19.962524] [<c02eafc8>] (smsc911x_irqhandler+0x0/0x6b0)
[ 19.967895] Disabling IRQ #336
[ 19.972167] smsc911x-mdio: probed
[ 19.975585] eth0: attached PHY driver [Generic PHY]
(mii_bus:phy_addr=0:01, irq=-1)
Can anybody to make a conjecture what's a problem with?.. Any advices
would be very useful.
We use Angstrem linux distribution on OMAP3530 beagleboard device.
Thanks very much!
We are trying to use gstreamer for accessing of a MPEG4 video stream
via RTSP/RTP. We use rtspsrc gstreamer element to get RTP video stream
from the video server.
But it doesn't work correctly. We found that the problem concerns
about the network interface being used (eth0) (RTP packets doen't
received correctly).
Also we noted wierd message about ethernet interface driver that is
thrown out during the kernel booting:
I have no idea what might be the reasons for these kernel output, but
just to reduce the problem scope - is there a chance that you can try
your application at some other host (like for example standard x86
notebook) and make sure that it works? Ideally, just to test the
pipeline with gst-launch. If it works, then the problem might not be
related to the gstreamer at all. It just triggers some other problem.
If not, than you can probable first make sure that your application
does not have errors and then continue investigate the problem with
network interface.
I understand that this suggestion does not bring you really further,
but maybe it still could be helpful.
It works fine on x86 Linux host, but doesn't work on beagleboard
Angstrem device.
Also if we make the video stream is being obtained from a local file
it works fine everywhere (on Beagleboard device and on x86 host), so
this pipeline:
works on x86 host but doesn't work on Beagleboard Angstrem host.
So we can suggest that the problem is at network driver functionality.
The transfering of non-realtime content between Beagleboard device and
other host works fine.
So at our point of view it seems like a problem in network driver
functionality...
We will very gratful to anyone who can help us.
Maybe someone already encountered with similar problem...
It works fine on x86 Linux host, but doesn't work on beagleboard
Angstrem device.
Also if we make the video stream is being obtained from a local file
it works fine everywhere (on Beagleboard device and on x86 host), so
this pipeline:
works on x86 host but doesn't work on Beagleboard Angstrem host.
So we can suggest that the problem is at network driver functionality.
The transfering of non-realtime content between Beagleboard device and
other host works fine.
So at our point of view it seems like a problem in network driver
functionality...
We will very gratful to anyone who can help us.
Maybe someone already encountered with similar problem...
It works fine on x86 Linux host, but doesn't work on beagleboard
Angstrem device.
Also if we make the video stream is being obtained from a local file
it works fine everywhere (on Beagleboard device and on x86 host), so
this pipeline:
works on x86 host but doesn't work on Beagleboard Angstrem host.
So we can suggest that the problem is at network driver functionality.
The transfering of non-realtime content between Beagleboard device and
other host works fine.
So at our point of view it seems like a problem in network driver
functionality...
We will very gratful to anyone who can help us.
Maybe someone already encountered with similar problem...