Date: Wed, 05 Apr 2006 16:56:28 -0400 From: Mike Tancsa <mike@sentex.net> To: shih@math.jussieu.fr Cc: freebsd-stable@freebsd.org Subject: Re: Disappointed Message-ID: <6.2.3.4.0.20060405164905.09e6d1c8@64.7.153.2> In-Reply-To: <20060405203741.GF14126@math.jussieu.fr> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405202100.GA28626@xor.obsecurity.org> <20060405203741.GF14126@math.jussieu.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
At 04:37 PM 05/04/2006, Albert Shih wrote:
>NB: Why this kind of problem can happen ? I ask this because until 6. I
>never have this kind of problem.
Think about it this way, if one of your users came to you and said,
"its not working. I need you to fix it"... You would start by getting
your user to provide details of what "it" is.
So when you ask "why this kind of problem can happen", you have not
provided any details as to what the problem is. The crash can be bad
hardware, it could be a change in any number of drivers. No one
knows what hardware you are using even. It could be something as
simple as a NIC driver regression or not. But without details, its
not possible to do anything.
Start by creating a debug kernel (see the website documentation on
how to do it and how to enable and save a crash dump) as well as by
providing a dmesg that shows the hardware you are using. The more
detail and description you provide in the PR, the better the chance
someone can fix it or help you work around it.
---Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.2.3.4.0.20060405164905.09e6d1c8>