On Mon 02 Dec 2013 "Ertman, DavidX M" wrote:
> I see what is going on here, we put a conditional check on the duration of
> the sleep range to use the correct delay function, but it only went on in one
> of the sleeps.
> I will submit a patch for this.
Thanks. I see that someone else found a s
Bjorn,
Seems not the same bug as http://sourceforge.net/p/e1000/bugs/367/
, Nick is not running his kernel on bare metal, per the error log,
he runs his kernel as HVM DomU guest or Dom0 on XEN ? so just a check
of NULL will not fix that.
Thanks,
Ethan
On Thu, Nov 21, 2013 at 5:22 AM, Bjorn
I'm having difficulty following this issue, most likely because of our email
system. Can you file a new bug on sourceforge?
Thanks.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Nic
> Intel maintains newer drivers out-of-tree at
> http://sourceforge.net/projects/e1000/, and it's possible this is some
> bug that has already been fixed. The current version there looks like
> e1000e-2.5.4, released 2013-09-05.
>
> Possible similar report: http://sourceforge.net/p/e1000/bugs/367/
I see what is going on here, we put a conditional check on the duration of the
sleep range to use the correct delay function, but it only went on in one of
the sleeps.
I will submit a patch for this.
Could you please submit your kernel configuration so that I can enable the same
debugging that
