From: Clemens Ladisch <clemens@ladisch.de>
To: Jeroen Van den Keybus <jeroen.vandenkeybus@gmail.com>
Cc: Josh Boyer <jwboyer@gmail.com>,
Borislav Petkov <borislav.petkov@amd.com>,
andymatei@gmail.com, "Huang, Shane" <Shane.Huang@amd.com>,
Borislav Petkov <bp@amd64.org>,
linux-kernel@vger.kernel.org
Subject: Re: Unhandled IRQs on AMD E-450
Date: Mon, 30 Apr 2012 11:57:16 +0200 [thread overview]
Message-ID: <4F9E61FC.8070409@ladisch.de> (raw)
In-Reply-To: <CAPRPZsB=axM88+fGkghbh3qxDv=vRQtfrKqT0e59EZPrrS0V+A@mail.gmail.com>
Jeroen Van den Keybus wrote:
> - Detect stuck interrupts after a number (5) of consecutive unhandled
> IRQs within a specified time frame (100ms).
Why 5? This threshold is likely to be too low; fast consecutive interrupts
can easily happen more often with a very busy device, while an actual stuck
interrupt will call the handler in an endless loop and very quickly result
in many thousands of calls.
> --- linux-3.2.16.orig/include/linux/irqdesc.h 2012-04-23
> 00:31:32.000000000 +0200
Your mailer wraps lines; see Documentation/email-clients.txt.
Regards,
Clemens
next prev parent reply other threads:[~2012-04-30 9:57 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.CZQqvHf3CBfYWzhSDPNOWxTTD9w@ifi.uio.no>
[not found] ` <fa.Vmg5vDod2/oKvwyy9BcalhoT+Lo@ifi.uio.no>
2012-04-25 8:35 ` Unhandled IRQs on AMD E-450 andymatei
2012-04-25 8:48 ` Clemens Ladisch
2012-04-27 8:22 ` Borislav Petkov
2012-04-27 8:29 ` Andrei Matei
2012-04-27 11:46 ` Jeroen Van den Keybus
2012-04-27 13:06 ` Josh Boyer
2012-04-27 13:28 ` Jeroen Van den Keybus
2012-04-27 13:49 ` Josh Boyer
2012-04-30 8:29 ` Jeroen Van den Keybus
2012-04-30 9:57 ` Clemens Ladisch [this message]
2012-04-30 10:41 ` Jeroen Van den Keybus
2012-04-30 12:47 ` Clemens Ladisch
2012-05-29 22:20 ` Grant Likely
2012-04-30 10:21 ` Borislav Petkov
2012-04-30 11:35 ` Jeroen Van den Keybus
2012-05-29 23:36 ` Grant Likely
2012-05-30 0:07 ` Thomas Gleixner
2012-05-30 10:44 ` Borislav Petkov
[not found] <fa.Tzg9rJm1oEMGIL8eap99R7gLU4Q@ifi.uio.no>
[not found] ` <fa.Yw7gRhZrXlfCxofC1BHK22C+oTk@ifi.uio.no>
[not found] ` <fa.l7CBcHbzr+l317AuKP87w9mccUk@ifi.uio.no>
[not found] ` <fa.VXfk4ts2TBVKqgBQtfGn6RQHemg@ifi.uio.no>
2012-04-25 8:48 ` andymatei
2011-11-29 21:44 Jeroen Van den Keybus
2011-11-30 8:30 ` Clemens Ladisch
2011-11-30 15:44 ` Borislav Petkov
2011-12-01 8:01 ` Huang, Shane
2011-12-03 20:36 ` Jeroen Van den Keybus
2011-12-04 12:48 ` Clemens Ladisch
2011-12-04 13:36 ` Jeroen Van den Keybus
2011-12-04 13:54 ` Jeroen Van den Keybus
2011-12-04 14:08 ` Jeroen Van den Keybus
2011-12-04 15:06 ` Jeroen Van den Keybus
2011-12-04 16:59 ` Clemens Ladisch
2011-12-06 0:06 ` Jeroen Van den Keybus
2011-12-08 11:33 ` Jeroen Van den Keybus
2011-12-08 12:45 ` Clemens Ladisch
2011-12-08 21:27 ` Jeroen Van den Keybus
2011-12-09 8:22 ` Clemens Ladisch
2011-12-09 11:17 ` Jeroen Van den Keybus
2011-12-09 12:55 ` Clemens Ladisch
2011-12-10 12:10 ` Jeroen Van den Keybus
2011-12-10 17:58 ` Clemens Ladisch
2011-12-11 15:28 ` Jeroen Van den Keybus
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=4F9E61FC.8070409@ladisch.de \
--to=clemens@ladisch.de \
--cc=Shane.Huang@amd.com \
--cc=andymatei@gmail.com \
--cc=borislav.petkov@amd.com \
--cc=bp@amd64.org \
--cc=jeroen.vandenkeybus@gmail.com \
--cc=jwboyer@gmail.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