From: Pavel Machek <pavel@ucw.cz>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: kernel list <linux-kernel@vger.kernel.org>,
linux-pcmcia@lists.infradead.org, axboe@kernel.dk
Subject: [solution exits] no PCMCIA in 4.0-rc3
Date: Tue, 10 Mar 2015 21:31:58 +0100 [thread overview]
Message-ID: <20150310203158.GA16375@amd> (raw)
In-Reply-To: <20150302115725.53baae2f@lxorguk.ukuu.org.uk>
On Mon 2015-03-02 11:57:25, One Thousand Gnomes wrote:
> On Sat, 28 Feb 2015 00:08:52 +0100
> Pavel Machek <pavel@ucw.cz> wrote:
>
> > Hi!
> >
> > It seems that pcmcia was unhappy even before, but eject definitely
> > oopsed it.
> >
> > Any ideas?
>
> Probably a PCMCIA not a block layer change - well I guess could be
> either. I fixed a pile of PCMCIA bugs and also reworked the allocator for
> pure PCI boxes so it didn't do various bad things.
>
> Can you tweak drivers/pcmcia/Kconfig for config YENTA and make
>
> select PCCARD_PCI if PCMCIA !=n && !ISA
>
> instead do
>
> select PCCARD_NONSTATIC if PCMCIA !=n && !ISA
>
> rebuild and re-test
If I do that, it breaks compile. If I do that, and delete "config
PCCARD_PCI", it fixes PCMCIA. Thanks!
> The tracel looks like a block layer bug, but it would be nice to know if
> its one that PCMCIA used it hide, or its in fact potentially something
> else.
Yeah the trace was from 3.18. 4.0 is ok with this regard.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-03-10 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 23:08 4.0-rc1: Oops on eject of CF card in PCMCIA slot Pavel Machek
2015-03-02 11:57 ` One Thousand Gnomes
2015-03-09 20:57 ` Pavel Machek
2015-03-09 21:11 ` Pavel Machek
2015-03-10 20:31 ` Pavel Machek [this message]
2015-03-10 21:56 ` [solution exits] no PCMCIA in 4.0-rc3 One Thousand Gnomes
2015-03-11 13:33 ` Greg KH
2015-03-10 11:48 ` 4.0-rc2+: PATA CF card not detected in PCMCIA slot Pavel Machek
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=20150310203158.GA16375@amd \
--to=pavel@ucw.cz \
--cc=axboe@kernel.dk \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.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 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.