From owner-freebsd-questions Fri Oct 16 16:54:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18470 for freebsd-questions-outgoing; Fri, 16 Oct 1998 16:54:41 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18348 for ; Fri, 16 Oct 1998 16:53:46 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from ben by scientia.demon.co.uk with local (Exim 2.05 #3) id 0zUJgM-0001hn-00; Sat, 17 Oct 1998 00:53:18 +0100 Date: Sat, 17 Oct 1998 00:53:18 +0100 From: Ben Smithurst To: Doug White Cc: freebsd-questions@FreeBSD.ORG Subject: Re: wd0 wdunwedge errors Message-ID: <19981017005318.A5558@scientia.demon.co.uk> References: <19981015180227.A9191@scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: User-Agent: Mutt/0.94.12i (FreeBSD 3.0-BETA i386) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White wrote: > wdunwedge is a function in the IDE controller driver that gets called when > the interface timeouts too much and it needs to try to get the disk > restarted. Ah, I see. Like the name says really :-) > If you get this a lot your disk is going south, something is > sitting on IRQ 14 or your cables are going bad. Hmm.. I'm pretty sure no-one's sitting on IRQ 14, so I have to hope it's the cables. The disk's only about 18 months old, it can't be dead already :-( (Would BIOS disk power down settings cause this? I think they caused timeouts before[1], but it was only a single line I used to see for them. I haven't seen it for wd2, which takes ages to start up, so it probably isn't this.) I've seen no other problems with this disk, so I'll just hope it isn't too serious. [1] before what I don't know, probably before upgrading to -current, but I don't see them anymore. -- Ben Smithurst ben@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message