All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-kernel@vger.kernel.org
Cc: Dave Airlie <airlied@redhat.com>
Subject: Re: Regression of v4.6-rc vs. v4.5: Merge tag 'drm-intel-next-2016-02-29'
Date: Sat, 30 Apr 2016 15:51:54 +0200	[thread overview]
Message-ID: <20160430155154.597829ca@kant> (raw)
In-Reply-To: <20160429100741.6be95385@kant>

On Apr 29 Stefan Richter wrote:
> 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.

 .config: http://www.spinics.net/lists/kernel/msg2243444.html
   lspci: http://www.spinics.net/lists/kernel/msg2243447.html

Some userland package versions, in case these have any bearing:
x11-base/xorg-drivers-1.17
x11-base/xorg-server-1.17.4
x11-bas/xorg-x11-7.4-r2

> 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...)

There are about 9 more bisection steps left to go.
The first few steps sent me straight into DRM land.
My current "git bisect log" with own annotations:

git bisect start

# bad: [9735a22799b9214d17d3c231fe377fc852f042e9] Linux 4.6-rc2
git bisect bad 9735a22799b9214d17d3c231fe377fc852f042e9

# good: [b562e44f507e863c6792946e4e1b1449fbbac85d] Linux 4.5
git bisect good b562e44f507e863c6792946e4e1b1449fbbac85d

# good: [6b5f04b6cf8ebab9a65d9c0026c650bb2538fd0f] Merge branch 'for-4.6' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup
# ++ still good after 18 h uptime
git bisect good 6b5f04b6cf8ebab9a65d9c0026c650bb2538fd0f

# good: [2c856e14dad8cb1b085ae1f30c5e125c6d46019b] Merge tag 'arm64-perf' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
# ++ still good after 24 h uptime
git bisect good 2c856e14dad8cb1b085ae1f30c5e125c6d46019b

# bad: [8bb7e27bbb9d0db7ca0e83d40810fb752381cdd5] staging: delete STE RMI4 hackish driver
# -- hung after 3 h uptime
git bisect bad 8bb7e27bbb9d0db7ca0e83d40810fb752381cdd5

# bad: [507d44a9e1bb01661c75b88fd866d2461ab41c9c] Merge tag 'drm-intel-next-2016-02-29' of git://anongit.freedesktop.org/drm-intel into drm-next
# -- hung after 2 h uptime
git bisect bad 507d44a9e1bb01661c75b88fd866d2461ab41c9c
-- 
Stefan Richter
-======----- -=-- ====-
http://arcgraph.de/sr/

  reply	other threads:[~2016-04-30 13:52 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 19:00 Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot Stefan Richter
2016-04-26 19:05 ` 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   ` Stefan Richter [this message]
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=20160430155154.597829ca@kant \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=airlied@redhat.com \
    --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.