Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Oops in arc_space_return after resume from hibernate-ram #1201

Closed
simonbuehler opened this issue Jan 14, 2013 · 6 comments
Closed

Oops in arc_space_return after resume from hibernate-ram #1201

simonbuehler opened this issue Jan 14, 2013 · 6 comments
Milestone

Comments

@simonbuehler
Copy link

hi,

got this after wakeup, how can this be debugged?

Jan 14 10:08:25 filepile kernel: [  140.563898] BUG: unable to handle kernel NULL pointer dereference at           (null)
Jan 14 10:08:25 filepile kernel: [  140.565704] IP: [<ffffffffa00ef290>] arc_space_return+0x1077/0x2143 [zfs]
Jan 14 10:08:25 filepile kernel: [  140.567240] PGD 0 
Jan 14 10:08:25 filepile kernel: [  140.568732] Oops: 0000 [#1] SMP 
Jan 14 10:08:25 filepile kernel: [  140.570266] Modules linked in: ipv6 joydev sr_mod cdrom snd_hda_codec_hdmi snd_hda_codec_realtek arc4 rt2800pci rt2800lib crc_ccitt rt2x00pci rt2x00lib i915 mac80211 drm_kms_helper drm coretemp cfg80211 kvm_intel rfkill kvm xhci_hcd snd_hda_intel snd_hda_codec r8168(O) i2c_algo_bit acpi_cpufreq mperf video i2c_i801 ghash_clmulni_intel eeprom_93cx6 usb_storage processor button microcode thermal_sys snd_hwdep snd_pcm snd_timer snd snd_page_alloc zfs(PO) zavl(PO) zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zlib_deflate usbhid uhci_hcd ehci_hcd usbcore usb_common dm_crypt dm_mod
Jan 14 10:08:25 filepile kernel: [  140.576014] CPU 1 
Jan 14 10:08:25 filepile kernel: [  140.576035] Pid: 905, comm: z_wr_int/1 Tainted: P           O 3.6.11-gentoo #4 MotherBoard By ZOTAC MotherBoard H67ITX-D-E/H67ITX-D-E
Jan 14 10:08:25 filepile kernel: [  140.579601] RIP: 0010:[<ffffffffa00ef290>]  [<ffffffffa00ef290>] arc_space_return+0x1077/0x2143 [zfs]
Jan 14 10:08:25 filepile kernel: [  140.581492] RSP: 0018:ffff880231261c30  EFLAGS: 00010246
Jan 14 10:08:25 filepile kernel: [  140.583196] RAX: ffffffffa00ef270 RBX: ffff88023135aea8 RCX: 0000000000000000
Jan 14 10:08:25 filepile kernel: [  140.585092] RDX: 0000000000000000 RSI: 0000000000020000 RDI: ffff88023135aea8
Jan 14 10:08:25 filepile kernel: [  140.586803] RBP: 0000000000000000 R08: 0000000000000018 R09: 00000000000003e1
Jan 14 10:08:25 filepile kernel: [  140.588488] R10: 000000000097c3c5 R11: 0000000000000246 R12: ffff880223999960
Jan 14 10:08:25 filepile kernel: [  140.590156] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Jan 14 10:08:25 filepile kernel: [  140.591838] FS:  0000000000000000(0000) GS:ffff88023fa80000(0000) knlGS:0000000000000000
Jan 14 10:08:25 filepile kernel: [  140.593549] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Jan 14 10:08:25 filepile kernel: [  140.595249] CR2: 0000000000000000 CR3: 000000000160b000 CR4: 00000000000407e0
Jan 14 10:08:25 filepile kernel: [  140.596953] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jan 14 10:08:25 filepile kernel: [  140.598666] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jan 14 10:08:25 filepile kernel: [  140.600379] Process z_wr_int/1 (pid: 905, threadinfo ffff880231260000, task ffff88023e988f00)
Jan 14 10:08:25 filepile kernel: [  140.602127] Stack:
Jan 14 10:08:25 filepile kernel: [  140.603869]  0000000200000000 ffff88023fa8d650 ffff88023135aea8 ffff88023135aea8
Jan 14 10:08:25 filepile kernel: [  140.605694]  ffff88023135aea8 ffff88023135aea8 0000000000000000 0000000000000000
Jan 14 10:08:25 filepile kernel: [  140.607545]  0000000000100000 ffffffffa016e350 ffff88023135aea8 00000010a0169ec7
Jan 14 10:08:25 filepile kernel: [  140.609420] Call Trace:
Jan 14 10:08:25 filepile kernel: [  140.611309]  [<ffffffffa016e350>] ? zio_worst_error+0x7ec/0xd34 [zfs]
Jan 14 10:08:25 filepile kernel: [  140.613236]  [<ffffffffa016e515>] ? zio_worst_error+0x9b1/0xd34 [zfs]
Jan 14 10:08:25 filepile kernel: [  140.615170]  [<ffffffffa0169ec7>] ? zil_vdev_offline+0x14f/0x349 [zfs]
Jan 14 10:08:25 filepile kernel: [  140.617118]  [<ffffffffa016e515>] ? zio_worst_error+0x9b1/0xd34 [zfs]
Jan 14 10:08:25 filepile kernel: [  140.619082]  [<ffffffffa016aa09>] ? zio_execute+0xf1/0x262 [zfs]
Jan 14 10:08:25 filepile kernel: [  140.621054]  [<ffffffff81050d0f>] ? __wake_up+0x35/0x46
Jan 14 10:08:25 filepile kernel: [  140.623044]  [<ffffffffa006dc52>] ? taskq_destroy+0x515/0x691 [spl]
Jan 14 10:08:25 filepile kernel: [  140.625059]  [<ffffffff810547bf>] ? try_to_wake_up+0x1fd/0x20f
Jan 14 10:08:25 filepile kernel: [  140.627080]  [<ffffffff810547d1>] ? try_to_wake_up+0x20f/0x20f
Jan 14 10:08:25 filepile kernel: [  140.629110]  [<ffffffffa006d99b>] ? taskq_destroy+0x25e/0x691 [spl]
Jan 14 10:08:25 filepile kernel: [  140.631155]  [<ffffffffa006d99b>] ? taskq_destroy+0x25e/0x691 [spl]
Jan 14 10:08:25 filepile kernel: [  140.633179]  [<ffffffff8104a5c7>] ? kthread+0x81/0x89
Jan 14 10:08:25 filepile kernel: [  140.635210]  [<ffffffff813d74b4>] ? kernel_thread_helper+0x4/0x10
Jan 14 10:08:25 filepile kernel: [  140.637252]  [<ffffffff8104a546>] ? kthread_freezable_should_stop+0x52/0x52
Jan 14 10:08:25 filepile kernel: [  140.639309]  [<ffffffff813d74b0>] ? gs_change+0xb/0xb
Jan 14 10:08:25 filepile kernel: [  140.641360] Code: 5b 5d 41 5c 41 5d 41 5e 41 5f c3 41 55 41 54 55 53 48 89 fb 48 83 ec 28 4c 8b a7 48 01 00 00 83 bf 78 02 00 00 00 4d 8b 6c 24 18 <49> 8b 6d 00 75 34 48 8b 47 50 48 8b 10 48 89 55 00 48 8b 40 08 
Jan 14 10:08:25 filepile kernel: [  140.646115] RIP  [<ffffffffa00ef290>] arc_space_return+0x1077/0x2143 [zfs]
Jan 14 10:08:25 filepile kernel: [  140.648450]  RSP <ffff880231261c30>
Jan 14 10:08:25 filepile kernel: [  140.650773] CR2: 0000000000000000
Jan 14 10:08:25 filepile kernel: [  140.653109] ---[ end trace 10f7feae09674bd5 ]---
@behlendorf
Copy link
Contributor

This might be enough. Is it easily reproducible after resuming from hibernation?

@simonbuehler
Copy link
Author

not really, i'll report back in case

@FransUrbo
Copy link
Contributor

Related to #260?

@FransUrbo
Copy link
Contributor

Is this still a problem, or could/should it be closed?

@behlendorf
Copy link
Contributor

I suspect this is still a legitimate, although unlikely problem. Let's leave it open.

@behlendorf behlendorf removed this from the 0.7.0 milestone Oct 7, 2014
@behlendorf behlendorf added Bug - Minor and removed Bug labels Oct 7, 2014
@behlendorf behlendorf added this to the 0.9.0 milestone Mar 26, 2016
@behlendorf
Copy link
Contributor

Closing as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants