[opensuse] error message in dmesg and terminals 1-6 and system log file
Hello: I have this problem in openSUSE Leap 42.2. dmesg if full with the following message: ----------------- [12458.189875] BUG: sleeping function called from invalid context at ../fs/dcache.c:760 [12458.189884] in_atomic(): 1, irqs_disabled(): 0, pid: 456, name: systemd-journal [12458.189891] CPU: 0 PID: 456 Comm: systemd-journal Tainted: G O 4.4.73-18.17-default #1 [12458.189901] Hardware name: Gigabyte Technology Co., Ltd. GA-870A-UD3/GA-870A-UD3, BIOS F5 08/01/2011 [12458.189915] 0000000000000000 ffffffff813295f7 ffff8802272df9d8 0000000000000001 [12458.189919] ffffffff8121cf8a ffff88022596fc10 0000000000000001 ffff8800cb157e30 [12458.189927] 00007ffe98d4dbf0 [12458.189934] ffffffff8120ff22 ffff88022596fc10 ffffffffa08d3098 [12458.189937] Call Trace: [12458.189966] [<ffffffff81019ea9>] dump_trace+0x59/0x320 [12458.189981] [<ffffffff8101a26a>] show_stack_log_lvl+0xfa/0x180 [12458.189990] [<ffffffff8101b011>] show_stack+0x21/0x40 [12458.190003] [<ffffffff813295f7>] dump_stack+0x5c/0x85 [12458.190012] [<ffffffff8121cf8a>] dput+0x2a/0x250 [12458.190022] [<ffffffff8120ff22>] path_put+0x12/0x20 [12458.190036] [<ffffffffa08d3098>] get_filename_from_opened_fd+0x98/0xd0 [bc_guard] [12458.190064] [<ffffffffa08d31c3>] wrapper_sys_ftruncate+0x33/0x110 [bc_guard] [12458.190079] [<ffffffff8160f772>] entry_SYSCALL_64_fastpath+0x16/0x71 [12458.196129] DWARF2 unwinder stuck at entry_SYSCALL_64_fastpath+0x16/0x71 [12458.196131] Leftover inexact backtrace: ------------------ This is repeated endless times. I googled and found that other have this bug, but I couldn't find a fix. The computer is working OK as far as I can say. Is there anything I should do with this or can I ignore this message? I have two other questions related: 1. This error message is shown repeatedly in a working virtual terminal window (vt 1-6). If I login to a vt the message interrupts my typing and makes impossible to work in the terminal. How can I fix this? 2. I tried to have a look at log messages and discovered I don't have /var/log/messages file? Where is the log file, I mean a simple text file I can read with any simple text viewer from any operating system. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zaterdag 22 juli 2017 00:04:03 CEST schreef Istvan Gabor:
Hello:
I have this problem in openSUSE Leap 42.2. dmesg if full with the following message:
----------------- [12458.189875] BUG: sleeping function called from invalid context at ../fs/dcache.c:760 [12458.189884] in_atomic(): 1, irqs_disabled(): 0, pid: 456, name: systemd-journal [12458.189891] CPU: 0 PID: 456 Comm: systemd-journal Tainted: G O 4.4.73-18.17-default #1 [12458.189901] Hardware name: Gigabyte Technology Co., Ltd. GA-870A-UD3/GA-870A-UD3, BIOS F5 08/01/2011 [12458.189915] 0000000000000000 ffffffff813295f7 ffff8802272df9d8 0000000000000001 [12458.189919] ffffffff8121cf8a ffff88022596fc10 0000000000000001 ffff8800cb157e30 [12458.189927] 00007ffe98d4dbf0 [12458.189934] ffffffff8120ff22 ffff88022596fc10 ffffffffa08d3098 [12458.189937] Call Trace: [12458.189966] [<ffffffff81019ea9>] dump_trace+0x59/0x320 [12458.189981] [<ffffffff8101a26a>] show_stack_log_lvl+0xfa/0x180 [12458.189990] [<ffffffff8101b011>] show_stack+0x21/0x40 [12458.190003] [<ffffffff813295f7>] dump_stack+0x5c/0x85 [12458.190012] [<ffffffff8121cf8a>] dput+0x2a/0x250 [12458.190022] [<ffffffff8120ff22>] path_put+0x12/0x20 [12458.190036] [<ffffffffa08d3098>] get_filename_from_opened_fd+0x98/0xd0 [bc_guard] [12458.190064] [<ffffffffa08d31c3>] wrapper_sys_ftruncate+0x33/0x110 [bc_guard] [12458.190079] [<ffffffff8160f772>] entry_SYSCALL_64_fastpath+0x16/0x71 [12458.196129] DWARF2 unwinder stuck at entry_SYSCALL_64_fastpath+0x16/0x71
[12458.196131] Leftover inexact backtrace: ------------------
This is repeated endless times.
I googled and found that other have this bug, but I couldn't find a fix.
The computer is working OK as far as I can say.
Is there anything I should do with this or can I ignore this message?
I have two other questions related:
1. This error message is shown repeatedly in a working virtual terminal window (vt 1-6). If I login to a vt the message interrupts my typing and makes impossible to work in the terminal. How can I fix this?
2. I tried to have a look at log messages and discovered I don't have /var/log/messages file? Where is the log file, I mean a simple text file I can read with any simple text viewer from any operating system.
Thanks,
Istvan
There is no /var/log/messages anymore . It's been replaced by journaling, which you can access by using journalctl . -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 22 Jul 2017 00:17:56 +0200, Knurpht - Gertjan Lettink wrote:
Op zaterdag 22 juli 2017 00:04:03 CEST schreef Istvan Gabor:
Hello:
I have this problem in openSUSE Leap 42.2. dmesg if full with the following message:
----------------- [12458.189875] BUG: sleeping function called from invalid context at ../fs/dcache.c:760 [12458.189884] in_atomic(): 1, irqs_disabled(): 0, pid: 456, name: systemd-journal [12458.189891] CPU: 0 PID: 456 Comm: systemd-journal Tainted: G O 4.4.73-18.17-default #1 [12458.189901] Hardware name: Gigabyte Technology Co., Ltd. GA-870A-UD3/GA-870A-UD3, BIOS F5 08/01/2011 [12458.189915] 0000000000000000 ffffffff813295f7 ffff8802272df9d8 0000000000000001 [12458.189919] ffffffff8121cf8a ffff88022596fc10 0000000000000001 ffff8800cb157e30 [12458.189927] 00007ffe98d4dbf0 [12458.189934] ffffffff8120ff22 ffff88022596fc10 ffffffffa08d3098 [12458.189937] Call Trace: [12458.189966] [<ffffffff81019ea9>] dump_trace+0x59/0x320 [12458.189981] [<ffffffff8101a26a>] show_stack_log_lvl+0xfa/0x180 [12458.189990] [<ffffffff8101b011>] show_stack+0x21/0x40 [12458.190003] [<ffffffff813295f7>] dump_stack+0x5c/0x85 [12458.190012] [<ffffffff8121cf8a>] dput+0x2a/0x250 [12458.190022] [<ffffffff8120ff22>] path_put+0x12/0x20 [12458.190036] [<ffffffffa08d3098>] get_filename_from_opened_fd+0x98/0xd0 [bc_guard] [12458.190064] [<ffffffffa08d31c3>] wrapper_sys_ftruncate+0x33/0x110 [bc_guard] [12458.190079] [<ffffffff8160f772>] entry_SYSCALL_64_fastpath+0x16/0x71 [12458.196129] DWARF2 unwinder stuck at entry_SYSCALL_64_fastpath+0x16/0x71
[12458.196131] Leftover inexact backtrace: ------------------
This is repeated endless times.
I googled and found that other have this bug, but I couldn't find a fix.
The computer is working OK as far as I can say.
Is there anything I should do with this or can I ignore this message?
I have two other questions related:
1. This error message is shown repeatedly in a working virtual terminal window (vt 1-6). If I login to a vt the message interrupts my typing and makes impossible to work in the terminal. How can I fix this?
2. I tried to have a look at log messages and discovered I don't have /var/log/messages file? Where is the log file, I mean a simple text file I can read with any simple text viewer from any operating system.
Thanks,
Istvan
There is no /var/log/messages anymore . It's been replaced by journaling, which you can access by using journalctl .
Are you saying that there is no way to set the system to produce simple text log files? How can I read the logs then if I mount openSUSE partition in another OS which doesn't have the specific tool? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-07-22 00:32, Istvan Gabor wrote:
On Sat, 22 Jul 2017 00:17:56 +0200, Knurpht - Gertjan Lettink wrote:
There is no /var/log/messages anymore . It's been replaced by journaling, which you can access by using journalctl .
Are you saying that there is no way to set the system to produce simple text log files? How can I read the logs then if I mount openSUSE partition in another OS which doesn't have the specific tool?
You can not; at least, none has explained how to do it. And yes, this is a consequence of having systemd. If the system is running, you use "journalctl" command to read the logs. You can dump them to a text file that way. Alternatively, you can /also/ install a traditional syslog service which will provide traditional text logs. My current recommendation is you install "rsyslogd". -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
* Istvan Gabor <suseuser04@gmail.hu> [07-21-17 18:07]: [...]
I have two other questions related:
1. This error message is shown repeatedly in a working virtual terminal window (vt 1-6). If I login to a vt the message interrupts my typing and makes impossible to work in the terminal. How can I fix this?
2. I tried to have a look at log messages and discovered I don't have /var/log/messages file? Where is the log file, I mean a simple text file I can read with any simple text viewer from any operating system.
if you want /var/log/messages to exist, you must install rsyslog. the install process will switch you to using syslog *and* journald, which you can limit by editing /etc/systemd/journald.conf and redirecting output. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 21 Jul 2017 18:39:18 -0400, Patrick Shanahan wrote:
* Istvan Gabor <suseuser04@gmail.hu> [07-21-17 18:07]: [...]
I have two other questions related:
1. This error message is shown repeatedly in a working virtual terminal window (vt 1-6). If I login to a vt the message interrupts my typing and makes impossible to work in the terminal. How can I fix this?
2. I tried to have a look at log messages and discovered I don't have /var/log/messages file? Where is the log file, I mean a simple text file I can read with any simple text viewer from any operating system.
if you want /var/log/messages to exist, you must install rsyslog. the install process will switch you to using syslog *and* journald, which you can limit by editing /etc/systemd/journald.conf and redirecting output.
Thank you Patrick, I will look into this. What about the error messages spitting my terminal screen? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Istvan Gabor <suseuser04@gmail.hu> [07-21-17 19:04]:
On Fri, 21 Jul 2017 18:39:18 -0400, Patrick Shanahan wrote:
* Istvan Gabor <suseuser04@gmail.hu> [07-21-17 18:07]: [...]
I have two other questions related:
1. This error message is shown repeatedly in a working virtual terminal window (vt 1-6). If I login to a vt the message interrupts my typing and makes impossible to work in the terminal. How can I fix this?
2. I tried to have a look at log messages and discovered I don't have /var/log/messages file? Where is the log file, I mean a simple text file I can read with any simple text viewer from any operating system.
if you want /var/log/messages to exist, you must install rsyslog. the install process will switch you to using syslog *and* journald, which you can limit by editing /etc/systemd/journald.conf and redirecting output.
Thank you Patrick, I will look into this.
What about the error messages spitting my terminal screen?
I have seen something about outputting kernel msgs or system msgs to a tty and have mine directed to tty10, but I don't recall the procedure. maybe google it. ps: a kernel oops will still output everywhere. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Istvan Gabor composed on 2017-07-22 00:04 (UTC+0200):
1. This error message is shown repeatedly in a working virtual terminal window (vt 1-6). If I login to a vt the message interrupts my typing and makes impossible to work in the terminal. How can I fix this?
Not the only way, just a way: Put 'kernel.printk = 3 4 1 3' in a .conf file in /etc/sysctl.d/ to make them stay away. Another is through use of loglevel= on kernel cmdline, but which? 3? 4? Other? Putting quiet on kernel cmdline also should work. The /best/ way I'd like to know. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-07-22 00:04, Istvan Gabor wrote:
Hello:
I have this problem in openSUSE Leap 42.2. dmesg if full with the following message:
Well, the kernel is complaining of some big problem, reporting a BUG, and probably happening a lot. You have to look at the full message in the logs to find out what it is about, then act. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
participants (5)
-
Carlos E. R. -
Felix Miata -
Istvan Gabor -
Knurpht - Gertjan Lettink -
Patrick Shanahan