From owner-freebsd-current@FreeBSD.ORG Fri Feb 6 09:29:20 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 B835C16A4CE for ; Fri, 6 Feb 2004 09:29:20 -0800 (PST) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4ACB43D41 for ; Fri, 6 Feb 2004 09:29:18 -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 602575D576 for ; Fri, 6 Feb 2004 12:57:37 -0500 (EST) Received: by dementia.afflictions.org (Postfix, from userid 1001) id EF0B76D42B; Fri, 6 Feb 2004 12:28:34 -0500 (EST) Date: Fri, 6 Feb 2004 12:28:34 -0500 From: Damian Gerow To: freebsd-current@freebsd.org Message-ID: <20040206172834.GK11717@afflictions.org> References: <20040126035539.GP1456@sentex.net> <20040127162251.GA90882@afflictions.org> <87oesdcqcd.fsf@strauser.com> <20040205192132.GA11676@afflictions.org> <87brodco8c.fsf@strauser.com> <20040205203316.GB11717@afflictions.org> <87ekt9b5ki.fsf@strauser.com> <20040205211614.GE11717@afflictions.org> <20040205220949.GF11717@afflictions.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040205220949.GF11717@afflictions.org> 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: Re: -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: Fri, 06 Feb 2004 17:29:20 -0000 Thus spake Damian Gerow (dgerow@afflictions.org) [05/02/04 17:09]: : One dump, and 45 minutes of bonnie++ later, I am having *zero* issues : running at UDMA100. So it looks like my problem is just in the boot : process. It may or may not be disk mode related, that was my assumption, as : it dies on boot when mounting /, and the difference between normal boot and : Safe Mode (that works for me) is UDMA100 vs. PIO4. : : So. It looks like I don't have any problem /running/ at UDMA100, just : /booting/ at UDMA100. A little more information... I just went through some testing (and have fubared my system) to try to narrow this down a bit more. If I soft reboot, I cannot boot with UDMA enabled. If I hard reboot, I cannot boot with UDMA enabled. If I disable DMA in the BIOS, FreeBSD still boots with UDMA enabled (even though the BIOS summary screen shows the drive in PIO4 mode). When it gets to the point of fsck_ufs dying, two things to note: 1) It registers the Linux compatibility module *after* the two messages indicating fsck's death. 2) If I ctrl+alt+del, the system goes through a normal reboot process (albeit after a small wait). If I just hit the reset switch, all filesystems are marked dirty on next reboot. It appears as though during one of my reboots, I screwed up one of my filesystems -- pam_self.so cannot be found, so I cannot log in. I don't know how to boot into Safe Mode manually, and the only way to get the system up at this point is to boot into single user mode via safe mode. I ran some more tests overnight, and I can actually run the system in DMA mode without problems. I just can't boot with DMA enabled. For whatever reason.