From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 22756] New: nouveau_fence.c kernel BUG and recursive faults
Date: Mon, 13 Jul 2009 14:27:33 -0700 (PDT) [thread overview]
Message-ID: <bug-22756-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=22756
Summary: nouveau_fence.c kernel BUG and recursive faults
Product: xorg
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: pq-X3B1VOXEql0@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=27647)
--> (http://bugs.freedesktop.org/attachment.cgi?id=27647)
Xorg log
Nouveau, KMS enabled and working fine, NV28 card.
DRM modules from nouveau/linux-2.6 git, v2.6.31-rc2-65-g7525cc6, branch
master-compat, commit 7525cc6ddc45772f78aa40fe0a767f512f2ae1ed "Clarify
nouveau/DEPENDS file.". This branch is up-to-date with master branch commit
"drm/nouveau: allow celcius on nv20". The host kernel is 2.6.28-gentoo-r5.
When trying to start X, screen blinks, goes black, kernel hits BUGs, but the
machine does not hang. SysRq can unlock the keyboard, but I do not get the
console back, screen stays black. The kernel recommends a reboot after the
recursive fault.
Attaching X.org log (nothing really interesting), and the kernel log with drm
debug=1, except all debug messages starting in nouveau_hw.h disabled (they
overflow the kernel message buffer and I hear they make I2C/DDC fail).
I'm guessing a way to reproduce this would be to remove e.g. NVxxTCL object
from the list of allowed grobjs, and then starting X. Missing NV11TCL was how I
first hit this kind of bug, but adding that did not fix everything. Probably
something wrong in the nouveau DRM error paths.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2009-07-13 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 21:27 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-22756-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2009-07-13 21:28 ` [Bug 22756] nouveau_fence.c kernel BUG and recursive faults bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-07-16 11:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-07-17 10:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-07-19 15:58 ` 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-22756-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.