Thanks for all reply me, but I didn't resolve the problem.
The most answers pointed to hardware problem.
I run sunvts, to test only the memory and after few seconds it crashed
the machine and did the same "panic[cpu1]" message. After the reboot
ifself, I run the same test using sunvts, and it rebooted again.
Well, I thought that the problem is really the memory, but this morning
I run the Power-On Self-Test (POST) and Openboot Diagnostics (OBDiag),
and no error were displayed.
> We have a E450 running Solaris 7 that on 3 and 4 December about 00:50
> was rebooted itself.
> Every day at 23:58, we have a cron that send a output of
> "/usr/platform/sun4u/sbin/prtdiag -v":
> 03/Dec | 04/Dec
> ambient temperature: 26 C | 27 C
> CPU: 47 C | 47 C
> According the E450 Server Owner's Guide (page 46), if the ambient
> temperature reaches 50 degrees C or CPU module reaches 80 degrees C, the
> system automatically shutdown. So it can't be a problem generated by
> temperature, and besides the system come up again.
> Today at 12:04 the machine rebooted ifself again, the ambient
> temperature was 22 degrees C, and the CPU 41 degrees C. But at this
> time, the /var/adm/messages logged the following:
> Dec 7 12:04:09 my_host unix: panic[cpu1]/thread=2a100047d60:
> Dec 7 12:04:09 my_host unix: Async data error at tl1: AFAR
> 0x00000000.3f0000b0 AFSR 0x001f0625.80300000
> Dec 7 12:04:09 my_host unix:
> Dec 7 12:04:09 my_host unix: syncing file systems...
> Dec 7 12:04:29 my_host unix: panic[cpu1]/thread=2a100063d60:
> Dec 7 12:04:29 my_host unix: panic sync timeout
> Dec 7 12:04:29 my_host unix:
> Dec 7 12:04:30 my_host unix: dumping to /dev/dsk/c0t0d0s1, offset 65536
> Dec 7 12:06:27 my_host unix: 100% done: 14621 pages dumped, compression
> ratio 3.35,
> Dec 7 12:06:27 my_host unix: dump succeeded
> I looked for the "Sun Managers Summaries Archives", and I founded
> something like our problem. The answer was some type of failure in the
> kernel code. The solution was install the Sun's recommended patches
> including kernel patch.
> We had installed the latest recommended patch and the latest "Kernel
> update patch" (106541-08) for Solaris 7, before this problem happened.
> What more I can do?
> H. S. Yann
> System & Network Administrator
-- H. S. Yann email@example.com System & Network Administrator VeritelNet
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:34 CDT