IBM GX3002 Fatal Trap



  • I picked up a few IBM GX3002 units (1Ghz Via C7 based boxes with 4 NICs and 1GB DDR2 RAM) pretty cheap and was going to try and make a few pfSense boxes.

    I downloaded the 512MB image and wrote it to a 52MB CF card, which I placed in the unit.

    When it boots, it starts up ok, then it comes to a Fatal Trap:

    wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
    wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (wpi_fw, 0xc0891b90, 0) error 1
    ACPI Error: A valid RSDP was not found (20100331/tbxfroot-309)
    ACPI: Table initialisation failed: AE_NOT_FOUND
    ACPI: Try disabling either ACPI or apic support.
    cryptosoft0: <software crypto="">on motherboard
    padlock0: <aes-cbc,sha1,sha256>on motherboard
    pcib0: <mptable host-pci="" bridge="">pcibus 0 on motherboard
    pci0: <pci bus="">on pcib0
    pcib1: <mptable pci-pci="" bridge="">at device 1.0 on pci0
    pci1: <pci bus="">on pcib1
    vgapci0: <vga-compatible display="">mem 0xf0000000-0xf3ffffff,0xf4000000-0xf4ffffff irq 16 at device 0.0 on pci1
    rl0: <realtek 10="" 8139="" 100basetx="">port 0xd000-0xd0ff mem 0xf6000000-0xf60000ff irq 16 at device 8.0 on pci0
    miibus0: <mii bus="">on rl0
    rlphy0: <realtek internal="" media="" interface="">PHY 0 on miibus0
    rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    rl0: [ITHREAD]
    rl1: <realtek 10="" 8139="" 100basetx="">port 0xd400-0xd4ff mem 0xf6001000-0xf60010ff irq 17 at device 9.0 on pci0
    miibus1: <mii bus="">on rl1
    rlphy1: <realtek internal="" media="" interface="">PHY 0 on miibus1
    rlphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    rl1: [ITHREAD]
    rl2: <realtek 10="" 8139="" 100basetx="">port 0xd800-0xd8ff mem 0xf6002000-0xf60020ff irq 18 at device 10.0 on pci0
    miibus2: <mii bus="">on rl2
    rlphy2: <realtek internal="" media="" interface="">PHY 0 on miibus2
    rlphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    rl2: [ITHREAD]
    rl3: <realtek 10="" 8139="" 100basetx="">port 0xdc00-0xdcff mem 0xf6003000-0xf60030ff irq 19 at device 11.0 on pci0
    miibus3: <mii bus="">on rl3
    rlphy3: <realtek internal="" media="" interface="">PHY 0 on miibus3
    rlphy3:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    rl3: [ITHREAD]
    atapci0: <via 8237="" udma133="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 15.0 on pci0
    ata0: <ata 0="" channel="">on atapci0
    ata0: [ITHREAD]
    ata1: <ata 1="" channel="">on atapci0
    ata1: [ITHREAD]
    isab0: <pci-isa bridge="">at device 17.0 on pci0
    isa0: <isa bus="">on isab0
    cpu0 on motherboard
    atrtc0: <at real="" time="" clock="">at port 0x70 irq 8 on isa0
    ppc0: parallel port not found.
    uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
    uart0: [FILTER]
    uart0: console (9600,n,8,1)
    uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0
    uart1: [FILTER]
    Timecounter "TSC" frequency 997509757 Hz quality 800
    Timecounters tick every 10.000 msec
    IPsec: Initialized Security Association Processing.
    
    Fatal trap 18: integer divide fault while in kernel mode
    cpuid = 0; apic id = 00
    instruction pointer     = 0x20:0xc0bdc46b
    stack pointer           = 0x28:0xc14208ac
    frame pointer           = 0x28:0xc1420924
    code segment            = base 0x0, limit 0xfffff, type 0x1b
                            = DPL 0, pres 1, def32 1, gran 1
    processor eflags        = interrupt enabled, resume, IOPL = 0
    current process         = 0 (swapper)
    trap number             = 18
    panic: integer divide fault
    cpuid = 0
    Uptime: 1s
    Cannot dump. Device not defined or unavailable.
    Automatic reboot in 15 seconds - press a key on the console to abort</at></isa></pci-isa></ata></ata></via></realtek></mii></realtek></realtek></mii></realtek></realtek></mii></realtek></realtek></mii></realtek></vga-compatible></pci></mptable></pci></mptable></aes-cbc,sha1,sha256></software> 
    

    Does anyone have any thoughts what is causing it? the C7 is a x86 processor, so the images available should work fine.

    I don't think its an individual box because I got the same thing on two different boxes.



  • It looks like a nice option until you notice the Realshit 8139.

    BTW this piece of junk original price is ridiculous.


  • Netgate Administrator

    So take it you don't approve then?  ::)

    @Cougar 281:
    Try disabling as much stuff as you can in the BIOS. Anything you don't need disable it. Since it's complaining about ACPI, try disabling that first.
    Exactly which image are you using? You might try one of the 2.1 snapshots to see if there's any difference.
    Apart from the Realtek NICs it looks like an interesting box. You may have no trouble with them at all.

    Steve



  • @stephenw10:

    So take it you don't approve then?  ::)

    @Cougar 281:
    Try disabling as much stuff as you can in the BIOS. Anything you don't need disable it. Since it's complaining about ACPI, try disabling that first.
    Exactly which image are you using? You might try one of the 2.1 snapshots to see if there's any difference.
    Apart from the Realtek NICs it looks like an interesting box. You may have no trouble with them at all.

    Steve

    I used the 'pfSense-2.0.2-RELEASE-512mb-i386-nanobsd.img.gz' file and wrote it to the CF card under Ubuntu 12.04.

    I've been through the BIOS several times and there is no reference to ACPI, I've disabled everything that isn't needed, but the Fatal Trap still persists.

    And yes, tirsojrp, IBM was charging an arm and a leg for these things, but remember, sometimes it's not the hardware you're paying for, but the software that's running on it that you're paying for. You don't think a Cisco ASA5515 really costs Cisco $3000, do you? You're not paying for the hardware. You're paying for what it can do.



  • @Cougar281:

    You're not paying for the hardware. You're paying for what it can do.

    I know that. They probably tested that hardware in every possible way to ensure it will work flawlessly. But for the price I would expect something better.

    I should also admit that being used to build my own network appliances makes me think this way.



  • @Cougar281:

    When it boots, it starts up ok, then it comes to a Fatal Trap:

    
    . . .
    Timecounter "TSC" frequency 997509757 Hz quality 800
    Timecounters tick every 10.000 msec
    IPsec: Initialized Security Association Processing.
    
    Fatal trap 18: integer divide fault while in kernel mode
    cpuid = 0; apic id = 00
    instruction pointer     = 0x20:0xc0bdc46b
    stack pointer           = 0x28:0xc14208ac
    frame pointer           = 0x28:0xc1420924
    code segment            = base 0x0, limit 0xfffff, type 0x1b
                            = DPL 0, pres 1, def32 1, gran 1
    processor eflags        = interrupt enabled, resume, IOPL = 0
    current process         = 0 (swapper)
    trap number             = 18
    panic: integer divide fault
    cpuid = 0
    Uptime: 1s
    Cannot dump. Device not defined or unavailable.
    Automatic reboot in 15 seconds - press a key on the console to abort
    
    

    Startup on my system reports

    Timecounter "TSC" frequency 797738273 Hz quality 800
    Timecounters tick every 1.000 msec
    IPsec: Initialized Security Association Processing.
    usbus0: 12Mbps Full Speed USB v1.0
    usbus1: 12Mbps Full Speed USB v1.0
    usbus2: 12Mbps Full Speed USB v1.0
    usbus3: 480Mbps High Speed USB v2.0
    ad0: DMA limited to UDMA33, device found non-ATA66 cable
    ugen0.1: <via>at usbus0
    uhub0: <via 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
    ugen1.1: <via>at usbus1

    so it seems the fault occurs before USB devices are reported. USB devices are enabled in the BIOS?

    Does the system have the most up to date BIOS?

    Can you successfully boot Linux?

    What is reported on a verbose boot? (At the timed prompt, type the appropriate number to get a loader prompt, then type

    boot -v

    ).</via></via></via>



  • Might want to try 2.1 also, the newer base OS might behave better on that hardware.



  • Here is what I would do.  Try using this image instead:

    pfSense-memstick-serial-2.0.3-RELEASE-i386-20130412-1022.img

    I currently have this on an MX1004, and it works on the MX0804 as well, one a Intel Celeron 600 MHz and another the VIA 1 GHZ C7.  We work with IBM devices, including the GX3002, but since they are now obsolete, our company gave them away for free, otherwise they will go to the shooting range (yes I know).

    I'll also test this out on a GX here that we no longer need to verify it works when I get the time.  I'm pretty sure it should work fine if its x86 arch.


Log in to reply