From owner-freebsd-hackers  Sun Jun  4 16:23:19 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id QAA17635
          for hackers-outgoing; Sun, 4 Jun 1995 16:23:19 -0700
Received: from mramirez.sy.yale.edu (mramirez.sy.yale.edu [130.132.57.207])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA17627
          for <freebsd-hackers@freebsd.org>; Sun, 4 Jun 1995 16:23:15 -0700
Received: (from mrami@localhost) by mramirez.sy.yale.edu (8.6.11/8.6.9) id TAA01141; Sun, 4 Jun 1995 19:11:09 -0400
Date: Sun, 4 Jun 1995 19:11:08 -0400 (EDT)
From: Marc Ramirez <mrami@mramirez.sy.yale.edu>
Reply-To: mrami@minerva.cis.yale.edu
To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
cc: freebsd-hackers@freebsd.org, joerg_wunsch@uriah.heep.sax.de
Subject: Re: kernel page fault while doing tar to /dev/rft0
In-Reply-To: <199506042159.OAA21672@gndrsh.aac.dev.com>
Message-ID: <Pine.BSF.3.91.950604190853.907A-100000@mramirez.sy.yale.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: hackers-owner@freebsd.org
Precedence: bulk

On Sun, 4 Jun 1995, Rodney W. Grimes wrote:

> > 
> > On Sun, 4 Jun 1995, J Wunsch wrote:
> > 
> > > CAN SOMEBODY WITH A WORKING FLOPPY TAPE PLEASE CHECK IF THE SUGGESTED
> > > FIX (move 5 lines below the #ifdef block) WOULD WORK?  THIS MUST GO
> > > INTO 2.0.5!!!
> > 
> > $ tar tvf /dev/rft0
> > fdc0: output ready timeout
> > fdc0: input ready timeout
> > fdc0: input ready timeout
> > tar: read error on /dev/rft0: Device not configured
> > fdc0: output ready timeout
> > fdc0: input ready timeout
> > fdc0: input ready timeout
> > $ 
> > 
> > The fdc0: messages are kernel printf's.
> 
> I can visually see that this patch would be wrong, first off fdc would
> be uninitialzed inside the #if block, and would be referenced.  I don't
> know why you didn't panic, but  you should have!!!  Just got lucky
> with what ever trash was on the stack :-).

Just noticed something: 'ft|tar tvf -' still works, although it is bracketed 
with the fdc0 error messages as above.  This is 950412-SNAP, by the way.

> Try again Joerg, only look very very carefully at the code!!!
> 
> 
> -- 
> Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
> Accurate Automation Company                   Custom computers for FreeBSD
>