This was not a problem with hyperthreading, it is a problem in the
bsdsock nlm and any multiple processors. There is a newer tcp/ip stack
that fixed that problem, however you don't want to go newer, you
actually want to go older. If you go newer you will run into different
problems with rpc timeout and backups restarting.
You want to install tcp659j.exe, If you don't have a copy of that one
laying around let me know and I can e-mail it to you...
George A. Raetzke, CNE & LPIC-1
Senior Systems Programmer
Enterprise System Support
Northern Illinois University
DeKalb, IL 60115
graetzke AT niu DOT edu
815-753-8549
>>> honnold AT STARKEY DOT COM 1/23/2006 10:56:22 AM >>>
Is there a resolution to this issue?
Is it a Legato client issue or a Netware issue?
Thanks,
joe.
On Mon, 26 Sep 2005 16:53:12 +0100, Kumar_Piyush AT EMC DOT COM wrote:
>I have seen this problem being reported elsewhere also and believe
that
>Novell is looking into it. The problem was reported with SP4 update on
6.5
>machines with hyperthreading enabled.
>
>Piyush
>
>
>-----Original Message-----
>From: Legato NetWorker discussion
[mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
>Behalf Of George Raetzke
>Sent: Monday, September 26, 2005 9:15 PM
>To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>Subject: [Networker] networker for netware 7.2 and BSDSOCK abends
>
>On Sunday I put the new 7.2 client on my first production server, and
it
>didn't go as well as I would have hoped. Shortly after SAVE.NLM
loads
>on the server the box abends in bsdsock.nlm->getBsdDebugInfo. I was
>able to prevent this abend from occuring by not loading acpidrv.psm
in
>the startup.ncf file, so this is likely a multicpu issue. The server
>was a HP ProLiant ML530G2, dual 2.8G, NetWare 6.5SP4+NSS patch.
>
>I submitted a coredump to Novell to see what they have to say about
>it.
>
>
>
>George A. Raetzke, CNE & LPIC-1
>Senior Systems Programmer
>Enterprise System Support
>Northern Illinois University
>DeKalb, IL 60115
>graetzke AT niu DOT edu
>815-753-8549
>
>To sign off this list, send email to listserv AT listserv.temple DOT edu and
type
>"signoff networker" in the
>body of the email. Please write to
networker-request AT listserv.temple DOT edu if
>you have any problems
>wit this list. You can access the archives at
>http://listserv.temple.edu/archives/networker.html or
>via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
>To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in
the
>body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any
problems
>wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html
or
>via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>===========================================================
==============
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
