There's really not enough information here. Ideally you would send us the dmesg
of when it fails, and a register dump before and after.
I would suggest opening on bug on sourceforge and attaching the dmesg &
register dumps to the bug. Don't just copy them into the bug because that's
much
On 2018-01-24 20:31, Ben Greear wrote:
On 01/24/2018 08:34 AM, Neftin, Sasha wrote:
On 1/24/2018 18:11, Alexander Duyck wrote:
On Tue, Jan 23, 2018 at 3:46 PM, Ben Greear
wrote:
Hello,
Anyone have any more suggestions for making e1000e work better?
This is
from a
On 01/24/2018 08:34 AM, Neftin, Sasha wrote:
On 1/24/2018 18:11, Alexander Duyck wrote:
On Tue, Jan 23, 2018 at 3:46 PM, Ben Greear wrote:
Hello,
Anyone have any more suggestions for making e1000e work better? This is
from a 4.9.65+ kernel,
with these additional
On 01/24/2018 10:38 AM, Denys Fedoryshchenko wrote:
On 2018-01-24 20:31, Ben Greear wrote:
On 01/24/2018 08:34 AM, Neftin, Sasha wrote:
On 1/24/2018 18:11, Alexander Duyck wrote:
On Tue, Jan 23, 2018 at 3:46 PM, Ben Greear wrote:
Hello,
Anyone have any more
On 1/24/2018 18:11, Alexander Duyck wrote:
On Tue, Jan 23, 2018 at 3:46 PM, Ben Greear wrote:
Hello,
Anyone have any more suggestions for making e1000e work better? This is
from a 4.9.65+ kernel,
with these additional e1000e patches applied:
e1000e: Fix error path
On Tue, Jan 23, 2018 at 3:46 PM, Ben Greear wrote:
> Hello,
>
> Anyone have any more suggestions for making e1000e work better? This is
> from a 4.9.65+ kernel,
> with these additional e1000e patches applied:
>
> e1000e: Fix error path in link detection
> e1000e: Fix
Dear maintainers,
We have a xen virtualization environment, with 6 nearly identical nodes,
Supermicro X8DTU boards.
We run debian stretch on them, the xen hypervisor and linux kernel is from
debian stretch, latest at the time of writing.
Unfortunately, we are facing an issue where randomly