On Thursday 29 January 2009 06:39:22 Artem Kuchin wrote: > I am sure this is not the case because the new raid was simply recreated > manually using 3ware bios and > then freebsd installed and then old data copied from backup.
Ah, I got that wrong from your mail. > BTW, here are the interrupts: > interrupt total rate > irq14: ata0 47 0 > irq15: ata1 4818547 3 > irq28: em0 137807398 105 > irq72: twe0 66970618 51 > cpu0: timer 2606991398 2000 > cpu1: timer 2596549865 1992 > cpu2: timer 2606991199 2000 > cpu3: timer 2596549863 1992 > Total 10616678935 8145 That should be normal: cpu0: timer 961443545 1999 irq256: em0 660532 1 cpu1: timer 961433589 1999 $ sysctl kern.clockrate kern.clockrate: { hz = 1000, tick = 1000, profhz = 2000, stathz = 133 } Not much has gone in 6-STABLE since 6.4 release. I would sync binaries in one jail that is offensive at the moment and restart it. See if the problem goes away for that jail. Resolver libraries and openssl have had an update for security patches, but that doesn't explain the kernel having a hard time. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"