SUN T1000: Kernel panic during jumpstart - SUN

This is a discussion on SUN T1000: Kernel panic during jumpstart - SUN ; Hi, we are trying to install Solaris 10 u5 on two purchased T1000 servers with jumpstart. The T1000 gets an IP via RARP and also fetches the kernel correctly via TFTP. The kernel also mounts the NFS root file system ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: SUN T1000: Kernel panic during jumpstart

  1. SUN T1000: Kernel panic during jumpstart

    Hi,

    we are trying to install Solaris 10 u5 on two purchased T1000 servers
    with jumpstart. The T1000 gets an IP via RARP and also fetches the
    kernel correctly via TFTP. The kernel also mounts the NFS root file
    system and starts the installation. After the installer probed bge3 to
    bge0 (to get ip-addresses) the kernel / t1000 panics with the
    following message:

    --- snip ---

    Using RPC Bootparams for network configuration information.
    Attempting to configure interface bge3...
    Skipped interface bge3
    Attempting to configure interface bge2...
    Skipped interface bge2
    Attempting to configure interface bge1...
    Skipped interface bge1
    Attempting to configure interface bge0...
    Configured interface bge0
    |
    panic[cpu0]/thread=2a10062fca0: BAD TRAP: type=31 rp=2a10062f3b0
    addr=1d8 mmu_fsr=0 occurred in module "ip" due to a NULL pointer
    dereference

    sched: trap type = 0x31
    addr=0x1d8
    pid=0, pc=0x7be7b9cc, sp=0x2a10062ec51, tstate=0x4480001607,
    context=0x0
    g1-g7: 0, 80000000, 0, 7bf2d800, 20, 0, 2a10062fca0

    000002a10062f0d0 unix:die+78 (31, 2a10062f3b0, 1d8, 0, 2a10062f190,
    1096800)
    %l0-3: 0000000000000000 0000000000000031 0000000001000000
    0000000000002000
    %l4-7: 0000000001831aa0 0000000001831800 0000000000000005
    0000000000000001
    000002a10062f1b0 unix:trap+9e4 (2a10062f3b0, 0, 5, 1c00, 0, 1)
    %l0-3: 0000000000000000 00000000018594e0 0000000000000031
    0000000000000000
    %l4-7: ffffffffffffe000 000000000191a000 0000000000000005
    0000000000000001
    000002a10062f300 unix:ktl0+64 (20, 600109b62e8, 600109b63d8,
    6001221d8c8, 60010b08a88, 0)
    %l0-3: 000000000180c000 0000000000000000 0000004480001607
    0000000001020308
    %l4-7: 0000000000000000 000000000191a000 0000000000000000
    000002a10062f3b0
    000002a10062f450 20 (2a10062f670, 0, 0, 0, 1, 600109b6320)
    %l0-3: 0000000000000000 0000000000000000 0000000000000040
    00000600109b7428
    %l4-7: 0000000000000000 000000000191a000 0000000000000000
    000006001089a000
    000002a10062f520 ip:ire_forward+524 (20, 600109b62e8, 600109b63d8,
    6001221d8c8, 60010b08a88, 6001089a000)
    %l0-3: 0000000000000000 000000005389603f 0000000000000040
    0000000000000000
    %l4-7: 0000000001935400 000000000191a000 0000000000000000
    0000000000000000
    000002a10062f680 ip:ip_fast_forward+d8 (e0000000, 5389603f,
    3000336e668, 6001226e400, 0, 1)
    %l0-3: 0000000000000000 0000000000000000 000006001089a000
    0000000000000000
    %l4-7: 00000000e0000000 0000000000000001 0000000053896018
    000006001218f460
    000002a10062f7a0 ip:ip_input+5a0 (6001218f460, 300017f0088, 0,
    3000336e668, 0, 0)
    %l0-3: 0000000000000000 0000000000000000 0000000000000000
    000006001089a000
    %l4-7: 00000000e0000000 0000000000000001 0000000000000000
    0000000000000000
    000002a10062f910 dls:soft_ring_drain+7c (600109b5e40, 6001226e400, 2,
    2000000, 2, 0)
    %l0-3: 0000000000000000 0000000000000000 0000000000000005
    000003000336e668
    %l4-7: 00000300017f0088 000000007be1bbc4 ffffffffffffffff
    0000000000000000
    000002a10062f9c0 dls:soft_ring_worker+64 (600109b5e40, 0, 2,
    600109b5e8c, 0, 2a10062fa8a)
    %l0-3: 000002a10062fa88 0000000000000000 0000000000000000
    0000000000000000
    %l4-7: 0000000000000000 0000000000000000 0000000000000002
    0000000000000000

    syncing file systems... done
    skipping system dump - no dump device configured
    rebooting...

    --- snip ---

    The system firmware is already updated to version 6.6.1.

    sc> showhost
    Sun-Fire-T1000 System Firmware 6.6.1 2008/02/11 15:54

    Host flash versions:
    OBP 4.28.1 2008/02/11 13:04
    Hypervisor 1.6.1 2008/02/11 12:15
    POST 4.28.1 2008/02/11 13:29

    If I press ctrl-c during probing bge3 to bge0 I get an root shell
    which works without a panic. Does this help somehow?

    Thanks in advance for any hint or help!

    P.S.: I'm using the sun4v netimage and not sun4u

  2. Re: SUN T1000: Kernel panic during jumpstart

    On 3 May, 02:18, Niels wrote:
    > Hi,
    >
    > we are trying to install Solaris 10 u5 on two purchased T1000 servers
    > with jumpstart. The T1000 gets an IP via RARP and also fetches the
    > kernel correctly via TFTP. The kernel also mounts the NFS root file
    > system and starts the installation. After the installer probed bge3 to
    > bge0 (to get ip-addresses) the kernel / t1000 panics with the
    > following message:
    >
    > --- snip ---
    >
    > Using RPC Bootparams for network configuration information.
    > Attempting to configure interface bge3...
    > Skipped interface bge3
    > Attempting to configure interface bge2...
    > Skipped interface bge2
    > Attempting to configure interface bge1...
    > Skipped interface bge1
    > Attempting to configure interface bge0...
    > Configured interface bge0
    > |
    > panic[cpu0]/thread=2a10062fca0: BAD TRAP: type=31 rp=2a10062f3b0
    > addr=1d8 mmu_fsr=0 occurred in module "ip" due to a NULL pointer
    > dereference
    >
    > sched: trap type = 0x31
    > addr=0x1d8
    > pid=0, pc=0x7be7b9cc, sp=0x2a10062ec51, tstate=0x4480001607,
    > context=0x0
    > g1-g7: 0, 80000000, 0, 7bf2d800, 20, 0, 2a10062fca0
    >
    > 000002a10062f0d0 unix:die+78 (31, 2a10062f3b0, 1d8, 0, 2a10062f190,
    > 1096800)
    > %l0-3: 0000000000000000 0000000000000031 0000000001000000
    > 0000000000002000
    > %l4-7: 0000000001831aa0 0000000001831800 0000000000000005
    > 0000000000000001
    > 000002a10062f1b0 unix:trap+9e4 (2a10062f3b0, 0, 5, 1c00, 0, 1)
    > %l0-3: 0000000000000000 00000000018594e0 0000000000000031
    > 0000000000000000
    > %l4-7: ffffffffffffe000 000000000191a000 0000000000000005
    > 0000000000000001
    > 000002a10062f300 unix:ktl0+64 (20, 600109b62e8, 600109b63d8,
    > 6001221d8c8, 60010b08a88, 0)
    > %l0-3: 000000000180c000 0000000000000000 0000004480001607
    > 0000000001020308
    > %l4-7: 0000000000000000 000000000191a000 0000000000000000
    > 000002a10062f3b0
    > 000002a10062f450 20 (2a10062f670, 0, 0, 0, 1, 600109b6320)
    > %l0-3: 0000000000000000 0000000000000000 0000000000000040
    > 00000600109b7428
    > %l4-7: 0000000000000000 000000000191a000 0000000000000000
    > 000006001089a000
    > 000002a10062f520 ip:ire_forward+524 (20, 600109b62e8, 600109b63d8,
    > 6001221d8c8, 60010b08a88, 6001089a000)
    > %l0-3: 0000000000000000 000000005389603f 0000000000000040
    > 0000000000000000
    > %l4-7: 0000000001935400 000000000191a000 0000000000000000
    > 0000000000000000
    > 000002a10062f680 ip:ip_fast_forward+d8 (e0000000, 5389603f,
    > 3000336e668, 6001226e400, 0, 1)
    > %l0-3: 0000000000000000 0000000000000000 000006001089a000
    > 0000000000000000
    > %l4-7: 00000000e0000000 0000000000000001 0000000053896018
    > 000006001218f460
    > 000002a10062f7a0 ip:ip_input+5a0 (6001218f460, 300017f0088, 0,
    > 3000336e668, 0, 0)
    > %l0-3: 0000000000000000 0000000000000000 0000000000000000
    > 000006001089a000
    > %l4-7: 00000000e0000000 0000000000000001 0000000000000000
    > 0000000000000000
    > 000002a10062f910 dls:soft_ring_drain+7c (600109b5e40, 6001226e400, 2,
    > 2000000, 2, 0)
    > %l0-3: 0000000000000000 0000000000000000 0000000000000005
    > 000003000336e668
    > %l4-7: 00000300017f0088 000000007be1bbc4 ffffffffffffffff
    > 0000000000000000
    > 000002a10062f9c0 dls:soft_ring_worker+64 (600109b5e40, 0, 2,
    > 600109b5e8c, 0, 2a10062fa8a)
    > %l0-3: 000002a10062fa88 0000000000000000 0000000000000000
    > 0000000000000000
    > %l4-7: 0000000000000000 0000000000000000 0000000000000002
    > 0000000000000000
    >
    > syncing file systems... done
    > skipping system dump - no dump device configured
    > rebooting...
    >
    > --- snip ---
    >
    > The system firmware is already updated to version 6.6.1.
    >
    > sc> showhost
    > Sun-Fire-T1000 System Firmware 6.6.1 2008/02/11 15:54
    >
    > Host flash versions:
    > OBP 4.28.1 2008/02/11 13:04
    > Hypervisor 1.6.1 2008/02/11 12:15
    > POST 4.28.1 2008/02/11 13:29
    >
    > If I press ctrl-c during probing bge3 to bge0 I get an root shell
    > which works without a panic. Does this help somehow?
    >
    > Thanks in advance for any hint or help!
    >
    > P.S.: I'm using the sun4v netimage and not sun4u


    Not sure whats up - mine t1000 had Solaris 10 u5 just fine?

    Could be a corrupted netboot install?

    You jumpstarted anything else on to these boxes?

  3. Re: SUN T1000: Kernel panic during jumpstart

    In comp.unix.solaris Niels wrote:
    > kernel correctly via TFTP. The kernel also mounts the NFS root file
    > system and starts the installation. After the installer probed bge3 to


    What is the NFS server? I'm assuming you don't have one T1000 jumpstarting
    the other.

    --
    Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/

  4. Re: SUN T1000: Kernel panic during jumpstart

    On Sat, 03 May 2008 07:06:07 -0700, kangcool wrote:

    > On 3 May, 02:18, Niels wrote:
    >> Hi,
    >>
    >> we are trying to install Solaris 10 u5 on two purchased T1000 servers
    >> with jumpstart. The T1000 gets an IP via RARP and also fetches the
    >> kernel correctly via TFTP. The kernel also mounts the NFS root file
    >> system and starts the installation. After the installer probed bge3 to
    >> bge0 (to get ip-addresses) the kernel / t1000 panics with the
    >> following message:
    >>
    >> --- snip ---
    >>
    >> Using RPC Bootparams for network configuration information.
    >> Attempting to configure interface bge3...
    >> Skipped interface bge3
    >> Attempting to configure interface bge2...
    >> Skipped interface bge2
    >> Attempting to configure interface bge1...
    >> Skipped interface bge1
    >> Attempting to configure interface bge0...
    >> Configured interface bge0
    >> |
    >> panic[cpu0]/thread=2a10062fca0: BAD TRAP: type=31 rp=2a10062f3b0
    >> addr=1d8 mmu_fsr=0 occurred in module "ip" due to a NULL pointer
    >> dereference
    >>
    >> sched: trap type = 0x31
    >> addr=0x1d8
    >> pid=0, pc=0x7be7b9cc, sp=0x2a10062ec51, tstate=0x4480001607,
    >> context=0x0
    >> g1-g7: 0, 80000000, 0, 7bf2d800, 20, 0, 2a10062fca0
    >>
    >> 000002a10062f0d0 unix:die+78 (31, 2a10062f3b0, 1d8, 0, 2a10062f190,
    >> 1096800)
    >> %l0-3: 0000000000000000 0000000000000031 0000000001000000
    >> 0000000000002000
    >> %l4-7: 0000000001831aa0 0000000001831800 0000000000000005
    >> 0000000000000001
    >> 000002a10062f1b0 unix:trap+9e4 (2a10062f3b0, 0, 5, 1c00, 0, 1)
    >> %l0-3: 0000000000000000 00000000018594e0 0000000000000031
    >> 0000000000000000
    >> %l4-7: ffffffffffffe000 000000000191a000 0000000000000005
    >> 0000000000000001
    >> 000002a10062f300 unix:ktl0+64 (20, 600109b62e8, 600109b63d8,
    >> 6001221d8c8, 60010b08a88, 0)
    >> %l0-3: 000000000180c000 0000000000000000 0000004480001607
    >> 0000000001020308
    >> %l4-7: 0000000000000000 000000000191a000 0000000000000000
    >> 000002a10062f3b0
    >> 000002a10062f450 20 (2a10062f670, 0, 0, 0, 1, 600109b6320)
    >> %l0-3: 0000000000000000 0000000000000000 0000000000000040
    >> 00000600109b7428
    >> %l4-7: 0000000000000000 000000000191a000 0000000000000000
    >> 000006001089a000
    >> 000002a10062f520 ip:ire_forward+524 (20, 600109b62e8, 600109b63d8,
    >> 6001221d8c8, 60010b08a88, 6001089a000)
    >> %l0-3: 0000000000000000 000000005389603f 0000000000000040
    >> 0000000000000000
    >> %l4-7: 0000000001935400 000000000191a000 0000000000000000
    >> 0000000000000000
    >> 000002a10062f680 ip:ip_fast_forward+d8 (e0000000, 5389603f,
    >> 3000336e668, 6001226e400, 0, 1)
    >> %l0-3: 0000000000000000 0000000000000000 000006001089a000
    >> 0000000000000000
    >> %l4-7: 00000000e0000000 0000000000000001 0000000053896018
    >> 000006001218f460
    >> 000002a10062f7a0 ip:ip_input+5a0 (6001218f460, 300017f0088, 0,
    >> 3000336e668, 0, 0)
    >> %l0-3: 0000000000000000 0000000000000000 0000000000000000
    >> 000006001089a000
    >> %l4-7: 00000000e0000000 0000000000000001 0000000000000000
    >> 0000000000000000
    >> 000002a10062f910 dls:soft_ring_drain+7c (600109b5e40, 6001226e400, 2,
    >> 2000000, 2, 0)
    >> %l0-3: 0000000000000000 0000000000000000 0000000000000005
    >> 000003000336e668
    >> %l4-7: 00000300017f0088 000000007be1bbc4 ffffffffffffffff
    >> 0000000000000000
    >> 000002a10062f9c0 dls:soft_ring_worker+64 (600109b5e40, 0, 2,
    >> 600109b5e8c, 0, 2a10062fa8a)
    >> %l0-3: 000002a10062fa88 0000000000000000 0000000000000000
    >> 0000000000000000
    >> %l4-7: 0000000000000000 0000000000000000 0000000000000002
    >> 0000000000000000
    >>
    >> syncing file systems... done
    >> skipping system dump - no dump device configured
    >> rebooting...
    >>
    >> --- snip ---
    >>



    panic[cpu0]/thread=2a10062fca0: BAD TRAP: type=31 rp=2a10062f3b0
    >> addr=1d8 mmu_fsr=0 occurred in module "ip" due to a NULL pointer
    >> dereference


    There's your problem. Google "ip" module Solaris and you'll find
    Sun Alert and Security Discussion - problem with module ip.

+ Reply to Thread