From owner-freebsd-stable Wed Mar 8 7: 6:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 1DC2737C058 for ; Wed, 8 Mar 2000 07:06:55 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id HAA28124; Wed, 8 Mar 2000 07:05:36 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda28122; Wed Mar 8 07:05:22 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id HAA66109; Wed, 8 Mar 2000 07:05:22 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdW66099; Wed Mar 8 07:05:20 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id HAA02774; Wed, 8 Mar 2000 07:05:19 -0800 (PST) Message-Id: <200003081505.HAA02774@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdTr2769; Wed Mar 8 07:05:09 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Bhishan Hemrajani Cc: Chris Byrnes , Archie Cobbs , freebsd-stable@FreeBSD.ORG Subject: Re: Help: interrupt timeout In-reply-to: Your message of "Mon, 06 Mar 2000 21:25:20 PST." <200003070525.VAA09958@cytosine.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Mar 2000 07:05:09 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003070525.VAA09958@cytosine.dhs.org>, Bhishan Hemrajani writes: > 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 It's quite possibly a hardware problem though I'm not entirely convinced that it's a fatal hardware problem. I have an IDE drive, wd2 below, wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (wd2): , DMA, 32-bit, multi-block-16 wd2: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S that occasionally has these errors under heavy load conditions, like fscking a badly damaged filesystem. It's done this since it was brand new over four years ago. The Western Digital diagnostics (just checked last week) reported no grown defects, and the Western Digital firmware utility says it doesn't need a firmware upgrade. Interestingly enough, the errors weren't bad enough to halt the system or abort an fsck. Could it be a software problem? Maybe, maybe not. Notice wd0. It too is a Western Digital drive, just older. It's had no problems, ever. Having said all that, I had a couple of WD Caviar WDAC280 drives that would cause an error message once every two to four years. When they had errors, the Western Digital diagnostics would fix them up and they'd run happily for another few years. Each drive had a couple of grown defects. I retired them after 8 years of service. One is still running in a Windows 3.1 PC, 11 years after I purchased it and the other serves quite well as a paper weight and would probably run nicely if it was still in use. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC "COBOL IS A WASTE OF CARDS." > > > 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. (stat > us 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.c > om > > > > > > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message