Re: [mainline][Oops][bisected 2ba3e6 ] 5.7.0 boot fails with kernel panic on powerpc

2020-06-03 Thread Abdul Haleem
On Wed, 2020-06-03 at 15:32 +0200, Joerg Roedel wrote: > On Wed, Jun 03, 2020 at 04:20:57PM +0530, Abdul Haleem wrote: > > @Joerg, Could you please have a look? > > Can you please try the attached patch? Thanks Joerg, The given patch fixes the boot problem. Please add Reported-b

Re: [linux-next][BUG][driver/scsi/lpfc][c00f62e6] Kernel panics when booting next kernel on my Power 9 box

2019-08-28 Thread Abdul Haleem
On Wed, 2019-08-28 at 08:22 -0700, James Smart wrote: > On 8/27/2019 10:02 PM, Abdul Haleem wrote: > > Greetings, > > > > linux-next kernel 5.3.0-rc1 failed to boot with kernel Oops on Power 9 > > box > > > > I see a recent changes to lpfc code was from

[linux-next][PPC][bisected c7d8b7][gcc 6.4.1] build error at drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:1471

2019-08-21 Thread Abdul Haleem
(hmm: use mmu_notifier_get/put for 'struct hmm') error disappears when commit is reverted. -- Regard's Abdul Haleem IBM Linux Technology Centre

[linux-next][PPC][bisected c7d8b7][gcc 6.4.1] build error at drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:1471

2019-08-21 Thread Abdul Haleem
(hmm: use mmu_notifier_get/put for 'struct hmm') Reverting the commit fixes the issue. -- Regard's Abdul Haleem IBM Linux Technology Centre

Re: [5.3.0-rc4-next][bisected 882632][qla2xxx] WARNING: CPU: 10 PID: 425 at drivers/scsi/qla2xxx/qla_isr.c:2784 qla2x00_status_entry.isra

2019-08-19 Thread Abdul Haleem
On Wed, 2019-08-14 at 20:42 -0700, Bart Van Assche wrote: > On 8/14/19 10:18 AM, Abdul Haleem wrote: > > On Wed, 2019-08-14 at 10:05 -0700, Bart Van Assche wrote: > >> On 8/14/19 9:52 AM, Abdul Haleem wrote: > >>> Greeting's > >>> > >>>

Re: [5.3.0-rc4-next][bisected 882632][qla2xxx] WARNING: CPU: 10 PID: 425 at drivers/scsi/qla2xxx/qla_isr.c:2784 qla2x00_status_entry.isra

2019-08-14 Thread Abdul Haleem
On Wed, 2019-08-14 at 10:05 -0700, Bart Van Assche wrote: > On 8/14/19 9:52 AM, Abdul Haleem wrote: > > Greeting's > > > > Today's linux-next kernel (5.3.0-rc4-next-20190813) booted with warning on > > my powerpc power 8 lpar > > > > The WARN_

[linux-next][P9]Build error at drivers/gpu/drm/amd/amdgpu/amdgpu_mn.h:69 error: field mirror has incomplete type

2019-07-09 Thread Abdul Haleem
ernel config attached -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.13.0-rc3 Kernel Configuration # CONFIG_PPC64=y # # Processor support # CONFIG_PPC_BOOK3S_64=y # CONFIG_PPC_BOOK3E_64 is not set # CONFIG_POWER7_CPU

[next-20180601][nvme][ppc] Kernel Oops is triggered when creating lvm snapshots on nvme disks

2018-06-26 Thread Abdul Haleem
slab cache. ksm_rmap_item but object is from kmalloc-128 -- Regard's Abdul Haleem IBM Linux Technology Centre

[next-20180517][ppc] watchdog: CPU 88 self-detected hard LOCKUP @ update_cfs_group+0x30/0x150

2018-05-20 Thread Abdul Haleem
0018682939, last heartbeat TB:23464816758804 (10160ms ago -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.11.0-rc4 Kernel Configuration # CONFIG_PPC64=y # # Processor support # CONFIG_PPC_BOOK3S_64=y # CONFIG_PPC_BOOK3E_64 is

Re: [PATCH] crypto: reorder paes test lexicographically

2018-05-15 Thread Abdul Haleem
.suite = { > @@ -3679,6 +3671,14 @@ static const struct alg_test_desc alg_test_descs[] = { > } > } > }, { > + .alg = "xts4096(paes)", > + .test = alg_test_null, > + .fips_allowed = 1, > +

Re: [linux-next][bisected c7c133f3][gcc 4.8.5] build fail with error: first argument to ‘__builtin_choose_expr’ not a constant

2018-03-14 Thread Abdul Haleem
On Wed, 2018-03-14 at 19:39 +1100, Stephen Rothwell wrote: > Hi Abdul, > > On Wed, 14 Mar 2018 13:59:54 +0530 Abdul Haleem > wrote: > > > > Today's next kernel fails to build with gcc 4.8.5 on powerpc machine. > > Thanks for the report. Just for the future,

[linux-next][bisected c7c133f3][gcc 4.8.5] build fail with error: first argument to ‘__builtin_choose_expr’ not a constant

2018-03-14 Thread Abdul Haleem
-- Regard's Abdul Haleem IBM Linux Technology Centre

[mainline][libhugetlbfs][ppc] stack_grow_into_huge test results in kernel Oops

2018-02-09 Thread Abdul Haleem
ite+0x70/0x74 Instruction dump: 990d028c 4bc8 3c4c006d 3842d910 7c0802a6 fbe1fff8 7c7f1b78 f8010010 f821ffd1 3940 994d028c 814d0008 <7d201829> 2c09 40c20010 7d40192d ---[ end trace b21abd323ba17f9e ]--- Fixing recursive fault but reboot is needed! -- Regard's Abdul Haleem IBM Li

[mainline][ppc - bare-metal ] memory hotunplug operation results in kernel Oops

2018-02-08 Thread Abdul Haleem
cfe3 4082fea4 e87f ---[ end trace b21abd323ba17f9d ]--- -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.13.0-rc2 Kernel Configuration # CONFIG_PPC64=y # # Processor support # CONFIG_PPC_BOOK3S_64=y # CON

[mainline][Memory off/on][83e3c48] kernel Oops with memory hot-unplug on ppc

2018-02-05 Thread Abdul Haleem
945, q=29) All QSes seen, last rcu_sched kthread activity 2102 (4295176275-4295174173), jiffies_till_next_fqs=1, root ->qsmask 0x0 sh R running task0 6189 1 0x00000080 -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; D

[linux-next] kernel Oops when booting powerpc

2018-01-16 Thread Abdul Haleem
ib_srpt srpt_add_one(cxgb3_0) failed. iw_cxgb3: Initialized device :01:00.0 -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.15.0-rc7 Kernel Configuration # CONFIG_PPC64=y # # Processor support # CONFIG_P

[linux-next][qla2xxx][85caa95]kernel BUG at lib/list_debug.c:31!

2018-01-09 Thread Abdul Haleem
p, prev=%p, next=%p.\n", 31 new, prev, next)) 32 return false; 33 -- Regard's Abdul Haleem IBM Linux Technology Centre

[mainline] rcu stalls on CPU when unbinding mpt3sas driver

2017-12-12 Thread Abdul Haleem
ite+0x60/0x110 [c07792d47e30] [c000b8e0] system_call+0x58/0x6c -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.11.0-rc4 Kernel Configuration # CONFIG_PPC64=y # # Processor support # CONFIG_PPC_BOO

Re: [linux-next][41e83b9][gcc 4.8.5] make modules fail at net/netfilter/xt_bpf.ko

2017-12-06 Thread Abdul Haleem
On Tue, 2017-12-05 at 18:06 +, Al Viro wrote: > On Tue, Dec 05, 2017 at 08:13:11PM +0530, Abdul Haleem wrote: > > Hi Al Viro, > > > > Today's next kernel build failed with commit 41e83b9: fix "netfilter: > > xt_bpf: Fix XT_BPF_MODE_FD_PINNED > > &

[linux-next][41e83b9][gcc 4.8.5] make modules fail at net/netfilter/xt_bpf.ko

2017-12-05 Thread Abdul Haleem
netfilter/xt_bpf.ko] undefined! Kernel built fine when bad commit is reverted. -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.10.0-rc5 Kernel Configuration # CONFIG_PPC64=y # # Processor support # CONFIG_PPC_BOOK3S_64=

[mainline][ppc] sysfs: cannot create duplicate filename '/devices/hv_24x7/events/PM_CAPP1_APC_UOP_SEND_PB_CMD'

2017-10-30 Thread Abdul Haleem
ported on 4.11.0 https://lkml.org/lkml/2017/3/7/763 -- Regard's Abdul Haleem IBM Linux Technology Centre

[linux-next][DLPAR CPU][Oops] Kernel crash with CPU hotunplug

2017-10-04 Thread Abdul Haleem
ys/devices/system/cpu/cpu2 thread: 3: /sys/devices/system/cpu/cpu3 thread: 4: /sys/devices/system/cpu/cpu4 thread: 5: /sys/devices/system/cpu/cpu5 thread: 6: /sys/devices/system/cpu/cpu6 thread: 7: /sys/devices/system/cpu/cpu7 Done. Probing cpu 0x1008 Kernel panics after ab

[linux-next][DLPAR] kernel BUG at arch/powerpc/lib/locks.c:34!

2017-09-28 Thread Abdul Haleem
353f7a1a73 ]--- Kernel panic - not syncing: Fatal exception Dumping ftrace buffer: (ftrace buffer empty) Rebooting in 10 seconds.. Test script to recreate : https://github.com/avocado-framework-tests/avocado-misc-tests/blob/master/memory/memhotplug.py $ avocado run memhotplug.py --show-job-lo

Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer

2017-09-22 Thread Abdul Haleem
On Fri, 2017-09-22 at 15:27 +0530, Abdul Haleem wrote: > On Wed, 2017-09-20 at 21:42 +1000, Michael Ellerman wrote: > > Abdul Haleem writes: > > > > > Hi, > > > > > > Dynamic CPU remove operation resulted in Kernel Panic on today's > > >

Re: [linux-next][EXT4][Oops]kernel panics when running fsfuzzer

2017-09-22 Thread Abdul Haleem
On Wed, 2017-09-20 at 16:44 +1000, Michael Ellerman wrote: > Abdul Haleem writes: > > > Hi, > > > > next kernel panics when running fsfuzzer test on ext4 file system. > > > > Machine Type: Power 7 PowerVM LPAR > > kernel : 4.13.0-next-2017091

Re: [1/2] powerpc/pseries: fix "OF: ERROR: Bad of_node_put() on /cpus" during DLPAR

2017-09-22 Thread Abdul Haleem
+0xa8/0x1a0 > > [c0026ecdfe30] [c15eb8e0] system_call+0x58/0x6c > > > > Fix the issue by removing the of_node_put(parent) call from > > dlpar_attach_node(), and ensuring that the reference to the parent node > > is properly held and released by the caller d

Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer

2017-09-22 Thread Abdul Haleem
On Wed, 2017-09-20 at 21:42 +1000, Michael Ellerman wrote: > Abdul Haleem writes: > > > Hi, > > > > Dynamic CPU remove operation resulted in Kernel Panic on today's > > next-20170915 kernel. > > > > Machine Type: Power 7 PowerVM LPAR > >

Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer

2017-09-19 Thread Abdul Haleem
On Mon, 2017-09-18 at 07:44 -0500, Rob Herring wrote: > On Mon, Sep 18, 2017 at 5:08 AM, Abdul Haleem > wrote: > > Hi, > > > > Dynamic CPU remove operation resulted in Kernel Panic on today's > > next-20170915 kernel. > > > > Machine Type: Power 7

Re: [mainline][DLPAR][Oops] OF: ERROR: Bad of_node_put() on /cpus

2017-09-19 Thread Abdul Haleem
.12 work or when was it last working? I'm not seeing anything > recent in the DT code that looks suspicious. The issue was not seen with 4.12.0 -- Regard's Abdul Haleem IBM Linux Technology Centre

[linux-next][XFS][trinity] WARNING: CPU: 32 PID: 31369 at fs/iomap.c:993

2017-09-18 Thread Abdul Haleem
00> 4bfffdb0 ---[ end trace bd674540a2bf235b ]--- -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.10.0-rc5 Kernel Configuration # CONFIG_PPC64=y # # Processor support # CONFIG_PPC_BOOK3S_64=y # CO

[linux-next][DLPAR CPU][Oops] Bad kernel stack pointer

2017-09-18 Thread Abdul Haleem
--[ end trace d504e921bec4201a ]--- -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.10.0-rc5 Kernel Configuration # CONFIG_PPC64=y # # Processor support # CONFIG_PPC_BOOK3S_64=y # CONFIG_PPC_BOOK3E_64 is not set CONFIG_GENERIC_CPU=y

[mainline][bisected 36ae3c0] Build fail at virt/kvm/eventfd.c:568

2017-09-16 Thread Abdul Haleem
>gsi >= KVM_MAX_IRQ_ROUTES) + return -EINVAL; if (args->flags & KVM_IRQFD_FLAG_DEASSIGN) return kvm_irqfd_deassign(kvm, args); -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc

Re: [PATCH 0/2] Allow scsi_prep_fn to occur for retried commands

2017-08-21 Thread Abdul Haleem
ime [PATCH 2/2] scsi: Preserve retry counter through scsi_prep_fn Reported-and-Tested-by: Abdul Haleem -- Regard's Abdul Haleem IBM Linux Technology Centre

Re: [linux-next][bisected c64e09ce] sysctl command hung indefinitely

2017-08-21 Thread Abdul Haleem
On Mon, 2017-08-21 at 09:50 +0200, Michal Hocko wrote: > On Sat 19-08-17 15:49:31, Abdul Haleem wrote: > > Hi Michal, > > > > 'sysctl -a' command never completes on my PowerPC machine with latest > > next kernel (As of next-20170811) > > > > Ma

[linux-next][bisected c64e09ce] sysctl command hung indefinitely

2017-08-19 Thread Abdul Haleem
r", - .data = &numa_zonelist_order, - .maxlen = NUMA_ZONELIST_ORDER_LEN, .mode = 0644, .proc_handler = numa_zonelist_order_handler, }, does the above change has caused the noise ? -- Regard's Abdul Haleem IBM Linux Technology Centre

Re: WARNING: CPU: 15 PID: 0 at block/blk-mq.c:1111 __blk_mq_run_hw_queue+0x1d8/0x1f0

2017-08-17 Thread Abdul Haleem
On Thu, 2017-08-17 at 14:18 -0500, Brian King wrote: > On 08/17/2017 10:32 AM, Bart Van Assche wrote: > > On Wed, 2017-08-16 at 15:10 -0500, Brian King wrote: > >> On 08/16/2017 01:15 PM, Bart Van Assche wrote: > >>> On Wed, 2017-08-16 at 23:37 +0530, Abdul Haleem w

WARNING: CPU: 15 PID: 0 at block/blk-mq.c:1111 __blk_mq_run_hw_queue+0x1d8/0x1f0

2017-08-16 Thread Abdul Haleem
tch bad users up front. Signed-off-by: Jens Axboe -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.13.0-rc2 Kernel Configuration # CONFIG_PPC64=y # # Processor support # CONFIG_PPC_BOOK3S_64=y # CONFIG_PPC_

[BUG][bisected 270065e] linux-next fails to boot on powerpc

2017-08-16 Thread Abdul Haleem
: Damien Le Moal Reviewed-by: Christoph Hellwig Reviewed-by: Johannes Thumshirn Signed-off-by: Martin K. Petersen -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.13.0-rc2 Kernel Configuration #

Re: [linux-next] cpus stalls detected few hours after booting next kernel

2017-07-24 Thread Abdul Haleem
On Fri, 2017-06-30 at 17:28 +1000, Nicholas Piggin wrote: > On Fri, 30 Jun 2017 10:52:18 +0530 > Abdul Haleem wrote: > > > On Fri, 2017-06-30 at 00:45 +1000, Nicholas Piggin wrote: > > > On Thu, 29 Jun 2017 20:23:05 +1000 > > > Nicholas Piggin wrote: > >

Re: [linux-next][bisected 1c0eaf0f] Today's next kernel fails to boot on ppc bare-metal

2017-07-16 Thread Abdul Haleem
On Mon, 2017-07-17 at 12:10 +1000, Michael Ellerman wrote: > Hi Abdul, > > Thanks for the bug report. > > Abdul Haleem writes: > > Hi > > > > Today's linux-next fails to boot on ppc bare-metal > > > > Test: Boot > > Machine: Power 8 bare

[linux-next][bisected 1c0eaf0f] Today's next kernel fails to boot on ppc bare-metal

2017-07-14 Thread Abdul Haleem
IAMR/AMOR git bisect good 1e2a516e89fc412a754327522ab271b42f99c6b4 # first bad commit: [1c0eaf0f56d6128af7f0f252855173fcee85d202] powerpc/powernv: Tell OPAL about our MMU mode on POWER9 -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDI

[BUG][cramfs] Kernel Oops while fuzz testing cramfs on mainline kernel

2017-07-13 Thread Abdul Haleem
ion fault ./fstest $DIR New tests failed aborting Message from syslogd@ltc at Jul 13 11:16:09 ... kernel:Dumping ftrace buffer: Message from syslogd@ltc at Jul 13 11:16:09 ... kernel: (ftrace buffer empty) -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically gene

[mainline][ext2] fsfuzzer triggered WARNING: CPU: 1 PID: 72688 at fs/super.c:1244 mount_fs+0x200/0x220

2017-07-13 Thread Abdul Haleem
t;negative value (%lld)\n", type->name, sb->s_maxbytes); up_write(&sb->s_umount); free_secdata(secdata); return root; -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.10.0-rc2 Kernel Configuration

Re: Today's linux-next build fail on powerpc

2017-07-10 Thread Abdul Haleem
On Mon, 2017-07-10 at 18:17 +0300, Andy Shevchenko wrote: > On Mon, Jul 10, 2017 at 5:37 PM, Abdul Haleem > wrote: > > On Fri, 2017-07-07 at 19:36 +0300, Andy Shevchenko wrote: > >> On Thu, Jul 6, 2017 at 9:00 AM, Abdul Haleem > >> wrote: > >> > next-201

Re: Today's linux-next build fail on powerpc

2017-07-10 Thread Abdul Haleem
On Fri, 2017-07-07 at 19:36 +0300, Andy Shevchenko wrote: > On Thu, Jul 6, 2017 at 9:00 AM, Abdul Haleem > wrote: > > Hi Luis, > > > > next-20170705 fails to build on powerpc with below errors. > > Hi, > > I had sent a fix yesterday. Had you chance to test

Re: [linux-next] cpus stalls detected few hours after booting next kernel

2017-07-07 Thread Abdul Haleem
On Fri, 2017-06-30 at 17:28 +1000, Nicholas Piggin wrote: > On Fri, 30 Jun 2017 10:52:18 +0530 > Abdul Haleem wrote: > > > On Fri, 2017-06-30 at 00:45 +1000, Nicholas Piggin wrote: > > > On Thu, 29 Jun 2017 20:23:05 +1000 > > > Nicholas Piggin wrote: > >

Re: [next-20170609] Oops while running CPU off-on (cpuset.c/cpuset_can_attach)

2017-07-06 Thread Abdul Haleem
The problem was reproducible all the time. With the patch fix, I tried multiple times and long runs of cpu off-on cycles but no Oops is seen. Thank you for spending your valuable time on fixing this issue. Reported-and-tested-by : Abdul Haleem > to confirm the fix by seeing whether it no longer tr

Re: [linux-next] cpus stalls detected few hours after booting next kernel

2017-07-04 Thread Abdul Haleem
On Fri, 2017-06-30 at 17:28 +1000, Nicholas Piggin wrote: > On Fri, 30 Jun 2017 10:52:18 +0530 > Abdul Haleem wrote: > > > On Fri, 2017-06-30 at 00:45 +1000, Nicholas Piggin wrote: > > > On Thu, 29 Jun 2017 20:23:05 +1000 > > > Nicholas Piggin wrote: > >

Re: [next-20170609] Oops while running CPU off-on (cpuset.c/cpuset_can_attach)

2017-07-03 Thread Abdul Haleem
On Tue, 2017-06-27 at 11:36 -0400, Tejun Heo wrote: > Hello, Abdul. > > Sorry about the long delay. > > On Mon, Jun 12, 2017 at 04:53:42PM +0530, Abdul Haleem wrote: > > linux-next kernel crashed while running CPU offline and online. > > > > Machine: Power 8

[selftest/powerpc] mainline kernel panics with tm/tm-signal-context-chk-vsx.c tests

2017-07-02 Thread Abdul Haleem
4c24> 4800 e8610178 88ed01db ---[ end trace a62498af9ec43680 ]--- Kernel panic - not syncing: Fatal exception Dumping ftrace buffer: (ftrace buffer empty) Rebooting in 10 seconds.. -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO N

[linux-next] SMT off triggers WARNING: CPU: 1 PID: 13 at arch/powerpc/kernel/watchdog.c:314 stop_wd_on_cpu+0x54/0xf0

2017-07-02 Thread Abdul Haleem
806be 79291f24 f8010010 f821ffc1 7fca4a14 7cea482a 7ce94436 792a07e1 40820030 <0fe0> 38210040 3860 e8010010 ---[ end trace bc1cf8bfb9c5be6e ]--- -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.10.0-rc2 Ker

Re: [linux-next] cpus stalls detected few hours after booting next kernel

2017-06-29 Thread Abdul Haleem
20/0x200 [ > > 5948.373313] \ > > [c00f1c1ebd90] [c02e2c48] vfs_write+0xc8/0x240 [ 5948.373371] \ > > [c00f1c1ebde0] [c02e4940] SyS_write+0x60/0x110 [ 5948.373430] \ > > [c00f1c1ebe30] [c000b8e0] system_call+0x38/0xdc [ 5948.373486] \ >

[linux-next][489e45][PowerPC] build broke on bare-metal with gcc 4.8.5

2017-06-22 Thread Abdul Haleem
/qede_dcbnl.c b/drivers/net/ethernet/qlogic/qede/qede_dcbnl.c new file mode 100644 index 000..03e8c02 --- /dev/null +++ b/drivers/net/ethernet/qlogic/qede/qede_dcbnl.c -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.9.

[BUG][next-20170619][347de24] PowerPC boot fails with Oops

2017-06-20 Thread Abdul Haleem
ed with crng_init=0 ---[ end trace 9756c1a885c69f33 ]--- -- Regard's Abdul Haleem IBM Linux Technology Centre kernel:kexec: Starting new kernel [ 205.035822] kexec: waiting for cpu 48 (physical 168) to enter 1 state [ 205.035955] kexec: waiting for cpu 0 (physical 32) to enter OPAL [ 205.03

Re: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

2017-06-15 Thread Abdul Haleem
On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote: > Hi, > > linux-next fails to boot on powerpc Bare-metal with these warnings. > > machine booted fine on next-20170613 Thanks Michael, Yes it is (75fe04e59 of: remove *phandle properties from expanded device tree) Frank, w

[Oops][next-20170614] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

2017-06-14 Thread Abdul Haleem
he idle task! Rebooting in 10 seconds.. -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.10.0-rc2 Kernel Configuration # CONFIG_PPC64=y # # Processor support # CONFIG_PPC_BOOK3S_64=y # CONFIG_PPC_BOOK3E_64 is not

[next-20170609] WARNING: CPU: 3 PID: 71167 at lib/idr.c:157 idr_replace

2017-06-12 Thread Abdul Haleem
tem_call+0x38/0xe0 Instruction dump: 38210050 7f83e378 e8010010 eb81ffe0 eba1ffe8 ebc1fff0 ebe1fff8 7c0803a6 4e800020 0fe0 3860ffea 4b94 <0fe0> 3860ffea 4b88 6042 ---[ end trace 5158244f52496ab9 ]--- _exception: 47 callbacks suppressed -- Regard's Abdul Halee

Re: [BUG][next-20170606][bisected 411fe24e6b] WARNING: CPU: 10 PID: 0 at kernel/time/tick-sched.c:791

2017-06-12 Thread Abdul Haleem
On Fri, 2017-06-09 at 15:09 +0200, Frederic Weisbecker wrote: > On Wed, Jun 07, 2017 at 12:56:53PM +0530, Abdul Haleem wrote: > > Hi, > > > > Test: Trinity (https://github.com/kernelslacker/trinity) > > Machine : Power 8 PowerVM LPAR > > Kernel : 4.12.0-rc4-next

WARNING: CPU: 2 PID: 7 at kernel/workqueue.c:2041 process_one_work

2017-05-30 Thread Abdul Haleem
d (-12), clearing slot 32 ptm ptm753: ldisc open failed (-12), clearing slot 753 stress-ng source : https://github.com/ColinIanKing/stress-ng -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.10.0-rc2 Kernel Configurati

Re: [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx

2017-05-25 Thread Abdul Haleem
On Wed, 2017-05-24 at 21:50 +1000, Michael Ellerman wrote: > Abdul Haleem writes: > > Hi Cyril, > > > > I see a similar trace, but with 'tm-signal-stack' test for mainline > > kernel 4.12.0-rc1 on PowerVM LPAR. > > I can't reproduce this here. It

[BUG][next-20170523][Bisected cf22cd5f3a] kernel oops while running trinity fuzzer

2017-05-24 Thread Abdul Haleem
f886 f8860008 f8860010 f8860018 38c60020 409e0010 f886 f8860008 38c60010 409f000c 38c60008 2c05 7cb01120 ---[ end trace c454dcc1309b8479 ]--- -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.11.0-rc7 K

Re: [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx

2017-05-22 Thread Abdul Haleem
On Mon, 2017-04-03 at 14:33 +0530, Abdul Haleem wrote: > On Mon, 2017-04-03 at 14:28 +0530, Abdul Haleem wrote: > > On Tue, 2017-03-28 at 21:00 +1100, Michael Ellerman wrote: > > > Abdul Haleem writes: > > > > > > > Hi, > > > > > > &

Re: Mainline build brakes on powerpc with error : fs/xfs/xfs_iomap.c:1152: undefined reference to `.put_dax

2017-05-18 Thread Abdul Haleem
On Tue, 2017-05-16 at 13:17 +0200, Arnd Bergmann wrote: > On Tue, May 16, 2017 at 1:02 PM, Abdul Haleem > wrote: > > Hi, > > > > Today's mainline 4.12-rc1 fails to build for the attached configuration > > file on Power7 box with below errors. > >

Mainline build brakes on powerpc with error : fs/xfs/xfs_iomap.c:1152: undefined reference to `.put_dax

2017-05-16 Thread Abdul Haleem
_begin': fs/xfs/xfs_iomap.c:1071: undefined reference to `.dax_get_by_host' Also reproducible on latest linux-next, and the last successful build was at next-20170510. -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4

Re: [linux-next][bock] [bisected c20cfc27a] WARNING: CPU: 22 PID: 0 at block/blk-core.c:2655 .blk_update_request+0x4f8/0x500

2017-05-11 Thread Abdul Haleem
atch. Thanks for all your support ! Reported-and-tested-by : Abdul Haleem > > --- > diff --git a/block/blk-core.c b/block/blk-core.c > index c580b0138a7f..c7068520794b 100644 > --- a/block/blk-core.c > +++ b/block/blk-core.c > @@ -2644,8 +2644,6 @@ bool blk_update_request(s

Re: [linux-next][bock] [bisected c20cfc27a] WARNING: CPU: 22 PID: 0 at block/blk-core.c:2655 .blk_update_request+0x4f8/0x500

2017-05-10 Thread Abdul Haleem
On Wed, 2017-05-10 at 09:56 +0200, Christoph Hellwig wrote: > On Tue, May 09, 2017 at 08:48:21PM +0530, Abdul Haleem wrote: > > A bisection for the above suspects resulted a bad commit; > > > > c20cfc27a47307e811346f85959cf3cc07ae42f9 is the first

Re: [linux-next][bock] [bisected c20cfc27a] WARNING: CPU: 22 PID: 0 at block/blk-core.c:2655 .blk_update_request+0x4f8/0x500

2017-05-09 Thread Abdul Haleem
On Mon, 2017-05-08 at 08:00 -0600, Jens Axboe wrote: > On 05/08/2017 01:13 AM, Abdul Haleem wrote: > > On Fri, 2017-05-05 at 08:02 -0600, Jens Axboe wrote: > >> On 05/05/2017 12:25 AM, Abdul Haleem wrote: > >>> Hi, > >>> > >>> 4.11.0 Linus ma

Re: [linux-next][bock] WARNING: CPU: 22 PID: 0 at block/blk-core.c:2655 .blk_update_request+0x4f8/0x500

2017-05-08 Thread Abdul Haleem
On Fri, 2017-05-05 at 08:02 -0600, Jens Axboe wrote: > On 05/05/2017 12:25 AM, Abdul Haleem wrote: > > Hi, > > > > 4.11.0 Linus mainline booted with Warnings on PowerPC. > > > > We did not see this on next-20170407 but on next-20170410 and later. > > Hav

[linux-next][bock] WARNING: CPU: 22 PID: 0 at block/blk-core.c:2655 .blk_update_request+0x4f8/0x500

2017-05-04 Thread Abdul Haleem
atcher Service... Started Network Manager Script Dispatcher Service -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.10.0-rc5 Kernel Configuration # CONFIG_PPC64=y # # Processor support # CONFIG_PPC_BOOK3S_64=y # CONFIG_PP

Re: [linux-next][bisected 1945bc45] build brakes for PowerPC BE configuration on LPAR

2017-05-04 Thread Abdul Haleem
On Thu, 2017-05-04 at 20:41 +1000, Nicholas Piggin wrote: > On Thu, 04 May 2017 14:54:19 +0530 > Abdul Haleem wrote: > > > Hi, > > > > linux-next build fails on BE config with next-20170424 onwards > > > > the patch https://lkml.org/lkml/2017/4/20/994 f

Re: [linux-next][bisected 1945bc45] build brakes for PowerPC BE configuration on LPAR

2017-05-04 Thread Abdul Haleem
On Thu, 2017-05-04 at 20:29 +1000, Michael Ellerman wrote: > Abdul Haleem writes: > > > Hi, > > > > linux-next build fails on BE config with next-20170424 onwards > > > > the patch https://lkml.org/lkml/2017/4/20/994 fixes a similar issue > > with kvm

[linux-next][bisected 1945bc45] build brakes for PowerPC BE configuration on LPAR

2017-05-04 Thread Abdul Haleem
--- arch/powerpc/kernel/idle_book3s.S| 25 + 3 files changed, 70 insertions(+), 35 deletions(-) the BE configuration file is attached. -- Regard's Abdul Haleem IBM Linux Technology C

Re: [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx

2017-04-03 Thread Abdul Haleem
On Mon, 2017-04-03 at 14:28 +0530, Abdul Haleem wrote: > On Tue, 2017-03-28 at 21:00 +1100, Michael Ellerman wrote: > > Abdul Haleem writes: > > > > > Hi, > > > > > > While running kernel self tests on ppc64, tm/tm-signal-context-chk-vsx > > >

Re: [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx

2017-04-03 Thread Abdul Haleem
On Tue, 2017-03-28 at 21:00 +1100, Michael Ellerman wrote: > Abdul Haleem writes: > > > Hi, > > > > While running kernel self tests on ppc64, tm/tm-signal-context-chk-vsx > > tests fails with Oops message. > > > > I was able to reproduce only twice ou

Re: 4.11.0-rc1 boot resulted in WARNING: CPU: 14 PID: 1722 at fs/sysfs/dir.c:31 .sysfs_warn_dup+0x78/0xb0

2017-03-13 Thread Abdul Haleem
On Sat, 2017-03-11 at 15:46 -0700, Jens Axboe wrote: > On 03/09/2017 05:59 AM, Brian Foster wrote: > > cc linux-block > > > > On Thu, Mar 09, 2017 at 04:20:06PM +0530, Abdul Haleem wrote: > >> On Wed, 2017-03-08 at 08:17 -0500, Brian Foster wrote: > >>>

Re: [BUG] [PowerPC] Kernel Oops when booting Linux mainline

2017-03-13 Thread Abdul Haleem
On Mon, 2017-03-13 at 14:48 +0530, Abdul Haleem wrote: > Hi, > > Mainline boot is broken on PowerPC bare metal with below traces: > Machine Type : Power 8 Bare metal > > [ OK ] Mounted Debug File System. > [ OK ] Started Nameserver information manager. > [ OK ] Star

[BUG] [PowerPC] Kernel Oops when booting Linux mainline

2017-03-13 Thread Abdul Haleem
hed. FYI, Good commit of last successful boot is : commit ea6200e84182989a3cce9687cf79a23ac44ec4db Merge: b4fb8f6 fc69910 Author: Linus Torvalds Date: Wed Mar 8 14:45:31 2017 -0800 Merge branch 'core-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

Today's mainline failed to boot on Power 6 with WARNING: CPU: 8 PID: 0 at kernel/sched/sched.h

2017-03-12 Thread Abdul Haleem
0addef 4872bd25 6000 <0fe0> 4bfff280 5540d97e 794a06e0 ---[ end trace f610c7e162cdd3b8 ]--- Unable to handle kernel paging request for data at address 0x2c2341820054 Faulting instruction address: 0xc01076e0 Oops: Kernel access of bad area, sig: 11 [#1] -- Regard's

Re: 4.11.0-rc1 boot resulted in WARNING: CPU: 14 PID: 1722 at fs/sysfs/dir.c:31 .sysfs_warn_dup+0x78/0xb0

2017-03-09 Thread Abdul Haleem
On Wed, 2017-03-08 at 08:17 -0500, Brian Foster wrote: > On Tue, Mar 07, 2017 at 10:01:04PM +0530, Abdul Haleem wrote: > > > > Hi, > > > > Today's mainline (4.11.0-rc1) booted with warnings on Power7 LPAR. > > > > Issue is not reproducible all the t

[libhugetlbfs] linkhuge_rw fails with gcc 6.2.0 on 4.11.0-rc1 ppc64le

2017-03-09 Thread Abdul Haleem
owerpc64le-linux-gnu/ld-2.24.so 3fffe31c-3fffe31f rw-p 00:00 0 [stack] -- Regard's Abdul Haleem IBM Linux Technology Centre

4.11.0-rc1 boot resulted in WARNING: CPU: 14 PID: 1722 at fs/sysfs/dir.c:31 .sysfs_warn_dup+0x78/0xb0

2017-03-07 Thread Abdul Haleem
b01 6000 ---[ end trace 78f08bafbc2388f3 ]--- kobject_add_internal failed for sda with -EEXIST, don't try to register things with the same name in the same directory. -- Regard's Abdul Haleem IBM Linux Technology Centre

[next-20170306] Memory off-on resulted in Oops on Power 6 system

2017-03-06 Thread Abdul Haleem
8ac202 2fa9 419e000c 794a2428 7d295214 3d020004 78840620 81487564 7c845436 5484103a 7c8807b4 548406ba ---[ end trace 911354ae3120f308 ]--- -- Regard's Abdul Haleem IBM Linux Technology Centre

Re: next-20170220 failed to build on PowerPC

2017-02-20 Thread Abdul Haleem
ngo Molnar Regard's Abdul Haleem IBM Linux Technology Center.

Re: Kernel Oops on 4.8.0-rc8 while running trinity tests

2016-09-26 Thread Abdul Haleem
7d081b78 796b0020 <7d49402a> 7c694214 2eaa f941ffd0 ---[ end trace f4f25c6801290199 ]--- On Friday 26 August 2016 12:02 PM, Abdul Haleem wrote: Hi, Trinity tests failed on mainline4.8.0-rc3with the following error message: Machine Type : PowerPC Bare Metal & also reproducible on Po

Re: [PowerPC] today's main line failed to build on PowerPC

2016-08-18 Thread Abdul Haleem
On Thursday18 August 2016 11:50 AM, Abdul Haleem wrote: Hi, The main line stable 4.8.0-rc2 failed to build on PowerPC with following build errors. config : pseries_le_defconfig Machine Type : PowerPC Bare Metal My mistake, The build is failing on the attached config and not for

[PowerPC] today's main line failed to build on PowerPC

2016-08-17 Thread Abdul Haleem
Hi, The main line stable 4.8.0-rc2 failed to build on PowerPC with following build errors. config : pseries_le_defconfig Machine Type : PowerPC Bare Metal 09:34:22 00:04:59 INFO | make -j 160 vmlinux 09:34:24 00:05:01 ERROR| [stderr] arch/powerpc/mm/hash_low_32.S: Assembler messages: 09:34:

[PowerPC] Kernel OOPS while compiling LTP test suite on linus mainline

2016-07-27 Thread Abdul Haleem
Hi, Kernel OOPS messages were seen while compiling linux test project (LTP) source on 4.7.0-rc5 mainline. Kernel config : pseries_le_defconfig Machine Type : PowerVM LPAR Machine hardware : LPAR uses 16 vCPUs, and 29G memory trace messages: *15:34:57* [ 862.548866] Unable to handle kernel pa

Re: [PATCH 2/2] workqueue:Fix affinity of an unbound worker of a node with 1 online CPU

2016-06-07 Thread Abdul Haleem
hen it comes online. b) the cpumask of the worker pool when the second CPU in the pool's cpumask comes online. Reported-by: Abdul Haleem Cc: Peter Zijlstra Cc: Thomas Gleixner Cc: Tejun Heo Cc: Michael Ellerman Signed-off-by: Gautham R. Shenoy ---