免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 2656 | 回复: 7
打印 上一主题 下一主题

L3000小型机问题 [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2009-10-10 09:24 |只看该作者 |倒序浏览
各位大侠,小弟这有个l3000的小型机不知道怎么就down机了,现在也查不出来问题,还望有过这个问题经历的大侠予以指导!相关报错如下:
GSP> sl



SL


Select Chassis Code Buffer to be displayed:

Incoming, Activity, Error, Current boot or Last boot? (I/A/E/C/L) e

e


Set up filter options on this buffer? (Y/[N])



The first entry is the most recent Chassis Code

Type + CR and CR to go up (back in time),

Type - CR and CR to go down (forward in time),

Type Q/q CR to quit.



Log Entry #   0 :

SYSTEM NAME: uninitialized

DATE: 10/01/2009 TIME: 23:53:39

ALERT LEVEL: 15 = Fatal hardware or configuration problem prevents operation


SOURCE: 8 = I/O

SOURCE DETAIL: 6 = disk   SOURCE ID: 0

PROBLEM DETAIL: 3 = functional failure


CALLER ACTIVITY: 1 = test   STATUS: 0

CALLER SUBACTIVITY: 48 = implementation dependent

REPORTING ENTITY TYPE: 0 = system firmware   REPORTING ENTITY ID: 00


0x000000F386001480 00000000 00000000 type  0 = Data Field Unused

0x580008F386001480 00006D09 01173527 type 11 = Timestamp 10/01/2009 23:53:39

Type CR for next entry, Q CR to quit.






Log Entry #   1 :

SYSTEM NAME: uninitialized

DATE: 10/01/2009 TIME: 23:53:39

ALERT LEVEL: 6 = Boot possible, pending failure - action required


SOURCE: 8 = I/O

SOURCE DETAIL: 6 = disk   SOURCE ID: 0

PROBLEM DETAIL: 0 = no problem detail


CALLER ACTIVITY: 2 = config   STATUS: 0

CALLER SUBACTIVITY: 35 = implementation dependent

REPORTING ENTITY TYPE: 0 = system firmware   REPORTING ENTITY ID: 00


0x0000006086002350 00000000 00000000 type  0 = Data Field Unused

0x5800086086002350 00006D09 01173527 type 11 = Timestamp 10/01/2009 23:53:39

Type CR for next entry, - CR for previous entry, Q CR to quit.




Log Entry #   2 :

SYSTEM NAME: uninitialized

DATE: 10/01/2009 TIME: 23:53:37

ALERT LEVEL: 6 = Boot possible, pending failure - action required


SOURCE: 8 = I/O

SOURCE DETAIL: 6 = disk   SOURCE ID: 0

PROBLEM DETAIL: 0 = no problem detail


CALLER ACTIVITY: 2 = config   STATUS: 0

CALLER SUBACTIVITY: 37 = implementation dependent

REPORTING ENTITY TYPE: 0 = system firmware   REPORTING ENTITY ID: 00


0x0000006086002370 00000000 00000000 type  0 = Data Field Unused

0x5800086086002370 00006D09 01173525 type 11 = Timestamp 10/01/2009 23:53:37

Type CR for next entry, - CR for previous entry, Q CR to quit.




Log Entry #   3 :

SYSTEM NAME: uninitialized

DATE: 10/01/2009 TIME: 23:48:29

ALERT LEVEL: 3 = System blocked waiting for operator input


SOURCE: 1 = processor

SOURCE DETAIL: 1 = processor general   SOURCE ID: 0

PROBLEM DETAIL: 0 = no problem detail


CALLER ACTIVITY: E = system warning   STATUS: F

CALLER SUBACTIVITY: FF = implementation dependent

REPORTING ENTITY TYPE: E = HP-UX   REPORTING ENTITY ID: 00


0xF8E000301100EFFF 00000000 0000EFFF type 31 = legacy PA HEX chassis-code

0x58E008301100EFFF 00006D09 0117301D type 11 = Timestamp 10/01/2009 23:48:29

Type CR for next entry, - CR for previous entry, Q CR to quit.




Log Entry #   4 :

SYSTEM NAME: uninitialized

DATE: 10/01/2009 TIME: 23:48:17

ALERT LEVEL: 3 = System blocked waiting for operator input


SOURCE: 1 = processor

SOURCE DETAIL: 1 = processor general   SOURCE ID: 0

PROBLEM DETAIL: 0 = no problem detail


CALLER ACTIVITY: E = system warning   STATUS: 0

CALLER SUBACTIVITY: 00 = implementation dependent

REPORTING ENTITY TYPE: E = HP-UX   REPORTING ENTITY ID: 00


0xF8E000301100E000 00000000 0000E000 type 31 = legacy PA HEX chassis-code

0x58E008301100E000 00006D09 01173011 type 11 = Timestamp 10/01/2009 23:48:17

Type CR for next entry, - CR for previous entry, Q CR to quit.




Log Entry #   5 :

SYSTEM NAME: uninitialized

DATE: 10/01/2009 TIME: 23:48:17

ALERT LEVEL: 13 = System hang detected via timer popping


SOURCE: 1 = processor

SOURCE DETAIL: 1 = processor general   SOURCE ID: 0

PROBLEM DETAIL: 4 = timeout


CALLER ACTIVITY: F = display_activity() update   STATUS: 0

CALLER SUBACTIVITY: 00 = implementation dependent

REPORTING ENTITY TYPE: E = HP-UX   REPORTING ENTITY ID: 00


0x78E000D41100F000 00000003 00000003 type 15 = Activity Level/Timeout

0x58E008D41100F000 00006D09 01173011 type 11 = Timestamp 10/01/2009 23:48:17

Type CR for next entry, - CR for previous entry, Q CR to quit.




Log Entry #   6 :

SYSTEM NAME: uninitialized

DATE: 10/01/2009 TIME: 23:48:22

ALERT LEVEL: 2 = Non-Urgent operator attention required


SOURCE: 0 = unknown, no source stated

SOURCE DETAIL: 0 = unknown, no source stated   SOURCE ID: FF

PROBLEM DETAIL: 0 = no problem detail


CALLER ACTIVITY: 6 = machine check   STATUS: 2

CALLER SUBACTIVITY: 53 = implementation dependent

REPORTING ENTITY TYPE: 0 = system firmware   REPORTING ENTITY ID: 02


0x0000202000FF6532 00000000 00000000 type  0 = Data Field Unused

0x5800282000FF6532 00006D09 01173016 type 11 = Timestamp 10/01/2009 23:48:22

Type CR for next entry, - CR for previous entry, Q CR to quit.
小弟也用cstm检测了memory,disk,cpu都没有报错信息。

论坛徽章:
0
2 [报告]
发表于 2009-10-10 09:33 |只看该作者
现在还能进系统
能到BCH么?

论坛徽章:
0
3 [报告]
发表于 2009-10-10 09:40 |只看该作者
根盘坏了吧!

论坛徽章:
0
4 [报告]
发表于 2009-10-10 21:11 |只看该作者
boot出问题,可能有盘坏了.

进系统仔细看看,最好把crash分析下.

论坛徽章:
0
5 [报告]
发表于 2009-10-12 10:29 |只看该作者

回复 #2 leelangco 的帖子

可以进系统!但是最近又异常down机了!

论坛徽章:
0
6 [报告]
发表于 2009-10-12 10:31 |只看该作者

回复 #3 mmm9843527 的帖子

可是用cstm测试跟盘的时候没有报错,而且一切都正常呀!
在10秒中断时候,也能找到路径,也可以启动的!

论坛徽章:
0
7 [报告]
发表于 2009-10-12 10:32 |只看该作者

回复 #4 hbh231 的帖子

系统已经都不产生core文件了!
每次异常重启日志都清完了!没有什么报错

论坛徽章:
0
8 [报告]
发表于 2009-10-12 11:02 |只看该作者
用q4分析一下
CPU坏的可能性比较大

进到BCH,然后检查一下 看有没有CPU被deconfig
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP