From: Alex Davis <alex14641@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Possible bug and question about ide_notify_reboot in drivers/ide/ide.c (2.4.19)
Date: Thu, 12 Sep 2002 19:37:44 -0700 (PDT) [thread overview]
Message-ID: <20020913023744.78077.qmail@web40510.mail.yahoo.com> (raw)
The ide_notify_reboot function contains the following code fragment:
for (unit = 0; unit < MAX_DRIVES; ++unit) {
drive = &hwif->drives[unit];
if (!drive->present)
continue;
/* set the drive to standby */
printk("%s ", drive->name);
if (event != SYS_RESTART)
if (drive->driver != NULL && DRIVER(drive)->standby(drive))
continue;
if (drive->driver != NULL && DRIVER(drive)->cleanup(drive))
continue;
}
The standby() function returns 0 on success, and non-zero on failure. If standby() returns
failure status, the cleanup() call is skipped. Is this intentional?
Second, why do we need to put the disks on standby before halting? I ask because putting
the disks on standby puts my hard drives into a coma!! When I power up after a halt, I have
to go into the BIOS and force auto-detect to wake them back up. I've removed the "standby"
code and things seem to be functioning normally. I have an Epox 8K7A motherboard with two
Maxtor Hard drives (model 5T040H4).
__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com
next reply other threads:[~2002-09-13 2:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 2:37 Alex Davis [this message]
2002-09-13 13:09 ` Possible bug and question about ide_notify_reboot in drivers/ide/ide.c (2.4.19) Alan Cox
2002-09-13 15:10 ` Tomas Szepe
2002-09-13 15:14 ` Alan Cox
2002-09-13 17:54 ` Tomas Szepe
2002-09-14 0:22 ` Matthias Andree
2002-09-13 15:19 ` Alex Davis
2002-09-13 16:15 ` Alan Cox
2002-09-13 17:39 ` Andre Hedrick
2002-09-14 1:08 ` Alex Davis
2002-09-14 0:21 ` Matthias Andree
2002-09-14 17:09 ` jbradford
2002-09-14 1:01 Alex Davis
2002-09-14 9:53 ` Matthias Andree
2002-09-14 13:37 ` Alan Cox
2002-09-14 13:42 ` Miquel van Smoorenburg
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=20020913023744.78077.qmail@web40510.mail.yahoo.com \
--to=alex14641@yahoo.com \
--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;
as well as URLs for NNTP newsgroup(s).