From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 87819] New: [NVAC] EQ overflowing
Date: Mon, 29 Dec 2014 05:52:54 +0000 [thread overview]
Message-ID: <bug-87819-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1814 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=87819
Bug ID: 87819
Summary: [NVAC] EQ overflowing
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: eurbah-GANU6spQydw@public.gmane.org
Created attachment 111450
--> https://bugs.freedesktop.org/attachment.cgi?id=111450&action=edit
Xorg.0.log for X freeze with nouveau from linux-3.19.0-rc2
Normally, I am using Ubuntu utopic (14.10), where module 'nouveau'
systematically crashes after a few minutes, whereas module nvidia from
nvidia-331-updates crashes only after several hours of work.
So, I have filed https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396840
Inside this Ubuntu bug, Christopher M. Penalver (penalvch) asked me to ensure
the issue is reproducible with the latest mainline kernel.
Currently, this latest mainline kernel is 'linux-3.19.0-rc2'.
With Cinnamon and Firefox, this kernel quickly froze with 'Xorg.0.log'
complaining 'EQ overflowing'.
Inside 'Xorg.0.log', I found :
- Module nouveau: vendor="X.Org Foundation" compiled for 1.16.0, module
version = 1.0.11
- 'AIGLX: enabled GLX_MESA_copy_sub_buffer'.
So I guess that the 'nouveau' module embedded in 'linux-3.19.0-rc2' is a 3D
driver from the 'Mesa' product (but I am NOT completely sure).
Anyway, I a trying to attach here :
- Xorg.0.log,
- kern.log, restricted to 'linux-3.19.0-rc2', with 'Loglevel set to 1' and
'SysRq : Show State'.
I hope that these log files will be useful.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3260 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:[~2014-12-29 5:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 5:52 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-87819-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-12-29 5:56 ` [Bug 87819] [NVAC] EQ overflowing bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-29 6:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-02 13:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-12 12:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-04 8:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-04 8:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-04 12:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-04 12:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-04 12:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-04 15:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-04 17:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-12 10:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-14 10:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-14 12:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-14 18:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-15 0:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-15 1:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-19 6:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-19 6:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-19 8:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-19 9:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-19 9:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-17 21:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-18 20:52 ` 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-87819-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.