public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: zlatko.calusic@iskon.hr
Cc: Jarno Paananen <jpaana@s2.org>,
	Pierre Rousselet <pierre.rousselet@wanadoo.fr>,
	lkml <linux-kernel@vger.kernel.org>,
	mingo@elte.hu
Subject: Re: 2.5.9 - HPT366 ide unexpected interrupts
Date: Sun, 28 Apr 2002 20:56:23 +0200	[thread overview]
Message-ID: <3CCC45D7.2030401@evision-ventures.com> (raw)
In-Reply-To: <3CC5BAA3.3080705@wanadoo.fr> <m3u1q0smou.fsf@kalahari.s2.org> <878z77er9m.fsf@atlas.iskon.hr>

Uz.ytkownik Zlatko Calusic napisa?:
> Jarno Paananen <jpaana@s2.org> writes:
> 
> 
>>Pierre Rousselet <pierre.rousselet@wanadoo.fr> writes:
>>
>>| PIII 650/Abit BE6 HPT366(ide2, ide3)
>>| 
>>| dmesg gives 482 times the same line :
>>| ide: unexpected interrupt 0 11
> 
> 
> I'm having the same problems on dual PIII (VIA chipset) with addon
> Promise IDE card:
> 
> Apr 24 19:34:51 atlas kernel: ide: unexpected interrupt 1 11
> 
> Lots of those...
> 
> Looks like it favors additional IDE interfaces. As system appears to
> behave sanely, modulo flooded logs, I decided to comment the printk
> for the time being.

That's fine and it will be gone in 2.5.11. The message is

> Ingo, does it have anything to do with your interrupt balancing code?
> If you need additional testing, let me know.

No no no. It's really harmless. It is affecting add on interfaces becouse
they are likely to share interrupts with other devices.



      reply	other threads:[~2002-04-28 19:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23 19:48 2.5.9 - HPT366 ide unexpected interrupts Pierre Rousselet
2002-04-24 23:26 ` Jarno Paananen
2002-04-28 16:12   ` Zlatko Calusic
2002-04-28 18:56     ` Martin Dalecki [this message]

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=3CCC45D7.2030401@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=jpaana@s2.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pierre.rousselet@wanadoo.fr \
    --cc=zlatko.calusic@iskon.hr \
    /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