From: Adrian Bunk <bunk@kernel.org>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: "Oliver Pinter (Pintér Olivér)" <oliver.pntr@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
gregkh@suse.de
Subject: Re: [BUG] skge 0000:02:05: read data parity error
Date: Mon, 14 Jan 2008 23:01:05 +0200 [thread overview]
Message-ID: <20080114210105.GG9847@does.not.exist> (raw)
In-Reply-To: <20080114125200.28cb4c69@deepthought>
On Mon, Jan 14, 2008 at 12:52:00PM -0800, Stephen Hemminger wrote:
> On Mon, 14 Jan 2008 20:57:49 +0100
> "Oliver Pinter (Pintér Olivér)" <oliver.pntr@gmail.com> wrote:
>
> > Hi All!
> >
> > It is fully reproductable under 2.6.22.15, 2.6.23.13 (all tainted and
> > not tainted [4 different kernel] ) and 2 different PC:
> >
> > [BUG] skge 0000:02:05: read data parity error
> > [BUG] skge 0000:02:05: read data parity error
> >
> > steps:
> > 1. login as root
> > 2. start mc
> > 3. cd /sys/bus/pci/drivers/skge/0000:02:05.0
> > 4. press F3 (mcview) on resource0
> > 5. the system hang up, without panic or bug ... only this message
> > printed 2x: [BUG] skge 0000:02:05: read data parity error
>
> This is not a bug.
>
> The hardware has some debug registers that if accessed cause a read
> back to the host. Since this can point anywhere, it will cause errors
> or system hang.
>
> The point is don't do it.
Is it really a good idea that _reading_ files under /sys can kill your
machine?
That sounds like a huge trap for people debugging their machine (or e.g.
forgetting to exclude /sys from their backup).
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2008-01-14 21:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 19:57 [BUG] skge 0000:02:05: read data parity error Oliver Pinter (Pintér Olivér)
2008-01-14 20:52 ` Stephen Hemminger
2008-01-14 21:01 ` Adrian Bunk [this message]
2008-01-14 21:30 ` Greg KH
2008-01-14 21:31 ` Oliver Pinter (Pintér Olivér)
2008-01-14 21:34 ` Adrian Bunk
2008-01-14 21:41 ` Oliver Pinter (Pintér Olivér)
2008-01-14 21:48 ` Greg KH
2008-01-14 21:52 ` Adrian Bunk
2008-01-14 21:58 ` Oliver Pinter (Pintér Olivér)
2008-01-14 22:37 ` Stephen Hemminger
2008-01-14 21:38 ` Greg KH
2008-01-14 21:44 ` Oliver Pinter (Pintér Olivér)
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=20080114210105.GG9847@does.not.exist \
--to=bunk@kernel.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver.pntr@gmail.com \
--cc=shemminger@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).