public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Burgess <lkml@jburgess.uklinux.net>
To: linux kernel <linux-kernel@vger.kernel.org>, jgarzik@pobox.com
Subject: Re: Serial ATA (SATA) for Linux status report
Date: Thu, 04 Dec 2003 18:03:48 +0000	[thread overview]
Message-ID: <3FCF7704.2070601@jburgess.uklinux.net> (raw)

**Jeff Garzik wrote:
 > Intel ICH5
...
 > drivers/ide driver status: Production, but see issue #1, #2.
...
 > Issue #2: Excessive interrupts are seen in some configurations.

I can reproduce this easily in my current setup. It looks like the 
chipset is generating some unexpected IRQ's when after performing the 
hdparm drive setting ioctl()'s.

More details are below, let me know if you need any more.

Hardware:
Gigabyte 8IG1000Pro (Intel ICH5)
2 x Parallel IDE drives on PATA IDE primary
2 x DVD drives on PATA IDE secondary
1 x Seagate 80GB SATA drive on SATA0

Software:
Linux-2.6.0-test10, using drivers/ide driver

The Root fileystem is currently on one of the parallel IDE drives, and 
the SATA doesn't get used much (yet). The PC boots and vmstat shows 
everything is OK.

Running an hdparm command on the drive causes an IRQ storm, reported by 
vmstat at ~ 100k IRQ/s. I think that "hdaprm -S 128 /dev/hde" will 
trigger it, but I can't remember for certain.
Performing another access to the drive, e.g. umount /dev/hde, clears the 
problem.
It is 100% repeatable, i.e. doing the hdparm makes it happen again, then 
mounting the drive will clear it.

I put some extra debug in the ide_intr routine and found that there was 
a storm of interrupts around when the partition table was being read 
(the "drive_check_ready()" check was failing continuously for a while). 
Afterwards there were times when  lots of IRQs happened when "handler" 
was NULL. It looks like the chipset might be generating some extra IRQ's 
which the existing code isn't expecting. Doing another access on the 
drive looks like it is enough to clear whatever interrupt is pending.

    Jon




             reply	other threads:[~2003-12-04 18:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 18:03 Jon Burgess [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-24 19:49 Serial ATA (SATA) for Linux status report Jeff Garzik
2003-12-03 20:44 Jeff Garzik
2003-12-03 23:27 ` Andre Tomt
2003-12-03 23:36   ` Jeff Garzik
2003-12-04  0:21     ` Miquel van Smoorenburg
2003-12-04  0:59     ` Samuel Flory
2003-12-04  1:02     ` Andre Tomt
2003-12-04 13:38     ` Justin Cormack
2003-12-04 14:54       ` Jeff Garzik
2003-12-04  8:17 ` Arnaud Launay
2003-12-04 15:01   ` Jeff Garzik
2003-12-05 17:42     ` Mickael Marchand
2003-12-05 17:47       ` Jeff Garzik
2003-12-05 18:16         ` Kevin P. Fleming
2003-12-05 18:29           ` Jeff Garzik
2003-12-09  9:39 ` Petr Sebor
2003-12-09 19:59 ` J. Ryan Earl
2004-01-14 22:18 ` Greg Stark
2004-01-14 22:56   ` Erik Andersen
2004-01-14 23:31     ` James Courtier-Dutton
2004-01-15  0:41       ` Jeff Garzik
2004-01-15  2:38         ` Erik Andersen
2004-01-18 12:34         ` Martin Schlemmer
2004-01-14 23:32     ` Raphael Rigo
2004-01-15  0:08       ` Erik Steffl
2004-01-15  2:39         ` Matthias Hentges
2004-01-15 21:08           ` Greg Stark
2004-01-14 23:12   ` Erik Steffl
2004-01-18 13:32 ` Witold Krecicki
2004-01-18 18:00   ` Jeff Garzik
2004-01-18 20:33     ` Craig Bradney

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=3FCF7704.2070601@jburgess.uklinux.net \
    --to=lkml@jburgess.uklinux.net \
    --cc=jgarzik@pobox.com \
    --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