Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp1078992ybl; Wed, 14 Aug 2019 10:21:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqzbadoeuHQt41nFbahYSZWJruhNGBwjB/FhNSn/v6yvssV1XyuOZFAemGeX9LW40Rz31ncl X-Received: by 2002:a63:3407:: with SMTP id b7mr216475pga.143.1565803267575; Wed, 14 Aug 2019 10:21:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565803267; cv=none; d=google.com; s=arc-20160816; b=B+lGn4cp5lp1pfBGgVhAFM703GatFUPf3wSnAMDSwqD0vX/GTV3oxF7VLze0TyYQcd Ffx5t2xqdGpfr1m2MMw0Gu6RCs2fAi9iUCnw0u57J1DK7dkcMXWuE+ZjRjlIW5pJXNnw PQi0dsF6w1cMyDwG+68Gp2mXb2e7iHkw8Ezkso8QOiLVcAv1PTpMj1pUm2chmzqX2I1Q 7uvSTzmqAwy1fhDbCL4qKzrEsc4w5WJn+OT++rONyzXJ76aZTmCK6Z9DvTRFGgkJXl/U RTfKztm0DoIRc/4lpqBxhqOstMDJMwyBnQJqDUhsPQBkwPS1UtDVQezcTvJJxR35atWv s19A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=15PU4COft//nLVBq937GDIMLrZRB4jv3N25l4uS4lNA=; b=UdV8NxG6OxdYSa1tGVuM0j1TwCS5RUl6JDvVnbVpcsa2zF8nsuF0hhwmLC1qk4o7To ZAXymnkKR6ojnqHMeJgSeTVCj5bohJKNVnMbl+3RjDPCy8KVDjS+zAX7f5l2ZRofHJaK WbkjACsIKzRTaiyo7mdQXMm8M9M9VAqloi00r/otZe7t8g38CRseDugqGwwxwc/Psh8y Vn9jhJo7oPPz+tMUzJN8sxYRc7LBDG7tOiZ+ka9rhSQb4Lxf+/vGuNwYM0oNwV17Mz0j q7jEB/XAYr4R2QPjp7J+mBl5fgKExdq3cKE6UkiPHUB4w3rSX9V61FRWL0reSeHBxOT9 yRJA== 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=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 19si58953pfc.239.2019.08.14.10.20.51; Wed, 14 Aug 2019 10:21:07 -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=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730180AbfHNRTH (ORCPT + 99 others); Wed, 14 Aug 2019 13:19:07 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:11048 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728776AbfHNRTG (ORCPT ); Wed, 14 Aug 2019 13:19:06 -0400 Received: from pps.filterd (m0098416.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x7EGr4o1001880; Wed, 14 Aug 2019 13:18:51 -0400 Received: from ppma03wdc.us.ibm.com (ba.79.3fa9.ip4.static.sl-reverse.com [169.63.121.186]) by mx0b-001b2d01.pphosted.com with ESMTP id 2ucp47s3vu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 14 Aug 2019 13:18:51 -0400 Received: from pps.filterd (ppma03wdc.us.ibm.com [127.0.0.1]) by ppma03wdc.us.ibm.com (8.16.0.27/8.16.0.27) with SMTP id x7EGtZYC006002; Wed, 14 Aug 2019 17:18:50 GMT Received: from b03cxnp08025.gho.boulder.ibm.com (b03cxnp08025.gho.boulder.ibm.com [9.17.130.17]) by ppma03wdc.us.ibm.com with ESMTP id 2u9nj648pe-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 14 Aug 2019 17:18:50 +0000 Received: from b03ledav006.gho.boulder.ibm.com (b03ledav006.gho.boulder.ibm.com [9.17.130.237]) by b03cxnp08025.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x7EHIn2S52232660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 14 Aug 2019 17:18:49 GMT Received: from b03ledav006.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 97EBBC605B; Wed, 14 Aug 2019 17:18:49 +0000 (GMT) Received: from b03ledav006.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 1204FC6059; Wed, 14 Aug 2019 17:18:45 +0000 (GMT) Received: from [9.85.86.184] (unknown [9.85.86.184]) by b03ledav006.gho.boulder.ibm.com (Postfix) with ESMTP; Wed, 14 Aug 2019 17:18:44 +0000 (GMT) Message-ID: <1565803123.6908.10.camel@abdul> Subject: 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 From: Abdul Haleem To: Bart Van Assche Cc: linuxppc-dev , linux-next , Stephen Rothwell , linux-scsi , martin.petersen@oracle.com, hmadhani@marvell.com, sachinp , linux-kernel Date: Wed, 14 Aug 2019 22:48:43 +0530 In-Reply-To: References: <1565801523.6908.6.camel@abdul> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-08-14_06:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=850 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1908140158 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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() was introduced by commit 88263208 (scsi: qla2xxx: Complain if sp->done() is not...) > > > > boot logs: > > > > WARNING: CPU: 10 PID: 425 at drivers/scsi/qla2xxx/qla_isr.c:2784 > > Hi Abdul, > > Thank you for having reported this. Is that the only warning reported on your setup by the qla2xxx > driver? If that warning is commented out, does the qla2xxx driver work as expected? boot warning did not show up when the commit is reverted. should I comment out only the WARN_ON_ONCE() which is causing the issue, and not the other one ? -- Regard's Abdul Haleem IBM Linux Technology Centre