Date: Sun, 21 Mar 2004 17:48:18 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: =?ISO-8859-1?Q?S=F8ren?= Schmidt <sos@DeepCore.dk> Cc: Putinas Piliponis <putinas.piliponis@icnspot.net> Subject: Re: system lockup - ata spurious interrupts - somehow updated Message-ID: <20040321174818.2de0a4ea@Magellan.Leidinger.net> In-Reply-To: <405DB4AB.1010306@DeepCore.dk> References: <405B9DCD.9040907@6by9.org> <0a0c01c40e90$2d86e070$32cba1cd@science1> <000401c40f33$86ce9210$1e64a8c0@spotripoli.local> <405D7D7F.3090209@DeepCore.dk> <20040321140202.5e93401c@Magellan.Leidinger.net> <405DB4AB.1010306@DeepCore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 21 Mar 2004 16:28:43 +0100
S=F8ren Schmidt <sos@DeepCore.dk> wrote:
> > I have the hardware and I'm willing to fix this problem. What kernel
> > clue are we talking about?
>=20
> Enough to know your way around the kernel, instrument code to see what=20
> is going on and do new code bits to fix potential problems etc etc, that=
=20
> kind of thing. In some cases having test HW around to see if there are=20
> physical interrupts delivered, if devices are really selected on the HW=20
> level etc, can be very handy as well..
So it's not about look at X for Y and at Z for K? I don't have
measurement hardware, but I could instrument code and lookout for
specific things if somebody tells me where and what I have to look
for...
Bye,
Alexander.
--=20
I will be available to get hired in April 2004.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint =3D C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040321174818.2de0a4ea>