make kernel breakage - src/sys/dev/usb/uplcom.c
Compiling from today's cvsup results in a failure to compile src/sys/dev/usb/uplcom.c due to USB_PRODUCT_RATOC_REXUSB60 being undefined. It appears that usbdevs.h needs to be regenerated and checked in to the repository. As a temporary fix: cd .../src/sys/dev/usb/ awk -f devlist2h.awk usbdevs seems to resolve the issue. Is there a reason this is (apparently) not run during the make process? Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: ACPI autoload failed -- unable to install
Summary:
Unable to boot from installation floppies on Sony PCG-SRX7E/P,
Asus (CUV4X?) MB, Intel SE440BX2 MB, due to missing acpi.ko or
inability of loader/kernel supplied with installation floppies to
run without it.
Otterr suggested that there may be ACPI issues with the ASUS MB (see
snippet at bottom of this message).
Just for a sanity check, I have tried booting an Intel SE440BX2 MB system
with the 5.0-20020314-CURRENT floppies, and obtain the same general results.
When mfsroot has loaded,
acpi_load=YES
hint.acpi.0.oem=PTLTD
hint.acpi.0.revision=1
hint.acpi.0.rsdt=0x03ffdd71
and this runs through the 'ACPI autoload failed - no such file or
directory' message, assumed from the code snippet of i386_module.c
shown in the next portion of this message. It is then followed by
(taken from a run where the boot process was un-interrupted by any
keyboard interaction other than ENTER once mfsroot floppy had been
inserted):
Please insert MFS root floppy and press enter:
-
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/kernel]...
ACPI autoload failed - no such file or directory
-
int=000e err=0002 efl=00010093 eip=c03069f2
eax=0081 ebx=0082fc00 ecx= edx=0102
esi=0082f000 edi=00837000 ebp= esp=c0832d98
cs=0008 ds=0010 es=0010fs=0010 gs=0010 ss=0010
cs:eip=00 83 ec 18 57 00 00 a1-84 15 37 c0 a3 0c 77 38
co a1 88 15 37 c0 a3 e4-77 38 c0 05 a0 1d 00 00
ss:esp=04 94 12 c0 00 70 83 00-00 f0 82 00 00 00 00 00
00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
BTX halted
If I 'OK unset acpi_load' (code for these functions appears to be
src/sys/boot/i386/libi386/ i386_module.c v1.5 and biosacpi.c v1.1)
then i386_module.c should *not* try to load acpi:
/* autoload ACPI support */
/* XXX should be in 4th keyed off acpi_load */
if ((getenv(acpi_load) !getenv(hint.acpi.0.disable))) {
error = mod_load(acpi, NULL, 0, NULL);
if (error != 0)
printf(ACPI autoload failed - %s\n, strerror(error));
}
However, from the 5.0-20020314-CURRENT floppies, this results in
(the same as above) BTX dump of:
OK boot
|
int=000e err=0002 efl=00010093 eip=c03069f2
eax=0081 ebx=0082fc00 ecx= edx=0102
esi=0082f000 edi=00837000 ebp= esp=c0832d98
cs=0008 ds=0010 es=0010fs=0010 gs=0010 ss=0010
cs:eip=00 83 ec 18 57 00 00 a1-84 15 37 c0 a3 0c 77 38
co a1 88 15 37 c0 a3 e4-77 38 c0 05 a0 1d 00 00
ss:esp=04 94 12 c0 00 70 83 00-00 f0 82 00 00 00 00 00
00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
BTX halted
just in case something has changed in the way to create floppies...
fdformat /dev/fd0
dd if=kern.flp of=/dev/fd0
(you never know -- that has been about the same since I installed
FreeBSD 2.2 -- some things *do* change)
Anyone else trying to install from floppies onto an ACPI-enabled
machine? The silence is deafening...
Jeff
On Fri, 15 Mar 2002, Otterr wrote:
Date: Fri, 15 Mar 2002 23:32:30 -0500
From: Otterr [EMAIL PROTECTED]
To: 'Jeff Kletsky' [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: ACPI autoload failed -- unable to install
Jeff,
FWIW, the Asus A7A266 is not completely ACPI compliant. Yours may not be
either. It may be worth researching *cough* or replacing *cough*.
-Otter
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jeff Kletsky
Sent: Friday, March 15, 2002 10:07 PM
To: Jeff Kletsky
Cc: [EMAIL PROTECTED]
Subject: Re: ACPI autoload failed -- unable to install
I find it impossible to install 5.0-CURRENT from floppies, for both a
current desktop and a current laptop machine. With this now occurring
on two disparate machines, I have to believe there is either something
very broken with the install floppies, or with me. If it is me,
*please* let me know!
I have gotten today's snapshot, 5.0-20020315-CURRENT, created the
kernel and mfsroot 1.44 floppies, and attempted to boot a desktop
machine from them. This is (from my 4.5-STABLE hard drive):
CPU: Pentium III/Pentium III Xeon/Celeron (733.13-MHz 686-class CPU)
Origin = GenuineIntel Id = 0x686 Stepping = 6
Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,
MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real memory = 402571264 (393136K bytes)
It is an Asus MB with a VIA chipset. Full (4.5) dmesg.boot is attached
at the end of this message.
Once again, the error message is that ACPI cannot be found. BTX then
halts with:
int=0006 err= efl=00010006 eip=c0306b40
eax=0081 ebx=0082fc00 ecx= edx=0102
esi=0082f000 edi=009b6000 ebp= esp=c09b1d98
cs=0008 ds=0010 es=0010fs=0010 gs=0010 ss=0010
cs:eip=ff ff ff ff ff 18 57 56-ff a1 e4 16 37 c0 a3 6c
78 38 c0 a1 e8 16 37 c0-a3 44 79 38 c0 05 a0 1d
ss:esp=04 94 12 c0 00 70 83 00-00 f0 82 00 00 00 00 00
00
Re: ACPI autoload failed -- unable to install
Based on Shizuka Kudo's observations, I have inventoried the recent boot.flp imaged using bootable CD and the Intel SE440BX-2 motherboard. I believe the breakage to have occurred between March 11th and 12th. The following images boot the machine: 20020302 20020303 20020304 20020307 20020308 20020309 20020310 20020311 The following images fail in a manner similar to that previously described in this thread: 20020312 20020313 The following images were previously observed to fail in the manner described in earlier messages in this thread: 20020314 20020315 Jeff On Sat, 16 Mar 2002, Shizuka Kudo wrote: Date: Sat, 16 Mar 2002 07:21:26 -0800 (PST) From: Shizuka Kudo [EMAIL PROTECTED] To: Jeff Kletsky [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: ACPI autoload failed -- unable to install [ Section describing inability to boot from -CURRENT floppies ] Same here when I tried 20020315 snapshot on a Toshiba Portege 7140. I finally started over with 20020302 and have no problem to install. You may try this if you can't wait... __ Do You Yahoo!? Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
VAIO install, sn0 kernel panic, workaround
Having determined that the last bootable install image was 20020311, I have network booted my Sony VAIO PCG-SRX7E/P using pxeboot and the contents of the boot.flp image on an NFS mount. If the boot process is allowed to progress without interruption, the kernel panics: [...] vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources (port) unknown: PNP0c02 can't assign resources (memory) psmcpnp0: irq resource info is missing: assuming irq 12 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x6d256d24 fault code = supervisor write, page not present instruction pointer = 0x8:0xc164cf00 stack pointer = 0x10:0xcb92cd00 frame pointer = 0x10:0xcb92cd1c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 27 (irq10: sn0) trap number = 12 panic: page fault syncing disks... done Uptime: 0s Automatic reboot in 15 seconds - press a key on the console to abort -- Press a key on the console to reboot. -- or switch off the system now. * Setting 'OK set boot_verbose' indicates that Device configuration finished. bpf: lo0 attached * Setting 'OK set hint.sn.0.disabled=1' resolves the issue and allows the machine to boot into the installer, and complete installation. On reboot, the classic symptoms of pcic unhappiness appear -- the boot process freezes after ad0: is recognized. As in the past, Werner Losh's recommended OK set hw.pcic.intr_path=1 OK set hw.pcic.irq=0 OK boot resolves the issue. (Stay calm, there is a pause while the Memory Stick times-out with the typical 15s SCSI delay.) Now to the psm0 problem... Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI autoload failed -- unable to install
With apologies for an incomplete report, I am including the (manually
transcribed) dump information. I have been able to network boot from a
combination of the boot.flp and bin distribution (though there are
problems with getting sysinstall to find disks that prevent that approach
so far) and confirm that the hw.pcic interrupt routing sysctls *are*
required. So the report that follows is based on using floppies from
5.0-20020314-CURRENT, including the one referred to as 'acpi.ko.flp' in
the Failed workaround description below.
To reproduce, follow the steps 1-7 outlined below. The tail end of the
process appears as:
OK load acpi.ko
/boot/kernel/acpi.ko text=0x2b5a0 data=0x1558+0x6cc
syms=[0x4+0x4ed0+0x4+0x675a]
OK boot
/
int=0006 err= efl=00010006 eip=c03069f0
eax=0001 ebx=009aec00 ecx= edx=0102
esi=009ae000 edi=009b6000 ebp= esp=c09b1d98
cs=0008 ds=0010 es=0010fs=0010 gs=0010 ss=0010
cs:eip=ff ff ff 83 ec 18 57 ff-ff a1 84 15 37 c0 a3 0c
77 38 c0 a1 88 15 37 c0-a3 e4 77 38 c0 05 a0 1d
ss:esp=04 94 12 c0 00 60 9b 00-00 e0 9a 00 00 00 00 00
00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
BTX halted
I am willing to try reasonable steps and debugging here. Unfortunately,
the BIOS driving the USB floppy seems to take about 10 min. to read a
floppy, so it testing multiple scenarios is somewhat painful. I will be
working with bootable CD configurations today, though the iLINK
(IEEE-1394) connection there has its own share of problems (no non-BIOS
support of the drive). At least with floppies, it *should* be a supported
configuration. (Note however the reported issues with fixit only being
mountable from /dev/fd0, not /dev/da0).
Jeff
On Thu, 14 Mar 2002, Jeff Kletsky wrote:
Date: Thu, 14 Mar 2002 18:49:35 -0800 (PST)
From: Jeff Kletsky [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: ACPI autoload failed -- unable to install (fwd)
Tried the obvious -- manually loading acpi.ko -- still fails
On Thu, 14 Mar 2002, Jeff Kletsky wrote:
Date: Thu, 14 Mar 2002 17:41:01 -0800 (PST)
From: Jeff Kletsky [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: ACPI autoload failed -- unable to install
Having been unable to confirm a complete and proper installation of
5.0-CURRENT on my Sony PCG-SRX7/EP (similar to SRX77) laptop using the
4.5-RELEASE installer, I have made a bootable CD from
5.0-20020313-CURRENT, as well as floppies from 5.0-20020314-CURRENT.
Both exhibit the same set of symptoms.
[...]
Results in:
ACPI autoload failed - no such file or directory
-
[dump followed]
Failed workaround:
1) Create floppies using dd
2) Make another copy of the mfsroot floopy,
mount /dev/fd0 /mnt
rm -rf /mnt/*
mkdir -p /mnt/boot/kernel
copy acpi.ko to /mnt/boot/kernel
### Note that copying to root of floppy fails on load attempt ###
### This is inconsistent with the loader (8) manpage in 5.0 ###
umount /mnt
3) Boot from kern.flp
4) Load mfsroot.flp
5) Interrupt boot process
set hw.pcic.intr_path=1
set hw.pcic.irq=0
6) Remove mfsroot.flp, insert 'acpi.ko.flp'
load acpi.ko
('boot'ing here causes the BTX to halt if the acpi.ko.flp is still
in the drive)
7) Remove acpi.ko.flp, insert mfsroot.flp
boot
...and watch the BTX halt
Jeff
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: ACPI autoload failed -- unable to install
I find it impossible to install 5.0-CURRENT from floppies, for both a current desktop and a current laptop machine. With this now occurring on two disparate machines, I have to believe there is either something very broken with the install floppies, or with me. If it is me, *please* let me know! I have gotten today's snapshot, 5.0-20020315-CURRENT, created the kernel and mfsroot 1.44 floppies, and attempted to boot a desktop machine from them. This is (from my 4.5-STABLE hard drive): CPU: Pentium III/Pentium III Xeon/Celeron (733.13-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE, MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 402571264 (393136K bytes) It is an Asus MB with a VIA chipset. Full (4.5) dmesg.boot is attached at the end of this message. Once again, the error message is that ACPI cannot be found. BTX then halts with: int=0006 err= efl=00010006 eip=c0306b40 eax=0081 ebx=0082fc00 ecx= edx=0102 esi=0082f000 edi=009b6000 ebp= esp=c09b1d98 cs=0008 ds=0010 es=0010fs=0010 gs=0010 ss=0010 cs:eip=ff ff ff ff ff 18 57 56-ff a1 e4 16 37 c0 a3 6c 78 38 c0 a1 e8 16 37 c0-a3 44 79 38 c0 05 a0 1d ss:esp=04 94 12 c0 00 70 83 00-00 f0 82 00 00 00 00 00 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 BTX halted Thanks for your help, Jeff On Fri, 15 Mar 2002, Jeff Kletsky wrote: Date: Fri, 15 Mar 2002 07:52:17 -0800 (PST) From: Jeff Kletsky [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: ACPI autoload failed -- unable to install With apologies for an incomplete report, I am including the (manually transcribed) dump information. I have been able to network boot from a combination of the boot.flp and bin distribution (though there are problems with getting sysinstall to find disks that prevent that approach so far) and confirm that the hw.pcic interrupt routing sysctls *are* required. So the report that follows is based on using floppies from 5.0-20020314-CURRENT, including the one referred to as 'acpi.ko.flp' in the Failed workaround description below. To reproduce, follow the steps 1-7 outlined below. The tail end of the process appears as: OK load acpi.ko /boot/kernel/acpi.ko text=0x2b5a0 data=0x1558+0x6cc syms=[0x4+0x4ed0+0x4+0x675a] OK boot / int=0006 err= efl=00010006 eip=c03069f0 eax=0001 ebx=009aec00 ecx= edx=0102 esi=009ae000 edi=009b6000 ebp= esp=c09b1d98 cs=0008 ds=0010 es=0010fs=0010 gs=0010 ss=0010 cs:eip=ff ff ff 83 ec 18 57 ff-ff a1 84 15 37 c0 a3 0c 77 38 c0 a1 88 15 37 c0-a3 e4 77 38 c0 05 a0 1d ss:esp=04 94 12 c0 00 60 9b 00-00 e0 9a 00 00 00 00 00 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 BTX halted I am willing to try reasonable steps and debugging here. Unfortunately, the BIOS driving the USB floppy seems to take about 10 min. to read a floppy, so it testing multiple scenarios is somewhat painful. I will be working with bootable CD configurations today, though the iLINK (IEEE-1394) connection there has its own share of problems (no non-BIOS support of the drive). At least with floppies, it *should* be a supported configuration. (Note however the reported issues with fixit only being mountable from /dev/fd0, not /dev/da0). Jeff On Thu, 14 Mar 2002, Jeff Kletsky wrote: Date: Thu, 14 Mar 2002 18:49:35 -0800 (PST) From: Jeff Kletsky [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: ACPI autoload failed -- unable to install (fwd) Tried the obvious -- manually loading acpi.ko -- still fails On Thu, 14 Mar 2002, Jeff Kletsky wrote: Date: Thu, 14 Mar 2002 17:41:01 -0800 (PST) From: Jeff Kletsky [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: ACPI autoload failed -- unable to install Having been unable to confirm a complete and proper installation of 5.0-CURRENT on my Sony PCG-SRX7/EP (similar to SRX77) laptop using the 4.5-RELEASE installer, I have made a bootable CD from 5.0-20020313-CURRENT, as well as floppies from 5.0-20020314-CURRENT. Both exhibit the same set of symptoms. [...] Results in: ACPI autoload failed - no such file or directory - [dump followed] Failed workaround: 1) Create floppies using dd 2) Make another copy of the mfsroot floopy, mount /dev/fd0 /mnt rm -rf /mnt/* mkdir -p /mnt/boot/kernel copy acpi.ko to /mnt/boot/kernel ### Note that copying to root of floppy fails on load attempt ### ### This is inconsistent with the loader (8) manpage in 5.0 ### umount /mnt 3) Boot from kern.flp 4) Load mfsroot.flp 5) Interrupt boot process set hw.pcic.intr_path=1 set hw.pcic.irq=0 6) Remove mfsroot.flp, insert 'acpi.ko.flp' load acpi.ko
ACPI autoload failed -- unable to install
Having been unable to confirm a complete and proper installation of 5.0-CURRENT on my Sony PCG-SRX7/EP (similar to SRX77) laptop using the 4.5-RELEASE installer, I have made a bootable CD from 5.0-20020313-CURRENT, as well as floppies from 5.0-20020314-CURRENT. Both exhibit the same set of symptoms. *or* after moving through the boot process and forcing the 'OK' prompt, enter: set hw.pcic.intr_path=1 set hw.pcic.irq=0 boot *or* set acpi_load=no set hw.pcic.intr_path=1 set hw.pcic.irq=0 boot *or* unset acpi_load set hw.pcic.intr_path=1 set hw.pcic.irq=0 boot Results in: ACPI autoload failed - no such file or directory - [dump followed] *or* unset acpi_load boot Results in a crash dump before anything else happens What am I missing here? This laptop has been able to successfully boot 4.5-RELEASE CD (with the hw.pcic changes above), install 4.5-RELEASE, boot, and run that OS. A similar issue was reported - but looks to be a different problem. Date: Fri, 14 Sep 2001 20:10:13 +0100 From: David Malone [EMAIL PROTECTED] To:[EMAIL PROTECTED] Subject: ACPI module loading. http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=684341+685945+/usr/local/www/db/text/2001/freebsd-current/20010916.freebsd-current Looking at the floppy images, I do not find /boot/kernel/acpi.ko in either the main image, or in the mfsroot image. There is not enough space on the kern.flp to copy acpi.ko to that floppy, and my belief (which may be incorrect) is that since this is during the kernel load, mfsroot still hasn't appeared to the loader. Nothing clear on disabling acpi in acpi (4) manpage, and the referenced acpi (9) manpage does not come up on the FreeBSD manpage web site (as I don't have 5.0 installed yet). Any suggestions, or is it time for GNATS? Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI autoload failed -- unable to install (fwd)
Tried the obvious -- manually loading acpi.ko -- still fails
On Thu, 14 Mar 2002, Jeff Kletsky wrote:
Date: Thu, 14 Mar 2002 17:41:01 -0800 (PST)
From: Jeff Kletsky [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: ACPI autoload failed -- unable to install
Having been unable to confirm a complete and proper installation of
5.0-CURRENT on my Sony PCG-SRX7/EP (similar to SRX77) laptop using the
4.5-RELEASE installer, I have made a bootable CD from
5.0-20020313-CURRENT, as well as floppies from 5.0-20020314-CURRENT.
Both exhibit the same set of symptoms.
[...]
Results in:
ACPI autoload failed - no such file or directory
-
[dump followed]
Failed workaround:
1) Create floppies using dd
2) Make another copy of the mfsroot floopy,
mount /dev/fd0 /mnt
rm -rf /mnt/*
mkdir -p /mnt/boot/kernel
copy acpi.ko to /mnt/boot/kernel
### Note that copying to root of floppy fails on load attempt ###
### This is inconsistent with the loader (8) manpage in 5.0 ###
umount /mnt
3) Boot from kern.flp
4) Load mfsroot.flp
5) Interrupt boot process
set hw.pcic.intr_path=1
set hw.pcic.irq=0
6) Remove mfsroot.flp, insert 'acpi.ko.flp'
load acpi.ko
('boot'ing here causes the BTX to halt if the acpi.ko.flp is still
in the drive)
7) Remove acpi.ko.flp, insert mfsroot.flp
boot
...and watch the BTX halt
Jeff
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
MAKEDEV - Installation fails - 20020312
Installing on a Sony VAIO PCG-SRX7E/P Boot from 4.5-INSTALL CD (iLINK) set hw.pcic.intr_path=1 set hw.pcic.irq=0 boot Visual configuration, leave only: ata0 atkbd0 psm0 sc0 pcic0 npx0 Partition disk, select Developer and Ports Select 5.0-20020312-CURRENT as release Select -CURRENT FTP installation site DHCP configuration of fxp0 watch all distributions get installed Message MAKEDEV returned non-zero status debug console shows a long series of pid 199 (sh), uid 0: exited on signal 12 (core dumped) Bad system call - core dumped pid 201 (sh), uid 0: exited on signal 12 (core dumped) Bad system call - core dumped pid 203 (sh), uid 0: exited on signal 12 (core dumped) Bad system call - core dumped pid 205 (sh), uid 0: exited on signal 12 (core dumped) Bad system call - core dumped Expect that this is probably due to the incompatibilities between the 4.5-RELEASE /stand/sysinstall and the 5.0 MAKEDEV Plan: try to create a bootable CD with a 5.0 kernel... Nero Burning ROM, select CD-ROM (Boot), boot.flp, Floppy Emulation 2.88MB Load segment of sectors (hex): 07C0 [jmk - their default] Number of loaded sectors: 1 [jmk - their default] set hw.pcic.intr_path=1 set hw.pcic.irq=0 boot ACPI autoload failed - no such file or directory - (crash dump appears) set hw.pcic.intr_path=1 set hw.pcic.irq=0 set hint.acpi.0.disabled=1 boot ACPI autoload failed - no such file or directory - (crash dump appears) # # Any additional suggestions??? # System boots on partial install, however, there is no MAKEDEV in /dev So I'm going to try 'make world kernel' and hope for the best... Thanks! Jeff (4.5-INSTALL) dmesg output follows: 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 4.5-RELEASE #2: Tue Jan 29 22:44:12 GMT 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/BOOTMFS Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 794926962 Hz CPU: Pentium III/Pentium III Xeon/Celeron (794.93-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 266862592 (260608K bytes) config intro \^[[m\^[[H\^[[J\^[[3;26H\^[[m\^[[1m\^[[m\^[[6;11H\^[[m\^[[7m\^[[m\^[[7;11H\^[[m\^[[8;11H\^[[m\^[[11;3H\^[[m\^[[12;3H\^[[m\^[[13;3H\^[[m\^[[15;3H\^[[m\^[[16;3H\^[[m\^[[18;3H\^[[m\^[[19;3H\^[[m\^[[21;3H\^[[m\^[[7m\^[[m\^[[22;3H\^[[m\^[[1;1H\^[[6;11H\^[[m\^[[7;11H\^[[m\^[[7m\^[[m\^[[8;11H\^[[m\^[[1;1H\^[[m\^[[H\^[[J\^[[m\^[[H\^[[J\^[[1;1H\^[[m\^[[1;4H\^[[m\^[[1m\^[[m\^[[1m\^[[1;64H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[1m\^[[10;1H\^[[m\^[[10;4H\^[[m\^[[1m\^[[m\^[[1m\^[[10;64H\^[[m\^[[1m\^[[18;1H\^[[m\^[[22;1H\^[[m\^[[m\^[[24;1H\^[[m\^[[24;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[1;46H\^[[m\^[[7m\^[[2;1H\^[[m\^[[2;1H\^[[3;1H\^[[m\^[[3;1H\^[[4;1H\^[[m\^[[4;1H\^[[5;1H\^[[m\^[[5;1H\^[[6;1H\^[[m\^[[6;1H\^[[7;1H\^[[m\^[[7;1H\^[[m\^[[8;1H\^[[m\^[[m\^[[9;1H\^[[m\^[[11;1H\^[[m\^[[11;1H\^[[12;1H\^[[m\^[[12;1H\^[[13;1H\^[[m\^[[13;1H\^[[14;1H\^[[m\^[[14;1H\^[[15;1H\^[[m\^[[15;1H\^[[16;1H\^[[m\^[[16;1H\^[[m\^[[17;1H\^[[m\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[2;1H\^[[m\^[[7m\^[[m\^[[2! 3;1H\^[[m\^[[23;1H\^[[m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[2;1H\^[[1;46H\^[[m\^[[7m\^[[2;1H\^[[m\^[[2;1H\^[[3;1H\^[[m\^[[3;1H\^[[4;1H\^[[m\^[[4;1H\^[[5;1H\^[[m\^[[5;1H\^[[6;1H\^[[m\^[[6;1H\^[[7;1H\^[[m\^[[7;1H\^[[8;1H\^[[m\^[[8;1H\^[[9;1H\^[[m\^[[9;1H\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[2;1H\^[[m\^[[7m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[2;1H\^[[2;1H\^[[m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[2;1H\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[21;2H\^[[m\^[[3;1H\^[[m\^[[7m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[3;1H\^[[1;46H\^[[m\^[[7m\^[[2;1H\^[[m\^[[2;1H\^[[3;1H\^[[m\^[[3;1H\^[[4;1H\^[[m\^[[4;1H\^[[5;1H\^[[m\^[[5;1H\^[[6;1H\^[[m\^[[6;1H\^[[7;1H\^[[m\^[[7;1H\^[[8;1H\^[[m\^[[8;1H\^[[9;1H\^[[m\^[[9;1H\^[[11;1H\^[[m\^[[11;1H\^[[12;1H\^[[m\^[[12;1H\^[[13;1H\^[[m\^[[13;1H\^[[14;1H\^[[m\^[[14;1H\^[[15;1H\^[[m\^[[15;!
