From owner-freebsd-bugs Sat Oct 17 12:24:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13630 for freebsd-bugs-outgoing; Sat, 17 Oct 1998 12:24:38 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13613; Sat, 17 Oct 1998 12:24:34 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id NAA06399; Sat, 17 Oct 1998 13:24:07 -0600 (MDT) Message-Id: <4.1.19981017130810.06f04590@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 17 Oct 1998 13:23:16 -0600 To: sos@FreeBSD.ORG From: Brett Glass Subject: Re: Crash workaround: ATAPI and ATAPI_STATIC required in 2.2.7 wd driver Cc: bugs@FreeBSD.ORG In-Reply-To: <199810171905.VAA11389@sos.freebsd.dk> References: <4.1.19981017121426.06ec3ea0@mail.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id MAA13619 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 09:05 PM 10/17/98 +0200, Søren Schmidt wrote: >Hmm, I doing a rewrite (slowly :( ) of the ata/atapi system, but the >problem you see I've never heard of before. What kind of drives do >you have We have several, but the machine that acted up first had a Western Digital Caviar 32500. Here are the messages displayed during a boot with the -v (verbose) boot option: wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S >and what flags do you have on the wd driver ?? The defaults. >The only thing that I can come up with is that the ATAPI options >alters the timing a bit... Are you sure? It seems to me that there might be an error in buffering (hence the page faults) or in IRQ handling. I don't know the code well enough to tell, though. (I'd love to become a FreeBSD kernel hacker, but can find no good reference on register use conventions, timing conventions, kernel data structures, etc. -- and I know that one can't always glean these subtleties from the code. The one time I hacked the wd driver and published some changes, I was told that I'd broken a bunch of rules, though the code somehow worked. But anyway, this is a side issue.) There's got to be some reason why the code is trying to access invalid addresses in one case but not the other.... --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message