From owner-freebsd-mobile Sat Apr 25 09:10:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10949 for freebsd-mobile-outgoing; Sat, 25 Apr 1998 09:10:13 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from jli.com (jli.com [199.2.111.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA10864 for ; Sat, 25 Apr 1998 09:10:02 -0700 (PDT) (envelope-from trost@cloud.rain.com) Received: (qmail 10167 invoked by uid 4); 25 Apr 1998 16:09:22 -0000 Received: (qmail 6260 invoked from network); 25 Apr 1998 16:08:40 -0000 Received: from softdnserror (127.0.0.1) by softdnserror with SMTP; 25 Apr 1998 16:08:40 -0000 To: jamin@eecs.umich.edu Subject: Re: error message cc: mobile@FreeBSD.ORG References: <199804241503.LAA08393@irl.eecs.umich.edu> In-reply-to: Your message of Fri, 24 Apr 1998 11:03:22 EDT. <199804241503.LAA08393@irl.eecs.umich.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6256.893520520.1@cloud.rain.com> Date: Sat, 25 Apr 1998 09:08:40 -0700 Message-ID: <6257.893520520@cloud.rain.com> From: Bill Trost Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sugih Jamin writes: I'm running FreeBSD 2.2.5-RELEASE with PAO on my Sony Vaio 505EX. You're using a *Vaio*? I didn't think X would work on those!? wd0: interrupt timeout: followed by: wd0: status 50 error 0 or wd0: status 58 error 0 or wd0: status 58 error 1 It sounds like the disk is spinning down but is immediately woken up again by the OS trying to write something. That is somewhat typical behaviour. If you have your disk timeout set to 5 minutes in the BIOS, and cron running atrun every 5 minutes, you could easily be seeing behavior like that. Atrun is not the only reason your disk might be getting hit all the time. You might nuke atrun (or at least make it less frequent) and/or change the disk spin-down interval. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message