From: Roy Dragseth <Roy.Dragseth@cc.uit.no>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Problem solved (was: disabling nics in efi.)
Date: Mon, 13 Jan 2003 09:37:53 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805668@msgid-missing> (raw)
Hi.
HP-Support suggested that we tried to disable something called the spanning
tree algorithm on the switch. We did, and voila the problem disappeared.
The spanning tre algorithm has a very long timeout, 30 seconds.
So, for our part the problem is solved, but the timeout issue might be worth
solving on a general basis.
Thanks for all the insightful suggestions from you people on this list. This
problem might be a bit mundane and not very ia64 specific, compared to what
I've seen on this list before, so I'm sorry if this thread has wasted
knowlegdable peoples time.
Regards,
Roy.
--
The Computer Center, University of Tromsø, N-9037 TROMSØ, Norway.
phone:+47 77 64 41 07, fax:+47 77 64 41 00
Roy Dragseth, High Performance Computing System Administrator
Direct call: +47 77 64 62 56. email: royd@cc.uit.no
next reply other threads:[~2003-01-13 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 9:37 Roy Dragseth [this message]
2003-01-14 19:54 ` [Linux-ia64] Problem solved (was: disabling nics in efi.) Gilad Ben-Yossef
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590709805668@msgid-missing \
--to=roy.dragseth@cc.uit.no \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox