Sorry if this is lengthy, but it gives full background.
I installed a back-up hd (from different computer) into a computer that 
I haven't used for some time.
It had openbsd-4.1 (generic kernel) installed. I booted and the system 
hung after probing floppy drive.
Last line I see: fd0 at fdc0 drive 0: 1.44MB 80cyl, 2 head, 18 sec
I re-booted and the same thing. I let the system run for 15 minutes to 
see if it would finish. It didn't
I rebooted with 4.2 install cd that I used to install 4.2 on a different 
computer, and upgraded 4.1 to 4.2.
Everything went well till I rebooted and the system hung/froze at the 
exact same spot. Thinking something was amiss in /etc, I rebooted with 
cd, and did a fresh install after deleting / and swap partition. 
Installation went smooth, and then I rebooted.
4.2 (Generic) hung/froze at the same line again. I rebooted and disabled 
usb in cmos to see if that would correct the problem. It didn't. 
Re-booting again, I booted with bsd.rd and the system booted fine. At 
the prompt, I selected "s", mounted my wd0a partition and a linux 
partition, copied the "messages" and "dmesg.boot" files to the linux 
partition.
Those files are both about 17k and I can add them if helpful.
This system I am trying to use is a Ali motherboard, 900mhz athlon, 512 
megs ram and 512 megs swap.
I tried searching for an answer but didn't see anything quite like this.

Which file would be helpful?  I can add either file or both, but again, 
they are 17k

Thanks.

btw- there was no disk activity, keyboard wasn't responsive. Nothing 
worked but reset button even after sitting for 30 minutes on last try 
before using bsd.rd

[ message continues ]

Post dmesg.boot inline in your email. Do that by default whenever you
have a hardware problem. It sounds like there is something else weird
going on. Obviously some driver in /bsd that isn't in /bsd.rd is
hanging because your hardware is some weird case (or maybe broken). Is
there anyway to diff the enabled drivers between the two?

-Nick

[ message continues ]

Here is complete dmesg.boot (contains part of older dmesg)

 vt100 emulation)
alipm0 at pci0 dev 17 function 0 "Acer Labs M7101 Power" rev 0x00: 74KHz 
clock
iic0 at alipm0
iic0: addr 0x2d 00=20 01=80 03=40 04=c2 0d=61 0e=ab 0f=50 13=9e 14=b4 15=c8
ohci1 at pci0 dev 20 function 0 "Acer Labs M5237 USB" rev 0x03: irq 10, 
version 1.0, legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0: Acer Labs OHCI root hub, rev 1.00/1.00, addr 1
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
midi1 at pcppi0: <PC speaker>
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
usb1 at ohci1: USB revision 1.0
uhub1 at usb1: Acer Labs OHCI root hub, rev 1.00/1.00, addr 1
biomask ef6d netmask ef6d ttymask ffef
pctr: user-level cycle counter enabled
mtrr: Pentium Pro MTRR support
dkcsum: wd0 matches BIOS drive 0x80
root on wd0a swap on wd0b dump on wd0b
syncing disks...
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) Processor ("AuthenticAMD" 686-class, 256KB L2 
cache) 901 MHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
real mem  = 536375296 (511MB)
avail mem = 511008768 (487MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 07/09/01, BIOS32 rev. 0 @ 0xfdad0, 
SMBIOS rev. 2.3 @ 0xf0600 (21 entries)
bios0: vendor American Megatrends Inc.         version 
"062710                          " date 07/15/97                       
bios0: PCCHIPS M817LMR
apm0 at bios0: Power Management spec V1.2
apm0: AC ...
[ message continues ]

I assume that the drive you just inserted is the only one in that
box, and you are booting from this drive. Please confirm, or give
some description of what drives are in the box and which one you are

Why would it? It's fdc that is making it freeze, not USB.


Do a clean install of 4.2, and save the output
of dmesg just before you halt-and-reboot (obviously,
save it somewhere outside the box.)

Then halt-and-reboot, see if it hangs. If it does not,
save the complete dmesg again. If it does, try disabling
fdc as shown above; if it boots now, save the dmesg
(and make the change to your kernel permanent via config(8)).

Then study the difference between the two dmesg's carefully,
and send both dmesg's to the list.

	Jan

[ message continues ]

I heard the system probe the floppy drive, so thinking it was done with 
that, the next 2 lines in sequence are:
usb1 at ohci1: USB revision 1.0
uhub1 at usb1: Acer Labs OHCI root hub, rev 1.00/1.00, addr 1

I thought that is where the system was hanging/freezing/ in a 
the linux partition/system (debian) that i am on now to write about the 
Will do that after trying the disable fdc*
Thanks!

[ message continues ]

Ok, just tried rebooting with your suggestion of:

boot -c
disable fdc*
boot

Actually, I had to "quit" instead of "boot"

It stopped at the same place: fd0 at fdc0 drive 0: 1.44MB 80cyl, 2 head, 18 sec
Perhaps I should say that is the last line visible. 

This box is just a home pc on a single hd, 1 primary partition for openbsd and 3 logical partitions for linux. 
It is not a server to/for anything. This one is just for home stuff connected to internet on cable.

I will try another fresh install and save the dmesg after installation and after rebooting (if successful).

Thanks again.

[ message continues ]

Enable "verbose" in ukc.  It often shows silent probes that fail and
lock the system before they can print out that they've failed.


[ message continues ]

Thanks everybody.
I did *another* fresh install and this time the system boots after 
installation.
I have done 4 reboots. Each reboot was after modifying a file in /etc 
(sudoers, /mail/aliases), and adding programs.

I don't know why the system wouldn't boot after previous upgrading and 
then fresh install, but it seems to be working fine now. I also saved 
dmesg immediately after installation, and then after the first reboot.

Now to get back on openbsd and get mutt set-up :)

Thanks again Jan, Nick, and everybody else.

[ message continues ]