From: Chris Rankin <rankincj@yahoo.com>
To: Dan Williams <dcbw@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: [2.6.23.9] hostap_plx locks up PC when reading PCI I/O memory
Date: Sun, 9 Dec 2007 19:41:58 +0000 (GMT) [thread overview]
Message-ID: <587622.50680.qm@web52902.mail.re2.yahoo.com> (raw)
In-Reply-To: <1193657365.19938.17.camel@localhost.localdomain>
Hi,
I've recently been having trouble loading the hostap_plx 802.11b wireless networking driver, and
this evening I managed to narrow the problem down to these lines of code by copying code from
hostap_plx into a "test driver" until the test driver also locked the PC up:
/* read CIS; it is in even offsets in the beginning of attr_mem */
for (i = 0; i < CIS_MAX_LEN; i++)
cis[i] = readb(attr_mem + 2 * i);
If I comment these lines out then my test driver just complains about the garbage CIS information
and fails gracefully. Leave these lines in and my PC freezes instantly.
These lines are part of the prism2_plx_check_cis() function, which is called when the module first
loads. CIX_MAX_LEN is a #define for 256, and cis is a u8* pointer previously allocated as:
cis = kmalloc(CIS_MAX_LEN, GFP_KERNEL);
attr_mem is one of the function's paramters, and is defined as void __iomem *attr_mem.
As far as I can tell, the PCI I/O memory information is correct, and matches what lspci tells me:
00:0e.0 Network controller: Netgear MA301 802.11b Wireless PCI Adapter (rev 02)
Subsystem: Netgear MA301 802.11b Wireless PCI Adapter
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+
FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR-
<PERR-
Interrupt: pin A routed to IRQ 5
Region 1: I/O ports at 1000 [size=128]
Region 2: Memory at e8002000 (32-bit, non-prefetchable) [size=4K]
Region 3: I/O ports at 1080 [size=64]
so there is apparently 4K of I/O memory at 0xe8002000.
Can anyone help me understand why my PC is locking up when it executes this code, please?
Thanks,
Chris
__________________________________________________________
Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com
next prev parent reply other threads:[~2007-12-09 19:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <511770.44451.qm@web52902.mail.re2.yahoo.com>
2007-10-29 7:36 ` [2.6.23.1] PCI device locking up the computer when its module loads 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 ` Chris Rankin [this message]
2007-12-09 21:33 ` [2.6.23.9] hostap_plx locks up PC when reading PCI I/O memory Arjan van de Ven
2007-12-09 22:06 ` Chris Rankin
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=587622.50680.qm@web52902.mail.re2.yahoo.com \
--to=rankincj@yahoo.com \
--cc=akpm@linux-foundation.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).