From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 85086] [NVE7] read/write faults leave machine unsuable
Date: Thu, 16 Oct 2014 16:09:39 +0000 [thread overview]
Message-ID: <bug-85086-8800-dTfclcbWN9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-85086-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1393 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=85086
Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|read/write faults leave |[NVE7] read/write faults
|machine unsuable |leave machine unsuable
--- Comment #4 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
In an effort to reduce irrelevant information, you've cut out potentially
relevant things. Best to attach unredacted logs...
(a) Is this an optimus setup? If so, can you try booting with nouveau.runpm=0
[this will cause the nvidia card not to auto-suspend when not used]
(b) Please attach a full kernel log, from boot until the errors.
It would appear that the errors are brought on by a channel hang, from which
nouveau recovers in a... less-than-graceful fashion. This is, generally, a
known "issue" (more like 100 inter-related issues). However perhaps you can
update your userspace (specifically mesa), and whatever issue causes the hang
has been fixed in 10.3.1. Upgrading the ddx to 1.0.11 wouldn't hurt either.
As Tobias suggested, if you can identify an action that causes the issue, that
would be extremely helpful.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2611 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 prev parent reply other threads:[~2014-10-16 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 11:45 [Bug 85086] New: read/write faults leave machine unsuable bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-85086-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-10-16 11:46 ` [Bug 85086] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-16 11:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-16 11:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-16 15:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-16 16:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-10-16 18:09 ` [Bug 85086] [NVE7] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-16 18:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:50 ` 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-85086-8800-dTfclcbWN9@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.