On Jun 13, 12:49pm, Simon Burge wrote:
} On a 3100, I get the following with a kernel I build this morning (the
} same kernel I'm using on mona, the 5k/240).  This it just copied from
} the screen, so hopefully there aren't any typos:
} 
} > configuring pm at afc00000 interrupt number 3
} > pm0 at mainbus0(1024x864x8) (console)configuring dc at bc000000 interrupt number 2
} > dc0 at mainbus0 (kn01: intr_establish hardcoded)
} > configuring lance at b8000000 interrupt number 1
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  Note that the lance device did not configure!

} > configuring sii at ba000000 interrupt number 0
} > sii0 at mainbus0 (kn01: intr_establish hardcoded)
} > configuring mc146818 at bd000000 interrupt number 16
} > clock0 at mainbus0
} > configuring dc at b5000000 interrupt number 4
} > configuring dc at b5200000 interrupt number 5
} > configuring  at 0 interrupt number 0
} 
} and hang.  Notice the double space and the 0's on the last line.  Just
} guessing it could be hanging trying to configure a "nothing"...

  There is a problem with configuring the LANCE device on the 3100 if you
are using NEWCONF or a similar config file.  In your case, the le0 device
did not configure and probably got an interrupt.  Since the lance did
not get connected, I think the interrupt will cause the 3100 to hang when
it enables interrupts after the device configuration.

  I think I've got a fix for this problem - I've just booted my 3100 with
the changes and it looks like it may be working.

Michael