Bug 1370702

Summary: page dumped because: VM_BUG_ON_PAGE(1 && PageCompound(page))
Product: [Fedora] Fedora Reporter: Ralf Corsepius <rc040203>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: ajax, gansalmon, ichavero, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:23:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ralf Corsepius 2016-08-27 04:22:14 UTC
Description of problem:

All fedora kernels > 4.8.0-0.rc1.git0.1.fc25.i686 fail to boot for me.

[   97.782880] page dumped because: VM_BUG_ON_PAGE(1 && PageCompound(page))
[   97.782966] ------------[ cut here ]------------
[   97.783233] kernel BUG at ./include/linux/page-flags.h:275!
[   97.783233] invalid opcode: 0000 [#1] SMP
[   97.783233] Modules linked in: ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_broute bridge stp llc ebtable_nat ip6table_raw ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_security ip6table_mangle iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_security iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables bnep iTCO_wdt iTCO_vendor_support gpio_ich msi_wmi sparse_keymap coretemp arc4 rt2800pci joydev rt2800mmio rt2800lib rt2x00pci rt2x00mmio rt2x00lib btusb btrtl mac80211 btbcm btintel bluetooth snd_hda_codec_realtek snd_hda_codec_generic cfg80211 snd_hda_intel snd_hda_codec lpc_ich snd_hda_core eeprom_93cx6 rfkill snd_hwdep snd_seq snd_seq_device snd_pcm wmi acpi_cpufreq snd_timer snd
[   97.783233]  tpm_tis tpm_tis_core soundcore tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc i915 i2c_algo_bit drm_kms_helper serio_raw syscopyarea ums_realtek uas sysfillrect sysimgblt usb_storage fb_sys_fops drm r8169 mii fjes video
[   97.783233] CPU: 1 PID: 1075 Comm: Xorg Not tainted 4.8.0-0.rc3.git1.1.fc25.i686 #1
[   97.783233] Hardware name: MEDION E1210/E1210, BIOS 4.6.3 01/14/2009
[   97.783233] task: f3324e00 task.stack: f00d6000
[   97.783233] EIP: 0060:[<f7cf32fa>] EFLAGS: 00013292 CPU: 1
[   97.783233] EIP is at drm_pci_alloc+0xca/0x1b0 [drm]
[   97.783233] EAX: 00000000 EBX: 00004000 ECX: f73c5020 EDX: 00000007
[   97.783233] ESI: f0265c40 EDI: dc018db0 EBP: f00d7be4 ESP: f00d7bc0
[   97.783233]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[   97.783233] CR0: 80050033 CR2: b6cfc000 CR3: 3179c000 CR4: 000006d0
[   97.783233] Stack:
[   97.783233]  f0290000 00000000 f46ca868 f0290000 024040c0 779ceb52 00000000 f6df7680
[   97.783233]  f6df771c f00d7bfc f7f5c8e3 00000100 f6d77000 f10c0b40 f10c0f00 f00d7c28
[   97.783233]  f7fa9a1e 00000000 00000001 00000000 f7fa22ff f3470000 f6df7680 00000003
[   97.783233] Call Trace:
[   97.783233]  [<f7f5c8e3>] i915_gem_object_attach_phys+0xc3/0x130 [i915]
[   97.783233]  [<f7fa9a1e>] intel_prepare_plane_fb+0x1be/0x2b0 [i915]
[   97.783233]  [<f7fa22ff>] ? intel_atomic_commit+0x28f/0x530 [i915]
[   97.783233]  [<f7fa9860>] ? intel_crtc_restore_mode+0xc0/0xc0 [i915]
[   97.783233]  [<f7d775ad>] drm_atomic_helper_prepare_planes+0x3d/0xc0 [drm_kms_helper]
[   97.783233]  [<f7fa2313>] intel_atomic_commit+0x2a3/0x530 [i915]
[   97.783233]  [<f7d0827a>] ? drm_atomic_get_crtc_state+0x5a/0xe0 [drm]
[   97.783233]  [<dc1b8f4a>] ? kmemdup+0x2a/0x40
[   97.783233]  [<f7f87e30>] ? intel_plane_duplicate_state+0x30/0x40 [i915]
[   97.783233]  [<f7d08fe2>] drm_atomic_commit+0x32/0x60 [drm]
[   97.783233]  [<f7d78425>] drm_atomic_helper_update_plane+0xc5/0x110 [drm_kms_helper]
[   97.783233]  [<f7cf7918>] __setplane_internal+0x1e8/0x260 [drm]
[   97.783233]  [<f7cf7b0a>] drm_mode_cursor_common+0x17a/0x3a0 [drm]
[   97.783233]  [<f7cfc160>] ? drm_mode_setcrtc+0x5e0/0x5e0 [drm]
[   97.783233]  [<f7cfc1b7>] drm_mode_cursor_ioctl+0x57/0x70 [drm]
[   97.783233]  [<f7cedca1>] drm_ioctl+0x2e1/0x4f0 [drm]
[   97.783233]  [<dc336866>] ? avc_has_extended_perms+0x196/0x650
[   97.783233]  [<dc336715>] ? avc_has_extended_perms+0x45/0x650
[   97.783233]  [<f7cfc160>] ? drm_mode_setcrtc+0x5e0/0x5e0 [drm]
[   97.783233]  [<dc0985c7>] ? sched_clock_cpu+0x107/0x170
[   97.783233]  [<dc098389>] ? sched_clock_local+0x49/0x180
[   97.783233]  [<dc08d3d2>] ? __might_sleep+0x32/0xa0
[   97.783233]  [<dc0985c7>] ? sched_clock_cpu+0x107/0x170
[   97.783233]  [<f7ced9c0>] ? drm_getclient+0x70/0x70 [drm]
[   97.783233]  [<dc227061>] do_vfs_ioctl+0x91/0x8a0
[   97.783233]  [<dc33885e>] ? __inode_security_revalidate+0x5e/0x80
[   97.783233]  [<dc33b729>] ? selinux_file_ioctl+0x109/0x1e0
[   97.783233]  [<dc3332cc>] ? security_file_ioctl+0x3c/0x60
[   97.783233]  [<dc2278d0>] SyS_ioctl+0x60/0x70
[   97.783233]  [<dc001e15>] do_fast_syscall_32+0xa5/0x230
[   97.783233]  [<dc801733>] sysenter_past_esp+0x4c/0x7f
[   97.783233] Code: 00 8d 82 00 00 00 40 c1 e8 0c 8d 0c 80 a1 84 84 65 dd 8d 04 c8 8b 08 80 e5 40 74 15 90 8d 74 26 00 ba cc a3 d1 f7 e8 b6 5c 4d e4 <0f> 0b 8d 74 26 00 8b 48 14 83 e1 01 75 e8 81 c2 00 10 00 40 66
[   97.783233] EIP: [<f7cf32fa>] drm_pci_alloc+0xca/0x1b0 [drm] SS:ESP 0068:f00d7bc0
[   98.210398] ---[ end trace 81c7f9d2e3776840 ]---


Version-Release number of selected component (if applicable):
kernels > 4.8.0-0.rc1.git0.1.fc25.i686


Additional info:
Last bootable fc25-kernel was kernel-4.8.0-0.rc1.git0.1.fc25.i686.

Comment 1 Ralf Corsepius 2016-08-30 04:49:43 UTC
FYI: kernel-4.8.0-0.rc4.git0.1.fc25.i686 boots.

Comment 2 Ralf Corsepius 2016-08-30 05:06:38 UTC
I do not share Laura's view that this problem caused by xorg-x11-drv-intel, because

- kernel-4.8.0-0.rc4.git0.1.fc25.i686 boots
- kernel-4.8.0-0.rc2.git3.1.fc25.i686 fails to boot

with an otherwise unchanged installation, esp. with identical
xorg-x11-drv-intel-2.99.917-25.20160712.fc25.i686

Comment 3 Josh Boyer 2016-08-30 10:59:30 UTC
(In reply to Ralf Corsepius from comment #2)
> I do not share Laura's view that this problem caused by xorg-x11-drv-intel,
> because
> 
> - kernel-4.8.0-0.rc4.git0.1.fc25.i686 boots
> - kernel-4.8.0-0.rc2.git3.1.fc25.i686 fails to boot
> 
> with an otherwise unchanged installation, esp. with identical
> xorg-x11-drv-intel-2.99.917-25.20160712.fc25.i686

https://fedoraproject.org/wiki/KernelBugTriage#Video_Subsystem_bugs

Comment 4 Fedora End Of Life 2017-11-16 18:51:18 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2017-12-12 10:23:45 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.