> I have a UDB with a 2.1.78 kernel. Occasionnaly, syslogd becomes wild
> and dumps countless messages "Exception at ..." that bring the box to
> its knees.
>
> Today I had this while trying a newly compiled portmap, and this was by
> rlogin. The system seemed to crash, so I unlogued from my Sun station
> and came to see my UDB... and it was ok. It seems that my unlogin
> killed the portmap that was causing the messages (it was in debug mode
> and so lost its terminal when I unlogued) and the messages stopped.
>
> So... this time I _have_ the messages. There are two of them, alterning :
>
> Jan 12 19:40:22 orion kernel: portmap: Exception at [<fffffc00003b15bc>] (fffffc00003b15c4)
> Jan 12 19:40:22 orion kernel: portmap: Exception at
> [<fffffc00003f4e80>] (fffffc00003f4efc)
Just kill that message from kernel, if you want to cure symptoms. If
you want to cure reason, look at portmap, its probably buggy. If it
does 'wrong thing' in loop, it will do this. PLEASE INVESTIGATE
portmap, as it may be bug in kernel.
-- I'm really pavel@atrey.karlin.mff.cuni.cz. Pavel Look at http://atrey.karlin.mff.cuni.cz/~pavel/ ;-).