All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 74992] [NVAA] gnome-shell freezes with vram_list validate fail, texture traps
Date: Fri, 14 Feb 2014 19:16:41 +0000	[thread overview]
Message-ID: <bug-74992-8800-svWWUf1otV@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-74992-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 3389 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=74992

Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|display freeze              |[NVAA] gnome-shell freezes
                   |                            |with vram_list validate
                   |                            |fail, texture traps

--- Comment #4 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
[30028.608886] nouveau E[gnome-shell[1661]] fail ttm_validate
[30028.608894] nouveau E[gnome-shell[1661]] validate vram_list
[30028.608938] nouveau E[gnome-shell[1661]] validate: -12
[30029.187282] nouveau E[gnome-shell[1661]] fail ttm_validate
[30029.187290] nouveau E[gnome-shell[1661]] validate vram_list
[30029.187306] nouveau E[gnome-shell[1661]] validate: -12
[30029.706353] nouveau E[  PGRAPH][0000:02:00.0] magic set 0:
[30029.706364] nouveau E[  PGRAPH][0000:02:00.0]     0x00408604: 0x20081401
[30029.706368] nouveau E[  PGRAPH][0000:02:00.0]     0x00408608: 0x00000000
[30029.706372] nouveau E[  PGRAPH][0000:02:00.0]     0x0040860c: 0x40000432
[30029.706376] nouveau E[  PGRAPH][0000:02:00.0]     0x00408610: 0x00000000
[30029.706380] nouveau E[  PGRAPH][0000:02:00.0] TRAP_TEXTURE - TP0: Unhandled
ustatus 0x00000003
[30029.706383] nouveau E[  PGRAPH][0000:02:00.0]  TRAP
[30029.706390] nouveau E[  PGRAPH][0000:02:00.0] ch 4 [0x000797f000
gnome-shell[1661]] subc 3 class 0x8397 mthd 0x15e0 data 0x00000000
[30029.706400] nouveau E[     PFB][0000:02:00.0] trapped read at 0x0000000000
on channel 0x0000797f [gnome-shell[1661]] PGRAPH/TEXTURE/00 reason:
PT_NOT_PRESENT
[30029.706563] nouveau E[  PGRAPH][0000:02:00.0] magic set 0:
[30029.706566] nouveau E[  PGRAPH][0000:02:00.0]     0x00408604: 0x20086701
[30029.706570] nouveau E[  PGRAPH][0000:02:00.0]     0x00408608: 0x00000000
[30029.706573] nouveau E[  PGRAPH][0000:02:00.0]     0x0040860c: 0x40000432
[30029.706577] nouveau E[  PGRAPH][0000:02:00.0]     0x00408610: 0x00000000
[30029.706580] nouveau E[  PGRAPH][0000:02:00.0] TRAP_TEXTURE - TP0: Unhandled
ustatus 0x00000003
[30029.706583] nouveau E[  PGRAPH][0000:02:00.0]  TRAP
[30029.706588] nouveau E[  PGRAPH][0000:02:00.0] ch 4 [0x000797f000
gnome-shell[1661]] subc 3 class 0x8397 mthd 0x15e0 data 0x00000000


To me, this reads like "you ran out of vram and the driver did not handle this
at all gracefully". "Unhandled ustatus 3" means "FAULT" as best I can tell. And
of course since gnome-shell also acts as a compositor, that means your display
is shot.

The question is how can this happen though... I guess something was requested
to be migrated to vram and that request failed, but the driver didn't notice?
Not sure. Your second log shows a pushbuf submission failure that caused a
validate fail. I don't remember if that means that something was claimed to be
in VRAM and wasn't or if it means that something was requested to be moved to
vram and the move failed.

The fact that you can even go to another TTY and restart GS indicates that the
card is in no way hung, which is nice.

You don't mention what version of mesa you're using... but I'm assuming
something pretty recent, like 10.0.3 or maybe even 10.1-rc1?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4631 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-02-14 19:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 16:59 [Bug 74992] New: display freeze bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-74992-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-02-14 17:01   ` [Bug 74992] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-14 17:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-14 17:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-14 19:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-02-14 22:50   ` [Bug 74992] [NVAA] gnome-shell freezes with vram_list validate fail, texture traps bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-23  9:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-23  9:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-24 12:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-13 10:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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=bug-74992-8800-svWWUf1otV@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 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.