From owner-freebsd-current Wed Jan 13 11:56:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16040 for freebsd-current-outgoing; Wed, 13 Jan 1999 11:56:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtpott1.nortel.ca (smtpott1.nortel.ca [192.58.194.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15985 for ; Wed, 13 Jan 1999 11:55:59 -0800 (PST) (envelope-from atrens@nortelnetworks.com) Received: from zcars01t by smtpott1; Wed, 13 Jan 1999 14:54:37 -0500 Received: from wmerh01z.ca.nortel.com by zcars01t; Wed, 13 Jan 1999 14:54:03 -0500 Received: from hcarp00g.ca.nortel.com (atrens@hcarp00g.ca.nortel.com@wmerh01z) by wmerh01z.ca.nortel.com with ESMTP (8.7.1/8.7.1) id OAA02806; Wed, 13 Jan 1999 14:54:03 -0500 (EST) Date: Wed, 13 Jan 1999 15:03:13 -0500 (EST) From: "Andrew Atrens" Reply-To: "Andrew Atrens" To: lcremean@tidalwave.net cc: "Joseph T. Lee" , freebsd-current@FreeBSD.ORG Subject: Re: potential ide_pci.c bugster In-Reply-To: <19990113105152.A5109@tidalwave.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 13 Jan 1999, Lee Cremeans wrote: > Date: Wed, 13 Jan 1999 10:51:52 -0500 > From: Lee Cremeans > Reply-To: lcremean@tidalwave.net > To: Joseph T. Lee , "Atrens, Andrew (A.B.) [EXCHANGE:SKY:1V45:BNR]" , freebsd-current@FreeBSD.ORG > Subject: Re: potential ide_pci.c bugster > > > wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa > > wdc1: unit 0 (wd2): , LBA, 32-bit, multi-block-8, sleep-hack > > wd2: 258MB (528640 sectors), 524 cyls, 16 heads, 63 S/T, 512 B/S > > > > wd2: interrupt timeout (status 58 error 1) > > wd2: wdtimeout() DMA status 4 > > > > -current as of 10th. Error pops up once in a while with or without > > softupdates. I use it for /usr/src so nothing vital on it..yet. > > This drive is too old to support even multiword 2 DMA. If you're getting > timeouts, and they seem to only happen when accessing certain files or > areas, then your drive has some bad-but-not-totally-dead sectors on it, and > the drive electronics are being slow about correcting the error. > If this is the case you'll hear an audible `clicking' from the drive as it attempts to re-read the bad data block. I'm curious, why is the controller reporting that sleep-hack is enabled when the wdc flags indicate that it shouldn't be? you asked for: > wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa ~ inputted options `0xa' == `1010' ( DMA + 32-bit transfers ) you got: > wdc1: unit 0 (wd2): , LBA, 32-bit, multi-block-8, sleep-hack translates to options `0xd' == `1101' ( LBA, 32-bit, Sleep hack ) or, wdc1 at 0x170-0x177 irq 15 flags 0xd0ffd0ff on isa ~ So you didn't get the options you asked for :) -- This translation is taken from man wd(4) (and /sys/i386/isa/wd.c) which describes the flag bitset is mapped like so: 0000 0000 0000 0000 0000 0000 0000 0000 |||| |||+------ 0x1000 Use LBA addressing ||+------- 0x2000 Probe for and use DMA |+-------- 0x4000 APM Sleep hack +--------- 0x8000 Test and use the 32bit transfers Since the `flags' seems to be an `|' of device flags + controller flags, stored in isa_biotab_wdc[] and isa_devtab_bio[] in ioconf.c, the only way that I can see that sleep hack _could_ be `enabled' is if something is trashing those tables. Andrew. -- +----------------------------------------------------+ = Andrew Atrens - Nortel Networks (atrens@nortel.ca) = = P.O. Box 3511, Station C Ottawa, Canada = = = = All opinions expressed are mine, not Nortel's. = +----------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message