linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Erik Slagter <erik@slagter.name>
Cc: Linux IDE <linux-ide@vger.kernel.org>
Subject: Re: Dreaded PDC irq nobody cared
Date: Thu, 06 Oct 2005 15:09:56 +0900	[thread overview]
Message-ID: <4344BFB4.4080600@gmail.com> (raw)
In-Reply-To: <1128506696.4964.28.camel@localhost.localdomain>

Erik Slagter wrote:
> On Mon, 2005-10-03 at 10:47 +0200, Erik Slagter wrote:
> 
>>> - is there any chance booting with noapic would make a difference? I
>>>must say my apic is a bit flaky (according to the logs)
>>
>>BTW I tried noapic, it did seem to work for two days, but then again
>>crashed with the same problem :-(
> 
> 
> I have played around a little more and found these interesting results.
> 
>  - The difference between having or having not the stuck interrupt seems
> to be the forced cooling of the attached harddisks; I find this also
> very hard to believe, but it is very reproducable; so to anyone having
> problems with the promise sata controllers I'd recommend buying
> dedicated harddisk coolers.
>  - I did a test run with disabling of "stuck" interrupts disabled and I
> can say: the interrupt is really stuck, it's no kernel bug; after some
> time I rebooted and the controller (or harddisk) still was in a confused
> state (no booting possible at all), only after an hour it started
> working again; indeed looks like a heat problem.

  Sounds like you got a faulty drive or really bad ventilation in your case.

-- 
tejun

  reply	other threads:[~2005-10-06  6:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 11:32 Dreaded PDC irq nobody cared Erik Slagter
2005-10-03  8:47 ` Erik Slagter
2005-10-05 10:04   ` Erik Slagter
2005-10-06  6:09     ` Tejun Heo [this message]
2005-10-06  9:20       ` Erik Slagter
2005-10-08 17:17         ` Mark Hahn
2005-10-10 10:31           ` Erik Slagter

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=4344BFB4.4080600@gmail.com \
    --to=htejun@gmail.com \
    --cc=erik@slagter.name \
    --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).