From: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>
To: linux-xfs@oss.sgi.com
Subject: 3.8.7: general protection fault
Date: Thu, 02 May 2013 16:45:48 +0200 [thread overview]
Message-ID: <kltu6o$33j$1@ger.gmane.org> (raw)
I just got this issue on one of my test servers:
> [784650.537576] general protection fault: 0000 [#1] SMP DEBUG_PAGEALLOC
> [784650.540018] Modules linked in: fhgfs(O) fhgfs_client_opentk(O) nfsd xfs ext4 mbcache jbd2 crc16 mlx4_ib mlx4_core ib_umad rdma_ucm rdma_cm iw_cm ib_addr ib_uverbs sg ib_ipoib ib_cm ib_sa loop arcmsr dm_mod md_mod evdev snd_pcm snd_timer snd soundcore tpm_tis snd_page_alloc tpm psmouse tpm_bios pcspkr shpchp serio_raw pci_hotplug ib_mthca ib_mad parport_pc parport amd64_edac_mod ib_core i2c_nforce2 processor k8temp edac_core thermal_sys edac_mce_amd button i2c_core ehci_pci fuse sd_mod crc_t10dif btrfs zlib_deflate crc32c libcrc32c ata_generic e1000 pata_amd sata_nv ohci_hcd floppy ehci_hcd libata scsi_mod usbcore usb_common
> [784650.540018] CPU 1
> [784650.540018] Pid: 247, comm: kworker/1:1H Tainted: G O 3.8.7 #34 Supermicro H8DCE/H8DCE
> [784650.540018] RIP: 0010:[<ffffffffa05b38ba>] [<ffffffffa05b38ba>] xfs_trans_ail_delete_bulk+0x7a/0x1d0 [xfs]
> [784650.540018] RSP: 0018:ffff8801f29ddbf8 EFLAGS: 00010202
> [784650.540018] RAX: 0000000000000001 RBX: ffff8801f319bf00 RCX: 0000000000000000
> [784650.540018] RDX: ffff8801f29ddc68 RSI: 6b6b6b6b6b6b6b6b RDI: 6b6b6b6b6b6b6b6b
> [784650.540018] RBP: ffff8801f29ddc48 R08: 0000000000000001 R09: 0000000000000000
> [784650.540018] R10: 0000000000000001 R11: ffffffffa05ccb35 R12: 0000000000000002
> [784650.540018] R13: 0000000000000008 R14: ffff8801f319bf10 R15: ffff8801f7951550
> [784650.540018] FS: 00007f10717f4700(0000) GS:ffff8801ff600000(0000) knlGS:0000000000000000
> [784650.540018] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> [784650.540018] CR2: 00007fe7eed59000 CR3: 00000000ae5e4000 CR4: 00000000000007e0
> [784650.540018] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [784650.540018] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> [784650.540018] Process kworker/1:1H (pid: 247, threadinfo ffff8801f29dc000, task ffff8801f2f14980)
> [784650.540018] Stack:
> [784650.540018] ffff880100000000 ffff880100000000 ffff8801f29ddc60 ffff88005ff27838
> [784650.540018] ffff8801f29ddc48 ffff88014c4c0b20 ffff8801f319bf00 ffff8801f29ddc78
> [784650.540018] ffff8801f29ddc60 ffff8801f29ddd58 ffff8801f29ddca8 ffffffffa05b3320
> [784650.540018] Call Trace:
> [784650.540018] [<ffffffffa05b3320>] xfs_iflush_done+0x1c0/0x1f0 [xfs]
> [784650.540018] [<ffffffffa05b3174>] ? xfs_iflush_done+0x14/0x1f0 [xfs]
> [784650.540018] [<ffffffffa05b0d8c>] xfs_buf_do_callbacks+0x3c/0x50 [xfs]
> [784650.540018] [<ffffffffa05b145e>] xfs_buf_iodone_callbacks+0x3e/0x250 [xfs]
> [784650.540018] [<ffffffffa0554309>] xfs_buf_iodone_work+0x59/0xa0 [xfs]
> [784650.540018] [<ffffffff8107b744>] process_one_work+0x204/0x550
> [784650.540018] [<ffffffff8107b6d0>] ? process_one_work+0x190/0x550
> [784650.540018] [<ffffffff8107ddeb>] worker_thread+0x12b/0x3d0
> [784650.540018] [<ffffffff8107dcc0>] ? manage_workers+0x2f0/0x2f0
> [784650.540018] [<ffffffff810836ce>] kthread+0xee/0x100
> [784650.540018] [<ffffffff810835e0>] ? __init_kthread_worker+0x70/0x70
> [784650.540018] [<ffffffff8158dabc>] ret_from_fork+0x7c/0xb0
> [784650.540018] [<ffffffff810835e0>] ? __init_kthread_worker+0x70/0x70
> [784650.540018] Code: 00 00 48 89 f2 31 c0 31 c9 eb 19 66 0f 1f 44 00 00 4c 8b 7a 08 48 83 c2 08 41 f6 47 34 01 0f 84 ad 00 00 00 49 8b 3f 49 8b 77 08 <48> 89 77 08 48 89 3e 48 bf 00 01 10 00 00 00 ad de 48 be 00 02
> [784650.540018] RIP [<ffffffffa05b38ba>] xfs_trans_ail_delete_bulk+0x7a/0x1d0 [xfs]
> [784650.540018] RSP <ffff8801f29ddbf8>
> [784650.849642] ---[ end trace 38cae66ea9b6d0f5 ]---
> [784650.854439] BUG: sleeping function called from invalid context at kernel/rwsem.c:20
> [784650.862280] in_atomic(): 1, irqs_disabled(): 0, pid: 247, name: kworker/1:1H
[... further messages and tracing causing a panic skipped]
I can resolve line numbers if required, but I don't have any minute to
look into it myself.
Cheers,
Bernd
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-05-02 14:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 14:45 Bernd Schubert [this message]
2013-05-06 8:14 ` 3.9.0: general protection fault Bernd Schubert
2013-05-06 9:40 ` Bernd Schubert
2013-05-06 12:28 ` Dave Chinner
2013-05-06 12:47 ` Bernd Schubert
2013-05-07 1:12 ` Dave Chinner
2013-05-07 11:18 ` Bernd Schubert
2013-05-07 22:07 ` Dave Chinner
2013-05-08 17:48 ` Bernd Schubert
2013-05-09 0:41 ` Dave Chinner
2013-05-10 10:19 ` Bernd Schubert
2013-05-10 13:33 ` Eric Sandeen
2013-05-11 0:12 ` Dave Chinner
2013-06-03 16:39 ` Bernd Schubert
2013-05-09 7:16 ` Stan Hoeppner
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='kltu6o$33j$1@ger.gmane.org' \
--to=bernd.schubert@itwm.fraunhofer.de \
--cc=linux-xfs@oss.sgi.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.