From: "Martin Eriksson" <nitrax@giron.wox.org>
To: "Michael Obster" <michael.obster@bingo-ev.de>,
<linux-kernel@vger.kernel.org>
Subject: Re: AMD Athlon + VIA Crashing On Disk I/O
Date: Wed, 17 Apr 2002 00:55:51 +0200 [thread overview]
Message-ID: <01a101c1e599$db6634b0$0201a8c0@homer> (raw)
In-Reply-To: <Pine.LNX.4.33.0204160921060.472-100000@polywog.navpoint.com> <00dc01c1e58b$668dd2f0$0201a8c0@homer> <3CBCB762.4030902@bingo-ev.de>
----- Original Message -----
From: "Michael Obster" <michael.obster@bingo-ev.de>
To: <linux-kernel@vger.kernel.org>
Sent: Wednesday, April 17, 2002 1:44 AM
Subject: Re: AMD Athlon + VIA Crashing On Disk I/O
> hi,
>
> >>I get (when FSCK):
> >>
> >>spurious 8259A IRQ7
>
> I also get this message every time i boot my machine when the fs are
> mounted. but i don't had a machine lock yet.
> Configuration: Athlon 1GHz on a VIA chip (ASUS A7V).
> Btw. What does this message say?
Nothing to worry about.
Interrupts which are not known where they originate from are sent to IRQ7
(per 8259A spec). It could be just about anything in your machine generating
these interrupts, and this is only a problem if it happens very often. There
were a discussion about this a while ago and the conclusion is that it
happens with just about every chipset.
>
> > First check out what kind of chipset you really have;
> > lspci -xs 0:0
> > should do the thing. Post the results.
>
> Kernel is 2.4.19pre5
>
> my result is:
> 00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133]
> (rev 02)
> 00: 06 11 05 03 06 00 10 22 02 00 00 06 00 08 00 00
> 10: 08 00 00 e4 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 33 80
> 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00
You should have no problem with this chipset if it is the KT133 without
onboard graphics (99% chance).
>
> I hope you can do s.th. with that.
LOL! I mistakenly read your acronym as "sh*t".
_____________________________________________________
| Martin Eriksson <nitrax@giron.wox.org>
| MSc CSE student, department of Computing Science
| Umeå University, Sweden
next prev parent reply other threads:[~2002-04-16 22:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 13:28 E M Recio
2002-04-16 21:12 ` Martin Eriksson
2002-04-16 23:44 ` Michael Obster
2002-04-16 22:50 ` Rene Rebe
2002-04-16 22:55 ` Martin Eriksson [this message]
2002-04-17 3:14 ` Emilio Recio
2002-04-16 23:45 ` Denis Vlasenko
2002-04-17 1:55 ` Josh McKinney
2002-04-17 3:47 ` Andre Hedrick
2002-04-20 17:15 Richard Ems
2002-04-20 17:32 ` Nicolae P. Costescu
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='01a101c1e599$db6634b0$0201a8c0@homer' \
--to=nitrax@giron.wox.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.obster@bingo-ev.de \
/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®