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 73373] New: [NVE4] GPU lockup after opening many tabs in Chromium web browser
Date: Tue, 07 Jan 2014 21:44:05 +0000	[thread overview]
Message-ID: <bug-73373-8800@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 73373
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: [NVE4] GPU lockup after opening many tabs in Chromium
                    web browser
          Severity: blocker
    Classification: Unclassified
                OS: Linux (All)
          Reporter: mbarrera-KK0ffGbhmjU@public.gmane.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: 10.0
         Component: Drivers/DRI/nouveau
           Product: Mesa

When using the Chromium web browser, if I open too many tabs with graphics, the
graphics will crash leaving the desktop not responsive, still the system will
continue to work.

Attached are the kernel logs I got through SSH after reproducing the bug four
times.

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

[-- Attachment #1.2: Type: text/html, Size: 2180 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:[~2014-01-07 21:44 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 21:44 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-73373-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-01-07 21:44   ` [Bug 73373] [NVE4] GPU lockup after opening many tabs in Chromium web browser bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-07 21:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-07 21:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-07 21:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-07 21:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-07 21:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-07 21:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-07 21:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-07 21:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-07 21:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-08 18:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-08 18:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-08 23:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-09  1:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-25 19:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-25 19:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-25 20:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-25 20:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-01  1:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-28  8:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-28  8:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 19:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-03 16:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-03 16:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-03 16:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-10 14:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-11 22:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-13 15:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:41   ` 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-73373-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.