From: Stefan Lippers-Hollmann <s.l-h@gmx.de>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Dave Airlie <airlied@linux.ie>,
Ander Conselvan de Oliveira
<ander.conselvan.de.oliveira@intel.com>,
Nicolas Kalkhof <nkalkhof@web.de>,
Jani Nikula <jani.nikula@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org,
DRI mailing list <dri-devel@lists.freedesktop.org>,
torvalds@linux-foundation.org
Subject: Re: git pull] drm for v4.1-rc1
Date: Sun, 7 Jun 2015 04:32:53 +0200 [thread overview]
Message-ID: <20150607043253.12f4058e@mir> (raw)
In-Reply-To: <20150606235248.GZ5176@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 2139 bytes --]
Hi
On 2015-06-07, Ville Syrjälä wrote:
> On Fri, Jun 05, 2015 at 11:18:21PM +0200, Stefan Lippers-Hollmann wrote:
> > Hi
> >
> > On 2015-04-20, Dave Airlie wrote:
> > [...]
> > > The following changes since commit 09d51602cf84a1264946711dd4ea0dddbac599a1:
> > >
> > > Merge branch 'turbostat' of git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux (2015-04-19 14:31:41 -0700)
> > >
> > > are available in the git repository at:
> > >
> > > git://people.freedesktop.org/~airlied/linux drm-next-merged
> > >
> > > for you to fetch changes up to 2c33ce009ca2389dbf0535d0672214d09738e35e:
> > >
> > > Merge Linus master into drm-next (2015-04-20 13:05:20 +1000)
> > [...]
> > > Ander Conselvan de Oliveira (28):
> > [...]
> > > drm/i915: Allocate connector state together with the connectors
> > [...]
> >
> > This commit introduces a regression relative to v4.0 on an Intel
> > D945GCLF2 mainboard[1] (Atom 330) with Intel 82945G/GZ onboard graphics
> > using its (only-) VGA connector for me.
> >
> > v4.1-rc6-52-gff25ea8:
> > [ 13.265699] BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
> > [ 13.265723] IP: [<ffffffffa0556f01>] intel_modeset_update_connector_atomic_state+0x61/0x90 [i915]
>
> Hmm. Smells like a connector with a NULL state pointer, and the bad
> commit touched exactly the part that sets it up. I can't immediately
> spot any place where we'd forget to set it up though.
>
> Can you try with something like this so we'd at least find out which
> connector(s) is/are at fault here?
With the patch applied, the kernel (v4.1-rc6-104-g4b17069) locks up even
harder, so I had to switch to a serial console in order to fetch the
boot messages:
[ 13.492784] connector = ffff880079bb8000
[ 13.910439] connector = ffff8800795b5800
[ 14.463114] connector = ffff8800795b6000
[ 14.700707] connector = ffff8800795b6800
[ 14.869418] connector = ffff8800795b7000
[ 14.923848] connector = ffff8800795b7000
Full, gzipped, bootlog attached - thanks a lot for your efforts.
Regards
Stefan Lippers-Hollmann
[-- Attachment #1.2: D945GCLF2.dmesg.gz --]
[-- Type: application/gzip, Size: 15935 bytes --]
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-07 2:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 3:32 git pull] drm for v4.1-rc1 Dave Airlie
2015-04-21 16:07 ` Linus Torvalds
2015-04-21 21:12 ` Bjorn Helgaas
2015-04-23 21:30 ` Bjorn Helgaas
2015-04-23 21:56 ` Matthew Garrett
2015-04-23 22:47 ` Linus Torvalds
2015-04-23 22:59 ` Matthew Garrett
2015-04-24 0:55 ` Alex Deucher
2015-06-05 21:18 ` Stefan Lippers-Hollmann
2015-06-06 23:52 ` Ville Syrjälä
2015-06-07 2:32 ` Stefan Lippers-Hollmann [this message]
2015-06-08 8:06 ` Ander Conselvan De Oliveira
2015-06-08 8:29 ` Ander Conselvan De Oliveira
2015-06-08 10:28 ` Stefan Lippers-Hollmann
2015-06-08 8:26 ` [PATCH] drm/i915: Properly initialize SDVO analog connectors Ander Conselvan de Oliveira
2015-06-08 10:36 ` [Fwd: Re: [PATCH] drm/i915: Properly initialize SDVO analog connectors] Ander Conselvan De Oliveira
2015-06-08 10:50 ` [PATCH] drm/i915: Properly initialize SDVO analog connectors Jani Nikula
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=20150607043253.12f4058e@mir \
--to=s.l-h@gmx.de \
--cc=airlied@linux.ie \
--cc=ander.conselvan.de.oliveira@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nkalkhof@web.de \
--cc=torvalds@linux-foundation.org \
--cc=ville.syrjala@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox