public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Barnhart <sbarn03@softhome.net>
To: Paul Rolland <rol@as2917.net>
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@transmeta.com>,
	Andrew Morton <akpm@digeo.com>
Subject: Re: [2.5.54 - Oops] CPUFreq [Was: Re: [2.5.54] OOPS: unable to handle kernel paging request]
Date: 05 Jan 2003 11:47:01 -0500	[thread overview]
Message-ID: <1041785228.10728.6.camel@sbarn.net> (raw)
In-Reply-To: <012601c2b4a7$55ce8090$2101a8c0@witbe>

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.
> 1 [11:40] rol@donald:~> cat /proc/cpufreq 
>           minimum CPU frequency  -  maximum CPU frequency  -  policy
> CPU  0       302902 kHz ( 12 %)  -    2423222 kHz (100 %)  -
> performance
> 
> Cool...
> 
> Paul Rolland, rol@as2917.net
> 
> > -----Original Message-----
> > From: linux-kernel-owner@vger.kernel.org 
> > [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Paul Rolland
> > Sent: Sunday, January 05, 2003 10:26 AM
> > To: 'Steven Barnhart'; 'Mark Hahn'
> > Cc: linux-kernel@vger.kernel.org
> > Subject: [2.5.54 - Oops] CPUFreq [Was: Re: [2.5.54] OOPS: 
> > unable to handle kernel paging request]
> > 
> > 
> > Hello,
> > 
> > I've got it running my serial console. Full trace at boot time is :
> > SBF: Simple Boot Flag extension found and enabled.
> > SBF: Setting boot flags 0x1
> > cpufreq: P4/Xeon(TM) CPU On-Demand Clock Modulation available 
> > divide error: 0000
> > CPU:    0
> > EIP:    0060:[<c01151bb>]    Not tainted
> > EFLAGS: 00010246
> > Unable to handle kernel paging request at virtual address 
> > ffffff8d  printing eip: c012ebcf *pde = 00001067 *pte = 00000000
> > Oops: 0002
> > CPU:    0
> > EIP:    0060:[<c012ebcf>]    Not tainted
> > EFLAGS: 00010006
> > 
> > and ksymoops says :
> > 8 [10:21] rol@donald:~> ksymoops -v /usr/src/linux/vmlinux -K 
> > -m /boot/System.map-2.5.54 <oops-cpufreq2 ksymoops 2.4.8 on 
> > i686 2.4.20.  Options used
> >      -v /usr/src/linux/vmlinux (specified)
> >      -K (specified)
> >      -l /proc/modules (default)
> >      -o /lib/modules/2.4.20/ (default)
> >      -m /boot/System.map-2.5.54 (specified)
> > 
> > No modules in ksyms, skipping objects
> > No ksyms, skipping lsmod
> > CPU:    0
> > EIP:    0060:[<c01151bb>]    Not tainted
> > Using defaults from ksymoops -t elf32-i386 -a i386
> > EFLAGS: 00010246
> > Unable to handle kernel paging request at virtual address 
> > ffffff8d c012ebcf *pde = 00001067
> > Oops: 0002
> > CPU:    0
> > EIP:    0060:[<c012ebcf>]    Not tainted
> > EFLAGS: 00010006
> > Warning (Oops_read): Code line not seen, dumping what data is 
> > available
> > 
> > 
> > >>EIP; c01151bb <time_cpufreq_notifier+14f/208>   <=====
> > >>EIP; c012ebcf <kallsyms_lookup+df/194>   <=====
> > 
> > 
> > 1 warning issued.  Results may not be reliable.
> > 
> > Problem is that ksymoops seems to decode the paging request 
> > fault, not the 0 divide error...
> > 
> > This comes from a plain 2.5.54 kernel, no patches applied.
> > 
> > Dominik, you told me last week, with 2.5.53, that a patch was 
> > to be used. 
> > Is it included in 2.5.54 ?
> > If not, forget this mail... just tell me, I'll apply the 
> > patch and I'll tell you if it's better.
> > 
> > Regards,
> > Paul
> > 
> > 
> > > -----Original Message-----
> > > From: linux-kernel-owner@vger.kernel.org
> > > [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of 
> > > Steven Barnhart
> > > Sent: Friday, January 03, 2003 10:06 PM
> > > To: Mark Hahn
> > > Cc: linux-kernel@vger.kernel.org
> > > Subject: Re: [2.5.54] OOPS: unable to handle kernel paging request
> > > 
> > > 
> > > On Fri, 2003-01-03 at 10:48, Mark Hahn wrote:
> > > > it's not very meaningful: some part of the kernel tried
> > > dereferencing
> > > > a null pointer (as it happens, with a negative offset, such as you
> > > > might expect from a variable sitting in the stack). the 
> > > negativeness
> > > > is not surprising, and the value of the offset would 
> > depend on your
> > > > cpu/compiler/config.
> > > 
> > > Well I have a Intel Celeron 1.06 GHz (i686). 384MB ram, gcc
> > > 3.2 (redhat 8 release). I don't really know how to decode it 
> > > since I have no serial console hookups...anything paticualr I 
> > > could get from the oops report during bootup? i.e. what 
> > > sections to copy?
> > > 
> > > --
> > > Steven
> > > sbarn03@softhome.net
> > > GnuPG Fingerprint: 9357 F403 B0A1 E18D 86D5  2230 BB92 6D64 
> > D516 0A94
> > > 
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe
> > > linux-kernel" in the body of a message to 
> > > majordomo@vger.kernel.org More majordomo info at  
> > http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> > 
> > -
> > To unsubscribe from this list: send the line "unsubscribe 
> > linux-kernel" in the body of a message to 
> > majordomo@vger.kernel.org More majordomo info at  
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
-- 
Steven
sbarn03@softhome.net
GnuPG Fingerprint: 9357 F403 B0A1 E18D 86D5  2230 BB92 6D64 D516 0A94


  reply	other threads:[~2003-01-05 16:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0301031046100.25684-100000@coffee.psychology.mcmaster.ca>
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 [this message]
2003-01-05 17:43 Steven Barnhart
  -- strict thread matches above, loose matches on Subject: below --
2003-01-05 18:00 Paolo Ciarrocchi

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=1041785228.10728.6.camel@sbarn.net \
    --to=sbarn03@softhome.net \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rol@as2917.net \
    --cc=torvalds@transmeta.com \
    /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