bat trap: type=34

From: Gerard Henry (ghenry_at_cmi.univ-mrs.fr)
Date: 12/30/03

  • Next message: Drew Skinner: "fssnap versus Instant Image" 
    Date: Tue, 30 Dec 2003 09:25:01 +0100
To: sunmanagers@sunmanagers.org

    hello,
    our server, E250 sol8, with latest recommended patches cluster applied last day did a kernel panic
    Dec 30 06:51:33 scr ^Mpanic[cpu0]/thread=3000858bc80:
    Dec 30 06:51:33 scr unix: [ID 799565 kern.notice] BAD TRAP: type=34 rp=2a100590f
    d0 addr=fffffeefdeadbf0f mmu_fsr=0
    Dec 30 06:51:33 scr unix: [ID 100000 kern.notice]
    Dec 30 06:51:33 scr unix: [ID 839527 kern.notice] atalkd:
    Dec 30 06:51:33 scr unix: [ID 123557 kern.notice] alignment error:

    i suspect netatalk, but this works fine until we applied new patches.
    But since september, this machine did also a "bad trap: type=30" and "bad trap: type=31",

    SunOS scr 5.8 Generic_108528-27 sun4u sparc SUNW,Ultra-250

    anybody using netatalk? version?

    thanks in advance, i'll resume

    gerard henry
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers

  • Next message: Drew Skinner: "fssnap versus Instant Image"