Kernel Panic after LPFC driver upgrade

From: Sebastien Daubigne (sebastien.daubigne_at_atosorigin.com)
Date: 10/07/05

  • Next message: Martin Wheatley: "Cleaning wtmp and wtmpx" 
    To: <sunmanagers@sunmanagers.org>
Date: Fri, 7 Oct 2005 11:54:25 +0200

    Hi,

    After upgrading lpfc driver (for Emulex LP8000 V2) from 5.02c to 6.02f on a
    SUN E450 (Solaris 8), the kernel panics at early boot during LUN scanning.

    On a SUN V280R with the same OS level, same patch level (showrev -p are
    identical except 2 Netbackup patchs on E450), the 6.02f drivers works like a
    charm.
    I tried the last lpfc version (6.02g) on E450, with the same error.
    OBP level on E450 is the last one (3.30.0), and the driver requires 3.26+.

    I couldn't make 6.0x lpfc version work on the E450, so I went back to 5.02c.

    The only differences between E450 kernel space config and V280R config are :
    - some SUN hardware-specific drivers (network cards, USB, etc.)
    - 2 third-party hardware drivers : "sg" driver (SCSI driver for Netbackup)
    and "gd" driver (SCSI driver for a CD burning software called "Gear 2.0")

    I suspect some kernel space conflict between "sg"/"gd" and "lpfc 6.0x"
    drivers.

    I will try to disable "sg"/"gd" driver loading via "exclude" directive in
    /etc/system, and see it it helps.
    Do you have another idea ?

    Here is the kernel panic message :

    panic[cpu0]/thread=2a10007dd20: BAD TRAP: type=31 rp=2a10007d510
    addr=3f00000000

    : trap type = 0x31
    addr=0x3f00000008
    pid=0, pc=0x7803dc00, sp=0x2a10007cdb1, tstate=0x480001607, context=0x0
    g1-g7: 10034210, 0, fffe0000, 30001cca850, 78066800, 0, 2a10007dd20

    000002a10007d120 unix:die+a4 (31, 2a10007d510, 3f00000008, 0, 2a10007d510,
    d877)
      %l0-3: 0000000000000008 0000000000000f01 00000300000a88c8 fffffffffffffffe
      %l4-7: 00000300000a9c08 000002a1001056dc 00000000104ad660 0000000000000000
    000002a10007d200 unix:trap+8b8 (3f00000000, 1, 5, 0, 2a10007d510, 0)
      %l0-3: 0000000000000001 0000000000000000 00000000104245b0 0000000000000000
      %l4-7: 0000000000000031 0000000000000000 0000000000010000 0000030001114000
    000002a10007d340 unix:sfmmu_tsb_miss+66c (104293b0, 0, 3000016df88, 0,
    3000016d)
      %l0-3: 0000003f00000000 0000000000000004 0000000000000000 0000031000047100
      %l4-7: 0000003f00000000 0000030001114000 0000000000000000 0000003f00000003
    000002a10007d460 unix:prom_rtt+0 (30001cca000, 78066b48, 78066b10, 78066800,
    30)
      %l0-3: 0000000000000000 0000000000001400 0000000480001607 000000001001a8bc
      %l4-7: 000000001041bc00 0000030001cca8c0 0000000000000006 000002a10007d510
    000002a10007d5b0 lpfc:lpfc_nlp_list+3b4 (2, 30001cca860, 300002dcf68,
    300011140)
      %l0-3: 000000007801a738 0000000000000002 0000000000000000 0000030001114018
      %l4-7: 0000030001114380 0000030001114000 0000030001114000 0000030001114380
    000002a10007d680 lpfc:lpfc_cmpl_els_plogi+304 (30001e89228, 30001cca000,
    300011)
      %l0-3: 0000000000000001 0000030001ec7840 8000000000000000 0000030001cca000
      %l4-7: 0000030001cca860 0000030001dba400 0000030001114380 0000000078042c1c
    000002a10007d760 lpfc:elx_sli_handle_ring_event+4f4 (30001114000,
    300011140d8, )
      %l0-3: 0000030001e89048 000000000000ff00 0000030001e88da8 0000000000000001
      %l4-7: 0000000000000016 0000030001e88da8 0000030001114000 0000030001114380
    000002a10007d8f0 lpfc:elx_sli_intr+154 (110, 30001114270, 30001114000, fffe,
    2a)
      %l0-3: 0000000000000003 0000000000000008 0000000000000f01 000000001000a408
      %l4-7: 0000030002717ac8 0000030002d8b0f8 0000000000000000 000002a100105290
    000002a10007d9a0 lpfc:lpfc_intr_handler+4c (30001114000, 30001114000, 1,
    100fea)
      %l0-3: 0000000000000001 0000000000000f01 00000300000a88c8 fffffffffffffffe
      %l4-7: 00000300000a9c08 000002a1001056dc 00000000104ad660 0000000000000000
    000002a10007da60 pcipsy:pci_intr_wrapper+80 (78068fe0, 78069018,
    3000055f190, 3)
      %l0-3: 0000000078019d80 0000000000000000 00000300003b7c80 0000000000000014
      %l4-7: 00000300000b06d8 0000000000000370 0000030002d85c40 000000001046f848 

    --
Sebastien DAUBIGNE
Sebastien.daubigne@atosorigin.com - +33(0)5.57.26.56.36
AtosOrigin Infogerance - IMS/ERP/Pessac
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
  • Next message: Martin Wheatley: "Cleaning wtmp and wtmpx"

    Relevant Pages

    • Re: CompactFlash and Solaris[9-10]
      ... > If the hardware vendors treat the details of how to talk to their hardware ... Sun does still have enough weight to throw around or at least entice HW ... vendors to release the drivers. ... Personally I couldn't care less if all the drivers were just ...
      (comp.unix.solaris)
    • Re: Linux Advocates Fear Solaris 10.
      ... >> Why did Donald Becker attack Sun? ... > This driver porting kit violated the license on the code. ... But if Sun released the porting kit under the GPL, ... as Donald Becker's drivers. ...
      (comp.unix.solaris)
    • Emulex HBA Leadville Drivers and STMS
      ... I understand that Sun is now selling OEM Emulex HBAs. ... Does this mean my long wait for Leadville complaint drivers for Emulex ...
      (SunManagers)
    • Driver Compatibility - Sound Blaster
      ... I have a suggestion for Sun, OpenSound.com, and Solaris driver ... Probably the biggest sound card manufacturer in North America. ... everything installed and how one had to apparently license the DRIVERS, ... SUN, change your HCL recommendations. ...
      (comp.unix.solaris)
    • (UPDATE): Link Location Sun Storedge PCI Dual Ultra3 SCSI Card (possibly)
      ... The drivers are referenced off an old sun URL ... copy or otherwise use it and do not disclose ... to improve our service and for security and regulatory purposes. ...
      (SunManagers)