From: andymatei@gmail.com
To: fa.linux.kernel@googlegroups.com
Cc: Clemens Ladisch <clemens@ladisch.de>,
"Huang, Shane" <Shane.Huang@amd.com>,
Borislav Petkov <bp@amd64.org>,
"Nguyen, Dong" <Dong.Nguyen@amd.com>,
linux-kernel@vger.kernel.org
Subject: Re: Unhandled IRQs on AMD E-450
Date: Wed, 25 Apr 2012 01:35:03 -0700 (PDT) [thread overview]
Message-ID: <14969994.2790.1335342903511.JavaMail.geo-discussion-forums@vbbfr18> (raw)
In-Reply-To: <fa.Vmg5vDod2/oKvwyy9BcalhoT+Lo@ifi.uio.no>
Hello all,
I am not that good in Linux as you guys are but here it goes. I have bought the Asus E45M1-M PRO to use in my home storage. I had 2 PCI Intel NICs that i wanted to use for iSCSI traffic that goes to 2 ESXi servers. 4 Seagate@2TB and one WD for OS. I use Openfiler as a storage appliance. Problem appears after 20-30 minutes after starting the PC. I get "Disabling IRQ 16" and "Disabling IRQ 19". SATA disks drop from 130MB/s to 2MB/s speed, web interface does not work anymore. After reboot everything works but goes down again after 30 minutes. Is there a patch or something that resolves this issue yet?
Thanks,
Andrei
next parent reply other threads:[~2012-04-25 9:10 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 ` andymatei [this message]
2012-04-25 8:48 ` Unhandled IRQs on AMD E-450 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
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=14969994.2790.1335342903511.JavaMail.geo-discussion-forums@vbbfr18 \
--to=andymatei@gmail.com \
--cc=Dong.Nguyen@amd.com \
--cc=Shane.Huang@amd.com \
--cc=bp@amd64.org \
--cc=clemens@ladisch.de \
--cc=fa.linux.kernel@googlegroups.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