linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tabris <tabris@tabris.net>
To: Boylenate316@aol.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS: Something about kswapd
Date: Mon, 3 Nov 2003 16:06:10 -0500	[thread overview]
Message-ID: <200311031606.11916.tabris@tabris.net> (raw)
In-Reply-To: <59D81E86.2137402F.11E481F9@aol.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

well, I can't say I know for sure, but there is a good chance you may have 
bad RAM. consider running memtest86 on it thru a couple passes.
I had a similar problem lately with kscand and kswapd

and it seems I had two single bit errors in one of my DIMMs

you can get memtest86 from http://www.memtest86.org

HTH

On Monday 03 November 2003 3:19 pm, Boylenate316@aol.com wrote:
> I'm not on the list.
> Kernel: 2.4.22, no patches
> CPU: AMD Athlon XP
> Memory: 512MB
> Swap: 1GB
> OOPS during ROCK linux compilation, I don't know which package...
> It didn't hang, but kswapd is defunct as I type.
> ksymoops output:
> ksymoops 2.3.7 on i686 2.4.22.  Options used
>      -v /usr/src/linux-2.4.22/vmlinux (specified)
>      -k /proc/ksyms (default)
>      -l /proc/modules (default)
>      -o /lib/modules/2.4.22/ (default)
>      -m /usr/src/linux-2.4.22/System.map (specified)
>
> Warning (compare_maps): mismatch on symbol tulip_max_interrupt_work  ,
> tulip says e0bf4a2c,
> /lib/modules/2.4.22/kernel/drivers/net/tulip/tulip.o says e0bf422c. 
> Ignoring /lib/modules/2.4.22/kernel/drivers/net/tulip/tulip.o entry
> Warning (compare_maps): mismatch on symbol tulip_rx_copybreak  , tulip
> says e0bf4a30, /lib/modules/2.4.22/kernel/drivers/net/tulip/tulip.o
> says e0bf4230.  Ignoring
> /lib/modules/2.4.22/kernel/drivers/net/tulip/tulip.o entry Warning
> (compare_maps): mismatch on symbol usb_devfs_handle  , usbcore says
> e0ba40d0, /lib/modules/2.4.22/kernel/drivers/usb/usbcore.o says
> e0ba3b50.  Ignoring /lib/modules/2.4.22/kernel/drivers/usb/usbcore.o
> entry unable to handle kernel NULL pointer dereference at virtual
> address 0000001c *pde = 00000000
> Oops: 0000
> CPU:    0
> EIP:    0010:[<c0138e64>]    Not tainted
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010282
> eax: 00000000   ebx: c1435d5c   ecx: c1435d78   edx: cfa9a2c0
> esi: 000001d0   edi: 00002d82   ebp: c02d9eb0   esp: c1599f44
> ds: 0018   es: 0018   ss: 0018
> Process kswapd (pid: 4, stackpage=c1599000)
> Stack: 000001d0 c1435d5c c012f948 c1435d5c 000001d0 c1598000 00000200
> 000001d0
>        00000014 00000020 000001d0 00000020 00000006 c012fb30 00000006
> 0000000a
>        c02d9eb0 00000006 000001d0 c02d9eb0 00000000 c012fb90 00000020
> c02d9eb0
- --
tabris
- -
Predestination was doomed from the start.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/psNC1U5ZaPMbKQcRApNAAJwKaUcDSlSsfL1Ho3KWcgC5nMOiegCeNYjz
0fP9gW4+rf4Fdf1EPue6N98=
=ze2g
-----END PGP SIGNATURE-----


      reply	other threads:[~2003-11-03 21:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03 20:19 OOPS: Something about kswapd Boylenate316
2003-11-03 21:06 ` tabris [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=200311031606.11916.tabris@tabris.net \
    --to=tabris@tabris.net \
    --cc=Boylenate316@aol.com \
    --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;
as well as URLs for NNTP newsgroup(s).