See the attached panic.tar.gz which contains system info, messages. panic stack trace and these notes Kernel panic with RHEL 3 Update 1 Beta (2.4.21-6.EL) on zx8000. \"IoGet:Connection timed out\" is seen frequently on zx2000 and zx6000 as well with RHEL 3, RHEL2.1 Update 3 and RHEL3 Update 1. The test started at Dec 22 ~2:37. This panic occurred at approx Dec 25 ~noon. Included are lsmod, lspci -vv, /proc/meminfo, /proc/cpuinfo, messages and log.cfg144 (which shows the panic information). Notes that the panic information is not showing up in /var/log/messages; our test tool is getting this from syslog. The lan configuration contains eth0 tg3 @ 192.1.1.144 eth1 e1000 @ 10.10.20.144 eth2 e100 @ 192.1.2.144 eth0 is a direct connect to machine 146 (eth0 tg3 @ 192.1.1.146) eth2 is a direct connect to machine 146 (eth1 e1000 @ 192.1.2.146) ---------- Action by: kim.jensen Issue Registered ---------- Action by: kim.jensen Attached file (panic.tar.gz) contains additional information Status set to: Waiting on Tech ---------- Action by: ltroan Kim, there's no attachment.... kim.jensen assigned to issue for HP-IPF. Category set to: Kernel Status set to: Waiting on Client ---------- Action by: kim.jensen Attaching panic.tar.gz again. I am seeing many machines reboot with a few hours of running test; no information in /var/log/messages on what the cause was. This shows up as a "rlogin: recv: Connection timed out Connection closed" - which I believe is the result and not the cause of the connection closing when the system dies. This is the first time I saw the panic along with the behaviour. This issue is limiting the amount of testing that can be completed. File uploaded: panic.tar.gz ISSUE TRACKER 31131 OPENED AS SEV 2.
Created attachment 96966 [details] panic.tar.gz
EIP is at pfm_context_exit + 0x11, which is in ia64-specific perfmon code. Reassigning to Jason, our ia64 arch maintainer.
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.