From: Paul Mackerras <paulus@samba.org>
To: Alan Ford <alan@whirlnet.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.17-pre2 & PCMCIA Errors
Date: Mon, 3 Dec 2001 15:29:57 +1100 (EST) [thread overview]
Message-ID: <15370.65477.649725.353028@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <20011202203207.A1014@whirlnet.co.uk>
In-Reply-To: <20011202203207.A1014@whirlnet.co.uk>
Alan Ford writes:
> Just tried 2.4.17-pre2 (was previously on 2.4.16-pre1) and when pcmcia-cs is
> started on bootup, the following happens:
>
> cs: IO port probe 0x0c00-0x0cff: clean.
> cs: IO port probe 0x0100-0x04ff: excluding 0x4d0-0x4d7
> cs: IO port probe 0x0a00-0x0aff: clean.
> cs: memory probe 0xa0000000-0xa0ffffff:<1>Unable to handle kernel NULL pointer
> dereference at virtual address 00000004
Please try this patch and let me know whether it fixes the problem.
Paul.
diff -urN linux-2.4.17-pre2/drivers/pcmcia/rsrc_mgr.c pmac/drivers/pcmcia/rsrc_mgr.c
--- linux-2.4.17-pre2/drivers/pcmcia/rsrc_mgr.c Sat Dec 1 15:49:24 2001
+++ pmac/drivers/pcmcia/rsrc_mgr.c Mon Dec 3 14:28:16 2001
@@ -107,17 +107,19 @@
static struct resource *resource_parent(unsigned long b, unsigned long n,
int flags, struct pci_dev *dev)
{
- struct resource res;
+ struct resource res, *pr;
- if (dev == NULL) {
- if (flags & IORESOURCE_MEM)
- return &iomem_resource;
- return &ioport_resource;
+ if (dev != NULL) {
+ res.start = b;
+ res.end = b + n - 1;
+ res.flags = flags;
+ pr = pci_find_parent_resource(dev, &res);
+ if (pr)
+ return pr;
}
- res.start = b;
- res.end = b + n - 1;
- res.flags = flags;
- return pci_find_parent_resource(dev, &res);
+ if (flags & IORESOURCE_MEM)
+ return &iomem_resource;
+ return &ioport_resource;
}
static inline int check_io_resource(unsigned long b, unsigned long n,
next prev parent reply other threads:[~2001-12-03 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 20:32 Alan Ford
2001-12-03 4:29 ` Paul Mackerras [this message]
2001-12-03 9:19 ` Alan Ford
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=15370.65477.649725.353028@argo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=alan@whirlnet.co.uk \
--cc=linux-kernel@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®