From owner-freebsd-questions  Mon Jul 21 10:14:54 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA25576
          for questions-outgoing; Mon, 21 Jul 1997 10:14:54 -0700 (PDT)
Received: from gdi.uoregon.edu (cisco-ts10-line11.uoregon.edu [128.223.150.109])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA25570
          for <questions@FreeBSD.ORG>; Mon, 21 Jul 1997 10:14:50 -0700 (PDT)
Received: from localhost (dwhite@localhost)
          by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id KAA01316;
          Mon, 21 Jul 1997 10:14:42 -0700 (PDT)
Date: Mon, 21 Jul 1997 10:14:42 -0700 (PDT)
From: Doug White <dwhite@gdi.uoregon.edu>
X-Sender: dwhite@localhost
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Christopher Rose <crose@mogli.rutgers.edu>
cc: FreeBSD Questions <questions@FreeBSD.ORG>
Subject: Re: stupid toshiba laptop
In-Reply-To: <9707191823.AA01223@mogli>
Message-ID: <Pine.BSF.3.96.970721101255.1259H-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 19 Jul 1997, Christopher Rose wrote:

> I'm not even sure you're the right folks to contact about this but
> here goes anyway:
> 
> 1) Toshiba laptop (tecra 510CDT with 2.xG disk)
> 
> 2) Problem: disk error messages, specifically
> timeout and busy errors which hang the system.
> Particularly bad if you try to run a bad block check.
> Drive gets into a loop which makes it go
> brpbrpbrp...  until cows come home (never since I live
> in a city).

Hm....

> 3) Even more specifically:
> 
> a) Freebsd v2.2.2
> b) Cdrom installation
> 
> c) Installing on second half of hard disk (enhanced ide controller)
> (linux is on first half... will deep six whichever one gives more
> trouble... linux has similar problems but seems to work around them [
> then crash much later :)]
> 
> d) Disk Error messages:
> 
> 	wd0: interrupt timeout:
> 	wd0: status 50 <rdy,seekdone> error 0
> 	wd0: interrupt timeout:
> 	wd0: status 50 <rdy,seekdone> error 1<no_dam>
> 
> then complete and utter disk thrashing.

Have you tried disabling IDE spindown?  That's what usually spawns those
messages.

Or disk overheating.

> e) Just wierd (to me):
> 	Disk is 4200/16/63 but BIOS insists that
> 	it's 525/128/63.  Might this be a problem?
> 	I have not tried forcing the geometry
> 	yet, but will do so soon at the rate I'm going

No, it should be OK.  If you got installed, you're fine :)

> 1) Is this a known OS problem with this particular type of laptop?

Not that I know of.  Laptops are a weird breed though.

> 
> 2) Does this in your great experience sound more like a disk
> controller problem (toshiba has been singularly unhelpful... want to
> sequester my machine for 2 weeks while they brood over the problem)

Not yet.  Need...more...data :)  If you have any more disk or controller
console messages those would be helpful. 

Good luck..

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major
Spam routed to /dev/null by Procmail    | Death to Cyberpromo