mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Rankin <rankincj@yahoo.com>
To: Dan Williams <dcbw@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Chris Rankin <rankincj@yahoo.com>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [2.6.23.1] PCI device locking up the computer when its module loads
Date: Sat, 8 Dec 2007 18:39:20 +0000 (GMT)	[thread overview]
Message-ID: <624437.35639.qm@web52911.mail.re2.yahoo.com> (raw)
In-Reply-To: <1193657365.19938.17.camel@localhost.localdomain>

> > On Mon, 22 Oct 2007 13:43:16 +0100 (BST) Chris Rankin <rankincj@yahoo.com> wrote:
> > > I have a Netgear MA301 PLX wireless networking adapter which wants to use the hostap_plx
> > > driver in Linux 2.6.23.1. This very same piece of hardware works fine in an old(!) P120
> > > machine running 2.4.33, but makes the 2.6.23.1 kernel freeze as soon as the
> > > pci_enable_device() function is called in prism2_plx_probe.

Interestingly, I have just discovered that I can do the following on this machine *without*
locking it up (on Linux 2.6.23.9):

# cat /sys/bus/pci/devices/0000:00:0e.0/enable
0
# echo 1 > /sys/bus/pci/devices/0000:00:0e.0/enable
# cat /sys/bus/pci/devices/0000:00:0e.0/enable
1

where according to lspci:

00:0e.0 Network controller: Netgear MA301 802.11b Wireless PCI Adapter (rev 02)

Doesn't writing to this sysfs file also call pci_enable_device()? Loading the hostap_plx module is
still instantly lethal.

Cheers,
Chris



      __________________________________________________________
Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com

  parent reply	other threads:[~2007-12-08 18:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 12:43 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 [this message]
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
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=624437.35639.qm@web52911.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

all inboxes | Powered by JetHome®