Bug#719277: linux-image-3.11-rc4-amd64: Kernel crashes when running Folding@Home as a system service
I was unable to get a photo of the screen output, apparently neither of
the cameras I have available can take high enough resolution shots to
actually read the output even slightly, so I carefully wrote down
(nearly) everything that was displayed and carefully typed it out into a
text file (formatting may not be *exactly* as was on screen, but should
be close enough) to send to you. The only thing not written down/typed
out was the large list of kernel modules linked to (as I didn't think it
was necessary), though if needed I can easily enough crash the kernel
again to get that list for you.
During my writing out of the terminal output I came to understand, due
to its specifically being referenced in the output, that it's not the
Folding@Home client service itself that's crashing the kernel, but the
Folding@Home core (specifically, FahCore_a4, as you'll see in the
terminal output) that's causing the kernel crash.
Anyway, I hope this might help shed some light on the problem.
BUG: Unable to handle kernel NULL pointer dereference at (null)
IP: [<ffffffffa029728c>] jbd2_journal_file_inode+0x35/0xdd [jbd2]
PGD 1399c1067 PUD 1399b6067 PMD 0
Oops: 0000 [#1] SMP
Modules linked in: [long list of modules]
CPU: 0 PID: 1963 Comm: FahCore_a4 Tainted: G I 3.11-rc4-amd64 #1 Debian 3.11~rc4-1~exp1
Hardware name: Acer Aspire 1810TZ/JM11-MS, BIOS v1.3314 08/31/2010
task: ffff880139a40801 ti: ffff880139a40000 task.ti: ffff880139a40000
RIP: 0010:[<ffffffffa029728c>] [<ffffffffa029728c>] jbd2_journal_file_inode+0x35/0xdd [jbd2]
RSP: 0018:ffff880139a41d10 EFLAGS:00010246
RAX: 0000000000000000 RBX: ffff880138f7e1c0 RCX: 0000000000000019
RDX: ffff880138f7e1c0 RSI: 0000000000000000 RDI: ffff8801382c4408
RBP: 0000000000000000 R08: ffff8801382cf218 R09: 0000000000000020
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8801382c4408
R13: ffff8801328c4408 R14: 00000000000008cc R15: 0000000000001000
FS: 00007f595ead8700(0000) GS: ffff88013fc00000(0000) knlGS: 0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000139993000 CR4: 00000000000407f0
Stack:
ffffea000404b728 ffff8801382cf0b0 0000000000000734 ffff8801382c4408
ffffffffa02b1112 0000000000001000 000000000000007f 00000000000008cc
ffff8801382cb540 ffff8801382cf0b0 ffff880139a41de0 ffff8801382c4408
Call Trace:
[<ffffffffa02b1112>] ? ext4_block_zero_page_range+0x28b/0x29c [ext4]
[<ffffffffa02b1bff>] ? ext4_truncate+0x152/0x27f [ext4]
[<ffffffff8111d48e>] ? walk_component+0x163/0x1a2
[<ffffffff8112a22c>] ? mntget+0x17/0x1c
[<ffffffff811287b9>] ? inode_change+0x2c/0x11a
[<ffffffffa02b25b2>] ? ext4_setattr+0x412/0x4b2 [ext4]
[<ffffffff81046971>] ? current_fs_time+0x2f/0x35
[<ffffffff81128a87>] ? notify_change+0x1e0/0x2cc
[<ffffffff81103b75>] ? kmem_cache_free+0x3f/0x7c
[<ffffffff811134fa>] ? do_truncate+0x63/0x87
[<ffffffff81113656>] ? vfs_truncate+0xe6/0x10d
[<ffffffff811137ce>] ? do_sys_truncate+0x3d/0x77
[<ffffffff81393d29>] ? system_call_fastpath+0x16/0x1b
Code: f5 53 48 8b 1f 48 85 db 75 11 be 49 09 00 00 48 c7 c7 14 03 2a a0 e8 70 c7 da e0 4c 89 e7 e8 3f df ff ff 85 c0 0f 85 98 00 00 <48> 39 5d 00 4c 8b 2b 0f 84 92 00 00 00 48 39 5d 08 0f 84 88 00
RIP [<ffffffffa029728c>] jbd2_journal_file_inode+0x35/0xdd [jbd2]
RSP <ffff880139a41d10>
CR2: 0000000000000000
---[ end trace 0b57ed6584cd4409 ]---
Reply to: