Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" <valdis.kletnieks@vt.edu>
To:     Subhashini Rao Beerisetty <subhashbeerisetty@gmail.com>
Cc:     kernelnewbies <kernelnewbies@kernelnewbies.org>,
        linux-kernel@vger.kernel.org
Subject: Re: general protection fault vs Oops
In-Reply-To: <CAPY=qRQ6gzN1BWh=ianVDBQ1C9kibWHwxs5Z0+QSwGxKymLDTQ@mail.gmail.com>
References: <CAPY=qRQ6gzN1BWh=ianVDBQ1C9kibWHwxs5Z0+QSwGxKymLDTQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1589637193_23225P";
         micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date:   Sat, 16 May 2020 09:53:13 -0400
Message-ID: <374485.1589637193@turing-police>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

--==_Exmh_1589637193_23225P
Content-Type: text/plain; charset=us-ascii

On Sat, 16 May 2020 18:05:07 +0530, Subhashini Rao Beerisetty said:

> In the first attempt when I run that test case I landed into “general
> protection fault: 0000 [#1] SMP" .. Next I rebooted and ran the same
> test , but now it resulted the “Oops: 0002 [#1] SMP".

And the 0002 is telling you that there's been 2 previous bug/oops since the
reboot, so you need to go back through your dmesg and find the *first* one.

> In both cases the call trace looks exactly same and RIP points to
> “native_queued_spin_lock_slowpath+0xfe/0x170"..

The first few entries in the call trace are the oops handler itself. So...


> May 16 12:06:17 test-pc kernel: [96934.567347] Call Trace:
> May 16 12:06:17 test-pc kernel: [96934.569475]  [<ffffffff8183c427>]__raw_spin_lock_irqsave+0x37/0x40
> May 16 12:06:17 test-pc kernel: [96934.571686]  [<ffffffffc0606812>] event_raise+0x22/0x60 [osa]
> May 16 12:06:17 test-pc kernel: [96934.573935]  [<ffffffffc06aa2a4>] multi_q_completed_one_buffer+0x34/0x40 [mcore]

The above line is the one where you hit the wall.

> May 16 12:59:22 test-pc kernel: [ 3011.405602] Call Trace:
> May 16 12:59:22 test-pc kernel: [ 3011.407892]  [<ffffffff8183c427>] _raw_spin_lock_irqsave+0x37/0x40
> May 16 12:59:22 test-pc kernel: [ 3011.410256]  [<ffffffffc0604812>] event_raise+0x22/0x60 [osa]
> May 16 12:59:22 test-pc kernel: [ 3011.412652]  [<ffffffffc06b72a4>] multi_q_completed_one_buffer+0x34/0x40 [mcore]

And again.

However,  given that it's a 4.4 kernel from 4 years ago, it's going to be
hard to find anybody who really cares.

In fact. I'm wondering if this is from some out-of-tree or vendor patch,
because I'm not finding any sign of that function in either the 5.7 or 4.4
tree.  Not even a sign of ## catenation abuse - no relevant hits for
"completed_one_buffer" or "multi_q" either

I don't think anybody's going to be able to help unless somebody first
identifies where that function is....


--==_Exmh_1589637193_23225P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Comment: Exmh version 2.9.0 11/07/2018

iQIVAwUBXr/wSQdmEQWDXROgAQLmLQ//TxlbNV2RGPp3REQ8H1b2HJ7NxUwvwg9v
UeVv+9WCMn2w6Ra/UKBybERvFWIrS2BSRDXrdl1L6J5Kw7gEbeUEyl73DR0qHO8e
B8ahq4yuvwivG6jd2uN2qYsfCgvIgpYki/Rkb/72FtO+nY/VmzrxpYfVF+1mGHLd
O5quR4peIOUgm+8XPZLmZJu6SIUcVAc6iXuei08MhaRqxtRw0sPcM7M++HelbEg5
+MqbiH/R87FcHVIP5x/BRw79drf2hQ7Fz+9VfAaQBpi6j2Y0HcgilTvnegyNk1qM
ZITt4TLWgzbCeqFjwAq+cyF674mnSyFYv5Ef+sGfcuwwOxXkDKPlavaezRjunz1H
XVIX9ENws/SITj/gS90SNJ32vmomnxICCBJGyGLUm8DZdyVim07h7tcaW7t9vjGe
ZuID1kgm1xkr6c++SD+pCMlNu2Xk74SkOvox2ylbcln9xF2hO+mlZoHjSWGcg3co
h+gocMcSVVHlWg5dmCR6ZpGZ5J88Mv/l3k2cpDE70lGyYy3rutjYcX0jrLHlTVCy
McjFpaQi+HaDCiMTfLgZfg0wkhaANd1B4MOmDLOYiKW4ErxvywEEnjzEpj7iLJmt
y+L1OXdZCdiRTPneLThvxGsGVtTiUJDKwAtGjcR0sJb8f1dkpIs035Vkjz1JGNm9
K6VW2Glkfy0=
=1zv1
-----END PGP SIGNATURE-----

--==_Exmh_1589637193_23225P--