mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: kevin@labsysgrp.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: lost interrupt hell - Plea for Help
Date: Sun, 19 May 2002 22:26:00 +0200 (MET DST)	[thread overview]
Message-ID: <200205192026.WAA27881@harpo.it.uu.se> (raw)

On Sun, 19 May 2002 11:43:09 -0700, Kevin P. Fleming wrote:
>I have just switched motherboards in my file server, which previously had no
>problems ripping audio from my Creative 52X drives. The new motherboard has
>the KT266A chipset, but the CD drives are _not_ connected to that chipset's
>IDE ports. I am getting "lost interrupt" messages when I try to rip audio
>from the drives, or even mount ISO9660 discs (which do eventually succeed,
>they just take over a minute to mount). So far I have done the following:
>
>- turned off "dma" and "unmaskirq" for the CD drives
>- tried ide-scsi/sg instead of ide-cd
>- tried booting with "noapic"
>- tried 2.4.19-pre8 and 2.4.19-pre8-ac4
>
>Nothing has helped. The machine configuration is an MSI KT7266-Pro2RU
>motherboard, KT266A chipset with on-board Promise PDC20265R FastTrak
>"lite"). There is also a Promise PDC20262 (Ultra66TX2) in a PCI slot, and
>that is where the CD drives are connected. Each CD drive is the master on
>its channel, and one of them also has a Iomega ZIP 250 ATAPI drive as its
>slave. Interestingly, the ZIP drive works perfectly, no "lost interrupt"
>messages at all.

1. It's been stated here on LKML several times that optical drives
   should NOT be connected to Promise chips. It may work with Promise's
   Windows drivers, but that doesn't help here. A better strategy is to
   connect your CD-ROMs and Zip drive to the KT266A, and any IDE disks
   either to the FastTrak or the Ultra66 add-on card (though from your
   `lspci` I suppose your disks are SCSI).

2. "noapic" only controls whether the I/O-APIC is used or not.
   If you want to test without the _local_ APIC being enabled,
   then I'm afraid you have to rebuild the kernel with
   CONFIG_X86_UP_APIC disabled.

/Mikael

             reply	other threads:[~2002-05-19 20:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-19 20:26 Mikael Pettersson [this message]
2002-05-19 22:19 ` Kevin P. Fleming
2002-05-20  0:35 ` Kevin P. Fleming
  -- strict thread matches above, loose matches on Subject: below --
2002-05-19 12:25 Mikael Pettersson
2002-05-20  8:42 ` Erik Steffl
2002-05-07 18:01 mikeH
2002-05-09 11:34 ` Tomasz Rola
2002-05-10 16:15   ` Denis Vlasenko
2002-05-10 21:28     ` Erik Steffl
2002-05-11  8:32       ` mikeH
2002-05-11  8:38         ` Rudmer van Dijk
2002-05-11  8:53           ` mikeH
2002-05-11  8:48             ` Rudmer van Dijk
2002-05-16 20:50           ` Rudmer van Dijk
2002-05-17  8:49             ` Mike
2002-05-19  7:14               ` Erik Steffl
2002-05-19 18:43                 ` Kevin P. Fleming
2002-05-11  8:48         ` Erik Steffl
2002-05-09 11:42 ` Tomasz Rola

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=200205192026.WAA27881@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=kevin@labsysgrp.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®