[Eisfair] Server nicht erreichbar

[Carsten Weisky]

Das gleiche mittlerweile  das 2. Mal heute.

Bitte helft mir!!!





Am 12.06.2013 07:55, schrieb Carsten Weisky:
> Hallo zusammen,
> heute war zum zweiten mal nacheinander (in 2 Tagen) mein Eis1 nicht mehr
> zu erreichen.
> in der messages.log steht folgende Meldung von gestern:
> könnt Ihr mir weiterhelfen..
>
> messages:
> Jun 11 17:41:41 server kernel: ------------[ cut here ]------------
> Jun 11 17:41:42 server kernel: WARNING: at net/sched/sch_generic.c:261
> dev_watchdog+0xf9/0x177()
> Jun 11 17:41:42 server kernel: Hardware name: G31M-ES2L
> Jun 11 17:41:42 server kernel: NETDEV WATCHDOG: eth0 (r8169): transmit
> queue 0 timed out
> Jun 11 17:41:42 server kernel: Modules linked in: capidrv isdn slhc
> f1pci(P) capi kernelcapi i2c_i801 i2c_core snd_hda_codec_realtek
> snd_hda_intel snd_hda_codec snd_pcm snd_timer snd soundcore
> snd_page_alloc 8139too nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp
> xt_conntrack xt_recent xt_state nf_conntrack xt_limit ipt_REJECT ipt_LOG
> iptable_filter ip_tables x_tables nls_iso8859_15 nls_cp850 smbfs ipv6
> nfsd nfs_acl auth_rpcgss lockd sunrpc capifs r8169 mii usblp isofs
> ide_tape ide_cd_mod cdrom ata_piix libata sd_mod scsi_mod usbhid hid
> xhci ohci_hcd ssb uhci_hcd ehci_hcd usbcore psmouse [last unloaded:
> kernelcapi]
> Jun 11 17:41:42 server kernel: Pid: 0, comm: swapper Tainted: P
> 2.6.32-eisfair-1-SMP #1
> Jun 11 17:41:42 server kernel: Call Trace:
> Jun 11 17:41:42 server kernel:  [warn_slowpath_common+0x60/0x77]
> warn_slowpath_common+0x60/0x77
> Jun 11 17:41:42 server kernel:  [warn_slowpath_fmt+0x24/0x27]
> warn_slowpath_fmt+0x24/0x27
> Jun 11 17:41:42 server kernel:  [dev_watchdog+0xf9/0x177]
> dev_watchdog+0xf9/0x177
> Jun 11 17:41:42 server kernel:  [insert_work+0x43/0x4b] ?
> insert_work+0x43/0x4b
> Jun 11 17:41:42 server kernel:  [__queue_work+0x26/0x2b] ?
> __queue_work+0x26/0x2b
> Jun 11 17:41:42 server kernel:  [delayed_work_timer_fn+0x0/0x24] ?
> delayed_work_timer_fn+0x0/0x24
> Jun 11 17:41:42 server kernel:  [dev_watchdog+0x0/0x177] ?
> dev_watchdog+0x0/0x177
> Jun 11 17:41:42 server kernel:  [run_timer_softirq+0x105/0x158]
> run_timer_softirq+0x105/0x158
> Jun 11 17:41:42 server kernel:  [__do_softirq+0x84/0xfd]
> __do_softirq+0x84/0xfd
> Jun 11 17:41:42 server kernel:  [do_softirq+0x26/0x2b] do_softirq+0x26/0x2b
> Jun 11 17:41:42 server kernel:  [irq_exit+0x29/0x2b] irq_exit+0x29/0x2b
> Jun 11 17:41:42 server kernel:  [smp_apic_timer_interrupt+0x6f/0x7d]
> smp_apic_timer_interrupt+0x6f/0x7d
> Jun 11 17:41:42 server kernel:  [apic_timer_interrupt+0x2a/0x30]
> apic_timer_interrupt+0x2a/0x30
> Jun 11 17:41:42 server kernel:  [mwait_idle+0x4c/0x52] ?
> mwait_idle+0x4c/0x52
> Jun 11 17:41:42 server kernel:  [cpu_idle+0x3a/0x4e] cpu_idle+0x3a/0x4e
> Jun 11 17:41:42 server kernel:  [rest_init+0x5d/0x5f] rest_init+0x5d/0x5f
> Jun 11 17:41:42 server kernel:  [start_kernel+0x28c/0x291]
> start_kernel+0x28c/0x291
> Jun 11 17:41:42 server kernel:  [i386_start_kernel+0x91/0x96]
> i386_start_kernel+0x91/0x96
> Jun 11 17:41:42 server kernel: ---[ end trace 35e6e8fea1aee3fd ]---
> Jun 11 17:41:42 server kernel: r8169: eth0: link up
> Jun 11 17:41:52 server imapd[25493]: Logout user=af host=server.home.lan
> [192.168.1.1]
> Jun 11 17:42:24 server kernel: r8169: eth0: link up
> Jun 11 17:43:06 server kernel: r8169: eth0: link up
> Jun 11 17:44:06 server last message repeated 2 times
> Jun 11 17:45:06 server last message repeated 2 times
> Jun 11 17:46:06 server last message repeated 2 times
> Jun 11 17:47:06 server last message repeated 2 times
> Jun 11 17:48:06 server last message repeated 2 times
> Jun 11 17:48:54 server kernel: r8169: eth0: link up
> Jun 11 17:50:12 server kernel: r8169: eth0: link up
> Jun 11 17:51:18 server kernel: r8169: eth0: link up
> Jun 11 17:52:36 server kernel: r8169: eth0: link up