Subject: Re: "hda: lost interrupt" and low battery
From: H Dziardziel (hdz@operamail.com)
Date: Mon Dec 11 2000 - 13:35:37 GMT+1
On Mon, 11 Dec 2000 00:29:54 +0100, Marco Boglione
<Marco@pancake-software.de> wrote:
>
>
>I already tried this but nothing changed. This is a linux-only problem -
>Windows works perfectly. I also have tested it with 3 different batteries:
>the same result everytime. So what could be the reason?
>
Right after sending my post I recalled this which may be the same?
Quoted with header snips etc>
From: Andrew Jaffe <jaffe@cfpa.berkeley.edu>
Newsgroups: comp.os.linux.portable,comp.os.linux.setup
Subject: Re: apm problems after 2.2.16 upgrade ("/hda: lost
interrupt")
Date: 23 Aug 2000 12:15:14 -0700
Organization: University of California at Berkeley
Solved my own problem!
After being admonished to look at the various apm-related files
scattered throughout /etc/*, I found
/etc/sysconfig/apmd
It contains many possible switches to affect the behavior of apmd.
One of the lines documented in the file refers to exactly this
problem,
and uncommenting the "HDPARM" lines seems to do the trick!
It would be nice if this was actually in the documentation, rather
than
just the files, of course!
Andrew
Andrew Jaffe <jaffe@cfpa.berkeley.edu> writes:
> Hi All-
>
> I recently upgraded the kernel on my RH6.1 system (on a Gateway 5150) to
> 2.2.16. Things went relatively smoothly.
>
> However, I've had many problems with apm. I upgraded to the latest apmd
> RPMs (3.0final), and this helped a bit.
>
> However, sometimes when I wake up after going to sleep, I find that my
> hard disk is completely inaccessible. X works until you try anything
> that accesses the disk, at which point it stops. On a console screen, I
> get a message that is something like
> "hda: lost interrupt"
> if I try to login. Again, this implies disk problems.
>
> This didn't happen before, ever! Any ideas?
>
> Andrew
> --
>
unquote
This archive was generated by hypermail 2b25 : Sat Dec 16 2000 - 08:44:14 GMT+1