Hi SunManagers !
First of all many thanx to the next ppl:
Chris Marble
Rodney Ramdas
Bismark Espinoza
Joel Lee
Francisco de la Torre
Wim Olivier
Casper Dik
Almost all ppl told me about old release and patchlevel
of my system (SunOS sun 5.4 Generic_101945-10 sun4m sparc).
There are so many bugs related to the deadlock condition.
The common recommendation is to patch the system to the
most recent patchlevel or to the next OS release.
So, I am going upgrade my system to the 2.5.1 release.
I am not sure if any similar bugs would pop up after
installing the new release. Do I need to patch a virgin
2.5.1 OS ?
Thanx all ppl who send me answers.
Mikhail V Zdorovenko
The original question:
>
> I've got the next problem. Today morning my SS20
> (SunOS sun 5.4 Generic_101945-10 sun4m sparc) has
> been rebooted because of panic condition. Here is
> diagnostic messages from /var/adm/messages:
>
> Jun 22 12:58:16 sun unix: panic: Deadlock condition detected: cycle in
> blocking chain. Thread: 0xfc7625a0
> Jun 22 12:58:16 sun unix: syncing file systems... [5] 3 [5] 3 [5] 3
> [5] 3 [5] 3 [5] 3 [5] 3 [5] 3 [5] 3 [5] 3 [5] 3 [5] 3 [5] 3 [5] 3
> [5] 3 [5] 3 [5] 3 [5] 3 [5] 3 [5] 3 done
> Jun 22 12:58:16 sun unix: 4796 static and sysmap kernel pages
> Jun 22 12:58:16 sun unix: 80 dynamic kernel data pages
> Jun 22 12:58:16 sun unix: 198 kernel-pageable pages
> Jun 22 12:58:16 sun unix: 0 seg
>
> After reboot one of filesystems was not mounted. The system
> told me that I have to run fcsk manually. So, I did it. I've
> successfully mount that filesystem after fcsk'ing.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:42 CDT