[Bug 1014357] New: BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21 - openSUSE Bugs - openSUSE Mailing Lists

newer
[Bug 1021294] New: VUL-0:...

[Bug 1014357] New: BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21

older
[Bug 1021290] New: KDevelop5...

bugzilla_noreply＠novell.com

7 Dec 2016 7 Dec '16

20:00

http://bugzilla.novell.com/show_bug.cgi?id=1014357 Bug ID: 1014357 Summary: BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: digulla@hepe.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- This is for Leap 42.2 (not available in the OS checkbox) I see this error on the screen every time I suspend to disk (hibernate). -- You are receiving this mail because: You are on the CC list for the bug.

Attachments:

attachment.htm (text/html — 2.3 KB)

Reply

Sign in to reply online Use email software

Show replies by date

bugzilla_noreply＠novell.com

7 Dec 7 Dec

20:05

New subject: [Bug 1014357] BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21

http://bugzilla.novell.com/show_bug.cgi?id=1014357 http://bugzilla.novell.com/show_bug.cgi?id=1014357#c1 --- Comment #1 from Aaron Digulla --- I'm also seeing "BUG: scheduling while atomic: systemd-sleep/.../..." which might be related. Or should I create a new bug for the second message? -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

20:30

New subject: [Bug 1014357] BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21

http://bugzilla.novell.com/show_bug.cgi?id=1014357 http://bugzilla.novell.com/show_bug.cgi?id=1014357#c2 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |digulla@hepe.com, | |tiwai@suse.com Flags| |needinfo?(digulla@hepe.com) --- Comment #2 from Takashi Iwai --- I saw you mentioning about Nvidia driver in another bug report. If the issue is seen with Nvidia binary-only stuff, we can't debug further at all. If so, try to reproduce the problem without Nvidia driver stuff, i.e. no tainted kernel. Once when you get the same issue with a clean kernel, please give the kernel messages (dmesg output) before and after the hibernation. Also, give hwinfo output, too. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

10 Dec 10 Dec

16:50

New subject: [Bug 1014357] BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21

http://bugzilla.novell.com/show_bug.cgi?id=1014357 http://bugzilla.novell.com/show_bug.cgi?id=1014357#c3 --- Comment #3 from Aaron Digulla --- Exact same messages without NVIDIA driver. # uname -a Linux xxx 4.4.36-5-default #1 SMP Tue Dec 6 20:57:24 UTC 2016 (bd51250) x86_64 x86_64 x86_64 GNU/Linux Here is the output of dmesg: [ 184.732299] PM: Creating hibernation image: [ 185.061099] PM: Avoid snapshot the page of hibernation key. [ 185.061111] PM: Need to copy 467864 pages [ 185.061112] PM: Normal pages needed: 467864 + 1024, available pages: 7899666 [ 185.392926] PM: Avoid snapshot the page of hibernation key. [ 185.392944] BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21 [ 185.392944] in_atomic(): 1, irqs_disabled(): 1, pid: 6247, name: systemd-sleep [ 185.392946] CPU: 0 PID: 6247 Comm: systemd-sleep Tainted: G W O 4.4.36-5-default #1 [ 185.392946] Hardware name: System manufacturer System Product Name/Z170-A, BIOS 1302 11/09/2015 [ 185.392948] 0000000000000000 ffffffff81327b07 ffffffff81ebe900 0000000000000409 [ 185.392949] ffffffff8160888c ffffffff81a61c96 ffffffff812dd30d ffffffff81a61c96 [ 185.392949] 000000000000240f 000000000000240f ffffffff812dd40b ffffffff81858a40 [ 185.392950] Call Trace: [ 185.392956] [<ffffffff81019ea9>] dump_trace+0x59/0x320 [ 185.392958] [<ffffffff8101a26a>] show_stack_log_lvl+0xfa/0x180 [ 185.392960] [<ffffffff8101b011>] show_stack+0x21/0x40 [ 185.392962] [<ffffffff81327b07>] dump_stack+0x5c/0x85 [ 185.392965] [<ffffffff8160888c>] down_read+0x1c/0x30 [ 185.392967] [<ffffffff812dd30d>] crypto_alg_lookup+0x1d/0x50 [ 185.392968] [<ffffffff812dd40b>] crypto_larval_lookup+0x2b/0x160 [ 185.392970] [<ffffffff812dd56d>] crypto_alg_mod_lookup+0x2d/0xa0 [ 185.392971] [<ffffffff812dd7d3>] crypto_alloc_tfm+0x53/0xe0 [ 185.392973] [<ffffffff810d0645>] swsusp_save+0x365/0x4a0 [ 185.392976] [<ffffffff814f405b>] swsusp_arch_suspend+0x5b/0x60 [ 185.393815] DWARF2 unwinder stuck at swsusp_arch_suspend+0x5b/0x60 [ 185.393816] Leftover inexact backtrace: [ 185.393817] [<ffffffff810cdf51>] ? hibernation_snapshot+0x2c1/0x360 [ 185.393819] [<ffffffff810ce79e>] ? hibernate+0x15e/0x210 [ 185.393820] [<ffffffff810cbf9d>] ? state_store+0x5d/0x80 [ 185.393821] [<ffffffff8127f14f>] ? kernfs_fop_write+0x12f/0x170 [ 185.393823] [<ffffffff81204e83>] ? __vfs_write+0x23/0x100 [ 185.393824] [<ffffffff812a1148>] ? security_file_permission+0x38/0xc0 [ 185.393825] [<ffffffff810c8b89>] ? percpu_down_read+0x29/0x60 [ 185.393826] [<ffffffff812055fd>] ? vfs_write+0x9d/0x190 [ 185.393827] [<ffffffff812062c2>] ? SyS_write+0x42/0xa0 [ 185.393829] [<ffffffff8160a8f2>] ? entry_SYSCALL_64_fastpath+0x16/0x71 [ 184.732899] ACPI: Hardware changed while hibernated, success doubtful! [ 184.732900] PM: Restoring platform NVS memory [ 184.734516] Enabling non-boot CPUs ... [ 184.734558] x86: Booting SMP configuration: -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

16:53

New subject: [Bug 1014357] BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21

http://bugzilla.novell.com/show_bug.cgi?id=1014357 http://bugzilla.novell.com/show_bug.cgi?id=1014357#c4 Aaron Digulla changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(digulla@hepe.com) | --- Comment #4 from Aaron Digulla --- Created attachment 705958 --> http://bugzilla.novell.com/attachment.cgi?id=705958&action=edit output of hwinfo -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

27 Dec 27 Dec

08:52

New subject: [Bug 1014357] BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21

http://bugzilla.novell.com/show_bug.cgi?id=1014357 http://bugzilla.novell.com/show_bug.cgi?id=1014357#c6 --- Comment #6 from Aaron Digulla --- Just to make sure I understand correctly: You want me to install kernel-default-4.9.0-2.1.g6fbc0c0.x86_64 from http://download.opensuse.org/repositories/Kernel:/stable/standard/, right? Is there some documentation how to keep two kernels on the disk? I don't want to loose my 4.4 kernel. I'm asking because the normal kernel is 4.4 and 4.9 feels far away :-) -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

12:15

New subject: [Bug 1014357] BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21

http://bugzilla.novell.com/show_bug.cgi?id=1014357 http://bugzilla.novell.com/show_bug.cgi?id=1014357#c7 Martin Pluskal changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpluskal@suse.com --- Comment #7 from Martin Pluskal --- By dea(In reply to Aaron Digulla from comment #6)

Just to make sure I understand correctly: You want me to install kernel-default-4.9.0-2.1.g6fbc0c0.x86_64 from http://download.opensuse.org/repositories/Kernel:/stable/standard/, right?

Is there some documentation how to keep two kernels on the disk? I don't want to loose my 4.4 kernel.

I'm asking because the normal kernel is 4.4 and 4.9 feels far away :-)

By default running kernel, latest and latest-1 kernels are kept on system (see /etc/zypp/zypp.conf - multiversion.kernels = latest,latest-1,running), so you should be safe. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

21 Jan 21 Jan

22:14

New subject: [Bug 1014357] BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21

http://bugzilla.novell.com/show_bug.cgi?id=1014357 http://bugzilla.novell.com/show_bug.cgi?id=1014357#c8 Roman Evstifeev changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |someuniquename@gmail.com --- Comment #8 from Roman Evstifeev --- I can confirm this bug on my ASUS X550 laptop. Gpu is intel. I am trying to recalibrate my battery controller after replace of batteries. So i think systemd(?) tries to hibernate, as the controller thinks that battery is at 0% now (it is not). Will try newer kernel when I have time. Actually the fact that hibernate fails allows me to properly discharge battery to recalibrate controller =) Anyone has any idea how to disable this hibernation on 0%? I checked kde power settings without any luck... journal: ----- Jan 22 00:43:19 linux-1zpk kernel: Disabling non-boot CPUs ... Jan 22 00:43:19 linux-1zpk kernel: Broke affinity for irq 17 Jan 22 00:43:19 linux-1zpk kernel: Broke affinity for irq 23 Jan 22 00:43:19 linux-1zpk kernel: Broke affinity for irq 27 Jan 22 00:43:19 linux-1zpk kernel: smpboot: CPU 1 is now offline Jan 22 00:43:19 linux-1zpk kernel: PM: Creating hibernation image: Jan 22 00:43:19 linux-1zpk kernel: PM: Avoid snapshot the page of hibernation key. Jan 22 00:43:19 linux-1zpk kernel: PM: Need to copy 1048492 pages Jan 22 00:43:19 linux-1zpk kernel: PM: Normal pages needed: 1048492 + 1024, available pages: 1953078 Jan 22 00:43:19 linux-1zpk kernel: PM: Avoid snapshot the page of hibernation key. Jan 22 00:43:19 linux-1zpk kernel: BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21 Jan 22 00:43:19 linux-1zpk kernel: in_atomic(): 1, irqs_disabled(): 1, pid: 8317, name: systemd-sleep Jan 22 00:43:19 linux-1zpk kernel: CPU: 0 PID: 8317 Comm: systemd-sleep Tainted: G W 4.4.36-8-default #1 Jan 22 00:43:19 linux-1zpk kernel: Hardware name: ASUSTeK COMPUTER INC. X550CA/X550CA, BIOS X550CA.208 05/29/2013 Jan 22 00:43:19 linux-1zpk kernel: 0000000000000000 ffffffff81327b17 ffffffff81ebe900 0000000000000409 Jan 22 00:43:19 linux-1zpk kernel: ffffffff8160888c ffffffff81a61cae ffffffff812dd32d ffffffff81a61cae Jan 22 00:43:19 linux-1zpk kernel: 000000000000240f 000000000000240f ffffffff812dd42b ffffffff81858a40 Jan 22 00:43:19 linux-1zpk kernel: Call Trace: Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff81019ea9>] dump_trace+0x59/0x320 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff8101a26a>] show_stack_log_lvl+0xfa/0x180 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff8101b011>] show_stack+0x21/0x40 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff81327b17>] dump_stack+0x5c/0x85 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff8160888c>] down_read+0x1c/0x30 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff812dd32d>] crypto_alg_lookup+0x1d/0x50 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff812dd42b>] crypto_larval_lookup+0x2b/0x160 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff812dd58d>] crypto_alg_mod_lookup+0x2d/0xa0 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff812dd7f3>] crypto_alloc_tfm+0x53/0xe0 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff810d0675>] swsusp_save+0x365/0x4a0 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff814f405b>] swsusp_arch_suspend+0x5b/0x60 Jan 22 00:43:19 linux-1zpk kernel: DWARF2 unwinder stuck at swsusp_arch_suspend+0x5b/0x60 Jan 22 00:43:19 linux-1zpk kernel: Jan 22 00:43:19 linux-1zpk kernel: Leftover inexact backtrace: Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff810cdf81>] ? hibernation_snapshot+0x2c1/0x360 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff810ce7ce>] ? hibernate+0x15e/0x210 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff810cbfcd>] ? state_store+0x5d/0x80 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff8127f16f>] ? kernfs_fop_write+0x12f/0x170 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff81204eb3>] ? __vfs_write+0x23/0x100 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff812a1168>] ? security_file_permission+0x38/0xc0 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff810c8bb9>] ? percpu_down_read+0x29/0x60 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff8120562d>] ? vfs_write+0x9d/0x190 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff812062f2>] ? SyS_write+0x42/0xa0 Jan 22 00:43:19 linux-1zpk kernel: [<ffffffff8160a8f2>] ? entry_SYSCALL_64_fastpath+0x16/0x71 Jan 22 00:43:19 linux-1zpk kernel: PM: Hibernation image created (1048492 pages copied) Jan 22 00:43:19 linux-1zpk kernel: PM: Restoring platform NVS memory -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

22:48

New subject: [Bug 1014357] BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21

http://bugzilla.novell.com/show_bug.cgi?id=1014357 http://bugzilla.novell.com/show_bug.cgi?id=1014357#c9 --- Comment #9 from Roman Evstifeev --- Ok, just tried to manually hibernate with kernel 4.9.5. It fails at some later stage, now I see the error "kernel: PM: Swap header not found!" and the second time i tried right after - I got another error: " kernel: PM: Cannot find swap device, try swapon -a. kernel: PM: Cannot get swap writer " -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

22:53

New subject: [Bug 1014357] BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21

http://bugzilla.novell.com/show_bug.cgi?id=1014357 http://bugzilla.novell.com/show_bug.cgi?id=1014357#c10 --- Comment #10 from Roman Evstifeev --- Tried the hibernation by systemd, and saw the same result as manual hibernation: "kernel: PM: Cannot find swap device, try swapon -a." I do have swap file, not the swap partition. I guess hibernation requires the partition. So the OP bug seems to be resolved in the kernel 4.9.5. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

2662

Age (days ago)

2707

Last active (days ago)

Download

9 comments

1 participants

tags

participants (1)

bugzilla_noreply＠novell.com