Hello,
I think this bug can be closed as the kernel version has been updated which
pretty much was the purpose of the original bug request.
Thank you.
Kind Regards,
Narayanan.
On Fri, 2017-02-17 at 09:03 +0530, Narayanan R S wrote:
> Hi Ben,
>
> I can try (re)running the 4.9 backport and see if the issue resurfaces.
>
> What is the correlation between the debian kernel (backported) and the
> mainline one (it says version 4.9.2-2~bpo8+1 - so is it essentially
>
Hi Ben,
I can try (re)running the 4.9 backport and see if the issue resurfaces.
What is the correlation between the debian kernel (backported) and the
mainline one (it says version 4.9.2-2~bpo8+1 - so is it essentially
_EXACTLY_ 4.9.2)?
Thanks.
Regards,
Narayanan.
On Fri, Feb 17, 2017 at
[Reply to all, not just to me.]
On Fri, 2017-02-17 at 08:42 +0530, Narayanan R S wrote:
> Hello Ben,
>
> I did have the documented ICMP network issues when I used the 4.9 version
> of the backported kernel.
>
> When I reverted back to the 4.8 version (of the backported kernel),
> everything was
Forwarded Message
Message-id:
Control: tag -1 moreinfo
On Thu, 2017-02-09 at 17:55 +0530, Narayanan R S wrote:
> Package: linux-image-amd64
> Version: 4.9+78
>
> The current (backported) version of linux-image-amd64 (for Jessie) appears
> to need a few important fixes from the kernel source (upstream).
>
> Please see:
>
>
Package: linux-image-amd64
Version: 4.9+78
The current (backported) version of linux-image-amd64 (for Jessie) appears
to need a few important fixes from the kernel source (upstream).
Please see:
https://www.spinics.net/lists/kernel/msg2406212.html
7 matches
Mail list logo
