public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: linux-kernel@vger.kernel.org
Subject: Re: What is this: skge Ram read/write data parity error
Date: Tue, 7 Mar 2006 10:12:39 -0800	[thread overview]
Message-ID: <20060307101239.5de16cce@localhost.localdomain> (raw)
In-Reply-To: 440DA96B.5010604@isotton.com

On Tue, 07 Mar 2006 16:40:27 +0100
Aaron Isotton <aaron@isotton.com> 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?

      reply	other threads:[~2006-03-07 18:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07 15:40 What is this: skge Ram read/write data parity error Aaron Isotton
2006-03-07 18:12 ` Stephen Hemminger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060307101239.5de16cce@localhost.localdomain \
    --to=shemminger@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox