From: "Olaf Frączyk" <olaf@cbk.poznan.pl>
To: linux-kernel@vger.kernel.org
Subject: Spurious interrupts and VIA chipsets
Date: Fri, 4 Jan 2002 10:59:40 +0100 [thread overview]
Message-ID: <20020104105940.A7113@venus.local.navi.pl> (raw)
Hi,
Are these chipsets dangerous to use?
I found that other people reported similar problems to this one.
I have Asus ATV133-C motherboard, Duron 1000 MHz.
It does NOT have a Promise controller on board.
And I get such message, everytime after I reboot:
Jan 4 08:53:53 venus kernel: spurious 8259A interrupt: IRQ7.
My other hardware is OK: I putted everything from my previous Intel box.
In /proc/interrupts after 1:53 uptime I have:
ERR: 435
Here is what tells /proc/pci about chipset:
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 3).
Master Capable. Latency=8. Prefetchable 32 bit memory at
0xe6000000 [0xe7ffffff].
Bus 0, device 1, function 0:
PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] (rev
0).
Master Capable. No bursts. Min Gnt=8.
Bus 0, device 4, function 0:
ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev
64).
Please CC me, as I'm not subscribed to this list.
Regards,
Olaf Fraczyk
reply other threads:[~2002-01-04 10:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020104105940.A7113@venus.local.navi.pl \
--to=olaf@cbk.poznan.pl \
--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®