From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 9729] ondemand cpufreq governor doesn't see when kcryptd/dm-crypt is busy
Date: Wed, 16 Jan 2008 02:08:02 -0800 (PST) [thread overview]
Message-ID: <20080116100802.86ABD108069@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-9729-3570@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=9729
tch@wpkg.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |REJECTED
Resolution| |UNREPRODUCIBLE
------- Comment #1 from tch@wpkg.org 2008-01-16 02:08 -------
After a reboot, I can't reproduce it anymore.
Previously, it was reproducible almost always.
Strange, but that's good, isn't it?
Will reopen if it happens again.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-01-16 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 12:29 [Bug 9729] New: ondemand cpufreq governor doesn't see when kcryptd/dm-crypt is busy bugme-daemon
2008-01-16 10:08 ` bugme-daemon [this message]
2008-01-18 13:57 ` [Bug 9729] " bugme-daemon
2008-01-18 22:42 ` bugme-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=20080116100802.86ABD108069@picon.linux-foundation.org \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=cpufreq@www.linux.org.uk \
/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