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 69375] New: [NV4E] GPU lockup when using chrome/flash
Date: Sun, 15 Sep 2013 12:36:09 +0000	[thread overview]
Message-ID: <bug-69375-8800@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 69375
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: [NV4E] GPU lockup when using chrome/flash
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: taylor_tails-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: Driver/nouveau
           Product: xorg

Created attachment 85858
  --> https://bugs.freedesktop.org/attachment.cgi?id=85858&action=edit
dmesg output

I recent upgrade using apt-get dist-upgrade on debian testing ~2 weeks ago has
caused chrome to start looking up the GPU.

dmesg highlights:
Linux version 3.9-1-amd64

[  805.747928] nouveau E[  PGRAPH][0000:00:05.0]  ERROR nsource: DATA_ERROR
nstatus: BAD_ARGUMENT
[  805.747945] nouveau E[  PGRAPH][0000:00:05.0] ch 3 [0x00056000 chrome[3853]]
subc 2 class 0x0039 mthd 0x0314 data 0x01197000
[  836.696327] nouveau E[   PFIFO][0000:00:05.0] DMA_PUSHER - ch 3
[chrome[3853]] get 0xbeef0200 put 0x0065a6f4 state 0xc0028188 (err: MEM_FAULT)
push 0x00001000
[  850.504026] nouveau E[chrome[3853]] failed to idle channel 0xcccc0000
[chrome[3853]]
[  853.508018] nouveau E[chrome[3853]] failed to idle channel 0xcccc0000
[chrome[3853]]
[  863.804030] nouveau E[Xorg[2162]] reloc wait_idle failed: -16
[  863.804036] nouveau E[Xorg[2162]] reloc apply: -16
[  865.743035] nouveau E[     DRM] GPU lockup - switching to software fbcon
[  866.804032] nouveau E[Xorg[2162]] reloc wait_idle failed: -16
[  866.804079] nouveau E[Xorg[2162]] reloc apply: -16
[  869.804037] nouveau E[Xorg[2162]] reloc wait_idle failed: -16
[  869.804103] nouveau E[Xorg[2162]] reloc apply: -16
[  887.836034] nouveau E[Xorg[2162]] failed to idle channel 0xcccc0000
[Xorg[2162]]
[  890.836025] nouveau E[Xorg[2162]] failed to idle channel 0xcccc0000
[Xorg[2162]]

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

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

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

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

             reply	other threads:[~2013-09-15 12:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-15 12:36 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-69375-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-09-16 15:25   ` [Bug 69375] [NV4E] GPU lockup when using chrome/flash bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-16 15:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-16 15:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-16 15:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-16 15:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-16 15:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-09 20:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-11 21:08   ` 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-69375-8800@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.