Your message dated Mon, 5 Aug 2019 21:39:45 +0200 (CEST)
with message-id <alpine.DEB.2.21.1908052131230.23802@hier>
and subject line
has caused the Debian Bug report #933973,
regarding general: System totally freeze all the time (Debian 10)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
933973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I don't know! This happens every day by different reasons.
* What exactly did you do (or not do) that was effective (or
ineffective)?
This is the point, a totally different things. There is not something specific,
even when i do nothing.
* What was the outcome of this action?
The system stop responing.
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Am 05.08.19 um 19:24 schrieb Nikolay Stoyanov:> Package: general
* What led up to the situation?
I don't know! This happens every day by different reasons.
* What exactly did you do (or not do) that was effective (or
ineffective)?
This is the point, a totally different things. There is not
something specific, even when i do nothing.
* What was the outcome of this action?
The system stop responing.
* What outcome did you expect instead?
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Now there's another important questions that is completely unclear and
would need to be answered:
* What do you think we can do now with this bugreport and the
information you have provided here?
There is *nothing* specific in your bug report except for the kernel
version.
The idea of reporting a bug here is to get a bug fixed. But what's the
bug? Is it broken hardware? Something else? What? How can Debian find
out given the information?
Please do go to a Debian user IRC channel and people there can
possibly help you to narrow the problem down. bugs.debian.org however is
*not* a support site to do this. You'd need to provide much more and much
more specific information here.
Thanks,
*t
--- End Message ---
