From: Jeff Garzik <jgarzik@pobox.com>
To: Yaroslav Halchenko <kernel@onerussian.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8 -> 2.6.11 (+ata-dev patch) -- HDD is always on
Date: Fri, 29 Jul 2005 00:25:42 -0400 [thread overview]
Message-ID: <42E9AFC6.9010805@pobox.com> (raw)
In-Reply-To: <20050729041031.GU16285@washoe.onerussian.com>
Yaroslav Halchenko wrote:
> I've been running debian stable with 2.6.8 kernel but due to recent
> failure of the SATA harddrive I've decided to upgrade to 2.6.11 + libata
> patch (2.6.11-libata-dev1.patch.gz) and recent smartmontools
>
> After everything worked out and I decided to rest in piece but I've
> found that HDD LED light nomater what. It seems to turn off during BIOS
> checks and then kicks in 1-2 secs after kernel starts booting. No
> prominent harddrive activity noise can be heard but this drive is
> quite silent so it is hard to say.
Does this happen in unpatched 2.6.12.3 or 2.6.13-rc4?
> QUESTION:
>
> LED constantly ON - does it signal about a problem or may be just
> that some status bit is hanging? Should I worry and try differen kernel
> version?
>
> YIKES: ran hddtemp /dev/sda and whole box hanged... SysRq keys - no
> effect... heh heh... reboot -> nothing in logs
> P.S. was ata-dev patch incorporated in recent kernel versions so I could
> use SMART with vanilla kernel?
This is one of the reasons why SMART support is not yet in the mainline
kernel!
Jeff
next prev parent reply other threads:[~2005-07-29 4:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 4:10 2.6.8 -> 2.6.11 (+ata-dev patch) -- HDD is always on Yaroslav Halchenko
2005-07-29 4:25 ` Jeff Garzik [this message]
2005-07-29 5:58 ` Yaroslav Halchenko
2005-07-29 6:15 ` Yaroslav Halchenko
2005-07-29 7:09 ` Yaroslav Halchenko
2005-07-31 0:11 ` Yaroslav Halchenko
2005-07-31 1:23 ` Jeff Garzik
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=42E9AFC6.9010805@pobox.com \
--to=jgarzik@pobox.com \
--cc=kernel@onerussian.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 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.