Bug 1370269 - [abrt] BUG: sleeping function called from invalid context at mm/slab.h:391
Summary: [abrt] BUG: sleeping function called from invalid context at mm/slab.h:391
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
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:97cb95136ac065e29e3a26bbfdf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-25 18:58 UTC by lejeczek
Modified: 2021-08-11 11:54 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-26 16:59:17 UTC
Type: ---


Attachments (Terms of Use)
File: dmesg (101.93 KB, text/plain)
2016-08-25 18:58 UTC, lejeczek
no flags Details

Description lejeczek 2016-08-25 18:58:05 UTC
Additional info:
reporter:       libreport-2.7.2
BUG: sleeping function called from invalid context at mm/slab.h:391
in_atomic(): 1, irqs_disabled(): 0, pid: 379, name: systemd-udevd
no locks held by systemd-udevd/379.
CPU: 0 PID: 379 Comm: systemd-udevd Not tainted 4.8.0-0.rc0.git2.1.fc26.x86_64 #1
Hardware name: Dell Inc. Latitude E7470/0T6HHJ, BIOS 1.5.3 04/18/2016
 0000000000000286 0000000062a06694 ffff8fe1ff72f8d0 ffffffffa1463ef3
 ffff8fe1ff5832c0 ffffffffa1c7c846 ffff8fe1ff72f8f8 ffffffffa10de799
 ffffffffa1c7c846 0000000000000187 0000000000000000 ffff8fe1ff72f920
Call Trace:
 [<ffffffffa1463ef3>] dump_stack+0x86/0xc3
 [<ffffffffa10de799>] ___might_sleep+0x179/0x230
 [<ffffffffa10de899>] __might_sleep+0x49/0x80
 [<ffffffffa126ef96>] kmem_cache_alloc_trace+0x1e6/0x2d0
 [<ffffffffa149ce00>] ? mpi_alloc+0x20/0x80
 [<ffffffffa149ce00>] mpi_alloc+0x20/0x80
 [<ffffffffa149a755>] mpi_read_raw_from_sgl+0xd5/0x1e0
 [<ffffffffa1403666>] rsa_verify+0x66/0x100
 [<ffffffffa1270bf5>] ? __kmalloc+0x2e5/0x320
 [<ffffffffa1404ab9>] pkcs1pad_verify+0x149/0x190
 [<ffffffffa141f379>] public_key_verify_signature+0x1f9/0x290
 [<ffffffffa141f425>] public_key_verify_signature_2+0x15/0x20
 [<ffffffffa141f07c>] verify_signature+0x3c/0x50
 [<ffffffffa14212ed>] pkcs7_validate_trust+0x11d/0x230
 [<ffffffffa11f518b>] verify_pkcs7_signature+0xbb/0x180
 [<ffffffffa115c24d>] mod_verify_sig+0xdd/0x130
 [<ffffffffa1158f8c>] load_module+0x16c/0x2960
 [<ffffffffa124a05c>] ? vmap_page_range_noflush+0x25c/0x360
 [<ffffffffa1037e89>] ? sched_clock+0x9/0x10
 [<ffffffffa10ea457>] ? sched_clock_cpu+0xa7/0xc0
 [<ffffffffa1234ba3>] ? __might_fault+0x43/0xa0
 [<ffffffffa1234ba3>] ? __might_fault+0x43/0xa0
 [<ffffffffa115b8f2>] SYSC_init_module+0x172/0x1b0
 [<ffffffffa115ba5e>] SyS_init_module+0xe/0x10
 [<ffffffffa1003fec>] do_syscall_64+0x6c/0x1e0
 [<ffffffffa18f18bf>] entry_SYSCALL64_slow_path+0x25/0x25

Potential duplicate: bug 1361614

Comment 1 lejeczek 2016-08-25 18:58:17 UTC
Created attachment 1194096 [details]
File: dmesg

Comment 2 lejeczek 2016-08-29 09:15:26 UTC
problem was that when only on battery laptop would not resume, it would sort of start but then a reset happened and a fresh new hardware boot took place instead.
I think this might be fixed in Dell's 1.7 version of the BIOS for this laptop, at least 4.8.x now resume from sleep seems to work.

Comment 3 Laura Abbott 2016-09-23 19:22:19 UTC
*********** MASS BUG UPDATE **************
 
We apologize for the inconvenience.  There is 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 24 kernel bugs.
 
Fedora 24 has now been rebased to 4.7.4-200.fc24.  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 25, and are still experiencing this issue, please change the version to Fedora 25.
 
If you experience different issues, please open a new bug report for those.

Comment 4 Laura Abbott 2016-10-26 16:59:17 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 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.

Comment 5 lejeczek 2021-08-11 11:54:50 UTC
ok


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