public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joshua Kwan <joshk@triplehelix.org>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: con@kolivas.org
Subject: Weirdness with 2.4.20-ck4
Date: Sun, 16 Mar 2003 12:11:24 -0800	[thread overview]
Message-ID: <20030316201124.GA2849@triplehelix.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]

So I tried out 2.4.20-ck4 on my server box, which continually leans
towards the experimental because, well, it seems to work fine.

For 13 days, everything was peachy. Then on the 14th morning I wake
up and dhcp3-server is not responding timely, since my laptop
is unable to acquire an IP address automatically. I serial in and 
init has gone D and is eating 99.8% of the CPU.

Every single process under init was DEFUNCT!

New processes also were defunct as well, after being started. I guess
bash was somehow not affected when I logged in.

I can't provide a dmesg, since the machine eventually stopped responding
and I had to hard reboot it. But unless I know for sure what's going on
soon, I'll need to move back to a vanilla kernel or perhaps try out
2.4.20aa, without the rest of the 'desktop' tuning stuff that I don't
really make use of.

Sorry I can't give much info, except possibly my .config. You can get it
at http://triplehelix.org/~joshk/linux/config.gz. If this happens again
I'll be sure to get some pstree output logged somewhere. (Would slabinfo
be useful too in this kind of situation?)

Regards
Josh

-- 
New PGP public key: 0x27AFC3EE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-03-16 20:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-16 20:11 Joshua Kwan [this message]
2003-03-17  4:09 ` Weirdness with 2.4.20-ck4 Con Kolivas
2003-03-17  4:15   ` Joshua Kwan
2003-03-17  6:32     ` Con Kolivas

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=20030316201124.GA2849@triplehelix.org \
    --to=joshk@triplehelix.org \
    --cc=con@kolivas.org \
    --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