3.5.7 oops when launching chrome
Hello,
I am experiencing this oops for a while, I first encountered it when running kernel 3.5. It is easily reproducible on my machine. I have attached my kernel configuration.
The backtrace from the logs:
------------[ cut here ]------------ WARNING: at arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0xa6/0xd0() Hardware name: To Be Filled By O.E.M. empty IPI mask Modules linked in: binfmt_misc fuse nls_ascii nls_cp437 w83627ehf hwmon_vid snd_hda_codec_realtek coretemp kvm_intel kvm crc32c_intel snd_hda_intel snd_hda_codec aesni_intel snd_pcm xts snd_page_alloc snd_timer aes_i586 lrw gf128mul ablk_helper cryptd snd i2c_i801 evdev Pid: 5106, comm: chrome Not tainted 3.7.5 #2 Call Trace: [<c1031a58>] ? warn_slowpath_common+0x78/0xb0 [<c1021e06>] ? default_send_IPI_mask_logical+0xa6/0xd0 [<c1021e06>] ? default_send_IPI_mask_logical+0xa6/0xd0 [<c1031b23>] ? warn_slowpath_fmt+0x33/0x40 [<c1021e06>] ? default_send_IPI_mask_logical+0xa6/0xd0 [<c1020088>] ? native_send_call_func_ipi+0x48/0x80 [<c1079a0d>] ? smp_call_function_many+0x17d/0x220 [<c102dba0>] ? do_flush_tlb_all+0x50/0x50 [<c102dc48>] ? native_flush_tlb_others+0x28/0x30 [<c102df62>] ? flush_tlb_page+0x82/0xd0 [<c10c0c3d>] ? ptep_clear_flush+0x1d/0x30 [<c10b3592>] ? do_wp_page+0x262/0x890 [<c10b2761>] ? __do_fault+0x301/0x4a0 [<c1056ada>] ? check_preempt_curr+0x6a/0x80 [<c10b4ec0>] ? handle_pte_fault+0x2d0/0x8b0 [<c13e4bee>] ? _raw_spin_unlock_irq+0xe/0x30 [<c13e4a88>] ? rwsem_down_failed_common+0x88/0x100 [<c10b630a>] ? handle_mm_fault+0xea/0x150 [<c10292f0>] ? vmalloc_sync_all+0x10/0x10 [<c1028ffd>] ? __do_page_fault+0x12d/0x410 [<c106cafa>] ? ktime_get_ts+0x3a/0x150 [<c1079e33>] ? generic_smp_call_function_interrupt+0x73/0x160 [<c10292f0>] ? vmalloc_sync_all+0x10/0x10 [<c13e5766>] ? error_code+0x5a/0x60 [<c13e0000>] ? dump_header.isra.10+0x27/0x1bd [<c10292f0>] ? vmalloc_sync_all+0x10/0x10 ---[ end trace f4a1cce7cc9bee19 ]---
I have enabled kernel debugging hoping it would reveal more about the oops but I was not able to replicate the oops with the debug enabled kernel. Is there any other method which can help me figure out what triggers this oops ?
My hardware is: ASRock Z77 Pro4-M with 8GB of RAM, Intel I5-3470 CPU running on-board graphics.
Please put me on CC: when replying as I am not subscribed to the list.
Regards,
Darko