From: Marc MERLIN <marc@merlins.org>
To: Arne Jansen <sensille@gmx.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs panic in 3.5.0
Date: Tue, 7 Aug 2012 11:47:36 -0700 [thread overview]
Message-ID: <20120807184736.GA22686@merlins.org> (raw)
In-Reply-To: <50215AFF.1080800@gmx.net>
On Tue, Aug 07, 2012 at 08:14:23PM +0200, Arne Jansen wrote:
> On 08/07/2012 07:40 PM, Marc MERLIN wrote:
> > Unfortunately I only have a screenshot.
> >
> > Apparently the panic was in
> > btrfs_set_lock_blocking_rw
> > with a RIP in btrfs_cow_block
>
> Can you please resolve btrfs_cow_block+0x3b to a line number?
>
> gdb btrfs.ko
> (gdb) info line *btrfs_cow_block+0x3b
So, I'm not very good at this, sorry if I'm doing it wrong:
gandalfthegreat:~# gdb /lib/modules/3.5.0-amd64-preempt-noide-20120410/kernel/fs/btrfs/btrfs.ko
Reading symbols from /lib/modules/3.5.0-amd64-preempt-noide-20120410/kernel/fs/btrfs/btrfs.ko...(no debugging symbols found)...done.
(gdb) info line *btrfs_cow_block+0x3b
No line number information available for address 0x9a6e
Mmmh, it seems that I'm missing a kernel option that adds symbols in modules?
I can add it for my next kernel compile. Do you have the config option name
off hand?
I put my module here if that helps:
http://marc.merlins.org/tmp/btrfs.ko
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2012-08-07 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 17:40 btrfs panic in 3.5.0 Marc MERLIN
2012-08-07 18:14 ` Arne Jansen
2012-08-07 18:47 ` Marc MERLIN [this message]
2012-08-09 2:52 ` Marc MERLIN
2012-08-09 6:42 ` Arne Jansen
2012-08-09 6:43 ` Jan Schmidt
2012-08-08 2:38 ` Jérôme Poulin
2012-08-08 2:47 ` Marc MERLIN
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=20120807184736.GA22686@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=sensille@gmx.net \
/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;
as well as URLs for NNTP newsgroup(s).