On Fri, Feb 07, 2003 at 02:44:38PM +1030, Brett Lymn wrote:

> Hmmm ok - it may be clutching at straws but there appears to be a MI
> problem that may be related.  Perhaps a cvs update?

Synchronizing against the repository as of three hours ago didn't change
anything ...

... turning on DEBUG and DIAGNOSTIC revealed something interesting, however:

timeout delayed -3
Process (pid 1) got signal 11
Process (pid 1) got signal 11
Process (pid 1) got signal 11
Process (pid 1) got signal 11
Process (pid 1) got ignal 11
xcall(cpu0,0xf0007938): couldn't ping cpus:timeout delayed -1
timeout delayed -1
timeout delayed -2
timeout delayed -2
timeout delayed -2
Process (pid 1) got signal 11

... which doesn't look terribly MI to me :)

This has to be something recent -- a kernel dated mid-January works okay
(for small values of okay -- it at least boots).

-- Chris
	GPG key FEB9DE7F (91AF 4534 4529 4BCC 31A5  938E 023E EEFB FEB9 DE7F)