From: Tony Asleson <tasleson@redhat.com>
To: Sagi Grimberg <sagi@grimberg.me>, linux-nvme@lists.infradead.org
Subject: Re: nvmet: Kernel oops when doing mkfs on nvme-tcp device
Date: Mon, 23 Mar 2020 10:57:00 -0500 [thread overview]
Message-ID: <c8fce5f3-a01b-da38-820f-cf6caaa377ab@redhat.com> (raw)
In-Reply-To: <f390f5a1-a80f-44d7-5d69-642119eef9b8@grimberg.me>
On 3/23/20 3:33 AM, Sagi Grimberg wrote:
>
>>> Can you share which line *(nvme_tcp_io_work+0x303) map to?
>>
>> I'm not running a debug kernel so I don't think I have that available?
>> Please advise if otherwise.
>
> Maybe you will still have frame pointers though?
>
> If you run:
> gdb <path_to_mod>
> ...
>> l *(nvme_tcp_io_work+0x303)
>
> Do you get anything useful?
Nope, sorry.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-03-23 15:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 21:36 nvmet: Kernel oops when doing mkfs on nvme-tcp device Tony Asleson
2020-03-20 22:23 ` Chaitanya Kulkarni
2020-03-20 23:24 ` Tony Asleson
2020-03-20 22:54 ` Sagi Grimberg
2020-03-20 22:59 ` Sagi Grimberg
2020-03-20 23:46 ` Tony Asleson
2020-03-21 0:43 ` Chaitanya Kulkarni
2020-03-23 17:56 ` Tony Asleson
2020-03-23 19:42 ` Sagi Grimberg
2020-03-23 20:10 ` Tony Asleson
2020-03-20 23:43 ` Tony Asleson
2020-03-23 8:33 ` Sagi Grimberg
2020-03-23 15:57 ` Tony Asleson [this message]
2020-03-23 19:41 ` Sagi Grimberg
2020-03-23 20:46 ` Chaitanya Kulkarni
2020-03-23 20:52 ` Sagi Grimberg
2020-03-23 22:02 ` Sagi Grimberg
2020-03-23 23:37 ` Tony Asleson
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=c8fce5f3-a01b-da38-820f-cf6caaa377ab@redhat.com \
--to=tasleson@redhat.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox