From owner-freebsd-questions Tue Jan 11 14:19:55 2000 Delivered-To: freebsd-questions@freebsd.org Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by hub.freebsd.org (Postfix) with ESMTP id DB49414F7B for ; Tue, 11 Jan 2000 14:19:47 -0800 (PST) (envelope-from bartequi@nojunk.com) Received: from bartequi.ottodomain.org (ppp39-pa4.neomedia.it [195.103.207.231]) by aragorn.neomedia.it (8.9.3/8.9.3) with SMTP id XAA04789 for ; Tue, 11 Jan 2000 23:19:44 +0100 (CET) From: Salvo Bartolotta Date: Tue, 11 Jan 2000 22:21:16 GMT Message-ID: <20000111.22211600@bartequi.ottodomain.org> Subject: Re: Re: Newbie has a lot of questions - APM, ASUS mainboard and Pentium III To: freebsd-questions@FreeBSD.ORG References: <20000111.8533800@bartequi.ottodomain.org> X-Mailer: Supercalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear readers, I am afraid that John was somehow right. I appear to have discovered a minor bug, which seems to have "ethical" connotations, so to speak. If I boot just after a "shutdown -p now", I get a "WARNING: / was not properly dismounted" error. I have investigated the problem just a little. The result is surprising: AFAICS, the error only occurs when I issue "shutdown -p now" *immediately* after my login. If I do anything requiring a little "syncing disks", like opening a few windows or saving a few files, NO error is displayed at the subsequent boot. I would never have noticed it if John had not set me thinking. In fact, I usually perform quite a few tasks on my system. I confess that I even find it difficult to call it a proper bug ... My platform is much like John's: ASUS P2B-F AGP motherboard, Pentium III 450MHz, 384 MB RAM etc.; FreeBSD 3.3-Release: kernel options: options "VM86" device apm0 at isa? Incidentally, at boot time, two short messages are displayed about BIOS basemem and extmem (64MB), the latter not corresponding to (RTC) RAM (384MB). These messages are not logged in /var/log/messages, either. AFAICS, the OS sees my real memory (correctly indicated) and simply *ignores* what the BIOS extmem reports. Somehow, the OS considers the two "BIOS" messages even NOT worth logging ... Apart from this curious little anomaly, my system seems to work with no problems. All of my RAM is seen (real memory=3D393216K bytes) and used. On the other hand, I reproduced the above-described situation (shutdown -p now just after a login) for testing purposes only. Normally, "shutdown -p now" gives rise to no boot errors on my system. Finally, AFAIR, no such errors have occurred under R.H. Linux 6.1. Evidently, FreeBSD does NOT tolerate laziness ... ;-) Best regards Salvo N.B. myjokingdomain =3D=3D=3D> neomedia.it to e-mail to me. ******************************* * * * Windows: brain-dead limits * * BeOS: limited apps * * Linux: unlimited (mindset) * * FreeBSD: no limits * * * ******************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message