From owner-freebsd-hackers Sun Dec 8 12:13:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA22320 for hackers-outgoing; Sun, 8 Dec 1996 12:13:30 -0800 (PST) Received: from ican.net (ican.net [198.133.36.9]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA22315 for ; Sun, 8 Dec 1996 12:13:26 -0800 (PST) Received: from gate.ican.net(really [198.133.36.2]) by ican.net via sendmail with esmtp id for ; Sun, 8 Dec 1996 15:13:17 -0500 (EST) (Smail-3.2 1996-Jul-4 #1 built 1996-Jul-10) Received: (from smap@localhost) by gate.ican.net (8.7.5/8.7.3) id PAA02597 for ; Sun, 8 Dec 1996 15:10:10 -0500 (EST) Received: from nap.io.org(10.1.1.3) by gate.ican.net via smap (V1.3) id sma002595; Sun Dec 8 15:10:03 1996 Received: from localhost (taob@localhost) by nap.io.org (8.7.5/8.7.3) with SMTP id PAA16999 for ; Sun, 8 Dec 1996 15:07:15 -0500 (EST) X-Authentication-Warning: nap.io.org: taob owned process doing -bs Date: Sun, 8 Dec 1996 15:07:15 -0500 (EST) From: Brian Tao To: FREEBSD-HACKERS-L Subject: Odd booting problems with 2.2-ALPHA Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently installed 2.2-ALPHA on a handful of new workstations around the office, and noticed problems related to the boot procedure. The hardware is an Intel P166 on a Gigabyte 430VX motherboard: FreeBSD 2.2-ALPHA #0: Mon Nov 25 17:40:00 EST 1996 mattp@schmooze.io.org:/usr/local/src/sys/compile/SCHMOOZE Calibrating clock(s) relative to mc146818A clock ... i586 clock: 167066126 Hz, i8254 clock: 1193331 Hz CPU: Pentium (167.04-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 63856640 (62360K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 vga0 rev 3 on pci0:8 ahc0 rev 0 int a irq 11 on pci0:9 ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs (ahc0:1:0): "SEAGATE ST31051N 0284" type 0 fixed SCSI 2 sd0(ahc0:1:0): Direct-Access 1010MB (2069860 512 byte sectors) sd0(ahc0:1:0): with 4177 cyls, 4 heads, and an average 123 sectors/track (ahc0:4:0): "SONY CD-ROM CDU-76S 1.1c" type 5 removable SCSI 2 cd0(ahc0:4:0): CD-ROM cd present [216888 x 2048 byte records] de0 rev 17 int a irq 9 on pci0:10 de0: DC21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:cf:73:f2 [...] All the machines have experienced one of the two problems I want to describe. On random occasions when rebooting, the machine will simply freeze just after the initial kernel load message and before it prints the BIOS memory size check (the first line printed in bright white with the syscons driver). This can happen from power-on, coming from a DOS session, or rebooting from FreeBSD. The second problem happened to my machine today. I switched to a vty from the xdm console in order to login and shutdown the machine. The machine froze when it should have given me the "Password:" prompt. I didn't catch any kernel messages (couldn't switch to vty0), and it rebooted itself. The boot cycle stopped at the "WARNING: / was not properly dismounted." kernel message. There was no disk or screen activity from the expected fsck. Hard resets and power cycles do not cure the problem. Booting into single-user mode hangs at the same place. I haven't had a chance to pull out the drive and mount it on another machine yet, so there may be some critical filesystem corruption going on in /etc or /bin that I haven't found yet. There was no activity to the mounted DOS filesystems. Any ideas why the boot process might hang at the point it should be running /etc/rc, without any sort of error messages or diagnostics? -- Brian Tao (BT300, taob@io.org, taob@ican.net) Senior Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't"