Return-Path: <alex_c@MIT.EDU>
Received: from grand-central-station.mit.edu by po11.mit.edu (8.9.2/4.7) id PAA23089; Wed, 12 Dec 2001 15:11:18 -0500 (EST)
Received: from manawatu-mail-centre.mit.edu (MANAWATU-MAIL-CENTRE.MIT.EDU [18.7.21.85])
	by grand-central-station.mit.edu (8.9.2/8.9.2) with ESMTP id PAA05171;
	Wed, 12 Dec 2001 15:11:12 -0500 (EST)
Received: from QUICHE-LORRAINE.MIT.EDU (QUICHE-LORRAINE.MIT.EDU [18.187.1.71])
	by manawatu-mail-centre.mit.edu (8.9.2/8.9.2) with ESMTP id PAA01615;
	Wed, 12 Dec 2001 15:11:11 -0500 (EST)
Received: (from alex_c@localhost) by QUICHE-LORRAINE.MIT.EDU (8.9.3)
	id PAA15055; Wed, 12 Dec 2001 15:11:12 -0500
Date: Wed, 12 Dec 2001 15:11:12 -0500
Message-Id: <200112122011.PAA15055@QUICHE-LORRAINE.MIT.EDU>
From: Alex Coventry <alex_c@MIT.EDU>
To: Sipb-Office <sipb-office@mit.edu>
Cc: mycroft@mit.edu
Subject: chomp's woes.


hi, everyone.  there's probably a chomp-maintainers list that this
should go to or something.  someone should let me know. 

chomp doesn't boot reliably.  i extricated it from the rat's nest around
the sound system and connected it into the keyboard, network cable and
monitor that granola usually uses.  with that set up, i could get it to
boot.  however, when i hooked it back up to the rat's nest, it still
failed to boot (most of the time).  dbj looked at a few tcpdumps of the
traffic it generates with zsr.  when chomp is power-cycled, a large
amount of data, presumably a kernel, is transmitted from zsr to chomp,
but chomp usually hangs as soon as this transmission stops.  a couple of
times, chomp managed to get through the boot process, but we couldn't
figure out why -- one time it happened just after i'd pulled the
earphone jack from chomp, another time just after i'd switched the drop
it was plugged into to the drop granola usually uses.  we couldn't
reproduce either of these successes.

Alex.

