Processed: Re: Bug#885348: linux-image-4.14.0-2-amd64: aLatest kernel (linux-image-4.14.0-2-amd64) breaks e1000e driver on Intel 82579V Gigabit adapter

2017-12-30 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + pending confirmed
Bug #885348 [src:linux] Latest kernel (linux-image-4.14.0-2-amd64) breaks 
e1000e driver on Intel 82579V Gigabit adapter
Added tag(s) pending and confirmed.

-- 
885348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#885348: linux-image-4.14.0-2-amd64: aLatest kernel (linux-image-4.14.0-2-amd64) breaks e1000e driver on Intel 82579V Gigabit adapter

2017-12-30 Thread Salvatore Bonaccorso
Control: tags -1 + pending confirmed

Hi Timo,

On Wed, Dec 27, 2017 at 03:07:36AM +0100, Timo van Roermund wrote:
> Hi Salvatore,
> 
> 
> On 26-12-2017 16:37, Salvatore Bonaccorso wrote:
> > Hi Timo,
> > 
> > On Tue, Dec 26, 2017 at 03:38:24PM +0100, T.A. van Roermund wrote:
> > > Package: src:linux
> > > Version: 4.14.7-1
> > > Severity: critical
> > > Tags: patch upstream
> > > Justification: breaks the whole system
> > > 
> > > Dear Maintainer,
> > > 
> > > This morning, I updated the Linux kernel from linux-image-4.13.0-1-amd64 
> > > to linux-image-4.14.0-2-amd64.
> > > Afterwards, my Intel Gigabit adapter (details below) did not work 
> > > properly anymore (no link).
> > > When booting back into the previous kernel (4.13), everything works 
> > > properly again.
> > > 
> > > It seems like others experience the same behavior, see:
> > > https://bugzilla.kernel.org/show_bug.cgi?id=198047
> > > 
> > > According to that thread, this bug was introduced in v4.14.3 through 
> > > commit 830466993daf09adbd179e4c74db07279a088f8c
> > > ("e1000e: Separate signaling for link check/link up", upstream: 
> > > 19110cfbb34d4af0cdfe14cd243f3b09dc95b013).
> > > 
> > > The thread also includes a patch that (apparently) fixes the problem:
> > > https://bugzilla.kernel.org/attachment.cgi?id=261183=diff==1=raw
> > > 
> > > Could you please apply this patch to the Debian kernel, until it is 
> > > included in upstream?
> > Sorry to hear that. Would it be possible for you to confirm that the
> > patch fixes your issue, following:
> > 
> > https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2
> > 
> > Regards,
> > Salvatore
> 
> I followed these instructions to build a patched kernel:
> Linux 4.14.0-2-amd64 #1 SMP Debian 4.14.7-1a~test (2017-12-27) x86_64
> GNU/Linux
> 
> With this kernel, the link of my Intel Gigabit adapter comes up again and
> works normally.
> 
> So yes, I can hereby confirm that the patch fixes my issue.

FTR, and sorry for the delay: The change is pending por the next
upload.

https://anonscm.debian.org/cgit/kernel/linux.git/commit/?h=sid=6a221d27b1ef3406e2dc4a822bb7fe9b4318590d

Regards,
Salvatore



Bug#885348: linux-image-4.14.0-2-amd64: aLatest kernel (linux-image-4.14.0-2-amd64) breaks e1000e driver on Intel 82579V Gigabit adapter

2017-12-28 Thread T

Does this affect 82574L as well?

/T



Bug#885348: linux-image-4.14.0-2-amd64: aLatest kernel (linux-image-4.14.0-2-amd64) breaks e1000e driver on Intel 82579V Gigabit adapter

2017-12-26 Thread Timo van Roermund

Hi Salvatore,


On 26-12-2017 16:37, Salvatore Bonaccorso wrote:

Hi Timo,

On Tue, Dec 26, 2017 at 03:38:24PM +0100, T.A. van Roermund wrote:

Package: src:linux
Version: 4.14.7-1
Severity: critical
Tags: patch upstream
Justification: breaks the whole system

Dear Maintainer,

This morning, I updated the Linux kernel from linux-image-4.13.0-1-amd64 to 
linux-image-4.14.0-2-amd64.
Afterwards, my Intel Gigabit adapter (details below) did not work properly 
anymore (no link).
When booting back into the previous kernel (4.13), everything works properly 
again.

It seems like others experience the same behavior, see:
https://bugzilla.kernel.org/show_bug.cgi?id=198047

According to that thread, this bug was introduced in v4.14.3 through commit 
830466993daf09adbd179e4c74db07279a088f8c
("e1000e: Separate signaling for link check/link up", upstream: 
19110cfbb34d4af0cdfe14cd243f3b09dc95b013).

The thread also includes a patch that (apparently) fixes the problem:
https://bugzilla.kernel.org/attachment.cgi?id=261183=diff==1=raw

Could you please apply this patch to the Debian kernel, until it is included in 
upstream?

Sorry to hear that. Would it be possible for you to confirm that the
patch fixes your issue, following:

https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2

Regards,
Salvatore


I followed these instructions to build a patched kernel:
Linux 4.14.0-2-amd64 #1 SMP Debian 4.14.7-1a~test (2017-12-27) x86_64 
GNU/Linux


With this kernel, the link of my Intel Gigabit adapter comes up again 
and works normally.


So yes, I can hereby confirm that the patch fixes my issue.

Best regards,

Timo



Bug#885348: linux-image-4.14.0-2-amd64: aLatest kernel (linux-image-4.14.0-2-amd64) breaks e1000e driver on Intel 82579V Gigabit adapter

2017-12-26 Thread Salvatore Bonaccorso
Hi Timo,

On Tue, Dec 26, 2017 at 03:38:24PM +0100, T.A. van Roermund wrote:
> Package: src:linux
> Version: 4.14.7-1
> Severity: critical
> Tags: patch upstream
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
> This morning, I updated the Linux kernel from linux-image-4.13.0-1-amd64 to 
> linux-image-4.14.0-2-amd64.
> Afterwards, my Intel Gigabit adapter (details below) did not work properly 
> anymore (no link).
> When booting back into the previous kernel (4.13), everything works properly 
> again.
> 
> It seems like others experience the same behavior, see:
> https://bugzilla.kernel.org/show_bug.cgi?id=198047
> 
> According to that thread, this bug was introduced in v4.14.3 through commit 
> 830466993daf09adbd179e4c74db07279a088f8c 
> ("e1000e: Separate signaling for link check/link up", upstream: 
> 19110cfbb34d4af0cdfe14cd243f3b09dc95b013).
> 
> The thread also includes a patch that (apparently) fixes the problem:
> https://bugzilla.kernel.org/attachment.cgi?id=261183=diff==1=raw
> 
> Could you please apply this patch to the Debian kernel, until it is included 
> in upstream?

Sorry to hear that. Would it be possible for you to confirm that the
patch fixes your issue, following:

https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2

Regards,
Salvatore



Bug#885348: linux-image-4.14.0-2-amd64: aLatest kernel (linux-image-4.14.0-2-amd64) breaks e1000e driver on Intel 82579V Gigabit adapter

2017-12-26 Thread T.A. van Roermund
Package: src:linux
Version: 4.14.7-1
Severity: critical
Tags: patch upstream
Justification: breaks the whole system

Dear Maintainer,

This morning, I updated the Linux kernel from linux-image-4.13.0-1-amd64 to 
linux-image-4.14.0-2-amd64.
Afterwards, my Intel Gigabit adapter (details below) did not work properly 
anymore (no link).
When booting back into the previous kernel (4.13), everything works properly 
again.

It seems like others experience the same behavior, see:
https://bugzilla.kernel.org/show_bug.cgi?id=198047

According to that thread, this bug was introduced in v4.14.3 through commit 
830466993daf09adbd179e4c74db07279a088f8c 
("e1000e: Separate signaling for link check/link up", upstream: 
19110cfbb34d4af0cdfe14cd243f3b09dc95b013).

The thread also includes a patch that (apparently) fixes the problem:
https://bugzilla.kernel.org/attachment.cgi?id=261183=diff==1=raw

Could you please apply this patch to the Debian kernel, until it is included in 
upstream?

Best regards,

Timo

** PCI devices:
00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network 
Connection [8086:1503] (rev 04)
Subsystem: Intel Corporation 82579V Gigabit Network Connection 
[8086:2041]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: e1000e
Kernel modules: e1000e