On 10/12/2017 06:13 AM, Greg Kroah-Hartman wrote: > On Thu, Oct 12, 2017 at 01:54:26PM +0200, Greg Kroah-Hartman wrote: >> On Thu, Oct 12, 2017 at 12:39:52PM +0200, Greg Kroah-Hartman wrote: >>> On Wed, Oct 11, 2017 at 04:54:51PM -0600, Shuah Khan wrote: >>>> On 10/11/2017 06:56 AM, Greg Kroah-Hartman wrote: >>>>> On Tue, Oct 10, 2017 at 06:58:40PM -0600, Shuah Khan wrote: >>>>>> On 10/10/2017 01:49 PM, Greg Kroah-Hartman wrote: >>>>>>> This is the start of the stable review cycle for the 4.9.55 release. >>>>>>> There are 105 patches in this series, all will be posted as a response >>>>>>> to this one. If anyone has any issues with these being applied, please >>>>>>> let me know. >>>>>>> >>>>>>> Responses should be made by Thu Oct 12 19:24:56 UTC 2017. >>>>>>> Anything received after that time might be too late. >>>>>>> >>>>>>> The whole patch series can be found in one patch at: >>>>>>> >>>>>>> kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.55-rc1.gz >>>>>>> or in the git tree and branch at: >>>>>>> >>>>>>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >>>>>>> linux-4.9.y >>>>>>> and the diffstat can be found below. >>>>>>> >>>>>>> thanks, >>>>>>> >>>>>>> greg k-h >>>>>>> >>>>>> >>>>>> Compiled and booted. Networking is dead. I will bisect tomorrow and >>>>>> let you know what I find. >>>>>> >>>>>> r8169 is the suspect perhaps or some other change that affects it. >>>>>> Anyway more on this tomorrow. >>>>> >>>>> Odd, let me know if you find anything. >>>>> >>>> >>>> git bisect came up with the following: >>>> >>>> # first bad commit: [830e3de48a789f8d294a0d1461600f958afddde4] >>>> ip6_gre: skb_push ipv6hdr before packing the header in ip6gre_header >>>> >>>> However, reverting this commit didn't work either. I might have to >>>> start bisect again. Update for now in case David or Xin Long can >>>> think of something that could possibly lead this failure. There are >>>> a few more patches in this space. >>> >>> What is the symptom of the networking failure? No networking device? >>> No dhcp request? ipv4 or ipv6? Differences in dmesg?
No differences in dmesg. The interface reports it is up, however doesn't respond to ping. Network manager reports it down. I enabled and disabled the networking. That didn't bring it back. Doesn't happen on 4.9.54. >> >> Hm, I'm getting an odd report from some of the google auto-builders >> about a networking issue as well with 4.9. So you might be onto >> something here. I really have no insight into the google tests to >> figure out what it is doing, but I can feed it patches to test, so I'll >> try reverting this patch to see if it solves anything or not... > > Nope reverting that failed as well, I'm running out of time at the > moment to test this, will be able to pick it back up later this evening > or tomorrow, so any help you could provide here would be great. > I will do some controlled tests today. I will have to run through bisect again. There are other ipv6 related patches in this release. I will let you know what I can find. I don't think it is driver/hw related. thanks, -- Shuah
