From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 99968] New: [NV4C] System crashes reliably with glxinfo
Date: Sun, 26 Feb 2017 01:16:06 +0000 [thread overview]
Message-ID: <bug-99968-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2416 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99968
Bug ID: 99968
Summary: [NV4C] System crashes reliably with glxinfo
Product: Mesa
Version: 12.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: dmo2118-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
CC: laurent.riffard+freedesktop-GANU6spQydw@public.gmane.org,
nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Depends on: 91992
Created attachment 129920
--> https://bugs.freedesktop.org/attachment.cgi?id=129920&action=edit
Example display corruption
+++ This bug was initially created as a clone of Bug #91992 +++
Hardware is NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) on an
old Dell Inspiron 531. Integrated graphics.
The system boots OK (with high-resolution console) into X11. I can log in to a
Lubuntu desktop (2D, no OpenGL, AFAIK). Then, from a terminal window I run:
$ while true; do nice -n19 glxinfo > /dev/null; done
Then I drag the window around for a few seconds. Then the entire system
crashes: total system lockup, followed by display corruption a second or two
later. (I've attached a photograph, because I can't take a normal screen shot.)
No Ctrl-Alt-F1, no magic SysRq, no ping response.
Other OpenGL apps (i.e. glxgears) can run...sometimes. Other times, they crash
the same way. It seems to happen on GL init.
Ubuntu 16.10 (with Lubuntu Desktop)
Linux kernel 4.10.0 (freshly compiled)
libdrm 2.4.70-1 (from distro)
Mesa 12.0.3-1ubuntu2 (from distro)
xf86-video-nouveau 1:1.0.12-2 (from distro)
This seems a lot like bug 91992, but I've got my video memory cranked up to 256
MB in the BIOS settings, and it still happens.
Referenced Bugs:
https://bugs.freedesktop.org/show_bug.cgi?id=91992
[Bug 91992] [NV4C] computer hangs after few minutes of use
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4685 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2017-02-26 1:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 1:16 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-99968-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-02-26 1:17 ` [Bug 99968] [NV4C] System crashes reliably with glxinfo bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-26 1:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-26 1:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-02-22 11:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-03-04 4:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20: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-99968-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.