From owner-freebsd-stable Mon Mar 6 21:25:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cytosine.dhs.org (cx272244-a.orng1.occa.home.com [24.1.177.149]) by hub.freebsd.org (Postfix) with ESMTP id 2455B37BE01; Mon, 6 Mar 2000 21:25:32 -0800 (PST) (envelope-from bhishan@cytosine.dhs.org) Received: (from bhishan@localhost) by cytosine.dhs.org (8.9.3/8.9.3) id VAA09958; Mon, 6 Mar 2000 21:25:20 -0800 (PST) (envelope-from bhishan) From: Bhishan Hemrajani Message-Id: <200003070525.VAA09958@cytosine.dhs.org> Subject: Re: Help: interrupt timeout In-Reply-To: from Chris Byrnes at "Mar 6, 2000 10:02:34 pm" To: Chris Byrnes Date: Mon, 6 Mar 2000 21:25:20 -0800 (PST) Cc: Archie Cobbs , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I sometimes have this problem with my pc. Usually, a good kick will get it to boot. Sometimes on laptops and stuff the hard drive cable gets loose or something. Or, it's a bad hard drive. Try giving is a shove. --bhishan > 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: rev 0x01 on pci0.0.0 > > > chip1: rev 0x02 on pci0.7.0 > > > ide_pci0: rev 0x01 on pci0.7.1 > > > ... > > > wdc0 at 0x1f0-0x3f7 irq 14 on isa > > > wdc0: unit 0 (wd0): > > > 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): , removable, accel, dma, iordis > > > ... > > > # fsck / > > > *** /dev/rwd0s3a > > > *** Last Mounted on / > > > *** Root file system > > > *** Phase 1 - Check Blocks and Sizes > > > wd0: interrupt timeout (status 58 error 0) > > > wd0: wdtimeout DMA status 4 > > > wd0: interrupt timeout (status 50 error 1) > > > wd0: wdtimeout DMA status 4 > > > wd0: interrupt timeout (status 50 error 1) > > > wd0: wdtimeout DMA status 4 > > > wd0: interrupt timeout (status 50 error 1) > > > wd0: wdtimeout DMA status 4 > > > wd0: interrupt timeout (status 50 error 1) > > > wd0: wdtimeout DMA status 4 > > > wd0: Last time I say: interrupt timeout. Probably a portable PC. (status 50 error 1) > > > > 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-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message