From: Ted Percival <ted@tedp.id.au>
To: Maarten Lankhorst <maarten.lankhorst@ubuntu.com>
Cc: Ben Skeggs <bskeggs@redhat.com>, dri-devel@lists.freedesktop.org
Subject: nouveau regression: read fault PAGE_NOT_PRESENT with new fence interface
Date: Thu, 18 Sep 2014 14:07:33 -0600 [thread overview]
Message-ID: <541B3B85.6000906@tedp.id.au> (raw)
Hi, I noticed a regression in the next-20140903 kernel that was not
present in next-20140902. When Xorg starts up, the display is garbled
(or contains old image bits) and I see a page fault in the kernel log. X
is not usable in this state - there is no pointer and gdm doesn't come
up. It works fine after Xorg (gdm3) is restarted. The fault is still
present in next-20140918.
[drm] Initialized nouveau 1.2.0 20120801 for 0000:01:00.0 on minor 0
nouveau E[ PFIFO][0000:01:00.0] read fault at 0x0001260000
[PAGE_NOT_PRESENT] from PGRAPH/GPC0/TEX on channel 0x001fcd1000 [Xorg[3874]]
nouveau E[ PFIFO][0000:01:00.0] PGRAPH engine fault on channel 2,
recovering...
nouveau E[ PGRAPH][0000:01:00.0] TRAP ch 2 [0x001fcd1000 Xorg[3874]]
nouveau E[ PGRAPH][0000:01:00.0] GPC0/TPC0/TEX: 0x80000041
My hardware is: NVIDIA Corporation GF119 [Quadro NVS 4200M] (rev a1)
I bisected it down to this commit:
commit 29ba89b2371d466ca68973525816cf10debc2655
Author: Maarten Lankhorst <maarten.lankhorst@ubuntu.com>
Date: Thu Jan 9 11:03:11 2014 +0100
drm/nouveau: rework to new fence interface
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
Acked-by: Ben Skeggs <bskeggs@redhat.com>
I tried tracing the DEVICE, PGRAPH, PFIFO & PCE0 engines but nothing
obvious stood out before the read fault shown above.
Is there any other information I can provide to help track this down?
paranoia or spam level logging, for example?
next reply other threads:[~2014-09-18 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 20:07 Ted Percival [this message]
2014-09-22 8:38 ` nouveau regression: read fault PAGE_NOT_PRESENT with new fence interface Maarten Lankhorst
2014-09-22 16:19 ` Ted Percival
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=541B3B85.6000906@tedp.id.au \
--to=ted@tedp.id.au \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=maarten.lankhorst@ubuntu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.