Date: Fri, 29 Apr 2016 10:07:41 +0200
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Regression of v4.6-rc vs. v4.5: hangs after a few minutes after
 boot
Message-ID: <20160429100741.6be95385@kant>
In-Reply-To: <20160426210008.2f79fcdf@kant>
References: <20160426210008.2f79fcdf@kant>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1442
Lines: 34

On Apr 26 Stefan Richter wrote:
> v4.6-rc solidly hangs after a short while after boot, login to X11, and
> doing nothing much remarkable on the just brought up X desktop.
> 
> Hardware: x86-64, E3-1245 v3 (Haswell),
>           mainboard Supermicro X10SAE,
>           using integrated Intel graphics (HD P4600, i915 driver),
>           C226 PCH's AHCI and USB 2/3, ASMedia ASM1062 AHCI,
>           Intel LAN (i217, igb driver),
>           several IEEE 1394 controllers, some of them behind
>           PCIe bridges (IDT, PLX) or PCIe-to-PCI bridges (TI, Tundra)
>           and one PCI-to-CardBus bridge (Ricoh)
> 
> kernel.org kernel, Gentoo Linux userland
> 
> 1. known good:  v4.5-rc5 (gcc 4.9.3)
>    known bad:   v4.6-rc2 (gcc 4.9.3), only tried one time
> 
> 2. known good:  v4.5.2 (gcc 5.2.0)
>    known bad:   v4.6-rc5 (gcc 5.2.0), only tried one time
> 
> I will send my linux-4.6-rc5/.config in a follow-up message.

After it proved impossible to capture an oops through netconsole, I
started git bisect.  This will apparently take almost a week, as git
estimated 13 bisection steps and I will be allowing about 12 hours of
uptime as a sign for a good kernel.  (In my four or five tests of bad
kernels before I started bisection, they hung after 3 minutes...5.5 hours
uptime, with no discernible difference in workload.  Maybe 12 h cutoff is
even too short...)
-- 
Stefan Richter
-======----- -=-- ===-=
http://arcgraph.de/sr/