Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 32 replies
  • Subscribers 2 subscribers
  • Views 10625 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

UTM 9.204 Intel E1000e NIC crash

ECKEROTH
Just upgraded to 9.204 and I still have Intel E1000e NIC crashs. PLEAZE SOPHOS - fix this now asap...

After manuel set "ethtool -K eth1 gso off gro off" normal operation can be obtained, but this it gone when rebooting [:@] 

2014:07:11-20:28:20 fw kernel: [ 6621.930212] next_to_watch 

2014:07:11-20:28:20 fw kernel: [ 6621.930212] jiffies 

2014:07:11-20:28:20 fw kernel: [ 6621.930212] next_to_watch.status 

2014:07:11-20:28:20 fw kernel: [ 6621.930212] MAC Status 

2014:07:11-20:28:20 fw kernel: [ 6621.930212] PHY Status 

2014:07:11-20:28:20 fw kernel: [ 6621.930212] PHY 1000BASE-T Status 

2014:07:11-20:28:20 fw kernel: [ 6621.930212] PHY Extended Status 

2014:07:11-20:28:20 fw kernel: [ 6621.930212] PCI Status 

2014:07:11-20:28:20 fw kernel: [ 6621.937388] e1000e 0000:00:19.0 eth1: Reset adapter unexpectedly

2014:07:11-20:28:23 fw kernel: [ 6625.762700] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

2014:07:11-20:32:06 fw kernel: [ 6847.695940] e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:

2014:07:11-20:32:06 fw kernel: [ 6847.695940] TDH 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] TDT 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] next_to_use 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] next_to_clean 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] buffer_info[next_to_clean]:

2014:07:11-20:32:06 fw kernel: [ 6847.695940] time_stamp 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] next_to_watch 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] jiffies 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] next_to_watch.status 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] MAC Status 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] PHY Status 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] PHY 1000BASE-T Status 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] PHY Extended Status 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] PCI Status 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:

2014:07:11-20:32:08 fw kernel: [ 6849.693885] TDH 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] TDT 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] next_to_use 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] next_to_clean 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] buffer_info[next_to_clean]:

2014:07:11-20:32:08 fw kernel: [ 6849.693885] time_stamp 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] next_to_watch 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] jiffies 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] next_to_watch.status 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] MAC Status 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] PHY Status 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] PHY 1000BASE-T Status 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] PHY Extended Status 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] PCI Status 

2014:07:11-20:32:09 fw kernel: [ 6850.691975] e1000e 0000:00:19.0 eth1: Reset adapter unexpectedly

2014:07:11-20:32:12 fw kernel: [ 6854.449265] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

2014:07:11-20:33:27 fw kernel: [ 6928.600113] e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:

2014:07:11-20:33:27 fw kernel: [ 6928.600113] TDH 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] TDT 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] next_to_use 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] next_to_clean 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] buffer_info[next_to_clean]:

2014:07:11-20:33:27 fw kernel: [ 6928.600113] time_stamp 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] next_to_watch 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] jiffies 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] next_to_watch.status 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] MAC Status 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] PHY Status 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] PHY 1000BASE-T Status 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] PHY Extended Status 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] PCI Status 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:

2014:07:11-20:33:29 fw kernel: [ 6930.598052] TDH 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] TDT 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] next_to_use 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] next_to_clean 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] buffer_info[next_to_clean]:

2014:07:11-20:33:29 fw kernel: [ 6930.598052] time_stamp 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] next_to_watch 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] jiffies 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] next_to_watch.status 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] MAC Status 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] PHY Status 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] PHY 1000BASE-T Status 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] PHY Extended Status 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] PCI Status 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:

2014:07:11-20:33:31 fw kernel: [ 6932.595992] TDH 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] TDT 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] next_to_use 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] next_to_clean 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] buffer_info[next_to_clean]:

2014:07:11-20:33:31 fw kernel: [ 6932.595992] time_stamp 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] next_to_watch 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] jiffies 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] next_to_watch.status 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] MAC Status 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] PHY Status 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] PHY 1000BASE-T Status 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] PHY Extended Status 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] PCI Status 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:

2014:07:11-20:33:33 fw kernel: [ 6934.593959] TDH 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] TDT 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] next_to_use 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] next_to_clean 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] buffer_info[next_to_clean]:

2014:07:11-20:33:33 fw kernel: [ 6934.593959] time_stamp 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] next_to_watch 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] jiffies 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] next_to_watch.status 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] MAC Status 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] PHY Status 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] PHY 1000BASE-T Status 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] PHY Extended Status 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] PCI Status 

2014:07:11-20:33:33 fw kernel: [ 6934.604903] e1000e 0000:00:19.0 eth1: Reset adapter unexpectedly

2014:07:11-20:33:36 fw kernel: [ 6938.414254] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx


This thread was automatically locked due to age.
Parents
  • 0
    Wondering why this hasn't been fixed.
  • 0 in reply to Jhaislet
    Think about this, is it a core sophos issue, no, does it affect sophos hardware no.
    What does it affect people, using UTM in a vmware that is what e1000 is?
    I haven't seen this issues on any of my hardware devices for awhile. I have 3 running different version of intel NICs.

    This might seem like a silly question, but why would you run a security device in a VM other than a test setup, why expose another layer of network software to the internet for attack? In VMwares case that would make two firewalls in series. Hyper-V, I prefer not to discuss that setups weaknesses.

    Please update my thinking.

    Ian
  • 0 in reply to RFCat_vk_01
    Think about this, is it a core sophos issue, no, does it affect sophos hardware no.
    What does it affect people, using UTM in a vmware that is what e1000 is?
    I haven't seen this issues on any of my hardware devices for awhile. I have 3 running different version of intel NICs.

    This might seem like a silly question, but why would you run a security device in a VM other than a test setup, why expose another layer of network software to the internet for attack? In VMwares case that would make two firewalls in series. Hyper-V, I prefer not to discuss that setups weaknesses.

    Please update my thinking.

    Ian


    Ian

    We are not on VMware! Intel 82579 Is the E1000 chipset on my fysical server.

    // Martin

    Sent from my iPad using Astaro.org
Reply
  • 0 in reply to RFCat_vk_01
    Think about this, is it a core sophos issue, no, does it affect sophos hardware no.
    What does it affect people, using UTM in a vmware that is what e1000 is?
    I haven't seen this issues on any of my hardware devices for awhile. I have 3 running different version of intel NICs.

    This might seem like a silly question, but why would you run a security device in a VM other than a test setup, why expose another layer of network software to the internet for attack? In VMwares case that would make two firewalls in series. Hyper-V, I prefer not to discuss that setups weaknesses.

    Please update my thinking.

    Ian


    Ian

    We are not on VMware! Intel 82579 Is the E1000 chipset on my fysical server.

    // Martin

    Sent from my iPad using Astaro.org
Children
No Data