From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 69952] [NVAA] Xorg crash+restart after glxgears on 3.12-rc2
Date: Fri, 22 Nov 2013 11:10:36 +0000 [thread overview]
Message-ID: <bug-69952-8800-tsg4pZSSv6@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-69952-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 985 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69952
--- Comment #3 from dirkneukirchen-S0/GAf8tV78@public.gmane.org ---
I enabled posting via kernel cmdline.
cat /proc/cmdline:
BOOT_IMAGE=/vmlinuz-3.12.0 root=UUID=c52e229d-be9c-4d85-b262-5085459dc2d9 ro
rootflags=subvol=@ sysrq_always_enabled ignore_loglevel debug log_buf_len=5M
nouveau.config=NvMSI=0 nouveau.config=NvForcePost=1 sysrq_always_enabled
The crash still occurs:
- LXDE running glxgears
- XFCE running glxgears
Running on KDE : running glxgears "freezes" / makes the Desktop very slow but
it does not crash Xorg there.
System:
-Linux Mint 15 (Ubuntu 13.04)
-NVAA (Geforce 8200) onboard (Jetway JNC62K)
-dual monitor setup (HDMI+VGA)
-Kernel 3.12.0
Steps to replicate this time:
- Login to desktop (XFCE, dual screen)
- in open terminal window : run glxgears
- switch to other virtual desktop
- Xorg hangs, crash (login screen reappers)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1740 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:[~2013-11-22 11:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 9:47 [Bug 69952] New: [NVAA] Xorg crash+restart after glxgears on 3.12-rc2 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-69952-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-10-15 17:04 ` [Bug 69952] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-18 16:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-22 11:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2013-11-22 11:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-06 22:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-19 10:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:37 ` 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-69952-8800-tsg4pZSSv6@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.