From: Jason Baron <jbaron@redhat.com>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.4.22
Date: Wed, 27 Aug 2003 11:35:11 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0308271127150.1491-100000@dhcp64-178.boston.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0308261327540.229@chaos>
On Tue, 26 Aug 2003, Richard B. Johnson wrote:
>
> I configured, built and booted Linux-2.4.22. There are
> some problems.
>
> (1) `dmesg` fails to read the first part of the buffered
> kernel log. I have attached two files, dmesg-20 (normal)
sounds like the log buffer wrapped around from a lot of printks
> (3) When umounting the root file-system, the machine usually
> hangs. The result is a long `fsck` on the next boot. The problem
> seems to be that sendmail doesn't get killed during the `init 0`
> sequence. It remains with a file open and the root file-system isn't
> unmounted. A temporary work-round is to `ifconfig eth0 down` before
> starting shutdown. Otherwise, sendmail remains stuck in the 'D' state.
this is likely the unshare_files change, which has been mentioned in
several threads as causing similar type issues...i posted a patch that
solves the issue, and Alan included a patch in his -ac series, which
also addresses this issue.
-Jason
next prev parent reply other threads:[~2003-08-27 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 17:30 Linux-2.4.22 Richard B. Johnson
2003-08-27 15:35 ` Jason Baron [this message]
2003-08-27 15:40 ` Linux-2.4.22 Richard B. Johnson
2003-08-27 20:59 ` Linux-2.4.22 Richard B. Johnson
2003-09-01 20:45 ` Linux-2.4.22 Marcelo Tosatti
2003-09-01 21:14 ` Linux-2.4.22 Marcelo Tosatti
2003-09-02 12:57 ` Linux-2.4.22 Richard B. Johnson
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=Pine.LNX.4.44.0308271127150.1491-100000@dhcp64-178.boston.redhat.com \
--to=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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).