Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [RFC PATCH v1 13/26] docs: reporting-bugs: point out the
 environment might be causing issue
To:     Thorsten Leemhuis <linux@leemhuis.info>,
        Jonathan Corbet <corbet@lwn.net>
Cc:     linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
References: <cover.1601541165.git.linux@leemhuis.info>
 <6dab906efb915c6cd6733df525b1f3da3753c4b4.1601541165.git.linux@leemhuis.info>
From:   Randy Dunlap <rdunlap@infradead.org>
Message-ID: <a226274e-7bda-bd27-a0a5-1f1bb165fcd1@infradead.org>
Date:   Fri, 2 Oct 2020 10:32:36 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <6dab906efb915c6cd6733df525b1f3da3753c4b4.1601541165.git.linux@leemhuis.info>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 10/1/20 1:39 AM, Thorsten Leemhuis wrote:
> Help users to avoid a few pitfalls, as they might be the real reason why
> the kernel is acting up somehow.
> 
> Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
> ---
>  Documentation/admin-guide/reporting-bugs.rst | 34 ++++++++++++++++++++
>  1 file changed, 34 insertions(+)
> 
> diff --git a/Documentation/admin-guide/reporting-bugs.rst b/Documentation/admin-guide/reporting-bugs.rst
> index d96b21512c03..2292b79cf462 100644
> --- a/Documentation/admin-guide/reporting-bugs.rst
> +++ b/Documentation/admin-guide/reporting-bugs.rst
> @@ -583,6 +583,40 @@ not part of the Linux kernel. Your package manager might thus force you to
>  remove those, too.
>  
>  
> +Ensure a healthy environment
> +----------------------------
> +
> +    *Make sure it's not the kernels surroundings that are causing the issue you

                               kernel's

> +    face.*
> +
> +Problems that look a lot like a kernel issue are sometimes caused by build
> +or runtime environment. It's hard to rule out that problem completely, but you
> +should minimize it:
> +
> + * Use proven tools when building your kernel, as bugs in the compiler or the
> +   binutils can cause the resulting kernel to misbehave.
> +
> + * Ensure your computer components runs within their design specifications;

                                      run

> +   that's especially important for the main processor, the main memory, and the
> +   motherboard. Therefore, stop overclocking when facing a potential kernel
> +   issue.
> +
> + * Try to make sure it's not faulty hardware that is causing your issue. Bad
> +   main memory for example can result in a multitude of issues that will
> +   manifest itself in problems looking like kernel issues.
> +
> + * If you're dealing with a filesystem issue, you might want to check the file
> +   system in question with ``fsck`` before trying to reproduce it again.
> +
> + * When dealing with a regression, make sure it's not something else that
> +   changed in parallel to updating the kernel. The problem for example might be
> +   caused by another software that was updated at the same time. It can also

             by other software

> +   happen that a hardware component coincidentally just broke when you rebooted
> +   into a new kernel for the first time. Updating the systems BIOS or changing
> +   something in the BIOS Setup can also lead to problems that on the first sight
> +   look like a regression.
> +
> +
>  .. ############################################################################
>  .. Temporary marker added while this document is rewritten. Sections above
>  .. are new and dual-licensed under GPLv2+ and CC-BY 4.0, those below are old.
> 


-- 
~Randy