From owner-freebsd-stable  Mon Mar  6 20: 2:49 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ns1.highstability.com (ns1.highstability.com [216.114.10.34])
	by hub.freebsd.org (Postfix) with ESMTP
	id A2B5B37BF1D; Mon,  6 Mar 2000 20:02:43 -0800 (PST)
	(envelope-from chrisb@highstability.com)
Received: from localhost (chrisb@localhost)
	by ns1.highstability.com (8.9.3/8.9.3) with ESMTP id WAA78478;
	Mon, 6 Mar 2000 22:02:34 -0600 (CST)
Date: Mon, 6 Mar 2000 22:02:34 -0600 (CST)
From: Chris Byrnes <chrisb@highstability.com>
To: Archie Cobbs <archie@whistle.com>
Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
Subject: Re: Help: interrupt timeout
In-Reply-To: <200003070357.TAA38892@bubba.whistle.com>
Message-ID: <Pine.BSF.4.10.10003062202020.78468-100000@ns1.highstability.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I've had the same problem.  Most people have told me that I have to
replace the hard drive.

I never had the problem before 3.4.  Maybe that's just a coincidence,
though.


--
Chris Byrnes (CB5820)
Network Engineer, High Stability Internet Services
http://www.highstability.com

On Mon, 6 Mar 2000, Archie Cobbs wrote:

> My laptop running 3.4-RELEASE decided it doesn't want to boot.
> It was uncleanly shut down via the power switch by someone
> who thought they were shutting down a different machine.
> 
> Now when it boots, running fsck gives this result:
> 
> > chip0: <Intel 82439TX System Controller (MTXC)> rev 0x01 on pci0.0.0
> > chip1: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.7.0
> > ide_pci0: <Intel PIIX4 Bus-master IDE controller> rev 0x01 on pci0.7.1
> > ...
> > wdc0 at 0x1f0-0x3f7 irq 14 on isa
> > wdc0: unit 0 (wd0): <TOSHIBA MK6409MAV>
> > wd0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T 512 B/S
> > wdc1 at 0x170-0x177 irq 15 on isa
> > wdc1: unit 0 (atapi): <MATSHITADVD-ROM SR-8171/058A>, removable, accel, dma, iordis
> > ...
> > # fsck /
> > *** /dev/rwd0s3a
> > *** Last Mounted on /
> > *** Root file system
> > *** Phase 1 - Check Blocks and Sizes
> > wd0: interrupt timeout (status 58<rdy,seekdone> error 0)
> > wd0: wdtimeout DMA status 4
> > wd0: interrupt timeout (status 50<rdy,seekdone> error 1<no_dam>)
> > wd0: wdtimeout DMA status 4
> > wd0: interrupt timeout (status 50<rdy,seekdone> error 1<no_dam>)
> > wd0: wdtimeout DMA status 4
> > wd0: interrupt timeout (status 50<rdy,seekdone> error 1<no_dam>)
> > wd0: wdtimeout DMA status 4
> > wd0: interrupt timeout (status 50<rdy,seekdone> error 1<no_dam>)
> > wd0: wdtimeout DMA status 4
> > wd0: Last time I say: interrupt timeout.  Probably a portable PC. (status 50<rdy,seekdone> error 1<no_dam>)
> 
> Well, yes in fact it is a portable PC :-)  It just seems to hang
> at this point, even though there seems to be disk activity (like
> it's continuously retrying).
> 
> This machine has run fine under this kernel since I installed
> 3.4-REL a month ago or so. This same problem happens with the
> 3.4-REL GENERIC kernel.
> 
> Before this, it was running fine with a 3.0++ kernel and never
> had this problem after many power cycles.
> 
> Is there any hope in getting this machine to work again??
> Howabout disabling DMA? Is there some way to do that?
> 
> Thanks for any pointers..
> -Archie
> 
> ___________________________________________________________________________
> Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message