From: Rene Rebe <rene.rebe@gmx.net>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: alex14641@yahoo.com, linux-kernel@vger.kernel.org
Subject: Re: I've stopped the 'Spurious interrupts on IRQ7'
Date: Mon, 28 Jan 2002 12:53:45 +0100 (CET) [thread overview]
Message-ID: <20020128.125345.884013673.rene.rebe@gmx.net> (raw)
In-Reply-To: <200201280846.g0S8k1E22015@Port.imtp.ilyichevsk.odessa.ua>
In-Reply-To: <20020128083726.83324.qmail@web9205.mail.yahoo.com> <200201280846.g0S8k1E22015@Port.imtp.ilyichevsk.odessa.ua>
Hi.
From: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Subject: Re: I've stopped the 'Spurious interrupts on IRQ7'
Date: Mon, 28 Jan 2002 10:46:02 -0200
> On 28 January 2002 06:37, Alex Davis wrote:
> > I added the following line to /etc/lilo.conf
> >
> > append = "parport=0x378,7"
> >
> > and re-ran lilo. I also noticed that the 'ERR' field in
> > /proc/interrupts stays at 0, whereas before the mod it
> > was increasing.
>
> Do you have a printer? Try to boot while it is powered off.
> WHAT is generating irq 7 now?
Hi. As I stated before I get "Spurious interrupts on IRQ7" ony many
(all?) systems (from AMD-K62/Ali, over Pentium-II to AMD-K7-XP/SiS)
with the latest kernels. I started arround 2.4.14/15 ... - None system
has anything attached to the LPT port ...
I'll try to find some time to reboot some to see where it started ...
> It is documented that interrupt controller will report irq 7 if it sees irq
> but cannot determine what device sends it. That's exactly what's happening
> when you see "spurious int" message.
>
> You made kernel believe it's from printer. That does not cure the real
> problem. BTW, there's not much of a problem, kernel just ignores spurious
> interrupts. It _is_ a problem if you see 'ERR' number rapidly increasing.
> --
> vda
k33p h4ck1n6
René
--
René Rebe (Registered Linux user: #248718 <http://counter.li.org>)
eMail: rene.rebe@gmx.net
rene@rocklinux.org
Homepage: http://drocklinux.dyndns.org/rene/
Anyone sending unwanted advertising e-mail to this address will be
charged $25 for network traffic and computing time. By extracting my
address from this message or its header, you agree to these terms.
next prev parent reply other threads:[~2002-01-28 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200201281219.g0SCJBE22987@Port.imtp.ilyichevsk.odessa.ua>
2002-01-28 12:46 ` Denis Vlasenko
2002-01-28 8:37 ` Alex Davis
2002-01-28 11:53 ` Rene Rebe [this message]
2002-01-28 14:39 ` Rene Rebe
2002-01-29 14:14 ` Maciej W. Rozycki
2002-01-28 14:30 ` Alex Davis
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=20020128.125345.884013673.rene.rebe@gmx.net \
--to=rene.rebe@gmx.net \
--cc=alex14641@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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®