Hi,
da ich in der Vergangenheit immer wieder Probleme mit meiner Technotrend DVB S-3650 hatte und v4l-dvb-dkms hatte, habe ich auf meinem Acer Aspire Revo 3610 noch einmal yavdr0.4 sauber neu aufgesetzt. Diesmal wollte ich die s2-liplianin-dkms testen, aber das Installieren des Paketes aus dem Repository (aptitude update & aptitude dist-upgrade waren durchgeführt) führt leider reproduzierbar zum Einfiereren des ganzen Systems.
Die letzten Mitteilungen im Syslog sind
Nov 5 09:51:42 revo kernel: [ 1072.773562] ------------[ cut here ]------------
Nov 5 09:51:42 revo kernel: [ 1072.773579] kernel BUG at /build/buildd/linux-2.6.38/fs/dcache.c:2246!
Nov 5 09:51:42 revo kernel: [ 1072.773590] invalid opcode: 0000 [#1] SMP
Nov 5 09:51:42 revo kernel: [ 1072.773602] last sysfs file: /sys/devices/pci0000:00/0000:00:0b.0/host1/target1:0:0/1:0:0:0/block/sda/uevent
Nov 5 09:51:42 revo kernel: [ 1072.773614] CPU 0
Nov 5 09:51:42 revo kernel: [ 1072.773620] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc snd_hda_codec_hdmi nvidia(P) snd_hda_codec_realtek arc4 ath5k snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event ath psmouse mac80211 snd_seq joydev serio_raw cfg80211 snd_timer snd_seq_device snd shpchp soundcore snd_page_alloc i2c_nforce2 lp parport usbhid hid usb_storage uas ahci libahci forcedeth vesafb
Nov 5 09:51:42 revo kernel: [ 1072.773744]
Nov 5 09:51:42 revo kernel: [ 1072.773755] Pid: 13906, comm: video directory Tainted: P W 2.6.38-12-generic #51-Ubuntu Acer Aspire R3610/FMCP7A-ION-LE
Nov 5 09:51:42 revo kernel: [ 1072.773776] RIP: 0010:[<ffffffff8117a049>] [<ffffffff8117a049>] d_move+0x2a9/0x2f0
Nov 5 09:51:42 revo kernel: [ 1072.773804] RSP: 0000:ffff880054c2fa98 EFLAGS: 00010286
Nov 5 09:51:42 revo kernel: [ 1072.773813] RAX: ffff88005607ff00 RBX: ffff88005607ff00 RCX: 000000000000001b
Nov 5 09:51:42 revo kernel: [ 1072.773821] RDX: ffff88005603c000 RSI: ffff880007a38f00 RDI: ffff88005607ff00
Nov 5 09:51:42 revo kernel: [ 1072.773830] RBP: ffff880054c2fab8 R08: ffff880054f28000 R09: ffff880054f90020
Nov 5 09:51:42 revo kernel: [ 1072.773838] R10: 0000000000000001 R11: ffffc90000205000 R12: ffff880007a38f00
Nov 5 09:51:42 revo kernel: [ 1072.773849] R13: ffff8800561681c0 R14: ffff880007a38f00 R15: ffff8800561681e0
Nov 5 09:51:42 revo kernel: [ 1072.773861] FS: 00007f0e72819700(0000) GS:ffff88006fc00000(0000) knlGS:0000000000000000
Nov 5 09:51:42 revo kernel: [ 1072.773873] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 5 09:51:42 revo kernel: [ 1072.773882] CR2: 00002b94be6bb000 CR3: 00000000581d2000 CR4: 00000000000006f0
Nov 5 09:51:42 revo kernel: [ 1072.773892] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Nov 5 09:51:42 revo kernel: [ 1072.773903] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Nov 5 09:51:42 revo kernel: [ 1072.773915] Process video directory (pid: 13906, threadinfo ffff880054c2e000, task ffff8800581016e0)
Nov 5 09:51:42 revo kernel: [ 1072.773924] Stack:
Nov 5 09:51:42 revo kernel: [ 1072.773932] ffff880007a38f00 ffff88005607ff00 ffff88005607ff00 ffff8800561681c0
Nov 5 09:51:42 revo kernel: [ 1072.773950] ffff880054c2fb18 ffffffff8117bfc6 0000000000000000 0000000000000000
Nov 5 09:51:42 revo kernel: [ 1072.773967] 0000000000000000 0000000000000000 ffff880007a38f00 ffff8800560b81c0
Nov 5 09:51:42 revo kernel: [ 1072.773984] Call Trace:
Nov 5 09:51:42 revo kernel: [ 1072.774002] [<ffffffff8117bfc6>] d_materialise_unique+0x236/0x2a0
Nov 5 09:51:42 revo kernel: [ 1072.774045] [<ffffffffa0b637ad>] nfs_lookup+0x15d/0x1c0 [nfs]
Nov 5 09:51:42 revo kernel: [ 1072.774080] [<ffffffffa0b6656e>] nfs_atomic_lookup+0x1be/0x2d0 [nfs]
Nov 5 09:51:42 revo kernel: [ 1072.774114] [<ffffffffa0b65271>] ? nfs_lookup_revalidate+0x121/0x4d0 [nfs]
Nov 5 09:51:42 revo kernel: [ 1072.774135] [<ffffffff8116f145>] d_alloc_and_lookup+0x45/0x90
Nov 5 09:51:42 revo kernel: [ 1072.774150] [<ffffffff8117c665>] ? d_lookup+0x35/0x60
Nov 5 09:51:42 revo kernel: [ 1072.774165] [<ffffffff81171552>] do_lookup+0x182/0x2e0
Nov 5 09:51:42 revo kernel: [ 1072.774197] [<ffffffffa0b65ec2>] ? nfs_permission+0xe2/0x1d0 [nfs]
Nov 5 09:51:42 revo kernel: [ 1072.774214] [<ffffffff81171d06>] link_path_walk+0x656/0xc40
Nov 5 09:51:42 revo kernel: [ 1072.774229] [<ffffffff81171e9d>] ? link_path_walk+0x7ed/0xc40
Nov 5 09:51:42 revo kernel: [ 1072.774247] [<ffffffff811725eb>] do_path_lookup+0x5b/0x160
Nov 5 09:51:42 revo kernel: [ 1072.774262] [<ffffffff81173a5c>] do_filp_open+0x13c/0x7c0
Nov 5 09:51:42 revo kernel: [ 1072.774277] [<ffffffff81172962>] ? user_path_at+0x62/0xa0
Nov 5 09:51:42 revo kernel: [ 1072.774311] [<ffffffffa0b69c70>] ? nfs_attribute_cache_expired+0x30/0x50 [nfs]
Nov 5 09:51:42 revo kernel: [ 1072.774333] [<ffffffff812e6e37>] ? __strncpy_from_user+0x27/0x60
Nov 5 09:51:42 revo kernel: [ 1072.774352] [<ffffffff81180f17>] ? alloc_fd+0xf7/0x150
Nov 5 09:51:42 revo kernel: [ 1072.774368] [<ffffffff8116429a>] do_sys_open+0x6a/0x150
Nov 5 09:51:42 revo kernel: [ 1072.774383] [<ffffffff811643a0>] sys_open+0x20/0x30
Nov 5 09:51:42 revo kernel: [ 1072.774400] [<ffffffff8100c002>] system_call_fastpath+0x16/0x1b
Nov 5 09:51:42 revo kernel: [ 1072.774412] Code: c5 81 0b 80 00 00 00 eb c3 66 0f 1f 84 00 00 00 00 00 48 85 d2 0f 84 cc fd ff ff 0f 0b 0f 1f 44 00 00 48 85 d2 0f 84 9c fd ff ff <0f> 0b 0f 1f 44 00 00 49 8b 44 24 18 48 89 43 18 49 8d 84 24 90
Nov 5 09:51:42 revo kernel: [ 1072.774552] RIP [<ffffffff8117a049>] d_move+0x2a9/0x2f0
Nov 5 09:51:42 revo kernel: [ 1072.774570] RSP <ffff880054c2fa98>
Nov 5 09:51:42 revo kernel: [ 1072.774583] ---[ end trace a5d5ca969bcfb879 ]---
Nov 5 09:51:45 revo vdr: [13818] switching to channel 1
Nov 5 09:51:45 revo vdr: [13818] switching to channel 1
Nov 5 09:51:45 revo vdr: [13818] info: Kanal nicht verfügbar!
Nov 5 09:51:56 revo vdr: [13818] switching to channel 1
Nov 5 09:51:56 revo vdr: [13818] info: Kanal nicht verfügbar!
Nov 5 09:52:07 revo vdr: [13818] switching to channel 1
Nov 5 09:52:07 revo vdr: [13818] info: Kanal nicht verfügbar!
Alles anzeigen
lspci liefert
lspci
00:00.0 Host bridge: nVidia Corporation MCP79 Host Bridge (rev b1)
00:00.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
00:03.0 ISA bridge: nVidia Corporation MCP79 LPC Bridge (rev b2)
00:03.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
00:03.2 SMBus: nVidia Corporation MCP79 SMBus (rev b1)
00:03.3 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
00:03.5 Co-processor: nVidia Corporation MCP79 Co-processor (rev b1)
00:04.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:04.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
00:08.0 Audio device: nVidia Corporation MCP79 High Definition Audio (rev b1)
00:09.0 PCI bridge: nVidia Corporation MCP79 PCI Bridge (rev b1)
00:0a.0 Ethernet controller: nVidia Corporation MCP79 Ethernet (rev b1)
00:0b.0 IDE interface: nVidia Corporation MCP79 SATA Controller (rev b1)
00:0c.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
00:10.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
00:15.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
00:16.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
00:17.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
00:18.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
03:00.0 VGA compatible controller: nVidia Corporation ION VGA (rev b1)
05:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)
Alles anzeigen
Wie man sieht, zuckt das System noch etwas (vdr schreibt noch seine Informationen), aber alle Shell Prozesse (SSH sessions via Network, Virtuelle Terminals usw) reagieren nicht mehr und das System läßt sich nur noch via MagicSysRq zum Neustart bewegen. An solche "Tainted" kann ich mich zuletzt als Todesmeldugen von Xen VM Guest erinnern, die ich auf Ubuntu 8.04 betrieben habe und das lag an völlig vergurkter Implementierung der Xen Installation.
Haben die Treiber der s2-liplianin-dkms ähnliche Probleme? Unter yavdr04pre2 habe ich auf einem anderen System die noch sauber installieren können (allerdings andere Hardware)
Erstaunlicherweise passiert es ja beim Kompilieren der Treiber, aktiv sind sie ja noch gar nicht....
Any ideas?
Gruss aus Kölle