* Dmitry Fleytman (dmi...@daynix.com) wrote:
> Hello Dave,
>
> It looks like we identified the problem.
>
> We are working on fix and will send it as soon as it is ready.
Thanks!
Dave
> ~Dmitry.
>
> Sent from my iPhone
>
> > On 15 May 2017, at 12:22, Dr. David Alan Gilbert
> > wrote:
> >
Hello Dave,
It looks like we identified the problem.
We are working on fix and will send it as soon as it is ready.
~Dmitry.
Sent from my iPhone
> On 15 May 2017, at 12:22, Dr. David Alan Gilbert wrote:
>
> * Dmitry Fleytman (dmi...@daynix.com) wrote:
>> Hello Dave,
>
> Hi Dmitry,
> Thanks
* Dmitry Fleytman (dmi...@daynix.com) wrote:
> Hello Dave,
Hi Dmitry,
Thanks for the reply.
> We are trying to reproduce this issue on our systems but with no luck so far…
Note our QE hit this with both a Win8.1 and a win2012r2 guest - although
the 2012r2 is reported to have recoverd after a f
Hello Dave,
We are trying to reproduce this issue on our systems but with no luck so far…
From what you describe it looks like some bit in ICR is not being cleared by
the driver.
This usually means that this bit should never be set in that specific interrupt
mode.
Could you please check which
Hi Dmitry,
Have you seen any problems with e1000e migration under windows?
I've got a repeatable case where after migration with e1000e windows
hangs/almost hangs.
I'm seeing the e1000e generate interrupts at a very very high
rate (maybe ~1000 second ish?) after migration.
Some versions of q
