| 

.NET C# Java Javascript Exception

2
Hallo zusammen,

aus unerklärlichen Gründen hängt sich unser Server (SUSE11.2) (neuerdings) alle paar Tage auf und muss hardresettet werden.

Hier der letzte Logeintrag mit einer Kernelmeldung aus /var/log/messages:

Dec  1 05:35:05 workserver kernel: Eeek! page_mapcount(page) went negative! (-1)
Dec 1 05:35:05 workserver kernel: page pfn = 11b91
Dec 1 05:35:05 workserver kernel: page->flags = 1008000001002c
Dec 1 05:35:05 workserver kernel: page->count = 2
Dec 1 05:35:05 workserver kernel: page->mapping = ffff81002ec78e68
Dec 1 05:35:05 workserver kernel: vma->vm_ops = 0x0
Dec 1 05:35:05 workserver kernel: ------------[ cut here ]------------
Dec 1 05:35:05 workserver kernel: kernel BUG at mm/rmap.c:669!
Dec 1 05:35:05 workserver kernel: invalid opcode: 0000 [3] SMP
Dec 1 05:35:05 workserver kernel: last sysfs file: /sys/devices/system/cpu/cpu3/cache/index2/shared_cpu_map
Dec 1 05:35:05 workserver kernel: CPU 0
Dec 1 05:35:05 workserver kernel: Modules linked in: ip6t_LOG xt_tcpudp xt_pkttype ipt_LOG xt_limit ip6t_REJECT nf_conntrack_ipv6 ipt_REJECT xt_state iptable_mangle iptable_nat nf_nat iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack ip_tables cpufreq_conservative cpufreq_userspace cpufreq_powersave powernow_k8 ip6table_filter ip6_tables x_tables ipv6 quota_v2 fuse loop raid456 async_xor async_memcpy async_tx xor dm_mod ppdev parport_pc sr_mod rtc_cmos rtc_core shpchp pci_hotplug rtc_lib parport serio_raw wmi forcedeth usb_storage cdrom button sg ohci_hcd ehci_hcd sd_mod usbcore edd ext3 mbcache jbd fan pata_amd ahci libata scsi_mod dock thermal processor
Dec 1 05:35:05 workserver kernel: Pid: 7767, comm: monitor.pl Tainted: G B D N 2.6.25.18-0.2-default #1
Dec 1 05:35:05 workserver kernel: RIP: 0010:[<ffffffff8028bc4f>] [<ffffffff8028bc4f>] page_remove_rmap+0x120/0x13a
Dec 1 05:35:05 workserver kernel: RSP: 0000:ffff810093ca9a58 EFLAGS: 00010246
Dec 1 05:35:05 workserver kernel: RAX: 0000000000000000 RBX: ffffe200003e07b8 RCX: ffffe200038538c8
Dec 1 05:35:05 workserver kernel: RDX: 0000000000000046 RSI: 0000000000000046 RDI: 0000000000000296
Dec 1 05:35:05 workserver kernel: RBP: ffff810093ca9a68 R08: 0000000000000000 R09: ffff81013b8f8000
Dec 1 05:35:05 workserver kernel: R10: ffffffff8052281c R11: ffffffff80815320 R12: ffff8101345a83f8
Dec 1 05:35:05 workserver kernel: R13: ffffe200003e07b8 R14: ffffe200038538c8 R15: ffff81009dc30158
Dec 1 05:35:05 workserver kernel: FS: 00007f2b4485f6f0(0000) GS:ffffffff80632000(0000) knlGS:0000000000000000
Dec 1 05:35:05 workserver kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 1 05:35:05 workserver kernel: CR2: 0000000000c2b488 CR3: 00000000af105000 CR4: 00000000000006e0
Dec 1 05:35:05 workserver kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Dec 1 05:35:05 workserver kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Dec 1 05:35:05 workserver kernel: Process monitor.pl (pid: 7767, threadinfo ffff810093ca8000, task ffff810025510480)
Dec 1 05:35:05 workserver kernel: Stack: 000000009dc30000 0000000000000000 ffff810093ca9ae8 ffffffff80282c80
Dec 1 05:35:05 workserver kernel: ffff810093ca9aa8 ffff81004e98a030 ffff81009dc30158 0000000000c2b488
Dec 1 05:35:05 workserver kernel: ffff8101345a83f8 ffff81013cd8d400 ffffe20002282a90 ffffffff880d05a6
Dec 1 05:35:05 workserver kernel: Call Trace:
Dec 1 05:35:05 workserver kernel: [<ffffffff80282c80>] do_wp_page+0x411/0x5b5
Dec 1 05:35:05 workserver kernel: [<ffffffff80284900>] handle_mm_fault+0x874/0x940
Dec 1 05:35:05 workserver kernel: [<ffffffff8044bf82>] do_page_fault+0x676/0xabf
Dec 1 05:35:05 workserver kernel: [<ffffffff80449ca9>] error_exit+0x0/0x60
Dec 1 05:35:05 workserver kernel: [<000000000046dfdd>]
Dec 1 05:35:05 workserver kernel:
Dec 1 05:35:05 workserver kernel:
Dec 1 05:35:05 workserver kernel: Code: e8 f1 f9 fc ff 49 8b 84 24 90 00 00 00 48 85 c0 74 19 48 8b 40 20 48 85 c0 74 10 48 8b 70 58 48 c7 c7 5a 28 52 80 e8 cb f9 fc ff <0f> 0b eb fe 48 8b 77 18 83 e6 01 f7 de 83 c6 04 e8 f3 49 ff ff
Dec 1 05:35:05 workserver kernel: RIP [<ffffffff8028bc4f>] page_remove_rmap+0x120/0x13a
Dec 1 05:35:05 workserver kernel: RSP <ffff810093ca9a58>
Dec 1 05:35:05 workserver kernel: ---[ end trace c0ca3258e1a45304 ]---


Leider bin ich nicht derart in der Hardware firm, dass ich wüsste, was hier für ein Problem vorliegt.

Vielen Dank für Eure Hilfe!
News:
01.12.2011
doublem 683 1 1 9
1 Antwort
2
Eine kurze Suche mit der ersten Zeile liefert massenhaft Seiten, in denen Nutzer ein ähnliches Verhalten feststellen. Eine Ursache kann in diesem Fall ein defekter Speicherchip sein. Teste mal den Hauptspeicher, z.B. mit memtester.
Gruß
Daniel.
01.12.2011
puls200 3,8k 7
Danke, das werde ich testen.
doublem 01.12.2011

Stelle deine Linux-Frage jetzt!