You are not logged in.

#1 2014-11-14 09:35:41

mrz87
Member
Registered: 2011-05-11
Posts: 8

Kernel panic on 3.17.2, most likely related to btrfs

Hello all.

Yesterday I had a kernel panic on my ThinkPad X201. It happened while I was reindexing mu's email database from Emacs, and now every time I reboot I get the same error, and it drops me in a recovery shell.
I have a Samsung 840 EVO and use dm-crypt (I get to enter the password before the error is triggered). The stacktrace I get seems to indicate a problem with btrfs stack, up to the actual crashing function - I can provide a picture if it helps.
Is there any way I can investigate this further, either from the recovery shell or from Arch live ISO? Thanks for any feedback.

Last edited by mrz87 (2014-11-14 09:41:57)

Offline

#2 2014-11-14 17:08:45

nstgc
Member
Registered: 2014-03-17
Posts: 393

Re: Kernel panic on 3.17.2, most likely related to btrfs

Could you post the result of "journelctl | grep BTRFS" as well as "dmesg"?

Offline

#3 2014-11-16 08:40:53

mrz87
Member
Registered: 2011-05-11
Posts: 8

Re: Kernel panic on 3.17.2, most likely related to btrfs

Mmh journalctl is not available from the recovery shell, and in dmesg there's nothing more that the stracktrace from the error. I could provide that, but I tried booting the live ISO and from there mount my partition - after the `cryptsetup open` phase when mounting the partition I get the same error - subsequent tries seem to lock the device, can't ^C out of the second `mount` command I try. So yeah I'm thinking this is hosed, unless someone can chip in with some suggestions. Additionally, smartcl -t short didn't find any problems, if it can help.

Offline

#4 2014-11-16 22:37:44

weirddan455
Member
Registered: 2012-04-15
Posts: 213

Re: Kernel panic on 3.17.2, most likely related to btrfs

Try running btrfsck on it?  You'd have to cryptsetup open it first and then instead of mounting it do for example

btrfsck /dev/mapper/cryptroot

If that doesn't fix it then yea post the stacktrace and the exact error you're getting.

Offline

#5 2014-11-17 10:10:34

mrz87
Member
Registered: 2011-05-11
Posts: 8

Re: Kernel panic on 3.17.2, most likely related to btrfs

Ehi weirddan,  I found out about btrfsck earlier today and indeed I managed to mount and reboot my machine. The weird this is, the very next time I tried to reindex mu's database, I got the same error - kernel panic and errors at reboot. I've rebooted into the live ISO and ran btrfsck again, same output as before (a shitload of errors in the command output, but a mountable FS). I am thinking of backing up the most urgent things and starting from scratch - possibly with a more stable FS. I really really would like to know what is causing this though, it seems weird.


EDIT: additionally, I have the output of dmesg FULL of errors. Stuff like

[ 2570.191666] ------------[ cut here ]------------
[ 2570.191675] WARNING: CPU: 0 PID: 119 at fs/btrfs/super.c:259 __btrfs_abort_transaction+0x50/0x110 [btrfs]()
[ 2570.191677] BTRFS: Transaction aborted (error -2)
[ 2570.191678] Modules linked in: joydev mousedev snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic iTCO_wdt iTCO_vendor_support arc4 iwldvm mac80211 intel_powerclamp kvm_intel iwlwifi intel_ips kvm serio_raw psmouse i2c_i801 pcspkr cfg80211 lpc_ich thinkpad_acpi wmi thermal nvram led_class tpm_tis rfkill battery ac tpm evdev mac_hid acpi_cpufreq snd_hda_intel processor snd_hda_controller snd_hda_codec snd_hwdep snd_pcm e1000e snd_timer snd shpchp mei_me soundcore ptp mei pps_core intel_agp sch_fq_codel tp_smapi(O) thinkpad_ec(O) coretemp hwmon msr btrfs xor raid6_pq algif_skcipher af_alg dm_crypt dm_mod sd_mod crc_t10dif atkbd libps2 crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ahci libahci
[ 2570.191724]  libata scsi_mod ehci_pci ehci_hcd usbcore usb_common i8042 serio i915 button intel_gtt i2c_algo_bit video drm_kms_helper drm i2c_core
[ 2570.191735] CPU: 0 PID: 119 Comm: kworker/u8:6 Tainted: G        W  O   3.17.3-1-ARCH #1
[ 2570.191737] Hardware name: LENOVO 362611G/362611G, BIOS 6QET47WW (1.17 ) 07/14/2010
[ 2570.191750] Workqueue: btrfs-extent-refs btrfs_extent_refs_helper [btrfs]
[ 2570.191751]  0000000000000000 000000005447cd61 ffff8800379bba40 ffffffff815378be
[ 2570.191755]  ffff8800379bba88 ffff8800379bba78 ffffffff8107078d 00000000fffffffe
[ 2570.191758]  ffff8801f768e140 ffff88022e567000 ffffffffa03b5330 000000000000174a
[ 2570.191761] Call Trace:
[ 2570.191764]  [<ffffffff815378be>] dump_stack+0x4d/0x6f
[ 2570.191767]  [<ffffffff8107078d>] warn_slowpath_common+0x7d/0xa0
[ 2570.191772]  [<ffffffff8107080c>] warn_slowpath_fmt+0x5c/0x80
[ 2570.191782]  [<ffffffffa0308d10>] __btrfs_abort_transaction+0x50/0x110 [btrfs]
[ 2570.191792]  [<ffffffffa031c904>] __btrfs_free_extent+0x714/0xc80 [btrfs]
[ 2570.191796]  [<ffffffff812a9101>] ? cpumask_next_and+0x31/0x50
[ 2570.191807]  [<ffffffffa0321d7c>] __btrfs_run_delayed_refs+0x47c/0x12d0 [btrfs]
[ 2570.191810]  [<ffffffff810a51ef>] ? dequeue_entity+0x13f/0x580
[ 2570.191814]  [<ffffffff810954ce>] ? ttwu_stat+0x9e/0x110
[ 2570.191826]  [<ffffffffa0326de3>] btrfs_run_delayed_refs.part.57+0x73/0x270 [btrfs]
[ 2570.191837]  [<ffffffffa0327088>] delayed_ref_async_start+0x88/0xa0 [btrfs]
[ 2570.191851]  [<ffffffffa03689c3>] normal_work_helper+0x73/0x350 [btrfs]
[ 2570.191854]  [<ffffffff81085c7d>] ? pwq_activate_delayed_work+0x3d/0xa0
[ 2570.191867]  [<ffffffffa0369052>] btrfs_extent_refs_helper+0x12/0x20 [btrfs]
[ 2570.191871]  [<ffffffff81088df5>] process_one_work+0x145/0x400
[ 2570.191874]  [<ffffffff810893bb>] worker_thread+0x6b/0x4a0
[ 2570.191877]  [<ffffffff81089350>] ? init_pwq.part.22+0x10/0x10
[ 2570.191880]  [<ffffffff8108e2da>] kthread+0xea/0x100
[ 2570.191883]  [<ffffffff8108e1f0>] ? kthread_create_on_node+0x1b0/0x1b0
[ 2570.191886]  [<ffffffff8153d83c>] ret_from_fork+0x7c/0xb0
[ 2570.191889]  [<ffffffff8108e1f0>] ? kthread_create_on_node+0x1b0/0x1b0
[ 2570.191891] ---[ end trace 222ef6a3d2bd0765 ]---
[ 2570.191894] BTRFS warning (device dm-0): __btrfs_free_extent:5962: Aborting unused transaction(No such entry).
[ 2570.191898] BTRFS warning (device dm-0): btrfs_run_delayed_refs:2806: Aborting unused transaction(No such entry).

I'll backup what's important and nuke this installation. Hopefully this is not caused by hardware failure - smartctl seems to be happy about the health of my SSD, hopefully it's right.

Last edited by mrz87 (2014-11-17 11:06:16)

Offline

Board footer

Powered by FluxBB