From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 79518] New: nouveau causes lockup and reboot on GT215
Date: Mon, 02 Jun 2014 00:26:29 +0000 [thread overview]
Message-ID: <bug-79518-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1111 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=79518
Priority: medium
Bug ID: 79518
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: nouveau causes lockup and reboot on GT215
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: kilobyte-b9QjgO8OEXPVItvQsEIGlw@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: 7.7 (2011)
Component: Driver/nouveau
Product: xorg
Created attachment 100258
--> https://bugs.freedesktop.org/attachment.cgi?id=100258&action=edit
kernel log via a serial console
On my system, with nvidia GT215/240, nouveau causes random crashes on the order
of 1 hour. Typically, there's a lockup followed by a reboot a few seconds
later. With the proprietary driver, the system is stable. The crash happens
on both old and new kernels, up to 3.15-rc.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2550 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2014-06-02 0:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 0:26 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-79518-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-06-02 1:36 ` [Bug 79518] nouveau causes lockup and reboot on GT215 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06 7:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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@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.