Power machines fail to boot after build being successful
Hi,
After successfully building the kernel version 2.6.36-rc2-git4(commitid d4348c678977c) with the config file attached(used make oldconfig), P5 and P6 power machines fails to reboot with the following logs
Logs collected while rebooting into today next, same occurs with the upstream kernel too.
Please wait, loading kernel...
Allocated 01a00000 bytes for kernel @ 03500000
Elf64 kernel loaded...
Loading ramdisk...
ramdisk loaded 00841ae7 @ 04f00000
OF stdout device is: /vdevice/vty@30000000
Preparing to boot Linux version 2.6.36-rc2-autotest-next-20100826 (root@llm62) (gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) ) #1 SMP Thu Aug 26 10:55:01 IST 2010 Max number of cores passed to firmware: 512 (NR_CPUS = 1024)
Calling ibm,client-architecture-support... done
command line: root=/dev/sda5 IDENT=1282801372 xmon=early
memory layout at init:
memory_limit : 0000000000000000 (16 MB aligned)
alloc_bottom : 0000000005750000
alloc_top : 0000000008000000
alloc_top_hi : 0000000008000000
rmo_top : 0000000008000000
ram_top : 0000000008000000
instantiating rtas at 0x00000000074e0000... done
boot cpu hw idx 0
starting cpu hw idx 2... done
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x0000000005760000 -> 0x00000000057615fa
Device tree struct 0x0000000005770000 -> 0x0000000005790000
Calling quiesce...
returning from prom_init
Using pSeries machine description
Using 1TB segments
Found initrd at 0xc000000004f00000:0xc000000005741ae7
Partition configured for 4 cpus.
CPU maps initialized for 2 threads per core
Starting Linux PPC64 #1 SMP Thu Aug 26 10:55:01 IST 2010
-----------------------------------------------------
ppc64_pft_size = 0x1a physicalMemorySize = 0x100000000 htab_hash_mask = 0x7ffff
-----------------------------------------------------
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.36-rc2-autotest-next-20100826 (root@llm62) (gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) ) #1 SMP Thu Aug 26 10:55:01 IST 2010 [boot]0012 Setup Arch
EEH: No capable adapters found
PPC64 nvram contains 15360 bytes
Zone PFN ranges:
DMA 0x00000000 -> 0x00010000
Normal empty
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
1: 0x00000000 -> 0x00010000
Could not find start_pfn for node 0
[boot]0015 Setup Done
PERCPU: Embedded 29 pages/cpu @c000000002100000 s1859840 r0 d40704 u2097152
pcpu-alloc: s1859840 r0 d40704 u2097152 alloc=2*1048576
pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Built 2 zonelists in Node order, mobility grouping on. Total pages: 65480
Policy zone: DMA
Kernel command line: root=/dev/sda5 IDENT=1282801372 xmon=early
PID hash table entries: 4096 (order: -1, 32768 bytes)
freeing bootmem node 1
Memory: 4124352k/4194304k available (10880k kernel code, 69952k reserved, 2880k data, 10947k bss, 2432k init) Hierarchical RCU implementation.
Verbose stalled-CPUs detection is disabled.
NR_IRQS:512
[boot]0020 XICS Init
[boot]0021 XICS Done
clocksource: timebase mult[7d0000] shift[22] registered
Console: colour dummy device 80x25
console [hvc0] enabled, bootconsole disabled
console [hvc0] enabled, bootconsole disabled
Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
... MAX_LOCKDEP_SUBCLASSES: 8 ... MAX_LOCK_DEPTH: 48 ... MAX_LOCKDEP_KEYS: 8191 ... CLASSHASH_SIZE: 4096 ... MAX_LOCKDEP_ENTRIES: 16384 ... MAX_LOCKDEP_CHAINS: 32768 ... CHAINHASH_SIZE: 16384
memory used by lock dependency info: 6335 kB
per task-struct memory footprint: 2688 bytes
allocated 2621440 bytes of page_cgroup
please try 'cgroup_disable=memory' option if you don't want memory cgroupspid_max: default: 32768 minimum: 301
Security Framework initialized
SELinux: Disabled at boot.
AppArmor: AppArmor disabled by boot time parameter
Dentry cache hash table entries: 524288 (order: 6, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 5, 2097152 bytes) Mount-cache hash table entries: 4096
Initializing cgroup subsys ns
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
cpu 0x1: Vector: 300 (Data Access) at [c0000000fedcbd10]
pc: 0000000000017f00
lr: 0000000000008290
sp: c0000000fedcbf90 msr: 8000000000001000
dar: c0000000fedcbfa0
dsisr: 42000000
current = 0xc0000000fedb4e70
paca = 0xc000000007440280
pid = 0, comm = swapper
WARNING: exception is not recoverable, can't continue
enter ? for help
1:mon> Unable to handle kernel paging request for data at address 0xc0000000fedcbfa0 Faulting instruction address: 0x00017f00
Processor 1 is stuck.
cpu 0x2: Vector: 300 (Data Access) at [c0000000fedcfd10]
pc: 0000000000017f00
lr: 0000000000008290
sp: c0000000fedcff90
msr: 8000000000001002
dar: c0000000fedcffa0
dsisr: 42000000
current = 0xc0000000fedb7580
paca = 0xc000000007440500
pid = 0, comm = swapper
Unable to handle kernel paging request for data at address 0xc0000000fedcffa0
Faulting instruction address: 0x00017f00
Processor 2 is stuck.
cpu 0x3: Vector: 300 (Data Access) at [c0000000fee33d10]
pc: 0000000000017f00
lr: 0000000000008290
sp: c0000000fee33f90 msr: 8000000000001000
dar: c0000000fee33fa0
dsisr: 42000000
current = 0xc0000000fedb9c90
paca = 0xc000000007440780
pid = 0, comm = swapper
WARNING: exception is not recoverable, can't continue
Thanks
Divya
CONFIG_ALTIVEC=y
# CONFIG_WIRELESS is not setCONFIG_VSX=yCONFIG_TASKSTATS=yCONFIG_TASK_DELAY_ACCT=yCONFIG_TASK_XACCT=yCONFIG_TASK_IO_ACCOUNTING=yCONFIG_HAVE_KPROBES=yCONFIG_HAVE_KRETPROBES=yCONFIG_TREE_RCU=yCONFIG_RCU_FANOUT=64CONFIG_CGROUP_SCHED=yCONFIG_CGROUPS=yCONFIG_CGROUP_NS=yCONFIG_CGROUP_FREEZER=yCONFIG_CGROUP_DEVICE=yCONFIG_CPUSETS=yCONFIG_PROC_PID_CPUSET=yCONFIG_CGROUP_CPUACCT=yCONFIG_RESOURCE_COUNTERS=yCONFIG_CGROUP_MEM_RES_CTLR=yCONFIG_CGROUP_MEM_RES_CTLR_SWAP=yCONFIG_NAMESPACES=yCONFIG_UTS_NS=yCONFIG_IPC_NS=yCONFIG_USER_NS=yCONFIG_PID_NS=yCONFIG_NET_NS=yCONFIG_KALLSYMS=yCONFIG_KALLSYMS_ALL=yCONFIG_KPROBES=yCONFIG_CMM=yCONFIG_PPC_HAS_HASH_64K=yCONFIG_PPC_64K_PAGES=yCONFIG_FORCE_MAX_ZONEORDER=9CONFIG_PPC_SUBPAGE_PROT=yCONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=yCONFIG_ARCH_HAS_WALK_MEMORY=yCONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=yCONFIG_KEXEC=yCONFIG_MEMORY_HOTPLUG=yCONFIG_MEMORY_HOTPLUG_SPARSE=yCONFIG_MEMORY_HOTREMOVE=yCONFIG_IBMEBUS=yCONFIG_EHEA=yCONFIG_SCSI_IBMVSCSI=yCONFIG_SCSI_IBMVFC=mCONFIG_SCSI_IPR=yCONFIG_DEBUG_KERNEL=yCONFIG_DETECT_SOFTLOCKUP=yCONFIG_DETECT_HUNG_TASK=yCONFIG_DEBUG_SPINLOCK=yCONFIG_DEBUG_SPINLOCK_SLEEP=yCONFIG_DEBUG_BUGVERBOSE=yCONFIG_DEBUG_INFO=yCONFIG_KPROBES_SANITY_TEST=yCONFIG_LATENCYTOP=yCONFIG_SYSCTL_SYSCALL_CHECK=yCONFIG_DEBUG_PAGEALLOC=yCONFIG_NOP_TRACER=yCONFIG_HAVE_FUNCTION_TRACER=yCONFIG_HAVE_FUNCTION_GRAPH_TRACER=yCONFIG_HAVE_DYNAMIC_FTRACE=yCONFIG_HAVE_FTRACE_MCOUNT_RECORD=yCONFIG_RING_BUFFER=yCONFIG_TRACING=yCONFIG_TRACING_SUPPORT=y
ONFIG_BLK_DEV_IO_TRACE=yCONFIG_FTRACE_SELFTEST=yCONFIG_FTRACE_STARTUP_TEST=yCONFIG_KEYS=yCONFIG_KEYS_DEBUG_PROC_KEYS=yCONFIG_SECURITY=yCONFIG_SECURITYFS=yCONFIG_SECURITY_NETWORK=yCONFIG_RCU_CPU_STALL_DETECTOR=yCONFIG_EXT2_FS=yCONFIG_EXT2_FS_XATTR=yCONFIG_EXT2_FS_POSIX_ACL=yCONFIG_EXT2_FS_SECURITY=yCONFIG_EXT3_FS=yCONFIG_EXT3_FS_XATTR=yCONFIG_EXT3_FS_POSIX_ACL=yCONFIG_EXT3_FS_SECURITY=yCONFIG_EXT4_FS=yCONFIG_EXT4DEV_COMPAT=yCONFIG_EXT4_FS_XATTR=yCONFIG_EXT4_FS_POSIX_ACL=yCONFIG_EXT4_FS_SECURITY=yCONFIG_JBD=yCONFIG_JBD2=yCONFIG_REISERFS_PROC_INFO=yCONFIG_REISERFS_FS_XATTR=yCONFIG_REISERFS_FS_POSIX_ACL=yCONFIG_REISERFS_FS_SECURITY=yCONFIG_JFS_FS=mCONFIG_JFS_POSIX_ACL=yCONFIG_JFS_SECURITY=yCONFIG_JFS_STATISTICS=yCONFIG_FS_POSIX_ACL=yCONFIG_FILE_LOCKING=yCONFIG_XFS_FS=mCONFIG_XFS_QUOTA=yCONFIG_XFS_POSIX_ACL=yCONFIG_XFS_RT=yCONFIG_GFS2_FS=mCONFIG_GFS2_FS_LOCKING_DLM=mCONFIG_OCFS2_FS=mCONFIG_OCFS2_FS_O2CB=mCONFIG_OCFS2_FS_USERSPACE_CLUSTER=mCONFIG_OCFS2_FS_STATS=yCONFIG_BTRFS_FS=yCONFIG_BTRFS_FS_POSIX_ACL=yCONFIG_LOCALVERSION_AUTO=nCONFIG_LOCALVERSION=""CONFIG_SLUB_DEBUG=yCONFIG_SLUB=yCONFIG_DEVPTS_MULTIPLE_INSTANCES=yCONFIG_HAVE_PERF_COUNTERS=yCONFIG_PERF_COUNTERS=yCONFIG_DEFAULT_MMAP_MIN_ADDR=65536CONFIG_FSNOTIFY=yCONFIG_RCU_TORTURE_TEST=yCONFIG_RCU_TORTURE_TEST_RUNNABLE=yCONFIG_RCU_CPU_STALL_DETECTOR=yCONFIG_PERF_EVENTS=yCONFIG_PPC_OF_BOOT_TRAMPOLINE=yCONFIG_BLOCK=yCONFIG_BLK_DEV_BSG=yCONFIG_BLK_DEV_INTEGRITY=yCONFIG_BLK_CGROUP=yCONFIG_DEBUG_BLK_CGROUP=yCONFIG_BLOCK_COMPAT=yCONFIG_IOSCHED_NOOP=yCONFIG_IOSCHED_CFQ=yCONFIG_CFQ_GROUP_IOSCHED=yCONFIG_DEBUG_CFQ_IOSCHED=yCONFIG_DEFAULT_CFQ=yCONFIG_DEFAULT_IOSCHED="cfq"CONFIG_VIRTUALIZATION=yCONFIG_VIRTIO_PCI=yCONFIG_VIRTIO_BALLOON=yCONFIG_NR_IRQS=512CONFIG_MIGRATION=yCONFIG_KSM=yCONFIG_PM=yCONFIG_SUSPEND=yCONFIG_SUSPEND_FREEZER=yCONFIG_HIBERNATION=yCONFIG_SYSFS_DEPRECATED_V2=yCONFIG_LOCK_STAT=yCONFIG_LOCKDEP_SUPPORT=yCONFIG_LOCKDEP=yCONFIG_IXGBE_DCB=yCONFIG_DCB=y
Quoted 5 lines · divya
Hi,
After successfully building the kernel version 2.6.36-rc2-git4(commitid
d4348c678977c) with the config file attached(used make oldconfig), P5 and P6 power machines fails to reboot with the following logs
<snip>
Quoted 1 line
Preparing to boot Linux version 2.6.36-rc2-autotest-next-20100826 (root@llm62) (gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) ) #1 SMP Thu Aug 26 10:55:01 IST 2010
You say you're booting -git4 but you're running kernel is Linux next from Aug. 26th Can you confirm you see this boot failure with Linus's tree NOT linux next?
Adding linux-ppc and linux-next lists.
Yours Tony
Quoted 7 lines
After successfully building the kernel version 2.6.36-rc2-git4(commitid
d4348c678977c) with the config file attached(used make oldconfig), P5 and P6 power machines fails to reboot with the following logsLogs collected while rebooting into today next, same occurs with the upstream kernel too.
This will fix your problem:
http://patchwork.ozlabs.org/patch/62757/
Please CC [email protected] for pwoerpc bug reports.
Mikey
Quoted 7 lines
Please wait, loading kernel...
Allocated01a00000bytes for kernel @ 03500000
Elf64 kernel loaded...
Loading ramdisk...
ramdisk loaded00841ae7@04f00000
OF stdout device is: /vdevice/vty@30000000
Preparing to boot Linux version 2.6.36-rc2-autotest-next-20100826 (root@llm62
) (gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) ) #1 SMP Thu
Aug 26 10:55:01 IST 2010
Quoted 27 lines
Max number of cores passed to firmware: 512 (
NR_CPUS= 1024) Calling ibm,client-architecture-support... done command line: root=/dev/sda5 IDENT=1282801372 xmon=early memory layout at init:memory_limit : 0000000000000000 (16 MB aligned) alloc_bottom : 0000000005750000 alloc_top : 0000000008000000 alloc_top_hi : 0000000008000000 rmo_top : 0000000008000000 ram_top : 0000000008000000instantiating rtas at
0x00000000074e0000... done boot cpu hw idx 0
starting cpu hw idx 2... done
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings0x0000000005760000->0x00000000057615faDevice tree struct0x0000000005770000->0x0000000005790000Calling quiesce...
returning fromprom_init
Using pSeries machine description
Using 1TB segments
Found initrd at 0xc000000004f00000:0xc000000005741ae7 Partition configured for 4 cpus.
CPU maps initialized for 2 threads per core Starting Linux PPC64 #1 SMP Thu Aug 26 10:55:01 IST 2010
-----------------------------------------------------
Quoted 7 lines
ppc64_pft_size = 0x1a physicalMemorySize = 0x100000000 htab_hash_mask = 0x7ffff-----------------------------------------------------
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.36-rc2-autotest-next-20100826 (root@llm62) (gcc version 4.3
.2 [gcc-4_3-branch revision 141291] (SUSE Linux) ) #1 SMP Thu Aug 26 10:55:01 I ST 2010
Quoted 9 lines
[boot]0012 Setup Arch
EEH: No capable adapters found
PPC64 nvram contains 15360 bytes
Zone PFN ranges:DMA 0x00000000 -> 0x00010000 Normal empty Movable zone start PFN for each node early_node_map[1] active PFN ranges 1: 0x00000000 -> 0x00010000
Quoted 11 lines
Could not find
start_pfnfor node 0
[boot]0015 Setup Done
PERCPU: Embedded 29 pages/cpu @c000000002100000 s1859840 r0 d40704 u2097152
pcpu-alloc: s1859840 r0 d40704 u2097152 alloc=2*1048576
pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Built 2 zonelists in Node order, mobility grouping on. Total pages: 65480 Policy zone: DMA
Kernel command line: root=/dev/sda5 IDENT=1282801372 xmon=early PID hash table entries: 4096 (order: -1, 32768 bytes)
freeing bootmem node 1
Memory: 4124352k/4194304k available (10880k kernel code, 69952k reserved, 288
0k data, 10947k bss, 2432k init)
Quoted 39 lines
Hierarchical RCU implementation.
Verbose stalled-CPUs detection is disabled.
NR_IRQS:512
[boot]0020 XICS Init
[boot]0021 XICS Done
clocksource: timebase mult[7d0000] shift[22] registered
Console: colour dummy device 80x25
console [hvc0] enabled, bootconsole disabled
console [hvc0] enabled, bootconsole disabled
Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar... MAX_LOCKDEP_SUBCLASSES: 8 ... MAX_LOCK_DEPTH: 48 ... MAX_LOCKDEP_KEYS: 8191 ... CLASSHASH_SIZE: 4096 ... MAX_LOCKDEP_ENTRIES: 16384 ... MAX_LOCKDEP_CHAINS: 32768 ... CHAINHASH_SIZE: 16384memory used by lock dependency info: 6335 kB
per task-struct memory footprint: 2688 bytes
allocated 2621440 bytes ofpage_cgroup
please try 'cgroup_disable=memory' option if you don't want memory cgroupspid_max: default: 32768 minimum: 301
Security Framework initialized
SELinux: Disabled at boot.
AppArmor: AppArmor disabled by boot time parameter
Dentry cache hash table entries: 524288 (order: 6, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 5, 2097152 bytes) Mount-cache hash table entries: 4096
Initializing cgroup subsys ns
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
cpu0x1: Vector: 300 (Data Access) at [c0000000fedcbd10]pc: 0000000000017f00 lr: 0000000000008290 sp: c0000000fedcbf90 msr: 8000000000001000 dar: c0000000fedcbfa0
Quoted 7 lines
dsisr: 42000000
current =0xc0000000fedb4e70
paca =0xc000000007440280
pid = 0, comm = swapper
WARNING: exception is not recoverable, can't continue
enter ? for help
1:mon> Unable to handle kernel paging request for data at address0xc0000000
fedcbfa0
Quoted 202 lines
Faulting instruction address:
0x00017f00Processor 1 is stuck.
cpu0x2: Vector: 300 (Data Access) at [c0000000fedcfd10]pc: 0000000000017f00 lr: 0000000000008290 sp: c0000000fedcff90 msr: 8000000000001002 dar: c0000000fedcffa0 dsisr: 42000000 current = 0xc0000000fedb7580 paca = 0xc000000007440500 pid = 0, comm = swapper Unable to handle kernel paging request for data at address 0xc0000000fedcffa0 Faulting instruction address: 0x00017f00 Processor 2 is stuck. cpu 0x3: Vector: 300 (Data Access) at [c0000000fee33d10] pc: 0000000000017f00 lr: 0000000000008290 sp: c0000000fee33f90 msr: 8000000000001000 dar: c0000000fee33fa0dsisr: 42000000
current =0xc0000000fedb9c90
paca =0xc000000007440780
pid = 0, comm = swapper
WARNING: exception is not recoverable, can't continueThanks
Divya--------------060402090502050601040804
Content-Type: text/plain;
name="config_ppc_slub"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="config_ppc_slub"
CONFIG_ALTIVEC=y
#CONFIG_WIRELESSis not setCONFIG_VSX=yCONFIG_TASKSTATS=yCONFIG_TASK_DELAY_ACCT=yCONFIG_TASK_XACCT=yCONFIG_TASK_IO_ACCOUNTING=yCONFIG_HAVE_KPROBES=yCONFIG_HAVE_KRETPROBES=yCONFIG_TREE_RCU=yCONFIG_RCU_FANOUT=64CONFIG_CGROUP_SCHED=yCONFIG_CGROUPS=yCONFIG_CGROUP_NS=yCONFIG_CGROUP_FREEZER=yCONFIG_CGROUP_DEVICE=yCONFIG_CPUSETS=yCONFIG_PROC_PID_CPUSET=yCONFIG_CGROUP_CPUACCT=yCONFIG_RESOURCE_COUNTERS=yCONFIG_CGROUP_MEM_RES_CTLR=yCONFIG_CGROUP_MEM_RES_CTLR_SWAP=yCONFIG_NAMESPACES=yCONFIG_UTS_NS=yCONFIG_IPC_NS=yCONFIG_USER_NS=yCONFIG_PID_NS=yCONFIG_NET_NS=yCONFIG_KALLSYMS=yCONFIG_KALLSYMS_ALL=yCONFIG_KPROBES=yCONFIG_CMM=yCONFIG_PPC_HAS_HASH_64K=yCONFIG_PPC_64K_PAGES=yCONFIG_FORCE_MAX_ZONEORDER=9CONFIG_PPC_SUBPAGE_PROT=yCONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=yCONFIG_ARCH_HAS_WALK_MEMORY=yCONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=yCONFIG_KEXEC=yCONFIG_MEMORY_HOTPLUG=yCONFIG_MEMORY_HOTPLUG_SPARSE=yCONFIG_MEMORY_HOTREMOVE=yCONFIG_IBMEBUS=yCONFIG_EHEA=yCONFIG_SCSI_IBMVSCSI=yCONFIG_SCSI_IBMVFC=mCONFIG_SCSI_IPR=yCONFIG_DEBUG_KERNEL=yCONFIG_DETECT_SOFTLOCKUP=yCONFIG_DETECT_HUNG_TASK=yCONFIG_DEBUG_SPINLOCK=yCONFIG_DEBUG_SPINLOCK_SLEEP=yCONFIG_DEBUG_BUGVERBOSE=yCONFIG_DEBUG_INFO=yCONFIG_KPROBES_SANITY_TEST=yCONFIG_LATENCYTOP=yCONFIG_SYSCTL_SYSCALL_CHECK=yCONFIG_DEBUG_PAGEALLOC=yCONFIG_NOP_TRACER=yCONFIG_HAVE_FUNCTION_TRACER=yCONFIG_HAVE_FUNCTION_GRAPH_TRACER=yCONFIG_HAVE_DYNAMIC_FTRACE=yCONFIG_HAVE_FTRACE_MCOUNT_RECORD=yCONFIG_RING_BUFFER=yCONFIG_TRACING=yCONFIG_TRACING_SUPPORT=y
ONFIG_BLK_DEV_IO_TRACE=yCONFIG_FTRACE_SELFTEST=yCONFIG_FTRACE_STARTUP_TEST=yCONFIG_KEYS=yCONFIG_KEYS_DEBUG_PROC_KEYS=yCONFIG_SECURITY=yCONFIG_SECURITYFS=yCONFIG_SECURITY_NETWORK=yCONFIG_RCU_CPU_STALL_DETECTOR=yCONFIG_EXT2_FS=yCONFIG_EXT2_FS_XATTR=yCONFIG_EXT2_FS_POSIX_ACL=yCONFIG_EXT2_FS_SECURITY=yCONFIG_EXT3_FS=yCONFIG_EXT3_FS_XATTR=yCONFIG_EXT3_FS_POSIX_ACL=yCONFIG_EXT3_FS_SECURITY=yCONFIG_EXT4_FS=yCONFIG_EXT4DEV_COMPAT=yCONFIG_EXT4_FS_XATTR=yCONFIG_EXT4_FS_POSIX_ACL=yCONFIG_EXT4_FS_SECURITY=yCONFIG_JBD=yCONFIG_JBD2=yCONFIG_REISERFS_PROC_INFO=yCONFIG_REISERFS_FS_XATTR=yCONFIG_REISERFS_FS_POSIX_ACL=yCONFIG_REISERFS_FS_SECURITY=yCONFIG_JFS_FS=mCONFIG_JFS_POSIX_ACL=yCONFIG_JFS_SECURITY=yCONFIG_JFS_STATISTICS=yCONFIG_FS_POSIX_ACL=yCONFIG_FILE_LOCKING=yCONFIG_XFS_FS=mCONFIG_XFS_QUOTA=yCONFIG_XFS_POSIX_ACL=yCONFIG_XFS_RT=yCONFIG_GFS2_FS=mCONFIG_GFS2_FS_LOCKING_DLM=mCONFIG_OCFS2_FS=mCONFIG_OCFS2_FS_O2CB=mCONFIG_OCFS2_FS_USERSPACE_CLUSTER=mCONFIG_OCFS2_FS_STATS=yCONFIG_BTRFS_FS=yCONFIG_BTRFS_FS_POSIX_ACL=yCONFIG_LOCALVERSION_AUTO=nCONFIG_LOCALVERSION=""CONFIG_SLUB_DEBUG=yCONFIG_SLUB=yCONFIG_DEVPTS_MULTIPLE_INSTANCES=yCONFIG_HAVE_PERF_COUNTERS=yCONFIG_PERF_COUNTERS=yCONFIG_DEFAULT_MMAP_MIN_ADDR=65536CONFIG_FSNOTIFY=yCONFIG_RCU_TORTURE_TEST=yCONFIG_RCU_TORTURE_TEST_RUNNABLE=yCONFIG_RCU_CPU_STALL_DETECTOR=yCONFIG_PERF_EVENTS=yCONFIG_PPC_OF_BOOT_TRAMPOLINE=yCONFIG_BLOCK=yCONFIG_BLK_DEV_BSG=yCONFIG_BLK_DEV_INTEGRITY=yCONFIG_BLK_CGROUP=yCONFIG_DEBUG_BLK_CGROUP=yCONFIG_BLOCK_COMPAT=yCONFIG_IOSCHED_NOOP=yCONFIG_IOSCHED_CFQ=yCONFIG_CFQ_GROUP_IOSCHED=yCONFIG_DEBUG_CFQ_IOSCHED=yCONFIG_DEFAULT_CFQ=yCONFIG_DEFAULT_IOSCHED="cfq"CONFIG_VIRTUALIZATION=yCONFIG_VIRTIO_PCI=yCONFIG_VIRTIO_BALLOON=yCONFIG_NR_IRQS=512CONFIG_MIGRATION=yCONFIG_KSM=yCONFIG_PM=yCONFIG_SUSPEND=yCONFIG_SUSPEND_FREEZER=yCONFIG_HIBERNATION=yCONFIG_SYSFS_DEPRECATED_V2=yCONFIG_LOCK_STAT=yCONFIG_LOCKDEP_SUPPORT=yCONFIG_LOCKDEP=yCONFIG_IXGBE_DCB=yCONFIG_DCB=y--------------060402090502050601040804--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Hi Mikey,
Quoted 11 lines · On Fri, 27 Aug 2010 11:15:46 +1000 Michael Neuling <[email protected]> wrote:
Quoted 8 lines
After successfully building the kernel version 2.6.36-rc2-git4(commitid
d4348c678977c) with the config file attached(used make oldconfig), P5 and P6 power machines fails to reboot with the following logsLogs collected while rebooting into today next, same occurs with the upstream kernel too.
This will fix your problem:
http://patchwork.ozlabs.org/patch/62757/
I have seen something similar in my linux-next boot tests, so I will add this patch to linux-next for today.
Signature · 3 lines
Cheers, Stephen Rothwell [email protected] http://www.canb.auug.org.au/~sfr/
Quoted 10 lines · Stephen Rothwell
Hi Mikey,
Quoted 6 lines · On Fri, 27 Aug 2010 11:15:46 +1000 Michael Neuling<[email protected]> wrote:
Quoted 6 lines
After successfully building the kernel version 2.6.36-rc2-git4(commitid
d4348c678977c) with the config file attached(used make oldconfig), P5 and P6 power machines fails to reboot with the following logs
Quoted 9 lines
Quoted 6 lines
Quoted 3 lines
Logs collected while rebooting into today next, same occurs with the upstream kernel too.
This will fix your problem:
http://patchwork.ozlabs.org/patch/62757/I have seen something similar in my linux-next boot tests, so I will add this patch to linux-next for today.
Hi,
The same problem occurs on the linux-tree , now that since the patch is integrated into linux-next, im not able to find the problem with linux-next-20100827.
When will the patch be integrated with the linux-tree.
Thanks
Divya
Quoted 4 lines · In message <[email protected]> you wrote:
Quoted 3 lines · Stephen Rothwell
Hi Mikey,
On Fri, 27 Aug 2010 11:15:46 +1000 Michael Neuling<[email protected]> wrot
e:
Quoted 16 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
After successfully building the kernel version 2.6.36-rc2-git4(commitid
d4348c678977c) with the config file attached(used make oldconfig), P5 and P6 power machines fails to reboot with the following logsQuoted 9 lines
Quoted 6 lines
Quoted 3 lines
Logs collected while rebooting into today next, same occurs with the upstream kernel too.
This will fix your problem:
http://patchwork.ozlabs.org/patch/62757/I have seen something similar in my linux-next boot tests, so I will add this patch to linux-next for today.
Quoted 7 lines
Hi,
The same problem occurs on the linux-tree , now that since the patch is integrated into linux-next, im not able to find the problem with linux-next-20100827.
When will the patch be integrated with the linux-tree.
By "the linux-tree" do you mean Linus' tree?
If so, benh is likely to ask Linus to pull the fix in the next few days.
Mikey
Quoted 37 lines · Michael Neuling
Quoted 6 lines · In message<[email protected]> you wrote:
Quoted 4 lines · Stephen Rothwell
Hi Mikey,
On Fri, 27 Aug 2010 11:15:46 +1000 Michael Neuling<[email protected]> wrot
e:
Quoted 27 lines
Quoted 13 lines
Quoted 13 lines
Quoted 13 lines
After successfully building the kernel version 2.6.36-rc2-git4(commitid
d4348c678977c) with the config file attached(used make oldconfig), P5 and P6 power machines fails to reboot with the following logsLogs collected while rebooting into today next, same occurs with the upstream kernel too.
Quoted 8 lines
Quoted 4 lines
This will fix your problem:
http://patchwork.ozlabs.org/patch/62757/I have seen something similar in my linux-next boot tests, so I will add this patch to linux-next for today.
Hi,
The same problem occurs on the linux-tree , now that since the patch is integrated into linux-next, im not able to find the problem with linux-next-20100827.
Quoted 8 lines
Quoted 2 lines
When will the patch be integrated with the linux-tree.
By "the linux-tree" do you mean Linus' tree?
If so, benh is likely to ask Linus to pull the fix in the next few days.
Mikey
Yes i mean to say Linus' tree.ccing benh.
Divya