From: Chris Rankin <rankincj@yahoo.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Dan Williams <dcbw@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [2.6.23.9] hostap_plx locks up PC when reading PCI I/O memory
Date: Sun, 9 Dec 2007 22:06:21 +0000 (GMT) [thread overview]
Message-ID: <642708.11296.qm@web52902.mail.re2.yahoo.com> (raw)
In-Reply-To: <20071209133311.2db5ce4f@laptopd505.fenrus.org>
--- Arjan van de Ven <arjan@infradead.org> wrote:
> can you check if the attr_mem is properly ioremap'd ?
> (probably with ioremap_nocache)
Can you elaborate, please? I am not familiar with these I/O primitives.
> I wonder if there's anything else in that area as well..
So I should check /proc/iomem? But wouldn't Linux complain if two PCI devices conflicted as you're
suggesting?
Cheers,
Chris
___________________________________________________________
Support the World Aids Awareness campaign this month with Yahoo! For Good http://uk.promotions.yahoo.com/forgood/
next prev parent reply other threads:[~2007-12-09 22:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 12:43 [2.6.23.1] PCI device locking up the computer when its module loads Chris Rankin
2007-10-29 7:36 ` Andrew Morton
2007-10-29 11:29 ` Dan Williams
2007-10-29 11:39 ` Chris Rankin
2007-12-08 18:39 ` Chris Rankin
2007-12-09 19:41 ` [2.6.23.9] hostap_plx locks up PC when reading PCI I/O memory Chris Rankin
2007-12-09 21:33 ` Arjan van de Ven
2007-12-09 22:06 ` Chris Rankin [this message]
2007-12-09 22:32 ` Arjan van de Ven
2007-12-10 3:20 ` Chris Rankin
2007-12-10 16:40 ` Chris Rankin
2007-12-09 22:06 ` Stefano Brivio
2007-12-09 22:13 ` Chris Rankin
2007-12-09 23:42 ` Stefano Brivio
2007-12-12 1:11 ` Andrew Morton
2007-12-12 8:56 ` Chris Rankin
2007-12-12 10:03 ` Andrew Morton
2007-12-12 10:22 ` Chris Rankin
2007-12-12 20:45 ` Chris Rankin
2007-12-28 1:39 ` Chris Rankin
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=642708.11296.qm@web52902.mail.re2.yahoo.com \
--to=rankincj@yahoo.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=dcbw@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).