Am 2014-02-02 23:08, schrieb Günther Zisham:
Vielen Dank!! Hab ein gutes Gefühl mit dem neuen Treiber, könnte funktionieren.
Hallo! Hab den neuen Treiber einspielen können: # ethtool -i eth1 driver: e1000e version: 2.5.4-NAPI firmware-version: 1.0-0 bus-info: 0000:04:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no Leider tritt der Fehler unter Netzwerk-Last noch immer auf: Feb 4 23:36:19 s1 kernel: [2985571.964754] e1000e 0000:04:00.1 eth1: Detected Hardware Unit Hang: Feb 4 23:36:19 s1 kernel: [2985571.964754] TDH <2f> Feb 4 23:36:19 s1 kernel: [2985571.964754] TDT <5a> Feb 4 23:36:19 s1 kernel: [2985571.964754] next_to_use <5a> Feb 4 23:36:19 s1 kernel: [2985571.964754] next_to_clean <2d> Feb 4 23:36:19 s1 kernel: [2985571.964754] buffer_info[next_to_clean]: Feb 4 23:36:19 s1 kernel: [2985571.964754] time_stamp <2c7be49d> Feb 4 23:36:19 s1 kernel: [2985571.964754] next_to_watch <2f> Feb 4 23:36:19 s1 kernel: [2985571.964754] jiffies <2c7be8a8> Feb 4 23:36:19 s1 kernel: [2985571.964754] next_to_watch.status <0> Feb 4 23:36:19 s1 kernel: [2985571.964754] MAC Status <2080787> Feb 4 23:36:19 s1 kernel: [2985571.964754] PHY Status <792d> Feb 4 23:36:19 s1 kernel: [2985571.964754] PHY 1000BASE-T Status <3800> Feb 4 23:36:19 s1 kernel: [2985571.964754] PHY Extended Status <3000> Feb 4 23:36:19 s1 kernel: [2985571.964754] PCI Status <10> Feb 4 23:36:23 s1 kernel: [2985575.964694] e1000e 0000:04:00.1 eth1: Detected Hardware Unit Hang: Feb 4 23:36:23 s1 kernel: [2985575.964694] TDH <2f> Feb 4 23:36:23 s1 kernel: [2985575.964694] TDT <5a> Feb 4 23:36:23 s1 kernel: [2985575.964694] next_to_use <5a> Feb 4 23:36:23 s1 kernel: [2985575.964694] next_to_clean <2d> Feb 4 23:36:23 s1 kernel: [2985575.964694] buffer_info[next_to_clean]: Feb 4 23:36:23 s1 kernel: [2985575.964694] time_stamp <2c7be49d> Feb 4 23:36:23 s1 kernel: [2985575.964694] next_to_watch <2f> Feb 4 23:36:23 s1 kernel: [2985575.964694] jiffies <2c7bec90> Feb 4 23:36:23 s1 kernel: [2985575.964694] next_to_watch.status <0> Feb 4 23:36:23 s1 kernel: [2985575.964694] MAC Status <2080787> Feb 4 23:36:23 s1 kernel: [2985575.964694] PHY Status <792d> Feb 4 23:36:23 s1 kernel: [2985575.964694] PHY 1000BASE-T Status <3800> Feb 4 23:36:23 s1 kernel: [2985575.964694] PHY Extended Status <3000> Feb 4 23:36:23 s1 kernel: [2985575.964694] PCI Status <10> Feb 4 23:36:27 s1 kernel: [2985580.171413] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 4 23:58:25 s1 kernel: [2986898.000712] e1000e 0000:04:00.1 eth1: Detected Hardware Unit Hang: Feb 4 23:58:25 s1 kernel: [2986898.000712] TDH <fe> Feb 4 23:58:25 s1 kernel: [2986898.000712] TDT <12> Feb 4 23:58:25 s1 kernel: [2986898.000712] next_to_use <12> Feb 4 23:58:25 s1 kernel: [2986898.000712] next_to_clean <fa> Feb 4 23:58:25 s1 kernel: [2986898.000712] buffer_info[next_to_clean]: Feb 4 23:58:25 s1 kernel: [2986898.000712] time_stamp <2c80f23b> Feb 4 23:58:25 s1 kernel: [2986898.000712] next_to_watch <fe> Feb 4 23:58:25 s1 kernel: [2986898.000712] jiffies <2c80f79d> Feb 4 23:58:25 s1 kernel: [2986898.000712] next_to_watch.status <0> Feb 4 23:58:25 s1 kernel: [2986898.000712] MAC Status <2080787> Feb 4 23:58:25 s1 kernel: [2986898.000712] PHY Status <792d> Feb 4 23:58:25 s1 kernel: [2986898.000712] PHY 1000BASE-T Status <7800> Feb 4 23:58:25 s1 kernel: [2986898.000712] PHY Extended Status <3000> Feb 4 23:58:25 s1 kernel: [2986898.000712] PCI Status <10> Feb 4 23:58:27 s1 kernel: [2986900.012061] e1000e 0000:04:00.1 eth1: Reset adapter unexpectedly Feb 4 23:58:30 s1 kernel: [2986902.783430] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Desto mehr Netzwerklast, desto mehr Fehler dieser Art. Noch andere Ideen? Gruß Günther -- Um die Liste abzubestellen, schicken Sie eine Mail an: opensuse-de+unsubscribe@opensuse.org Um den Listen Administrator zu erreichen, schicken Sie eine Mail an: opensuse-de+owner@opensuse.org