Hide Forgot
=Comment: #0================================================= Lucio Jose Herculano Correia <luciojhc.com> - After installing RHEL6 Snap13 on standalone P6 HV4, I got these error messages during first boot. It seems to happen on every boot. Starting udev: ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. [ OK ] Contact Information = Lucio Correia <luciojhc.com> ---uname output--- Linux devhv4e-woodward-lp1.austin.ibm.com 2.6.32-70.el6.ppc64 #1 SMP Wed Aug 25 11:09:30 EDT 2010 ppc64 ppc64 ppc64 GNU/Linux Machine Type = CHRP IBM,8203-E4A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Just install Snap13. ---Kernel - Filesystem Component Data--- Stack trace output: Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: Badness at fs/sysfs/dir.c:491 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: NIP: c0000000002402ec LR: c0000000002402e8 CTR: 0000000000000001 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: REGS: c0000000c59ef230 TRAP: 0700 Tainted: G W ---------------- (2.6.32-70.el6.ppc64) Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: MSR: 8000000000029032 <EE,ME,CE,IR,DR> CR: 28248444 XER: 20000008 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: TASK = c0000000c9a66190[758] 'modprobe' THREAD: c0000000c59ec000 CPU: 0 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: GPR00: c0000000002402e8 c0000000c59ef4b0 c000000000e8cd80 0000000000000082 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: GPR04: 0000000000000000 ffffffffffffffff 0000000000000003 0000000000080000 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: GPR08: 000000000001064f c000000000df0990 00000000000105d5 000000000000000a Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: GPR12: 0000000028248442 c000000000f62500 00000fffabe000a0 0000000000000000 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: GPR16: 000001001f3e0130 c0000000cdcebb80 0000000000000000 0000000000000000 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: GPR20: fffffffffffff000 c0000000cdcebc2c 0000000000000010 c0000000cd51d1f0 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: GPR24: c00000000024026c 0000000000001000 c0000000cf040180 c0000000c9b77b00 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: GPR28: c0000000c59ef5d0 c0000000c6babc50 c000000000e2b370 ffffffffffffffef Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: NIP [c0000000002402ec] .sysfs_add_one+0xfc/0x170 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: LR [c0000000002402e8] .sysfs_add_one+0xf8/0x170 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: Call Trace: Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59ef4b0] [c0000000002402e8] .sysfs_add_one+0xf8/0x170 (unreliable) Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59ef560] [c000000000240de8] .create_dir+0x68/0x130 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59ef620] [c000000000240ef8] .sysfs_create_dir+0x48/0x80 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59ef6b0] [c0000000002dcddc] .kobject_add_internal+0xdc/0x2e0 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59ef750] [c0000000002dd2a8] .kobject_add+0x48/0x90 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59ef7d0] [c000000000392064] .device_add+0xe4/0x6a0 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59ef8b0] [d0000000024807ec] .enclosure_component_register+0x10c/0x160 [enclosure] Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59ef970] [d000000002510bd4] .ses_enclosure_data_process+0x424/0x480 [ses] Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59efa60] [d0000000025111fc] .ses_intf_add+0x30c/0x650 [ses] Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59efb20] [c00000000039792c] .class_interface_register+0xdc/0x120 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59efbd0] [c0000000003bc744] .scsi_register_interface+0x24/0x40 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59efc50] [d000000002511680] .ses_init+0x28/0x4f8 [ses] Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59efce0] [c0000000000096ec] .do_one_initcall+0x5c/0x200 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59efd90] [c0000000000d65cc] .SyS_init_module+0x14c/0x2c0 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59efe30] [c00000000000852c] syscall_exit+0x0/0x40 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: Instruction dump: Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: 7f64db78 4bfffec1 e89e8038 4be0b595 60000000 e89d0018 4be0b589 60000000 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: 7c641b78 e87e8040 48342995 60000000 <0fe00000> 7f63db78 4bf5b4bd 60000000 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: Call Trace: Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59ef600] [c000000000012d84] .show_stack+0x74/0x1c0 (unreliable) Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59ef6b0] [c0000000002dce9c] .kobject_add_internal+0x19c/0x2e0 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59ef750] [c0000000002dd2a8] .kobject_add+0x48/0x90 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59ef7d0] [c000000000392064] .device_add+0xe4/0x6a0 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59ef8b0] [d0000000024807ec] .enclosure_component_register+0x10c/0x160 [enclosure] Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59ef970] [d000000002510bd4] .ses_enclosure_data_process+0x424/0x480 [ses] Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59efa60] [d0000000025111fc] .ses_intf_add+0x30c/0x650 [ses] Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59efb20] [c00000000039792c] .class_interface_register+0xdc/0x120 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59efbd0] [c0000000003bc744] .scsi_register_interface+0x24/0x40 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59efc50] [d000000002511680] .ses_init+0x28/0x4f8 [ses] Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59efce0] [c0000000000096ec] .do_one_initcall+0x5c/0x200 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59efd90] [c0000000000d65cc] .SyS_init_module+0x14c/0x2c0 Sep 4 08:05:43 devhv4e-woodward-lp1 kernel: [c0000000c59efe30] [c00000000000852c] syscall_exit+0x0/0x40 =Comment: #1================================================= Lucio Jose Herculano Correia <luciojhc.com> - sosreport =Comment: #2================================================= Lucio Jose Herculano Correia <luciojhc.com> - Same bug has been reported on Red Hat bugzilla for RHEL5.4: https://bugzilla.redhat.com/show_bug.cgi?id=505284 =Comment: #9================================================= Lucio Jose Herculano Correia <luciojhc.com> - dmesg output =Comment: #10================================================= Lucio Jose Herculano Correia <luciojhc.com> - Boot log =Comment: #13================================================= Lucio Jose Herculano Correia <luciojhc.com> - 1.Server architecture(s) (please list all effected) (x86/POWER6/Z/etc.): POWER6 2.Server type (9117-MMA/HS20/s390/etc.): CHRP IBM,8203-E4A 3.General component (desktop/kernel/base OS/dev tools/etc.): sysfs 4.Other components involved (ixgbe/java/emulex/etc.): 5.Does the server have the latest GA firmware? Yes 6.Has the problem been shown to occur on more than one system? No 7.Is a tested patch available? No If yes to the above, has it been approved upstream? 8.What is the latest official Red Hat build on which this bug has been seen? RHEL6 Snap13 =Comment: #16================================================= bugproxy bugproxy <bugproxy.com> - Issue Registered (Severity: 2) Status set to: Waiting on Tech Added Customer Reference: 66973 File uploaded: sosreport-LucioCorreia.66973-20100904141137-0928.tar.xz File uploaded: dmesg.out File uploaded: bootconsole.out =Comment: #17================================================= bugproxy bugproxy <bugproxy.com> - ------- Comment #11726923 from balkov at 2010/09/08 15:56:19 EDT ------- Is this causing a problem other than log spam? balkov assigned to issue for IBM-LTC. Status set to: Waiting on Client Ticket type changed from 'Problem' to 'Question' =Comment: #18================================================= Lucio Jose Herculano Correia <luciojhc.com> - On a first glance, just log spam. =Comment: #19================================================= bugproxy bugproxy <bugproxy.com> - Status set to: Waiting on Tech =Comment: #21================================================= MUNI P. BEERAKAM <> - Hello Redhat, Any updates? Thanks Muni =Comment: #22================================================= Anibal Cesar Aguiar De Carvalho <anibalca.ibm.com> - Hit this bug on RHEL6 RC1: Welcome to Red Hat Enterprise Linux Server Starting udev: ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. ------------[ cut here ]------------ Badness at fs/sysfs/dir.c:491 kobject_add_internal failed for with -EEXIST, don't try to register things with the same name in the same directory. [ OK ] =Comment: #23================================================= MUNI P. BEERAKAM <> - Hello Redhat, Please let us know when this issue(by which snapshot) could be resolved? Thanks Muni =Comment: #24================================================= bugproxy bugproxy <bugproxy.com> - ------- Comment #13402223 from balkov at 2010/12/08 14:07:27 EST ------- Is this still occurring on RHEL 6 GA? Status set to: Waiting on Client ======================================= The bug is hit on RHEL6.1-Alpha (on the standalone P6 H4 machine ) at the first boot after the installation. Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: ------------[ cut here ]------------ - Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: Badness at fs/sysfs/dir.c:491 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: NIP: c00000000024f71c LR: c000000000 024f718 CTR: 0000000000000001 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: REGS: c0000000ca287230 TRAP: 0700 Not tainted (2.6.32-118.el6.ppc64) Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: MSR: 8000000000029032 <EE,ME,CE,IR,, DR> CR: 28248444 XER: 20000010 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: TASK = c0000000cbee46f0[754] 'modprr obe' THREAD: c0000000ca284000 CPU: 4 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: GPR00: c00000000024f718 c0000000ca22 874b0 c000000000ed1090 0000000000000082 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: GPR04: 0000000000000000 ffffffffffff fffff 0000000000000003 0000000000080000 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: GPR08: 0000000000004c87 c000000000ee 32010 0000000000004c0d 000000000000000a Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: GPR12: 0000000028248442 c000000000ff a2f00 00000fff8abc00a0 0000000000000000 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: GPR16: 000001001ca300f0 c000000003dd e2f80 0000000000000000 0000000000000000 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: GPR20: fffffffffffff000 c000000003dd e302c 0000000000000010 c0000000c674b970 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: GPR24: c00000000024f69c 000000000000 01000 c0000000cf040180 c0000000cbf21b80 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: GPR28: c0000000ca2875d0 c0000000c6ff 5b660 c000000000e6d400 ffffffffffffffef Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: NIP [c00000000024f71c] .sysfs_add_oo ne+0xfc/0x170 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: LR [c00000000024f718] .sysfs_add_onn e+0xf8/0x170 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: Call Trace: Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca2874b0] [c00000000024f711 8] .sysfs_add_one+0xf8/0x170 (unreliable) Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287560] [c000000000250211 8] .create_dir+0x68/0x130 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287620] [c000000000250322 8] .sysfs_create_dir+0x48/0x80 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca2876b0] [c0000000002f1daa c] .kobject_add_internal+0xdc/0x2e0 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287750] [c0000000002f2277 8] .kobject_add+0x48/0x90 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca2877d0] [c0000000003a8544 8] .device_add+0xf8/0x6c0 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca2878b0] [d000000001a407ee c] .enclosure_component_register+0x10c/0x160 [enclosure] Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287970] [d000000001ad0bdd 4] .ses_enclosure_data_process+0x424/0x480 [ses] Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287a60] [d000000001ad11ff c] .ses_intf_add+0x30c/0x650 [ses] Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287b20] [c0000000003ade22 c] .class_interface_register+0xdc/0x120 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287bd0] [c0000000003d5555 4] .scsi_register_interface+0x24/0x40 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287c50] [d000000001ad1688 0] .ses_init+0x28/0x4f8 [ses] Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287ce0] [c000000000009766 c] .do_one_initcall+0x5c/0x200 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287d90] [c0000000000dcfff c] .SyS_init_module+0x14c/0x2c0 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287e30] [c000000000008566 4] syscall_exit+0x0/0x40 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: Instruction dump: Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: 7f64db78 4bfffec1 e89e8038 4bdfcee55 60000000 e89d0018 4bdfced9 60000000 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: 7c641b78 e87e8040 4835407d 600000000 <0fe00000> 7f63db78 4bf5a78d 60000000 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: kobject_add_internal failed for ww ith -EEXIST, don't try to register things with the same name in the same directoo ry. Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: Call Trace: Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287600] [c000000000012e00 4] .show_stack+0x74/0x1c0 (unreliable) Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca2876b0] [c0000000002f1e66 c] .kobject_add_internal+0x19c/0x2e0 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287750] [c0000000002f2277 8] .kobject_add+0x48/0x90 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca2877d0] [c0000000003a8544 8] .device_add+0xf8/0x6c0 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca2878b0] [d000000001a407ee c] .enclosure_component_register+0x10c/0x160 [enclosure] Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287970] [d000000001ad0bdd 4] .ses_enclosure_data_process+0x424/0x480 [ses] Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287a60] [d000000001ad11ff c] .ses_intf_add+0x30c/0x650 [ses] Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287b20] [c0000000003ade22 c] .class_interface_register+0xdc/0x120 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287bd0] [c0000000003d5555 4] .scsi_register_interface+0x24/0x40 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287c50] [d000000001ad1688 0] .ses_init+0x28/0x4f8 [ses] Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287ce0] [c000000000009766 c] .do_one_initcall+0x5c/0x200 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287c50] [d000000001ad1688 0] .ses_init+0x28/0x4f8 [ses] Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287ce0] [c000000000009766 c] .do_one_initcall+0x5c/0x200 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287d90] [c0000000000dcfff c] .SyS_init_module+0x14c/0x2c0 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: [c0000000ca287e30] [c000000000008566 4] syscall_exit+0x0/0x40 Mar 15 00:26:54 devhv4e-woodward-lp1 kernel: sysfs: cannot create duplicate filee name '/devices/pci0000:00/0000:00:01.0/host0/target0:4:18/0:4:18:0/enclosure/0:44 :18:0/ ' [root@devhv4e-woodward-lp1 /]# lsscsi [0:3:0:0] cd/dvd IBM DROM0040502 WA61 /dev/sr0 [0:4:2:0] disk IBM ST973402SS BF05 /dev/sda [0:4:4:0] disk IBM ST973402SS BF05 /dev/sdb [0:4:6:0] disk IBM ST973402SS BF05 /dev/sdc [0:4:7:0] disk IBM ST973402SS BF05 /dev/sdd [0:4:8:0] disk IBM ST973402SS BF05 /dev/sde [0:4:9:0] disk IBM ST973402SS BF05 /dev/sdf [0:4:11:0] disk IBM ST973402SS BF05 /dev/sdg [0:4:13:0] disk IBM ST973402SS BF05 /dev/sdh [0:4:18:0] enclosu IBM 0001 - [0:6:18:0] enclosu IBM 0001 - [0:8:0:0] enclosu IBM VSBPM2SE4 3GSAS 01 - [0:255:255:255]no dev IBM 572C001SISIOA 0150 -
Created attachment 484093 [details] sosreport
Created attachment 484095 [details] dmesg output
Created attachment 484096 [details] Boot log
with this filelineno: bug 584507 bug 619422 with this guiltyfunc: bug 590019 bug 604564
------- Comment From tpnoonan.com 2011-03-15 15:44 EDT------- please consider as exception for rhel6.1
Created attachment 487128 [details] Details on the system and disk drives. ------- Comment (attachment only) From hienn.com 2011-03-23 15:37 EDT-------
------- Comment From sbest.com 2011-03-24 09:44 EDT------- Hi Wayne, we could we use some of your scsi expertise. If I'm looking at the log correct drivers/scsi/ses.c sees 3 enclosures ses 0:4:18:0: Attached Enclosure device ses 0:6:18:0: Attached Enclosure device ses 0:8:0:0: Attached Enclosure device and when Hien physically looked at this system there was 1 enclosure with 8 disks. ideas on why ses.c thinks there are 3 enclosures? -Steve
------- Comment From wayneb.com 2011-03-24 15:00 EDT------- The first thing that needs to be done is to upgrade firmware. I've upgraded the firmware on the Cadet-X adapter. It was quite old. The first two enclosure devices are part of the internal Lahaina enclosure. The current firmware level is this: A1700DE2.0001 (04-18-2008) Bring up Code. It needs to be upgraded to A1700DE2.0008, but I need someone to verify the following: Microcode Update/Download directions from 0001 to 0008 ?? Make sure you do NOT have any cable attached to the back of Lahaina during this code update from 0001 to 0008. ( I am talking about the RED cable that goes from Lahaina to the back of the system ) Hien, could you verify that this cable is not attached? If it is, could you disconnect it so that I can do the upgrade? Also, would someone please post the HMC information for this system?
------- Comment From wayneb.com 2011-03-25 12:40 EDT------- (In reply to comment #44) > Hi Wayne, > > we could we use some of your scsi expertise. If I'm looking at the log correct > drivers/scsi/ses.c sees 3 enclosures > > ses 0:4:18:0: Attached Enclosure device > ses 0:6:18:0: Attached Enclosure device > ses 0:8:0:0: Attached Enclosure device > > and when Hien physically looked at this system there was 1 enclosure with 8 > disks. ideas on why ses.c thinks there are 3 enclosures? > > -Steve Steve, To answer your question, the three enclosure devices are expected and are part of the internal SAS architecture. http://ausgsa.ibm.com/~jschwarz/SAS%20Presentation/SAS%20on%20HV8%20&%20HV4.htm The SAS addressing for Lahaina shows the three ses devices. http://ausgsa.ibm.com/~jschwarz/SAS%20Presentation/SAS%20on%20HV8%20&%20HV4.htm#SAS_Addressing In this case 0:4:18:0 and 0:6:18:0 are the 1st and 2nd ses devices. 0:0:8:0 is the virtual ses device.
closing upgrading the firmware fixed this issue