From: Fionn Behrens <Fionn.Behrens@unix-ag.org>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: SMP IRQ management issues in 2.4.x
Date: Thu, 21 Mar 2002 22:38:24 +0100 [thread overview]
Message-ID: <20020321223824.62fb6f21.fionn@unix-ag.org> (raw)
In-Reply-To: <E16o3bM-0005Jz-00@the-village.bc.nu>
On Thu, 21 Mar 2002 14:31:36 +0000 (GMT)
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > After changing from 2.2.18 to 2.4.17 recently, I noticed that after
> > booting 2.4 my interrupts were routed a lot less effectively than under
> > 2.2
>
> Can you post both 2.2 and 2.4 tables for comparison
I am afraid this will get slightly problematic since I upgraded several system components (LVM update and some ext2->ext3 partition changes amongst others) which would probably make booting back into a working 2.2 system a rather adventurous task.
I think I'll try to do it tomorrow, however. Hope nothing gets broken.
> > Needless to say that Harddrives connected to ide2 and ide3 (Promise)
> > constantly lose interrupts when used as long as X is running (nvidia),
> > bringing the system to crawl.
>
> You should never be losing interrupts, even with everything on one IRQ line.
> PCI interrupts are level trigger so don't get "lost" in the same way as ISA
> ones did
As a matter of fact I keep getting the following kernel messages when accessing large chunks of data on ide2 or ide2 only while X is running:
Mar 21 09:56:41 localhost kernel: hde: drive not ready for command
Mar 21 09:56:41 localhost kernel: hde: status error: status=0x58 { DriveReady
SeekComplete DataRequest }
Mar 21 09:56:41 localhost kernel: hde: drive not ready for command
Mar 21 09:56:41 localhost kernel: hde: write_intr error1: nr_sectors=128,
stat=0 xd0
Mar 21 09:56:41 localhost kernel: hde: write_intr: status=0xd0 { Busy }
Mar 21 09:56:41 localhost kernel: ide2: reset: success
Mar 21 09:56:41 localhost kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
[...and so on, mostly without the write_intr error, just status errors...]
When X is not running (aka opencount 0 for nvdriver) all runs smoothly.
Alas, I can't find a way to assign that nv module to its own interrupt.
Regards,
Fionn
--
I believe we have been called by history to lead the world.
G.W. Bush, 2002-03-01
next prev parent reply other threads:[~2002-03-21 21:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 13:57 Fionn Behrens
2002-03-21 14:31 ` Alan Cox
2002-03-21 21:38 ` Fionn Behrens [this message]
2002-03-21 22:10 ` Alan Cox
2002-03-22 14:25 ` Fionn Behrens
2002-03-22 15:11 ` Alan Cox
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=20020321223824.62fb6f21.fionn@unix-ag.org \
--to=fionn.behrens@unix-ag.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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®