From: Lee Trager <Lee@PicturesInMotion.net>
To: Lee Trager <Lee@PicturesInMotion.net>
Cc: Tejun Heo <htejun@gmail.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: ICH4-M ACPI Error
Date: Wed, 16 Aug 2006 19:55:57 -0400 [thread overview]
Message-ID: <44E3B08D.4000907@PicturesInMotion.net> (raw)
In-Reply-To: <44E2E177.5040903@PicturesInMotion.net>
Lee Trager wrote:
> Lee Trager wrote:
>
>> Tejun Heo wrote:
>>
>>
>>> [resending as reply to add linux-ide back, please don't drop cc list]
>>>
>>> Tejun Heo wrote:
>>>
>>>
>>>> Lee Trager wrote:
>>>>
>>>>
>>>>> Tejun Heo wrote:
>>>>>
>>>>>
>>>>>> Lee Trager wrote:
>>>>>>
>>>>>>
>>>>>>> Hey I've been having this problem for awhile on my laptop(IBM
>>>>>>> Thinkpad
>>>>>>> T40) and have no been able to figure out how to fix it. It seems that
>>>>>>> when ever I resume my laptop from suspend(from hard drive or RAM) my
>>>>>>> dmesg is filled with this and I am unable to do anything that
>>>>>>> requires
>>>>>>> access to the hard drive.
>>>>>>>
>>>>>>> ide: failed opcode was: unknown
>>>>>>> hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
>>>>>>> hda: task_out_intr: error=0x10 { SectorIdNotFound },
>>>>>>> LBAsect=74853287,
>>>>>>> sector=74853287
>>>>>>>
>>>>>>>
>>>> Ah... it was the IDE driver, sorry. You can try using Alan Cox's
>>>> libata pata drivers patch which is included in recent -mm trees.
>>>> With the patch, libata ata_piix driver can drive the controller
>>>> instead of ide and it has better error handling.
>>>>
>>>> Be warned that the drive will come up as /dev/sda instead of /dev/hda
>>>> and it currently doesn't disable host protected area unlike IDE, so
>>>> your disk can be messed up.
>>>>
>>>>
>> Isn't libata for SATA drivers? My drive is an IDE. Also I'm worried
>> about using something that could mess up my drive when this is going to
>> be used for school next month and I need something that can sleep as
>> well as reliable.
>>
>>
> I read about it a little more and it seems that my controller is
> supported and its maturity is listed as "No known major issues. New
> issues tend to get fixed quickly." So does this mean they fixed the
> issue you were talking about? I guess Ill test it tomarrow(its kina
> late) and report back.
>
>
> I tried the mm sources and as soon as I boot into it I get "atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly" It seems that they dont have a patch for just libata for any recent kerenls(the latest patch ive found is 2.6.17-rc4-git2). I could try that but id rather but on a recent, and for normal use, stable kernel.
>
next prev parent reply other threads:[~2006-08-16 23:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 6:01 ICH4-M ACPI Error Lee Trager
2006-08-16 6:13 ` Tejun Heo
[not found] ` <44E2C82A.3040802@PicturesInMotion.net>
[not found] ` <44E2CB82.8050100@gmail.com>
2006-08-16 7:40 ` Tejun Heo
2006-08-16 8:13 ` Lee Trager
2006-08-16 9:12 ` Lee Trager
2006-08-16 23:55 ` Lee Trager [this message]
2006-08-17 1:45 ` Lee Trager
2006-08-16 7:40 ` Lee Trager
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=44E3B08D.4000907@PicturesInMotion.net \
--to=lee@picturesinmotion.net \
--cc=htejun@gmail.com \
--cc=linux-ide@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).