From: rct@gherkin.frus.com (Bob Tracy)
To: linux@dominikbrodowski.net
Cc: linix-pcmcia@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.12 vs. /sbin/cardmgr
Date: Sat, 16 Jul 2005 11:36:45 -0500 (CDT) [thread overview]
Message-ID: <20050716163645.8FD8DDBA1@gherkin.frus.com> (raw)
In-Reply-To: "from (env: rct) at Jul 15, 2005 11:01:39 pm"
rct wrote:
> Dominik Brodowski wrote:
> > On Sun, Jul 10, 2005 at 03:37:22PM -0500, Bob Tracy wrote:
> > > Dominik Brodowski wrote:
> > > > On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote:
> > > > > (/sbin/cardmgr chewing up lots of CPU cycles with 2.6.12 kernel)
> > > >
> > > > Please post the output of "lspci" and "lsmod" as I'd like to know which
> > > > kind of PCMCIA bridge is in your notebook.
> >
> > OK, it's a plain TI1225. Could you try whether the bug is still existent in
> > 2.6.13-rc3, please?
>
> 2.6.13-rc3 works fine here. The "cardmgr" process is no longer chewing
> up lots of CPU time, and otherwise seems to be working correctly. Thanks!
I spoke too soon :-(. The first boot on 2.6.13-rc3 was fine. Every
boot since then has reflected no change relative to the 2.6.12 behavior.
The "cardmgr" process racks up CPU time almost as fast as time
elapses: it's at the top of the "top" list.
--
-----------------------------------------------------------------------
Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------
next reply other threads:[~2005-07-16 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 16:36 Bob Tracy [this message]
2005-07-16 21:28 ` Dominik Brodowski
2005-07-17 2:30 ` Grant Coady
-- strict thread matches above, loose matches on Subject: below --
2005-07-09 5:12 Bob Tracy
2005-07-10 18:46 ` Dominik Brodowski
2005-07-10 20:37 ` Bob Tracy
2005-07-15 17:23 ` Dominik Brodowski
2005-07-16 4:01 ` Bob Tracy
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=20050716163645.8FD8DDBA1@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=linix-pcmcia@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.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 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®