From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Mihai Moldovan <ionic@ionic.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: null pointer dereference while loading i915
Date: Fri, 10 Aug 2012 12:10:59 +0200 [thread overview]
Message-ID: <CAKMK7uFutq0Hn3FL==53Vvt-M00ReWaeXKq3uo8C_kzUfX+1ew@mail.gmail.com> (raw)
In-Reply-To: <5021F00B.7000503@ionic.de>
On Wed, Aug 8, 2012 at 6:50 AM, Mihai Moldovan <ionic@ionic.de> wrote:
> Hi Daniel, hi list
>
> ever since version 3.2.0 (maybe even earlier, but 3.0.2 is still working fine),
> my box is crashing when loading the i915 driver (mode-setting enabled.)
>
> The current version I'm testing with is 3.5.0.
>
> I was able to get the BUG output (please forgive any errors/flips in the output,
> I have had to transcribe the messages from the screen/images), however, I'm not
> able to find out what's wrong.
>
> If I see it correctly, there's a null pointer dereference in a printk called
> from inside gmbus_xfer. The only printk calls I can see in
> drivers/gpu/drm/i915/intel_i2c.c gmbus_xfer() however are issued by the
> DRM_DEBUG_KMS() and DRM_INFO() macros.
> Neither call looks wrong to me, I even tried to swap adapter->name with
> bus->adapter.name and make *sure* i < num is true, but haven't had any success.
>
> I'd really like to see this bug fixed, as it's preventing me from updating the
> kernel for over a year now.
>
> Also, while 3.0.2 works, it *does* spew error/warning messages related to gmbus
> and I've had corrupted VTs in the past (albeit after a long uptime with multiple
> X restarting and DVI cable unplugging/reattaching events), so maybe there's a
> lot more broken than "expected".
Hm, this is rather strange. gmbus should not be enable on 3.2 nor 3.0,
since exactly this issue might happen. We've re-enabled gmbus again on
3.5 after having fixed this bug. Are you sure that this is plain 3.2
you're running?
Yours, Daniel
--
Daniel Vetter
daniel.vetter@ffwll.ch - +41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2012-08-10 10:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 4:50 null pointer dereference while loading i915 Mihai Moldovan
2012-08-10 10:10 ` Daniel Vetter [this message]
2012-08-10 16:05 ` Mihai Moldovan
2012-08-10 16:39 ` Daniel Vetter
2012-08-10 17:44 ` Mihai Moldovan
2012-08-10 23:09 ` Mihai Moldovan
2012-08-13 14:33 ` [PATCH 0/1] hopefully fix null pointer dereference on i915 load Jani Nikula
2012-08-13 14:33 ` [PATCH 1/1] drm/i915: ensure i2c adapter is all set before adding it Jani Nikula
2012-08-13 17:05 ` Daniel Vetter
2012-08-13 15:03 ` [PATCH 0/1] hopefully fix null pointer dereference on i915 load Mihai Moldovan
2012-08-13 15:09 ` Daniel Vetter
2012-08-13 15:27 ` Mihai Moldovan
2012-08-13 16:15 ` Mihai Moldovan
2012-08-14 6:17 ` 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='CAKMK7uFutq0Hn3FL==53Vvt-M00ReWaeXKq3uo8C_kzUfX+1ew@mail.gmail.com' \
--to=daniel.vetter@ffwll.ch \
--cc=ionic@ionic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).