Subject: Re: Problems after upgarding to 32M
To: None <thieleke@lust.isca.uiowa.edu>
From: Mike Long <mike.long@analog.com>
List: port-i386
Date: 05/16/1996 11:05:55
>From: Jeff Thieleke <thieleke@lust.isca.uiowa.edu>
>Date: Thu, 16 May 1996 00:51:53 -0500 (CDT)

>I really have no idea what is wrong here.  The only things unusual in the
>boot messages are a few extraneous devices.  For example, 1.1 & 1.1B say
>that I have a sea0 and ie0 devices.  1.1B additionally says I have ie1.  

>sea0: board type unknown at address 0xf82a3000
>mcd0: timeout in getresult
>mcd0: timeout in getresult
>mcd0: timeout in getresult
>ie0: unknown AT&T board type code 15
>*** NetBSD 1.1B also finds an ie1 ***

These devices are not really found; the messages you see are spewage
from their respective probe routines.  I have submitted a PR
(port-i386/2108) that shuts them up.  Probe routines should print
nothing, in order to avoid confusion like you're experiencing.  The
only exception would be if you define a driver-specific *DEBUG
option (e.g. IEDEBUG).

Sorry I can't help you with your kernel-panic problem; but at least
now you know that these messages aren't part of it.  To verify, try
booting a kernel with all sea?, mcd?, and ie? devices removed.
-- 
Mike Long <mike.long@analog.com>     <URL:http://www.shore.net/~mikel>
VLSI Design Engineer         finger mikel@shore.net for PGP public key
Analog Devices, CPD Division          CCBF225E7D3F7ECB2C8F7ABB15D9BE7B
Norwood, MA 02062 USA       (eq (opinion 'ADI) (opinion 'mike)) -> nil