From owner-freebsd-hardware Wed Aug 20 15:25:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA13060 for hardware-outgoing; Wed, 20 Aug 1997 15:25:25 -0700 (PDT) Received: from lariat.lariat.org (ppp0.lariat.org@[129.72.251.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA13045 for ; Wed, 20 Aug 1997 15:25:19 -0700 (PDT) Received: from solo ([129.72.251.10] (may be forged)) by lariat.lariat.org (8.8.6/8.8.6) with SMTP id QAA23408; Wed, 20 Aug 1997 16:20:08 -0600 (MDT) Message-Id: <3.0.3.32.19970820162223.00967b70@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 20 Aug 1997 16:22:23 -0600 To: Anthony.Kimball@East.Sun.COM, pius@ienet.com From: Brett Glass Subject: Re: wdunwedge failed Cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: <882564F9.00799310.00@IWNS2.infoworld.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Actually, it is much more likely that the display is redrawing, erasing, and scrolling so fast that it appears blank or dim. Which means the messages are coming in at a rate of hundreds per second. The WD driver has some busy-waits that could easily cause the rest of the system to freeze at the same time. --Brett At 04:29 PM 8/20/97 -0500, alk@pobox.com wrote: > > > >Quoth pius@ienet.com on Wed, 20 August: >: It flickers. For example, a screen full of these "wdunwedge failed" error >: messages appears for a second or two and then the screen completely >blanks >: out for a second. Then the error messages are visible again briefly, then >: the screen goes blank, and so no. Sort of like someone quickly turning >the >: monitor on and off. >Sounds like a dead marmoset stuck in the transformer coils of your >power supply. Have you been routing in the rainforest lately? >Try releasing some mealworms to clean it out. >Pius, eh. Say, weren't you Pope for a while? > > > > > > >