You are correct it's a 7300 based chipset, and though not the newest
machine going, still a pretty darn quick box that is supposed to support
virtualization.
Here is an lspci from the machine if it's of any help:
00:00.0 Host bridge: Intel Corporation 7300 Chipset Memory Controller Hub
(rev 01)
00:01.0 PCI bridge: Intel Corporation 7300 Chipset PCI Express Port 1 (rev
01)
00:02.0 PCI bridge: Intel Corporation 7300 Chipset PCI Express Port 2 (rev
01)
00:03.0 PCI bridge: Intel Corporation 7300 Chipset PCI Express Port 3 (rev
01)
00:04.0 PCI bridge: Intel Corporation 7300 Chipset PCI Express Port 4 (rev
01)
00:05.0 PCI bridge: Intel Corporation 7300 Chipset PCI Express Port 5 (rev
01)
00:06.0 PCI bridge: Intel Corporation 7300 Chipset PCI Express Port 6 (rev
01)
00:07.0 PCI bridge: Intel Corporation 7300 Chipset PCI Express Port 7 (rev
01)
00:10.0 Host bridge: Intel Corporation 7300 Chipset FSB Registers (rev 01)
00:10.1 Host bridge: Intel Corporation 7300 Chipset FSB Registers (rev 01)
00:10.2 Host bridge: Intel Corporation 7300 Chipset FSB Registers (rev 01)
00:10.3 Host bridge: Intel Corporation 7300 Chipset FSB Registers (rev 01)
00:11.0 Host bridge: Intel Corporation 7300 Chipset Snoop Filter Registers
(rev 01)
00:11.3 Host bridge: Intel Corporation 7300 Chipset Snoop Filter Registers
(rev 01)
00:13.0 Host bridge: Intel Corporation 7300 Chipset Debug and Miscellaneous
Registers (rev 01)
00:15.0 Host bridge: Intel Corporation 7300 Chipset FBD Branch 0 Registers
(rev 01)
00:16.0 Host bridge: Intel Corporation 7300 Chipset FBD Branch 1 Registers
(rev 01)
00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI
Express Root Port 1 (rev 09)
00:1d.0 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI
USB Controller #1 (rev 09)
00:1d.1 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI
USB Controller #2 (rev 09)
00:1d.2 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI
USB Controller #3 (rev 09)
00:1d.3 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI
USB Controller #4 (rev 09)
00:1d.7 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI
USB2 Controller (rev 09)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC
Interface Controller (rev 09)
00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA
IDE Controller (rev 09)
01:03.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
ES1000 (rev 02)
01:04.0 System peripheral: Compaq Computer Corporation Integrated Lights Out
Controller (rev 03)
01:04.2 System peripheral: Compaq Computer Corporation Integrated Lights Out
Processor (rev 03)
01:04.4 USB controller: Hewlett-Packard Company Integrated Lights-Out
Standard Virtual USB Controller
01:04.6 IPMI SMIC interface: Hewlett-Packard Company Integrated Lights-Out
Standard KCS Interface
02:00.0 RAID bus controller: Hewlett-Packard Company Smart Array Controller
(rev 04)
03:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream
Port (rev 01)
03:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X
Bridge (rev 01)
04:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream
Port E1 (rev 01)
04:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream
Port E2 (rev 01)
04:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream
Port E3 (rev 01)
05:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3)
06:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
Gigabit Ethernet (rev 12)
07:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3)
08:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
Gigabit Ethernet (rev 12)
0b:00.0 PCI bridge: PLX Technology, Inc. PEX 8533 32-lane, 6-port PCI
Express Switch (rev aa)
0c:00.0 PCI bridge: PLX Technology, Inc. PEX 8533 32-lane, 6-port PCI
Express Switch (rev aa)
0c:01.0 PCI bridge: PLX Technology, Inc. PEX 8533 32-lane, 6-port PCI
Express Switch (rev aa)
0c:09.0 PCI bridge: PLX Technology, Inc. PEX 8533 32-lane, 6-port PCI
Express Switch (rev aa)
17:00.0 PCI bridge: PLX Technology, Inc. PEX 8533 32-lane, 6-port PCI
Express Switch (rev aa)
18:01.0 PCI bridge: PLX Technology, Inc. PEX 8533 32-lane, 6-port PCI
Express Switch (rev aa)
18:02.0 PCI bridge: PLX Technology, Inc. PEX 8533 32-lane, 6-port PCI
Express Switch (rev aa)
18:08.0 PCI bridge: PLX Technology, Inc. PEX 8533 32-lane, 6-port PCI
Express Switch (rev aa)
18:09.0 PCI bridge: PLX Technology, Inc. PEX 8533 32-lane, 6-port PCI
Express Switch (rev aa)
18:0a.0 PCI bridge: PLX Technology, Inc. PEX 8533 32-lane, 6-port PCI
Express Switch (rev aa)
If there is any other info on the machine that would be useful, let me
know..
---
Howard Leadmon
> -----Original Message-----
> From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On
> Behalf Of Akemi Yagi
> Sent: Thursday, September 05, 2013 6:32 PM
> To: CentOS mailing list
> Subject: Re: Getting a do_IRQ: xx.xxx No irq handler for
vector(irq-
> 1), any ideas?
>
> On Thu, Sep 5, 2013 at 2:50 PM, Howard Leadmon <howard@xxxxxxxxxxx>
> wrote:
> > Well back to the drawing board over here, but I did get a kvm error it
> > seems in the log as well this time. After restarting with the
centosplus
> > kernel as suggested, I still got:
> >
> > do_IRQ: 18.146 No irq handler for vector (irq -1)
> > kvm: 8547: cpu0 disabled perfctr wrmsr: 0xc1 data 0xabcd
> > kvm: 8547: cpu0 disabled perfctr wrmsr: 0xc1 data 0xabcd
> > do_IRQ: 18.104 No irq handler for vector (irq -1)
> > do_IRQ: 3.136 No irq handler for vector (irq -1)
> > do_IRQ: 3.74 No irq handler for vector (irq -1)
> > do_IRQ: 18.162 No irq handler for vector (irq -1)
> > do_IRQ: 18.164 No irq handler for vector (irq -1)
> >
> >
> > The kernel is currently: 2.6.32-358.18.1.el6.centos.plus.x86_64
>
> Just checked the chipset of the HP ProLiant DL580-G5. It looks like
> Intel 7300. According to :
>
> https://access.redhat.com/site/solutions/110053
>
> the issue is related to Intel 5500 and 5520 chipsets. That might be
> the reason the patch did not work. Or it is also possible that the
> patch itself does not work.
>
> Akemi
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
