SUMMARY: SolarNet LAN Client and BAD TRAP

From: Stephen.Fitzgerald@dsto.defence.gov.au
Date: Sun Apr 14 1996 - 20:21:49 CDT


Managers,
        I had a number of responses, the response from Casper Dik pointing me to
a "just released" patch which solves the problem.

        The patch is (SPARC and X86 respectively)

103348-01: Solarnet LAN client 1.1 causes Solaris 2.5 panic with data fault
103349-01: Solarnet LAN client 1.1 causes Solaris 2.5 panic with data fault

Thanks to

Casper Dik <casper@holland.Sun.COM>
Kevin.Sheehan@uniq.com.au (Kevin Sheehan)
rob.jackard@amp.com (Robby Jackard)

Regards
Stephen Fitzgerald

----- Begin Included Message -----

Managers,
        can anyone shed some light on this problem.

        Machine SS5
        OS 2.5
        Memory 40M

I have installed SolarNet LAN Client 1.1 on a SS5 running 2.5. I can now
login as SUPERVISOR on the Novell Server running 3.11. This step is
mandatory if we wish to mount Novell volumes under Solaris 2.5.

The SS5 has been rebooted with "-r" to reconfigure the kernel, but whenever
I attempt to mount a Novell volume the BAD TRAP occurs and the SS5 reboots.

The mount command I use is

        mount -F snfs nw:NOVELL-SERVER:VOL1 /mnt

The BAD TRAP occurs and reports a message similar to this,

        BAD TRAP snfs due to illegal access to user database

Has anyone seen this error message before?

NOTE: The above process works OK for Solaris 2.4

Thanks for any help

Regards
Stephen Fitzgerald

----- End Included Message -----



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:57 CDT