Date: Tue, 7 Mar 2000 11:34:16 -0700 (MST) From: Nate Williams <nate@yogotech.com> To: Archie Cobbs <archie@whistle.com> Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Help: interrupt timeout Message-ID: <200003071834.LAA03194@nomad.yogotech.com> In-Reply-To: <200003070357.TAA38892@bubba.whistle.com> References: <200003070357.TAA38892@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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). Your disk went bad. It is probably unrelated to FreeBSD, but it may have occurred due to a bad interaction when the computer shut down. I had this happen on an old Thinkpad (486/25), and I was never able to get it to work reliably every since, since the bad spot on the disk kept getting hit with fsck. You may not have seen it prior because fsck never was run on the disk since it was shutdown gracefully, hence the bad sector was never accessed. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003071834.LAA03194>