From: Pekka Enberg <penberg@kernel.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tomas Winkler <tomasw@gmail.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Daniel Vetter <daniel@ffwll.ch>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Disable all outputs early, before KMS takeover
Date: Tue, 5 Apr 2011 17:11:56 +0300 [thread overview]
Message-ID: <BANLkTins76X1mOFepqXEQjMEh_hd4Vgw1Q@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=kXod21RUukrTuMzP5TFqgo4NxRw@mail.gmail.com>
On Tue, Apr 5, 2011 at 1:37 PM, Pekka Enberg <penberg@kernel.org> wrote:
> Hi Chris!
>
> On Tue, Apr 5, 2011 at 1:30 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>> On Tue, 5 Apr 2011 13:21:08 +0300, Tomas Winkler <tomasw@gmail.com> wrote:
>>> On Fri, Apr 1, 2011 at 2:51 PM, Pekka Enberg <penberg@kernel.org> wrote:
>>> > Unfortunately I get a blank screen with after boot:
>>> > Nacked-by: Pekka Enberg <penberg@kernel.org>
>>
>> But until you can tell me where it explodes on your system, we fix
>> issues on several other machines...
>
> Oh, that's nice, you first made the damn thing flicker in 2.6.39-rc1
> and now you're fixing it for others by giving me a blank screen after
> boot?
I compiled i195 drm as module and I now see this with netconsole:
[ 4.861272] i8042: No controller found
[ 5.260688] Unable to load isight firmware
[ 7.120150] usbhid 5-1:1.0: couldn't find an input interrupt endpoint
[ 9.310010]
[ 9.310010] Pid: 3757, comm: sh Not tainted 2.6.38+ #18 Apple Inc.
MacBook2,1/Mac-F4208CAA
[ 9.310010] RIP: 0010:[<0000000000000000>] [< (null)>]
(null)
[ 9.310010] RSP: 0018:ffff88003de03d80 EFLAGS: 00010096
[ 9.310010] RAX: 000000000000006d RBX: ffff88002e6be000 RCX: 000000000003ffff
[ 9.310010] RDX: 0000000000000000 RSI: 0000000000000046 RDI: ffff88002e6be030
[ 9.310010] RBP: ffff88003de03de8 R08: 0000000000000000 R09: 0000000000000000
[ 9.310010] R10: 0000000000000006 R11: 0000000000000003 R12: ffff88002e5db800
[ 9.310010] R13: ffff88002e6be82c R14: ffff88003ad24200 R15: 0000000000000000
[ 9.310010] FS: 00007f60f21aa700(0000) GS:ffff88003de00000(0000)
knlGS:0000000000000000
[ 9.310010] [<ffffffffa0061628>] ? i915_handle_error+0x198/0xed0 [i915]
[ 9.310010] [<ffffffff8137d04a>] ? scsi_next_command+0x4a/0x60
[ 9.310010] [<ffffffff8137ddd6>] ? scsi_io_completion+0x2f6/0x630
[ 9.310010] [<ffffffffa0064c62>] i915_driver_irq_handler+0x472/0x17f0 [i915]
[ 9.310010] [<ffffffff810e150d>] handle_irq_event_percpu+0x5d/0x210
[ 9.310010] [<ffffffff8108c56c>] ? __do_softirq+0x11c/0x200
[ 9.310010] [<ffffffff8108c56c>] ? __do_softirq+0x11c/0x200
[ 9.310010] [<ffffffff810e173a>] handle_irq_event+0x4a/0x80
[ 9.310010] [<ffffffff810e42c1>] handle_fasteoi_irq+0x51/0xc0
[ 9.310010] [<ffffffff8103e3a2>] handle_irq+0x22/0x30
[ 9.310010] [<ffffffff81698e0d>] do_IRQ+0x5d/0xe0
[ 9.310010] [<ffffffff8168fad3>] common_interrupt+0x13/0x13
[ 9.310010] <EOI> [ 9.310010] Call Trace:
[ 9.310010] <IRQ> [<ffffffff8168cd0c>] panic+0x91/0x19e
[ 9.310010] [<ffffffff816909ea>] oops_end+0xea/0xf0
[ 9.310010] [<ffffffff8106afbb>] no_context+0xfb/0x260
[ 9.310010] [<ffffffff8106b245>] __bad_area_nosemaphore+0x125/0x1e0
[ 9.310010] [<ffffffff8106b313>] bad_area_nosemaphore+0x13/0x20
[ 9.310010] [<ffffffff816930c0>] do_page_fault+0x310/0x4c0
[ 9.310010] [<ffffffff810ac06f>] ? up+0x2f/0x50
[ 9.310010] [<ffffffff8108652f>] ? console_unlock+0x17f/0x1d0
[ 9.310010] [<ffffffff8168fd25>] page_fault+0x25/0x30
[ 9.310010] [<ffffffffa0061628>] ? i915_handle_error+0x198/0xed0 [i915]
[ 9.310010] [<ffffffff8137d04a>] ? scsi_next_command+0x4a/0x60
[ 9.310010] [<ffffffff8137ddd6>] ? scsi_io_completion+0x2f6/0x630
[ 9.310010] [<ffffffffa0064c62>] i915_driver_irq_handler+0x472/0x17f0 [i915]
This is the same pre-2.6.39-rc1 kernel with the two patches applied.
I'll try latest Linus master next to see if the same problem triggers.
Pekka
next prev parent reply other threads:[~2011-04-05 14:11 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
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 [this message]
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=BANLkTins76X1mOFepqXEQjMEh_hd4Vgw1Q@mail.gmail.com \
--to=penberg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomasw@gmail.com \
--cc=torvalds@linux-foundation.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).