public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Won <phlegm@home.com>
To: "Arnaud S . Launay" <asl@launay.org>
Cc: Gregory Maxwell <greg@linuxpower.cx>, linux-kernel@vger.kernel.org
Subject: Re: Newby help. Tons and tons of Oops
Date: Thu, 16 Nov 2000 02:42:44 -0500	[thread overview]
Message-ID: <00111602424400.00817@phlegmish.com> (raw)
In-Reply-To: <00111214191100.01043@phlegmish.com> <00111307592400.01166@phlegmish.com> <20001113162205.A30602@profile4u.com>
In-Reply-To: <20001113162205.A30602@profile4u.com>

I just noticed these errors in my log as well. Something is weird with my 
swapping I think. If I get Oops that say "Unable to handle kernel paging 
request at virtual address ff7f1014" would that not be swap since it is 
virtual? 
The errors that make me think it may be with my swapper are as follows.

Nov 12 21:12:51 phlegmish kernel: swap_free: Trying to free nonexistent 
swap-page
Nov 12 21:12:51 phlegmish kernel: swap_free: Trying to free nonexistent 
swap-page
Nov 14 02:57:28 phlegmish rc.sysinit: Enabling swap space:  succeeded 
Nov 14 03:01:51 phlegmish kernel: swap_free: offset exceeds max
Nov 14 03:01:51 phlegmish kernel: swap_free: offset exceeds max
Nov 14 03:17:37 phlegmish kernel: swap_free: Trying to free nonexistent 
swap-page
Nov 14 03:17:37 phlegmish kernel: swap_free: Trying to free nonexistent 
swap-page


And so on......
I tried deleting my swap partiton and recreating it but that made no 
difference.  Any ideas or things to try?

Thanks for the help so far
Dave



On Monday 13 November 2000 10:22, Arnaud S . Launay wrote:
> Le Mon, Nov 13, 2000 at 07:59:24AM -0500, David Won a écrit:
> > I'm running 2.4.0test11pre3. but the kernel shipped with Redhat 7 doesn't
> > work either. When I was running 2.2.15 and RedHat 6.2 before upgrading it
> > worked great. Never had an oops ever.
> > I ran a memory checker under dos as well and it didn't find anything. Any
> > tips?
>
> Could you please check:
> 1/ if memtest really worked, as I had problems with 2.4 (in fact, it wasn't
> launched, I had to downgrade to 2.3 for having a test) (have you seen a
> scrolling bar of '#' ?) (anyway, i'm sending 2.3 binary privatly)
> 2/ your hardware internal temperature (put your hand into the box)
> 3/ if every cable is correctly plugged in
>
> It looks to me like an hardware failure, not a software one.
>
> 	Arnaud.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> 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
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-11-16  8:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-12 19:19 Newby help. Tons and tons of Oops David Won
     [not found] ` <20001112171230.B32489@xi.linuxpower.cx>
2000-11-13 12:59   ` David Won
2000-11-13 15:22     ` Arnaud S . Launay
2000-11-14 15:23       ` David Won
2000-11-16  7:42       ` David Won [this message]
2000-11-16  7:56       ` David Won

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=00111602424400.00817@phlegmish.com \
    --to=phlegm@home.com \
    --cc=asl@launay.org \
    --cc=greg@linuxpower.cx \
    --cc=linux-kernel@vger.kernel.org \
    /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