From: war <war@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: Promise ATA/133 TX2 IDE Card - Linux 2.4.x driver problem.
Date: Mon, 23 Jun 2003 21:54:17 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.56.0306232150120.690@p500> (raw)
It may be too early to speculate, however, I have received no spurious
kernel messages with the first generation Promise ATA/100 board (so far).
I have another motherboard (MSI), with another Promise ATA/133 board
(TX2), which also gives this spurious interrupts.
root@l1:/var/log# grep -i spurious *
syslog.1:Jun 19 10:08:48 l1 kernel: spurious 8259A interrupt: IRQ7.
syslog.2:Jun 12 09:33:07 l1 kernel: spurious 8259A interrupt: IRQ7.
syslog.2:Jun 12 20:03:55 l1 kernel: spurious 8259A interrupt: IRQ7.
syslog.2:Jun 14 06:42:23 l1 kernel: spurious 8259A interrupt: IRQ7.
syslog.2:Jun 14 16:12:37 l1 kernel: spurious 8259A interrupt: IRQ7.
syslog.3:Jun 3 09:27:44 l1 kernel: spurious 8259A interrupt: IRQ7.
Is there a particular problem with the ATA/133 TX2 boards, this
error/problem seems to appear with box (that I've used) with this board
(ATA/133 TX2).
Also, I've used the ATA/100 in another box for about a 2 year period
without a single spurious interrupt message.
This leads me to believe there may be something wrong with the Promise
ATA/133 TX2 driver for Linux?
next reply other threads:[~2003-06-24 2:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 1:54 war [this message]
2003-06-24 8:53 Vid Strpic
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=Pine.LNX.4.56.0306232150120.690@p500 \
--to=war@lucidpixels.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®