Summary: | e1000e Network card hang driver issue | ||
---|---|---|---|
Product: | IPFire | Reporter: | Stefan <stefan.schembera87> |
Component: | --- | Assignee: | Arne.F <arne.fitzenreiter> |
Status: | NEW --- | QA Contact: | |
Severity: | Crash | ||
Priority: | - Unknown - | CC: | christian.keck, jonatan.schlag, mw+ipfire |
Version: | 2 | ||
Hardware: | x86_64 | ||
OS: | Linux |
Description
Stefan
2021-10-08 23:53:27 UTC
This is quite a popular NIC which is running fine for probably most people. Could you try a firmware update of the board? What is the rest of the hardware? (In reply to Michael Tremer from comment #1) > This is quite a popular NIC which is running fine for probably most people. > > Could you try a firmware update of the board? What is the rest of the > hardware? first of all i will do a bios update then I keep looking I help myself to enter it befhelms each new star so that the map runs until the next restart without any problems if the error is not resolved, I will buy a new network card 4x 10gbits intel this is my hardware https://www.supermicro.com/products/motherboard/Xeon/C202_C204/X9SCL.cfm https://fireinfo.ipfire.org/profile/17d94e763f9ebbd470a3e57866faffd5b7caf12f (In reply to Michael Tremer from comment #1) > This is quite a popular NIC which is running fine for probably most people. > > Could you try a firmware update of the board? What is the rest of the > hardware? This is old as sin for the e1000 and later e1000e. Check my comments and links in the thread, especially this: https://community.ipfire.org/t/e1000e-green0-detected-hardware-unit-hang/6324/18?u=mangrove Just google for the message and you will get hundreds of reports of this error from other projects. I was also suffering from this (in ipfire) a couple of years ago and then I came to the conclusion that it's probably physical chip revision related or something like that, so all instances aren't suffering (I run lots of virtualized e1000 machines and not a single one has had this bug). My solution was to swap my NICs in the affected physical machine (a Dell Optiplex). But it's a (driver|hardware|firmware) bug and a really old one at that. Could be related to the IOMMU-problems like in Bug #12943. |