From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26635] New: [drm-radeon-testing] warning message that can't be true
Date: Thu, 18 Feb 2010 11:56:30 -0800 (PST) [thread overview]
Message-ID: <bug-26635-502@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=26635
Summary: [drm-radeon-testing] warning message that can't be true
Product: DRI
Version: DRI CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: liquid.acid@gmx.net
CC: jb.faq@gmx.de
Created an attachment (id=33396)
--> (http://bugs.freedesktop.org/attachment.cgi?id=33396)
dmesg output
Hi there,
just pulled latest drm-radeon-testing and updated xf86-video-ati, libdrm and
mesa to git master.
Now I get this in the kernel log:
You have old & broken userspace please consider updating mesa
(full log attached)
Well this can't be true, since userspace is brand new...
Hardware:
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon HD 4770 [RV740]
Greets,
Tobias
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next reply other threads:[~2010-02-18 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 19:56 bugzilla-daemon [this message]
2010-03-18 15:17 ` [Bug 26635] [drm-radeon-testing] warning message that can't be true bugzilla-daemon
2010-10-16 0:03 ` bugzilla-daemon
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-26635-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox