linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Pat LaVarre <p.lavarre@ieee.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: IRQ re-disabled when SATAPI via CONFIG_BLK_DEV_IDE_SATA
Date: Wed, 18 Aug 2004 01:38:45 -0400	[thread overview]
Message-ID: <4122EB65.9020009@pobox.com> (raw)
In-Reply-To: <1092774469.4599.4.camel@patlinux.iomegacorp.com>

Pat LaVarre wrote:
> Jeff G:
> 
> By the way,
> 
> I see the following dmesg repeat often, like once per open of the
> device, if I connect SATAPI in 2.6.8.1 via CONFIG_BLK_DEV_IDE_SATA.
> 
> kernel: irq 18: nobody cared!
> kernel:  [<c010822b>] __report_bad_irq+0x2a/0x8b
> kernel:  [<c0108315>] note_interrupt+0x6f/0x9f
> kernel:  [<c01086a8>] do_IRQ+0x1d4/0x226
> kernel:  [<c0103cbe>] default_idle+0x0/0x2d
> kernel:  [<c0106800>] common_interrupt+0x18/0x20
> kernel:  [<c0103cbe>] default_idle+0x0/0x2d
> kernel:  [<c0103ce8>] default_idle+0x2a/0x2d
> kernel:  [<c0103d5c>] cpu_idle+0x37/0x40
> kernel:  [<c0451885>] start_kernel+0x1b0/0x201
> kernel:  [<c045130a>] unknown_bootoption+0x0/0x16f
> kernel: handlers:
> kernel: [<c0249b12>] (ide_intr+0x0/0x1d1)
> kernel: Disabling IRQ #18
> 
> I recognise this "disabling IRQ" message from the history of libata.ko
> development, where I more often saw it once and then immediately a
> kernel crash.

See 'ide_intr' in there?  we need to teach the IDE driver about the 
ICH5's weird interrupt acknowledgment stuff.

Alternative is to get ATAPI working in libata, then we can do PATA under 
libata as well, which resolves this problem.

	Jeff




      reply	other threads:[~2004-08-18  5:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17 20:27 IRQ re-disabled when SATAPI via CONFIG_BLK_DEV_IDE_SATA Pat LaVarre
2004-08-18  5:38 ` Jeff Garzik [this message]

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=4122EB65.9020009@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=p.lavarre@ieee.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).