From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: Dave Jones <davej@redhat.com>
Cc: Dominik Brodowski <linux@dominikbrodowski.de>, cpufreq@www.linux.org.uk
Subject: Re: oops on resume
Date: Thu, 05 Aug 2004 16:19:30 -0400 [thread overview]
Message-ID: <1091737170.10552.32.camel@pc> (raw)
In-Reply-To: <20040805200857.GA28775@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 717 bytes --]
On Thu, 2004-08-05 at 21:08 +0100, Dave Jones wrote:
> Although that should have
> triggered this message..
>
> if (!fsb)
> printk(KERN_DEBUG "speedstep-lib: couldn't detect FSB speed. Please send an e-mail to <linux@brodo.de>\n");
At KERN_DEBUG though. My /proc/sys/kernel/printk is at:
$ cat /proc/sys/kernel/printk
6 4 1 7
I don't recall how those 4 fields work. Will I get KERN_DEBUG on the
console with those settings?
> Might be useful, though right now, my bets are on an unknown FSB.
Yeah, me too. Any (one have any) idea how to calculate fsb for that
sucker? I may as well throw that code in there too to see if it
alleviates the problem.
b.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq
next prev parent reply other threads:[~2004-08-05 20:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 19:02 oops on resume Brian J. Murrell
2004-08-05 19:26 ` Dominik Brodowski
2004-08-05 19:34 ` Brian J. Murrell
2004-08-05 19:52 ` Dave Jones
2004-08-05 20:02 ` Brian J. Murrell
2004-08-05 20:08 ` Dave Jones
2004-08-05 20:19 ` Brian J. Murrell [this message]
2004-08-05 20:29 ` Dave Jones
2004-08-05 21:03 ` Dominik Brodowski
2004-08-05 21:26 ` Brian J. Murrell
2004-08-05 21:27 ` Dave Jones
2004-08-05 21:29 ` Dave Jones
2004-08-05 21:09 ` Dominik Brodowski
2004-08-05 21:45 ` Brian J. Murrell
2004-08-06 17:14 ` Dominik Brodowski
2004-08-06 17:43 ` Brian J. Murrell
2004-08-06 17:55 ` Dominik Brodowski
2004-08-06 21:13 ` Dave Jones
2004-08-06 21:18 ` Brian J. Murrell
2004-08-06 21:44 ` Dave Jones
2004-08-06 22:10 ` Brian J. Murrell
2004-08-06 22:51 ` Dave Jones
2004-08-06 23:00 ` Brian J. Murrell
2004-08-06 23:23 ` Dave Jones
2004-08-07 13:24 ` Dominik Brodowski
2004-08-07 19:03 ` Brian J. Murrell
2004-08-08 16:24 ` Dominik Brodowski
2004-08-09 13:37 ` Brian J. Murrell
2004-08-09 14:53 ` Dominik Brodowski
2004-08-09 17:27 ` Brian J. Murrell
2004-08-09 19:38 ` Dominik Brodowski
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=1091737170.10552.32.camel@pc \
--to=brian@interlinx.bc.ca \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@redhat.com \
--cc=linux@dominikbrodowski.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