From: Patrick Kilian <petschge@gmx.de>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] 2.6.0 uptime bug
Date: Thu, 4 Sep 2003 17:06:03 +0200 [thread overview]
Message-ID: <200309041706.03045.petschge@gmx.de> (raw)
Hi,
I found a bug in the 2.6.0-test? kernels. /proc/uptime shows a uptime
since the start of the epoch, approx. 33 years.
Is anybody able to reproduce this bug?
mfg,
Patrick "Petschge" Kilian
--
I still think the fastest way to get wholesale IPv6 adoption
is to write a pr0n server that serves thumbnails over IPv[46]
and full-size images over IPv6 only. -- Ingvar
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2003-09-04 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 15:06 Patrick Kilian [this message]
2003-09-04 19:11 ` [uml-devel] 2.6.0 uptime bug Geert Uytterhoeven
[not found] ` <20030905151952.6EBFC3BCE4@home.petschge.de>
[not found] ` <20030906190708.56B8C3BCE4@home.petschge.de>
2003-09-09 16:16 ` [uml-devel] " Jeff Dike
2003-09-09 16:28 ` Patrick "Petschge" Kilian
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=200309041706.03045.petschge@gmx.de \
--to=petschge@gmx.de \
--cc=petschge@web.de \
--cc=user-mode-linux-devel@lists.sourceforge.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