Erstmal die Vorgeschichte in Kurzform:
Kurz vor Ostern setzten plötzlich extreme Empfangsprobleme ein; da dies unmittelbar nach einem apt-get dist-upgrade (yavdr 0.3) geschah, war der erste Verdächtige klar... Beim Booten einer älteren Version von einer Backup-Partition blieb das Problem jedoch bestehen, also wohl den falschen verdächtigt (sorry dafür).
Also erstmal komplett neu installiert (diesmal yavdr 0.4) - keine Besserung.
Daraufhin sukzessive die Hardware getauscht: RAM, Mainboard (exakt gleiches Modell), DVb-Karte (von Cine S2 Rev. 5.4/ngene auf 2*Duoflex S2 an Oktopus miniPCIe/ddbridge), Antennenkabel - kein Erfolg.
Zum Schluss den LNB gewechselt, daraufhin hab ich gar kein Bild mehr.
Das ddbridge-Modul wird zwar geladen, im syslog findet sich aber folgendes:
Code
Apr 14 20:08:55 yavdr1 udevd-work[359]: '/sbin/modprobe -bv pci:v0000DD01d000000
03sv0000DD01sd00000010bc04sc80i00' unexpected exit with status 0x000b
Apr 14 20:08:55 yavdr1 kernel: [ 10.629810] I2C timeout
Apr 14 20:08:55 yavdr1 kernel: [ 10.629820] IRS 00000000
Apr 14 20:08:55 yavdr1 kernel: [ 10.630388] No STV0900 found!
Apr 14 20:08:55 yavdr1 kernel: [ 10.630395] port_attach on port 0 failed
Apr 14 20:08:55 yavdr1 kernel: [ 10.693532] fail3
Apr 14 20:08:55 yavdr1 kernel: [ 10.693542] fail2
Apr 14 20:08:55 yavdr1 kernel: [ 10.708215] fail1
Apr 14 20:08:55 yavdr1 kernel: [ 10.708269] ------------[ cut here ]----------
--
Apr 14 20:08:55 yavdr1 kernel: [ 10.708277] kernel BUG at /build/buildd/linux-
2.6.38/drivers/pci/msi.c:315!
Apr 14 20:08:55 yavdr1 kernel: [ 10.708285] invalid opcode: 0000 [#1] SMP
Apr 14 20:08:55 yavdr1 kernel: [ 10.708291] last sysfs file: /sys/module/lockd
/initstate
Apr 14 20:08:55 yavdr1 kernel: [ 10.708297] CPU 1
Apr 14 20:08:55 yavdr1 kernel: [ 10.708301] Modules linked in: snd_seq_device
nfs lockd fscache nfs_acl auth_rpcgss sunrpc joydev stv090x snd ddbridge(+) psmo
use dvb_core soundcore serio_raw cxd2099 shpchp i2c_nforce2 snd_page_alloc lp pa
rport xfs hid_logitech ff_memless exportfs usbhid hid ahci libahci forcedeth vesafb
Apr 14 20:08:55 yavdr1 kernel: [ 10.708352]
Apr 14 20:08:55 yavdr1 kernel: [ 10.708360] Pid: 491, comm: modprobe Tainted:
P 2.6.38-14-generic #58-Ubuntu To Be Filled By O.E.M. To Be Filled By
O.E.M./To be filled by O.E.M.
Apr 14 20:08:55 yavdr1 kernel: [ 10.708375] RIP: 0010:[<ffffffff81313c91>] [<
ffffffff81313c91>] free_msi_irqs+0x141/0x150
Apr 14 20:08:55 yavdr1 kernel: [ 10.708395] RSP: 0018:ffff8800b6513bc8 EFLAGS: 00010282
Apr 14 20:08:55 yavdr1 kernel: [ 10.708402] RAX: ffff8800b5ebe100 RBX: ffff8800b79a3f00 RCX: 0000000000000000
Apr 14 20:08:55 yavdr1 kernel: [ 10.708409] RDX: 0000000000000000 RSI: 0000000000000029 RDI: 0000000000000000
Apr 14 20:08:55 yavdr1 kernel: [ 10.708416] RBP: ffff8800b6513c08 R08: ffff8800b5ebe100 R09: ffff8800bc000160
Apr 14 20:08:55 yavdr1 kernel: [ 10.708423] R10: 0000000000000000 R11: 0000000000000002 R12: ffff8800b87bf8f0
Apr 14 20:08:55 yavdr1 kernel: [ 10.708430] R13: 0000000000000001 R14: ffff8800b87bf000 R15: 0000000000000000
Apr 14 20:08:55 yavdr1 kernel: [ 10.708439] FS: 00007f3662990720(0000) GS:ffff8800bff2a000(0000) knlGS:0000000000000000
Apr 14 20:08:55 yavdr1 kernel: [ 10.708447] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Apr 14 20:08:55 yavdr1 kernel: [ 10.708454] CR2: 00007ff1ce549000 CR3: 00000000b57f1000 CR4: 00000000000006e0
Apr 14 20:08:55 yavdr1 kernel: [ 10.708461] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 14 20:08:55 yavdr1 kernel: [ 10.708469] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Apr 14 20:08:55 yavdr1 kernel: [ 10.708477] Process modprobe (pid: 491, threadinfo ffff8800b6512000, task ffff880036c00000)
Apr 14 20:08:55 yavdr1 kernel: [ 10.708483] Stack:
Apr 14 20:08:55 yavdr1 kernel: [ 10.708487] ffff8800b6513c08 0000000181314ba2 ffffc90000000008 ffff8800b87bf000
Apr 14 20:08:55 yavdr1 kernel: [ 10.708498] ffffc90003088000 ffff8800b87bf000 0000000000000000 0000000000000000
Apr 14 20:08:55 yavdr1 kernel: [ 10.708508] ffff8800b6513c28 ffffffff81314c55 0000000000000000 ffff8800b87bf000
Apr 14 20:08:55 yavdr1 kernel: [ 10.708518] Call Trace:
Apr 14 20:08:55 yavdr1 kernel: [ 10.708532] [<ffffffff81314c55>] pci_disable_msi+0x45/0x50
Apr 14 20:08:55 yavdr1 kernel: [ 10.708549] [<ffffffffa01c0741>] ddb_probe+0xd9e/0xefd [ddbridge]
Apr 14 20:08:55 yavdr1 kernel: [ 10.708562] [<ffffffff81300c5f>] local_pci_probe+0x5f/0xd0
Apr 14 20:08:55 yavdr1 kernel: [ 10.708573] [<ffffffff81302559>] pci_device_probe+0x129/0x130
Apr 14 20:08:55 yavdr1 kernel: [ 10.708586] [<ffffffff813bb14a>] ? driver_sysfs_add+0x7a/0xb0
Apr 14 20:08:55 yavdr1 kernel: [ 10.708597] [<ffffffff813bb278>] really_probe+0x68/0x190
Apr 14 20:08:55 yavdr1 kernel: [ 10.708608] [<ffffffff813bb585>] driver_probe_device+0x45/0x70
Apr 14 20:08:55 yavdr1 kernel: [ 10.708619] [<ffffffff813bb65b>] __driver_attach+0xab/0xb0
Apr 14 20:08:55 yavdr1 kernel: [ 10.708630] [<ffffffff813bb5b0>] ? __driver_attach+0x0/0xb0
Apr 14 20:08:55 yavdr1 kernel: [ 10.708640] [<ffffffff813ba3fe>] bus_for_each_dev+0x5e/0x90
Apr 14 20:08:55 yavdr1 kernel: [ 10.708651] [<ffffffff813bb0ce>] driver_attach+0x1e/0x20
Apr 14 20:08:55 yavdr1 kernel: [ 10.708661] [<ffffffff813bac35>] bus_add_driver+0xc5/0x280
Apr 14 20:08:55 yavdr1 kernel: [ 10.708675] [<ffffffffa013c000>] ? module_init_ddbridge+0x0/0x1000 [ddbridge]
Apr 14 20:08:55 yavdr1 kernel: [ 10.708686] [<ffffffff813bb8f6>] driver_register+0x76/0x140
Apr 14 20:08:55 yavdr1 kernel: [ 10.708701] [<ffffffffa013c000>] ? module_init_ddbridge+0x0/0x1000 [ddbridge]
Apr 14 20:08:55 yavdr1 kernel: [ 10.708711] [<ffffffff81301306>] __pci_register_driver+0x56/0xd0
Apr 14 20:08:55 yavdr1 kernel: [ 10.708725] [<ffffffffa013c07e>] module_init_ddbridge+0x7e/0x1000 [ddbridge]
Apr 14 20:08:55 yavdr1 kernel: [ 10.708738] [<ffffffff81002175>] do_one_initcall+0x45/0x190
Apr 14 20:08:55 yavdr1 kernel: [ 10.708750] [<ffffffff810a508b>] sys_init_module+0xfb/0x250
Apr 14 20:08:55 yavdr1 kernel: [ 10.708761] [<ffffffff8100c002>] system_call_fastpath+0x16/0x1b
Apr 14 20:08:55 yavdr1 kernel: [ 10.708768] Code: 68 f0 f6 03 01 75 b3 48 8b 43 10 eb b2 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f c9 c3 48 8b 7b 20 e8 a5 cd d2 ff 48 8b 43 10 eb 94 <0f> 0b 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 0f 1f
Apr 14 20:08:55 yavdr1 kernel: [ 10.708845] RIP [<ffffffff81313c91>] free_msi_irqs+0x141/0x150
Apr 14 20:08:55 yavdr1 kernel: [ 10.708856] RSP <ffff8800b6513bc8>
Apr 14 20:08:55 yavdr1 kernel: [ 10.708864] ---[ end trace 6c7837ec50f98b46 ]---
Zum Thema i2c findet sich auch ein verdächtiger Eintrag:
Code
Apr 14 20:08:53 yavdr1 kernel: [ 7.871647] i2c i2c-0: nForce2 SMBus adapter at 0x4d00
Apr 14 20:08:53 yavdr1 kernel: [ 7.871667] ACPI: resource nForce2_smbus [io 0x4e00-0x4e3f] conflicts with ACPI region SM00 [io 0x4e00-0x4e3f]
Apr 14 20:08:53 yavdr1 kernel: [ 7.871676] ACPI: This conflict may cause random problems and system instability
Apr 14 20:08:53 yavdr1 kernel: [ 7.871684] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Apr 14 20:08:53 yavdr1 kernel: [ 7.871818] i2c i2c-1: nForce2 SMBus adapter at 0x4e00Bevor ich jetzt wieder Turnübungen mache, um die Antenne abzumontieren und zu zerlegen, um an den LNB ranzukommen:
Was hat ein i2c-Bus-Problem mit einem neuen LNB zu tun?
Kann ein defekter LNB dazu führen? Oder ein falscher LNB (vielleicht quattro statt quad? Wer liest schon die Beschriftung auf dem Teil, wenn auf dem Lieferschein das richtige steht 
)