libreport version: 2.0.10 cmdline: BOOT_IMAGE=/vmlinuz-3.4.6-1.fc16.x86_64 root=/dev/mapper/VGAlpine-LVRoot ro rd.lvm.lv=VGAlpine/LVRoot rd.md=0 rd.dm=0 LANG=en_GB.UTF-8 rd.lvm.lv=VGAlpine/LVSwap quiet SYSFONT=latarcyrheb-sun16 rhgb KEYTABLE=uk rd.luks=0 backtrace: :BUG: Bad page state in process firefox pfn:10563e :page:ffffea0004158f80 count:0 mapcount:0 mapping: (null) index:0x7fe5a7d78 :page flags: 0x40000000000014(referenced|dirty) :Modules linked in: fuse be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i libcxgbi cxgb3 ebtable_nat ebtables mdio lockd ib_iser rfcomm rdma_cm ib_cm iw_cm ib_sa ib_mad bnep ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_REJECT nf_conntrack_ipv6 xt_physdev it87 hwmon_vid nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ip6table_filter ip6_tables snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec ppdev snd_hwdep snd_seq parport_pc vhost_net snd_seq_device parport snd_pcm macvtap btusb edac_core r8169 macvlan sp5100_tco snd_timer snd soundcore snd_page_alloc tun mii bluetooth kvm_amd kvm i2c_piix4 uinput edac_mce_amd shpchp k10temp sunrpc microcode rfkill binfmt_misc firewire_ohci firewire_core ata_generic pata_acpi crc_itu_t pata_jmicron wmi radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan] :Pid: 21540, comm: firefox Tainted: G W 3.4.6-1.fc16.x86_64 #1 :Call Trace: : [<ffffffff81129b2f>] bad_page+0xbf/0x110 : [<ffffffff8112b24c>] get_page_from_freelist+0x6dc/0x8a0 : [<ffffffff8112b5cb>] __alloc_pages_nodemask+0x1bb/0x950 : [<ffffffff8112f6d6>] ? release_pages+0x1d6/0x220 : [<ffffffff81165703>] alloc_pages_vma+0xb3/0x190 : [<ffffffff81148d52>] handle_pte_fault+0x732/0xad0 : [<ffffffff811494a8>] handle_mm_fault+0x1f8/0x310 : [<ffffffff81600102>] do_page_fault+0x142/0x4f0 : [<ffffffff8108fded>] ? set_next_entity+0x9d/0xb0 : [<ffffffff810135da>] ? __switch_to+0x17a/0x410 : [<ffffffff815faf34>] ? __schedule+0x3c4/0x7c0 : [<ffffffff815fcca5>] page_fault+0x25/0x30
I wrote a comment in abrt but it got lost: is this a bug? I see a comment I made for a recent oops report (bug 845343) did not make it to bugzilla either. Here is the comment, pasted from ~/.abrt/spool: Firefox memory use went crazy, mainly due to some yahoo mail/toolbar javascript suddenly eating up nearly 2GB (on a machine with two users logged in, leading to: $ free -m total used free shared buffers cached Mem: 7479 6477 1002 0 19 284 -/+ buffers/cache: 6174 1305 Swap: 6143 2 6141 The kernel is tainted by an earlier warning due to bug 715137.
These sorts of bugs are a really obscure, and a lot of the time when we see them they are indicative of some kind of hardware fault (like memory going bad). That said, they can also occur from memory corruption caused by actual bugs. Can you update to 3.5 and see if you can reproduce it ? (If you have time, an overnight run of memtest86 might be a good thing too, just to rule out bad memory)
disregard the comment about 3.5 for now, we haven't pushed an update for 16 yet. There's a few bugs we want to get worked out in f17 before we backport.
Did memtest turn up anything? Otherwise you can grab the current F17 kernel and see if it fixes the issue for you.
Memtest didn't turn up anything. Haven't had the oops again, but then I haven't had the runaway firefox memory again.
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.