From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <943c93affdb2ae75e398c7d0428638c0@plan9.bell-labs.com>
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] aha1542 -> kernel panic
In-Reply-To: <001e01c2b0eb$f756a8d0$78b5fc3e@swlocal>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Tue, 31 Dec 2002 11:58:55 -0500
Topicbox-Message-UUID: 3a4a1fce-eacb-11e9-9e20-41e7f4b1d025

someone has changed the message you get in the current kernel to

		panic("fault but up is zero; pc 0x%8.8lux addr 0x%8.8lux\n", ureg->pc, addr);

it's in trap.c/fault386 and means you have taken a page fault either in an
interrupt handler or during initialisation before the sceduler is started.

use the acid on the kernel binary with the addr given in the panic to
find where the fault happened and we can maybe track it down.