CBI event on CPU0

I am running Solaris 8 on a Ultra Enterprise 450. I found some error messages in the messages file that I don't understand.

Does anyone have any idea what this means?

Jul 30 12:27:08 chicagokent SUNW,UltraSPARC-II: [ID 695070 kern.info] NOTICE: [AFT2] errID 0x0005eb01.e43b04e5 CBI event on CPU0

Jul 30 12:27:08 chicagokent SUNW,UltraSPARC-II: [ID 358435 kern.info] [AFT2] errID 0x0005eb01.e43b04e5 PA=0x00000000.00eb4700

Jul 30 12:27:08 chicagokentE$tag 0x00000000.0e40001d E$State: Shared E$parity 0x07

Jul 30 12:27:08 chicagokent SUNW,UltraSPARC-II: [ID 359263 kern.info] [AFT2] E$Data (0x00): 0x00000000.00000000

Jul 30 12:27:08 chicagokent SUNW,UltraSPARC-II: [ID 989652 kern.info] [AFT2] E$Data (0x08): 0x00000000.00000000 *Bad* PSYND=0x0002

Jul 30 12:27:08 chicagokent SUNW,UltraSPARC-II: [ID 359263 kern.info] [AFT2] E$Data (0x10): 0x00000000.00000000

Jul 30 12:27:08 chicagokent SUNW,UltraSPARC-II: [ID 989652 kern.info] [AFT2] E$Data (0x18): 0x00000000.00000000 *Bad* PSYND=0x0002

Jul 30 12:27:08 chicagokent SUNW,UltraSPARC-II: [ID 359263 kern.info] [AFT2] E$Data (0x20): 0x00000000.00000000

Jul 30 12:27:08 chicagokent SUNW,UltraSPARC-II: [ID 989652 kern.info] [AFT2] E$Data (0x28): 0x00000000.00000000 *Bad* PSYND=0x0002

Jul 30 12:27:08 chicagokent SUNW,UltraSPARC-II: [ID 359263 kern.info] [AFT2] E$Data (0x30): 0x00000000.00000000

Jul 30 12:27:08 chicagokent SUNW,UltraSPARC-II: [ID 989652 kern.info] [AFT2] E$Data (0x38): 0x00000000.00000400 *Bad* PSYND=0x0002

Jul 30 12:27:18 chicagokent SUNW,UltraSPARC-II: [ID 928670 kern.info] NOTICE: [AFT2] errID 0x0005eb04.38de4db6 CBI event on CPU1

Jul 30 12:27:18 chicagokent SUNW,UltraSPARC-II: [ID 651112 kern.info] [AFT2] errID 0x0005eb04.38de4db6 PA=0x00000000.00eb4700

Jul 30 12:27:18 chicagokentE$tag 0x00000000.0e40001d E$State: Shared E$parity 0x07

Jul 30 12:27:18 chicagokent SUNW,UltraSPARC-II: [ID 359263 kern.info] [AFT2] E$Data (0x00): 0x00000000.00000000

Jul 30 12:27:18 chicagokent SUNW,UltraSPARC-II: [ID 359263 kern.info] [AFT2] E$Data (0x08): 0x00000000.00000000

Jul 30 12:27:18 chicagokent SUNW,UltraSPARC-II: [ID 359263 kern.info] [AFT2] E$Data (0x10): 0x00000000.00000000

Jul 30 12:27:18 chicagokent SUNW,UltraSPARC-II: [ID 359263 kern.info] [AFT2] E$Data (0x18): 0x00000000.00000000

Jul 30 12:27:18 chicagokent SUNW,UltraSPARC-II: [ID 359263 kern.info] [AFT2] E$Data (0x20): 0x00000000.00000000

Jul 30 12:27:18 chicagokent SUNW,UltraSPARC-II: [ID 359263 kern.info] [AFT2] E$Data (0x28): 0x00000000.00000000

Jul 30 12:27:18 chicagokent SUNW,UltraSPARC-II: [ID 359263 kern.info] [AFT2] E$Data (0x30): 0x00000000.00000000

Jul 30 12:27:18 chicagokent SUNW,UltraSPARC-II: [ID 989652 kern.info] [AFT2] E$Data (0x38): 0x00000000.00000400 *Bad* PSYND=0x00ff

Thanks

Larry

[2900 byte] By [sgtrock] at [2007-11-26 9:09:07]
# 1
Might want to look at these: http://www.sunmanagers.org/pipermail/summaries/2002-November/002767.htmland http://forum.sun.com/jive/thread.jspa?threadID=97092
mikep_vt90 at 2007-7-6 23:26:21 > top of Java-index,General,Talk to the Sysop...
# 2

Both of those links that Mike gave have good information.

Please take note of the dates inside the first link, however.

They're discussing information from 2002.

If you have a questionable or failing cpu module, it would have shown up long ago.

I suspect the second link will be more pertinent to your current issue.

Your MESSAGES file called out multiple cpu modules,

on essentially the same timestamp, not just one.

CBI's were all over the place, thus it's probably going to be found

to be a DIMM and/or a down-rev kernel patch that's been causing this.

Spectrum Infodoc 70361 covers the subject, as I mentioned in that May '06 thread.

rukbat at 2007-7-6 23:26:21 > top of Java-index,General,Talk to the Sysop...
# 3
Thanks for the info.I will check this out.
sgtrock at 2007-7-6 23:26:21 > top of Java-index,General,Talk to the Sysop...