cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: Tim Weippert <weiti@security.tds.de>
Cc: akpm@osdl.org, cpufreq@lists.linux.org.uk, discuss@x86-64.org,
	linux-kernel@vger.kernel.org, davej@codemonkey.org.uk
Subject: Re: Bad page state on AMD Opteron Dual System with kernel 2.6.13-rc6-git13
Date: Mon, 29 Aug 2005 11:49:16 +0100	[thread overview]
Message-ID: <4312E82C.9090908@gentoo.org> (raw)
In-Reply-To: <20050829052454.GA8172@pbkg4>

Tim Weippert wrote:
> As this is an Server, i don't even use cpufreq on this machine. So it
> think this isn't the same problem ...

Maybe you could post your experiences here:

	http://bugzilla.kernel.org/show_bug.cgi?id=5133

Daniel

      parent reply	other threads:[~2005-08-29 10:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050826165342.GA11796@pbkg4>
2005-08-28  0:20 ` Bad page state on AMD Opteron Dual System with kernel 2.6.13-rc6-git13 Daniel Drake
2005-08-29  5:24   ` Tim Weippert
2005-08-29 10:28     ` Tim Weippert
2005-08-29 10:49     ` Daniel Drake [this message]

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=4312E82C.9090908@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=akpm@osdl.org \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=weiti@security.tds.de \
    /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