From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 08:22:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9873916A4CF for ; Tue, 27 Jan 2004 08:22:23 -0800 (PST) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28ABD43D39 for ; Tue, 27 Jan 2004 08:21:38 -0800 (PST) (envelope-from dgerow@afflictions.org) Received: from dementia.afflictions.org (dementia [172.16.0.56]) by pandora.afflictions.org (Postfix) with ESMTP id D372D5D399 for ; Tue, 27 Jan 2004 11:51:54 -0500 (EST) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 0D1CF6D457; Tue, 27 Jan 2004 11:22:52 -0500 (EST) Date: Tue, 27 Jan 2004 11:22:51 -0500 From: Damian Gerow To: current@freebsd.org Message-ID: <20040127162251.GA90882@afflictions.org> References: <20040126035539.GP1456@sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040126035539.GP1456@sentex.net> X-Operating-System: FreeBSD 5.2-RC on a i386 X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.5.1i Subject: -CURRENT barfing on UDMA on Via 8233 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2004 16:22:23 -0000 Okay, it looks like some UDMA stuff broke sometime between 5.2-R and current as of two days ago. I couldn't boot into the system unless in 'safe mode', so I booted back into 5.2-R, re-sup'ed, rebuilt, and rebooted. Same issue as before: atapci0: port 0xd400-0xd40f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] ad0: 38166MB [77545/16/63] at ata0-master UDMA100 Mounting root from ufs:/dev/ad0s1a pid 86 (fsck_ufs), uid0: exited on signal 8 pid 87 (fsck_ufs), uid0: exited on signal 8 Okay, fine and dandy. Yes, a reboot with a dirty root resulted in the same repeated error message about needing to fsck root before R/W mounting it, but that's a separate problem. So I took a closer look at the 'Safe Mode' booting, and here's what I see instead: atapci0: port 0xd400-0xd40f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] ad0: 38166MB [77545/16/63] at ata0-master PIO4 Mounting root from ufs:/dev/ad0s1a And then it continues to boot normally. So I'm guessing that the UDMA (or possibly just UDMA100) support for the 8233 controller is pooched? FWIW, here's a snippet of a boot -v: ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ata0-master: setting PIO4 on VIA 8233 chip ata0-master: setting UDMA100 on VIA 8233 chip ad0: ATA-6 disk at ata0-master ad0: 38166MB (78165360 sectors), 77545 C, 16 H, 63 S, 512 B ad0: 16secs/int, 1 depth queue, UDMA100 GEOM: new disk ad0 [0]: f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:78156162 [1]: f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 e:0 l:0 [2]: f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 e:0 l:0 [3]: f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 e:0 l:0 GEOM: Configure ad0s1, start 32256 length 40015954944 end 40015987199 GEOM: Configure ad0s1a, start 1073741824 length 1073741824 end 2147483647 GEOM: Configure ad0s1b, start 0 length 1073741824 end 1073741823 GEOM: Configure ad0s1c, start 0 length 40015954944 end 40015954943 GEOM: Configure ad0s1d, start 2147483648 length 8589934592 end 10737418239 GEOM: Configure ad0s1e, start 10737418240 length 29278536704 end 40015954943 Mounting root from ufs:/dev/ad0s1a start_init: trying /sbin/init pid 86 (fsck_ufs), uid0: exited on signal 8 pid 87 (fsck_ufs), uid0: exited on signal 8 And then we hang. Again num/caps/scroll lock respond, so the whole machine isn't frozen, but FBSD doesn't respond to anything.