* RE: acpi nic card flapping
@ 2006-11-25 7:34 Yong Lee
2006-11-28 12:00 ` Thomas Renninger
2006-11-29 7:14 ` Kenji Kaneshige
0 siblings, 2 replies; 4+ messages in thread
From: Yong Lee @ 2006-11-25 7:34 UTC (permalink / raw)
To: linux-acpi
Hi all,
I’m hoping that someone out there can lend me a hand with a problem that we
were seeing. I’m not very familiar with the acpi tool so please bear with
me.
We had an outage where we could not ssh into our web server and we had to do
a reboot from our console to get things running again. It looks like an
acpi problem and I’m trying to figure out what was going on. Was ACPI going
crazy or was it trying to report a problem condition that we were not aware
of.
What we saw in the dmesg log was this :
shpchp: Address64 -------- Resource unparsed
shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
shpchp: acpi_shpchprm: Slot sun(0) at s:b:d:f=0x00:04:1f:00
shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
During the time of the outage we saw from our router logs that the
connection to the server was going up and down.
There was a lot of other messages on the console but our sysadmin guy didn’t
capture this.
We’re running redhat linux 2.6.9-34.0.2.ELsmp on intel xeon processors.
We have 2 intel nic cards : Intel Corporation 82541GI/PI Gigabit Ethernet
Controller (rev 05)
Any light you can shed on this problem would be great. Note that while the
kacpid kernel thread is running the acpid daemon was shut off during this
incident.
Many thanks,
Yong.
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: acpi nic card flapping
2006-11-25 7:34 acpi nic card flapping Yong Lee
@ 2006-11-28 12:00 ` Thomas Renninger
2006-11-29 7:14 ` Kenji Kaneshige
1 sibling, 0 replies; 4+ messages in thread
From: Thomas Renninger @ 2006-11-28 12:00 UTC (permalink / raw)
To: Yong Lee; +Cc: linux-acpi
On Fri, 2006-11-24 at 23:34 -0800, Yong Lee wrote:
> Hi all,
>
> I’m hoping that someone out there can lend me a hand with a problem that we
> were seeing. I’m not very familiar with the acpi tool so please bear with
> me.
>
> We had an outage where we could not ssh into our web server and we had to do
> a reboot from our console to get things running again. It looks like an
> acpi problem and I’m trying to figure out what was going on. Was ACPI going
> crazy or was it trying to report a problem condition that we were not aware
> of.
>
> What we saw in the dmesg log was this :
>
> shpchp: Address64 -------- Resource unparsed
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_shpchprm: Slot sun(0) at s:b:d:f=0x00:04:1f:00
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
>
> During the time of the outage we saw from our router logs that the
> connection to the server was going up and down.
>
> There was a lot of other messages on the console but our sysadmin guy didn’t
> capture this.
Hmm, so that may not be the root cause of your problems?
>
> We’re running redhat linux 2.6.9-34.0.2.ELsmp on intel xeon processors.
> We have 2 intel nic cards : Intel Corporation 82541GI/PI Gigabit Ethernet
> Controller (rev 05)
>
> Any light you can shed on this problem would be great. Note that while the
> kacpid kernel thread is running the acpid daemon was shut off during this
> incident.
If the pci hotplug module (shpchp, difficult to spell...) really causes
this it might be kernel or a BIOS bug. If this is a production machine
that is already running for a while, I would not risk a BIOS update or
waste time with kernel compilations. Best/simplest would be to remove
the module out of /lib/modules/xy/kernel/drivers/pci/hotplug/shpchp.ko
directory if you do not need PCI hotplug urgently.
Hope that works...
Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: acpi nic card flapping
2006-11-25 7:34 acpi nic card flapping Yong Lee
2006-11-28 12:00 ` Thomas Renninger
@ 2006-11-29 7:14 ` Kenji Kaneshige
2006-11-30 6:23 ` Yong Lee
1 sibling, 1 reply; 4+ messages in thread
From: Kenji Kaneshige @ 2006-11-29 7:14 UTC (permalink / raw)
To: Yong Lee; +Cc: linux-acpi
Hi Yong Lee,
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
This message means OSHP method is not found under _SB.PCI0.PBLO. This
message itself is harmless, I think.
But, IIRC, old shpchp driver had a problem that loading shpchp driver
may cause a master-abort on some ongoing PCI cards. The root cause is
old shpchp driver writes 0xFFFFFFFF to BARs of some ongoing PCI cards
to know the size of resources assigned to the cards at modprobe time.
I don't know this is related to your problem. But I hope this info is
helpful for you.
Thanks,
Kenji Kaneshige
Yong Lee wrote:
> Hi all,
>
> I’m hoping that someone out there can lend me a hand with a problem that we
> were seeing. I’m not very familiar with the acpi tool so please bear with
> me.
>
> We had an outage where we could not ssh into our web server and we had to do
> a reboot from our console to get things running again. It looks like an
> acpi problem and I’m trying to figure out what was going on. Was ACPI going
> crazy or was it trying to report a problem condition that we were not aware
> of.
>
> What we saw in the dmesg log was this :
>
> shpchp: Address64 -------- Resource unparsed
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_shpchprm: Slot sun(0) at s:b:d:f=0x00:04:1f:00
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
>
> During the time of the outage we saw from our router logs that the
> connection to the server was going up and down.
>
> There was a lot of other messages on the console but our sysadmin guy didn’t
> capture this.
>
> We’re running redhat linux 2.6.9-34.0.2.ELsmp on intel xeon processors.
> We have 2 intel nic cards : Intel Corporation 82541GI/PI Gigabit Ethernet
> Controller (rev 05)
>
> Any light you can shed on this problem would be great. Note that while the
> kacpid kernel thread is running the acpid daemon was shut off during this
> incident.
>
> Many thanks,
> Yong.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: acpi nic card flapping
2006-11-29 7:14 ` Kenji Kaneshige
@ 2006-11-30 6:23 ` Yong Lee
0 siblings, 0 replies; 4+ messages in thread
From: Yong Lee @ 2006-11-30 6:23 UTC (permalink / raw)
To: 'Kenji Kaneshige'; +Cc: linux-acpi
Thanks all for the feedback. We're having problems with acpi turned off
leading me to suspect that acpi may not be the issue at all. We're doing a
swap of the hardrive into a new identical machine to see if we can isolate
it as a hardware problem.
-----Original Message-----
From: linux-acpi-owner@vger.kernel.org
[mailto:linux-acpi-owner@vger.kernel.org] On Behalf Of Kenji Kaneshige
Sent: Tuesday, November 28, 2006 11:14 PM
To: Yong Lee
Cc: linux-acpi@vger.kernel.org
Subject: Re: acpi nic card flapping
Hi Yong Lee,
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
This message means OSHP method is not found under _SB.PCI0.PBLO. This
message itself is harmless, I think.
But, IIRC, old shpchp driver had a problem that loading shpchp driver
may cause a master-abort on some ongoing PCI cards. The root cause is
old shpchp driver writes 0xFFFFFFFF to BARs of some ongoing PCI cards
to know the size of resources assigned to the cards at modprobe time.
I don't know this is related to your problem. But I hope this info is
helpful for you.
Thanks,
Kenji Kaneshige
Yong Lee wrote:
> Hi all,
>
> I'm hoping that someone out there can lend me a hand with a problem that
we
> were seeing. I'm not very familiar with the acpi tool so please bear with
> me.
>
> We had an outage where we could not ssh into our web server and we had to
do
> a reboot from our console to get things running again. It looks like an
> acpi problem and I'm trying to figure out what was going on. Was ACPI
going
> crazy or was it trying to report a problem condition that we were not
aware
> of.
>
> What we saw in the dmesg log was this :
>
> shpchp: Address64 -------- Resource unparsed
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_shpchprm: Slot sun(0) at s:b:d:f=0x00:04:1f:00
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.PBLO OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: acpi_pciehprm:\_SB_.PCI0.VPR0 OSHP fails=0x5
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: shpc_init : shpc_cap_offset == 0
> shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
>
> During the time of the outage we saw from our router logs that the
> connection to the server was going up and down.
>
> There was a lot of other messages on the console but our sysadmin guy
didn't
> capture this.
>
> We're running redhat linux 2.6.9-34.0.2.ELsmp on intel xeon processors.
> We have 2 intel nic cards : Intel Corporation 82541GI/PI Gigabit Ethernet
> Controller (rev 05)
>
> Any light you can shed on this problem would be great. Note that while
the
> kacpid kernel thread is running the acpid daemon was shut off during this
> incident.
>
> Many thanks,
> Yong.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-11-30 6:23 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-11-25 7:34 acpi nic card flapping Yong Lee
2006-11-28 12:00 ` Thomas Renninger
2006-11-29 7:14 ` Kenji Kaneshige
2006-11-30 6:23 ` Yong Lee
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox