Ok, so I finally got around to upgrading my systems.  The upgrade
process went fine on my first one, rebooted fine twice, but now it's
boot>
booting hd0a:/bsd: 5665588+872060 [52+291168+272312]=0x6c5c70
entry point at 0x200120

Nothing more shows up in my serial console but the dump and trace are
up on my monitor if anyone needs me to transcribe it.  It starts out
with:

trap: 4(0): protection fault
cn_tab=0x4a6a0

System boots fine if I interrupt the boot process and do a boot hda0:/bsd.

boot> boot hd0a:/bsd
booting hd0a:/bsd: 5665588+872060 [52+291168+272312]=0x6c5c70
entry point at 0x200120*
[ using 563904 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2007 OpenBSD. All rights reserved.  http://www.OpenBSD.org

OpenBSD 4.2 (GENERIC) #375: Tue Aug 28 10:38:44 MDT 2007
    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Athlon(tm) XP 1800+ ("AuthenticAMD" 686-class, 256KB L2
cache) 1.54 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,F
XSR,SSE
real mem  = 267939840 (255MB)
avail mem = 251437056 (239MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 04/22/05, BIOS32 rev. 0 @
0xfdae0, SMBIOS rev. 2.3 @ 0xf0650 (25 entries)
bios0: vendor American Megatrends Inc. version "07.00T" date 04/02/01
bios0: ECS M848A
pcibios0 at bios0: rev 2.1 @ 0xf0000/0x10000
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf77d0/160 (8 entries)
pcibios0: PCI Interrupt Router at 000:02:0 ("SiS 85C503 System" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc0000/0xc000 0xcc000/0x2200
acpi at mainbus0 not configured
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "SiS 746 PCI" rev 0x10
ppb0 at pci0 dev 1 function 0 "SiS 86C202 VGA" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "ATI Radeon VE QY" rev 0x00
wsdisplay0 ...
[ message continues ]

boot>
booting hd0a:/bsd: 5665588+872060 [52+291168+272312]=0x6c5c70
entry point at 0x200120


booting hd0a:/bsd: 5665588+872060 [52+291168+272312]=0x6c5c70
entry point at 0x200120*


Here's where I get slammed as the n00b I am.

It looks to me like they're looking at two different but related memory
locations. Look at the entry points "0x200120" vs "0x200120*"

Someone who understands what's going on better can comment on what this
means, but I'm almost willing to be there's a file somewhere you need to
recompile so it's looking at the correct location.

James





[ message continues ]

Yep, so far the only thing I've thought to do is re-install the
bootblocks which I already did.

I just can't figure out why there's a difference between letting it
boot automatically or interrupting the boot process to do the boot
hda0:/bsd.

Thanks for looking.



-- 
Ticketmaster and Ticketweb suck, but everyone knows that:
http://ticketmastersucks.org
http://lodesertprotosites.org
Dethink to survive - Mclusky

[ message continues ]

yeah, that is quite a puzzler.  Along with why the contents of the
panic come out on the CRT when you apparently have a serial console...

I'm really grasping at straws here...but what's in your /etc/boot.conf?
(and are you SURE?)
What happens if you just delete(/rename/hide) it?

what happens if you just "boot" instead of "boot hd0a:/bsd"?

ALSO...does anything different happen between a cold power-off/power-on
and a reboot?

Nick.

[ message continues ]

I originally had "set tty com0" in it but renamed it to boot.conf.bak

Well, this thing is very flaky.  It panicked using both "boot" and

Same behavior.

This isn't the first time that I've had strange boot problems with
cheap PCs.  I had a Pentium 133 at one time that I discussed with you
where OpenBSD wouldn't boot unless "boot" was in boot.conf, nor could
I interrupt the boot process with F8 and the like in Windows.  My
workaround on that box was to put a simple "boot" in boot.conf.  So...

...I did the same on this box and it boots with no problems.  I'll
have to keep an alternative boot method, CD, whatever, in case I need
stop the boot process.

Greg


-- 
Ticketmaster and Ticketweb suck, but everyone knows that:
http://ticketmastersucks.org
http://lodesertprotosites.org
Dethink to survive - Mclusky

[ message continues ]

What does appending boot do that  isn't otherwise done?  Inquiring minds
must know...

[ message continues ]