saa7130 video card problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I've just replaced my Pinaccle card with a SAA7130 card. The system has
recognised the card, but tvtime is giving absolutely nothing out -just a
black screen.

When I right click to set things up, I get a video card called "default"
but am unable to do a channel scan or anything like that.

dmesg comes up with

Linux version 2.6.19-1.2911.fc7 
Linux video capture interface: v2.00
saa7130/34: v4l2 driver version 0.2.14 loaded
ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
ACPI: PCI Interrupt 0000:02:0a.0[A] -> Link [APC3] -> GSI 18 (level,
low) -> IRQ 18
saa7130[0]: found at 0000:02:0a.0, rev: 1, irq: 18, latency: 32, mmio:
0xf700c000
saa7130[0]: subsystem: 1301:2001, board: UNKNOWN/GENERIC
[card=0,autodetected]
saa7130[0]: board init: gpio is 0
saa7130[0]: i2c eeprom 00: 01 13 01 20 08 20 1c 55 43 43 a9 1c 55 43 43
a9
saa7130[0]: i2c eeprom 10: ff ff 00 00 ff ff ff ff ff ff ff ff ff ff ff
ff
saa7130[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff
saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff
saa7130[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff
saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff
saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff
saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff
saa7130[0]: i2c scan: found device @ 0xa0  [eeprom]
saa7130[0]: i2c scan: found device @ 0xc0  [tuner (analog)]
saa7130[0]: i2c scan: found device @ 0xc2  [???]
saa7130[0]: registered device video0 [v4l2]
saa7130[0]: registered device vbi0


=======================================================
[ INFO: possible circular locking dependency detected ]
2.6.19-1.2911.fc7 #1
-------------------------------------------------------
tvtime/3389 is trying to acquire lock:
 (&mm->mmap_sem){----}, at: [<ffffffff8820c870>] videobuf_dma_init_user
+0xcd/0x174 [video_buf]

but task is already holding lock:
 (&q->lock#2){--..}, at: [<ffffffff80262305>] mutex_lock+0x2a/0x2e

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&q->lock#2){--..}:
       [<ffffffff802a579c>] __lock_acquire+0x90e/0xa50
       [<ffffffff802a5bbb>] lock_acquire+0x4c/0x65
       [<ffffffff80262305>] mutex_lock+0x2a/0x2e
       [<ffffffff80262151>] __mutex_lock_slowpath+0xef/0x279
       [<ffffffff8020e144>] do_mmap_pgoff+0x44a/0x7e9
       [<ffffffff80262305>] mutex_lock+0x2a/0x2e
       [<ffffffff8820b73a>] videobuf_mmap_mapper+0x1c/0x23c [video_buf]
       [<ffffffff8821d708>] video_mmap+0x35/0x37 [saa7134]
       [<ffffffff8020e1e6>] do_mmap_pgoff+0x4ec/0x7e9
       [<ffffffff802a4a0b>] trace_hardirqs_on+0x11a/0x13e
       [<ffffffff80223fa9>] sys_mmap+0x90/0x119
       [<ffffffff8025c2b5>] tracesys+0xdc/0xe1
       [<ffffffffffffffff>] 0xffffffffffffffff

-> #0 (&mm->mmap_sem){----}:
       [<ffffffff802a56ae>] __lock_acquire+0x820/0xa50
       [<ffffffff802a5bbb>] lock_acquire+0x4c/0x65
       [<ffffffff8820c870>] videobuf_dma_init_user+0xcd/0x174
[video_buf]
       [<ffffffff802a1723>] down_read+0x3e/0x4a
       [<ffffffff8820c870>] videobuf_dma_init_user+0xcd/0x174
[video_buf]
       [<ffffffff8820c6cd>] videobuf_dma_free+0x7a/0xa3 [video_buf]
       [<ffffffff8820cbc7>] videobuf_iolock+0x86/0xd5 [video_buf]
       [<ffffffff8821b19a>] buffer_prepare+0x194/0x206 [saa7134]
       [<ffffffff8820d243>] videobuf_qbuf+0x242/0x2ef [video_buf]
       [<ffffffff8821c90d>] video_do_ioctl+0xdeb/0xf5d [saa7134]
       [<ffffffff8031fd4d>] avc_has_perm+0x49/0x5b
       [<ffffffff881eb6c0>] video_usercopy+0x1d1/0x2a9 [videodev]
       [<ffffffff802164a3>] prio_tree_insert+0x18c/0x231
       [<ffffffff8821bb22>] video_do_ioctl+0x0/0xf5d [saa7134]
       [<ffffffff8821a21c>] video_ioctl+0x10/0x12 [saa7134]
       [<ffffffff80240fe9>] do_ioctl+0x5e/0x77
       [<ffffffff80230688>] vfs_ioctl+0x260/0x27d
       [<ffffffff8024b62b>] sys_ioctl+0x5f/0x82
       [<ffffffff8025c2b5>] tracesys+0xdc/0xe1
       [<ffffffffffffffff>] 0xffffffffffffffff

other info that might help us debug this:

1 lock held by tvtime/3389:
 #0:  (&q->lock#2){--..}, at: [<ffffffff80262305>] mutex_lock+0x2a/0x2e

stack backtrace:

Call Trace:
 [<ffffffff802a3eca>] print_circular_bug_tail+0x70/0x7b
 [<ffffffff802a56ae>] __lock_acquire+0x820/0xa50
 [<ffffffff802a5bbb>] lock_acquire+0x4c/0x65
 [<ffffffff8820c870>] :video_buf:videobuf_dma_init_user+0xcd/0x174
 [<ffffffff802a1723>] down_read+0x3e/0x4a
 [<ffffffff8820c870>] :video_buf:videobuf_dma_init_user+0xcd/0x174
 [<ffffffff8820c6cd>] :video_buf:videobuf_dma_free+0x7a/0xa3
 [<ffffffff8820cbc7>] :video_buf:videobuf_iolock+0x86/0xd5
 [<ffffffff8821b19a>] :saa7134:buffer_prepare+0x194/0x206
 [<ffffffff8820d243>] :video_buf:videobuf_qbuf+0x242/0x2ef
 [<ffffffff8821c90d>] :saa7134:video_do_ioctl+0xdeb/0xf5d
 [<ffffffff8031fd4d>] avc_has_perm+0x49/0x5b
 [<ffffffff881eb6c0>] :videodev:video_usercopy+0x1d1/0x2a9
 [<ffffffff802164a3>] prio_tree_insert+0x18c/0x231
 [<ffffffff8821bb22>] :saa7134:video_do_ioctl+0x0/0xf5d
 [<ffffffff8821a21c>] :saa7134:video_ioctl+0x10/0x12
 [<ffffffff80240fe9>] do_ioctl+0x5e/0x77
 [<ffffffff80230688>] vfs_ioctl+0x260/0x27d
 [<ffffffff8024b62b>] sys_ioctl+0x5f/0x82
 [<ffffffff8025c2b5>] tracesys+0xdc/0xe1

Any help on setting this up would help! I am not sure if the above is a
tvtime problem or a kernel problem.

TTFN

Paul
-- 
"Mmmmmmmm....Shakira geschmiert mit schokolade" sagt Homer

Attachment: signature.asc
Description: This is a digitally signed message part

-- 
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe: 
https://www.redhat.com/mailman/listinfo/fedora-test-list

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]