mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "오늘과내일 홍석범" <antihong@tt.co.kr>
To: <linux-kernel@vger.kernel.org>
Subject: Some problems in kernel 2.4.3
Date: Tue, 24 Apr 2001 22:36:43 +0900	[thread overview]
Message-ID: <00b601c0ccc3$9a7dd240$2e402fd3@tt.co.kr> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="ks_c_5601-1987", Size: 1802 bytes --]

Hello.. All..

I upgraded the linux servers' kernel verison from 2.2.16 to 2.4.3 .
when my linux kernel version was 2.2.16, there is no problem to work. 
but After upgrading, some critical problem is occured.
Surely, kernel compile option and method has no problem.
(H/W spec is P3 733 Dual, 512M RAM and  SCSI)

(1) some  process is not killed 
I built kernel 2.4.3 in my linux server which works in php+mysql.
But after a few days, I found that my mysql daemon was not work.
(But mysql process is seen)
So I typed like this to kill the mysql process.

kill -9 pid or 
killall -9 -ev mysqld
/usr/local/mysql/bin/mysql.server stop
...... etc....

But I can't kill mysql process with any command.
So I reboot the system.
(Unfortunately,  this phenomenon is occured very often and 
 occured other linux servers that kernel is 2.4.3...)
Of cource, mysql process is just a sample
and other process(proftpd, sendmail, etc...) 
is not killed either.


(2) Anyone (even root) can't access some directory.
A few days ago, I moved the special user's directory and typed "ls -la" to see the 
directory structure. but that command was not work and the process is stopped.
--- keyboard is not work too.
(the process is not dead even would kill the process as root)
so other processes to access the directory were seen in the "ps aux" command.
and the load average is so high(about 100)  even all processes are killed 
except those undead processes.  
and the load average can't down any more before reboot the system.
 
I think that these two problems are bug in the 2.4.3 .



Please give me some advice about these problems.

Thanks for your help.
 
 
ý:.žË›±Êâmçë¢kaŠÉb²ßìzwm…ébïîžË›±Êâmébžìÿ‘êçz_âžØ^n‡r¡ö¦zË\x1aëh™¨è­Ú&£ûàz¿äz¹Þ—ú+€Ê+zf£¢·hšˆ§~†­†Ûiÿÿïêÿ‘êçz_è®\x0fæj:+v‰¨þ)ߣømšSåy«\x1e­æ¶\x17…\x01\x06­†ÛiÿÿðÃ\x0fí»\x1fè®\x0få’i\x7f

             reply	other threads:[~2001-04-24 13:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24 13:36 오늘과내일 홍석범 [this message]
2001-04-24 13:45 ` Mohammad A. Haque

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='00b601c0ccc3$9a7dd240$2e402fd3@tt.co.kr' \
    --to=antihong@tt.co.kr \
    --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®