>From: "Michael D. Harnois" <[EMAIL PROTECTED]>
>Date: 26 Feb 2002 08:38:22 -0600
>I cvsuped and built world and kernel this morning, and the kernel hangs
>at atkbd0: flags 0x1 irq 1 on atkbdc0.
I didn't see that problem. Indeed, my (desktop) build machine built and
ran today's -CURRENT just fine. By "today's," I'm referring to the
results after a "cvs update" from a local CVS repository updated:
freebeast(4.5-S)[1] tail /var/log/cvsup-history.log
CVSup begin from cvsup14.freebsd.org at Sat Feb 23 04:35:13 PST 2002
CVSup ended from cvsup14.freebsd.org at Sat Feb 23 04:42:37 PST 2002
CVSup begin from cvsup14.freebsd.org at Sun Feb 24 03:47:03 PST 2002
CVSup ended from cvsup14.freebsd.org at Sun Feb 24 03:53:45 PST 2002
CVSup begin from cvsup14.freebsd.org at Mon Feb 25 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Mon Feb 25 03:53:57 PST 2002
CVSup begin from cvsup14.freebsd.org at Mon Feb 25 10:01:00 PST 2002
CVSup ended from cvsup14.freebsd.org at Mon Feb 25 10:07:56 PST 2002
CVSup begin from cvsup14.freebsd.org at Tue Feb 26 03:47:03 PST 2002
CVSup ended from cvsup14.freebsd.org at Tue Feb 26 03:53:30 PST 2002
freebeast(4.5-S)[2]
My laptop (using sources of the same vintage) was not so fortunate,
however. Although it built and ran -CURRENT OK yesterday, and built
today's -CURRENT OK, when I tied to boot (even in single-user mode), I
got the following (hand-transcribed, as my laptop doesn't have a serial
console):
...
Pentium Pro MTRR support enabled
pci_open(1):mode 1 addr port (0x0cf8) is 0x80003904
pci_open(1a): mode1res=0x8000 (0x8000)
pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71908086)
Using $PIR table, 7 entries at 0xc00fdf50
ACPI-0161: *** Error: AcpiLoadTables: Could not get RDS: AE_NO_ACPI_TABLES
ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABLES
ACPI: table load failed: AE_NO_ACPI_TABLES
Fatal trap 22: FPU device not available while in vm86 mode
instruction pointer = 0xf000:0xf959
stack pointer = 0x0:0xff8
frame pointer = 0x0:0x0
code segment= base 0x0, limit 0x0, type 0x0
= DPL 0, pres 0, def32 0, gran 0
procssor eflags = interrupt enabled, resume, vm86, IOPL=0
current process = 0 (swapper)
kernel: type 22 trap, code=0
Stopped at 0xf959
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xf959
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0367b64
stack pointer = 0x10:0xc05b1e84
frame pointer = 0x10:0xc05b1e88
code segment= base 0x0, limit 0xf, type 0x16
= DPL 0, pres 1, def32 1, gran 1
procssor eflags = interrupt enabled, resume, IOPL=0
current process = 0 (swapper)
kernel: type 12 trap, code=0
db>
Attempts at this point to get a traceback or a panic dump merely
yielded additional stanzas similar to that last one (the "page fault
in kernel mode"). The "reset" command worked, though, and I was
able to get the machine booted running yesterday's -CURRENT kernel
(which is how I'm typing this at the moment).
The dsdt output from acpidump from 23 Feb. is available at
http://www.catwhisker.org/~david/FreeBSD/laptop.dsdt; the ASL output
from the same time is available from
http://www.catwhisker.org/~david/FreeBSD/laptop.asl, in case that would
be of interest or use.
Clues welcome; until I get a job, I can work on this sort of thing (when
I'm not looking for one)
Thanks,
david (links to my resume at http://www.catwhisker.org/~david)
--
David H. Wolfskill [EMAIL PROTECTED]
I believe it would be irresponsible (and thus, unethical) for me to advise,
recommend, or support the use of any product that is or depends on any
Microsoft product for any purpose other than personal amusement.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
