From owner-freebsd-bugs Sat Oct 17 13:37:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22511 for freebsd-bugs-outgoing; Sat, 17 Oct 1998 13:37:16 -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 NAA22501; Sat, 17 Oct 1998 13:37:04 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id OAA07090; Sat, 17 Oct 1998 14:36:41 -0600 (MDT) Message-Id: <4.1.19981017143202.06f40410@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 17 Oct 1998 14:35:47 -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: <199810172023.WAA11624@sos.freebsd.dk> References: <4.1.19981017135219.06f00520@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 NAA22505 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 10:23 PM 10/17/98 +0200, Søren Schmidt wrote: >Hmm, not really I just took a look at the 2.2.7 wd.c... >Does your BIOS allow you to set the parameters used for the disk, >ie can you hardwire it to a specific PIO mode ?? Nope. There's no setting for that. This a 486 machine; the BIOS was developed before people talked about "PIO modes." >Maybe you already stated that, but what chipset does your machine(s) >have ?? Some chipsets does push the timing quite a bit which in >some cases causes problems. This is a Zeos "Rattler" board with an Intel chipset. The Saturn, I think. Here's what I see at boot time: FreeBSD 2.2.7-RELEASE #0: Fri Oct 16 23:54:10 MDT 1998 brett@lariat.lariat.org:/usr/src/sys/compile/LARIAT Calibrating clock(s) ... i8254 clock: 1193135 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency CPU: i486 DX4 (486-class CPU) Origin = "GenuineIntel" Id = 0x480 Stepping=0 Features=0x3 real memory = 16777216 (16384K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x001b4000 - 0x00ffdfff, 14983168 bytes (3658 pages) avail memory = 15065088 (14712K bytes) pcibus_setup(1): mode 1 addr port (0x0cf8) is 0x00000000 pcibus_setup(1a): mode1res=0x00000000 (0x80000000) pcibus_setup(1b): mode1res=0x00000000 (0xff000001) pcibus_setup(2): mode 2 enable port (0x0cf8) is 0x00 pcibus_setup(2a): mode2res=0x0e (0x0e) pcibus_setup(2a): now trying mechanism 2 pcibus_check: device 0 is there (id=04838086) Probing for devices on PCI bus 0: configuration mode 2 allows 16 devices. chip0 rev 4 on pci0:0:0 CPU: 486DX2 or 486DX4, bus=33MHz, CPU->Memory posting ON Warning: NO DRAM parity! Cache: 256KB writeback, cache clocks=2-1-1-1 DRAM: page mode code fetch, read and write, memory clocks=X-1-2-1 CPU->PCI: posting ON, burst mode ON PCI->Memory: posting OFF chip1 rev 3 on pci0:2:0 Bus Modes: Resource Lock, Coprocessor errors enabled Keyboard controller: 60h,62h,64h,66h RTC: 70h-77h Port 92: enabled vga0 rev 0 on pci0:13:0 mapreg[10] type=0 addr=10000000 size=800000. pci0: uses 8388608 bytes of memory from 10000000 upto 107fffff. Probing for devices on the ISA bus: ...etc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message