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 79518] nouveau causes lockup and reboot on GT215
Date: Wed, 06 Apr 2016 07:48:10 +0000	[thread overview]
Message-ID: <bug-79518-8800-dxJMmFM7xt@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-79518-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #2 from Adam Borowski <kilobyte-b9QjgO8OEXPVItvQsEIGlw@public.gmane.org> ---
Created attachment 122750
  --> https://bugs.freedesktop.org/attachment.cgi?id=122750&action=edit
syslog with kernel 4.6-rc2

With kernel 4.6-rc2, there's some new output, including a stack trace.
The frequency of crashes seems to be lower, before it crashed reliably after no
longer than an hour, here's the first and so far only crash after ~2 days of
trying nouveau instead of proprietary.

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2016-04-06  7:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02  0:26 [Bug 79518] New: nouveau causes lockup and reboot on GT215 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-79518-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-06-02  1:36   ` [Bug 79518] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06  7:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2016-04-06 18:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06 18:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06 20:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06 20:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06 20:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06 20:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06 21:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06 21:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:45   ` 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-79518-8800-dxJMmFM7xt@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.