On 04/03/2014 05:06 PM, Alexander Holler wrote: > Am 03.04.2014 10:49, schrieb Sebastian Hesselbarth: >> On 04/03/2014 09:17 AM, Alexander Holler wrote: >>> Am 03.04.2014 00:27, schrieb Sebastian Hesselbarth: >>>> On 04/03/2014 12:12 AM, Alexander Holler wrote: >>>>>> I am curious, how you determined above commit to be the cause of the >>>>>> regression you are seeing. Can you bisect, if you didn't already? >>>>> >>>>> There was no bisecting necessary. I've just looked at what changed in >>>>> mv643xx_eth since 3.13 and the first commit I've reverted was >>>>> already a >>>>> hit. Reading a bit source revealed the differences between the old >>>>> reset >>>>> and the newly used one and ended up with my patch (first try) and >>>>> was a >>>>> hit too. >>>> > > Sorry, continuing this discussion doesn't make sense. You have the same > hw, so just try enabling netconsole with 3.14 and use dhcpcd from > userland (this does the final reset here which hangs. > > But don't suggest me (or insist on) a time consuming and totally useless > bisect when I already know what makes the problem to appear (100% > reliable here). Alexander, I tried to reproduce the regression on Dockstar with 3.14.0 and 3.14.0-07247-gcd6362be, netconsole enabled, DHCP (dhclient). I can neither reproduce any issues with ethernet before nor after dhclient kicks in. I can also use netconsole just fine and see plenty of kernel bootlog messages sent to netconsole receiver. Can you _please_ share a full report how to properly reproduce it? Sebastian -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html