linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: "Nathan A. Mourey II" <nmoureyii@ne.rr.com>
Cc: linux-kernel@vger.kernel.org,
	Linux PM mailing list <linux-pm@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-fsdevel@vger.kernel.org
Subject: Re: Kernel bug with btrfs on laptop with external hd and suspend and resume.
Date: Mon, 13 Feb 2012 19:47:39 +0530	[thread overview]
Message-ID: <4F391B83.7080703@linux.vnet.ibm.com> (raw)
In-Reply-To: <1328990690.2464.6.camel@firefly>

Adding some Cc's.

On 02/12/2012 01:34 AM, Nathan A. Mourey II wrote:

> I just installed the new kernel with yum update.  I have an external eSATA hard drive that is 
> formatted with btrfs.  I closed the lid once it had booted up, I had not logged in yet.  Latter I opened
> the lid and had the following message on the screen.  Hope it helps.
> 
> 
> Feb 11 14:39:03 firefly kernel: [  253.236050] ------------[ cut here ]------------
> Feb 11 14:39:03 firefly kernel: [  253.236066] kernel BUG at fs/btrfs/transaction.c:1337!
> Feb 11 14:39:03 firefly kernel: [  253.236073] invalid opcode: 0000 [#1] SMP
> Feb 11 14:39:03 firefly kernel: [  253.236081] CPU 1
> Feb 11 14:39:03 firefly kernel: [  253.236084] Modules linked in: ebtable_nat ebtables ppdev parport_pc ipt_MASQUERADE iptable_nat nf_nat lp parport be2iscsi iscsi_boot_sysfs xt_CHECKSUM bnx2i iptable_mangle cnic uio cxgb4i cxgb4 bridge stp cxgb3i libcxgbi cxgb3 llc mdio ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr nf_conntrack_netbios_ns iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nf_conntrack_broadcast nf_conntrack_ftp ip6t_REJECT nf_conntrack_ipv6 nf_conntrack_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter xt_state ip6_tables nf_conntrack binfmt_misc xfs snd_hda_codec_si3054 snd_hda_codec_realtek arc4 snd_hda_intel snd_hda_codec snd_hwdep iwlwifi snd_seq snd_seq_device uvcvideo snd_pcm mac80211 jmb38x_ms cfg80211 videodev media iTCO_wdt memstick usblp snd_time
 r snd soundcore snd_page_alloc i2c_i801 iTCO_vendor_support v4l2_compat_ioctl32 r8169 rfkill mii serio_raw microcode joydev vhost_net macvtap macvlan tun virtio_net kvm_intel nfsd kvm lockd 
nfs_acl auth_rpcgss uinput sunrpc btrfs
> Feb 11 14:39:03 firefly kernel: zlib_deflate libcrc32c sdhci_pci sdhci mmc_core firewire_ohci firewire_core crc_itu_t nouveau ttm drm_kms_helper drm i2c_algo_bit i2c_core mxm_wmi wmi video [last unloaded: scsi_wait_scan]
> Feb 11 14:39:03 firefly kernel: [  253.236312]
> Feb 11 14:39:03 firefly kernel: [  253.236316] Pid: 2469, comm: umount Not tainted 3.2.5-3.fc16.x86_64 #1 System76, Inc. Serval Professional/Serval Professional
> Feb 11 14:39:03 firefly kernel: [  253.236329] RIP: 0010:[<ffffffffa01c2f3c>]  [<ffffffffa01c2f3c>] btrfs_commit_transaction+0x81c/0x820 [btrfs]
> Feb 11 14:39:03 firefly kernel: [  253.236355] RSP: 0018:ffff880104789d28  EFLAGS: 00010282
> Feb 11 14:39:03 firefly kernel: [  253.236361] RAX: 00000000fffffffb RBX: ffff880113cf9f00 RCX: 0000000000000000
> Feb 11 14:39:03 firefly kernel: [  253.236367] RDX: 0000000000000000 RSI: 0000000001c11000 RDI: 0000000000000000
> Feb 11 14:39:03 firefly kernel: [  253.236373] RBP: ffff880104789db8 R08: 0000000000002000 R09: 0000000000000010
> Feb 11 14:39:03 firefly kernel: [  253.236380] R10: 0000000000000000 R11: 0000000000000000 R12: ffff8801324ebc00
> Feb 11 14:39:03 firefly kernel: [  253.236386] R13: ffff880137378f78 R14: ffff880113cf9f78 R15: 0000000000000000
> Feb 11 14:39:03 firefly kernel: [  253.236393] FS:  00007f003c745800(0000) GS:ffff88013fd00000(0000) knlGS:0000000000000000
> Feb 11 14:39:03 firefly kernel: [  253.236400] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> Feb 11 14:39:03 firefly kernel: [  253.236405] CR2: 00007f4113b74000 CR3: 0000000103e51000 CR4: 00000000000406e0
> Feb 11 14:39:03 firefly kernel: [  253.236412] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> Feb 11 14:39:03 firefly kernel: [  253.236418] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Feb 11 14:39:03 firefly kernel: [  253.236425] Process umount (pid: 2469, threadinfo ffff880104788000, task ffff880138b14560)
> Feb 11 14:39:03 firefly kernel: [  253.236434] Stack:
> Feb 11 14:39:03 firefly kernel: [  253.236437]  ffff880104789d58 0000000000000001 0000000000000000 ffff880138b14560
> Feb 11 14:39:03 firefly kernel: [  253.236448]  ffffffff81090440 ffff880104789d50 ffff880104789d50 ffffffffa01c3394
> Feb 11 14:39:03 firefly kernel: [  253.236459]  7fffffffffffffff 00000000324eb000 ffff880104789d78 ffff8801324ebc00
> Feb 11 14:39:03 firefly kernel: [  253.236470] Call Trace:
> Feb 11 14:39:03 firefly kernel: [  253.236478]  [<ffffffff81090440>] ? remove_wait_queue+0x50/0x50
> Feb 11 14:39:03 firefly kernel: [  253.236494]  [<ffffffffa01c3394>] ? start_transaction+0x94/0x2a0 [btrfs]
> Feb 11 14:39:03 firefly kernel: [  253.236508]  [<ffffffffa019e21c>] btrfs_sync_fs+0x6c/0xf0 [btrfs]
> Feb 11 14:39:03 firefly kernel: [  253.236516]  [<ffffffff811a56b3>] __sync_filesystem+0x63/0x90
> Feb 11 14:39:03 firefly kernel: [  253.236524]  [<ffffffff811a575b>] sync_filesystem+0x4b/0x70
> Feb 11 14:39:03 firefly kernel: [  253.236531]  [<ffffffff8117ae2b>] generic_shutdown_super+0x3b/0xd0
> Feb 11 14:39:03 firefly kernel: [  253.236539]  [<ffffffff8117af56>] kill_anon_super+0x16/0x30
> Feb 11 14:39:03 firefly kernel: [  253.236546]  [<ffffffff8117b30c>] deactivate_locked_super+0x3c/0xa0
> Feb 11 14:39:03 firefly kernel: [  253.236552]  [<ffffffff8117bd7e>] deactivate_super+0x4e/0x70
> Feb 11 14:39:03 firefly kernel: [  253.236559]  [<ffffffff811967d5>] mntput_no_expire+0xb5/0x100
> Feb 11 14:39:03 firefly kernel: [  253.236566]  [<ffffffff8119755c>] sys_umount+0x6c/0x350
> Feb 11 14:39:03 firefly kernel: [  253.236573]  [<ffffffff81183912>] ? path_put+0x22/0x30
> Feb 11 14:39:03 firefly kernel: [  253.236581]  [<ffffffff815e9782>] system_call_fastpath+0x16/0x1b
> Feb 11 14:39:03 firefly kernel: [  253.236586] Code: e9 9b f9 ff ff 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b be fc 04 00 00 48 c7 c7 93 60 21 a0 e8 5d ae ea e0 e9 4d fb ff ff 0f 0b 0f 0b <0f> 0b 66 90 55 48 89 e5 53 48 83 ec 08 66 66 66 66 90 48 8b 77
> Feb 11 14:39:03 firefly kernel: [  253.236680] RIP  [<ffffffffa01c2f3c>] btrfs_commit_transaction+0x81c/0x820 [btrfs]
> Feb 11 14:39:03 firefly kernel: [  253.236698]  RSP <ffff880104789d28>
> Feb 11 14:39:03 firefly kernel: [  253.296027] usb 2-4: new high-speed USB device number 5 using ehci_hcd
> Feb 11 14:39:03 firefly kernel: [  253.301277] ---[ end trace b10e35848f70f893 ]---
> 
> 
> 

       reply	other threads:[~2012-02-13 14:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1328990690.2464.6.camel@firefly>
2012-02-13 14:17 ` Srivatsa S. Bhat [this message]
2012-02-13 14:41   ` Kernel bug with btrfs on laptop with external hd and suspend and resume Chris Mason
2012-02-16 21:48     ` Nathan A. Mourey II
2012-02-17 13:34       ` Chris Mason

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=4F391B83.7080703@linux.vnet.ibm.com \
    --to=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nmoureyii@ne.rr.com \
    --cc=rjw@sisk.pl \
    /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).