[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian/kernel's policy for fatal errors, etc.



Merciadri Luca wrote:
> When a computer stays turned on for a long amount of time, some problems
> could arise. I have the following questions:
> 
> 1. What habitually makes a computer 'running Linux) go down (except
> electric problems)?

One possibility is soft memory errors in the RAM.  Using ECC RAM
reduces the likely to a vanishingly small probability and has long
been the normal hardware for high quality systems.  But cheaper
commodity hardware desktops designed to run a well known commercial OS
these days uses cheaper non-ECC RAM since it doesn't make sense to be
more reliable than the target OS.  Linux tends to expose these systems
since it is very reliable in and of itself.

Another possibility is a kernel bug either in the main kernel core or
in a device driver.  Device drivers have a higher incidence of bugs
especially for unique low use niche hardware.  Popular devices are
better tested than hardware that only three people in the world use.
But kernel bugs in the public code are rare.  When found those are
fixed pretty quickly.

A third more common case is when closed source proprietary drivers are
loaded into the kernel such as a vendor's graphics driver.  Because
those are closed source there isn't any public review.  Bugs there are
frustrating to all since they can't be debugged by anyone but the
vendor and the vendor doesn't usually have access to your system nor
motivation to debug your system.  For high reliability you should
avoid loading any closed source proprietary driver, unless you
yourself are the author of it.

> 2. What are Debian/kernel's adaptations to prevent such problems from
> arising?

Debian adds few patches over and above the standard stock Linux
kernel.  Basically in this area (as far as I know) you are getting the
stock upstream Linux kernel capability.

Bob

Attachment: signature.asc
Description: Digital signature


Reply to: