From owner-freebsd-ppc  Mon Aug  5  6:50:27 2002
Delivered-To: freebsd-ppc@freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A649037B400
	for <freebsd-ppc@FreeBSD.ORG>; Mon,  5 Aug 2002 06:50:22 -0700 (PDT)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D4A5243E72
	for <freebsd-ppc@FreeBSD.ORG>; Mon,  5 Aug 2002 06:50:21 -0700 (PDT)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA00015;
	Mon, 5 Aug 2002 09:50:21 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g75DnpQ25572;
	Mon, 5 Aug 2002 09:49:51 -0400 (EDT)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15694.33407.146642.70257@grasshopper.cs.duke.edu>
Date: Mon, 5 Aug 2002 09:49:50 -0400 (EDT)
To: Peter Grehan <peterg@ptree32.com.au>
Cc: freebsd-ppc@FreeBSD.ORG
Subject: Re: Single-user
In-Reply-To: <3D4DAE9C.FA1B05C9@ptree32.com.au>
References: <3D4CF994.7478E7D0@ptree32.com.au>
	<20020804150712.GA81125@electricjellyfish.net>
	<3D4DAE9C.FA1B05C9@ptree32.com.au>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Sender: owner-freebsd-ppc@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-ppc.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-ppc>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-ppc>
X-Loop: FreeBSD.ORG


Peter Grehan writes:
 > Hi Garrett,
 > 
 > > well, that was the shortest uptime i can recall ;-)
 > 
 >  Yep, that's not good.
 > 
 > > tried the iso on my ibook, and got the following results:
 > 
 >  The fact that there's different types of failure, and the alignment
 > exception, point the finger at a timing and/or cache-related problem :-(
 >  

Speaking of timing related problems, I'm seeing something really odd.
If I attempt to remount root read/write, the kernel complains:
   udp: Netconfig database has invalid format

Thinking that's odd, I cat /etc/netconfig & I see that it has a large
number of (what I assume are) nulls at the front of it:

%cat /etc/netconfig 
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@st of:
#
#       <network_id> <semantics> <flags> <protofamily> <protoname> \
#               <device> <nametoaddr_libs>

Note that what I see on the console makes it look like the file
starts with the string "st of:", I only see the nulls when looking
at the conserver log files.

This looks really odd to me .. I'm used to seeing races where you get
entire pages of nulls, not just 239 of them.  Could this be a cache
related problem?   Do you see this behaviour on your test machine?

This is probably unrelated, but the machine will lock solid under
heavy io (dd'ing 100MB file over NFS to /dev/null).

I can also panic it by doing 'sysctl -a' on the console:

<..>
  hw.pagesize: 4096
  hw.machine_arch: powerpc
  hw.ata.ata_dma: 1
  hw.ata.wc: 1
  hw.ata.tags: 0
  hw.ata.atapi_dma: 0
  hw.pci.enable_io_modes: 1
  panic: kmem



Drew







To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ppc" in the body of the message