From: Paolo Ornati <ornati@fastwebnet.it>
To: Hamish <hamish@travellingkiwi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SATA hangs...
Date: Wed, 28 Jun 2006 21:13:48 +0200 [thread overview]
Message-ID: <20060628211348.41df2ef1@localhost> (raw)
In-Reply-To: <200606242330.48248.hamish@travellingkiwi.com>
On Sat, 24 Jun 2006 23:30:43 +0100
Hamish <hamish@travellingkiwi.com> wrote:
> damned stats # gzip -dc /proc/config.gz |grep -i preempt
> # CONFIG_PREEMPT_NONE is not set
> # CONFIG_PREEMPT_VOLUNTARY is not set
> CONFIG_PREEMPT=y
> CONFIG_PREEMPT_BKL=y
> CONFIG_DEBUG_PREEMPT=y
> damned stats #
>
> I also tried 2.6.17-mm but that dies in reiserfs claiming a bug in bitmap.c
>
> I'll try a re-compile of 2.7.17.1 vanilla with no pre-empt & see how it goes.
It happened again 2 times here, then I've opened the case and done a
"cleanup". I've also switched the power cable of the disk.
After that it isn't happened anymore.
When it happened I think I've heard a small "beep", like a small power
"failure" that made it powering off/on in a fraction of second.
(Is that plausible?)
So maybe mine was an "hardware" problem followed by the software unable
to get the disk to behave correctly... or something.
Another interesting thing is that the disk preserves his state of
brokenness across a reboot... I need a full power OFF/ON to get it back.
I hope to never see this again :)
--
Paolo Ornati
Linux 2.6.17.1 on x86_64
next prev parent reply other threads:[~2006-06-28 19:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 20:34 SATA hangs Hamish
2006-06-23 21:41 ` Jeff Garzik
2006-06-24 7:36 ` Paolo Ornati
2006-06-24 8:09 ` Paolo Ornati
2006-06-24 22:30 ` Hamish
2006-06-28 19:13 ` Paolo Ornati [this message]
2006-06-29 21:53 ` Hamish
2006-06-30 9:26 ` Paolo Ornati
2006-07-21 22:07 ` Hamish
-- strict thread matches above, loose matches on Subject: below --
2006-06-27 12:23 Fortier,Vincent [Montreal]
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=20060628211348.41df2ef1@localhost \
--to=ornati@fastwebnet.it \
--cc=hamish@travellingkiwi.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