[opensuse] "Crash" in booting sequence
This flashes by each I boot and is in /var/log/warn If I unmount and FSCK each of my reiserFS I see no problems. I can't account for it. It has been apparent though the last dozen or so revisions of the kernel. It only occurs ONCE, not once for each filesystem. I recall that ReiserFS isn't concurrent threaded, perhaps that's why there's only one. But, as I say, everything functions OK. Any suggesting as to the why and whwerefor? Why now? It has percolated to the top of my 'annoyances' stack following a visit to the dentist yesterday. I've stripped label and timestamps for clarity main kernel: [ 172.799354] Workqueue: events_long flush_old_commits [reiserfs] main kernel: [ 172.799356] Call Trace: main kernel: [ 172.799374] dump_stack+0x5c/0x7a main kernel: [ 172.799380] __warn+0xbe/0xe0 main kernel: [ 172.799390] dquot_writeback_dquots+0x261/0x270 main kernel: [ 172.799398] ? __switch_to+0x20f/0x450 main kernel: [ 172.799404] reiserfs_sync_fs+0x17/0x70 [reiserfs] main kernel: [ 172.799418] ? __schedule+0x3d7/0x8c0 main kernel: [ 172.799423] ? flush_old_commits+0x35/0x50 [reiserfs] main kernel: [ 172.799427] process_one_work+0x18e/0x460 main kernel: [ 172.799431] worker_thread+0x4a/0x470 main kernel: [ 172.799434] kthread+0xfc/0x130 main kernel: [ 172.799437] ? process_one_work+0x460/0x460 main kernel: [ 172.799438] ? kthread_create_on_node+0x40/0x40 main kernel: [ 172.799440] ret_from_fork+0x26/0x40 main kernel: [ 172.799443] ---[ end trace 88d141723fb947e5 ]--- # cat /etc/os-release NAME="openSUSE Leap" VERSION="42.1" VERSION_ID="42.1" PRETTY_NAME="openSUSE Leap 42.1 (x86_64)" -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 4 May 2017 08:48:53 -0400
Anton Aylward
This flashes by each I boot and is in /var/log/warn
If I unmount and FSCK each of my reiserFS I see no problems. I can't account for it. It has been apparent though the last dozen or so revisions of the kernel. It only occurs ONCE, not once for each filesystem. I recall that ReiserFS isn't concurrent threaded, perhaps that's why there's only one. But, as I say, everything functions OK.
Any suggesting as to the why and whwerefor?
Why now? It has percolated to the top of my 'annoyances' stack following a visit to the dentist yesterday.
Dunno. FWIW I use reiserfs as well on 42.1 and I don't see the problem. The only lines in var/log/warn that mention reiser say: reiserfs: using flush barriers Cheers, Dave
I've stripped label and timestamps for clarity
main kernel: [ 172.799354] Workqueue: events_long flush_old_commits [reiserfs] main kernel: [ 172.799356] Call Trace: main kernel: [ 172.799374] dump_stack+0x5c/0x7a main kernel: [ 172.799380] __warn+0xbe/0xe0 main kernel: [ 172.799390] dquot_writeback_dquots+0x261/0x270 main kernel: [ 172.799398] ? __switch_to+0x20f/0x450 main kernel: [ 172.799404] reiserfs_sync_fs+0x17/0x70 [reiserfs] main kernel: [ 172.799418] ? __schedule+0x3d7/0x8c0 main kernel: [ 172.799423] ? flush_old_commits+0x35/0x50 [reiserfs] main kernel: [ 172.799427] process_one_work+0x18e/0x460 main kernel: [ 172.799431] worker_thread+0x4a/0x470 main kernel: [ 172.799434] kthread+0xfc/0x130 main kernel: [ 172.799437] ? process_one_work+0x460/0x460 main kernel: [ 172.799438] ? kthread_create_on_node+0x40/0x40 main kernel: [ 172.799440] ret_from_fork+0x26/0x40 main kernel: [ 172.799443] ---[ end trace 88d141723fb947e5 ]---
# cat /etc/os-release NAME="openSUSE Leap" VERSION="42.1" VERSION_ID="42.1" PRETTY_NAME="openSUSE Leap 42.1 (x86_64)"
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/05/17 10:53 AM, Dave Howorth wrote:
Dunno. FWIW I use reiserfs as well on 42.1 and I don't see the problem. The only lines in var/log/warn that mention reiser say:
reiserfs: using flush barriers
Yes, I get that as well. I'm not sure it should be warning, just a notification. its not as if it is anything wrong. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2017-05-04 at 08:48 -0400, Anton Aylward wrote: El 2017-05-04 a las 08:48 -0400, Anton Aylward escribió:
I've stripped label and timestamps for clarity
main kernel: [ 172.799354] Workqueue: events_long flush_old_commits [reiserfs] main kernel: [ 172.799356] Call Trace: main kernel: [ 172.799374] dump_stack+0x5c/0x7a main kernel: [ 172.799380] __warn+0xbe/0xe0 main kernel: [ 172.799390] dquot_writeback_dquots+0x261/0x270 main kernel: [ 172.799398] ? __switch_to+0x20f/0x450 main kernel: [ 172.799404] reiserfs_sync_fs+0x17/0x70 [reiserfs] main kernel: [ 172.799418] ? __schedule+0x3d7/0x8c0 main kernel: [ 172.799423] ? flush_old_commits+0x35/0x50 [reiserfs] main kernel: [ 172.799427] process_one_work+0x18e/0x460 main kernel: [ 172.799431] worker_thread+0x4a/0x470 main kernel: [ 172.799434] kthread+0xfc/0x130 main kernel: [ 172.799437] ? process_one_work+0x460/0x460 main kernel: [ 172.799438] ? kthread_create_on_node+0x40/0x40 main kernel: [ 172.799440] ret_from_fork+0x26/0x40 main kernel: [ 172.799443] ---[ end trace 88d141723fb947e5 ]---
Well, you have a kernel oops. The entire report will be in the normal log. Just post it on a Bugzilla. You are using an advanced kernel, as I recall, you have found a bug, apparently. Report it. - -- Cheers, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlkLl90ACgkQtTMYHG2NR9VHngCeKxJKZlWuzoXqWT5tqIdfyT4M FEgAn0GH01Rzgud+ieqU9Y+ooVef/d86 =m01p -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2017-05-04 at 11:24 -0400, Anton Aylward wrote:
On 04/05/17 10:53 AM, Dave Howorth wrote:
Dunno. FWIW I use reiserfs as well on 42.1 and I don't see the problem. The only lines in var/log/warn that mention reiser say:
reiserfs: using flush barriers
Yes, I get that as well. I'm not sure it should be warning, just a notification. its not as if it is anything wrong.
You do have a kernel oops. That is wrong. - -- Cheers, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlkMVgIACgkQtTMYHG2NR9V1cQCfc69krHeydUisRCgB59VukSVQ oLMAoIsmZx+Lvgv4ttLp/CFDBvkzriEq =gU2n -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/05/17 06:37 AM, Carlos E. R. wrote:
You do have a kernel oops. That is wrong.
A grep for "- i oops /var/log/*" returns nothing. I was under the impression that a kernel oops was terminal. The point I'm trying to make clear is that whatever that is, it doesn't actually affect anything. The file systems all come up, they FSCK OK, they mount OK, the read/write OK. If I wasn't one of those people who who turn off the graphical boot and get their jollies from watching the boot sequence go by, the times that I'm not off making coffee (or feeding the cat) while the machine boots (which is why I don't care that it takes twice as long to boot as Linda's machine) then I'd never have noticed it it. Its not in any way dysfunctional. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/05/17 05:06 PM, Carlos E. R. wrote:
Well, you have a kernel oops. The entire report will be in the normal log. Just post it on a Bugzilla.
It is not an "oops". it is not terminal. I don't know what you think is a "normal' log. its not in 'boot.msg' or in 'messages' and 'systemctl -b' isn't reporting it. It ONLY shows up in 'warn'. Most of 'warn' is populated by warnings from fetchmail that my one and only POP connection is 'insecure', that is, its not using TLS or anything. The other is that my screen mane has changed from "VDA" to "VDA1". If this is of the same order of criticality than it is certainly not a terminal 'oops' and
You are using an advanced kernel, as I recall, you have found a bug, apparently. Report it.
Dave Howorth didn't report which kernel he was using. I've just today graduated to 4.11.0, but I recall this in all of the 4.10 sequence. It may have been in the 4.9 sequence, I don't recall. its not as if I was tracking such things. I only watched the boot messages for amusement, not for analysis. I certainly don't rate this as a bug. It doesn't really even rate as an annoyance. As I've said, if I was simply one of those people who disables graphical boot and get jollies from watching boot message, I'd never have noticed it. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 5 May 2017 07:56:19 -0400
Anton Aylward
You are using an advanced kernel, as I recall, you have found a bug, apparently. Report it.
Dave Howorth didn't report which kernel he was using.
Neither did you. You did say you were using 42.1 and so am I, which I also said. When I say it I mean it, including the kernel :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-05-05 13:56, Anton Aylward wrote:
On 04/05/17 05:06 PM, Carlos E. R. wrote:
Well, you have a kernel oops. The entire report will be in the normal log. Just post it on a Bugzilla.
It is not an "oops". it is not terminal.
Not all are terminal.
I don't know what you think is a "normal' log. its not in 'boot.msg' or in 'messages' and 'systemctl -b' isn't reporting it. It ONLY shows up in 'warn'.
grep "end trace 88d141723fb947e5" /var/log/messages or: journalctl | grep "end trace 88d141723fb947e5"
Most of 'warn' is populated by warnings from fetchmail that my one and only POP connection is 'insecure', that is, its not using TLS or anything.
There are settings in man fetchmail to cover that. I don't remember offhand. On one account I have to tell it that the ssl commonname is different from the server name, for instance. Thunderbird is a very good tool to find out what is the best combination of parameters for a given account, when entering a new account (on automatic). Then translate the findings to fecthmail (which is better at logging and reporting the issues).
I certainly don't rate this as a bug. It doesn't really even rate as an annoyance. As I've said, if I was simply one of those people who disables graphical boot and get jollies from watching boot message, I'd never have noticed it.
The kernel log rates it as a bug and asks you to report it ;-) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 05/05/17 08:44 AM, Carlos E. R. wrote:
On 2017-05-05 13:56, Anton Aylward wrote:
Most of 'warn' is populated by warnings from fetchmail that my one and only POP connection is 'insecure', that is, its not using TLS or anything.
There are settings in man fetchmail to cover that. I don't remember offhand.
I'm well aware of them and have tried them. That particular ISP doesn't support any kind of security on POP. I don't take that account very seriously. I said "most". There are other equally lame warnings as well. most of them from KDE. Sometimes I wonder about the KDE developers; are they obsessed with using syslog or what?
The kernel log rates it as a bug and asks you to report it ;-)
Bug 1037795 -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-05-05 15:00, Anton Aylward wrote:
On 05/05/17 08:44 AM, Carlos E. R. wrote:
On 2017-05-05 13:56, Anton Aylward wrote:
Most of 'warn' is populated by warnings from fetchmail that my one and only POP connection is 'insecure', that is, its not using TLS or anything.
There are settings in man fetchmail to cover that. I don't remember offhand.
I'm well aware of them and have tried them. That particular ISP doesn't support any kind of security on POP. I don't take that account very seriously.
Well, the idea is to silence the warning. Perhaps --sslproto '' (ie, empty string, means none).
I said "most". There are other equally lame warnings as well. most of them from KDE. Sometimes I wonder about the KDE developers; are they obsessed with using syslog or what?
I use several filters to silence thousands of messages from gnome or gtk tools. Somebody decided that dumping debug messages to syslog at warning level is a good idea, and has been doing so for years.
The kernel log rates it as a bug and asks you to report it ;-)
Bug 1037795
:-))) Comment: boot.msg is deprecated. I told you how to find the whole log. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On 05/05/17 12:37 PM, Carlos E. R. wrote:
I'm well aware of them and have tried them. That particular ISP doesn't support any kind of security on POP. I don't take that account very seriously. Well, the idea is to silence the warning.
Perhaps --sslproto '' (ie, empty string, means none).
Thank you for that. I was aware of the "--ssl***" but that ISP said not to bother as there was no support for anything. I'll let you know. OK, looks good. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Anton Aylward -
Carlos E. R. -
Dave Howorth