Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #79893

Bug#1041142: closed by Diederik de Haas <didi.debian@cknow.org> (Re: Debian's BTS is not for regular user questions)

From AlMa <AlMa0@ro.ru>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#1041142: closed by Diederik de Haas <didi.debian@cknow.org> (Re: Debian's BTS is not for regular user questions)
Date 2023-08-01 21:40 +0200
Message-ID <GY3nP-4maK-7@gated-at.bofh.it> (permalink)
References (4 earlier) <GXLTX-4axo-3@gated-at.bofh.it> <GY1vH-4l1l-1@gated-at.bofh.it> <GY34t-4m3L-3@gated-at.bofh.it> <GRD33-iQl-1@gated-at.bofh.it> <GY34t-4m3L-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw



On 01.08.23 21:08, AlMa wrote:
>> This is a rather naive understanding of how logging is done in
>> practice.  The reality is that developers often don't know (and maybe
>> can't know) just how severe an odd condition may be in practice.
> 
> Unfortunately, neither do I.  Though seemingly unrelated journal-visible 
> issues are quite often indeed independent, sometimes unexpected 
> interactions or common root causes occur.

Perhaps, there should be a category for tentative errors and/or 
tentative warnings (i.e., with an unknown (or yet unknown) severity in 
practice).  E.g., dereferencing a zero pointer, or division by zero, or 
garbled screen output, or the inability to read '/' as the root user, 
etc. are almost always errors (except when you test error-handling 
routes themselves; then a division by zero is not a bug but a must).  If 
you say that it is unknown how severe a message such as “ACPI Warning: 
SystemIO range … conflicts with OpRegion … . lpc_ich: Resource 
conflict(s) found affecting gpio_ich” really is, it should not be a 
warning (especially, it should not warn the reader) but be a tentative 
warning (i.e., it might warn the reader in the future or under 
particular circumstances).  The (new?) colors of the tentative errors 
and warnings should be clearly stated in the manpages of journalctl.

Back to linux.debian.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

Bug#1041142: ACPI Warning: SystemIO range … conflicts with OpRegion … . lpc_ich: Resource conflict(s) found affecting gpio_ich AlMa <AlMa0@ro.ru> - 2023-07-15 04:20 +0200
  Bug#1041142: marked as done (ACPI Warning: SystemIO range  … conflicts with OpRegion … .  lpc_ich: Resource conflict(s) found affecting gpio_ich) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-08-01 01:20 +0200
  Bug#1041142: closed by Diederik de Haas <didi.debian@cknow.org> (Re: Debian's BTS is not for regular user questions) AlMa <AlMa0@ro.ru> - 2023-08-01 03:00 +0200
    Bug#1041140: mass bug closing AlMa <AlMa0@ro.ru> - 2023-08-01 03:20 +0200
    Bug#1041197: mass bug closing AlMa <AlMa0@ro.ru> - 2023-08-01 03:30 +0200
    Bug#1041142: closed by Diederik de Haas <didi.debian@cknow.org> (Re: Debian's BTS is not for regular user questions) Ben Hutchings <ben@decadent.org.uk> - 2023-08-01 19:40 +0200
      Bug#1041142: closed by Diederik de Haas <didi.debian@cknow.org> (Re: Debian's BTS is not for regular user questions) AlMa <AlMa0@ro.ru> - 2023-08-01 21:20 +0200
        Bug#1041142: closed by Diederik de Haas <didi.debian@cknow.org> (Re: Debian's BTS is not for regular user questions) AlMa <AlMa0@ro.ru> - 2023-08-01 21:40 +0200

csiph-web