Bug 1597022 - [abrt] drm_modeset_unlock: kernel BUG at mm/slub.c:296! [drm] [NEEDINFO]
Summary: [abrt] drm_modeset_unlock: kernel BUG at mm/slub.c:296! [drm]
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 27
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:534a712852b85cba14e4c4b30d1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-01 15:15 UTC by Babak Farrokhi
Modified: 2018-08-29 15:07 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-08-29 15:07:20 UTC
Type: ---
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
File: dmesg (112.32 KB, text/plain)
2018-07-01 15:15 UTC, Babak Farrokhi
no flags Details

Description Babak Farrokhi 2018-07-01 15:15:32 UTC
Additional info:
reporter:       libreport-2.9.3
kernel BUG at mm/slub.c:296!
invalid opcode: 0000 [#1] SMP PTI
Modules linked in: rfcomm fuse nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables bnep vmw_vsock_vmci_transport vsock sunrpc crct10dif_pclmul btusb crc32_pclmul btrtl ghash_clmulni_intel btbcm btintel bluetooth intel_rapl_perf ecdh_generic rfkill joydev vmw_balloon vmw_vmci i2c_piix4 shpchp vmwgfx crc32c_intel drm_kms_helper ttm mptspi serio_raw scsi_transport_spi mptscsih drm e1000 mptbase
 ata_generic pata_acpi
CPU: 0 PID: 2308 Comm: python Not tainted 4.17.3-100.fc27.x86_64 #1
Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 05/19/2017
RIP: 0010:__slab_free+0x18a/0x300
RSP: 0018:ffffbdce42a078e0 EFLAGS: 00010246
RAX: ffff972f75126a00 RBX: ffff972f75126a00 RCX: 000000018040003f
RDX: ffff972f75126a00 RSI: fffff26cc2d44900 RDI: ffff972f7f807180
RBP: ffffbdce42a07980 R08: 0000000000000001 R09: ffffffffc01fa607
R10: fffff26cc2d44900 R11: 0000000000000001 R12: ffff972f7f807180
R13: fffff26cc2d44900 R14: ffff972f75126a00 R15: ffff972ef5940000
FS:  00007f5f289dc4c0(0000) GS:ffff972f7a600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000563847600000 CR3: 000000000e0f8002 CR4: 00000000001606f0
Call Trace:
 ? drm_modeset_unlock+0x16/0x40 [drm]
 ? vmwgfx_set_config_internal.constprop.4+0x151/0x180 [vmwgfx]
 ? _cond_resched+0x15/0x40
 ? vmw_fb_set_par+0x287/0x4e0 [vmwgfx]
 vmw_fb_set_par+0x287/0x4e0 [vmwgfx]
 ? fb_set_var+0x179/0x3e0
 ? vmw_fb_kms_detach.constprop.3+0x110/0x110 [vmwgfx]
 fb_set_var+0x179/0x3e0
 ? selinux_inode_permission+0xe0/0x1a0
 do_fb_ioctl+0x4a2/0x620
 ? ns_capable_common+0x63/0x80
 ? vt_ioctl+0x6ca/0x1120
 ? do_vfs_ioctl+0xa4/0x620
 ? do_fb_ioctl+0x620/0x620
 do_vfs_ioctl+0xa4/0x620
 ksys_ioctl+0x70/0x80
 __x64_sys_ioctl+0x16/0x20
 do_syscall_64+0x5b/0x160
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7f5f2775d0f7
RSP: 002b:00007ffd54fdb998 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000558fef5d1d30 RCX: 00007f5f2775d0f7
RDX: 00007ffd54fdb9b0 RSI: 0000000000004601 RDI: 0000000000000004
RBP: 0000000000000000 R08: 0000000000000006 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 0000558fef537c50
R13: 00007ffd54fdba50 R14: 00000000000002d0 R15: 0000000000000000
Code: fe ff ff 44 0f b6 bd 7f ff ff ff 80 7d ab 00 79 05 45 84 ff 74 7b 48 83 c4 78 5b 41 5c 41 5d 41 5e 41 5f 5d 49 8d 65 f0 41 5d c3 <0f> 0b 4c 89 d0 4c 89 55 88 45 89 fa 48 85 c0 44 0f b6 bd 7f ff 
RIP: __slab_free+0x18a/0x300 RSP: ffffbdce42a078e0

Comment 1 Babak Farrokhi 2018-07-01 15:15:49 UTC
Created attachment 1455765 [details]
File: dmesg

Comment 2 Justin M. Forbes 2018-07-23 15:12:04 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs.

Fedora 27 has now been rebased to 4.17.7-100.fc27.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 28, and are still experiencing this issue, please change the version to Fedora 28.

If you experience different issues, please open a new bug report for those.

Comment 3 Justin M. Forbes 2018-08-29 15:07:20 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 5 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.


Note You need to log in before you can comment on or make changes to this bug.