Subject: port-i386/4556: i386 boot blocks in 1.3_ALPHA can cause infinite reboots
To: None <>
From: Eric S. Hvozda <>
List: netbsd-bugs
Date: 11/21/1997 09:13:11
>Number:         4556
>Category:       port-i386
>Synopsis:       Without intervention, i386 boot blocks can reboot a machine forever
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    gnats-admin (GNATS administrator)
>State:          open
>Class:          support
>Submitter-Id:   net
>Arrival-Date:   Fri Nov 21 06:20:01 1997
>Release:        NetBSD 1.3_ALPHA supped 19Nov97
System: NetBSD 1.3_ALPHA NetBSD 1.3_ALPHA (RA) #0: Thu Nov 20 21:37:02 EST 1997 i386

IWill P55XUW
64Mb parity memory
Adaptec Fast SCSI-2 PCI Host Adapter
Fujitsu M2684S FAST SCSI-2 hard disk

ahc0 and sd0 are the booting devices in this machine.

NetBSD 1.3_ALPHA (RA) #0: Thu Nov 20 21:37:02 EST 1997
cpu0: family 5 model 2 step c
cpu0: Intel Pentium (P54C) (586-class)
real mem  = 66715648
avail mem = 60477440
using 840 buffers containing 3440640 bytes of memory
mainbus0 (root)
pci0 at mainbus0 bus 0: configuration mode 1
pchb0 at pci0 dev 0 function 0
pchb0: Intel 82439TX System Controller (MTXC) (rev. 0x01)
pcib0 at pci0 dev 7 function 0
pcib0: Intel 82371AB PCI-to-ISA Bridge (PIIX4) (rev. 0x01)
Intel 82371AB IDE controller (PIIX4) (IDE mass storage, interface 0x80, revision 0x01) at pci0 dev 7 function 1 not configured
Intel 82371AB USB Host Controller (PIIX4) (USB serial bus, revision 0x01) at pci0 dev 7 function 2 not configured
Intel 82371AB Power Management Controller (PIIX4) (miscellaneous bridge, revision 0x01) at pci0 dev 7 function 3 not configured
ahc0 at pci0 dev 8 function 0
ahc0: interrupting at irq 10
ahc0: Reading SEEPROM...done.
ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs
ahc0: Resetting Channel A
ahc0: Downloading Sequencer Program...Done
scsibus0 at ahc0 channel 0: 8 targets
ahc0: target 1 synchronous at 10.0MHz, offset = 0xf
sd0 at scsibus0 targ 1 lun 0: <FUJITSU, M2684S-512, 2036> SCSI2 0/direct fixed
sd0: 507MB, 2380 cyl, 6 head, 72 sec, 512 bytes/sect x 1039329 sectors
ahc0: target 5 synchronous at 4.0MHz, offset = 0xf
cd0 at scsibus0 targ 5 lun 0: <TOSHIBA, CD-ROM XM-3601TA, 0725> SCSI2 5/cdrom removable
ahc0: target 6 synchronous at 10.0MHz, offset = 0xf
cd1 at scsibus0 targ 6 lun 0: <MATSHITA, CD-ROM CR-506, 8S05> SCSI2 5/cdrom removable
bha0 at pci0 dev 9 function 0: BusLogic 9xxC SCSI
bha0: interrupting at irq 9
bha0: model BT-946C, firmware 4.25J
bha0: sync, parity
bha0 targ 0: sync, offset 15, period 100nsec
bha0 targ 4: sync, offset 15, period 200nsec
scsibus1 at bha0: 8 targets
sd3 at scsibus1 targ 0 lun 0: <MICROP, 4221-09   1128RQ, 28RQ> SCSI2 0/direct fixed
sd3: 1955MB, 4048 cyl, 9 head, 109 sec, 512 bytes/sect x 4004219 sectors
st0 at scsibus1 targ 4 lun 0: <ARCHIVE, Python 28849-XXX, 4.CM> SCSI2 1/sequential removable
st0: drive empty
ch0 at scsibus1 targ 4 lun 1: <ARCHIVE, Python 28849-XXX, 4.CM> SCSI2 8/changer removable
ch0: 0 slots, 1 drive, 1 picker, 0 portals
Matrox product 0x051b (VGA display) at pci0 dev 10 function 0 not configured
ep0 at pci0 dev 11 function 0: 3Com 3C905 Ethernet
ep0: MAC address 00:60:08:42:9f:7b
ep0: 8KB word-wide FIFO, (undefined) Rx:Tx split, mii default mii, autoselect
ep0: interrupting at irq 11
ahc1 at pci0 dev 12 function 0
ahc1: interrupting at irq 10
ahc1: Reading SEEPROM...checksum error
ahc1: No SEEPROM availible
ahc1: Using left over BIOS settings
ahc1: aic7880 Wide Channel, SCSI Id=7, 16 SCBs
ahc1: Resetting Channel A
ahc1: Downloading Sequencer Program...Done
scsibus2 at ahc1 channel 0: 16 targets
ahc1: target 2 synchronous at 10.0MHz, offset = 0xf
sd1 at scsibus2 targ 2 lun 0: <FUJITSU, M2684S-512, 2039> SCSI2 0/direct fixed
sd1: 507MB, 2380 cyl, 6 head, 72 sec, 512 bytes/sect x 1039329 sectors
ahc1: target 3 synchronous at 10.0MHz, offset = 0xf
sd2 at scsibus2 targ 3 lun 0: <FUJITSU, M2684S-512, 2039> SCSI2 0/direct fixed
sd2: 507MB, 2380 cyl, 6 head, 72 sec, 512 bytes/sect x 1039328 sectors
isa0 at pcib0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
lpt0 at isa0 port 0x378-0x37b: polled
npx0 at isa0 port 0xf0-0xff: using exception 16
pc0 at isa0 port 0x60-0x6f irq 1: color
pms0 at pc0 irq 12
spkr0 at pc0 port 0x61
pc0: console
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
isapnp0 at isa0 port 0x279: read port 0x203
sb0 at isapnp0 port 0x220/16,0x330/2,0x388/4 irq 5 drq 1,5
sb0: Creative ViBRA16C PnP Audio: dsp v4.13
audio0 at sb0
joy0 at isapnp0 port 0x200/8
joy0: Creative ViBRA16C PnP Game
joy0: joystick not connected
biomask 640 netmask e40 ttymask 1e42
boot device: sd0
root on sd0a dumps on sd0b
init: copying out path `/sbin/init' 11

	After installing the new boot blocks on my new P5-200, I noticed
	if I reboot the machine unattended, the machine continues to
	reboot itself.

	However, if one simply presses return during the count down
	all will be well and the machine will boot successfully.
	Install NetBSD 1.3_ALPHA on disks that previously held
	NetBSD 1.2.1.  Notice upon reboot you're still using old
	boot blocks.  Install new boot blocks as follows:

	cd /usr/mdec
	./installboot -v biosboot.sym /dev/rsd0a

	Reboot the machine.  Be patient, don't press return to force
	the boot blocks to boot NetBSD *now*.  Notice that during
	kernel load the machine reboots.  Notice it always seems to
	reboot after printing the left bracket '['.  Sit there
	and notice the machine just keeps rebooting itself.

	However, after some experimentation note that any key press
	while the boot blocks are in control of the the machine,
	the kernel will load no problem and get on with life.

	I will probably downgrade to 1.2.1 boot blocks if I can
	find my old rescue floppies.  However, I can see how
	this could be a show stopper for installing 1.3 on
	some machines.  I currently wonder how many other
	machines are affected by this.
	Unknown at this time, I did not have this problem before 
	I upgraded the boot blocks from the 1.2.1 boot blocks.

	I am more than willing to test new bootblocks on demand to
	get this issue resolved.