[ath9k-devel] ath9k and D-Link 652

[ath9k-devel] ath9k and D-Link 652

[Russ Adams]

I have a D-Link 652; which should be an AR5416.  It worked reliably in
2.6.28-7, but has not worked for me since.  In 2.6.32, when I modprobe
ath9k the wlan0 device is not created.

Can someone direct me to or recommend some debugging steps so that I
can provide the list with a better description of the problem?

Thank you,
Russ

[ath9k-devel] ath9k and D-Link 652

[Pavel Roskin]

On Wed, 2009-12-16 at 17:12 -0500, Russ Adams wrote:
> I have a D-Link 652; which should be an AR5416.  It worked reliably in
> 2.6.28-7, but has not worked for me since.  In 2.6.32, when I modprobe
> ath9k the wlan0 device is not created.
> 
> Can someone direct me to or recommend some debugging steps so that I
> can provide the list with a better description of the problem?

Use "lspci -vnn" to make sure that the device is still present on the
PCI bus.  Use dmesg to see error messages from ath9k and other kernel
messages.

Since it's AR5416, you could try MadWifi trunk with it to make sure that
the hardware is functional.

-- 
Regards,
Pavel Roskin

[ath9k-devel] ath9k and D-Link 652

[Russ Adams]

Hardware is functional under 2.6.28-7.  Below is lspci output for
kernel 2.6.28 and 2.6.32.  It appears to be coming up as AR5008
instead of AR5416.

Under 2.6.28-7:
% sudo lspci -vnn
03:00.0 Network controller [0280]: Atheros Communications Inc. AR5008
Wireless Network Adapter [168c:0023] (rev 01)
        Subsystem: D-Link System Inc Device [1186:3a6e]
        Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 11
        Memory at 68000000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [40] #80 [0000]
        Kernel driver in use: ath9k

Under 2.6.32:
% sudo lspci -vnn
03:00.0 Network controller [0280]: Atheros Communications Inc. AR5008
Wireless Network Adapter [168c:0023] (rev 01)
        Subsystem: D-Link System Inc Device [1186:3a6e]
        Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 11
        Memory at 58000000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [40] #80 [0000]
        Kernel driver in use: ath9k
        Kernel modules: ath9k

I will followup with dmesg output for modprobe and rmmod.

On Wed, Dec 16, 2009 at 6:04 PM, Pavel Roskin <proski@gnu.org> wrote:
> On Wed, 2009-12-16 at 17:12 -0500, Russ Adams wrote:
>> I have a D-Link 652; which should be an AR5416. ?It worked reliably in
>> 2.6.28-7, but has not worked for me since. ?In 2.6.32, when I modprobe
>> ath9k the wlan0 device is not created.
>>
>> Can someone direct me to or recommend some debugging steps so that I
>> can provide the list with a better description of the problem?
>
> Use "lspci -vnn" to make sure that the device is still present on the
> PCI bus. ?Use dmesg to see error messages from ath9k and other kernel
> messages.
>
> Since it's AR5416, you could try MadWifi trunk with it to make sure that
> the hardware is functional.
>
> --
> Regards,
> Pavel Roskin
>

[ath9k-devel] ath9k and D-Link 652

[Russ Adams]

Here's a sequence of events:

% sudo modprobe ath9k # no pertinent dmesg output

% iwconfig # wlan0 not present
lo        no wireless extensions.

eth0      no wireless extensions.

% sudo rmmod ath9k # not sure why it's telling me "Killed" here
Killed

% dmesg | less
...
...
BUG: unable to handle kernel NULL pointer dereference at 0000000c
IP: [<c116de6a>] kref_put+0x1a/0x60
*pde = 00000000
Oops: 0002 [#1] PREEMPT SMP
last sysfs file:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/energy_full
Modules linked in: ipv6 fan nls_cp437 hid_microsoft vfat fat
snd_seq_dummy firewire_ohci mmc_block snd_seq_oss firewire_core
snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss sdhci_pci
snd_intel8x0 radeon snd_intel8x0m crc_itu_t ttm snd_ac97_codec sdhci
drm_kms_helper snd_pcm drm i2c_algo_bit snd_timer intel_agp
snd_mixer_oss video snd ac97_bus joydev iTCO_wdt i2c_core
iTCO_vendor_support soundcore shpchp output dell_laptop ac battery
button psmouse snd_page_alloc agpgart pci_hotplug processor thermal
dcdbas serio_raw evdev usbhid pcspkr sg hid rtc_cmos rtc_core rtc_lib
ext3 jbd mbcache ath9k(-) mac80211 ath cfg80211 rfkill led_class b44
ssb mmc_core pcmcia ipw2100 yenta_socket rsrc_nonstatic libipw
uhci_hcd mii lib80211 pcmcia_core sr_mod sd_mod cdrom ehci_hcd usbcore
ata_piix ata_generic pata_acpi libata scsi_mod

Pid: 2089, comm: rmmod Tainted: G        W  (2.6.32-ARCH #1) Inspiron
9200
EIP: 0060:[<c116de6a>] EFLAGS: 00010202 CPU: 0
EIP is at kref_put+0x1a/0x60
EAX: 0000000c EBX: 0000000c ECX: f70ce360 EDX: f8444410
ESI: f8444410 EDI: f732108c EBP: f70ce260 ESP: f559fec4
 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Process rmmod (pid: 2089, ti=f559e000 task=f54edd50 task.ti=f559e000)
Stack:
 f70ce260 f84ef8b0 f843814d f70cea54 f70cea54 f70cea54 f84cc40d f70cea54
<0> f84ef8b0 f732108c f84ef8e4 f84cc4d8 f7321000 c11832f6 f7321058 c11f631d
<0> f7321058 f84ef8b0 c11f6407 f84ef880 f84ef8b0 c13c4c80 c11f55eb f84ef880
Call Trace:
 [<f843814d>] ? ieee80211_unregister_hw+0x5d/0xd0 [mac80211]
 [<f84cc40d>] ? ath_detach+0x5d/0x120 [ath9k]
 [<f84cc4d8>] ? ath_cleanup+0x8/0x30 [ath9k]
 [<c11832f6>] ? pci_device_remove+0x16/0x40
 [<c11f631d>] ? __device_release_driver+0x4d/0xb0
 [<c11f6407>] ? driver_detach+0x87/0x90
 [<c11f55eb>] ? bus_remove_driver+0x5b/0xa0
 [<c118353b>] ? pci_unregister_driver+0x2b/0x80
 [<f84d431c>] ? ath9k_exit+0x8/0x31 [ath9k]
 [<c1070ef0>] ? sys_delete_module+0x190/0x240
 [<c10c6b47>] ? remove_vma+0x37/0x50
 [<c1025a92>] ? do_page_fault+0x102/0x300
 [<c1003913>] ? sysenter_do_call+0x12/0x28
Code: 00 c7 00 01 00 00 00 0f ae f0 89 f6 c3 8d 74 26 00 83 ec 08 85
d2 89 1c 24 89 c3 89 74 24 04 89 d6 74 39 81 fa a0 86 0d c1 74 20 <3e>
ff 0b 0f 94 c2 31 c0 84 d2 74 09 89 d8 ff d6 b8 01 00 00 00
EIP: [<c116de6a>] kref_put+0x1a/0x60 SS:ESP 0068:f559fec4
CR2: 000000000000000c
---[ end trace a7919e7f17c0a727 ]---


On Wed, Dec 16, 2009 at 7:58 PM, Russ Adams <russ.adams@gmail.com> wrote:
> Hardware is functional under 2.6.28-7. ?Below is lspci output for
> kernel 2.6.28 and 2.6.32. ?It appears to be coming up as AR5008
> instead of AR5416.
>
> Under 2.6.28-7:
> % sudo lspci -vnn
> 03:00.0 Network controller [0280]: Atheros Communications Inc. AR5008
> Wireless Network Adapter [168c:0023] (rev 01)
> ? ? ? ?Subsystem: D-Link System Inc Device [1186:3a6e]
> ? ? ? ?Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 11
> ? ? ? ?Memory at 68000000 (32-bit, non-prefetchable) [size=64K]
> ? ? ? ?Capabilities: [40] #80 [0000]
> ? ? ? ?Kernel driver in use: ath9k
>
> Under 2.6.32:
> % sudo lspci -vnn
> 03:00.0 Network controller [0280]: Atheros Communications Inc. AR5008
> Wireless Network Adapter [168c:0023] (rev 01)
> ? ? ? ?Subsystem: D-Link System Inc Device [1186:3a6e]
> ? ? ? ?Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 11
> ? ? ? ?Memory at 58000000 (32-bit, non-prefetchable) [size=64K]
> ? ? ? ?Capabilities: [40] #80 [0000]
> ? ? ? ?Kernel driver in use: ath9k
> ? ? ? ?Kernel modules: ath9k
>
> I will followup with dmesg output for modprobe and rmmod.
>
> On Wed, Dec 16, 2009 at 6:04 PM, Pavel Roskin <proski@gnu.org> wrote:
>> On Wed, 2009-12-16 at 17:12 -0500, Russ Adams wrote:
>>> I have a D-Link 652; which should be an AR5416. ?It worked reliably in
>>> 2.6.28-7, but has not worked for me since. ?In 2.6.32, when I modprobe
>>> ath9k the wlan0 device is not created.
>>>
>>> Can someone direct me to or recommend some debugging steps so that I
>>> can provide the list with a better description of the problem?
>>
>> Use "lspci -vnn" to make sure that the device is still present on the
>> PCI bus. ?Use dmesg to see error messages from ath9k and other kernel
>> messages.
>>
>> Since it's AR5416, you could try MadWifi trunk with it to make sure that
>> the hardware is functional.
>>
>> --
>> Regards,
>> Pavel Roskin
>>
>

[ath9k-devel] ath9k and D-Link 652

[Pavel Roskin]

On Wed, 2009-12-16 at 20:23 -0500, Russ Adams wrote:
> Here's a sequence of events:
> 
> % sudo modprobe ath9k # no pertinent dmesg output
> 
> % iwconfig # wlan0 not present
> lo        no wireless extensions.
> 
> eth0      no wireless extensions.

Is that Linux 2.6.32 without patches?

It would be interesting to see the kernel log at this point.  Perhaps
something fails to be initialized, which causes the crash at the unload
time.

I suggest that you write to linux-wireless at vger.kernel.org, as the crash
is the first priority issue compared to the failed initialization, and
it happens in the mac80211 code.

-- 
Regards,
Pavel Roskin

[ath9k-devel] ath9k and D-Link 652

[Russ Adams]

Thanks Pavel-

I'm using Arch Linux's testing kernel.  They do patch the kernel:
ftp://ftp.archlinux.org/other/kernel26/patch-2.6.32.1-1-ARCH.bz2

I see some cosmetic changes and some changes to ext4.  Nothing
directly pertaining to mac80211 or ath9k.

I will followup with linux-wireless at vger.kernel.org tonight or tomorrow.


On Fri, Dec 18, 2009 at 4:55 PM, Pavel Roskin <proski@gnu.org> wrote:
> On Wed, 2009-12-16 at 20:23 -0500, Russ Adams wrote:
>> Here's a sequence of events:
>>
>> % sudo modprobe ath9k # no pertinent dmesg output
>>
>> % iwconfig # wlan0 not present
>> lo ? ? ? ?no wireless extensions.
>>
>> eth0 ? ? ?no wireless extensions.
>
> Is that Linux 2.6.32 without patches?
>
> It would be interesting to see the kernel log at this point. ?Perhaps
> something fails to be initialized, which causes the crash at the unload
> time.
>
> I suggest that you write to linux-wireless at vger.kernel.org, as the crash
> is the first priority issue compared to the failed initialization, and
> it happens in the mac80211 code.
>
> --
> Regards,
> Pavel Roskin
>