mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: mgm@havoc.gtf.org (Michael G. Mobley)
To: linux-kernel@vger.kernel.org (Linux Kernel Mailing List)
Subject: shutdown "anomoly" with kernel 2.4.9
Date: Thu, 20 Sep 2001 16:43:19 -0400 (EDT)	[thread overview]
Message-ID: <20010920204319.4E0741F76@havoc.gtf.org> (raw)


Folks,

I thought I'd mention something weird I'm seeing with kernel 2.4.9...

BTW, I just recently subscribed to this list, but have scoured the
archives and didn't find anything pertinent to this particular problem.

When running kernel 2.4.9, my system cannot reliably reboot/
halt/shutdown.  It hangs when killall5 sends out the TERM signal, as if
init itself is terminating.  This is VERY repeatable (happens pretty
much every time, whether the shutdown is through 'shutdown -r now',
'reboot', 'halt', whatever...)

I wouldn't have thought this is a kernel problem, but, an identical build
of 2.4.8 does not seem to exhibit this behavior.  And I've played around,
making one change at a time, and that really is the ONLY difference.

BTW, I'm building both kernels to exactly the same config.  (diff of the
.configs show only three commented out sound card options that have been
added to 2.4.9 as differences.)

Brief system setup is:

1xPIII/800, Asus P3V4X MB, 640MB RAM
AHA29160 SCSI controller w/ 3 HDDs, 2 CDROMs
No IDE
USB, AGP, etc...
etc. etc...  (Can provide more details if needed)
GCC version is:  2.96
Binutils version is: 2.10.91.0.2
(Basically it's a stock RH7.1 install right now)

Regards, 
  Michael
-- 
                                              |  Michael G. Mobley
                                              |  mgm@havoc.gtf.org

             reply	other threads:[~2001-09-20 20:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-20 20:43 Michael G. Mobley [this message]
2001-09-20 21:05 ` Ignacio Vazquez-Abrams

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=20010920204319.4E0741F76@havoc.gtf.org \
    --to=mgm@havoc.gtf.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

all inboxes | Powered by JetHome®