From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 26986] New: TNT2 crashed on startup with 2.6.34-rc1
Date: Tue, 9 Mar 2010 18:57:28 -0800 (PST) [thread overview]
Message-ID: <bug-26986-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=26986
Summary: TNT2 crashed on startup with 2.6.34-rc1
Product: xorg
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: randrik-JGs/UdohzUI@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Well, i have nouveau_vieux_dri.so in my system.
But thing is ... exactly this setup works with 2.6.32-based nouveau kernel
tree.
Trees used:
mesa: commit e5923a1240d8b32f5af080b0b4191d3b9299a630 (Merge branch '7.8')
drm: commit 04fd3872ee8bd8d5e2c27740508c67c2d51dbc11 (nouveau: Small lighting
related addition to nouveau_class.h.)
kernel (good): commit 4b52473c354f7238afe0c78f50a6c84c40aa3478 ( drm/nv50: add
a memory barrier to pushbuf submission)
kernel (bad): commit 57d54889cd00db2752994b389ba714138652e60c ( Linux
2.6.34-rc1)
xf86-video-nouveau: commit 29647021044463768cbfa3eead1416ef1cf27fa1 ( remove
drm patchlevel check, libdrm checks this for us )
xserver: commit db4f676f25c6d8e58263d5151942be730592d444 ( xselinux: Bump
extension minor version.)
usual logs follow ....
--
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:[~2010-03-10 2:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 2:57 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-26986-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-03-10 2:58 ` [Bug 26986] TNT2 crashed on startup with 2.6.34-rc1 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-03-10 3:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-03-10 3:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-03-10 3:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-03-10 3:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-03-10 5:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-03-10 18:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-12 6:41 ` 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-26986-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.