Both plasma and icewm sessions freeze attempting startx. Remote login does work. Has this happened to anyone else lately? I did same on a different but similar machine yesterday, and its plasma worked fine.
This is dmesg tail:
[ 127.769897] ------------[ cut here ]------------ [ 127.769929] kernel BUG at include/linux/page-flags.h:272! [ 127.769958] invalid opcode: 0000 [#1] SMP [ 127.769985] Modules linked in: fuse ppdev msdos fat snd_intel8x0 snd_ac97_codec ac97_bus snd_seq i915 tg3 snd_seq_device snd_pcm snd_timer snd video i2c_algo_bit drm_kms_helper drm sata_sil ptp iTCO_wdt soundcore gpio_ich pps_core iTCO_vendor_support parport_pc lpc_ich parport dcdbas i2c_i801 fjes acpi_cpufreq tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc serio_raw ata_generic pata_acpi [ 127.770273] CPU: 1 PID: 1005 Comm: Xorg Not tainted 4.5.2-301.fc24.i686+PAE #1 [ 127.770310] Hardware name: Dell Inc. OptiPlex GX280 /0G5611, BIOS A08 03/03/2006 [ 127.770361] task: f0fce300 ti: f2562000 task.ti: f2562000 [ 127.770391] EIP: 0060:[<f81c0e42>] EFLAGS: 00013286 CPU: 1 [ 127.770446] EIP is at drm_pci_alloc+0xc2/0x1b0 [drm] [ 127.770473] EAX: 00000000 EBX: 00004000 ECX: f7770848 EDX: 00000007 [ 127.770506] ESI: f33e1fe0 EDI: c0419f90 EBP: f2563b90 ESP: f2563b6c [ 127.770538] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 127.770566] CR0: 80050033 CR2: b68d9000 CR3: 323019a0 CR4: 000006f0 [ 127.770600] Stack: [ 127.770612] 024040c0 00000000 f51d9864 f88ba688 024040c0 04cf9711 00000000 f256c480 [ 127.770631] f256c4f8 f2563ba8 f882f75f 00000100 f4242a00 f24509c0 f2450900 f2563bdc [ 127.770631] f88768db f4000000 f4753800 f72f9000 f885e501 f6ce2c00 f7350400 00000000 [ 127.770631] Call Trace: [ 127.770631] [<f882f75f>] i915_gem_object_attach_phys+0xef/0x190 [i915] [ 127.770631] [<f88768db>] intel_prepare_plane_fb+0x18b/0x300 [i915] [ 127.770631] [<f885e501>] ? intel_crtc_destroy+0x11/0x60 [i915] [ 127.770631] [<f85b8295>] drm_atomic_helper_prepare_planes+0x45/0xb0 [drm_kms_helper] [ 127.770631] [<f886dfc9>] intel_atomic_commit+0x249/0x16e0 [i915] [ 127.770631] [<f88708c6>] ? intel_atomic_check+0x886/0x10a0 [i915] [ 127.770631] [<c05c63fd>] ? __kmalloc_track_caller+0x18d/0x230 [ 127.770631] [<f8870040>] ? intel_link_compute_m_n+0x50/0x50 [i915] [ 127.770631] [<f81d5e9f>] ? drm_atomic_check_only+0x19f/0x670 [drm] [ 127.770631] [<f81d5664>] ? drm_atomic_get_crtc_state+0x54/0xc0 [drm] [ 127.770631] [<c058c7ca>] ? kmemdup+0x2a/0x40 [ 127.770631] [<f886dd80>] ? modeset_get_crtc_power_domains+0x140/0x140 [i915] [ 127.770631] [<f81d63a4>] drm_atomic_commit+0x34/0x60 [drm] [ 127.770631] [<f85b8c6c>] drm_atomic_helper_update_plane+0xbc/0x100 [drm_kms_helper] [ 127.770631] [<f85b8bb0>] ? drm_atomic_helper_wait_for_vblanks+0x210/0x210 [drm_kms_helper] [ 127.770631] [<f81c5eeb>] __setplane_internal+0x1eb/0x230 [drm] [ 127.770631] [<f81c60ae>] drm_mode_cursor_common+0x17e/0x3a0 [drm] [ 127.770631] [<f81ca3b0>] ? drm_mode_setcrtc+0x570/0x570 [drm] [ 127.770631] [<f81ca407>] drm_mode_cursor_ioctl+0x57/0x70 [drm] [ 127.770631] [<f81bb3f9>] drm_ioctl+0x149/0x4f0 [drm] [ 127.770631] [<f81ca3b0>] ? drm_mode_setcrtc+0x570/0x570 [drm] [ 127.770631] [<c059bb67>] ? __do_fault+0x67/0x180 [ 127.770631] [<c059fbf4>] ? handle_mm_fault+0x204/0x18a0 [ 127.770631] [<f81bb2b0>] ? drm_getmap+0xc0/0xc0 [drm] [ 127.770631] [<c05ec381>] do_vfs_ioctl+0x91/0x6f0 [ 127.770631] [<c05a6cca>] ? do_mmap+0x24a/0x320 [ 127.770631] [<c05eca48>] SyS_ioctl+0x68/0x80 [ 127.770631] [<c040388f>] do_fast_syscall_32+0x8f/0x140 [ 127.770631] [<c0b2f49b>] sysenter_past_esp+0x40/0x61 [ 127.770631] Code: 70 8d 82 00 00 00 40 c1 e8 0c 8d 0c 80 a1 84 e3 04 c1 8d 04 c8 8b 08 80 e5 40 74 7d 90 8d 74 26 00 ba 18 75 1e f8 e8 be 86 3d c8 <0f> 0b 8d 74 26 00 8d 55 ec 8d 45 e4 e8 dd 8f 25 c8 84 c0 0f 84 [ 127.770631] EIP: [<f81c0e42>] drm_pci_alloc+0xc2/0x1b0 [drm] SS:ESP 0068:f2563b6c [ 127.824288] ---[ end trace a8650b456bdc8e85 ]---
Felix Miata composed on 2016-04-28 03:27 (UTC-0400):
Both plasma and icewm sessions freeze attempting startx. Remote login does work. Has this happened to anyone else lately? I did same on a different but similar machine yesterday, and its plasma worked fine.
This is dmesg tail:
Same with F25 on same machine:
[ 83.617160] ------------[ cut here ]------------ [ 83.617194] kernel BUG at include/linux/page-flags.h:272! [ 83.617225] invalid opcode: 0000 [#1] SMP [ 83.617252] Modules linked in: rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache fuse iTCO_wdt iTCO_vendor_support gpio_ich ppdev i915 msdos fat video i2c_algo_bit drm_kms_helper snd_intel8x0 snd_ac97_codec tg3 ac97_bus snd_seq snd_seq_device snd_pcm snd_timer ptp sata_sil snd pps_core drm soundcore parport_pc dcdbas lpc_ich parport i2c_i801 fjes acpi_cpufreq tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc serio_raw ata_generic pata_acpi [ 83.617569] CPU: 1 PID: 957 Comm: Xorg Not tainted 4.6.0-0.rc5.git0.1.fc25.i686+PAE #1 [ 83.617609] Hardware name: Dell Inc. OptiPlex GX280 /0G5611, BIOS A08 03/03/2006 [ 83.617658] task: f1e0d280 ti: f1e3e000 task.ti: f1e3e000 [ 83.617688] EIP: 0060:[<f81bc050>] EFLAGS: 00013296 CPU: 1 [ 83.617744] EIP is at drm_pci_alloc+0x110/0x1a0 [drm] [ 83.617773] EAX: 00000000 EBX: 00004000 ECX: f777088c EDX: 00000007 [ 83.617806] ESI: f1e6c9a0 EDI: c0430170 EBP: f1e3fb84 ESP: f1e3fb60 [ 83.617841] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 83.617871] CR0: 80050033 CR2: b592f000 CR3: 31efca00 CR4: 000006f0 [ 83.617905] Stack: [ 83.618010] 024040c0 00000000 f701a864 f88287a8 024040c0 28c10057 00000000 f1f1d680 [ 83.618010] f1f1d6f8 f1e3fb9c f879c30f 00000100 f6353000 f1f79000 f1f790c0 f1e3fbd0 [ 83.618010] f87e477b f1f5f400 f6948000 f2acc000 f6430000 f87cc101 f3f52000 00000000 [ 83.618010] Call Trace: [ 83.618010] [<f879c30f>] i915_gem_object_attach_phys+0xef/0x190 [i915] [ 83.618010] [<f87e477b>] intel_prepare_plane_fb+0x18b/0x300 [i915] [ 83.618010] [<f87cc101>] ? intel_update_cursor_plane+0x51/0x70 [i915] [ 83.618010] [<f85d9395>] drm_atomic_helper_prepare_planes+0x45/0xb0 [drm_kms_helper] [ 83.618010] [<f87dbcec>] intel_atomic_commit+0x27c/0x1970 [i915] [ 83.618010] [<f87de1ae>] ? intel_atomic_check+0x30e/0x10e0 [i915] [ 83.618010] [<c05cdc00>] ? __kmalloc_track_caller+0xa0/0x230 [ 83.618010] [<f87ddea0>] ? intel_link_compute_m_n+0x50/0x50 [i915] [ 83.618010] [<f81d123f>] ? drm_atomic_check_only+0x19f/0x670 [drm] [ 83.618010] [<f81d09c4>] ? drm_atomic_get_crtc_state+0x54/0xc0 [drm] [ 83.618010] [<c059300a>] ? kmemdup+0x2a/0x40 [ 83.618010] [<f87dba70>] ? modeset_get_crtc_power_domains+0x170/0x170 [i915] [ 83.618010] [<f81d1744>] drm_atomic_commit+0x34/0x60 [drm] [ 83.618010] [<f85d9e3c>] drm_atomic_helper_update_plane+0xbc/0x100 [drm_kms_helper] [ 83.618010] [<f85d9d80>] ? drm_atomic_helper_wait_for_vblanks+0x210/0x210 [drm_kms_helper] [ 83.618010] [<f81c1d6b>] __setplane_internal+0x1eb/0x230 [drm] [ 83.618010] [<f81c1f2e>] drm_mode_cursor_common+0x17e/0x3a0 [drm] [ 83.618010] [<f81c5710>] ? drm_mode_setcrtc+0x570/0x570 [drm] [ 83.618010] [<f81c5767>] drm_mode_cursor_ioctl+0x57/0x70 [drm] [ 83.618010] [<f81b65e9>] drm_ioctl+0x149/0x4f0 [drm] [ 83.618010] [<f81c5710>] ? drm_mode_setcrtc+0x570/0x570 [drm] [ 83.618010] [<c05a3067>] ? __do_fault+0x67/0x180 [ 83.618010] [<c05a717e>] ? handle_mm_fault+0x22e/0x1920 [ 83.618010] [<f81b64a0>] ? drm_getmap+0xc0/0xc0 [drm] [ 83.618010] [<c05f4121>] do_vfs_ioctl+0x91/0x6f0 [ 83.618010] [<c05ae0aa>] ? do_mmap+0x24a/0x320 [ 83.618010] [<c05f47e8>] SyS_ioctl+0x68/0x80 [ 83.618010] [<c040388f>] do_fast_syscall_32+0x8f/0x150 [ 83.618010] [<c0b4092a>] sysenter_past_esp+0x47/0x75 [ 83.618010] Code: 0c 8d 0c 80 a1 84 e3 06 c1 8d 04 c8 8b 08 80 e5 40 75 0e 8b 48 14 81 c2 00 10 00 00 83 e1 01 74 ca ba b4 25 1e f8 e8 80 48 3e c8 <0f> 0b 8d b6 00 00 00 00 8d 55 ec 8d 45 e4 e8 ad 3f 27 c8 84 c0 [ 83.618010] EIP: [<f81bc050>] drm_pci_alloc+0x110/0x1a0 [drm] SS:ESP 0068:f1e3fb60 [ 83.683499] ---[ end trace e1280ed67f050734 ]---
On Thu, 2016-04-28 at 04:54 -0400, Felix Miata wrote:
Felix Miata composed on 2016-04-28 03:27 (UTC-0400):
Both plasma and icewm sessions freeze attempting startx. Remote login does work. Has this happened to anyone else lately? I did same on a different but similar machine yesterday, and its plasma worked fine.
This is dmesg tail:
Same with F25 on same machine:
32-bit is fairly marginal at present, it's explicitly not supported by kernel team and does not block releases for F24+. Probably the best thing to do would be to file a bug *upstream* (kernel.org or freedesktop.org), as I'm not sure it'll get much priority if filed downstream.
I haven't seen this, but then I haven't booted any 32-bit images on metal lately.