From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 15245] [2.6.33-rc6 fc76be4 w/ drm-radon-testing and KMS enabled] Weird JCPU times?
Date: Fri, 12 Feb 2010 18:18:42 GMT [thread overview]
Message-ID: <201002121818.o1CIIgul018633@demeter.kernel.org> (raw)
In-Reply-To: <bug-15245-2300@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=15245
--- Comment #3 from Shawn Starr <shawn.starr@rogers.com> 2010-02-12 18:18:28 ---
I can confirm this is not due to Radeon as im using the intel GPU and see
spstarr 6085 7696761 0.0 18992 2024 pts/6 Ss 12:57 21114581:29 /bin/bash
spstarr 6092 152211946 0.0 18936 1364 pts/6 S+ 12:58 21114581:29 top
It seems to be a real kernel regression.
As of 2.6.33-rc7 last night's linus's tree still.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
next prev parent reply other threads:[~2010-02-12 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15245-2300@http.bugzilla.kernel.org/>
2010-02-07 9:11 ` [Bug 15245] [2.6.33-rc6 fc76be4 w/ drm-radon-testing and KMS enabled] Weird JCPU times? bugzilla-daemon
2010-02-07 20:04 ` bugzilla-daemon
2010-02-11 14:01 ` bugzilla-daemon
2010-02-12 18:18 ` bugzilla-daemon [this message]
2010-02-12 18:21 ` bugzilla-daemon
2010-02-12 23:52 ` [Bug 15245] [2.6.33-rc6 " bugzilla-daemon
2010-02-07 22:16 2.6.33-rc7: Reported regressions from 2.6.32 Rafael J. Wysocki
2010-02-07 22:28 ` [Bug #15245] [2.6.33-rc6 fc76be4 w/ drm-radon-testing and KMS enabled] Weird JCPU times? Rafael J. Wysocki
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=201002121818.o1CIIgul018633@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.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 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.