Re: [Madwifi-users] HAL crash with an atheros 5212

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

The driver most definitely operates with 5212 devices.
Recent hal changes have been needed to support newer analog chips
(which attach to the 5212).   The 20030802 driver won't handle the newer 
rf chips
and does have bugs.   If you use the current CVS version, there should 
not be any problems
if you have a reasonably recent kernel and current wireless tools package.
Yes, we should update the stable release so that newcomers don't have to 
seek
out advice and cvs files after failing with 20030802.

g

del...@pa... wrote:

>I was under the impression that the D-Link DWL-AG650 was supported
>under the madwifi-20030802 driver (the atheros 5212 chip), and so I purchased
>it, but I am having problems making it work: the HAL layer of madwifi
>segfaults (NULL dereference) when iwconfig tries to set the SSID.
>
>The README with the driver says the 5212 is supported, but I happened
>across a reply Sam gave in the developer list with a comment that
>appears inconsistent with the README:
>
>
>Sam> Per-packet TPC is possible on the 5212 and later parts but isn't yet available 
>Sam> (even for Atheros drivers).  It will happen together with support for 
>Sam> hardware multi-rate retranismission (another 5212-specific feature).  Right 
>Sam> now the main focus is getting support in for a new part that has already hit 
>Sam> the retail channels and which, unfortunately, the existing HAL code doesn't 
>Sam> handle properly (instead of rejecting the part as unsupported it attaches and 
>Sam> then jumps through a null function pointer--oops).
>
>The thread designation was:
>What does the HAL actually do ?	Anthony Wright <awright@ov...> 2003-10-20 08:48
>
>
>So now I am wondering is the 5212 supported or isn't it?  And if not,
>can I get it supported now that I've bought the card and how?
>
>
>Essentially the same problem was reported in this group in October but
>there were no replies.  The message description was:
>
>Kernel oops with DWL-AG650 (atheros 5212)	Thomas Backmark <total@vi...> 	2003-10-30 08:34
>
>He went to much greater lengths to try other options than I did to get
>things to work: they didn't improve the situation.  The problem
>appears to be in the HAL we can't modify easily..
>
>I found another comment by Sam in November that a new HAL was on its
>way, and so I tried to pull CVS down, but I can't find a HAL of any
>sort there (the one included with 20030802 or otherwise).  Maybe
>someone can point me in the right direction to obtain the latest HAL
>and this might solve the problem.
>
>
>
>In case it clarifies I'll give a system profile and log dump.
>
>My kernel is 2.4.20-13.9 in a RedHat 9 system on a Dell Inspiron 8100.
>I'm using the madwifi-20030802 release which I got to compile and
>install with only a few minor changes to find the kernel headers under
>the RedHat layout.
>
>* /sbin/lspci's output.
>
>00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 04)
>00:01.0 PCI bridge: Intel Corp. 82815 815 Chipset AGP Bridge (rev 04)
>00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 03)
>00:1f.0 ISA bridge: Intel Corp. 82801BAM ISA Bridge (LPC) (rev 03)
>00:1f.1 IDE interface: Intel Corp. 82801BAM IDE U100 (rev 03)
>00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 03)
>01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 Go] (rev b2)
>02:03.0 Multimedia audio controller: ESS Technology ES1983S Maestro-3i PCI Audio Accelerator (rev 10)
>02:06.0 PCI bridge: Actiontec Electronics Inc: Unknown device 0100 (rev 11)
>02:0f.0 CardBus bridge: Texas Instruments PCI4451 PC card Cardbus Controller
>02:0f.1 CardBus bridge: Texas Instruments PCI4451 PC card Cardbus Controller
>02:0f.2 FireWire (IEEE 1394): Texas Instruments PCI4451 IEEE-1394 Controller
>08:04.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
>08:08.0 Communication controller: Lucent Microelectronics WinModem 56k (rev 01)
>
>
>* What follows is the relevant part of the message log: note the NULL pointer dereference.
>
> kernel: cs: cb_alloc(bus 9): vendor 0x168c, device 0x0013
> kernel: PCI: Enabling device 09:00.0 (0000 -> 0002)
> cardmgr[9539]: socket 0: CardBus hotplug device
> /etc/hotplug/pci.agent: Setup ath_pci for PCI slot 09:00.0Dec 30 16:16:31 host kernel: ath_hal: 0.9.5.3 BETA (Sam Leffler <sa...@er...>)
> kernel: wlan: 0.7.1.1 BETA (Sam Leffler <sa...@er...>)
> kernel: ath_pci: 0.8.3.2 BETA (Sam Leffler <sa...@er...>)
> kernel: ath_pci: cache line size not set; forcing 32
> kernel: ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
> kernel: ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
> kernel: ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
> kernel: ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
> kernel: ath0: 802.11 address: xx:xx:xx:xx:xx:xx
> kernel: ath0: Atheros 5212: mem=0x20800000, irq=10
> insmod: Warning: loading /lib/modules/2.4.20-13.9/net/ath_hal.o will taint the kernel: non-GPL license - Proprietary
> insmod:   See http://www.tux.org/lkml/#export-tainted for information about tainted modules
> insmod: Module ath_hal loaded, with warnings
> insmod: Module wlan loaded, with warnings
> insmod: Module ath_pci loaded, with warnings
> /etc/hotplug/net.agent: invoke ifup ath0
> kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
> kernel:  printing eip:
> kernel: 00000000
> kernel: *pde = 00000000
> kernel: Oops: 0000
> kernel: ath_pci wlan ath_hal ds yenta_socket pcmcia_core ide-cd cdrom maestro3 ac97_codec soundcore nvidia e100 ohci1394 ieee1394 loop lvm-mod keybdev mousedev hid in
> kernel: CPU:    0
> kernel: EIP:    0060:[<00000000>]    Tainted: P
> kernel: EFLAGS: 00010292
> kernel:
> kernel: EIP is at [unresolved] (2.4.20-13.9)
> kernel: eax: d7a1dd90   ebx: d96a4000   ecx: d7a1dd6e   edx: e1ba9054
> kernel: esi: d7a1dea8   edi: d7a1dd90   ebp: d96a4000   esp: d7a1dd3c
> kernel: ds: 0068   es: 0068   ss: 0068
> kernel: Process iwconfig (pid: 9862, stackpage=d7a1d000)
> kernel: Stack: e1ba115a d96a4000 d7a1dd90 d7a1dd6c d7a1dd6e d7a1dea8 d7a1dd6e 00000000
> kernel:        00030003 00000001 00000c10 00000034 00200016 00200020 00200020 001c0020
> kernel:        0016001a 00000000 00000000 00000000 00200000 00000000 00000000 00000000
> kernel: Call Trace:   [<e1ba115a>] zz05b781e0 [ath_hal] 0xf52 (0xd7a1dd3c))
> kernel: [<e1ba81f8>] .rodata [ath_hal] 0x46f8 (0xd7a1de28))
> kernel: [<e1b9fc4a>] zz0002dbd2 [ath_hal] 0x486 (0xd7a1de2c))
> kernel: [<e1bbb96d>] ath_init [ath_pci] 0x75 (0xd7a1de7c))
> kernel: [<c01309be>] do_no_page [kernel] 0x16e (0xd7a1de9c))
> kernel: [<e1bb4a45>] ieee80211_ioctl_siwencode [wlan] 0x10b (0xd7a1debc))
> kernel: [<e1bb493a>] ieee80211_ioctl_siwencode [wlan] 0x0 (0xd7a1dedc))
> kernel: [<c01ff792>] ioctl_standard_call [kernel] 0x1b2 (0xd7a1deec))
> kernel: [<c01ff1db>] wireless_process_ioctl [kernel] 0x8b (0xd7a1df24))
> kernel: [<e1bb493a>] ieee80211_ioctl_siwencode [wlan] 0x0 (0xd7a1df34))
> kernel: [<c01f86ef>] dev_ioctl [kernel] 0x1ff (0xd7a1df44))
> kernel: [<c01ef6d6>] sock_ioctl [kernel] 0x26 (0xd7a1df84))
> kernel: [<c0156919>] sys_ioctl [kernel] 0xc9 (0xd7a1df94))Dec 30 16:16:32 host kernel: [<c010953f>] system_call [kernel] 0x33 (0xd7a1dfc0))
> kernel:
> kernel:
> kernel: Code:  Bad EIP value.
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: IBM Linux Tutorials.
>Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
>Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
>_______________________________________________
>Madwifi-users mailing list
>Mad...@li...
>https://lists.sourceforge.net/lists/listinfo/madwifi-users
>  
>