Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp3434157ybi; Sun, 26 May 2019 23:24:26 -0700 (PDT) X-Google-Smtp-Source: APXvYqzDKxZOPOW9CSUHAxLgQPyYT52ymg+jBlP6mOlRCtevaHexzoxzh8VGbsb+RNoP++/1gl9J X-Received: by 2002:a17:902:8f84:: with SMTP id z4mr41863627plo.233.1558938266726; Sun, 26 May 2019 23:24:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558938266; cv=none; d=google.com; s=arc-20160816; b=ZKz3PG+w6A9YcHoWaNxqWU+oPHXkhZ3dYk/eQUmqwDYr/Uth8hNR9eepnY0oeiLzXX ibi7IeH9DrB/ASL8By1/dZQvNlWbs/vWi14y7fSW7aAKGJPmynueeHANCT3L4LdDRPJz JDNzzvIaOv0cC2XKOWfrOqtX4BX12fdBYGfWzPHOgNWSHHuSEKr1jZFL9pOujjV0eNHL E/l2evMHHPxOtpXxxjO7yhd28oheifDvQemfhYK46SgtqMlUNEvfiXWxeuwlYikUijFq GTqNIRZ89eb70rc4CR0pKtycIGFmdJyDAvplO7SECSO0UyP/Zkq6yuYBh2BW6mrV9+Ru fScw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=2EwAn8/owM0ZpqAm1O3Pr+v/VNdJwGPW1zcKtSbo++g=; b=JKV3/v8++m6wulImDRdhSviIH/To0y31QB0ROu/L1S1EZH5vW5tABEjBaEyPBYPecT l4bfwEUv7YbT4QvBz0Xj1vYsqOZds3R9NpY2TjNgJ4ebTl64uiJZMjsbKeuW36qjV3hE G8BOuIOOzTPjjV3t3K1dCRxQcYe4j/kmfvaPyod5glPSfHBizPQjm7uDCl8ezpL3vdMA qvYBTPJ+l/aMIJgLAvD6iqLzT5kqPcGR8jr18NjqBod9bXdNUtQxb9frvWvs+ysVuLyF IqnIGud6ARCjy07diwOa6FdyP67Y3OA+TO2URxIHX4Fo/mB91/CDIBxO+wamJRUWTlD3 I2GA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n88si16518657pjc.7.2019.05.26.23.24.12; Sun, 26 May 2019 23:24:26 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726470AbfE0GXH (ORCPT + 99 others); Mon, 27 May 2019 02:23:07 -0400 Received: from mail-wm1-f68.google.com ([209.85.128.68]:51511 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726065AbfE0GXF (ORCPT ); Mon, 27 May 2019 02:23:05 -0400 Received: by mail-wm1-f68.google.com with SMTP id f10so7413527wmb.1 for ; Sun, 26 May 2019 23:23:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=2EwAn8/owM0ZpqAm1O3Pr+v/VNdJwGPW1zcKtSbo++g=; b=EN35T/dVwzVXzxIYmK5dIHX69jOP/XzAE652qVv12jBXhcg7Mjw3f8Qq82pozMU55d Qve0LQ/cUopUmbrPY5MteXLe4HZWA4OGv/rWRB4xRQielhiW1m3STbflWJORWlOhFwAp NyXXhOILs4aaIIEMZwkyOlPbRS8co8yL8CiVozsFUC3VEZWRhB4VDVMluXTVbBalN3aW DHJqV62VU8Otf0FQ3SI3q4KycfGK1dEmsGG/CmGFNWLKB0BfWvr5mhrpqmgwJ3nziqzI NH3Fc4jTQZWvkc/UJVeBkDYY50NqGvA+vMKrnsiqTwDG0nU8L3/71Dlc2nkZlfxFC4hw hj1w== X-Gm-Message-State: APjAAAVVeZA2HR3t/urGcbvjApKwiha1ECLMKl/RYjuGnjzfeZfYJT7p h2XTcpZ28BL+2mL+67cii8S+aKwXKyg= X-Received: by 2002:a1c:e183:: with SMTP id y125mr328512wmg.152.1558938183765; Sun, 26 May 2019 23:23:03 -0700 (PDT) Received: from localhost (nat-pool-brq-t.redhat.com. [213.175.37.10]) by smtp.gmail.com with ESMTPSA id g16sm9541735wrm.96.2019.05.26.23.23.02 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 26 May 2019 23:23:02 -0700 (PDT) Date: Mon, 27 May 2019 08:23:01 +0200 From: Oleksandr Natalenko To: Mel Gorman Cc: Justin Piszcz , LKML Subject: Re: 5.1 and 5.1.1: BUG: unable to handle kernel paging request at ffffea0002030000 Message-ID: <20190527062301.rk32mhnk2qy2ives@butterfly.localdomain> References: <20190520115608.GK18914@techsingularity.net> <20190521124310.GM18914@techsingularity.net> <20190524114329.hujd3qvtusz6uyfk@butterfly.localdomain> <20190524123146.GP18914@techsingularity.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190524123146.GP18914@techsingularity.net> User-Agent: NeoMutt/20180716 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 24, 2019 at 01:31:46PM +0100, Mel Gorman wrote: > On Fri, May 24, 2019 at 01:43:29PM +0200, Oleksandr Natalenko wrote: > > > Please use the offset 0xb9 > > > > > > addr2line -i -e /usr/src/linux/vmlinux `printf "0x%lX" $((0x$ADDR+0xb9)) > > > > > > -- > > > Mel Gorman > > > SUSE Labs > > > > Cc'ing myself since i observe such a behaviour sometimes right after KVM > > VM is launched. No luck with reproducing it on demand so far, though. > > > > It's worth testing the patch at https://lore.kernel.org/lkml/1558689619-16891-1-git-send-email-suzuki.poulose@arm.com/T/#u It is reported [1] that this fixes the issue. Thanks. [1] https://github.com/NixOS/nixpkgs/issues/61909 > > -- > Mel Gorman > SUSE Labs -- Best regards, Oleksandr Natalenko (post-factum) Senior Software Maintenance Engineer