On Sun, 28 Apr 2002, Hiten Pandya wrote:
> --- Lamont Granquist <[EMAIL PROTECTED]> wrote:
> > > I'm seeing this too, but I expect it's probably caused by out of sync
> > > kernel and world. I haven't yet been able to test this hypothesis.
> >
> > I don't think so, I did:
> >
> > [...]
>
> Jus
--- Lamont Granquist <[EMAIL PROTECTED]> wrote:
> > I'm seeing this too, but I expect it's probably caused by out of sync
> > kernel and world. I haven't yet been able to test this hypothesis.
>
> I don't think so, I did:
>
> [...]
Just cvsup again and rebuild your kernel, and that will fix the
On Sun, 28 Apr 2002, Kris Kennaway wrote:
> On Sat, Apr 27, 2002 at 03:45:49PM -0700, Lamont Granquist wrote:
> >
> > I just did a cvsup today to -current on a GENERIC+SMP kernel and my uptime
> > is showing 8909 days. Motherboard is an ASUS A7M266D with the (possibly
> > buggy) 1004 BIOS.
>
>
On Sun, Apr 28, 2002 at 03:05:47AM -0700, Hiten Pandya wrote:
> --- Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > I'm seeing this too, but I expect it's probably caused by out of sync
> > kernel and world. I haven't yet been able to test this hypothesis.
>
> Just wondering, could this be because
On Sat, 27 Apr 2002, Lamont Granquist wrote:
>
> I just did a cvsup today to -current on a GENERIC+SMP kernel and my uptime
> is showing 8909 days.
cvsup again, this problem should be fixed now.
--
"We have known freedom's price. We have shown freedom's power.
And in this grea
On Sun, 28 Apr 2002, Robert Watson wrote:
> Heh. I'm seeing this during the uptime announcement from the kernel after
> kernel shutdown, which means userland isn't involved:
>
> Uptime: 8909d8h59m52s
>
> Given that the uptime of the box was well less than a minute, that seems a
> little extreme.
On Sun, Apr 28, 2002 at 09:31:32AM -0400, Robert Watson wrote:
>
> On Sun, 28 Apr 2002, Kris Kennaway wrote:
>
> > On Sat, Apr 27, 2002 at 03:45:49PM -0700, Lamont Granquist wrote:
> > >
> > > I just did a cvsup today to -current on a GENERIC+SMP kernel and my uptime
> > > is showing 8909 days.
On Sun, 28 Apr 2002, Kris Kennaway wrote:
> On Sat, Apr 27, 2002 at 03:45:49PM -0700, Lamont Granquist wrote:
> >
> > I just did a cvsup today to -current on a GENERIC+SMP kernel and my uptime
> > is showing 8909 days. Motherboard is an ASUS A7M266D with the (possibly
> > buggy) 1004 BIOS.
>
--- Kris Kennaway <[EMAIL PROTECTED]> wrote:
> I'm seeing this too, but I expect it's probably caused by out of sync
> kernel and world. I haven't yet been able to test this hypothesis.
Just wondering, could this be because of the recent changes made to the
time code by phk? (uh oh, hiten.. you
On Sat, Apr 27, 2002 at 03:45:49PM -0700, Lamont Granquist wrote:
>
> I just did a cvsup today to -current on a GENERIC+SMP kernel and my uptime
> is showing 8909 days. Motherboard is an ASUS A7M266D with the (possibly
> buggy) 1004 BIOS.
I'm seeing this too, but I expect it's probably caused b
Lamont Granquist wrote:
> I just did a cvsup today to -current on a GENERIC+SMP kernel and my uptime
> is showing 8909 days. Motherboard is an ASUS A7M266D with the (possibly
> buggy) 1004 BIOS.
I'm really surprised... I didn't realize ASUS made PDP-11
compatibles. 1977... I also didn't realize
I just did a cvsup today to -current on a GENERIC+SMP kernel and my uptime
is showing 8909 days. Motherboard is an ASUS A7M266D with the (possibly
buggy) 1004 BIOS.
Here's my dmesg:
==
boot() called on cpu#1
Waiting (max 60
12 matches
Mail list logo
