Re: [next-20230317][PPC/MLX5][bisected 4d5ab0a] Boot WARNING: CPU: 0 PID: 9 at net/core/dev.c:1928 call_netdevice_notifiers_info

2023-03-22 Thread Abdul Haleem
: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/net/core/xdp.c?id=769639c1fe8a98129aa97c8ee981639db1e8955c Thanks Lorenzo, Verified the patch and it fixes the problem and next-20230321 kernel boots fine on my powerpc lpar Tested-by: Abdul Haleem -- Regard's Abdul Haleem

[next-20230317][PPC/MLX5][bisected 4d5ab0a] Boot WARNING: CPU: 0 PID: 9 at net/core/dev.c:1928 call_netdevice_notifiers_info

2023-03-20 Thread Abdul Haleem
409eff9c 3921 3c82fff1 3c62fff1 3d42017d 38a00788 3884b3c8 3863b3d8 992a2141 4b68a969 6000 <0fe0> 6000 3c4c0070 38422900 -- Regard's Abdul Haleem IBM Linux Technology Center

[5.17.0-rc6][DLPAR][SRIOV/mlx5]EEH errors and WARNING: CPU: 7 PID: 30505 at include/rdma/ib_verbs.h:3688 mlx5_ib_dev_res_cleanup

2022-03-07 Thread Abdul Haleem
k_diag bonding rfkill rpcrdma sunrpc rdma_ucm ib_srpt ib_isert iscsi_target_mod target_core_mod ib_iser ib_umad rdma_cm ib_ipoib iw_cm ib_cm li -- Regard's Abdul Haleem IBM Linux Technology Center

Re: [next-20220225] powerpc boot broken with maple tree code ?

2022-03-03 Thread Abdul Haleem
On 3/2/22 8:22 PM, Liam Howlett wrote: * Abdul Haleem [220302 01:22]: Greeting's linux-next kernel 5.17.0-rc5-next-20220225 boot is broken on powerpc Is this due to Introduction of maple patch series ? It could be - those are certainly maple tree functions. I do have a ppc64le VM booting

[next-20220225][Oops][ppc] lvm snapshot merge results kernel panics (throtl_pending_timer_fn)

2022-03-02 Thread Abdul Haleem
f821ffe1  3921 992d0932 3920 3941 <7c801829> 7c044800 40c20010 7d40192d  ---[ end trace ]--- -- Regard's Abdul Haleem IBM Linux Technology Center

[linux-next] 5.17.0-rc1-next-20220124 kernel fails to boot on my powerpc box

2022-01-25 Thread Abdul Haleem
ad+0x5c/0x64 call traces never ends and could not login -- Regard's Abdul Haleem IBM Linux Technology Center

[5.16.0-rc5][ppc][net] kernel oops when hotplug remove of vNIC interface

2022-01-05 Thread Abdul Haleem
        unsigned long val, new; 6964 6965        do { 6966            val = READ_ONCE(n->state); 6967            BUG_ON(!test_bit(NAPI_STATE_SCHED, )); 6968 6969            new = val & ~(NAPIF_STATE_SCHED | NAPIF_STATE_NPSVC); 6970            if (n->dev->threaded && n->thread) -- Re

[next-20211019][PPC] kernel panics with lspci -vvnn command

2021-10-21 Thread Abdul Haleem
c Corp. ISP2722-based 16/32Gb Fibre Channel to PCIe Adapter [1077:2261] (rev 01) Problem is not seen with 5.15.0-rc4-next-20211005 -- Regard's Abdul Haleem IBM Linux Technology Center

Re: [next-20210827][ppc][multipathd] INFO: task hung in dm_table_add_target

2021-09-28 Thread Abdul Haleem
On 9/1/21 7:06 PM, Christoph Hellwig wrote: On Wed, Sep 01, 2021 at 04:47:26PM +0530, Abdul Haleem wrote: Greeting's multiple task hung while adding the vfc disk back to the multipath on my powerpc box running linux-next kernel Can you retry to reproduce this with lockdep enabled to see

[5.15-rc1][PPC/PCI] IPR adapter reset threw EEH and fail to recover while booting mainline on powerpc

2021-09-19 Thread Abdul Haleem
0cfd4] ret_from_kernel_thread+0x5c/0x64 INFO: task systemd-udevd:473 blocked for more than 122 seconds.   Not tainted 5.15.0-rc1-autotest #3 -- Regard's Abdul Haleem IBM Linux Technology Center OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 5.15.0-rc1-autotest (root@ltcd

[next-20210827][ppc][multipathd] INFO: task hung in dm_table_add_target

2021-09-01 Thread Abdul Haleem
ze=30G features='1 queue_if_no_path' hwhandler='0' wp=rw $ -- Regard's Abdul Haleem IBM Linux Technology Center

Re: [next-20210820][ppc][nvme/raid] pci unbind WARNS at fs/kernfs/dir.c:1524 kernfs_remove_by_name_ns+

2021-09-01 Thread Abdul Haleem
Thanks Christoph, The problem is fixed with below commit and tested on next-20210823 Tested-by: Abdul Haleem On 8/26/21 10:00 PM, Christoph Hellwig wrote: Are you sure this is the very latest linux-next? This should hav been fixed by: "block: add back the bd_holder_dir refe

[next-20210820][ppc][nvme/raid] pci unbind WARNS at fs/kernfs/dir.c:1524 kernfs_remove_by_name_ns+

2021-08-26 Thread Abdul Haleem
Regard's Abdul Haleem IBM Linux Technology Center

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

2020-06-04 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/mainline][bisected 3acac06][ppc] Oops when unloading mpt3sas driver

2020-03-20 Thread Abdul Haleem
On Tue, 2020-02-25 at 12:23 +0530, Sreekanth Reddy wrote: > On Tue, Feb 25, 2020 at 11:51 AM Abdul Haleem > wrote: > > > > On Fri, 2020-01-17 at 18:21 +0530, Abdul Haleem wrote: > > > On Thu, 2020-01-16 at 09:44 -0800, Christoph Hellwig wrote: > > > > Hi Abd

Re: [linux-next/mainline][bisected 3acac06][ppc] Oops when unloading mpt3sas driver

2020-02-24 Thread Abdul Haleem
On Fri, 2020-01-17 at 18:21 +0530, Abdul Haleem wrote: > On Thu, 2020-01-16 at 09:44 -0800, Christoph Hellwig wrote: > > Hi Abdul, > > > > I think the problem is that mpt3sas has some convoluted logic to do > > some DMA allocations with a 32-bit coherent mask, and then

Re: [linux-next/mainline][bisected 3acac06][ppc] Oops when unloading mpt3sas driver

2020-01-17 Thread Abdul Haleem
On Thu, 2020-01-16 at 09:44 -0800, Christoph Hellwig wrote: > Hi Abdul, > > I think the problem is that mpt3sas has some convoluted logic to do > some DMA allocations with a 32-bit coherent mask, and then switches > to a 63 or 64 bit mask, which is not supported by the DMA API. &

Re: [linux-next/mainline][bisected 3acac06][ppc] Oops when unloading mpt3sas driver

2020-01-13 Thread Abdul Haleem
On Thu, 2020-01-09 at 06:22 -0800, Christoph Hellwig wrote: > On Thu, Jan 09, 2020 at 02:27:25PM +0530, Abdul Haleem wrote: > > + CC Christoph Hellwig > > The only thing this commit changed for the dma coherent case (which > ppc64 uses) is that we now look up the page to free

Re: [linux-next/mainline][bisected 3acac06][ppc] Oops when unloading mpt3sas driver

2020-01-09 Thread Abdul Haleem
+ CC Christoph Hellwig On Wed, 2020-01-08 at 18:48 +0530, Abdul Haleem wrote: > Greeting's > > Kernel Oops on my powerpc system when unloading driver mpt3sas. > > Thanks Oliver for bisecting it to commit 3acac06 ("dma-mapping: merge > the generic remapping

[linux-next/mainline][bisected 3acac06][ppc] Oops when unloading mpt3sas driver

2020-01-08 Thread Abdul Haleem
079:18: Removing driver -- 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 not set # CONFIG_POWER

net-next branch fails to build on my P8 CI system

2019-11-11 Thread Abdul Haleem
c47cbd u64_stats: provide u64_stats_t type -- Regard's Abdul Haleem IBM Linux Technology Centre

Re: [mainline][BUG][PPC][btrfs][bisected 00801a] kernel BUG at fs/btrfs/locking.c:71!

2019-09-11 Thread Abdul Haleem
On Wed, 2019-09-11 at 11:09 +0300, Nikolay Borisov wrote: > > On 11.09.19 г. 11:00 ч., Abdul Haleem wrote: > > On Tue, 2019-09-03 at 13:39 +0300, Nikolay Borisov wrote: > >> > > > > >> corresponds to? > > > > btrfs_se

Re: [mainline][BUG][PPC][btrfs][bisected 00801a] kernel BUG at fs/btrfs/locking.c:71!

2019-09-11 Thread Abdul Haleem
On Tue, 2019-09-03 at 13:39 +0300, Nikolay Borisov wrote: > > On 3.09.19 г. 11:55 ч., Abdul Haleem wrote: > > Greeting's > > > > Mainline kernel panics with LTP/fs_fill-dir tests for btrfs file system on > > my P9 box running mainline kernel 5.3.0-rc5 > &

[mainline][BUG][PPC][btrfs][bisected 00801a] kernel BUG at fs/btrfs/locking.c:71!

2019-09-03 Thread Abdul Haleem
639d78 4bb4a121 6000 <0fe0> 4bfffe5c 6000 6000 ---[ end trace 7890aa8e373f5bfb ]--- Rebooting in 10 seconds.. !!! 01FT700� FCode, Copyright (c) 2000-2017 Emulex !!! Version 4.03a12 -- Regard's Abdul Haleem IBM Linux Technology Centre

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
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
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 > >>> > >>> Today

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_ON_ONCE()

Re: [PATCH net] net/ibmnvic: Fix deadlock problem in reset

2018-11-21 Thread Abdul Haleem
ock(>reset_lock); > + rtnl_unlock(); > device_remove_file(>dev, _attr_failover); > free_netdev(netdev); > dev_set_drvdata(>dev, NULL); > diff --git a/drivers/net/ethernet/ibm/ibmvnic.h > b/drivers/net/ethernet/ibm/ibmvnic.h > index 18103b8..99c4f8d 100644 > --- a/drivers/net/ethernet/ibm/ibmvnic.h > +++ b/drivers/net/ethernet/ibm/ibmvnic.h > @@ -1075,7 +1075,7 @@ struct ibmvnic_adapter { > struct tasklet_struct tasklet; > enum vnic_state state; > enum ibmvnic_reset_reason reset_reason; > - struct mutex reset_lock, rwi_lock; > + struct mutex rwi_lock; > struct list_head rwi_list; > struct work_struct ibmvnic_reset; > bool resetting; > Thanks for the fix, Please add Reported-and-tested-by: Abdul Haleem -- Regard's Abdul Haleem IBM Linux Technology Centre

Re: [mainline][ppc][bnx2x] watchdog: CPU 80 self-detected hard LOCKUP @ opal_interrupt+0x28/0x70 when module load/unload

2018-11-15 Thread Abdul Haleem
On Fri, 2018-11-16 at 15:44 +1100, Michael Ellerman wrote: > Abdul Haleem writes: > > On Thu, 2018-11-15 at 16:40 +0530, Abdul Haleem wrote: > >> On Mon, 2018-09-24 at 15:49 +0530, Abdul Haleem wrote: > >> > On Mon, 2018-09-24 at 19:35 +1000, Oliver wrote: > >&

Re: [PATCH] powerpc/64: Fix kernel stack 16-byte alignment

2018-11-15 Thread Abdul Haleem
t; unsigned long pa; > > + BUILD_BUG_ON(STACK_INT_FRAME_SIZE % 16); > + > pa = memblock_alloc_base_nid(THREAD_SIZE, THREAD_SIZE, limit, > early_cpu_to_node(cpu), MEMBLOCK_NONE); > if (!pa) { Tested-by: Abdul Haleem Thi

Re: [mainline][ppc][bnx2x] watchdog: CPU 80 self-detected hard LOCKUP @ opal_interrupt+0x28/0x70 when module load/unload

2018-11-15 Thread Abdul Haleem
On Thu, 2018-11-15 at 16:40 +0530, Abdul Haleem wrote: > On Mon, 2018-09-24 at 15:49 +0530, Abdul Haleem wrote: > > On Mon, 2018-09-24 at 19:35 +1000, Oliver wrote: > > > On Mon, Sep 24, 2018 at 6:56 PM, Abdul Haleem > > > wrote: > > > > Greeting's > &

Re: [mainline][ppc][bnx2x] watchdog: CPU 80 self-detected hard LOCKUP @ opal_interrupt+0x28/0x70 when module load/unload

2018-11-15 Thread Abdul Haleem
On Mon, 2018-09-24 at 15:49 +0530, Abdul Haleem wrote: > On Mon, 2018-09-24 at 19:35 +1000, Oliver wrote: > > On Mon, Sep 24, 2018 at 6:56 PM, Abdul Haleem > > wrote: > > > Greeting's > > > > > > bnx2x module load/unload test results in continuous hard L

[mainline][bisected 55469b][ppc] build error at drivers/net/ethernet/mellanox/mlx4/en_rx.c

2018-10-30 Thread Abdul Haleem
/en_rx.c: In function ‘get_fixed_ipv4_csum’: drivers/net/ethernet/mellanox/mlx4/en_rx.c:586:20: error: dereferencing pointer to incomplete type __u8 ipproto = iph->protocol; ^ Kernel builds fine when the patch is reverted. -- Regard's Abdul Haleem IBM Linux Technology Cen

Re: [PATCH] powerpc: Fix stack protector crashes on CPU hotplug

2018-10-22 Thread Abdul Haleem
; > -#ifdef CONFIG_STACKPROTECTOR > - paca_ptrs[cpu]->canary = idle->stack_canary; > -#endif > #endif > ti->cpu = cpu; > secondary_ti = current_set[cpu] = ti; > @@ -1316,6 +1310,8 @@ void start_secondary(void *unused) > notify_cpu_starting(cpu); > set_cpu_online(cpu, true); > > + boot_init_stack_canary(); > + > local_irq_enable(); > > /* We can enable ftrace for secondary cpus now */ Tested-by: Abdul Haleem -- Regard's Abdul Haleem IBM Linux Technology Centre

Re: [PATCH] powerpc/64: properly initialise the stackprotector canary on SMP.

2018-10-15 Thread Abdul Haleem
is patch properly initialises the stack_canary of the secondary > idle tasks. > > Reported-by: Abdul Haleem > Fixes: 06ec27aea9fc ("powerpc/64: add stack protector support") > Signed-off-by: Christophe Leroy > --- > arch/powerpc/kernel/smp.c | 8 > 1

Re: [BUG][linux-next][ppc] kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __schedule+0x978/0xa80

2018-10-12 Thread Abdul Haleem
On Fri, 2018-10-12 at 12:36 +0200, Christophe LEROY wrote: > > Le 12/10/2018 à 12:31, Abdul Haleem a écrit : > > On Fri, 2018-10-12 at 10:08 +0200, Christophe LEROY wrote: > >> > >> Le 12/10/2018 à 09:48, Abdul Haleem a écrit : > >>> On Fri, 201

Re: [BUG][linux-next][ppc] kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __schedule+0x978/0xa80

2018-10-12 Thread Abdul Haleem
On Fri, 2018-10-12 at 10:08 +0200, Christophe LEROY wrote: > > Le 12/10/2018 à 09:48, Abdul Haleem a écrit : > > On Fri, 2018-10-12 at 13:15 +0530, Abdul Haleem wrote: > >> Greeting's > >> > >> Today's linux-next fails to boot on powerpc bare-metal with

Re: [BUG][linux-next][ppc] kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __schedule+0x978/0xa80

2018-10-12 Thread Abdul Haleem
On Fri, 2018-10-12 at 13:15 +0530, Abdul Haleem wrote: > Greeting's > > Today's linux-next fails to boot on powerpc bare-metal with this error > > POWER8 performance monitor hardware support registered > rcu: Hierarchical SRCU implementation. > smp: Bringing up secondary CP

[BUG][linux-next][ppc] kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __schedule+0x978/0xa80

2018-10-12 Thread Abdul Haleem
] start_secondary+0x4d4/0x520 [c01fed5b3f90] [c000b370] start_secondary_prolog+0x10/0x14 Rebooting in 10 seconds.. Machine: Power 8 bare-metal kernel version: 4.19.0-rc7-next-20181010 gcc version: 4.8.5 20150623 config attach -- Regard's Abdul Haleem IBM Linux Technology Centre

Re: [linux-next][bisected e3fbcc7c] build error at drivers/pci/pcie/aer_inject.c:444:6: error: ‘struct pt_regs’ has no member named ‘ip

2018-10-09 Thread Abdul Haleem
On Tue, 2018-10-09 at 20:47 +1100, Michael Ellerman wrote: > Abdul Haleem writes: > > Greeting's > > > > Today's linux-next fails to build on ppc with below error > > > > drivers/pci/pcie/aer_inject.c: In function ‘aer_inject_ftrace_thunk’: > > drivers/pci/

Re: [mainline][ppc][bnx2x] watchdog: CPU 80 self-detected hard LOCKUP @ opal_interrupt+0x28/0x70 when module load/unload

2018-09-24 Thread Abdul Haleem
On Mon, 2018-09-24 at 19:35 +1000, Oliver wrote: > On Mon, Sep 24, 2018 at 6:56 PM, Abdul Haleem > wrote: > > Greeting's > > > > bnx2x module load/unload test results in continuous hard LOCKUP trace on > > my powerpc bare-metal running mainline 4.19.0-rc4 kernel &

[mainline][ppc][bnx2x] watchdog: CPU 80 self-detected hard LOCKUP @ opal_interrupt+0x28/0x70 when module load/unload

2018-09-24 Thread Abdul Haleem
:01:00.3: msix capability found bnx2x 0008:01:00.3: Using 64-bit DMA iommu bypass bnx2x 0008:01:00.3: part number 0-0-0-0 bnx2x 0008:01:00.3: 32.000 Gb/s available PCIe bandwidth (5 GT/s x8 link) bnx2x 0008:01:00.3 enP8p1s0f3: renamed from eth0 -- Regard's Abdul Haleem IBM Linux Technology Centre

[next-20180727][qla2xxx][BUG] WARNING: CPU: 12 PID: 511 at drivers/scsi/scsi_lib.c:691 scsi_end_request+0x250/0x280

2018-08-01 Thread Abdul Haleem
00 /dev/sdb [1:0:1:0]diskIBM 2145 /dev/sdd # lsscsi -H [0]ibmvscsi [1] qla2xxx -- Regard's Abdul Haleem IBM Linux Technology Centre

Re: [next-20180711][Oops] linux-next kernel boot is broken on powerpc

2018-07-17 Thread Abdul Haleem
On Sat, 2018-07-14 at 10:55 +1000, Stephen Rothwell wrote: > Hi Abdul, > > On Fri, 13 Jul 2018 14:43:11 +0530 Abdul Haleem > wrote: > > > > On Thu, 2018-07-12 at 13:44 -0400, Pavel Tatashin wrote: > > > > Related commit could be one of below ? I see lo

[next-20180713][NET] linux-next kernel panics when booting powerpc

2018-07-16 Thread Abdul Haleem
41003c 0b09 78290464 8149000c 394a0200 9149000c e90d0030 3ee2 eaf78008 7ee9bb78 <7ce9402e> 3b070001 571807fe 7ce7c214 ---[ end trace 7f524609ba19346b ]--- Kernel panic - not syncing: Fatal exception in interrupt -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatical

[4.18.0-rc4][bisected a063057d][mpt3sas] WARNING: CPU: 87 PID: 18868 at block/blk-core.c:781 blk_cleanup_queue+0x20c/0x220

2018-07-16 Thread Abdul Haleem
:0:4:0: [sde] Synchronizing SCSI cache -- Regard's Abdul Haleem IBM Linux Technology Centre

Re: [next-20180711][Oops] linux-next kernel boot is broken on powerpc

2018-07-13 Thread Abdul Haleem
tually ignore > > mempolicies for high priority allocations > > 088018f6fe571444caaeb16e84c9f24f22dfc8b0 mm: skip invalid pages block at a > > time in zero_resv_unresv() > > Looks like: > 0ba29a108979 mm/sparse: Remove CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER > > This patch

Re: [next-20180709][bisected 9cf57731][ppc] build fail with ld: BFD version 2.26.1-1.fc25 assertion fail elf64-ppc.c:14734

2018-07-09 Thread Abdul Haleem
On Mon, 2018-07-09 at 13:47 +0200, Peter Zijlstra wrote: > On Mon, Jul 09, 2018 at 03:21:23PM +0530, Abdul Haleem wrote: > > Greeting's > > > > Today's next fails to build on powerpc with below error > > > > kernel/cpu.o:(.data.rel+0x18e0): undefined reference t

Re: Oops in kmem_cache_free() via bioset_exit() (was Re: [next-20180601][nvme][ppc] Kernel Oops is triggered when creating lvm snapshots on nvme disks)

2018-07-03 Thread Abdul Haleem
On Fri, 2018-06-29 at 00:42 +1000, Michael Ellerman wrote: > Kent, Jens, > > This looks like it might be related to the recent bioset changes? > > cheers > > Abdul Haleem writes: > > On Tue, 2018-06-26 at 23:36 +1000, Michael Ellerman wrote: > >> Abdul

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

2018-06-28 Thread Abdul Haleem
On Tue, 2018-06-26 at 23:36 +1000, Michael Ellerman wrote: > Abdul Haleem writes: > > > Greeting's > > > > Kernel Oops is seen on 4.17.0-rc7-next-20180601 kernel on a bare-metal > > machine when running lvm snapshot tests on nvme disks. > > > > M

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

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

[4.18.0-rc1][i40e][9b10df59] WARNING: CPU: 32 PID: 95246 at drivers/net/ethernet/intel/i40e/i40e_ethtool.c:1907 i40e_update_ethtool_fdir_entry.isra.12+0x2264/0x2270

2018-06-21 Thread Abdul Haleem
bfffbe8 6042 3c4c0004 ---[ end trace 1a1b8331349cf7fd ]--- -- 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_BOOK

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

2018-05-29 Thread Abdul Haleem
reproduce it easily? I'm thinking maybe adding some > tracepoints that track decrementer settings and interrupts, and > nohz offload activity might show something up. Yes, the problem is reproducible consistently on our CI setup and today It triggered on 4.17.0-rc6 (mainline) too. -- Re

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

2018-05-21 Thread Abdul Haleem
db8 <4e800020> 7c781b78 48000395 480003ad @ tick_nohz_next_event+0x38/0x200 kernel:watchdog: CPU 96 TB:23470018682939, last heartbeat TB:23464816758804 (10160ms ago -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc

Re: [PATCH] crypto: reorder paes test lexicographically

2018-05-15 Thread Abdul Haleem
On Fri, 2018-05-11 at 09:04 +0100, Gilad Ben-Yossef wrote: > Due to a snafu "paes" testmgr tests were not ordered > lexicographically, which led to boot time warnings. > Reorder the tests as needed. > > Fixes: a794d8d ("crypto: ccree - enable support for hardwa

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 <abdha...@linux.vnet.ibm.com> > wrote: > > > > Today's next kernel fails to build with gcc 4.8.5 on powerpc machine. > > Thanks for the

[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
30] [c000bf44] ret_from_except_lite+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! -- Regar

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

2018-02-08 Thread Abdul Haleem
000 9138005c 3860 4bfff9e4 <7d29502a> 7923cfe3 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

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

2018-02-05 Thread Abdul Haleem
iffies, g=25946, c=25945, 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 0x0080 -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically

[linux-next] kernel Oops when booting powerpc

2018-01-16 Thread Abdul Haleem
b_srpt MAD registration failed for cxgb3_0-1. 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 # #

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

2018-01-09 Thread Abdul Haleem
"list_add double add: new=%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_BOOK3S_6

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
f.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=y # CONFIG_PPC_BOOK3

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

2017-10-30 Thread Abdul Haleem
system trusted keyrings A similar issue was reported 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-05 Thread Abdul Haleem
eration. -- Regard's Abdul Haleem IBM Linux Technology Centre

Re: [linux-next][Oops] memory hot-unplug results fault instruction address at /include/linux/list.h:104

2017-10-03 Thread Abdul Haleem
On Wed, 2017-09-20 at 12:54 -0700, Kees Cook wrote: > On Wed, Sep 20, 2017 at 12:40 AM, Abdul Haleem > <abdha...@linux.vnet.ibm.com> wrote: > > On Tue, 2017-09-12 at 12:11 +0530, abdul wrote: > >> Hi, > >> > >> Memory hot-unplug on PowerVM LPAR r

Re: [linux-next] [bisected a4615d11] Memory DLPAR triggers WARN_ONCE() in mm/page_vma_mapped.c

2017-10-03 Thread Abdul Haleem
On Fri, 2017-09-29 at 10:07 -0400, Zi Yan wrote: > Hi Abdul, > > I just want to follow up with this. > > Did you have a chance to test my patch? Does it fix your original problem? Yes I did test the patch. it fixes the warning. Reported-and-tested-by: Abdul Haleem <abdha...@

Re: [linux-next][Oops] memory hot-unplug results fault instruction address at /include/linux/list.h:104

2017-09-29 Thread Abdul Haleem
On Wed, 2017-09-20 at 12:54 -0700, Kees Cook wrote: > On Wed, Sep 20, 2017 at 12:40 AM, Abdul Haleem > <abdha...@linux.vnet.ibm.com> wrote: > > On Tue, 2017-09-12 at 12:11 +0530, abdul wrote: > >> Hi, > >> > >> Memory hot-unplug on PowerVM LPAR r

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

2017-09-29 Thread Abdul Haleem
do run memhotplug.py --show-job-log -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.11.0-rc7 Kernel Configuration # CONFIG_PPC64=y # # Processor support # CONFIG_PPC_BOOK3S_64=y # CONFIG_PPC_BOOK3E_64 is not set # CONFIG_POWER7

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 <abdha...@linux.vnet.ibm.com> writes: > > > > > Hi, > > > > > > Dynamic CPU remove operation resulted in Ke

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 <abdha...@linux.vnet.ibm.com> writes: > > > Hi, > > > > next kernel panics when running fsfuzzer test on ext4 file system. > > > > Machine Type: Power 7 PowerVM LPAR > > ker

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

2017-09-22 Thread Abdul Haleem
S_write+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 cal

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 <abdha...@linux.vnet.ibm.com> writes: > > > Hi, > > > > Dynamic CPU remove operation resulted in Kernel Panic on today's > > next-20170915 kernel. > > > > Machine Type: Power

Re: [linux-next][Oops] memory hot-unplug results fault instruction address at /include/linux/list.h:104

2017-09-20 Thread Abdul Haleem
On Tue, 2017-09-12 at 12:11 +0530, abdul wrote: > Hi, > > Memory hot-unplug on PowerVM LPAR running next-20170911 results in > Faulting instruction address: 0xc02b56c4 > > which maps to the below code path: > > 0xc02b56c4 is in __rmqueue (./include

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

2017-09-19 Thread Abdul Haleem
On Fri, 2017-09-15 at 07:52 -0500, Rob Herring wrote: > On Fri, Sep 15, 2017 at 6:04 AM, abdul <abdha...@linux.vnet.ibm.com> wrote: > > Hi, > > > > Mainline kernel panics during DLPAR CPU add/remove operation. > > > > Machine Type: Power8 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 > <abdha...@linux.vnet.ibm.com> wrote: > > Hi, > > > > Dynamic CPU remove operation resulted in Kernel Panic on today's > > next-20170915 kernel. > &

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

2017-09-18 Thread Abdul Haleem
fffc0c 3be0fff4 4bfffc04 <0fe0> 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 su

[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_GENE

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

2017-09-16 Thread Abdul Haleem
E)) return -EINVAL; + if (args->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 # # Aut

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

2017-09-15 Thread abdul
al exception Regard's Abdul Haleem IBM Linux Technology Center # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.11.0-rc7 Kernel Configuration # CONFIG_PPC64=y # # Processor support # CONFIG_PPC_BOOK3S_64=y # CONFIG_PPC_BOOK3E_64 is not set # CONFIG_POWER7_CPU is not set CONFIG_

Re: [linux-next] [bisected a4615d11] Memory DLPAR triggers WARN_ONCE() in mm/page_vma_mapped.c

2017-09-12 Thread abdul
On Mon, 2017-09-11 at 10:53 -0400, Zi Yan wrote: > Hi Abdul, > > Can you try this patch below? I think I missed that pmd entries > can be zapped, so the WARN_ONCE is unnecessary. > > Thanks. > > diff --git a/mm/page_vma_mapped.c b/mm/page_vma_mapped.c > index 6a0394

Re: RCU lockup issues when CONFIG_SOFTLOCKUP_DETECTOR=n - any one else seeing this?

2017-08-22 Thread Abdul Haleem
eat to > cross it off the list! > > Jonathan > No more RCU stalls on PowerPC, system is clean when idle or with some test runs. Thank you all for your time and efforts in fixing this. Reported-and-Tested-by: Abdul Haleem <abdha...@linux.vnet.ibm.com> -- Regard's Abdul Haleem IBM Linux Technology Centre

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

2017-08-22 Thread Abdul Haleem
2/2] scsi: Preserve retry counter through scsi_prep_fn Reported-and-Tested-by: Abdul Haleem <abdha...@linux.vnet.ibm.com> -- 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) > > > > Machine Type

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

2017-08-19 Thread Abdul Haleem
.data = _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
context. Add a WARN_ON_ONCE() to catch bad users up front. Signed-off-by: Jens Axboe <ax...@kernel.dk> -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.13.0-rc2 Kernel Configuration # CONFIG_P

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

2017-08-16 Thread Abdul Haleem
Johannes Thumshirn <jthumsh...@suse.de> Signed-off-by: Martin K. Petersen <martin.peter...@oracle.com> -- 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 # # Process

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 <abdha...@linux.vnet.ibm.com> wrote: > > > On Fri, 2017-06-30 at 00:45 +1000, Nicholas Piggin wrote: > > > On Thu, 29 Jun 2017 20:23:05 +1000 > >

[linux-next] kernel Oops while running stress test on ppc

2017-07-24 Thread Abdul Haleem
33 <SF,HV,ME,IR,DR,RI,LE> CR: 42082822 XER: 2000 CFAR: c014dea8 SOFTE: 0 stress : http://people.seas.harvard.edu/~apw/stress -- Regard's Abdul Haleem IBM Linux Technology Centre # # Automatically generated file; DO NOT EDIT. # Linux/powerpc 4.10.0-rc2 Kernel C

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

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

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

2017-07-14 Thread Abdul Haleem
radix to hash kexec due to 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 fi

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

2017-07-13 Thread Abdul Haleem
w Tests... ./run_test: line 155: 25870 Segmentation 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

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

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

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 > <abdha...@linux.vnet.ibm.com> wrote: > > On Fri, 2017-07-07 at 19:36 +0300, Andy Shevchenko wrote: > >> On Thu, Jul 6, 2017 at 9:00 AM, Abdul Haleem > >>

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 > <abdha...@linux.vnet.ibm.com> wrote: > > Hi Luis, > > > > next-20170705 fails to build on powerpc with below errors. > > Hi, > > I had se

  1   2   >