Hi,
Today's next tree has warning messages in dmesg when running rcutorture
tests.
Machine : Power8 PowerVM LPAR
Build kernel : 4.10.0-rc5-next-20170125
Steps to recreate:
1.modprobe rcutorture
2.32 CPUS; offline 0-15 CPUS keeping 16-31 CPUs online and vice versa in
a loop
3. modprobe -r rc
Hi,
Today's next tree has warning messages in dmesg when running rcutorture
tests.
Machine : Power8 PowerVM LPAR
Build kernel : 4.10.0-rc5-next-20170125
Steps to recreate:
1.modprobe rcutorture
2.32 CPUS; offline 0-15 CPUS keeping 16-31 CPUs online and vice versa in
a loop
3. modprobe -r rc
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
] 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 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
99 tun: switch to u64_stats_t
316580b69d0a7a5063af47438b626bc47cbd u64_stats: provide u64_stats_t
type
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
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
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
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
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 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
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 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
;
> 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 ++
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
/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
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
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
&
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 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:
> >&
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 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_
; 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
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
#
slab cache. ksm_rmap_item but object is from kmalloc-128
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
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.
> >
> &
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 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
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
sd 16:0:4:0: [sde] Synchronizing SCSI cache
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
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
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
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
.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
+ 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
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
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 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 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
> >>>
> >>>
(hmm: use mmu_notifier_get/put for
'struct hmm')
Reverting the commit fixes the issue.
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
(hmm: use mmu_notifier_get/put for
'struct hmm')
error disappears when commit is reverted.
--
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
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 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
>
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
9 409eff9c 3921 3c82fff1 3c62fff1 3d42017d 38a00788
3884b3c8 3863b3d8 992a2141 4b68a969 6000 <0fe0> 6000
3c4c0070 38422900
--
Regard's
Abdul Haleem
IBM Linux Technology Center
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
f7f0 f821ffe1
3921 992d0932 3920 3941 <7c801829> 7c044800 40c20010 7d40192d
---[ end trace ]---
--
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
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
634fa04d6dac7dfd ]---
--
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
: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
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
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
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 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
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
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
8ac202 2fa9 419e000c 794a2428 7d295214
3d020004 78840620 81487564 7c845436 5484103a 7c8807b4 548406ba
---[ end trace 911354ae3120f308 ]---
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
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
owerpc64le-linux-gnu/ld-2.24.so
3fffe31c-3fffe31f rw-p 00:00 0 [stack]
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
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
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
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
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
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:
> >>>
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
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
> > >
: This should not happen!! Data will be lost
Starting 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
#
# Proces
---
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
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
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
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
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
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
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
On Wed, 2017-05-10 at 19:55 +0200, Christoph Hellwig wrote:
> Hi Abdul,
>
> can you test the patch below? I'll try to create a way to inject
> short WRITE SAME commands using qemu next, but I thought I'd give
> you a chance to try it as well.
No warnings with the p
_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
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.
> >
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,
> > > >
> > &
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
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
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
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
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
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
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
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
o this has been unnoticed so far. It was found by a
> proposed new powerpc watchdog that takes a soft-NMI directly from the
> masked_interrupt handler and using the emergency stack. That crashed at
> BUG_ON(in_nmi()) in nmi_enter(). preempt_count()s were found to be
> garbage.
>
> Report
/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.
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] \
>
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
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
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
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:
> >
On Wed, 2017-07-05 at 11:28 -0400, Tejun Heo wrote:
> Hello, Abdul.
>
> Thanks for the debug info. Can you please see whether the following
> patch fixes the issue?
It is my pleasure and yes the patch fixes the problem.
> If the problem is too difficult to reproduce
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:
> >
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
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
1 - 100 of 149 matches
Mail list logo
