From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 38050] New: segfault starting glxgears
Date: Tue, 7 Jun 2011 13:15:47 -0700 (PDT) [thread overview]
Message-ID: <bug-38050-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=38050
Summary: segfault starting glxgears
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: freedesktop-UCmSlPBN2tkLqRSKpNnsEbNAH6kLmebB@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
using:
- xf86-video-nouveau git
- libdrm git
- mesa-7.10.2
- xorg-drivers-1.9
- xorg-server-1.9.5
with:
gfx-card V7700 -> see attachement
crashes with modeset=1 and noaccel=1,
as with modeset=1 only.
- KDE log in works
- starting Konsole works
- calling glxgears segfaults
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-06-07 20:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 20:15 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-38050-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-06-07 20:20 ` [Bug 38050] segfault starting glxgears bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-07 20:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-07 20:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-08 13:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-08 21:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-08 21:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-08 21:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-08 21: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-38050-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.