[Prism54-users] WG511 pcmcia IRQ problem

[Georg Schild]

Doc Nielsen wrote:

>hia list.
>
>I've been having a bit of problems getting my netgear wg511 working. 
>It is the "made in china version" but it does seem to load as it's
>supposed to do. I think my problem is with my settings however i am
>not sure.
>
>I have uploaded a combined log of messages and syslog, to
>http://docnielsen.dk/tmp/inserted.log , which states that for some
>reason, the card is inserted, hotplug loads the driver, then bitches
>about no 'reset complete' IRQ seen.
>
>Since my Yenta driver claims to use IRQ 10 on both ports and my other
>(wired) netcard claims IRQ 3 when inserted, why can't i see what IRQ
>my wireless card is given?
>Any suggestions as to how to get it working?
>What am i doing wrong?
>
>- Doc
>  
>
Hi guys!

I wanted to use my SMC2835 today to build up a temporary ad-hoc network
and i recognized the same IRQ-problems. atm i am using a 2.6.11.5 kernel
wth just two patches and noone of them is affecting IRQ-handling or
prism-driver. i am sure the card once worked with 2.6.10 and before.
here a cut of the errors:

> Mar 29 12:46:01 baerbel PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
> Mar 29 12:46:01 baerbel ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 17
> (level, low) -> IRQ 185
> Mar 29 12:46:01 baerbel eth3: resetting device...
> Mar 29 12:46:02 baerbel eth3: no 'reset complete' IRQ seen - retrying
> Mar 29 12:46:03 baerbel eth3: no 'reset complete' IRQ seen - retrying
> Mar 29 12:46:03 baerbel eth3: interface reset failure
> Mar 29 12:46:03 baerbel prism54: Your card/socket may be faulty, or
> IRQ line too busy :(
> Mar 29 12:46:03 baerbel eth3: resetting device...
> Mar 29 12:46:04 baerbel eth3: no 'reset complete' IRQ seen - retrying
> Mar 29 12:46:05 baerbel eth3: no 'reset complete' IRQ seen - retrying
> Mar 29 12:46:05 baerbel eth3: interface reset failure
> Mar 29 12:46:05 baerbel prism54: Your card/socket may be faulty, or
> IRQ line too busy :(

 those messages appear a few times and then stop. i tried the second
pcmcia-port then and removed the card before the messages stopped to
appear. i got some nice messages then ;)

> Mar 29 12:46:08 baerbel ----------- [cut here ] --------- [please bite
> here ] ---------
> Mar 29 12:46:08 baerbel Kernel BUG at islpci_dev:950
> Mar 29 12:46:08 baerbel invalid operand: 0000 [1] PREEMPT
> Mar 29 12:46:08 baerbel CPU 0
> Mar 29 12:46:08 baerbel Modules linked in: fglrx ndiswrapper
> Mar 29 12:46:08 baerbel Pid: 20086, comm: wpa_supplicant Tainted: P  
> M  2.6.11.5
> Mar 29 12:46:08 baerbel RIP: 0010:[<ffffffff802f35de>]
> <ffffffff802f35de>{islpci_set_state+126}
> Mar 29 12:46:08 baerbel RSP: 0018:ffff810015215cd0  EFLAGS: 00010206
> Mar 29 12:46:08 baerbel RAX: 0000000000000000 RBX: ffff810015320000
> RCX: ffff810015215e48
> Mar 29 12:46:08 baerbel RDX: 0000000000000003 RSI: 0000000000000003
> RDI: ffff810006b8e360
> Mar 29 12:46:08 baerbel RBP: ffff810006b8e360 R08: 0000000000000003
> R09: 0000000000000074
> Mar 29 12:46:08 baerbel R10: 0000000000000068 R11: 0000000000000246
> R12: 0000000000000000
> Mar 29 12:46:08 baerbel R13: ffff810015215e38 R14: 0000000000000000
> R15: ffffffff802f1820
> Mar 29 12:46:08 baerbel FS:  000000000069c0a0(0000)
> GS:ffffffff8064dd80(0000) knlGS:00000000087138c0
> Mar 29 12:46:08 baerbel CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> Mar 29 12:46:08 baerbel CR2: 00002aaaae7ab000 CR3: 00000000156a7000
> CR4: 00000000000006e0
> Mar 29 12:46:08 baerbel Process wpa_supplicant (pid: 20086, threadinfo
> ffff810015214000, task ffff81001369f7a0)
> Mar 29 12:46:08 baerbel Stack: ffffffff802f3990 0000000000000000
> ffff810015215d20 ffffffff80130b2e
> Mar 29 12:46:08 baerbel 0000000300000000 ffffffff805b5880
> ffffffff805b5888 ffff810015215d40
> Mar 29 12:46:08 baerbel 00000000fffffff7 00007fffffffd6a0
> Mar 29 12:46:08 baerbel Call Trace:<ffffffff802f3990>{islpci_reset+48}
> <ffffffff80130b2e>{__wake_up_common+62}
> Mar 29 12:46:08 baerbel <ffffffff80130b2e>{__wake_up_common+62}
> <ffffffff802f1832>{prism54_reset+18}
> Mar 29 12:46:08 baerbel
> <ffffffff803fcedc>{wireless_process_ioctl+1276}
> <ffffffff804816fb>{__down_failed+53}
> Mar 29 12:46:08 baerbel <ffffffff803f34bf>{dev_ioctl+1087}
> <ffffffff801472d7>{synchronize_kernel+55}
> Mar 29 12:46:08 baerbel <ffffffff80254448>{sprintf+136}
> <ffffffff80147290>{wakeme_after_rcu+0}
> Mar 29 12:46:08 baerbel <ffffffff8043e5af>{packet_do_bind+287}
> <ffffffff803e83fb>{sock_ioctl+75}
> Mar 29 12:46:08 baerbel <ffffffff80189a2a>{do_ioctl+58}
> <ffffffff80189ddc>{vfs_ioctl+844}
> Mar 29 12:46:08 baerbel <ffffffff80189e4d>{sys_ioctl+77}
> <ffffffff8010e3d6>{system_call+126}
> Mar 29 12:46:08 baerbel
> Mar 29 12:46:08 baerbel
> Mar 29 12:46:08 baerbel Code: 0f 0b 2b 8a 4c 80 ff ff ff ff b6 03 66
> 66 90 66 66 90 48 83
> Mar 29 12:46:08 baerbel RIP <ffffffff802f35de>{islpci_set_state+126}
> RSP <ffff810015215cd0>
> Mar 29 12:46:08 baerbel <3>KERNEL: assertion
> (!atomic_read(&sk->sk_rmem_alloc)) failed at net/netlink/af_netlink.c
> (122)
> Mar 29 12:46:09 baerbel hald[12434]: Timed out waiting for hotplug
> event 1294. Rebasing to 1295


maybe someone has an idea on this, atm i am using an internal
broadcom-chip so this is not a big problem. if i missed already a
solution please point me there, i had to recognize today that my emails
are quite a mess so it is possible that i missed something ;)

regards

georg schild