From: Andreas Eriksen <andreer@pvv.ntnu.no>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] soverflow for fx->in
Date: Mon, 26 Oct 2009 17:33:00 +0100 [thread overview]
Message-ID: <4B4622FF-CD80-4466-9D07-316E2835D10F@pvv.ntnu.no> (raw)
Our cpu/auth/file went belly up some time during the weekend. It
responded to ping, but we couldn't drawterm in. No response from
the vblade process providing storage to our XenServers either.
Walking down to the machine I found the screen full of "soverflow
for fx->in" messages. I had to reboot it to get the virtual machines
back online, so this is my only clue (print statement in
/sys/src/9/pc/devether.c:186 ). The machine had been working happily
for over a week before this. Any ideas as to how i can keep this
from happening again?
The ethernet controller is an "Intel®PRO/1000 GT Desktop Adapter"
according to the sticker on the back, on bootup i get
#l0: i82543: 1000 Mbps port 0xFEBE0000 irq 5 tu 1514:000e0c73d17a
next reply other threads:[~2009-10-26 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 16:33 Andreas Eriksen [this message]
[not found] <<4B4622FF-CD80-4466-9D07-316E2835D10F@pvv.ntnu.no>
2009-10-26 20:53 ` erik quanstrom
2010-07-25 0:33 James Chapman
2010-07-25 4:52 ` erik quanstrom
2010-07-25 9:57 ` James Chapman
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=4B4622FF-CD80-4466-9D07-316E2835D10F@pvv.ntnu.no \
--to=andreer@pvv.ntnu.no \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).