Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 cmdline: BOOT_IMAGE=/vmlinuz-3.6.11-5.fc17.x86_64 root=/dev/mapper/vg_wam--fc15-lv00_root ro rd.md=0 rd.dm=0 KEYTABLE=us SYSFONT=True rd.luks=0 rd.lvm.lv=vg_wam-fc15/lv00_root LANG=en_US.UTF-8 rd.lvm.lv=vg_wam-fc15/lv00_Swap rhgb quiet kernel: 3.6.11-5.fc17.x86_64 backtrace: :BUG: Bad page map in process chrome pte:ffff000008854c40 pmd:49577067 :addr:000036ce46df8468 vm_flags:00100073 anon_vma:ffff88000598aa20 mapping: (null) index:36ce46df8 :Pid: 2027, comm: chrome Not tainted 3.6.11-5.fc17.x86_64 #1 :Call Trace: : [<ffffffff811516dc>] print_bad_pte+0x1dc/0x250 : [<ffffffff811553c1>] handle_pte_fault+0xaa1/0xb10 : [<ffffffff812da3f1>] ? cpumask_any_but+0x31/0x40 : [<ffffffff8104b516>] ? flush_tlb_mm_range+0x56/0x240 : [<ffffffff8115203a>] ? tlb_flush_mmu+0x9a/0xa0 : [<ffffffff81155d39>] handle_mm_fault+0x259/0x320 : [<ffffffff81622d9c>] do_page_fault+0x15c/0x4b0 : [<ffffffff81094f3f>] ? __dequeue_entity+0x2f/0x50 : [<ffffffff810135be>] ? __switch_to+0x16e/0x420 : [<ffffffff8161db76>] ? __schedule+0x3c6/0x7a0 : [<ffffffff8161f8e5>] page_fault+0x25/0x30
Does this still happen on 3.7.9 or 3.8.2 in updates-testing?
I am unable to run the 3.7 or 3.8 kernels because it does not support my version of nVIDIA chip set in the driver. > Does this still happen on 3.7.9 or 3.8.2 in updates-testing?
(In reply to comment #2) > I am unable to run the 3.7 or 3.8 kernels because it does not support my > version of nVIDIA chip set in the driver. Which driver? Do previous kernels work with that driver? > > Does this still happen on 3.7.9 or 3.8.2 in updates-testing?
(In reply to comment #3) The latest kernel I can run is 3.6.11-5.fc17.x86_64. > (In reply to comment #2) > > I am unable to run the 3.7 or 3.8 kernels because it does not support my > > version of nVIDIA chip set in the driver. > > Which driver? Do previous kernels work with that driver? > > > > Does this still happen on 3.7.9 or 3.8.2 in updates-testing?
Which driver do you mean by driver?
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
I am sorry I could not figure out which driver to list but, I figured it out and believe it is the "nouveau" driver or one in that family that controls the display. > Which driver do you mean by driver?
(In reply to comment #7) I am sorry I do not know much about the modules that are loaded. The display does not work and using the lsmod command this is the best I can come up with. See also new bug 947210 for the just released kernel. > I am sorry I could not figure out which driver to list but, I figured it out > and believe it is the "nouveau" driver or one in that family that controls > the display. > > > Which driver do you mean by driver?
OK. We'll duplicate this bug to your new one. *** This bug has been marked as a duplicate of bug 947210 ***