From: Pekka Enberg <penberg@kernel.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Move the irq wait queue initialisation into the ring init
Date: Tue, 29 Mar 2011 16:39:53 +0300 [thread overview]
Message-ID: <AANLkTi=Adq8i_qoiHhLB9K-CkUbT8uHZeg-H8Z3_Kgrw@mail.gmail.com> (raw)
In-Reply-To: <1bdc18$k1kc9s@fmsmga002.fm.intel.com>
On Tue, Mar 29, 2011 at 4:22 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Tue, 29 Mar 2011 16:05:35 +0300, Pekka Enberg <penberg@kernel.org> wrote:
>> On Tue, Mar 29, 2011 at 3:23 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>> > Required so that we don't obliterate the queue if initialising the
>> > rings after the global IRQ handler is installed.
>> >
>> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>>
>> I applied both of the patches on top of yesterdays git HEAD and I just
>> get a blank screen after GRUB. No serial or net console here. Do you
>> want me to try just one of the patches or turn on some debugging
>> options?
>
> That was the unspoken side-effect: if we fail to load the i915 module after
> disabling the outputs, then we would be left with a blank screen.
>
> If you can ssh in and retrieve the dmesg, then it should at least give a
> reason...
I have
CONFIG_DRM_I915=y
so there are no modules involved. I'll see if I can ssh to the box.
next prev parent reply other threads:[~2011-03-29 13:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=VqkYjdiDLJvM-OfmBSGx-EkRkt=4XCDEnvZsU@mail.gmail.com>
2011-03-29 10:46 ` [PATCH] drm/i915: Disable all outputs early, before KMS takeover Chris Wilson
2011-03-29 12:23 ` [PATCH] drm/i915: Move the irq wait queue initialisation into the ring init Chris Wilson
2011-03-29 13:05 ` Pekka Enberg
2011-03-29 13:22 ` Chris Wilson
2011-03-29 13:39 ` Pekka Enberg [this message]
2011-03-29 14:22 ` Pekka Enberg
2011-03-29 14:32 ` Chris Wilson
2011-03-29 15:21 ` Pekka Enberg
2011-04-01 11:44 ` [PATCH] drm/i915: Disable all outputs early, before KMS takeover Daniel Vetter
2011-04-01 11:51 ` [Intel-gfx] " Pekka Enberg
2011-04-05 10:21 ` Tomas Winkler
2011-04-05 10:30 ` Chris Wilson
2011-04-05 10:37 ` Pekka Enberg
2011-04-05 11:55 ` Tomas Winkler
2011-04-05 14:11 ` Pekka Enberg
2011-04-05 14:27 ` Chris Wilson
2011-04-05 14:31 ` [Intel-gfx] " Pekka Enberg
2011-04-05 14:34 ` Chris Wilson
2011-04-05 15:11 ` Pekka Enberg
2011-04-05 15:32 ` Chris Wilson
2011-04-05 15:44 ` Pekka Enberg
2011-04-05 14:42 ` Linus Torvalds
2011-04-05 15:01 ` Keith Packard
2011-04-05 15:12 ` [Intel-gfx] " Chris Wilson
2011-04-05 15:35 ` Pekka Enberg
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='AANLkTi=Adq8i_qoiHhLB9K-CkUbT8uHZeg-H8Z3_Kgrw@mail.gmail.com' \
--to=penberg@kernel.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--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).