[RFC v4] PCMCIA locking updates for 2.6.34

[Dominik Brodowski]

Hey,

On Tue, Jan 26, 2010 at 10:58:02PM +0100, Wolfram Sang wrote:
> On Sun, Jan 24, 2010 at 06:30:00PM +0100, Dominik Brodowski wrote:
> > Hey,
> > 
> > The v4 of the locking pathes are available in the git repository -- along
> > with a few other fixes and improvements -- at:
> > 
> >     git://git.kernel.org/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git#locking
> > 
> > Only those patches which changed (and which are marked with * below) will be
> > sent out to the PCMCIA list. Changes since v3:
> > 
> > - avoid prod_id memleak
> > - use pccardd for any requery work, not the workqueue
> 
> Okay, I tested your current locking-branch.
> 
> Changing PCMCIA-Cards works flawlessly. However:
> 
> 1) Insert a PCMCIA-network-card (I have two, doesn't matter which)
> 2) Remove it again
> 3) Insert a CardBus-Wireless card (Netgear WG511 in my case)
> 
> gives me a hard lockup! Nothing is printed, keyboard and mouse are dead.

Now that's strange -- especially as this works just fine over here
(different network cards, though). I guess it is repeatable with v4, but
did not happen with v3? If so, does it work fine with the "master" branch of
the PCMIA tree? Also, there is one more things you might want to try:

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
echo "15 4 1 7" > /proc/sys/kernel/printk

switch to the logging console (tty1?), insert/eject the PCMCIA card and
insert the CardBus card -- and take a photograph of the last log messages
you see.

Best,
	Dominik