From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 88893] New: [NV46] GPU lockup with Quadro NVS 110M
Date: Sun, 01 Feb 2015 02:56:48 +0000 [thread overview]
Message-ID: <bug-88893-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1011 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=88893
Bug ID: 88893
Summary: [NV46] GPU lockup with Quadro NVS 110M
Product: xorg
Version: 7.7 (2012.06)
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: hobbes1069-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
System Info:
Dell Latitude D620
Nvidia Quadro NVS 110M
Fedora 21 x86_64
With initial system install with 1.0.9 I could get a usable system with
nouveau.noaccel=1.
After an update which included 1.0.11 I would get the GPU lockup regardless of
the kernel parameter. I also tried current git with the same result.
libdrm is current 2.4.58.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2215 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2015-02-01 2:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 2:56 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-88893-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-02-01 14:01 ` [Bug 88893] [NV46] GPU lockup with Quadro NVS 110M bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-01 14:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-01 14:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-01 14:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-01 14:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-01 14:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-01 14:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-01 14:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-01 15:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-01 17:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-01 17:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-01 19:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-03 2:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-11 3:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-21 13:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-21 13:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-21 13:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-23 13:13 ` 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-88893-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.