mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: twaugh@redhat.com (Tim Waugh)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test11-pre7: isapnp hang
Date: Mon, 20 Nov 2000 00:09:06 +0000 (GMT)	[thread overview]
Message-ID: <E13xeWC-0003AP-00@the-village.bc.nu> (raw)
In-Reply-To: <20001119233450.H20970@redhat.com> from "Tim Waugh" at Nov 19, 2000 11:34:50 PM

> Reading from port 0x313 (my ISA NE2000 is at 0x300-0x31f) hangs my
> machine dead.  Unfortunately, reading from that port is exactly what
> the isapnp code does on boot, if compiled into the kernel.
> 
> Is it the network card's fault (probably), or is there a less invasive
> probe that isapnp could use (unlikely, I guess)?


That shouldnt be possible - we are supposed to start at 0x203 and skip the
problem area.


static int isapnp_next_rdp(void)
{
        int rdp = isapnp_rdp;
        while (rdp <= 0x3ff) {
                if (!check_region(rdp, 1)) {
                        isapnp_rdp = rdp;
                        return 0;
            	}
                rdp += RDP_STEP;
                /*
                 *      We cannot use NE2000 probe spaces for ISAPnP or we
                 *      will lock up machines.
                 */
                if(rdp >= 0x280 && rdp <= 0x380)
                        continue;
    	}
        return -1;
}

If you can find out why that port is being touched I'd like to know

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-20  0:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-19 23:34 Tim Waugh
2000-11-20  0:09 ` Alan Cox [this message]
2000-11-20  0:19   ` Alan Cox
2000-11-20  9:23     ` Tim Waugh
2000-11-20  0:32 ` H. Peter Anvin
2000-11-20  1:06   ` Alan Cox
2000-11-20  1:22     ` H. Peter Anvin
2000-11-20 12:45       ` Alan Cox

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=E13xeWC-0003AP-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=twaugh@redhat.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

all inboxes | Powered by JetHome®