Nie jesteś zalogowany.
Jeśli nie posiadasz konta, zarejestruj je już teraz! Pozwoli Ci ono w pełni korzystać z naszego serwisu. Spamerom dziękujemy!
Ogłoszenie
Prosimy o pomoc dla małej Julki — przekaż 1% podatku na Fundacji Dzieciom zdazyć z Pomocą.
Więcej informacji na dug.net.pl/pomagamy/.
#1 2018-02-02 15:24:13
tomtomdwa - 
Użytkownik
- tomtomdwa
- Użytkownik
- Zarejestrowany: 2013-03-18
Połączenie zerwane
Mój mini serwer działa poprawnie kilka dni po czym dostaję poniższy komunikat. Sieci brak, ktoś na miejscu restartuje i jest przez jakiś czas ok. Karta sieciowa do sprawdzenia?
Kod:
Feb 2 13:10:55 NAS kernel: [269366.507781] e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang: Feb 2 13:10:55 NAS kernel: [269366.507781] TDH <af> Feb 2 13:10:55 NAS kernel: [269366.507781] TDT <cd> Feb 2 13:10:55 NAS kernel: [269366.507781] next_to_use <cd> Feb 2 13:10:55 NAS kernel: [269366.507781] next_to_clean <ad> Feb 2 13:10:55 NAS kernel: [269366.507781] buffer_info[next_to_clean]: Feb 2 13:10:55 NAS kernel: [269366.507781] time_stamp <10402687e> Feb 2 13:10:55 NAS kernel: [269366.507781] next_to_watch <af> Feb 2 13:10:55 NAS kernel: [269366.507781] jiffies <104026988> Feb 2 13:10:55 NAS kernel: [269366.507781] next_to_watch.status <0> Feb 2 13:10:55 NAS kernel: [269366.507781] MAC Status <40080083> Feb 2 13:10:55 NAS kernel: [269366.507781] PHY Status <796d> Feb 2 13:10:55 NAS kernel: [269366.507781] PHY 1000BASE-T Status <3800> Feb 2 13:10:55 NAS kernel: [269366.507781] PHY Extended Status <3000> Feb 2 13:10:55 NAS kernel: [269366.507781] PCI Status <10> Feb 2 13:10:57 NAS kernel: [269368.523899] e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang: Feb 2 13:10:57 NAS kernel: [269368.523899] TDH <af> Feb 2 13:10:57 NAS kernel: [269368.523899] TDT <cd> Feb 2 13:10:57 NAS kernel: [269368.523899] next_to_use <cd> Feb 2 13:10:57 NAS kernel: [269368.523899] next_to_clean <ad> Feb 2 13:10:57 NAS kernel: [269368.523899] buffer_info[next_to_clean]: Feb 2 13:10:57 NAS kernel: [269368.523899] time_stamp <10402687e> Feb 2 13:10:57 NAS kernel: [269368.523899] next_to_watch <af> Feb 2 13:10:57 NAS kernel: [269368.523899] jiffies <104026b80> Feb 2 13:10:57 NAS kernel: [269368.523899] next_to_watch.status <0> Feb 2 13:10:57 NAS kernel: [269368.523899] MAC Status <40080083> Feb 2 13:10:57 NAS kernel: [269368.523899] PHY Status <796d> Feb 2 13:10:57 NAS kernel: [269368.523899] PHY 1000BASE-T Status <3800> Feb 2 13:10:57 NAS kernel: [269368.523899] PHY Extended Status <3000> Feb 2 13:10:57 NAS kernel: [269368.523899] PCI Status <10>
Kod:
Feb 2 13:11:00 NAS kernel: [269371.595330] ------------[ cut here ]------------ Feb 2 13:11:00 NAS kernel: [269371.595354] WARNING: CPU: 1 PID: 0 at /build/linux-EAZfyE/linux-4.9.51/net/sched/sch_generic.c:316 dev_watchdog+0x22d/0x230 Feb 2 13:11:00 NAS kernel: [269371.595358] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out Feb 2 13:11:00 NAS kernel: [269371.595361] Modules linked in: veth ebtable_filter ebtables ip6table_filter ip6_tables xt_nat xt_CHECKSUM xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_mangle iptable_nat nf_conntr ack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter cfg80211 bridge stp llc tun fuse intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clm ulni_intel evdev intel_cstate intel_uncore hci_uart sg btbcm btqca intel_rapl_perf iTCO_wdt i915 pcspkr iTCO_vendor_support serio_raw btintel battery bluetooth rfkill video drm_kms_helper intel_lpss_acpi intel_lpss mfd_core a cpi_pad button drm mei_me mei shpchp i2c_algo_bit acpi_als kfifo_buf industrialio ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto ecb mbcache raid10 raid456 async_raid6_recov Feb 2 13:11:00 NAS kernel: [269371.595447] async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid0 multipath linear dm_mod raid1 md_mod sd_mod crc32c_intel aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse e1000e ptp i2c_i801 pps_core i2c_smbus ahci libahci libata scsi_mod xhci_pci xhci_hcd usbcore usb_common r8169 mii i2c_hid hid Feb 2 13:11:00 NAS kernel: [269371.595493] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.9.0-4-amd64 #1 Debian 4.9.51-1 Feb 2 13:11:00 NAS kernel: [269371.595495] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H110M-ITX, BIOS P7.00 10/27/2016 Feb 2 13:11:00 NAS kernel: [269371.595498] 0000000000000000 ffffffffaf929974 ffff975b6ed03e20 0000000000000000 Feb 2 13:11:00 NAS kernel: [269371.595504] ffffffffaf676eae 0000000000000000 ffff975b6ed03e78 ffff975b68884000 Feb 2 13:11:00 NAS kernel: [269371.595510] 0000000000000001 ffff975b64de1080 0000000000000001 ffffffffaf676f2f Feb 2 13:11:00 NAS kernel: [269371.595515] Call Trace: Feb 2 13:11:00 NAS kernel: [269371.595518] <IRQ> Feb 2 13:11:00 NAS kernel: [269371.595525] [<ffffffffaf929974>] ? dump_stack+0x5c/0x78 Feb 2 13:11:00 NAS kernel: [269371.595532] [<ffffffffaf676eae>] ? __warn+0xbe/0xe0 Feb 2 13:11:00 NAS kernel: [269371.595537] [<ffffffffaf676f2f>] ? warn_slowpath_fmt+0x5f/0x80 Feb 2 13:11:00 NAS kernel: [269371.595544] [<ffffffffaf6aed52>] ? enqueue_task_fair+0x82/0x940 Feb 2 13:11:00 NAS kernel: [269371.595552] [<ffffffffafb2cb2d>] ? dev_watchdog+0x22d/0x230 Feb 2 13:11:00 NAS kernel: [269371.595556] [<ffffffffafb2c900>] ? qdisc_rcu_free+0x40/0x40 Feb 2 13:11:00 NAS kernel: [269371.595562] [<ffffffffaf6e4020>] ? call_timer_fn+0x30/0x110 Feb 2 13:11:00 NAS kernel: [269371.595568] [<ffffffffaf6e4524>] ? run_timer_softirq+0x1d4/0x430 Feb 2 13:11:00 NAS kernel: [269371.595573] [<ffffffffaf6f4cd0>] ? tick_sched_handle.isra.12+0x50/0x50 Feb 2 13:11:00 NAS kernel: [269371.595576] [<ffffffffaf6f4ca0>] ? tick_sched_handle.isra.12+0x20/0x50 Feb 2 13:11:00 NAS kernel: [269371.595580] [<ffffffffaf6f4d08>] ? tick_sched_timer+0x38/0x70 Feb 2 13:11:00 NAS kernel: [269371.595586] [<ffffffffafc0b0d5>] ? __do_softirq+0x105/0x290 Feb 2 13:11:00 NAS kernel: [269371.595590] [<ffffffffaf67cf8e>] ? irq_exit+0xae/0xb0 Feb 2 13:11:00 NAS kernel: [269371.595594] [<ffffffffafc0aeee>] ? smp_apic_timer_interrupt+0x3e/0x50 Feb 2 13:11:00 NAS kernel: [269371.595598] [<ffffffffafc0a202>] ? apic_timer_interrupt+0x82/0x90 Feb 2 13:11:00 NAS kernel: [269371.595599] <EOI> Feb 2 13:11:00 NAS kernel: [269371.595607] [<ffffffffafacd31a>] ? cpuidle_enter_state+0x11a/0x2b0 Feb 2 13:11:00 NAS kernel: [269371.595612] [<ffffffffafacd307>] ? cpuidle_enter_state+0x107/0x2b0 Feb 2 13:11:00 NAS kernel: [269371.595618] [<ffffffffaf6b9634>] ? cpu_startup_entry+0x154/0x240 Feb 2 13:11:00 NAS kernel: [269371.595624] [<ffffffffaf6480dd>] ? start_secondary+0x14d/0x190 Feb 2 13:11:00 NAS kernel: [269371.595629] ---[ end trace 7b3a3433a686e4cb ]--- Feb 2 13:11:04 NAS kernel: [269375.581573] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 2 13:11:18 NAS kernel: [269389.677511] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 2 13:11:32 NAS kernel: [269403.685420] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 2 13:11:46 NAS kernel: [269417.525389] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 2 13:12:00 NAS kernel: [269431.661326] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 2 13:12:14 NAS kernel: [269445.737262] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 2 13:12:28 NAS kernel: [269459.553201] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 2 13:12:42 NAS kernel: [269473.649137] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 2 13:12:56 NAS kernel: [269487.657070] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 2 13:13:10 NAS kernel: [269501.497008] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 2 13:13:25 NAS kernel: [269516.596939] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 2 13:13:39 NAS kernel: [269530.732879] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 2 13:13:53 NAS kernel: [269544.552813] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 2 13:37:32 NAS kernel: [ 0.000000] Linux version 4.9.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.51-1 (2017-09-28) Feb 2 13:37:32 NAS kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-4-amd64 root=UUID=73f3e636-eaeb-4e2a-b431-220d084925ee ro quiet Feb 2 13:37:32 NAS kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Feb 2 13:37:32 NAS kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Feb 2 13:37:32 NAS kernel: [ 0.000000] x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'compacted' format. Feb 2 13:37:32 NAS kernel: [ 0.000000] x86/fpu: Using 'eager' FPU context switches. Feb 2 13:37:32 NAS kernel: [ 0.000000] e820: BIOS-provided physical RAM map: Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009c7ff] usable Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x000000000009c800-0x000000000009ffff] reserved Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007f3d7fff] usable Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x000000007f3d8000-0x000000007f3d8fff] ACPI NVS Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x000000007f3d9000-0x000000007f3f2fff] reserved Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x000000007f3f3000-0x000000007f443fff] usable Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x000000007f444000-0x000000007f9c0fff] reserved Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x000000007f9c1000-0x000000008c25bfff] usable Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x000000008c25c000-0x000000008cbb4fff] reserved Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x000000008cbb5000-0x000000008d399fff] ACPI NVS Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x000000008d39a000-0x000000008d3fefff] ACPI data Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x000000008d3ff000-0x000000008d3fffff] usable Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved Feb 2 13:37:32 NAS kernel: [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000016effffff] usable Feb 2 13:37:32 NAS kernel: [ 0.000000] NX (Execute Disable) protection: active Feb 2 13:37:32 NAS kernel: [ 0.000000] SMBIOS 2.8 present.
Kod:
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31) 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
Offline
#2 2018-02-02 23:30:32
lis6502 - Łowca lamerów
- lis6502
- Łowca lamerów
- Skąd: Stalinogród
- Zarejestrowany: 2008-12-04
Re: Połączenie zerwane
Proponowałbym ustalić czy problem nie zachodzi przypadkiem po przekroczeniu określonej ilości pakietów, lub czy nie ma innego czynnika umożliwającego "zwiechę", bo tak to będziemy bawić się w debugowanie do usranej śmierci.
Spotkałem się kieydś z czymś podobnym na zintegrowanej karcie w jakiejś płycie na nForce, ale tam sam sterownik wrzucał do dmesg że może być "buggy".
Najlepiej podnieś wersję kernela i przyczaj, a najlepiej zmień WAN na tego realteka, bo lepiej chyba dostać info że nie działa i mieć się jak zalogować :)
Offline