D-Link DCF-660W and wlanctl-ng causes kernel panic

Solomon Peachy wrote:
> On Wed, Oct 04, 2006 at 04:39:29PM -0500, Dzuy Nguyen
wrote:
>   
>> I have a D-Link DCF-660W card plugged in a PPC
2.6.12 kernel with
>> wlan 0.2.3 and it panics every time.  I disable
/etc/pcmcia/wlan-ng script
>> and manually run
>>     
>
> Does this still happen with the latest (0.2.5) release?
>   
I have not tried 0.2.5, but I reading the CHANGES in the
release, it
does not seem
to have anything to address this issue.
>   
>> Oops: kernel access of bad area, sig: 11 [#1]
>>     
>
> Your'e not saying which architechure his is on, but I'm
guessing an 
> embedded PPC.  You didn't provide a symbol dump (use
insmod -m 
> modulename.o) so the backtrace is fairly useless..
>   
Yes, it's embedded PPC, 8xx processor type.  There is no -m
option in
insmod,
certainly not from busybox.  Are you referring to 2.4 kernel
convention
(modulename.o)?
This is 2.6.12 kernel (.ko).

Where do I start to debug this problem?  I compiled wlan
with debug
turned on.
The last function in the code was in
hfa384x_cmd_initialize(), but  you
probably
could have guessed that since it was just about to enable
the interface.
>  - Solomon
>   
_______________________________________________
Linux-wlan-user mailing list
Linux-wlan-userlists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-w
lan-user

On Thu, Oct 05, 2006 at 08:54:42AM -0500, Dzuy Nguyen wrote:
> I have not tried 0.2.5, but I reading the CHANGES in
the release, it
> does not seem
> to have anything to address this issue.

Perhaps not that specifically, but it's certianly possible
that it was 
inadvertantly fixed.

> Yes, it's embedded PPC, 8xx processor type.  There is
no -m option in
> insmod,
> certainly not from busybox.  Are you referring to 2.4
kernel convention
> (modulename.o)?
> This is 2.6.12 kernel (.ko).

What I wanted was the module symbol output.  -m gives it to
you on 
busybox built for 2.4 support, at least.  

> Where do I start to debug this problem?  I compiled
wlan with debug
> turned on.
> The last function in the code was in
hfa384x_cmd_initialize(), but  you
> probably
> could have guessed that since it was just about to
enable the interface.

Then the simplest way is binary searching to figure what
line in that 
function is causing you to crash.

I'd recommend you update to 0.2.5 first, though.

 - Solomon
-- 
Solomon Peachy                        solomonlinux-wlan.com
AbsoluteValue Systems                 http://www.linux-wlan.com
721-D North Drive                     +1 (321) 259-0737 
(office)
Melbourne, FL 32934                   +1 (321) 259-0286 
(fax)
_______________________________________________
Linux-wlan-user mailing list
Linux-wlan-userlists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-w
lan-user

Solomon,

I tried 0.2.5 and it miraculously works, Thanks!

BTW, there is a bug in 0.2.5.  In prism2_cs.c, line 44
defines
int prismsta_config(), but the actual function
implementation
at line 880 says void prismsta_config(), which causes an
error
when compiled.

Thanks,

Dzuy

Solomon Peachy wrote:
> On Thu, Oct 05, 2006 at 08:54:42AM -0500, Dzuy Nguyen
wrote:
>   
>> I have not tried 0.2.5, but I reading the CHANGES
in the release, it
>> does not seem
>> to have anything to address this issue.
>>     
>
> Perhaps not that specifically, but it's certianly
possible that it was 
> inadvertantly fixed.
>
>   
>> Yes, it's embedded PPC, 8xx processor type.  There
is no -m option in
>> insmod,
>> certainly not from busybox.  Are you referring to
2.4 kernel convention
>> (modulename.o)?
>> This is 2.6.12 kernel (.ko).
>>     
>
> What I wanted was the module symbol output.  -m gives
it to you on 
> busybox built for 2.4 support, at least.  
>
>   
>> Where do I start to debug this problem?  I compiled
wlan with debug
>> turned on.
>> The last function in the code was in
hfa384x_cmd_initialize(), but  you
>> probably
>> could have guessed that since it was just about to
enable the interface.
>>     
>
> Then the simplest way is binary searching to figure
what line in that 
> function is causing you to crash.
>
> I'd recommend you update to 0.2.5 first, though.
>
>  - Solomon
>   
_______________________________________________
Linux-wlan-user mailing list
Linux-wlan-userlists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-w
lan-user