From: Ettore Perazzoli <ettore@ximian.com>
To: timw@splhi.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Interesting fs corruption story
Date: 06 Mar 2001 20:10:10 -0500 [thread overview]
Message-ID: <983927410.11517.0.camel@milkplus.unknown.domain> (raw)
In-Reply-To: <20010306170102.B1095@kochanski.internal.splhi.com>
In-Reply-To: <Pine.LNX.4.21.0103042043320.27829-100000@trna.ximian.com> <20010306170102.B1095@kochanski.internal.splhi.com>
On 06 Mar 2001 17:01:02 -0800, Tim Wright wrote:
> Hi Ettore,
> I have no idea if this is related to your problem since you didn't mention
> that key part, but with the same drive, I managed to trash my root partition
> incredibly badly by trying to use DMA and then do APM suspend or hibernate.
> On wakeup, I'd get an 'hda: lost interrupt' but then things would appear to
> carry on.
>
> The fix for me was to rebuild the kernel and make sure CONFIG_APM_ALLOW_INTS
> was enabled. So, do you ever use power management and is this similar, or do
> you have a completely different problem ?
Wow, this sounds like this might be the problem. I just checked my
`.config' and indeed `CONFIG_APM_ALLOW_INTS' is not enabled. And indeed
I have been suspending/resuming the machine a few times before the
partition got corrupted.
So, does DMA work correctly on your system after setting this option?
I have now disabled it completely as a safety measure (and as suggested
by somebody else on this list), and indeed I have not had any more
troubles for now. (I have been forcing a fsck every day before turning
the machine off.)
Thanks a lot for the hint! I will now rebuild my kernel with that
option turned on.
--
Ettore
next prev parent reply other threads:[~2001-03-07 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 2:46 Interesting fs corruption story Ettore Perazzoli
2001-03-05 4:33 ` Jonathan Morton
2001-03-05 5:08 ` Ettore Perazzoli
2001-03-07 1:01 ` Tim Wright
2001-03-07 1:10 ` Ettore Perazzoli [this message]
2001-03-07 20:22 ` Tim Wright
2001-03-12 12:44 ` Ettore Perazzoli
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=983927410.11517.0.camel@milkplus.unknown.domain \
--to=ettore@ximian.com \
--cc=linux-kernel@vger.kernel.org \
--cc=timw@splhi.com \
/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