From owner-freebsd-bugs Fri Oct 4 12:21:08 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA08459 for bugs-outgoing; Fri, 4 Oct 1996 12:21:08 -0700 (PDT) Received: from gate.aix.can.ibm.com (gate.aix.can.ibm.com [204.138.188.66]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA08451 for ; Fri, 4 Oct 1996 12:21:04 -0700 (PDT) Received: from Mailhub by gate.aix.can.ibm.com id PAA05558; Fri, 4 Oct 1996 15:15:53 -0400 Received: from MailClients by Mailhub id PAA29600; Fri, 4 Oct 1996 15:16:34 -0400 Received: by drzook.mtlisc.can.ibm.com (AIX 4.1/UCB 5.64/4.03) id AA136298; Fri, 4 Oct 1996 15:21:50 -0400 Date: Fri, 4 Oct 1996 15:21:50 -0400 From: domenic@aix.can.ibm.com (Domenico P. Miele ing.) Message-Id: <9610041921.AA136298@drzook.mtlisc.can.ibm.com> To: bugs@freebsd.org Subject: new kernel at 2.1.5 Cc: avatar@aix.can.ibm.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Md5: vy1U0KDgw3XgXuCCJWkU5w== Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi folks, I've installed 2.1.5 and have no problems booting the generic kernel. When I boot from a kernel I've compiled I get the following error: =09 > Oct 3 20:48:06 eddie /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa > Oct 3 20:48:06 eddie /kernel: wdc0: unit 0 (wd0): > Oct 3 20:48:06 eddie /kernel: wd0: 251MB (515856 sectors), 977 cyls, = 11 heads, 48 S/T, 512 B/S > Oct 3 20:48:06 eddie /kernel: mcd0: type Mitsumi FX001D, version = info: D 4 > Oct 3 20:48:06 eddie /kernel: mcd0 at 0x300-0x303 irq 10 on isa > Oct 3 20:48:06 eddie /kernel: npx0 on motherboard > Oct 3 20:48:06 eddie /kernel: npx0: INT 16 interface > Oct 3 20:48:06 eddie /kernel: wd0: wdcontrol: wdcommand failed = reading=20 fsbn 0wd0: status ff = error 0 Yet the system still boots and runs fine. I've compile 2 different=20 kernels and the same error persists. I've searched thru the mailing lists and came up empty other than mere references to green mode and a failure to boot at 2.1 =09 Also looks like wdcommand that we require a wait ? =09 This answer as per Bruce Evans : =09 Callers of wdcommand() are required to check the status. Many callers (too many) check it immediately by calling wdwait(). The WDCS_ERR bit in the status register isn't valid until the WDCS_BUSY bit is clear, and it is necessary to wait for up to 31 seconds for it to become clear. Others wait for an interrupt before checking. They call wdwait() too. This is a bit wasteful because the WDCS_BUSY bit is probably already clear and the 450nsec delay before reading the status register is probably guaranteed by the slowness of getting to the interrupt handler. =09 anyone have any other ideas ? thanks, -- = `""""""' Domenico P. "drzook" Miele, P. Eng., M. Eng. "Use the Internet to | = = | IBM Canada Ltd. it's fullest potential" = OO--)| Internet: domenic@aix.can.ibm.com \__ (_ = = | IBMnet : domenic@drzook.mtlisc.can.ibm.com /\ = |____| tel: (514) 938-7378 (=3D(_><= \