Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 May 2003 13:27:13 +0100
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        Robert Storey <y2kbug@ms25.hinet.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: bad kernel fried motherboard???
Message-ID:  <20030524122713.GA29846@happy-idiot-talk.infracaninophile.co.uk>
In-Reply-To: <200305242016.21540.y2kbug@ms25.hinet.net>
References:  <200305242016.21540.y2kbug@ms25.hinet.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--2oS5YaxWCcQjTEyO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, May 24, 2003 at 08:16:21PM +0800, Robert Storey wrote:
> I've been offline for a few days because it seems my motherboard is fried=
=2E I'm=20
> sending this message from another machine.
>=20
> The really WEIRD thing - I had just recompiled a Linux kernel, then reboo=
ted,=20
> got a "kernel panic". Tried rebooting again into single-user mode, but ke=
rnel=20
> panic again. Next attempt to reboot into the old kernel, but this time=20
> nothing at all - no video, the motherboard just died.
>=20
> My question - is there any possibility that a misconfigured kernel could =
harm=20
> the hardware? Or is it just a strange coincidence that "kernel panic" was=
=20
> followed by real hardware failure?
>=20
> Sorry, I know this is off-topic, it was Linux not FreeBSD, but I'm still =
sort=20
> of dazed.

It's highly unlikely that booting up a FreeBSD or Linux kernel will
lead to hardware failure due to bad or malicious coding --- the core
people of both groups have too much invested in their products to
knowingly permit such a thing, and they are not going to be easy to
trick into accepting it either.

On the other hand, compiling a kernel will exercise your system,
raising the temperature of the CPU and memory, which tends to make
failure more likely.  Similarly rebooting a system (especially if you
power it off) is a vulnerable time.  But you could achieve the same
effect by compiling any large package, or rebooting for some other
reason.  It's also the case that kit which does fail in this way is
probably pretty marginal anyhow, and all you've really done is hasten
the inevitable by a few days or weeks.

Oh -- the kernel panic is the symptom of the failure, not the cause.
Chances are it's the memory or CPU or video card that will fail before
the motherboard, which you may be able to diagnose by judicious
swapping of components.

	Cheers,

	Matthew

--=20
Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK

--2oS5YaxWCcQjTEyO
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQE+z2UhdtESqEQa7a0RAjPKAJ9j2NqSU7UX/75gAjBw8KZVn2s96gCdHXes
VQoxoD6BQGt0SpyNd4S8gWU=
=JYx0
-----END PGP SIGNATURE-----

--2oS5YaxWCcQjTEyO--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030524122713.GA29846>