here:
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
Ab
9 409eff9c 3921 3c82fff1 3c62fff1 3d42017d 38a00788
3884b3c8 3863b3d8 992a2141 4b68a969 6000 <0fe0> 6000
3c4c0070 38422900
--
Regard's
Abdul Haleem
IBM Linux Technology Center
f_packet_diag netlink_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
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 bo
f7f0 f821ffe1
3921 992d0932 3920 3941 <7c801829> 7c044800 40c20010 7d40192d
---[ end trace ]---
--
Regard's
Abdul Haleem
IBM Linux Technology Center
0x11c/0x130
[c0004ccbbe10] [c000ce64] ret_from_kernel_thread+0x5c/0x64
call traces never ends and could not login
--
Regard's
Abdul Haleem
IBM Linux Technology Center
6962 {
6963 unsigned long val, new;
6964
6965 do {
6966 val = READ_ONCE(n->state);
6967 BUG_ON(!test_bit(NAPI_STATE_SCHED, &val));
6968
6969 new = val & ~(NAPIF_STATE_SCHED | NAPIF_STATE_NPSVC);
6970 if (n->dev->threaded &&am
04]: QLogic 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
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 s
read+0x18c/0x1a0
[cd167e10] [c000cfd4] 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
:80 active ready running
$
After test fail
$ multipath -ll
mpathf (360050768108001b3a8e8) dm-10 ##,##
size=30G features='1 queue_if_no_path' hwhandler='0' wp=rw
$
--
Regard's
Abdul Haleem
IBM Linux Technology Center
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 referen
634fa04d6dac7dfd ]---
--
Regard's
Abdul Haleem
IBM Linux Technology Center
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
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
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
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.
&
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
+ 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 remap
.1]-b079: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
# CO
99 tun: switch to u64_stats_t
316580b69d0a7a5063af47438b626bc47cbd u64_stats: provide u64_stats_t
type
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
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
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
>
0 2f89 409efe74
3c62ff9b 38639d78 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
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
(hmm: use mmu_notifier_get/put for
'struct hmm')
error disappears when commit is reverted.
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
(hmm: use mmu_notifier_get/put for
'struct hmm')
Reverting the commit fixes the issue.
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
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
> >>>
> >>>
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_
release_sub_crqs(adapter, 1);
> @@ -4852,7 +4835,7 @@ static int ibmvnic_remove(struct vio_dev *dev)
>
> adapter->state = VNIC_REMOVED;
>
> - mutex_unlock(&adapter->reset_lock);
> + rtnl_unlock();
> device_remove_file(&dev->dev, &dev_a
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:
> >&
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
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
&
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 h
/mlx4/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 Tech
RHEAD;
> -#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
;
> This 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 ++
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
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-m
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 se
047f34] 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
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’:
> > dr
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 ker
nx2x 0008: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
5 /dev/sdb
[1:0:1:0]diskIBM 2145 /dev/sdd
# lsscsi -H
[0]ibmvscsi
[1]qla2xxx
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
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 lots o
54a16ba 9141003c 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
sd 16:0:4:0: [sde] Synchronizing SCSI cache
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
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
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 r
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 Hal
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.
> >
> &
slab cache. ksm_rmap_item but object is from kmalloc-128
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
8022d45 e8410018 <0fe0> 4bfffbe8 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
#
; Can you 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 (mainlin
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
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
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,
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
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
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
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
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
p, prev=%p,
next=%p.\n",
31 new, prev, next))
32 return false;
33
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
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
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
> >
&
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=
ported on 4.11.0
https://lkml.org/lkml/2017/3/7/763
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
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
On Wed, 2017-09-20 at 12:54 -0700, Kees Cook wrote:
> On Wed, Sep 20, 2017 at 12:40 AM, Abdul Haleem
> wrote:
> > On Tue, 2017-09-12 at 12:11 +0530, abdul wrote:
> >> Hi,
> >>
> >> Memory hot-unplug on PowerVM LPAR running next-20170911 resul
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
Tha
On Wed, 2017-09-20 at 12:54 -0700, Kees Cook wrote:
> On Wed, Sep 20, 2017 at 12:40 AM, Abdul Haleem
> wrote:
> > On Tue, 2017-09-12 at 12:11 +0530, abdul wrote:
> >> Hi,
> >>
> >> Memory hot-unplug on PowerVM LPAR running next-20170911 resul
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
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
> > >
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
+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
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
> >
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
On Fri, 2017-09-15 at 07:52 -0500, Rob Herring wrote:
> On Fri, Sep 15, 2017 at 6:04 AM, abdul wrote:
> > Hi,
> >
> > Mainline kernel panics during DLPAR CPU add/remove operation.
> >
> > Machine Type: Power8 PowerVM LPAR
> > kernel 4.13.0
>
> Did 4
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
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
--[ 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
>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
] ret_from_kernel_thread+0x5c/0x7c
Instruction dump:
4bb73f35 6000 e95f66a0 e93f66a8 2fb8 394a0001 39290001 f95f66a0
f93f66a8 419e003c e95e0022 e93f66b0 <7d58502a> 39290001 f93f66b0
2faa
---[ end trace 9dc6afde15547583 ]---
Kernel panic - not syncing: Fatal exception
Regard's
Abdul Halee
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
talls 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
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
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
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
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
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
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_
: 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
#
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:
> >
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 Configuration
#
CONFIG_PPC64=y
#
# Processor su
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
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
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
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
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
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
1 - 100 of 149 matches
Mail list logo
