Bug 722315

Summary: transmission taints kernel
Product: [Fedora] Fedora Reporter: Canyon Bliss <canyon>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: aquini, charles, gansalmon, itamar, jonathan, jspaleta, kernel-maint, madhu.chinakonda, metherid, raghusiddarth, sanjay.ankur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-10 21:36:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Canyon Bliss 2011-07-14 21:17:44 UTC 
Description of problem:
kernel seems to randomly crash when transmission is running.


Version-Release number of selected component (if applicable):

transmission-gtk 2.22 (12099)

kernel 2.6.38.8-35.fc15.x86_64

How reproducible:
If transmission is running non-stop, it usually takes about one or two days before the kernel crashes.

Steps to Reproduce:
1. Start transmission-gtk
2. wait a day or two
3.
  
Actual results:
Linux kernel crashes

Expected results:
No crash

Additional info:
 Backtrace:

BUG: Bad page state in process transmission-gt  pfn:117fe0
page:ffffea0003d3f900 count:0 mapcount:0 mapping:ff00000000000000 index:0x31d9
page flags: 0x40000000000000()
Pid: 28974, comm: transmission-gt Tainted: P            2.6.38.8-35.fc15.x86_64 #1
Call Trace:
 [<ffffffff810dd905>] ? dump_page+0xbe/0xc3
 [<ffffffff810dd9f9>] bad_page+0xef/0x104
 [<ffffffff810de7e4>] get_page_from_freelist+0x3f6/0x64b
 [<ffffffff810deb86>] __alloc_pages_nodemask+0x14d/0x77f
 [<ffffffff8111a0cf>] ? fatal_signal_pending+0x12/0x29
 [<ffffffff8111c7b6>] ? __mem_cgroup_try_charge+0x111/0x480
 [<ffffffff8111de3c>] ? lookup_page_cgroup+0x32/0x48
 [<ffffffff8111d003>] ? mem_cgroup_charge_common+0xa3/0xb5
 [<ffffffff810ecabe>] ? zone_page_state_add+0x2f/0x34
 [<ffffffff8110a321>] alloc_pages_vma+0xf5/0xfa
 [<ffffffff810f3e4b>] handle_pte_fault+0x16f/0x7a5
 [<ffffffff8147252e>] ? __slab_free+0x27/0xeb
 [<ffffffff811ed56b>] ? selinux_inode_free_security+0x67/0x70
 [<ffffffff810f13cf>] ? pmd_offset+0x19/0x3f
 [<ffffffff810f47f8>] handle_mm_fault+0x1bb/0x1ce
 [<ffffffff8147b9b0>] do_page_fault+0x358/0x37a
 [<ffffffff81042cca>] ? set_next_entity+0x46/0x99
 [<ffffffff8100885c>] ? __switch_to+0x20e/0x220
 [<ffffffff81137698>] ? cpumask_next+0x1e/0x20
 [<ffffffff81045d57>] ? finish_task_switch+0x89/0xb4
 [<ffffffff81476dce>] ? schedule+0x653/0x66a
 [<ffffffff81478c55>] page_fault+0x25/0x30
Comment 1 Rahul Sundaram 2011-07-18 03:34:34 UTC 
Reassigning to kernel
Comment 2 Canyon Bliss 2011-08-10 21:36:38 UTC 
Closing bug because it was likely a hardware problem. I was getting paging errors once or twice a day. I ran a memory test, which showed errors. Changing the settings in the BIOS seems to elevated the problem. No crashes for over a week now.