From: Jon Dufresne <jon.dufresne@infinitevideocorporation.com>
To: Don Hiatt <DHiatt@zeugmasystems.com>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: RE: iomemory causing a data bus error
Date: Thu, 07 Feb 2008 16:40:34 -0500 [thread overview]
Message-ID: <1202420434.3298.53.camel@localhost> (raw)
In-Reply-To: <DDFD17CC94A9BD49A82147DDF7D545C57986CE@exchange.ZeugmaSystems.local>
> For ERR: http://lkml.org/lkml/2005/1/12/356
Thanks, I read through that. Seems like I could be dealing with some
imperfect hardware.
Whether or no my device is plugged into the box, I get an order of
magnitude of 10^4 ERRs. Does this seem like a huge amount to anyone
else?
Is there anything I can do to try to reduce this number? Or should I
even worry about it? Could this be connected to the device driver issues
I am having?
Thanks,
Jon
prev parent reply other threads:[~2008-02-07 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 15:20 iomemory causing a data bus error Jon Dufresne
2008-02-07 20:32 ` Jon Dufresne
[not found] ` <DDFD17CC94A9BD49A82147DDF7D545C57986B1@exchange.ZeugmaSystems.local>
2008-02-07 21:01 ` Jon Dufresne
[not found] ` <DDFD17CC94A9BD49A82147DDF7D545C57986CE@exchange.ZeugmaSystems.local>
2008-02-07 21:40 ` Jon Dufresne [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=1202420434.3298.53.camel@localhost \
--to=jon.dufresne@infinitevideocorporation.com \
--cc=DHiatt@zeugmasystems.com \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.