[cobalt-users] named crash/kernel oops on RaQ3s with OS update 3.0

[Chris Adams <cmadams@xxxxxxxxxx>]

I have 24 RaQ3s here that have all been running okay.  I upgraded them
with the OS 3.0 update on Monday, which went pretty smooth (except for
the slowness and duplicate entries in virtusertable that I mentioned
here).

However, so far today I've had 3 of them have the kernel oopsing,
killing named (the system has to be rebooted to get named working
again).  This _can't_ be a coincidence.

Is anyone else seeing anything like this?
-- 
Chris Adams <cmadams@xxxxxxxxxx>
Systems and Network Administrator - HiWAAY Information Services
I don't speak for anybody but myself - that's enough trouble.