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

Groups > linux.debian.kernel > #79889

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

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Tue, 2023-08-01 at 02:49 +0200, AlMa wrote:
> On 01.08.23 01:12, Debian Bug Tracking System wrote:
> > You filed *8* different 'bugs' which (almost?) all are about a Dell Mobile
> > Precision M6700 ... and not once did you say what actual problem you
> > experienced?!?
> 
> That's wrong.
> Before I posted some (not all) of the bug reports, the Dell laptop 
> stopped booting properly rather early; the root cause is still unknown 
> (though an intermediate cause is finally resolved now, the bug report is 
> already closed).  It took me a bit to get a working console, a mouse and 
> network going so as to simply be able to start debugging.  Some other 
> machines I manage had (and still have) other, less severe symptoms, 
> e.g., Wayland and programs depending on Wayland (e.g., “foot”) failing 
> to start after Debian upgrade.
> 
> If your computer doesn't boot properly, you go one by one through every 
> suspicious message you find. The fact that some messages are shown as 
> warnings and others as errors is clearly meant to warn whoever reads 
> them (i.e., the admin) and make him/her concerned.  By the definition of 
> the terms “warning” and “error”!

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.

>   If these messages shouldn't make the 
> admin concerned, well, then the journalctl shouldn't show these messages 
> as warnings (AFAIK, yellow) and errors (red according to `man 
> journalctl`).  Please don't try to unload on me because of this mess; 
> I'm just an admin, and not even a developer.
> 
> Therefore, please restore the bug reports you closed.

I agree with Diederik's closing these bug reports.  We as kernel
maintainers have limited time and resources for investigating bugs, and
we are certainly not able to provide individual support for users and
administrators.  Investigating warning messages one by one is not a
priority at all.

If there is still an actual problem on this machine (not just warning
messages), please open *1* bug report that describes the actual problem
and the log messages.

Ben.

-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next 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