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;
From:   <Narendra.K@dell.com>
To:     <rong.a.chen@intel.com>
CC:     <ard.biesheuvel@linaro.org>, <Mario.Limonciello@dell.com>,
        <linux-kernel@vger.kernel.org>, <torvalds@linux-foundation.org>,
        <lkp@lists.01.org>, <Narendra.K@dell.com>
Subject: Re: [efi] 1c5fecb612: WARNING:at_kernel/iomem.c:#memremap
Thread-Topic: [efi] 1c5fecb612: WARNING:at_kernel/iomem.c:#memremap
Thread-Index: AQHVqPSzwARs+w96okKqUpUqied7KqentwiAgAN61IA=
Date:   Thu, 5 Dec 2019 13:29:25 +0000
Message-ID: <20191205132915.GA2698@localhost.localdomain>
References: <20191201155238.GR18573@shao2-debian>
 <CAKv+Gu8MO_85Fa0y7YZ0iEgxrXbfR5-1e37FbiByzP8LrohcYA@mail.gmail.com>
 <51a225fa-6775-ed3f-22ff-4c88de6f6db4@intel.com>
In-Reply-To: <51a225fa-6775-ed3f-22ff-4c88de6f6db4@intel.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Mutt/1.10.1 (2018-07-13)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.143.18.86]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <723610D4B160D343901F769D1F9DF693@dell.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572
 definitions=2019-12-05_03:2019-12-04,2019-12-05 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 clxscore=1015 bulkscore=0
 suspectscore=0 impostorscore=0 phishscore=0 mlxscore=0 malwarescore=0
 adultscore=0 mlxlogscore=999 spamscore=0 lowpriorityscore=0
 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1
 engine=8.12.0-1910280000 definitions=main-1912050114
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 suspectscore=0 bulkscore=0
 clxscore=1011 priorityscore=1501 phishscore=0 impostorscore=0
 lowpriorityscore=0 malwarescore=0 mlxlogscore=999 spamscore=0 mlxscore=0
 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000
 definitions=main-1912050113
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Dec 03, 2019 at 04:20:51PM +0800, Rong Chen wrote:
> On 12/2/19 5:41 PM, Ard Biesheuvel wrote:
> > On Sun, 1 Dec 2019 at 16:53, kernel test robot <rong.a.chen@intel.com> =
wrote:
> > > FYI, we noticed the following commit (built with gcc-7):
> > >=20
> > > commit: 1c5fecb61255aa12a16c4c06335ab68979865914 ("efi: Export Runtim=
e Configuration Interface table to sysfs")
> > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git maste=
r
> > >=20
> > > in testcase: rcutorture
> > > with following parameters:
> > >=20
> > >          runtime: 300s
> > >          test: default
> > >          torture_type: tasks
> > >=20
> > > test-description: rcutorture is rcutorture kernel module load/unload =
test.
> > > test-url: https://www.kernel.org/doc/Documentation/RCU/torture.txt
> > >=20
> > >=20
> > > on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp=
 2 -m 8G
> > >=20
> > > caused below changes (please refer to attached dmesg/kmsg for entire =
log/backtrace):
> > >=20
> > >=20
> > > +------------------------------------------------+------------+------=
------+
> > > |                                                | 5828efb95b | 1c5fe=
cb612 |
> > > +------------------------------------------------+------------+------=
------+
> > > | boot_successes                                 | 0          | 0    =
      |
> > > | boot_failures                                  | 4          | 4    =
      |
> > > | Kernel_panic-not_syncing:No_working_init_found | 4          | 4    =
      |
> > > | WARNING:at_kernel/iomem.c:#memremap            | 0          | 4    =
      |
> > > | EIP:memremap                                   | 0          | 4    =
      |
> > > +------------------------------------------------+------------+------=
------+
> > >=20
> > I don't understand this result. Doesn't it say the number of failures
> > is the same, but it just fails in a different place? Is there a
> > working config that breaks due to that commit?
>=20
> Hi Ard,
>=20
> The results means all boot are failed, parent commit fails at
> "Kernel_panic-not_syncing:No_working_init_found"
> which may causes by the wrong test environment, but the commit "1c5fecb61=
2"
> introduced a new error:
> "WARNING:at_kernel/iomem.c:#memremap".
>=20
> We prepared the reproduce steps and config file in report mail:
> https://lore.kernel.org/lkml/20191201155238.GR18573@shao2-debian/
>=20

Hi Rong,

Thank you. I am trying to replicate the issue. I will share findings.

--=20
With regards,
Narendra K=