From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Inil30+ spurious debug messages
Date: Fri, 3 May 2002 16:20:43 +0200 [thread overview]
Message-ID: <200205031420.g43EKiS01784@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Fri, 03 May 2002 09:47:25 -0400." <c24d9c5dde9c5e523a7f92385209e151@plan9.bell-labs.com>
> > To my suprise, I see debug messages appear on the screen of the laptop,
> > once every lots-of-minutes - (one per hour or so?)
> > (toshiba tecra 8000, neomagic video card, orinoco card)
> > Those messages also appeared on 3e;
>
> What are the messages?
Inil30+
and then a second one, giving Inil30+Inil30+
Rebooted the machine some time ago, and now there is a Inil20+
In general, it seems that when the messages appear, the machine has
been idle for quite a long while -- don't know whether that matters.
Axel.
next prev parent reply other threads:[~2002-05-03 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 13:47 Sape Mullender
2002-05-03 14:20 ` Axel Belinfante [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-03 14:25 Sape Mullender
2002-05-03 13:54 presotto
2002-05-03 10:18 Axel Belinfante
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=200205031420.g43EKiS01784@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--cc=9fans@cse.psu.edu \
/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).