All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: "Nathan A. Mourey II" <nmoureyii@ne.rr.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs oops with kernel 3.5-rc4
Date: Tue, 26 Jun 2012 16:19:51 -0400	[thread overview]
Message-ID: <20120626201950.GB24953@localhost.localdomain> (raw)
In-Reply-To: <1340741359.2226.5.camel@athena>

On Tue, Jun 26, 2012 at 02:09:19PM -0600, Nathan A. Mourey II wrote:
> Oops with kernel v3.5-rc4.  This error produced while:
> 
> emerge --sync &&  emerge --update --newuse --deep --with-bdeps=y @world && emerge --depclean && revdep-rebuild
> and 
> stress --cpu 1 --io 8 -d 8  --vm 4  -t 8h
> 
> ver_linux.sh was ran on stable v3.4.4 system.  
> 
> Linux peach.example.com 3.4.4 #2 SMP Sun Jun 24 20:38:42 EDT 2012 i686
> Intel(R) Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux
> 
>  Gnu C                  4.5.3
>  Gnu make               3.82
>  binutils               2.21.1
>  util-linux             ./ver_linux: line 23: fdformat: command not found
>  mount                  support
>  module-init-tools      found
>  quota-tools            3.17.
>  Linux C Library        2.14.1
>  Dynamic linker (ldd)   2.14.1
>  Procps                 3.2.8
>  Kbd                    1.15.3wip
>  Sh-utils               8.14
>  Modules Loaded         ext3 jbd ehci_hcd
> 

Can you gdb btrfs.ko and do 

list *(btrfs_finish_ordered_io+0x22)

please?  And are you running compression by chance?  Thanks,

Josef

  reply	other threads:[~2012-06-26 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 20:09 btrfs oops with kernel 3.5-rc4 Nathan A. Mourey II
2012-06-26 20:19 ` Josef Bacik [this message]
2012-06-27 18:57   ` Nathan A. Mourey II
2012-06-27 21:16     ` Josef Bacik

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=20120626201950.GB24953@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nmoureyii@ne.rr.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.