From: Steven Barnhart <sbarn03@softhome.net>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, rol@as2917.net
Subject: Re: [2.5.54 - Oops] CPUFreq [Was: Re: [2.5.54] OOPS: unable to handle kernel paging request]
Date: 05 Jan 2003 12:43:10 -0500 [thread overview]
Message-ID: <1041788597.1136.6.camel@sbarn.net> (raw)
On Sun, 05 Jan 2003 11:47:01 +0000, Steven Barnhart wrote:
> On Sun, 2003-01-05 at 05:43, Paul Rolland wrote:
>> Hello,
>>
>> Good news !
>> Using the patch :
>> http://www.brodo.de/cpufreq/cpufreq-2.5.54-p4-1
>> it is now booting fine !
>
> Excellent!! I will apply immediately. This is great...wonder why it
> hasn't been applied yet.
>
> PS: Andrew: This is the serial console problem, if the patch works for
> me this should fix the problem thank god.
Obivously I spoke to soon...this doesn't fix my problem (maybe because I
don't have a p4 and cpufreq ISN'T enabled). Instead it floods my screen
with the oops now instead of staying their but from hard looking at
it..it's the exact same thing..what an annoying bug!
PS: Paul I've attached my config, any chance you could do a full serial
output on it? Hopefully that would reproduce the problem and shed some
light on it.
--
Steven
sbarn03@softhome.net
GnuPG Fingerprint: 9357 F403 B0A1 E18D 86D5 2230 BB92 6D64 D516 0A94
next reply other threads:[~2003-01-05 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 17:43 Steven Barnhart [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-05 18:00 [2.5.54 - Oops] CPUFreq [Was: Re: [2.5.54] OOPS: unable to handle kernel paging request] Paolo Ciarrocchi
2003-01-03 21:05 [2.5.54] OOPS: unable to handle kernel paging request Steven Barnhart
2003-01-05 9:25 ` [2.5.54 - Oops] CPUFreq [Was: Re: [2.5.54] OOPS: unable to handle kernel paging request] Paul Rolland
2003-01-05 10:43 ` Paul Rolland
2003-01-05 16:47 ` Steven Barnhart
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=1041788597.1136.6.camel@sbarn.net \
--to=sbarn03@softhome.net \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rol@as2917.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