https://bugzilla.novell.com/show_bug.cgi?id=393537 User bugproxy@us.ibm.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393537#c1 Summary: P550-Power5 not booting after installing Opensuse-11- Beta3-ppc64 image. Product: openSUSE 11.0 Version: Beta 2 Platform: PowerPC-64 OS/Version: All Status: NEW Severity: Blocker Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bugproxy@us.ibm.com QAContact: jsrain@novell.com Found By: Third Party Developer/Partner Partner ID: LTC 44935 =Comment: #1================================================= Cijurajan Kollanoor - 2008-05-22 07:48 EDT Problem description: ==================== After installation with Opensuse-11-Beta3 on P550 lpars, lpars are not coming up. It is hitting OOPs at scheduling part of the kernel code and generating call traces. Following are the boot messages with OOP and call traces: ------ boot messages that has the OOPs and call traces ---------- IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM / Elapsed time since release of system processors: 165799 mins 52 secs yaboot starting: loaded at 00040000 000633f0 (0/0/00c39a50; sp: 019fffd0) Welcome to yaboot version 10.1.22-r1034.SuSE booted from '/vdevice/v-scsi@3000000d/disk@8100000000000000' Using configfile 'built-in' Enter "help" to get some basic usage information boot: * Ppc64 linux boot: Please wait, loading kernel... Allocated 00a00000 bytes for kernel @ 00200000 Elf64 kernel loaded... Loading ramdisk... ramdisk loaded 00485000 @ 02b00000 OF stdout device is: /vdevice/vty@30000000 Hypertas detected, assuming LPAR ! command line: root=/dev/sda5 quiet sysrq=1 memory layout at init: alloc_bottom : 0000000002f85000 alloc_top : 0000000008000000 alloc_top_hi : 0000000072000000 rmo_top : 0000000008000000 ram_top : 0000000072000000 Looking for displays instantiating rtas at 0x00000000077ca000 ... done 0000000000000000 : boot cpu 0000000000000000 0000000000000002 : starting cpu hw idx 0000000000000002... done 0000000000000004 : starting cpu hw idx 0000000000000004... done 0000000000000006 : starting cpu hw idx 0000000000000006... done 0000000000000008 : starting cpu hw idx 0000000000000008... done 000000000000000a : starting cpu hw idx 000000000000000a... done 000000000000000c : starting cpu hw idx 000000000000000c... done 000000000000000e : starting cpu hw idx 000000000000000e... done 0000000000000010 : starting cpu hw idx 0000000000000010... done copying OF device tree ... Building dt strings... Building dt structure... Device tree strings 0x0000000003386000 -> 0x000000000338723f Device tree struct 0x0000000003388000 -> 0x0000000003393000 Calling quiesce ... returning from prom_init doing fast boot Creating device nodes with udev sd 2:0:1:0: [sda] Assuming drive cache: write through sd 2:0:1:0: [sda] Assuming drive cache: write through blogd: can not open pty/tty pair: No such file or directory Waiting for device /dev/sda5 to appear: ok fsck 1.40.8 (13-Mar-2008) [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda5 /dev/sda5: recovering journal /dev/sda5: clean, 126798/1089536 files, 858162/4351599 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/sda5 INIT: version 2.86 booting System Boot Control: Running /etc/init.d/boot Mounting procfs at /proc done Mounting sysfs at /sys done Mounting debugfs at /sys/kernel/debug done Initializing /dev done Mounting devpts at /dev/pts done Boot logging started on /dev/hvc0(/dev/console (deleted)) at Mon May 19 17:07:29 2008 done Starting udevd: ------------[ cut here ]------------ Badness at kernel/sched_rt.c:294 ------------[ cut here ]------------ Badness at kernel/sched_rt.c:300 ------------[ cut here ]------------ kernel BUG at kernel/sched_rt.c:502! Oops: Exception in kernel mode, sig: 5 [#1] SMP NR_CPUS=128 NUMA pSeries Modules linked in: e1000(+) sg sd_mod ibmvscsic scsi_transport_srp scsi_tgt pata_pdc2027x libata scsi_mod NIP: c00000000006b34c LR: c0000000004371b8 CTR: c00000000006b2dc REGS: c00000006e823780 TRAP: 0700 Tainted: G N (2.6.25.3-2-ppc64) MSR: 8000000000029032 CR: 24000044 XER: 20000001 TASK = c000000070593580[79] 'rtasd' THREAD: c00000006e820000 CPU: 8 GPR00: 0000000000000001 c00000006e823a00 c00000000077b6a0 c000000000923080 GPR04: c000000000923108 00000000000319cc 0000000000000001 00000000000319cc GPR08: c0000000009230e0 0000000000000064 c000000000923080 c000000000923158 GPR12: 0000000000000000 c0000000006d1000 c000000000651608 0000000000000000 GPR16: c00000006e823a88 c00000006e820000 c000000000660920 c000000000661080 GPR20: c0000000705938f0 0000000000000008 c000000000659890 c00000006e823e90 GPR24: c000000000923080 c000000070593580 c00000006e823de0 0000000000000002 GPR28: 7fffffffffffffff c00000006e820080 c00000000070b290 c000000000479b10 NIP [c00000000006b34c] .pick_next_task_rt+0x70/0xb0 LR [c0000000004371b8] .schedule+0x5c4/0x8c4 Call Trace: [c00000006e823a00] [c000000000437164] .schedule+0x570/0x8c4 (unreliable) [c00000006e823b50] [c0000000000768a8] .__cond_resched+0x2c/0x5c [c00000006e823be0] [c000000000437664] ._cond_resched+0x44/0x64 [c00000006e823c60] [c0000000004376d0] .wait_for_common+0x4c/0x250 [c00000006e823d40] [c000000000076ab0] .set_cpus_allowed+0x128/0x16c [c00000006e823e20] [c00000000004880c] .do_event_scan_all_cpus+0xac/0x1c0 [c00000006e823ef0] [c0000000000489b8] .rtasd+0x98/0xf8 [c00000006e823f90] [c000000000027894] .kernel_thread+0x4c/0x68 Instruction dump: 7d200074 2000003f 48000018 e92b0008 7c0900d0 7c004838 7c000074 2000007f 7c0907b4 2f890063 7c000026 5400f7fe <0b000000> 38090001 780026e4 7c6b002a ---[ end trace 400babcfe43f968b ]--- smp_call_function on cpu 10: other cpus not responding (14) smp_call_function on cpu 10: other cpus not responding (14) If this is a customer issue, please indicate the impact to the customer: ------------------------------------------------------------------------------- Machine information: ==================== Found this issue in P550 lpar1 and lpar3. Could reproduce this several times. Machine type (p650, x235, SF2, etc.): p510 Cpu type (Power4, Power5, IA-64, etc.):Power5 Reproducible: ============= Yes, it is reproducible. Describe the steps: -> Start the installation of Opensuse-11-beta3 using nfs method of installation. -> After Installation completes and yast-installer boots, watch the messages thrown on the console. (You can see machine hanging at 'Starting udevd' and generating this messages) Hung: ===== Is the system (not just the application) hung? No, its in a kind of wait state, but not dead. If so, describe how you determined this: I could see the status of the lpar in HMC as running. OOPs: ===== Did the system produce an OOPS message on the console? Yes If so, copy it here: Oops: Exception in kernel mode, sig: 5 [#1] SMP NR_CPUS=128 NUMA pSeries =Comment: #2================================================= Cijurajan Kollanoor - 2008-05-22 07:50 EDT Problem is happening only in the machine model p550. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.