On Mon, Jan 08, 2001 at 01:28:40PM -0800, Wolfgang Rupprecht wrote:
> 
> I just rebuilt the world from this morning's anoncvs, compiled up a
> fresh kernel (in an empty directory) and tried to reboot.  It would
> hang just after the line:
> 
>         biomask XXXX netmask XXXX ttymask XXXX 
> 
> On a normal boot, this line would occur just before the IPsec line.
>         "IPsec: Initialized Security Association Processing."
> 
> I could break into ddb and do a trace.
> 
>         Xspllower(...) + 0xe
>         configure(...) + 0x5a
> 
> FYI this problem is only seen on my Asus a7v, Athlon 1.1Ghz.  The same
> kernel boots just fine on the various Intel-based boards.  Also, a
> kernel built from Dec 29 sources and the same config file works fine
> on this board (and thats what I rev-ed back to).  Does any of this
> ring a bell?  Could this be more of the bogus "Promise ultra100"
> interrupt problem biting me?

No, I don't think so. The ddb trace would be different, you would get kernel
messages, and I'm not even sure you could drop into ddb if the kernel was
stuck in an interrupt loop.

--
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
--