From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-kernel@vger.kernel.org
Subject: Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot
Date: Tue, 26 Apr 2016 21:00:08 +0200 [thread overview]
Message-ID: <20160426210008.2f79fcdf@kant> (raw)
Hi,
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.
In theory I could collect more info (simplify the hardware, run
netconsole, bisect). In practice I cannot do so for the the time being
due to lack of spare time. That's also the reason why I did not already
send a report when I tested v4.6-rc2, and why I did not boot v4.6-rc[25]
more than once yet.
--
Stefan Richter
-======----- -=-- ==-=-
http://arcgraph.de/sr/
next reply other threads:[~2016-04-26 19:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 19:00 Stefan Richter [this message]
2016-04-26 19:05 ` Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot Stefan Richter
2016-04-26 19:07 ` Stefan Richter
2016-04-27 18:51 ` Stefan Richter
2016-04-27 19:22 ` Stefan Richter
2016-04-27 19:37 ` Stefan Richter
2016-04-29 8:07 ` Stefan Richter
2016-04-30 13:51 ` Regression of v4.6-rc vs. v4.5: Merge tag 'drm-intel-next-2016-02-29' Stefan Richter
2016-05-05 17:45 ` Regression of v4.6-rc vs. v4.5 bisected: a98ee79317b4 "drm/i915/fbc: enable FBC by default on HSW and BDW" Stefan Richter
2016-05-05 18:50 ` Zanoni, Paulo R
2016-05-05 19:59 ` Daniel Vetter
2016-05-05 19:59 ` [Intel-gfx] " Daniel Vetter
2016-05-05 22:56 ` Stefan Richter
2016-05-05 22:56 ` Stefan Richter
2016-05-05 22:54 ` Stefan Richter
2016-05-05 22:54 ` Stefan Richter
2016-05-05 23:55 ` Zanoni, Paulo R
2016-05-05 23:55 ` Zanoni, Paulo R
2016-05-08 10:18 ` Stefan Richter
2016-05-08 10:18 ` Stefan Richter
2016-05-08 11:20 ` Stefan Richter
2016-05-08 11:20 ` Stefan Richter
2016-05-05 19:54 ` Stefan Richter
2016-05-05 19:54 ` Stefan Richter
2016-05-05 20:45 ` Stefan Richter
2016-05-05 20:45 ` Stefan Richter
2016-05-06 6:37 ` Daniel Vetter
2016-05-06 6:37 ` Daniel Vetter
2016-05-08 11:44 ` Stefan Richter
2016-05-08 11:44 ` Stefan Richter
2016-05-08 11:49 ` Stefan Richter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160426210008.2f79fcdf@kant \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.