All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Pavel Machek <pavel@ucw.cz>
Cc: Richard Purdie <rpurdie@rpsys.net>,
	Dominik Brodowski <linux@dominikbrodowski.net>,
	linux-pcmcia@lists.infradead.org, lenz@cs.wisc.edu,
	kernel list <linux-kernel@vger.kernel.org>,
	metan@seznam.cz
Subject: Re: 2.6.17-rc1: collie -- oopsen in pccardd?
Date: Thu, 13 Apr 2006 17:54:52 +0100	[thread overview]
Message-ID: <20060413165452.GA7805@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20060413164706.GB18635@atrey.karlin.mff.cuni.cz>

On Thu, Apr 13, 2006 at 06:47:06PM +0200, Pavel Machek wrote:
> Hi!
> 
> > > > > I'm getting some oopses when inserting/removing pccard (on collie,
> > > > > oopses in pccardd). It does not break boot, so it is not immediate
> > > > > problem, but I wonder if it also happens on non-collie machines?
> > > > 
> > > > No idea what so ever.  Not even any clues as to what might be going wrong
> > > > due to the lack of oops dump.  (Not that I even look after PCMCIA anymore.)
> > > 
> > > Sorry for lack of oops. I was not expecting you to debug it, I
> > > expected some voices telling me it is broken for them, too :-).
> > 
> > With a recent git kernel (907d91d708d9999bec0185d630062576ac4181a7) I
> > see the oops below when booting spitz (SL-C3000 - ARM pxa270 based). Was
> > this the same oops you saw Pavel?
> 
> I think so.

diff --git a/drivers/pcmcia/pcmcia_resource.c b/drivers/pcmcia/pcmcia_resource.c
--- a/drivers/pcmcia/pcmcia_resource.c
+++ b/drivers/pcmcia/pcmcia_resource.c
@@ -89,7 +88,7 @@ static int alloc_io_space(struct pcmcia_
        }
        if ((s->features & SS_CAP_STATIC_MAP) && s->io_offset) {
                *base = s->io_offset | (*base & 0x0fff);
-               s->io[0].Attributes = attr;
+               s->io[0].res->flags = (s->io[0].res->flags & ~IORESOURCE_BITS) | (attr & IORESOURCE_BITS);
                return 0;
        }
        /* Check for an already-allocated window that must conflict with

will probably be the culpret - which is from commit
c7d006935dfda9174187aa557e94a137ced10c30.

Static maps do not have IO resources, so s->io[].Attributes was not a
"duplicated" field in this case.  This part of this change needs
reverting.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2006-04-13 16:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 12:22 2.6.17-rc1: collie -- oopsen in pccardd? Pavel Machek
2006-04-04 12:43 ` Russell King
2006-04-04  0:01   ` Pavel Machek
2006-04-13 10:11     ` Richard Purdie
2006-04-13 16:47       ` Pavel Machek
2006-04-13 16:54         ` Russell King [this message]
2006-04-13 17:14           ` Dominik Brodowski
2006-04-13 19:19             ` Pavel Machek
2006-04-13 23:18             ` Richard Purdie

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=20060413165452.GA7805@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=lenz@cs.wisc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=linux@dominikbrodowski.net \
    --cc=metan@seznam.cz \
    --cc=pavel@ucw.cz \
    --cc=rpurdie@rpsys.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.