Hello,
Since some time I'm getting the following log entries under 2.6.15:
Mar 7 05:42:48 tiger kernel: skge Ram write data parity error
Mar 7 05:42:48 tiger kernel: skge Ram read data parity error
Does this mean my hardware is faulty? The error message seems to imply
that, but since I am not experiencing any problems and a comment in
skge.c says
/* Parity errors seem to happen when Genesis is connected to a switch
* with no other ports present. Heartbeat error??
*/
talking about some other sort of parity error though ("mac parity") I'm
not sure any more. Can anybody enlighten me?
Thanks,
Aaron
--
Aaron Isotton | http://www.isotton.com/
I'll give you a definite maybe. --Samuel Goldwyn
On Tue, 07 Mar 2006 16:40:27 +0100
Aaron Isotton <[email protected]> wrote:
> Hello,
>
> Since some time I'm getting the following log entries under 2.6.15:
>
> Mar 7 05:42:48 tiger kernel: skge Ram write data parity error
> Mar 7 05:42:48 tiger kernel: skge Ram read data parity error
>
> Does this mean my hardware is faulty? The error message seems to imply
> that, but since I am not experiencing any problems and a comment in
> skge.c says
>
> /* Parity errors seem to happen when Genesis is connected to a switch
> * with no other ports present. Heartbeat error??
> */
>
> talking about some other sort of parity error though ("mac parity") I'm
> not sure any more. Can anybody enlighten me?
Which exact hardware is that, look for the skge line in the kernel log (dmesg)?
I am not a hardware wizard, but I wrote that comment. My guess is that it shows
up when the hardware decides to clock in some data that isn't really a packet
(line noise, etc). Both skge and sk98lin just clear the error and keep going.
Does it happen a lot or just once?