mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCMCIA regression
Date: Wed, 26 May 2010 13:35:15 +0200	[thread overview]
Message-ID: <20100526113515.GA7219@comet.dominikbrodowski.net> (raw)
In-Reply-To: <Pine.LNX.4.64.1005251619020.12278@hs20-bc2-1.build.redhat.com>

Hey,

On Tue, May 25, 2010 at 04:25:21PM -0400, Mikulas Patocka wrote:
> The commit a8408c17d0038b76a83affb1b56dc18fa1e7ed86 in Linux 2.6.34-rc6 
> broke pcmcia for me. I use 3c574 network card in yenta socket on Armada 
> 7400 laptop. My distribution is Debian lenny.
> 
> Reverting the test for "s->functions" in pccard_validate_cis makes the 
> network card work again.

Does this warning appear during reume, or during some other "special" use
case? Also, does commit cc83b08fc791045ac197e6f4a030599bcd7100c5 solve this
issue? If not: Could you enable dynamic debug logging via

# mount debugfs
mount none -t debugfs /sys/kernel/debug/

# enable debug
echo "module pcmcia +p" > /sys/kernel/debug/dynamic_debug/control
echo "module pcmcia_core +p" > /sys/kernel/debug/dynamic_debug/control
echo "module yenta_socket +p" > /sys/kernel/debug/dynamic_debug/control

and send me the resulting log (which may be looong).

Thanks,
	Dominik

  parent reply	other threads:[~2010-05-26 11:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-25 20:25 Mikulas Patocka
2010-05-26  7:14 ` Justin P. Mattock
2010-05-26 11:27   ` Mikulas Patocka
2010-05-26 13:29     ` Justin P. Mattock
2010-05-26 11:35 ` Dominik Brodowski [this message]
     [not found]   ` <20100602143822.GA11506@isilmar-3.linta.de>
2010-06-14 17:41     ` Another " Mikulas Patocka
2010-06-19 12:36       ` Dominik Brodowski

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=20100526113515.GA7219@comet.dominikbrodowski.net \
    --to=linux@dominikbrodowski.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpatocka@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
Powered by JetHome