All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Adrian Bunk <bunk@kernel.org>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
	"Oliver Pinter (Pint??r Oliv??r)" <oliver.pntr@gmail.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [BUG] skge 0000:02:05: read data parity error
Date: Mon, 14 Jan 2008 13:30:54 -0800	[thread overview]
Message-ID: <20080114213054.GA3573@suse.de> (raw)
In-Reply-To: <20080114210105.GG9847@does.not.exist>

On Mon, Jan 14, 2008 at 11:01:05PM +0200, Adrian Bunk wrote:
> 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?

No, but mmapping them as root and then doing bad things with that data
isn't recommended :)

Note that this is a special file, just like the ones in /proc, that
provide a mmap interface into the pci card's resource.  This is nothing
new...

thanks,

greg k-h

  reply	other threads:[~2008-01-14 21:30 UTC|newest]

Thread overview: 15+ 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 20:52   ` Stephen Hemminger
2008-01-14 21:01   ` Adrian Bunk
2008-01-14 21:01     ` Adrian Bunk
2008-01-14 21:30     ` Greg KH [this message]
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=20080114213054.GA3573@suse.de \
    --to=gregkh@suse.de \
    --cc=bunk@kernel.org \
    --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 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.