Kernel Newbies archive on lore.kernel.org
 help / color / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
	"Subhashini Rao Beerisetty" <subhashbeerisetty@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: general protection fault vs Oops
Date: Sat, 16 May 2020 08:59:53 -0700
Message-ID: <af03bee5-27b2-4e92-359a-b1cc8f500d6d@infradead.org> (raw)
In-Reply-To: <374485.1589637193@turing-police>

On 5/16/20 6:53 AM, Valdis Klētnieks wrote:
> 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.

Right.

> 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

Modules linked in:
dbg(OE) mcore(OE) osa(OE)

Out-of-tree, unsigned modules loaded.
We don't know what those are or how to debug them.

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


-- 
~Randy


_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  parent reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16 12:35 Subhashini Rao Beerisetty
2020-05-16 13:53 ` Valdis Klētnieks
2020-05-16 15:10   ` Subhashini Rao Beerisetty
2020-05-16 15:59   ` Randy Dunlap [this message]
2020-05-16 16:15     ` Subhashini Rao Beerisetty
2020-05-17 20:46       ` Cong Wang
2020-05-18  5:45         ` Subhashini Rao Beerisetty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=af03bee5-27b2-4e92-359a-b1cc8f500d6d@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=subhashbeerisetty@gmail.com \
    --cc=valdis.kletnieks@vt.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Kernel Newbies archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kernelnewbies/0 kernelnewbies/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernelnewbies kernelnewbies/ https://lore.kernel.org/kernelnewbies \
		kernelnewbies@kernelnewbies.org
	public-inbox-index kernelnewbies

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernelnewbies.kernelnewbies


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git