Re: Uptime of 8909 days on 5-CURRENT
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 cvsup ran on 6th edithion UNIX... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Uptime of 8909 days on 5-CURRENT
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 by out of sync kernel and world. I haven't yet been able to test this hypothesis. Kris msg37791/pgp0.pgp Description: PGP signature
Re: Uptime of 8909 days on 5-CURRENT
--- 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 are in trouble!). Regards, -- Hiten __ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Uptime of 8909 days on 5-CURRENT
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. 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. 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. This was on -CURRENT from late last night. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Uptime of 8909 days on 5-CURRENT
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. Motherboard is an ASUS A7M266D with the (possibly buggy) 1004 BIOS. 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. 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. This was on -CURRENT from late last night. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services @ uptime 3:36pm up 8909 days, 9:30, 2 users, load averages: 0,92 0,52 0,26 I love this ... I am _so_ proud :-) @ uname -a FreeBSD ole-guldberg.dk 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sun Apr 28 12:05:35 CEST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DYNAMIC i386 /ole -- see my pgp public key at http://home20.inet.tele.dk/ole_guldberg or at: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xEC74D4C5 I went to the museum where they had all the heads and arms from the statues that are in all the other museums. -- Steven Wright msg37800/pgp0.pgp Description: PGP signature
Re: Uptime of 8909 days on 5-CURRENT
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. This was on -CURRENT from late last night. This seems to be a bug in a little joke kern_tc.c. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Uptime of 8909 days on 5-CURRENT
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 great conflict, ... we will see freedom's victory. - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Uptime of 8909 days on 5-CURRENT
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 of the recent changes made to the time code by phk? (uh oh, hiten.. you are in trouble!). Yes, it is. Kris msg37814/pgp0.pgp Description: PGP signature
Re: Uptime of 8909 days on 5-CURRENT
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. 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: 1. buildworld 2. buildkernel 3. installkernel 4. single user 5. installworld 6. mergemaster and then for good measure tried building the world again, and i've still got the problem. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Uptime of 8909 days on 5-CURRENT
--- 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 problem. -- Hiten __ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Uptime of 8909 days on 5-CURRENT
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: [...] Just cvsup again and rebuild your kernel, and that will fix the problem. Just finished, it did. Vmstat is fixed too. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Uptime of 8909 days on 5-CURRENT
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 seconds) for system process `vnlru' to stop...stopped Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks... 9 8 7 6 5 4 3 2 2 done Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sat Apr 27 15:17:05 PDT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/COREDUMP Preloaded elf kernel /boot/kernel/kernel at 0xc059d000. Preloaded elf module /boot/kernel/acpi.ko at 0xc059d0a8. Timecounter i8254 frequency 1193182 Hz CPU: AMD Athlon(TM) XP 1600+ (1400.06-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x662 Stepping = 2 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc048MP,AMIE,DSP,3DNow! real memory = 536788992 (524208K bytes) avail memory = 515842048 (503752K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040010, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040010, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Pentium Pro MTRR support enabled Using $PIR table, 9 entries at 0xc00f1370 npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS A7M266-D on motherboard acpi0: power button is handled as a fixed feature programming model. acpi0: sleep button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_cpu1: CPU on acpi0 acpi_button0: Power Button on acpi0 acpi_pcib0: Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: PCI bus on acpi_pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 5.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: AMD 768 ATA100 controller port 0xd800-0xd80f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: bridge, PCI-unknown at device 7.3 (no driver attached) ahc0: Adaptec 3960D Ultra160 SCSI adapter port 0xd400-0xd4ff mem 0xed80-0xed800fff irq 10 at device 9.0 on pci0 aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs ahc1: Adaptec 3960D Ultra160 SCSI adapter port 0xd000-0xd0ff mem 0xed00-0xed000fff irq 5 at device 9.1 on pci0 aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs pcib2: PCI-PCI bridge at device 16.0 on pci0 pci2: PCI bus on pcib2 fxp0: Intel Pro 10/100B/100+ Ethernet port 0xb800-0xb83f mem 0xeb80-0xeb8f,0xec00-0xec000fff irq 10 at device 6.0 on pci2 fxp0: Ethernet address 00:90:27:bc:09:95 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci2: multimedia, audio at device 8.0 (no driver attached) pci2: input device at device 8.1 (no driver attached) ppc0 port 0x778-0x77f,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 orm0: Option ROMs at iomem 0xd8000-0xd8fff,0xc-0xcc7ff on isa0 fdc0: cannot reserve I/O port range (6 ports) pmtimer0 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 Timecounters tick every 10.000 msec acpi_cpu: CPU throttling enabled, 2 steps from 100% to 50.0% ad0: 12949MB IBM-DJNA-371350 [26310/16/63] at ata0-master UDMA66 acd0: DVD-ROM CREATIVEDVD8400E at ata1-master PIO4 Waiting 15 seconds for SCSI devices to settle da0 at ahc0 bus 0 target 0 lun 0 da0: SEAGATE ST336704LW 0004 Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 35003MB (71687369 512 byte sectors: 255H 63S/T 4462C) Mounting root from ufs:/dev/ad0s1a SMP: AP CPU #1 Launched! swi_net: unregistered isr number: 18. To Unsubscribe:
