Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: rbowman Newsgroups: comp.os.linux.misc Subject: Re: Wow - M$ Fixes Everything - Blue Screen-of-Death Replaced by BLACK Screen-of-Death Date: 28 Jun 2025 06:18:31 GMT Lines: 15 Message-ID: References: <4Z6dnVgDGMz1-cL1nZ2dnZfqn_idnZ2d@giganews.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net pnFxtwDQTGbpcWfMYyaaCQu3P2vhkBygDf8ognZkfpaPu6WTjY Cancel-Lock: sha1:nfyjnxzl7CC7eVHH9CmfEkhX2KI= sha256:v8ZvrMscciwWd5CAiKnVXBPNiR+wIMXy2MKg6Y3JlgE= User-Agent: Pan/0.160 (Toresk; ) Xref: csiph.com comp.os.linux.misc:69167 On Fri, 27 Jun 2025 23:41:27 -0400, c186282 wrote: > Clue - we need a generally BETTER fail-mode solution - much clearer > defs of what bombed and why and maybe some automated fixes or at > least really good instructions. In short a "system spy" routine that > runs even before official boot. https://fedoramagazine.org/%f0%9f%94%a7-deep-dive-into-sosreport- understanding-the-data-pack-layout-in-fedora-rhel/ https://fedoramagazine.org/unlocking-system-performance-a-practical-guide- to-tuning-pcp/ I don't know if either of those are useful. sosreport generates a lot of crap that might be meaningful to a Red Hat engineer.