Thanks to everyone for the testing. The patch is now committed.
Correct.
On Wed, Aug 05, 2015 at 01:08:19PM +0100, Stuart Henderson wrote:
> On 2015/08/05 10:08, Mark Patruck wrote:
> > But i still have a small problem with
> >
> > em0 at pci0 dev 25 function 0 "Intel I218-V" rev 0x00: msi, address f0:..
>
> Thanks for testing.
>
> "Still" -> just to check
On 2015/08/05 10:08, Mark Patruck wrote:
> But i still have a small problem with
>
> em0 at pci0 dev 25 function 0 "Intel I218-V" rev 0x00: msi, address f0:..
Thanks for testing.
"Still" -> just to check I understand correctly, this diff doesn't help
with your nic, but doesn't make things worse?
The em0 is the only ethernet nic on the laptop, this is on a Thinkpad
x250 laptop.
On 2015 Aug 05 (Wed) at 13:23:13 +0200 (+0200), Mark Patruck wrote:
:Hmm..weird. Is the I218-LM the only nic in your system? Because if
:i add an additional PCIe Intel 85247L, my onboard I218-V comes up
:with 1000b
Hmm..weird. Is the I218-LM the only nic in your system? Because if
i add an additional PCIe Intel 85247L, my onboard I218-V comes up
with 1000baseT as well.
em0 at pci1 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address 00:..
em1 at pci0 dev 25 function 0 "Intel I218-V" rev 0x00: msi, address
On 2015 Aug 05 (Wed) at 10:08:05 +0200 (+0200), Mark Patruck wrote:
:No issues on systems running
:
:em0 at pci3 dev 0 function 0 "Intel I210" rev 0x03: msi, address 0c:..
:em1 at pci4 dev 0 function 0 "Intel I210" rev 0x03: msi, address 0c:..
:
:Also working on
:
:em0 at pci1 dev 0 function 0 "In
No issues on systems running
em0 at pci3 dev 0 function 0 "Intel I210" rev 0x03: msi, address 0c:..
em1 at pci4 dev 0 function 0 "Intel I210" rev 0x03: msi, address 0c:..
Also working on
em0 at pci1 dev 0 function 0 "Intel 82576" rev 0x01: msi, address 90:..
em1 at pci1 dev 0 function 1 "Intel
On Tue, Aug 04, 2015 at 07:16:48PM -0600, Theo de Raadt wrote:
> > On Wed, Aug 05, 2015 at 02:04:28AM +0200, Hrvoje Popovski wrote:
> > > On 4.8.2015. 23:47, Stuart Henderson wrote:
> > > > On 2015/08/04 22:40, Stefan Fritsch wrote:
> > > >> someone mentioned to me the i217-LM problems that were re
> On Wed, Aug 05, 2015 at 02:04:28AM +0200, Hrvoje Popovski wrote:
> > On 4.8.2015. 23:47, Stuart Henderson wrote:
> > > On 2015/08/04 22:40, Stefan Fritsch wrote:
> > >> someone mentioned to me the i217-LM problems that were reported on misc
> > >> end of May. It is possible that the patch below
On Wed, Aug 05, 2015 at 02:04:28AM +0200, Hrvoje Popovski wrote:
> On 4.8.2015. 23:47, Stuart Henderson wrote:
> > On 2015/08/04 22:40, Stefan Fritsch wrote:
> >> someone mentioned to me the i217-LM problems that were reported on misc
> >> end of May. It is possible that the patch below helps.
> >
On 4.8.2015. 23:47, Stuart Henderson wrote:
> On 2015/08/04 22:40, Stefan Fritsch wrote:
>> someone mentioned to me the i217-LM problems that were reported on misc
>> end of May. It is possible that the patch below helps.
>
> This fixes my Dell poweredge T20:
> em0 at pci0 dev 25 function 0 "Inte
> On 2015/08/04 22:40, Stefan Fritsch wrote:
> > someone mentioned to me the i217-LM problems that were reported on misc
> > end of May. It is possible that the patch below helps.
>
> This fixes my Dell poweredge T20:
> em0 at pci0 dev 25 function 0 "Intel I217-LM" rev 0x04: msi, address
> f8:b1
On 2015/08/04 22:40, Stefan Fritsch wrote:
> someone mentioned to me the i217-LM problems that were reported on misc
> end of May. It is possible that the patch below helps.
This fixes my Dell poweredge T20:
em0 at pci0 dev 25 function 0 "Intel I217-LM" rev 0x04: msi, address
f8:b1:56:...
And d
Hi,
someone mentioned to me the i217-LM problems that were reported on misc
end of May. It is possible that the patch below helps.
For us, it fixed a problem on a laptop with i217-LM (pci id 8086:153a)
where the receiving of packets would stop until the battery of the laptop
was removed (or un
14 matches
Mail list logo
