mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jim Gifford" <maillist@jg555.com>
To: "Andrew Morton" <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kswapd 2.4.2? ext3
Date: Sun, 22 Jun 2003 11:01:27 -0700	[thread overview]
Message-ID: <07cf01c338e8$4f12b4e0$3400a8c0@W2RZ8L4S02> (raw)
In-Reply-To: <20030621200617.648c5ec2.akpm@digeo.com>

I get the same problem, but I never get a oops, because the system is
completely locked up. The wierd part about this is that if I leave a command
prompt open, I can type in a command, but it never gets executed. I even
tried to use the sysrq to get information and that doesn't even work,
because syslog is dead. Here is my system information. After about 20 hours
uptime server locks up.

Dell Poweredge 4200
2 - Pentium II - 333mhz
1 GIG ECC EDO RAM
Dell Perc2(Megaraid Controller) - Setup as WriteThru and DirectIO
Adaptec Duo Network Adapter

Using kernel 2.4.21 with the latest 1.18i driver from LSILogic for the
Megaraid, no other patches, built from source code only

I am a Linux From Scratch  user, I have used the same config file since
kernel 2.4.17 with no problems, problems first appeared in kernel 2.4.20. I
have had the  system checked, the memory tested, and changed raid
controllers. I have even checked cron events at the time it locks up

If you have a patch you would like me to test send it and I can report back
in 24 hours. I do have the capability of hooking up a laptop to the serial
port of the computer to collect statistics.

----- Original Message ----- 
From: "Andrew Morton" <akpm@digeo.com>
To: <john@beyondhelp.co.nz>
Cc: <linux-kernel@vger.kernel.org>
Sent: Saturday, June 21, 2003 8:06 PM
Subject: Re: kswapd 2.4.2? ext3


> John Duthie <john@beyondhelp.co.nz> wrote:
> >
> >
> > I don't think kswap should be doing this ....
> >
> >     4 ?        Z      0:14 [kswapd] <defunct>
>
> That means kswapd oopsed and then exitted.  It should be in the logs
> somewhere.
>
> -
> 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/
>


  reply	other threads:[~2003-06-22 17:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-21 23:55 John Duthie
2003-06-22  0:31 ` Jeff
2003-06-22 17:47   ` Jeff
2003-06-22  3:06 ` Andrew Morton
2003-06-22 18:01   ` Jim Gifford [this message]
2003-06-22 22:29   ` John Duthie
2003-06-22 22:52     ` Andrew Morton
2003-06-23 10:16 ` Torsten Wolf
2003-06-25  1:38   ` Jim Gifford

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='07cf01c338e8$4f12b4e0$3400a8c0@W2RZ8L4S02' \
    --to=maillist@jg555.com \
    --cc=akpm@digeo.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

all inboxes | Powered by JetHome®