linux-kernel - Re: [PATCH] drm/i915: Move the irq wait queue initialisation into the ring init

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 29 Mar 2011 17:22:13 +0300
From:	Pekka Enberg <penberg@...nel.org>
To:	Chris Wilson <chris@...is-wilson.co.uk>
Cc:	intel-gfx@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drm/i915: Move the irq wait queue initialisation into the
 ring init

On Tue, Mar 29, 2011 at 4:39 PM, Pekka Enberg <penberg@...nel.org> wrote:
> On Tue, Mar 29, 2011 at 4:22 PM, Chris Wilson <chris@...is-wilson.co.uk> wrote:
>> On Tue, 29 Mar 2011 16:05:35 +0300, Pekka Enberg <penberg@...nel.org> wrote:
>>> On Tue, Mar 29, 2011 at 3:23 PM, Chris Wilson <chris@...is-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@...is-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.

No ssh - the box seems to be dead.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/