Re: Problems with PCMCIA on AMD Alchemy DB1100

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2005-02-01 at 16:47 -0800, Pete Popov wrote:
> Josh Green wrote:
> > I'm using the latest Linux MIPS CVS (2.6.11-rc2) on an AMD Alchemy
> > DB1100 with a tool chain created with buildroot (gcc 3.4.3, binutils
> > 2.15.91.0.2) and found a bug in drivers/pcmcia/au1000_generic.c that was
> > causing the following error during initialization (not exact text, close
> > as I can remember), and subsequently the PCMCIA hardware was unavailable
> > (pcmcia_register_socket() was failing due to NULL resource_opts field).
> > 
> > au1x00_pcmcia: probe of au1x00-pcmcia0 failed with error -22
> 
> Interesting. I haven't seen this problem with a slightly older kernel.
> 

http://www.linux-mips.org/cvsweb/linux/drivers/pcmcia/cs.c.diff?r1=1.51&r2=1.52&f=h

The change around Line 212 looks like the reason.

<cut>

> Pete
> 

I'm still looking into those other problems.  I found another issue
though, which I'm unsure of the exact cause (seems related to hostap
module).  I get this from time to time:

Badness in local_bh_enable at kernel/softirq.c:140
Call Trace:
 [<802482c4>] skb_clone+0x24/0x374
 [<8012c3c8>] local_bh_enable+0x74/0x9c
 [<80251048>] dev_queue_xmit+0x310/0x374
 [<80249884>] kfree_skbmem+0x14/0x30
 [<c0064438>] hostap_data_start_xmit+0x80c/0xac4 [hostap]
 [<8024866c>] alloc_skb+0x58/0xf4
 [<802a1240>] arp_constructor+0x28/0x274
 [<802a0000>] udp_rcv+0x368/0x938
 [<80250e14>] dev_queue_xmit+0xdc/0x374
 [<80360000>] ip_auto_config_setup+0x64/0x240
 [<802a2944>] arp_process+0x7f8/0xa6c
 [<c0062b20>] hostap_80211_rx+0x1034/0x1f04 [hostap]
 [<80251978>] netif_receive_skb+0x1c4/0x3d4
 [<80251978>] netif_receive_skb+0x1c4/0x3d4
 [<80251c98>] process_backlog+0x110/0x2f0
 [<80250000>] dev_change_name+0x34/0x2ec
 [<c003f96c>] hostap_rx_tasklet+0x228/0x2bc [hostap_cs]
 [<80251f44>] net_rx_action+0xcc/0x294
 [<8012c818>] tasklet_action+0xc4/0x194
 [<801479f4>] handle_IRQ_event+0x7c/0x134
 [<8012c1dc>] __do_softirq+0x8c/0x14c
 [<80147c40>] __do_IRQ+0x194/0x1b4
 [<80360000>] ip_auto_config_setup+0x64/0x240
 [<80360000>] ip_auto_config_setup+0x64/0x240
 [<8012c328>] do_softirq+0x8c/0xb8
 [<80360000>] ip_auto_config_setup+0x64/0x240
 [<80100e2c>] au1000_IRQ+0x16c/0x1a0
 [<80360000>] ip_auto_config_setup+0x64/0x240
 [<80104a90>] cpu_idle+0x48/0x50
 [<80104a60>] cpu_idle+0x18/0x50
 [<801f4980>] idr_cache_ctor+0x0/0xc
 [<80360000>] ip_auto_config_setup+0x64/0x240
 [<803437ac>] start_kernel+0x200/0x2c0
 [<803430fc>] unknown_bootoption+0x0/0x310

Might not be a MIPS related problem though.  Seems line 140 is
"WARN_ON(irqs_disabled());" which is at the beginning of
local_bh_enable.  Cheers.
	Josh Green

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux MIPS Home]     [LKML Archive]     [Linux ARM Kernel]     [Linux ARM]     [Linux]     [Git]     [Yosemite News]     [Linux SCSI]     [Linux Hams]

  Powered by Linux