From: Stephen Hemminger <shemminger@osdl.org>
To: bernd-schubert@gmx.de
Cc: bernd.schubert@pci.uni-heidelberg.de, netdev@oss.sgi.com
Subject: Re: skge: reboot on sysfs resource0 access
Date: Fri, 9 Sep 2005 11:01:53 -0700 [thread overview]
Message-ID: <20050909110153.5a2e2e90@localhost.localdomain> (raw)
In-Reply-To: <200509091938.18079.bernd.schubert@pci.uni-heidelberg.de>
On Fri, 9 Sep 2005 19:38:17 +0200
Bernd Schubert <bernd.schubert@pci.uni-heidelberg.de> wrote:
> Hello,
>
> today we tried 2.6.13 on our server and also tried to use the skge driver.
> Well, in principle it works fine, until I became curious about the sysfs
> values. Stupid me, I was using the midnight commander to read the values.
> When I opened "/sys/bus/pci/drivers/skge/0000:01:01.0/resource0", the system
> immediately rebooted. After the reboot we tested using cat to the resource0
> file, which gave an input/output error. Using again the mc, the system again
> immediately rebooted.
> Well, I guess I better don't use the midnight commander in the future, but
> somehow I think it shouldn't cause the system to reboot, should it? Is the
> i/o error of cat supposed to happen?
>
Don't do that! resource0 is the pci space for the card and
reading it directly accesses the memory mapped space. The
register is sparse, and some places are unaccessable.
Accessing non-existent memory will cause system to hang and if you
are lucky a timeout and reboot.
Sorry, this is not a driver bug.
next prev parent reply other threads:[~2005-09-09 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 17:38 skge: reboot on sysfs resource0 access Bernd Schubert
2005-09-09 18:01 ` Stephen Hemminger [this message]
2005-09-09 18:09 ` Bernd Schubert
2005-09-09 18:21 ` Ben Greear
2005-09-12 11:01 ` Bernd Schubert
-- strict thread matches above, loose matches on Subject: below --
2005-09-09 17:34 Bernd Schubert
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=20050909110153.5a2e2e90@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=bernd-schubert@gmx.de \
--cc=bernd.schubert@pci.uni-heidelberg.de \
--cc=netdev@oss.sgi.com \
/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).