From: Heiko Schocher <hs@denx.de>
To: Tejun Heo <htejun@gmail.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org
Subject: Re: ata, pcmcia: problem with irq and ata_dev_read_id()
Date: Mon, 05 Jul 2010 11:25:45 +0200 [thread overview]
Message-ID: <4C31A519.7030806@denx.de> (raw)
In-Reply-To: <4C319D31.60705@gmail.com>
Hello Tejun,
Tejun Heo wrote:
> On 07/05/2010 10:26 AM, Heiko Schocher wrote:
>> IRQ 26: too many spurious IRQs, disabling and polling for 10k 10msec intervals.
>> IRQ 26: system performance may be affected
>> handlers:
>> [<c0198d00>] (ata_sff_interrupt+0x0/0x204)
>
> Yeah, that's the new polling code kicking in. If the IRQ problem
> doesn't persiste (which should be the case here), polling will step
> down after a while and everything will return to normal. If you keep
> the system running more than ten minutes and use the CF device, does
> the kernel complain anymore?
No, I can use the CF while kernel is in polling mode, also if the
kernel switched back to irq mode:
Log, direct after kernel is up:
[...]
Freeing unused kernel memory: 132k init
-bash-3.2# mount -t vfat /dev/sdb1 /home/hs/mnt
-bash-3.2# cat /proc/uptime
62.08 14.08
-bash-3.2# cat /proc/interrupts
CPU0
17: 0 CPM PIC Level error
18: 0 MPC8XX SIU Level tbint
19: 308 CPM PIC Level cpm_uart
21: 4 CPM PIC Level mpc8xxx_spi
22: 0 MPC8XX SIU Edge ads7846
23: 20043 MPC8XX SIU Level fs_enet-mac
24: 0 MPC8XX SIU Level m8xx-pcmcia
25: 9 MPC8XX SIU Level pata_pcmcia
26: 10000 MPC8XX SIU Level pata_pcmcia
27: 129 CPM PIC Level cpm_i2c
LOC: 6408 Local timer interrupts
SPU: 0 Spurious interrupts
CNT: 0 Performance monitoring interrupts
MCE: 0 Machine check exceptions
-bash-3.2#
No irq is used.
-bash-3.2# dmesg
[...]
Freeing unused kernel memory: 132k init
IRQ 26: spurious polling finished, reenabling IRQ
-bash-3.2#
Now it is back in irq mode:
-bash-3.2# cat /proc/uptime
419.65 370.56
-bash-3.2#
-bash-3.2# mount -t vfat /dev/sdb1 /home/hs/mnt
-bash-3.2# cat /proc/interrupts
CPU0
17: 0 CPM PIC Level error
18: 0 MPC8XX SIU Level tbint
19: 956 CPM PIC Level cpm_uart
21: 4 CPM PIC Level mpc8xxx_spi
22: 0 MPC8XX SIU Edge ads7846
23: 20414 MPC8XX SIU Level fs_enet-mac
24: 0 MPC8XX SIU Level m8xx-pcmcia
25: 9 MPC8XX SIU Level pata_pcmcia
26: 10033 MPC8XX SIU Level pata_pcmcia
27: 129 CPM PIC Level cpm_i2c
LOC: 10880 Local timer interrupts
SPU: 0 Spurious interrupts
CNT: 0 Performance monitoring interrupts
MCE: 0 Machine check exceptions
-bash-3.2#
Now it uses the irq ...
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2010-07-05 9:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 5:57 ata, pcmcia: problem with irq and ata_dev_read_id() Heiko Schocher
2010-05-31 23:55 ` Robert Hancock
2010-06-28 5:31 ` Heiko Schocher
2010-07-02 15:01 ` Tejun Heo
2010-07-05 8:26 ` Heiko Schocher
2010-07-05 8:52 ` Tejun Heo
2010-07-05 9:25 ` Heiko Schocher [this message]
2010-07-05 9:33 ` Tejun Heo
2010-07-26 12:59 ` Heiko Schocher
2010-07-26 13:11 ` Tejun Heo
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=4C31A519.7030806@denx.de \
--to=hs@denx.de \
--cc=hancockrwd@gmail.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).