Created attachment 319615 [details] dmesg Description of problem: The following failure showed during a PPC64 machine boot, NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 2, 262144 bytes) TCP established hash table entries: 131072 (order: 5, 2097152 bytes) TCP bind hash table entries: 65536 (order: 4, 1048576 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered vio_bus_init: processing c0000000f7ffba28 vio_bus_init: processing c0000000f7ffbbe0 vio_bus_init: processing c0000000f7ffbdb8 vio_bus_init: processing c0000000f7ffbef0 vio_bus_init: processing c0000000f7ffc048 vio_bus_init: processing c0000000f7ffc1a0 vio_bus_init: processing c0000000f7ffc438 kobject_add failed for 4003 with -EEXIST, don't try to register things with the same name in the same directory. Call Trace: [C00000000FF1FBA0] [C000000000010378] .show_stack+0x68/0x1b0 (unreliable) [C00000000FF1FC40] [C0000000001B6F90] .kobject_add+0x1a4/0x1fc [C00000000FF1FCE0] [C0000000002819A4] .device_add+0x88/0x3b0 [C00000000FF1FD90] [C000000000022020] .vio_register_device_node+0x1dc/0x238 [C00000000FF1FE40] [C00000000046A110] .vio_bus_init+0x98/0xc4 [C00000000FF1FEC0] [C000000000460518] .init+0x250/0x388 [C00000000FF1FF90] [C000000000026FFC] .kernel_thread+0x4c/0x68 vio_register_device_node: failed to register device 4003 IBM eBus Device Driver scan-log-dump not implemented on this system RTAS daemon started RTAS: event: 5333, Type: Dump Notification Event, Severity: 2 audit: initializing netlink socket (disabled) audit(1223349908.165:1): initialized Total HugeTLB memory allocated, 0 Version-Release number of selected component (if applicable): kernel-2.6.18-92.el5 kernel-2.6.18-118.el5 How reproducible: always Steps to Reproduce: 1. boot ibm-js21-01.lab.bos.redhat.com
Cai, does this still happened on
Updating PM score.
Yes, I have still seen it with -120.el5 kernel, http://rhts.redhat.com/cgi-bin/rhts/test_log.cgi?id=4818818 I am trying the -128.el5 now, and will update once done.
The machine is available again. I'll reserve it, and test it as soon as possible.
Someone put an access key on this machine. I'll need to ask system admins to access it.
I'll close this one out, since the machine is still unavailable, and I have not seen it on any other machine so far.