Forum Discussion

Asemoni67i's avatar
Asemoni67i
Icon for Nimbostratus rankNimbostratus
Sep 23, 2024

Host reset -bigip 7800- i7000

hello 
My device turns on. But when I turn on the host. A lot of time passes, but the host does not turn on. Sometimes it turns on, but after a while it resets again.
Using EUD, the following error was observed.
Please help, where is the problem?

 

EXTLINUX 3.11 0x4a399196 EBIOS Copyright (C) 1994-2005 H. Peter Anvin
F5 End User Diagnostics
LAPIC pending interrupts after 512 EOI
..MP-BIOS bug: 8254 timer not connected to IO-APIC..............................
APIC never delivered???
APIC delivery error (ef)........................................................
APIC never delivered???.........................................................
APIC delivery error (ef)........................................................
APIC never delivered???.........................................................
APIC delivery error (ef)........................................................
APIC never delivered???.........................................................
APIC delivery error (ef)........................................................
APIC never delivered???.........................................................
APIC delivery error (ef)........................................................
APIC never delivered???.........................................................
APIC delivery error (ef)........................................................
APIC never delivered???.........................................................
APIC delivery error (ef)........................................................
APIC never delivered???.........................................................
APIC delivery error (ef)........................................................
APIC never delivered???...............................................
APIC delivery error (ef).
APIC never delivered???
APIC delivery error (ef).
APIC never delivered???
APIC delivery error (ef).
native_cpu_up: bad cpu 12
pci 0000:ff:12.0: BAR 1: error updating (0x90000080 != 0x000080)
pci 0000:ff:12.0: BAR 3: error updating (0x90000090 != 0x000090)
pci 0000:ff:12.0: BAR 5: error updating (0x900000a0 != 0x0000a0)
usb 1-1: device not accepting address 2, error -110
usb 1-1: device not accepting address 3, error -110
usb 1-1: device not accepting address 5, error -110
hub 1-0:1.0: unable to enumerate USB device on port 1

bigip
host reset
  • Sebastiansierra's avatar
    Sebastiansierra
    Icon for MVP rankMVP
    Sep 23, 2024

    Hi Asemoni67i,

     

    You have to open a support case for this issue, it looks like a hardware replacement is required by the description of the problem.

     

    Hope it works

  • F5_Design_Engineer's avatar
    F5_Design_Engineer
    Icon for MVP rankMVP
    Sep 24, 2024

    Hi Asemoni67i,

     

    1. What is the OS version installed.

    2. Have you done any recent OS upgrades. High possibility of some Possible missing firmware .

    3. The error message "pci 0000:ff:12.0: BAR 1: error updating" in the kernel log may indicate a PCI-related issue due to non-compliant BARs. Other similar messages that may appear include:

    • "pci 0000:ff:12.0: BAR 1: error updating (0x90000080 != 0x000080)
    • "pci 0000:ff:12.0: BAR 3: error updating (0x90000080 != 0x000080) 

    4. The issue may be caused by the Peripheral Component Interconnect (PCI) device Power Control Unit's CONFIG_TDP_NOMINAL register being mistakenly implemented at offset 0x10.

     

    5. Can you login to the console  and in BASH mode go to the log file as follows:

     

    cat /var/log/kern.log

     

    And share the output.

    Looks like a straightforward case of the BIOS leaving a device outside the host bridge apertures.

    6. Are you trying to  integrate F5 with Cisco APIC using a Device Package.  

    7. MP-BIOS bug: 8254 timer not connected to IO-APIC..............................
    The "MP-BIOS bug: 8254 timer not connected to IO-APIC" error message shows up on boot on  RHEL servers. My understanding of the situation is that the timer is located elsewhere on the motherboard than where the kernel looks for it.

    8. It is highly likely you will need to raise a F5 Support ticket to obtain a fixed release (Engineering Hotfix).

    9. If that also does not help resolve the issue the last option is to raise for a hardware replacement by raising a request for device RMA.

     

    Please mark it as solution in case if you feel your query has been responded and saved your time and giving pointers toward resolving your issue, as it will help other to use your query scenario to solve their similar issue.

    Best regards

    F5 Design Engineer.