All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Derer <matthew@alumni.caltech.edu>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.4.18: aic7xxx soft reboot broken
Date: Sun, 12 May 2002 22:50:01 -0700	[thread overview]
Message-ID: <3CDF5409.9040809@alumni.caltech.edu> (raw)

I recently upgraded to a 2.4.18 kernel on a machine with an Adaptec 
2940AU SCSI controller.  Since the upgrade, soft reboots don't work; the 
machine appears to shut down normally, but during the subsequent boot 
the SCSI BIOS reports a timeout on an inquiry command and is unable to 
find any drives on the bus.  A hard power cycle is required to restore 
the card to a state in which it can find the drives.

Problem seems to be that the reboot notifier for the new aic7xxx driver 
is registered in aic7xxx_setup, which only gets called when there are 
module or kernel command-line params for aic7xxx.  Without reboot 
notification and cleanup, the card is left in a bad state at shutdown, 
and BIOS does not appear to clean it up during boot.

I think other people have run into the same problem:

http://groups.google.com/groups?selm=20010811.180158.1012502954.2309%40omit.nonsense.bigfoot.com

Workaround is obvious, just feed the module any param to get the 
notification registered, like aic7xxx=verbose, then soft reboots work 
just fine.  Fix would be to register the notifier whether there are 
params or not.  Also wouldn't hurt to check for SYS_POWER_OFF as well as 
SYS_HALT and SYS_DOWN when handling the notify, SYS_POWER_OFF can result 
in a halt without actually powering off on some machines.

Matthew


                 reply	other threads:[~2002-05-13  5:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3CDF5409.9040809@alumni.caltech.edu \
    --to=matthew@alumni.caltech.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.