From: Justin Guyett <justin@soze.net>
To: linux-kernel@vger.kernel.org
Subject: dead processes in 2.4.7-10smp and 2.4.19-rc1 (percraid problem?)
Date: Sat, 6 Jul 2002 20:02:14 +0000 [thread overview]
Message-ID: <20020706200214.GB12813@dreams.soze.net> (raw)
An smp + percraid machine that was running fine with 2.2 kernels was
recently reinstalled (rh 7.2). Now a variety of processes like cp,
mv, chmod, mail, and even a simply constructed program[1] (just
created to verify there wasn't something broken with the other
programs) occassionally (probably 20% of the time or less) stick
around indefinately as a pair[2] of process entries. This happens
with all combinations I've tried:
2.4.7-10smp (rpm) + glibc-2.2.4-24 (rpm)
2.4.19-rc1 + glibc 2.2.4-24 (rpm)
2.4.19-rc1 + glibc 2.2.5
Additionally, `ls` will occassionally not terminate and will start
consuming enormous amounts of memory. I haven't gotten a process
trace of this, yet.
The entire boot log and process trace is at http://www.soze.net/bootlog.txt
The bit below ([2]) is in broken.txt, and the .config is named broken.config
[1]
#include <stdio.h>
#include <unistd.h>
#include <fcntl.h>
int main(int argc, char **argv) {
int fd;
fd = open("./test.test", O_RDWR | O_CREAT | O_NONBLOCK);
if (fd == -1) {
perror("unable to open file");
exit(1);
}
write(fd, "test", 4);
close(fd);
fd = unlink("./test.test");
return(0);
}
[2]
Jul 6 14:38:55 broken kernel: chmod T F7547500 5772 179 1 185 210 138 (NOTLB)
Jul 6 14:38:55 broken kernel: Call Trace: [do_signal+166/688] [dev_ifsioc+31/1104] [sock_ioctl+63/128] [sys_ioctl+193/527] [signal_return+20/24]
Jul 6 14:38:55 broken kernel: chmod Z F75475A0 5840 185 179 (L-TLB)
Jul 6 14:38:55 broken kernel: Call Trace: [do_exit+711/768] [sig_exit+195/208] [dequeue_signal+100/208] [do_signal+450/688] [sock_write+174/208]
Jul 6 14:38:55 broken kernel: [sys_write+265/352] [signal_return+20/24]
next reply other threads:[~2002-07-06 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-06 20:02 Justin Guyett [this message]
2002-07-07 2:45 ` Justin Guyett
2002-07-07 0:30 Julian Anastasov
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=20020706200214.GB12813@dreams.soze.net \
--to=justin@soze.net \
--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®