* [linux-next] next-20101201: ath5k permanently disconnecting
@ 2010-12-01 10:09 Sedat Dilek
2010-12-01 10:21 ` Bruno Randolf
` (2 more replies)
0 siblings, 3 replies; 22+ messages in thread
From: Sedat Dilek @ 2010-12-01 10:09 UTC (permalink / raw)
To: wireless; +Cc: John Linville, Nick Kossifidis, Stephen Rothwell
Hi,
I have built today a linux-next (next-20101201) kernel which includes
wireless-next-2.6 up to master-2010-11-30.
>From tig utility:
2010-11-30 15:33 Stanislaw Gruszka [wireless-next-2.6] iwlagn: fix
microcode error on 4965
[main] 61790c5f3c5f158821821a00797d94504531839f - commit 1929 of 226338 (0%)
Unfortunately, my wlan network connection is totally unstable.
$ dmesg | grep "RX AssocResp" | wc -l
216
The block looks like this:
[ 4436.504059] ieee80211 phy0: wlan0: No probe response from AP
00:04:0e:e4:00:3d after 500ms, disconnecting.
[ 4436.504490] cfg80211: Calling CRDA to update world regulatory domain
[ 4440.677020] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
[ 4440.679096] wlan0: authenticated
[ 4440.679158] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
[ 4440.684667] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411
status=0 aid=1)
[ 4440.684673] wlan0: associated
My wlan device is an ath5k:
$ lspci -nnvv | grep "Ethernet controller" | grep -i ath
02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212
802.11abg NIC [168c:1014] (rev 01)
Any idea what's wrong? (Just speculating on the last patch-set from Nick...)
How can I help to dig into this problem?
Debug-session with wpasupplicant? Which kernel-parameters (debug) to
be considered/set?
Kind Regards,
- Sedat -
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-01 10:09 [linux-next] next-20101201: ath5k permanently disconnecting Sedat Dilek
@ 2010-12-01 10:21 ` Bruno Randolf
2010-12-01 10:56 ` Sedat Dilek
` (2 more replies)
2010-12-01 22:05 ` Nick Kossifidis
2010-12-02 12:17 ` Sedat Dilek
2 siblings, 3 replies; 22+ messages in thread
From: Bruno Randolf @ 2010-12-01 10:21 UTC (permalink / raw)
To: sedat.dilek; +Cc: wireless, John Linville, Nick Kossifidis, Stephen Rothwell
On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
> Hi,
>
> I have built today a linux-next (next-20101201) kernel which includes
> wireless-next-2.6 up to master-2010-11-30.
>
> >From tig utility:
> 2010-11-30 15:33 Stanislaw Gruszka [wireless-next-2.6] iwlagn: fix
> microcode error on 4965
> [main] 61790c5f3c5f158821821a00797d94504531839f - commit 1929 of 226338
> (0%)
>
> Unfortunately, my wlan network connection is totally unstable.
>
> $ dmesg | grep "RX AssocResp" | wc -l
> 216
>
> The block looks like this:
> [ 4436.504059] ieee80211 phy0: wlan0: No probe response from AP
> 00:04:0e:e4:00:3d after 500ms, disconnecting.
> [ 4436.504490] cfg80211: Calling CRDA to update world regulatory domain
> [ 4440.677020] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
> [ 4440.679096] wlan0: authenticated
> [ 4440.679158] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
> [ 4440.684667] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411
> status=0 aid=1)
> [ 4440.684673] wlan0: associated
>
> My wlan device is an ath5k:
>
> $ lspci -nnvv | grep "Ethernet controller" | grep -i ath
> 02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212
> 802.11abg NIC [168c:1014] (rev 01)
>
> Any idea what's wrong? (Just speculating on the last patch-set from
> Nick...) How can I help to dig into this problem?
> Debug-session with wpasupplicant? Which kernel-parameters (debug) to
> be considered/set?
1.) For identification of the chipset, please:
dmesg |grep "ath5.*chip"
2.) Is there a problem when you don't use encryption?
3.) git bisect might help track it down.
bruno
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-01 10:21 ` Bruno Randolf
@ 2010-12-01 10:56 ` Sedat Dilek
2010-12-01 11:21 ` Sedat Dilek
2010-12-01 21:04 ` Sedat Dilek
2010-12-02 17:33 ` Sedat Dilek
2 siblings, 1 reply; 22+ messages in thread
From: Sedat Dilek @ 2010-12-01 10:56 UTC (permalink / raw)
To: Bruno Randolf; +Cc: wireless, John Linville, Nick Kossifidis, Stephen Rothwell
[-- Attachment #1: Type: text/plain, Size: 4380 bytes --]
On Wed, Dec 1, 2010 at 11:21 AM, Bruno Randolf <br1@einfach.org> wrote:
> On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
>> Hi,
>>
>> I have built today a linux-next (next-20101201) kernel which includes
>> wireless-next-2.6 up to master-2010-11-30.
>>
>> >From tig utility:
>> 2010-11-30 15:33 Stanislaw Gruszka [wireless-next-2.6] iwlagn: fix
>> microcode error on 4965
>> [main] 61790c5f3c5f158821821a00797d94504531839f - commit 1929 of 226338
>> (0%)
>>
>> Unfortunately, my wlan network connection is totally unstable.
>>
>> $ dmesg | grep "RX AssocResp" | wc -l
>> 216
>>
>> The block looks like this:
>> [ 4436.504059] ieee80211 phy0: wlan0: No probe response from AP
>> 00:04:0e:e4:00:3d after 500ms, disconnecting.
>> [ 4436.504490] cfg80211: Calling CRDA to update world regulatory domain
>> [ 4440.677020] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
>> [ 4440.679096] wlan0: authenticated
>> [ 4440.679158] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
>> [ 4440.684667] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411
>> status=0 aid=1)
>> [ 4440.684673] wlan0: associated
>>
>> My wlan device is an ath5k:
>>
>> $ lspci -nnvv | grep "Ethernet controller" | grep -i ath
>> 02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212
>> 802.11abg NIC [168c:1014] (rev 01)
>>
>> Any idea what's wrong? (Just speculating on the last patch-set from
>> Nick...) How can I help to dig into this problem?
>> Debug-session with wpasupplicant? Which kernel-parameters (debug) to
>> be considered/set?
>
> 1.) For identification of the chipset, please:
> dmesg |grep "ath5.*chip"
>
> 2.) Is there a problem when you don't use encryption?
>
> 3.) git bisect might help track it down.
>
> bruno
>
When does it happen?
Normal daily usage of Internet-ing... + kernel build with -j5
(Pentium-M, 1G RAM)...
I have set now as extra (just rebuilding):
CONFIG_ATH_DEBUG=y
CONFIG_ATH5K_DEBUG=y
# egrep 'Dec 1 09:38' /var/log/syslog | egrep -i 'ath|80211|wlan'
Dec 1 09:38:40 tbox kernel: [ 6.919633] cfg80211: Calling CRDA to
update world regulatory domain
Dec 1 09:38:40 tbox kernel: [ 7.401522] ath5k 0000:02:02.0: PCI
INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
Dec 1 09:38:40 tbox kernel: [ 7.401677] ath5k 0000:02:02.0:
registered as 'phy0'
Dec 1 09:38:40 tbox kernel: [ 7.689793] ath: EEPROM regdomain: 0x61
Dec 1 09:38:40 tbox kernel: [ 7.689797] ath: EEPROM indicates we
should expect a direct regpair map
Dec 1 09:38:40 tbox kernel: [ 7.689803] ath: Country alpha2 being used: 00
Dec 1 09:38:40 tbox kernel: [ 7.689805] ath: Regpair used: 0x61
Dec 1 09:38:40 tbox kernel: [ 8.232093] ieee80211 phy0: Selected
rate control algorithm 'minstrel_ht'
Dec 1 09:38:40 tbox kernel: [ 8.233067] Registered led device:
ath5k-phy0::rx
Dec 1 09:38:40 tbox kernel: [ 8.233106] Registered led device:
ath5k-phy0::tx
Dec 1 09:38:40 tbox kernel: [ 8.233119] ath5k phy0: Atheros AR5212
chip found (MAC: 0x56, PHY: 0x41)
Dec 1 09:38:40 tbox kernel: [ 8.233165] ath5k phy0: RF5111 5GHz
radio found (0x17)
Dec 1 09:38:40 tbox kernel: [ 8.233202] ath5k phy0: RF2111 2GHz
radio found (0x23)
Dec 1 09:38:41 tbox kernel: [ 16.753896] ADDRCONF(NETDEV_UP):
wlan0: link is not ready
Dec 1 09:38:42 tbox wpa_supplicant[972]: Trying to associate with
00:04:0e:e4:00:3d (SSID='myCastle-WLAN WPA (Wireless LAN)' freq=2442
MHz)
Dec 1 09:38:42 tbox kernel: [ 21.967986] wlan0: authenticate with
00:04:0e:e4:00:3d (try 1)
Dec 1 09:38:42 tbox kernel: [ 21.970076] wlan0: authenticated
Dec 1 09:38:42 tbox kernel: [ 21.970094] wlan0: associate with
00:04:0e:e4:00:3d (try 1)
Dec 1 09:38:42 tbox kernel: [ 21.975454] wlan0: RX AssocResp from
00:04:0e:e4:00:3d (capab=0x411 status=0 aid=1)
Dec 1 09:38:42 tbox kernel: [ 21.975458] wlan0: associated
Dec 1 09:38:42 tbox kernel: [ 21.976415] ADDRCONF(NETDEV_CHANGE):
wlan0: link becomes ready
Dec 1 09:38:53 tbox kernel: [ 32.848041] wlan0: no IPv6 routers present
Dec 1 09:38:56 tbox kernel: [ 36.320070] ieee80211 phy0: wlan0: No
probe response from AP 00:04:0e:e4:00:3d after 500ms, disconnecting.
Dec 1 09:38:56 tbox kernel: [ 36.320961] cfg80211: Calling CRDA to
update world regulatory domain
Full syslog attached.
- Sedat -
[-- Attachment #2: syslog.txt --]
[-- Type: text/plain, Size: 87612 bytes --]
Dec 1 09:38:40 tbox kernel: imklog 5.7.2, log source = /proc/kmsg started.
Dec 1 09:38:40 tbox rsyslogd: [origin software="rsyslogd" swVersion="5.7.2" x-pid="1187" x-info="http://www.rsyslog.com"] start
Dec 1 09:38:40 tbox kernel: [ 0.000000] Initializing cgroup subsys cpuset
Dec 1 09:38:40 tbox kernel: [ 0.000000] Initializing cgroup subsys cpu
Dec 1 09:38:40 tbox kernel: [ 0.000000] Linux version 2.6.37-rc4-686 (Debian 2.6.37~rc4-1~next20101201.dileks.1) (sedat.dilek@gmail.com) (gcc version 4.4.5 (Debian 4.4.5-9) ) #1 SMP Wed Dec 1 06:27:52 CET 2010
Dec 1 09:38:40 tbox kernel: [ 0.000000] BIOS-provided physical RAM map:
Dec 1 09:38:40 tbox kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
Dec 1 09:38:40 tbox kernel: [ 0.000000] BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
Dec 1 09:38:40 tbox kernel: [ 0.000000] BIOS-e820: 00000000000d2000 - 00000000000d4000 (reserved)
Dec 1 09:38:40 tbox kernel: [ 0.000000] BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
Dec 1 09:38:40 tbox kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 000000003ff60000 (usable)
Dec 1 09:38:40 tbox kernel: [ 0.000000] BIOS-e820: 000000003ff60000 - 000000003ff77000 (ACPI data)
Dec 1 09:38:40 tbox kernel: [ 0.000000] BIOS-e820: 000000003ff77000 - 000000003ff79000 (ACPI NVS)
Dec 1 09:38:40 tbox kernel: [ 0.000000] BIOS-e820: 000000003ff80000 - 0000000040000000 (reserved)
Dec 1 09:38:40 tbox kernel: [ 0.000000] BIOS-e820: 00000000ff800000 - 0000000100000000 (reserved)
Dec 1 09:38:40 tbox kernel: [ 0.000000] Notice: NX (Execute Disable) protection missing in CPU!
Dec 1 09:38:40 tbox kernel: [ 0.000000] DMI present.
Dec 1 09:38:40 tbox kernel: [ 0.000000] DMI: 2374SG6/2374SG6, BIOS 1RETDRWW (3.23 ) 06/18/2007
Dec 1 09:38:40 tbox kernel: [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
Dec 1 09:38:40 tbox kernel: [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
Dec 1 09:38:40 tbox kernel: [ 0.000000] last_pfn = 0x3ff60 max_arch_pfn = 0x100000
Dec 1 09:38:40 tbox kernel: [ 0.000000] MTRR default type: uncachable
Dec 1 09:38:40 tbox kernel: [ 0.000000] MTRR fixed ranges enabled:
Dec 1 09:38:40 tbox kernel: [ 0.000000] 00000-9FFFF write-back
Dec 1 09:38:40 tbox kernel: [ 0.000000] A0000-BFFFF uncachable
Dec 1 09:38:40 tbox kernel: [ 0.000000] C0000-CFFFF write-protect
Dec 1 09:38:40 tbox kernel: [ 0.000000] D0000-DBFFF uncachable
Dec 1 09:38:40 tbox kernel: [ 0.000000] DC000-DFFFF write-back
Dec 1 09:38:40 tbox kernel: [ 0.000000] E0000-FFFFF write-protect
Dec 1 09:38:40 tbox kernel: [ 0.000000] MTRR variable ranges enabled:
Dec 1 09:38:40 tbox kernel: [ 0.000000] 0 base 000000000 mask FC0000000 write-back
Dec 1 09:38:40 tbox kernel: [ 0.000000] 1 base 03FF80000 mask FFFF80000 uncachable
Dec 1 09:38:40 tbox kernel: [ 0.000000] 2 disabled
Dec 1 09:38:40 tbox kernel: [ 0.000000] 3 disabled
Dec 1 09:38:40 tbox kernel: [ 0.000000] 4 disabled
Dec 1 09:38:40 tbox kernel: [ 0.000000] 5 disabled
Dec 1 09:38:40 tbox kernel: [ 0.000000] 6 disabled
Dec 1 09:38:40 tbox kernel: [ 0.000000] 7 disabled
Dec 1 09:38:40 tbox kernel: [ 0.000000] PAT not supported by CPU.
Dec 1 09:38:40 tbox kernel: [ 0.000000] initial memory mapped : 0 - 01800000
Dec 1 09:38:40 tbox kernel: [ 0.000000] init_memory_mapping: 0000000000000000-00000000377fe000
Dec 1 09:38:40 tbox kernel: [ 0.000000] 0000000000 - 0000400000 page 4k
Dec 1 09:38:40 tbox kernel: [ 0.000000] 0000400000 - 0037400000 page 2M
Dec 1 09:38:40 tbox kernel: [ 0.000000] 0037400000 - 00377fe000 page 4k
Dec 1 09:38:40 tbox kernel: [ 0.000000] kernel direct mapping tables up to 377fe000 @ 17fb000-1800000
Dec 1 09:38:40 tbox kernel: [ 0.000000] RAMDISK: 2f65a000 - 2ffc8000
Dec 1 09:38:40 tbox kernel: [ 0.000000] ACPI: RSDP 000f6d70 00024 (v02 IBM )
Dec 1 09:38:40 tbox kernel: [ 0.000000] ACPI: XSDT 3ff6a672 0004C (v01 IBM TP-1R 00003230 LTP 00000000)
Dec 1 09:38:40 tbox kernel: [ 0.000000] ACPI: FACP 3ff6a700 000F4 (v03 IBM TP-1R 00003230 IBM 00000001)
Dec 1 09:38:40 tbox kernel: [ 0.000000] ACPI Warning: 32/64X length mismatch in Gpe1Block: 0/32 (20101013/tbfadt-526)
Dec 1 09:38:40 tbox kernel: [ 0.000000] ACPI Warning: Optional field Gpe1Block has zero address or length: 0x000000000000102C/0x0 (20101013/tbfadt-557)
Dec 1 09:38:40 tbox kernel: [ 0.000000] ACPI: DSDT 3ff6a8e7 0C530 (v01 IBM TP-1R 00003230 MSFT 0100000E)
Dec 1 09:38:40 tbox kernel: [ 0.000000] ACPI: FACS 3ff78000 00040
Dec 1 09:38:40 tbox kernel: [ 0.000000] ACPI: SSDT 3ff6a8b4 00033 (v01 IBM TP-1R 00003230 MSFT 0100000E)
Dec 1 09:38:40 tbox kernel: [ 0.000000] ACPI: ECDT 3ff76e17 00052 (v01 IBM TP-1R 00003230 IBM 00000001)
Dec 1 09:38:40 tbox kernel: [ 0.000000] ACPI: TCPA 3ff76e69 00032 (v01 IBM TP-1R 00003230 PTL 00000001)
Dec 1 09:38:40 tbox kernel: [ 0.000000] ACPI: BOOT 3ff76fd8 00028 (v01 IBM TP-1R 00003230 LTP 00000001)
Dec 1 09:38:40 tbox kernel: [ 0.000000] 135MB HIGHMEM available.
Dec 1 09:38:40 tbox kernel: [ 0.000000] 887MB LOWMEM available.
Dec 1 09:38:40 tbox kernel: [ 0.000000] mapped low ram: 0 - 377fe000
Dec 1 09:38:40 tbox kernel: [ 0.000000] low ram: 0 - 377fe000
Dec 1 09:38:40 tbox kernel: [ 0.000000] Zone PFN ranges:
Dec 1 09:38:40 tbox kernel: [ 0.000000] DMA 0x00000010 -> 0x00001000
Dec 1 09:38:40 tbox kernel: [ 0.000000] Normal 0x00001000 -> 0x000377fe
Dec 1 09:38:40 tbox kernel: [ 0.000000] HighMem 0x000377fe -> 0x0003ff60
Dec 1 09:38:40 tbox kernel: [ 0.000000] Movable zone start PFN for each node
Dec 1 09:38:40 tbox kernel: [ 0.000000] early_node_map[2] active PFN ranges
Dec 1 09:38:40 tbox kernel: [ 0.000000] 0: 0x00000010 -> 0x0000009f
Dec 1 09:38:40 tbox kernel: [ 0.000000] 0: 0x00000100 -> 0x0003ff60
Dec 1 09:38:40 tbox kernel: [ 0.000000] On node 0 totalpages: 261871
Dec 1 09:38:40 tbox kernel: [ 0.000000] free_area_init_node: node 0, pgdat c13e7640, node_mem_map f6ffd200
Dec 1 09:38:40 tbox kernel: [ 0.000000] DMA zone: 32 pages used for memmap
Dec 1 09:38:40 tbox kernel: [ 0.000000] DMA zone: 0 pages reserved
Dec 1 09:38:40 tbox kernel: [ 0.000000] DMA zone: 3951 pages, LIFO batch:0
Dec 1 09:38:40 tbox kernel: [ 0.000000] Normal zone: 1744 pages used for memmap
Dec 1 09:38:40 tbox kernel: [ 0.000000] Normal zone: 221486 pages, LIFO batch:31
Dec 1 09:38:40 tbox kernel: [ 0.000000] HighMem zone: 271 pages used for memmap
Dec 1 09:38:40 tbox kernel: [ 0.000000] HighMem zone: 34387 pages, LIFO batch:7
Dec 1 09:38:40 tbox kernel: [ 0.000000] Using APIC driver default
Dec 1 09:38:40 tbox kernel: [ 0.000000] ACPI: PM-Timer IO Port: 0x1008
Dec 1 09:38:40 tbox kernel: [ 0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
Dec 1 09:38:40 tbox kernel: [ 0.000000] Local APIC disabled by BIOS -- reenabling.
Dec 1 09:38:40 tbox kernel: [ 0.000000] Found and enabled local APIC!
Dec 1 09:38:40 tbox kernel: [ 0.000000] nr_irqs_gsi: 16
Dec 1 09:38:40 tbox kernel: [ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
Dec 1 09:38:40 tbox kernel: [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000d2000
Dec 1 09:38:40 tbox kernel: [ 0.000000] PM: Registered nosave memory: 00000000000d2000 - 00000000000d4000
Dec 1 09:38:40 tbox kernel: [ 0.000000] PM: Registered nosave memory: 00000000000d4000 - 00000000000dc000
Dec 1 09:38:40 tbox kernel: [ 0.000000] PM: Registered nosave memory: 00000000000dc000 - 0000000000100000
Dec 1 09:38:40 tbox kernel: [ 0.000000] Allocating PCI resources starting at 40000000 (gap: 40000000:bf800000)
Dec 1 09:38:40 tbox kernel: [ 0.000000] Booting paravirtualized kernel on bare hardware
Dec 1 09:38:40 tbox kernel: [ 0.000000] setup_percpu: NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:1 nr_node_ids:1
Dec 1 09:38:40 tbox kernel: [ 0.000000] PERCPU: Embedded 12 pages/cpu @f6800000 s27136 r0 d22016 u4194304
Dec 1 09:38:40 tbox kernel: [ 0.000000] pcpu-alloc: s27136 r0 d22016 u4194304 alloc=1*4194304
Dec 1 09:38:40 tbox kernel: [ 0.000000] pcpu-alloc: [0] 0
Dec 1 09:38:40 tbox kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 259824
Dec 1 09:38:40 tbox kernel: [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.37-rc4-686 root=UUID=1ceb69a7-ecf4-47e9-a231-b74e0f0a9b62 ro radeon.modeset=1 lapic 3 init=/sbin/init.sysvinit
Dec 1 09:38:40 tbox kernel: [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
Dec 1 09:38:40 tbox kernel: [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Dec 1 09:38:40 tbox kernel: [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Dec 1 09:38:40 tbox kernel: [ 0.000000] Initializing CPU#0
Dec 1 09:38:40 tbox kernel: [ 0.000000] Initializing HighMem for node 0 (000377fe:0003ff60)
Dec 1 09:38:40 tbox kernel: [ 0.000000] Memory: 1023572k/1047936k available (2667k kernel code, 23912k reserved, 1367k data, 392k init, 138632k highmem)
Dec 1 09:38:40 tbox kernel: [ 0.000000] virtual kernel memory layout:
Dec 1 09:38:40 tbox kernel: [ 0.000000] fixmap : 0xffd36000 - 0xfffff000 (2852 kB)
Dec 1 09:38:40 tbox kernel: [ 0.000000] pkmap : 0xff800000 - 0xffc00000 (4096 kB)
Dec 1 09:38:40 tbox kernel: [ 0.000000] vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
Dec 1 09:38:40 tbox kernel: [ 0.000000] lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
Dec 1 09:38:40 tbox kernel: [ 0.000000] .init : 0xc13f1000 - 0xc1453000 ( 392 kB)
Dec 1 09:38:40 tbox kernel: [ 0.000000] .data : 0xc129aef4 - 0xc13f0c60 (1367 kB)
Dec 1 09:38:40 tbox kernel: [ 0.000000] .text : 0xc1000000 - 0xc129aef4 (2667 kB)
Dec 1 09:38:40 tbox kernel: [ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
Dec 1 09:38:40 tbox kernel: [ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Dec 1 09:38:40 tbox kernel: [ 0.000000] Hierarchical RCU implementation.
Dec 1 09:38:40 tbox kernel: [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
Dec 1 09:38:40 tbox kernel: [ 0.000000] RCU-based detection of stalled CPUs is disabled.
Dec 1 09:38:40 tbox kernel: [ 0.000000] NR_IRQS:1280
Dec 1 09:38:40 tbox kernel: [ 0.000000] CPU 0 irqstacks, hard=f6408000 soft=f640a000
Dec 1 09:38:40 tbox kernel: [ 0.000000] Extended CMOS year: 2000
Dec 1 09:38:40 tbox kernel: [ 0.000000] Console: colour VGA+ 80x25
Dec 1 09:38:40 tbox kernel: [ 0.000000] console [tty0] enabled
Dec 1 09:38:40 tbox kernel: [ 0.000000] Fast TSC calibration using PIT
Dec 1 09:38:40 tbox kernel: [ 0.000000] Detected 1694.296 MHz processor.
Dec 1 09:38:40 tbox kernel: [ 0.008008] Calibrating delay loop (skipped), value calculated using timer frequency.. 3388.59 BogoMIPS (lpj=6777184)
Dec 1 09:38:40 tbox kernel: [ 0.008082] pid_max: default: 32768 minimum: 301
Dec 1 09:38:40 tbox kernel: [ 0.008148] Security Framework initialized
Dec 1 09:38:40 tbox kernel: [ 0.008190] SELinux: Disabled at boot.
Dec 1 09:38:40 tbox kernel: [ 0.008244] Mount-cache hash table entries: 512
Dec 1 09:38:40 tbox kernel: [ 0.008504] Initializing cgroup subsys ns
Dec 1 09:38:40 tbox kernel: [ 0.008544] ns_cgroup deprecated: consider using the 'clone_children' flag without the ns_cgroup.
Dec 1 09:38:40 tbox kernel: [ 0.008593] Initializing cgroup subsys cpuacct
Dec 1 09:38:40 tbox kernel: [ 0.008632] Initializing cgroup subsys devices
Dec 1 09:38:40 tbox kernel: [ 0.008668] Initializing cgroup subsys freezer
Dec 1 09:38:40 tbox kernel: [ 0.008703] Initializing cgroup subsys net_cls
Dec 1 09:38:40 tbox kernel: [ 0.008739] Initializing cgroup subsys blkio
Dec 1 09:38:40 tbox kernel: [ 0.008831] mce: CPU supports 5 MCE banks
Dec 1 09:38:40 tbox kernel: [ 0.008878] CPU0: Thermal monitoring enabled (TM2)
Dec 1 09:38:40 tbox kernel: [ 0.008927] Performance Events: p6 PMU driver.
Dec 1 09:38:40 tbox kernel: [ 0.008989] ... version: 0
Dec 1 09:38:40 tbox kernel: [ 0.009023] ... bit width: 32
Dec 1 09:38:40 tbox kernel: [ 0.009057] ... generic registers: 2
Dec 1 09:38:40 tbox kernel: [ 0.009092] ... value mask: 00000000ffffffff
Dec 1 09:38:40 tbox kernel: [ 0.009127] ... max period: 000000007fffffff
Dec 1 09:38:40 tbox kernel: [ 0.009163] ... fixed-purpose events: 0
Dec 1 09:38:40 tbox kernel: [ 0.009198] ... event mask: 0000000000000003
Dec 1 09:38:40 tbox kernel: [ 0.009757] SMP alternatives: switching to UP code
Dec 1 09:38:40 tbox kernel: [ 0.014716] Freeing SMP alternatives: 16k freed
Dec 1 09:38:40 tbox kernel: [ 0.014756] ACPI: Core revision 20101013
Dec 1 09:38:40 tbox kernel: [ 0.031605] ACPI: setting ELCR to 0200 (from 0800)
Dec 1 09:38:40 tbox kernel: [ 0.032087] weird, boot CPU (#0) not listed by the BIOS.
Dec 1 09:38:40 tbox kernel: [ 0.032124] SMP motherboard not detected.
Dec 1 09:38:40 tbox kernel: [ 0.032162] Enabling APIC mode: Flat. Using 0 I/O APICs
Dec 1 09:38:40 tbox kernel: [ 0.036002] SMP disabled
Dec 1 09:38:40 tbox kernel: [ 0.036002] NMI watchdog enabled, takes one hw-pmu counter.
Dec 1 09:38:40 tbox kernel: [ 0.036002] Brought up 1 CPUs
Dec 1 09:38:40 tbox kernel: [ 0.036002] Total of 1 processors activated (3388.59 BogoMIPS).
Dec 1 09:38:40 tbox kernel: [ 0.036002] devtmpfs: initialized
Dec 1 09:38:40 tbox kernel: [ 0.036002] print_constraints: dummy: regulator:
Dec 1 09:38:40 tbox kernel: [ 0.036002] NET: Registered protocol family 16
Dec 1 09:38:40 tbox kernel: [ 0.036002] ACPI: bus type pci registered
Dec 1 09:38:40 tbox kernel: [ 0.036002] PCI: PCI BIOS revision 2.10 entry at 0xfd8d6, last bus=8
Dec 1 09:38:40 tbox kernel: [ 0.036002] PCI: Using configuration type 1 for base access
Dec 1 09:38:40 tbox kernel: [ 0.036002] bio: create slab <bio-0> at 0
Dec 1 09:38:40 tbox kernel: [ 0.037322] ACPI: EC: EC description table is found, configuring boot EC
Dec 1 09:38:40 tbox kernel: [ 0.052648] ACPI: Interpreter enabled
Dec 1 09:38:40 tbox kernel: [ 0.052685] ACPI: (supports S0 S3 S4 S5)
Dec 1 09:38:40 tbox kernel: [ 0.052823] ACPI: Using PIC for interrupt routing
Dec 1 09:38:40 tbox kernel: [ 0.056602] ACPI: Power Resource [PUBS] (on)
Dec 1 09:38:40 tbox kernel: [ 0.060549] ACPI: EC: GPE = 0x1c, I/O: command/status = 0x66, data = 0x62
Dec 1 09:38:40 tbox kernel: [ 0.061137] ACPI: ACPI Dock Station Driver: 3 docks/bays found
Dec 1 09:38:40 tbox kernel: [ 0.061137] PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug
Dec 1 09:38:40 tbox kernel: [ 0.061137] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
Dec 1 09:38:40 tbox kernel: [ 0.061137] pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
Dec 1 09:38:40 tbox kernel: [ 0.061137] pci_root PNP0A03:00: host bridge window [io 0x0d00-0xffff] (ignored)
Dec 1 09:38:40 tbox kernel: [ 0.061137] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
Dec 1 09:38:40 tbox kernel: [ 0.061137] pci_root PNP0A03:00: host bridge window [mem 0x000d4000-0x000d7fff] (ignored)
Dec 1 09:38:40 tbox kernel: [ 0.061137] pci_root PNP0A03:00: host bridge window [mem 0x000d8000-0x000dbfff] (ignored)
Dec 1 09:38:40 tbox kernel: [ 0.061137] pci_root PNP0A03:00: host bridge window [mem 0x40000000-0xfebfffff] (ignored)
Dec 1 09:38:40 tbox kernel: [ 0.061137] pci 0000:00:00.0: [8086:3340] type 0 class 0x000600
Dec 1 09:38:40 tbox kernel: [ 0.061137] pci 0000:00:00.0: reg 10: [mem 0xd0000000-0xdfffffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.061137] pci 0000:00:01.0: [8086:3341] type 1 class 0x000604
Dec 1 09:38:40 tbox kernel: [ 0.061174] pci 0000:00:1d.0: [8086:24c2] type 0 class 0x000c03
Dec 1 09:38:40 tbox kernel: [ 0.061219] pci 0000:00:1d.0: reg 20: [io 0x1800-0x181f]
Dec 1 09:38:40 tbox kernel: [ 0.061253] pci 0000:00:1d.1: [8086:24c4] type 0 class 0x000c03
Dec 1 09:38:40 tbox kernel: [ 0.061298] pci 0000:00:1d.1: reg 20: [io 0x1820-0x183f]
Dec 1 09:38:40 tbox kernel: [ 0.061333] pci 0000:00:1d.2: [8086:24c7] type 0 class 0x000c03
Dec 1 09:38:40 tbox kernel: [ 0.061377] pci 0000:00:1d.2: reg 20: [io 0x1840-0x185f]
Dec 1 09:38:40 tbox kernel: [ 0.061423] pci 0000:00:1d.7: [8086:24cd] type 0 class 0x000c03
Dec 1 09:38:40 tbox kernel: [ 0.061445] pci 0000:00:1d.7: reg 10: [mem 0xc0000000-0xc00003ff]
Dec 1 09:38:40 tbox kernel: [ 0.061525] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
Dec 1 09:38:40 tbox kernel: [ 0.061531] pci 0000:00:1d.7: PME# disabled
Dec 1 09:38:40 tbox kernel: [ 0.061551] pci 0000:00:1e.0: [8086:2448] type 1 class 0x000604
Dec 1 09:38:40 tbox kernel: [ 0.061595] pci 0000:00:1f.0: [8086:24cc] type 0 class 0x000601
Dec 1 09:38:40 tbox kernel: [ 0.061661] pci 0000:00:1f.0: quirk: [io 0x1000-0x107f] claimed by ICH4 ACPI/GPIO/TCO
Dec 1 09:38:40 tbox kernel: [ 0.061711] pci 0000:00:1f.0: quirk: [io 0x1180-0x11bf] claimed by ICH4 GPIO
Dec 1 09:38:40 tbox kernel: [ 0.061763] pci 0000:00:1f.1: [8086:24ca] type 0 class 0x000101
Dec 1 09:38:40 tbox kernel: [ 0.061778] pci 0000:00:1f.1: reg 10: [io 0x0000-0x0007]
Dec 1 09:38:40 tbox kernel: [ 0.061788] pci 0000:00:1f.1: reg 14: [io 0x0000-0x0003]
Dec 1 09:38:40 tbox kernel: [ 0.061799] pci 0000:00:1f.1: reg 18: [io 0x0000-0x0007]
Dec 1 09:38:40 tbox kernel: [ 0.061810] pci 0000:00:1f.1: reg 1c: [io 0x0000-0x0003]
Dec 1 09:38:40 tbox kernel: [ 0.061821] pci 0000:00:1f.1: reg 20: [io 0x1860-0x186f]
Dec 1 09:38:40 tbox kernel: [ 0.061832] pci 0000:00:1f.1: reg 24: [mem 0x00000000-0x000003ff]
Dec 1 09:38:40 tbox kernel: [ 0.061862] pci 0000:00:1f.3: [8086:24c3] type 0 class 0x000c05
Dec 1 09:38:40 tbox kernel: [ 0.061906] pci 0000:00:1f.3: reg 20: [io 0x1880-0x189f]
Dec 1 09:38:40 tbox kernel: [ 0.064040] pci 0000:00:1f.5: [8086:24c5] type 0 class 0x000401
Dec 1 09:38:40 tbox kernel: [ 0.064056] pci 0000:00:1f.5: reg 10: [io 0x1c00-0x1cff]
Dec 1 09:38:40 tbox kernel: [ 0.064066] pci 0000:00:1f.5: reg 14: [io 0x18c0-0x18ff]
Dec 1 09:38:40 tbox kernel: [ 0.064077] pci 0000:00:1f.5: reg 18: [mem 0xc0000c00-0xc0000dff]
Dec 1 09:38:40 tbox kernel: [ 0.064087] pci 0000:00:1f.5: reg 1c: [mem 0xc0000800-0xc00008ff]
Dec 1 09:38:40 tbox kernel: [ 0.064126] pci 0000:00:1f.5: PME# supported from D0 D3hot D3cold
Dec 1 09:38:40 tbox kernel: [ 0.064131] pci 0000:00:1f.5: PME# disabled
Dec 1 09:38:40 tbox kernel: [ 0.064148] pci 0000:00:1f.6: [8086:24c6] type 0 class 0x000703
Dec 1 09:38:40 tbox kernel: [ 0.064164] pci 0000:00:1f.6: reg 10: [io 0x2400-0x24ff]
Dec 1 09:38:40 tbox kernel: [ 0.064174] pci 0000:00:1f.6: reg 14: [io 0x2000-0x207f]
Dec 1 09:38:40 tbox kernel: [ 0.064226] pci 0000:00:1f.6: PME# supported from D0 D3hot D3cold
Dec 1 09:38:40 tbox kernel: [ 0.064231] pci 0000:00:1f.6: PME# disabled
Dec 1 09:38:40 tbox kernel: [ 0.064258] pci 0000:01:00.0: [1002:4c66] type 0 class 0x000300
Dec 1 09:38:40 tbox kernel: [ 0.064273] pci 0000:01:00.0: reg 10: [mem 0xe0000000-0xe7ffffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.064282] pci 0000:01:00.0: reg 14: [io 0x3000-0x30ff]
Dec 1 09:38:40 tbox kernel: [ 0.064291] pci 0000:01:00.0: reg 18: [mem 0xc0100000-0xc010ffff]
Dec 1 09:38:40 tbox kernel: [ 0.064315] pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.064335] pci 0000:01:00.0: supports D1 D2
Dec 1 09:38:40 tbox kernel: [ 0.064368] pci 0000:00:01.0: PCI bridge to [bus 01-01]
Dec 1 09:38:40 tbox kernel: [ 0.064406] pci 0000:00:01.0: bridge window [io 0x3000-0x3fff]
Dec 1 09:38:40 tbox kernel: [ 0.064411] pci 0000:00:01.0: bridge window [mem 0xc0100000-0xc01fffff]
Dec 1 09:38:40 tbox kernel: [ 0.064416] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe7ffffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.064441] pci 0000:02:00.0: [104c:ac55] type 2 class 0x000607
Dec 1 09:38:40 tbox kernel: [ 0.064459] pci 0000:02:00.0: reg 10: [mem 0xb0000000-0xb0000fff]
Dec 1 09:38:40 tbox kernel: [ 0.064479] pci 0000:02:00.0: supports D1 D2
Dec 1 09:38:40 tbox kernel: [ 0.064482] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Dec 1 09:38:40 tbox kernel: [ 0.064487] pci 0000:02:00.0: PME# disabled
Dec 1 09:38:40 tbox kernel: [ 0.064507] pci 0000:02:00.1: [104c:ac55] type 2 class 0x000607
Dec 1 09:38:40 tbox kernel: [ 0.064525] pci 0000:02:00.1: reg 10: [mem 0xb1000000-0xb1000fff]
Dec 1 09:38:40 tbox kernel: [ 0.064544] pci 0000:02:00.1: supports D1 D2
Dec 1 09:38:40 tbox kernel: [ 0.064547] pci 0000:02:00.1: PME# supported from D0 D1 D2 D3hot D3cold
Dec 1 09:38:40 tbox kernel: [ 0.064553] pci 0000:02:00.1: PME# disabled
Dec 1 09:38:40 tbox kernel: [ 0.064580] pci 0000:02:01.0: [8086:101e] type 0 class 0x000200
Dec 1 09:38:40 tbox kernel: [ 0.064599] pci 0000:02:01.0: reg 10: [mem 0xc0220000-0xc023ffff]
Dec 1 09:38:40 tbox kernel: [ 0.064610] pci 0000:02:01.0: reg 14: [mem 0xc0200000-0xc020ffff]
Dec 1 09:38:40 tbox kernel: [ 0.064621] pci 0000:02:01.0: reg 18: [io 0x8000-0x803f]
Dec 1 09:38:40 tbox kernel: [ 0.064653] pci 0000:02:01.0: reg 30: [mem 0x00000000-0x0000ffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.064677] pci 0000:02:01.0: PME# supported from D0 D3hot D3cold
Dec 1 09:38:40 tbox kernel: [ 0.064683] pci 0000:02:01.0: PME# disabled
Dec 1 09:38:40 tbox kernel: [ 0.064703] pci 0000:02:02.0: [168c:1014] type 0 class 0x000200
Dec 1 09:38:40 tbox kernel: [ 0.064720] pci 0000:02:02.0: reg 10: [mem 0xc0210000-0xc021ffff]
Dec 1 09:38:40 tbox kernel: [ 0.064818] pci 0000:00:1e.0: PCI bridge to [bus 02-08] (subtractive decode)
Dec 1 09:38:40 tbox kernel: [ 0.064859] pci 0000:00:1e.0: bridge window [io 0x4000-0x8fff]
Dec 1 09:38:40 tbox kernel: [ 0.064865] pci 0000:00:1e.0: bridge window [mem 0xc0200000-0xcfffffff]
Dec 1 09:38:40 tbox kernel: [ 0.064871] pci 0000:00:1e.0: bridge window [mem 0xe8000000-0xefffffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.064875] pci 0000:00:1e.0: bridge window [io 0x0000-0xffff] (subtractive decode)
Dec 1 09:38:40 tbox kernel: [ 0.064879] pci 0000:00:1e.0: bridge window [mem 0x00000000-0xffffffff] (subtractive decode)
Dec 1 09:38:40 tbox kernel: [ 0.064955] pci_bus 0000:00: on NUMA node 0
Dec 1 09:38:40 tbox kernel: [ 0.064960] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Dec 1 09:38:40 tbox kernel: [ 0.065011] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
Dec 1 09:38:40 tbox kernel: [ 0.065037] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
Dec 1 09:38:40 tbox kernel: [ 0.068540] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11)
Dec 1 09:38:40 tbox kernel: [ 0.068909] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11)
Dec 1 09:38:40 tbox kernel: [ 0.069275] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11)
Dec 1 09:38:40 tbox kernel: [ 0.069642] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11)
Dec 1 09:38:40 tbox kernel: [ 0.069986] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11) *0, disabled.
Dec 1 09:38:40 tbox kernel: [ 0.070380] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11) *0, disabled.
Dec 1 09:38:40 tbox kernel: [ 0.070773] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 11) *0, disabled.
Dec 1 09:38:40 tbox kernel: [ 0.071195] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 *11)
Dec 1 09:38:40 tbox kernel: [ 0.071484] HEST: Table is not found!
Dec 1 09:38:40 tbox kernel: [ 0.071602] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
Dec 1 09:38:40 tbox kernel: [ 0.071651] vgaarb: loaded
Dec 1 09:38:40 tbox kernel: [ 0.071730] PCI: Using ACPI for IRQ routing
Dec 1 09:38:40 tbox kernel: [ 0.071896] PCI: pci_cache_line_size set to 64 bytes
Dec 1 09:38:40 tbox kernel: [ 0.071962] reserve RAM buffer: 000000000009f000 - 000000000009ffff
Dec 1 09:38:40 tbox kernel: [ 0.071965] reserve RAM buffer: 000000003ff60000 - 000000003fffffff
Dec 1 09:38:40 tbox kernel: [ 0.072145] Switching to clocksource tsc
Dec 1 09:38:40 tbox kernel: [ 0.073774] pnp: PnP ACPI init
Dec 1 09:38:40 tbox kernel: [ 0.073834] ACPI: bus type pnp registered
Dec 1 09:38:40 tbox kernel: [ 0.074679] pnp 00:00: [mem 0x00000000-0x0009ffff]
Dec 1 09:38:40 tbox kernel: [ 0.074683] pnp 00:00: [mem 0x000c0000-0x000c3fff]
Dec 1 09:38:40 tbox kernel: [ 0.074686] pnp 00:00: [mem 0x000c4000-0x000c7fff]
Dec 1 09:38:40 tbox kernel: [ 0.074689] pnp 00:00: [mem 0x000c8000-0x000cbfff]
Dec 1 09:38:40 tbox kernel: [ 0.074692] pnp 00:00: [mem 0x000cc000-0x000cffff]
Dec 1 09:38:40 tbox kernel: [ 0.074696] pnp 00:00: [mem 0x000d0000-0x000d3fff]
Dec 1 09:38:40 tbox kernel: [ 0.074699] pnp 00:00: [mem 0x000d4000-0x000d3fff disabled]
Dec 1 09:38:40 tbox kernel: [ 0.074703] pnp 00:00: [mem 0x000d8000-0x000d7fff disabled]
Dec 1 09:38:40 tbox kernel: [ 0.074706] pnp 00:00: [mem 0x000dc000-0x000dffff]
Dec 1 09:38:40 tbox kernel: [ 0.074709] pnp 00:00: [mem 0x000e0000-0x000e3fff]
Dec 1 09:38:40 tbox kernel: [ 0.074712] pnp 00:00: [mem 0x000e4000-0x000e7fff]
Dec 1 09:38:40 tbox kernel: [ 0.074715] pnp 00:00: [mem 0x000e8000-0x000ebfff]
Dec 1 09:38:40 tbox kernel: [ 0.074718] pnp 00:00: [mem 0x000ec000-0x000effff]
Dec 1 09:38:40 tbox kernel: [ 0.074722] pnp 00:00: [mem 0x000f0000-0x000fffff]
Dec 1 09:38:40 tbox kernel: [ 0.074725] pnp 00:00: [mem 0x00100000-0x3fffffff]
Dec 1 09:38:40 tbox kernel: [ 0.074728] pnp 00:00: [mem 0xfec00000-0xffffffff]
Dec 1 09:38:40 tbox kernel: [ 0.074817] system 00:00: [mem 0x00000000-0x0009ffff] could not be reserved
Dec 1 09:38:40 tbox kernel: [ 0.074857] system 00:00: [mem 0x000c0000-0x000c3fff] could not be reserved
Dec 1 09:38:40 tbox kernel: [ 0.074896] system 00:00: [mem 0x000c4000-0x000c7fff] could not be reserved
Dec 1 09:38:40 tbox kernel: [ 0.074935] system 00:00: [mem 0x000c8000-0x000cbfff] could not be reserved
Dec 1 09:38:40 tbox kernel: [ 0.074974] system 00:00: [mem 0x000cc000-0x000cffff] could not be reserved
Dec 1 09:38:40 tbox kernel: [ 0.075013] system 00:00: [mem 0x000d0000-0x000d3fff] could not be reserved
Dec 1 09:38:40 tbox kernel: [ 0.075052] system 00:00: [mem 0x000dc000-0x000dffff] could not be reserved
Dec 1 09:38:40 tbox kernel: [ 0.075091] system 00:00: [mem 0x000e0000-0x000e3fff] could not be reserved
Dec 1 09:38:40 tbox kernel: [ 0.075130] system 00:00: [mem 0x000e4000-0x000e7fff] could not be reserved
Dec 1 09:38:40 tbox kernel: [ 0.075169] system 00:00: [mem 0x000e8000-0x000ebfff] could not be reserved
Dec 1 09:38:40 tbox kernel: [ 0.075208] system 00:00: [mem 0x000ec000-0x000effff] could not be reserved
Dec 1 09:38:40 tbox kernel: [ 0.075247] system 00:00: [mem 0x000f0000-0x000fffff] could not be reserved
Dec 1 09:38:40 tbox kernel: [ 0.075286] system 00:00: [mem 0x00100000-0x3fffffff] could not be reserved
Dec 1 09:38:40 tbox kernel: [ 0.075325] system 00:00: [mem 0xfec00000-0xffffffff] could not be reserved
Dec 1 09:38:40 tbox kernel: [ 0.075366] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Dec 1 09:38:40 tbox kernel: [ 0.075395] pnp 00:01: [bus 00-ff]
Dec 1 09:38:40 tbox kernel: [ 0.075399] pnp 00:01: [io 0x0cf8-0x0cff]
Dec 1 09:38:40 tbox kernel: [ 0.075402] pnp 00:01: [io 0x0000-0x0cf7 window]
Dec 1 09:38:40 tbox kernel: [ 0.075406] pnp 00:01: [io 0x0d00-0xffff window]
Dec 1 09:38:40 tbox kernel: [ 0.075415] pnp 00:01: [mem 0x000a0000-0x000bffff window]
Dec 1 09:38:40 tbox kernel: [ 0.075418] pnp 00:01: [mem 0x000c0000-0x000c3fff window]
Dec 1 09:38:40 tbox kernel: [ 0.075422] pnp 00:01: [mem 0x000c4000-0x000c7fff window]
Dec 1 09:38:40 tbox kernel: [ 0.075425] pnp 00:01: [mem 0x000c8000-0x000cbfff window]
Dec 1 09:38:40 tbox kernel: [ 0.075429] pnp 00:01: [mem 0x000cc000-0x000cffff window]
Dec 1 09:38:40 tbox kernel: [ 0.075432] pnp 00:01: [mem 0x000d0000-0x000d3fff window]
Dec 1 09:38:40 tbox kernel: [ 0.075435] pnp 00:01: [mem 0x000d4000-0x000d7fff window]
Dec 1 09:38:40 tbox kernel: [ 0.075439] pnp 00:01: [mem 0x000d8000-0x000dbfff window]
Dec 1 09:38:40 tbox kernel: [ 0.075442] pnp 00:01: [mem 0x000dc000-0x000dffff window]
Dec 1 09:38:40 tbox kernel: [ 0.075446] pnp 00:01: [mem 0x000e0000-0x000e3fff window]
Dec 1 09:38:40 tbox kernel: [ 0.075449] pnp 00:01: [mem 0x000e4000-0x000e7fff window]
Dec 1 09:38:40 tbox kernel: [ 0.075452] pnp 00:01: [mem 0x000e8000-0x000ebfff window]
Dec 1 09:38:40 tbox kernel: [ 0.075456] pnp 00:01: [mem 0x000ec000-0x000effff window]
Dec 1 09:38:40 tbox kernel: [ 0.075459] pnp 00:01: [mem 0x40000000-0xfebfffff window]
Dec 1 09:38:40 tbox kernel: [ 0.075529] pnp 00:01: Plug and Play ACPI device, IDs PNP0a03 (active)
Dec 1 09:38:40 tbox kernel: [ 0.075677] pnp 00:02: [io 0x0010-0x001f]
Dec 1 09:38:40 tbox kernel: [ 0.075681] pnp 00:02: [io 0x0090-0x009f]
Dec 1 09:38:40 tbox kernel: [ 0.075684] pnp 00:02: [io 0x0024-0x0025]
Dec 1 09:38:40 tbox kernel: [ 0.075687] pnp 00:02: [io 0x0028-0x0029]
Dec 1 09:38:40 tbox kernel: [ 0.075690] pnp 00:02: [io 0x002c-0x002d]
Dec 1 09:38:40 tbox kernel: [ 0.075693] pnp 00:02: [io 0x0030-0x0031]
Dec 1 09:38:40 tbox kernel: [ 0.075696] pnp 00:02: [io 0x0034-0x0035]
Dec 1 09:38:40 tbox kernel: [ 0.075699] pnp 00:02: [io 0x0038-0x0039]
Dec 1 09:38:40 tbox kernel: [ 0.075702] pnp 00:02: [io 0x003c-0x003d]
Dec 1 09:38:40 tbox kernel: [ 0.075705] pnp 00:02: [io 0x00a4-0x00a5]
Dec 1 09:38:40 tbox kernel: [ 0.075708] pnp 00:02: [io 0x00a8-0x00a9]
Dec 1 09:38:40 tbox kernel: [ 0.075710] pnp 00:02: [io 0x00ac-0x00ad]
Dec 1 09:38:40 tbox kernel: [ 0.075713] pnp 00:02: [io 0x00b0-0x00b5]
Dec 1 09:38:40 tbox kernel: [ 0.075716] pnp 00:02: [io 0x00b8-0x00b9]
Dec 1 09:38:40 tbox kernel: [ 0.075719] pnp 00:02: [io 0x00bc-0x00bd]
Dec 1 09:38:40 tbox kernel: [ 0.075722] pnp 00:02: [io 0x0050-0x0053]
Dec 1 09:38:40 tbox kernel: [ 0.075725] pnp 00:02: [io 0x0072-0x0077]
Dec 1 09:38:40 tbox kernel: [ 0.075728] pnp 00:02: [io 0x002e-0x002f]
Dec 1 09:38:40 tbox kernel: [ 0.075731] pnp 00:02: [io 0x1000-0x107f]
Dec 1 09:38:40 tbox kernel: [ 0.075734] pnp 00:02: [io 0x1180-0x11bf]
Dec 1 09:38:40 tbox kernel: [ 0.075737] pnp 00:02: [io 0x15e0-0x15ef]
Dec 1 09:38:40 tbox kernel: [ 0.075740] pnp 00:02: [io 0x1600-0x162f]
Dec 1 09:38:40 tbox kernel: [ 0.075743] pnp 00:02: [io 0x1632-0x167f]
Dec 1 09:38:40 tbox kernel: [ 0.075746] pnp 00:02: [io 0x004e-0x004f]
Dec 1 09:38:40 tbox kernel: [ 0.075749] pnp 00:02: [io 0x1630-0x1631]
Dec 1 09:38:40 tbox kernel: [ 0.075850] system 00:02: [io 0x1000-0x107f] has been reserved
Dec 1 09:38:40 tbox kernel: [ 0.075889] system 00:02: [io 0x1180-0x11bf] has been reserved
Dec 1 09:38:40 tbox kernel: [ 0.075927] system 00:02: [io 0x15e0-0x15ef] has been reserved
Dec 1 09:38:40 tbox kernel: [ 0.075965] system 00:02: [io 0x1600-0x162f] has been reserved
Dec 1 09:38:40 tbox kernel: [ 0.075965] system 00:02: [io 0x1632-0x167f] has been reserved
Dec 1 09:38:40 tbox kernel: [ 0.075965] system 00:02: [io 0x1630-0x1631] has been reserved
Dec 1 09:38:40 tbox kernel: [ 0.075965] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
Dec 1 09:38:40 tbox kernel: [ 0.075965] pnp 00:03: [io 0x0000-0x000f]
Dec 1 09:38:40 tbox kernel: [ 0.075965] pnp 00:03: [io 0x0080-0x008f]
Dec 1 09:38:40 tbox kernel: [ 0.075965] pnp 00:03: [io 0x00c0-0x00df]
Dec 1 09:38:40 tbox kernel: [ 0.075965] pnp 00:03: [dma 4]
Dec 1 09:38:40 tbox kernel: [ 0.075987] pnp 00:03: Plug and Play ACPI device, IDs PNP0200 (active)
Dec 1 09:38:40 tbox kernel: [ 0.076000] pnp 00:04: [io 0x0061]
Dec 1 09:38:40 tbox kernel: [ 0.076045] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Dec 1 09:38:40 tbox kernel: [ 0.076057] pnp 00:05: [io 0x00f0]
Dec 1 09:38:40 tbox kernel: [ 0.076062] pnp 00:05: [irq 13]
Dec 1 09:38:40 tbox kernel: [ 0.076103] pnp 00:05: Plug and Play ACPI device, IDs PNP0c04 (active)
Dec 1 09:38:40 tbox kernel: [ 0.076116] pnp 00:06: [io 0x0070-0x0071]
Dec 1 09:38:40 tbox kernel: [ 0.076119] pnp 00:06: [irq 8]
Dec 1 09:38:40 tbox kernel: [ 0.076159] pnp 00:06: Plug and Play ACPI device, IDs PNP0b00 (active)
Dec 1 09:38:40 tbox kernel: [ 0.076171] pnp 00:07: [io 0x0060]
Dec 1 09:38:40 tbox kernel: [ 0.076174] pnp 00:07: [io 0x0064]
Dec 1 09:38:40 tbox kernel: [ 0.076177] pnp 00:07: [irq 1]
Dec 1 09:38:40 tbox kernel: [ 0.076223] pnp 00:07: Plug and Play ACPI device, IDs PNP0303 (active)
Dec 1 09:38:40 tbox kernel: [ 0.076235] pnp 00:08: [irq 12]
Dec 1 09:38:40 tbox kernel: [ 0.076278] pnp 00:08: Plug and Play ACPI device, IDs IBM0057 PNP0f13 (active)
Dec 1 09:38:40 tbox kernel: [ 0.076320] pnp 00:09: [io 0x03f0-0x03f5]
Dec 1 09:38:40 tbox kernel: [ 0.076323] pnp 00:09: [io 0x03f7]
Dec 1 09:38:40 tbox kernel: [ 0.076326] pnp 00:09: [irq 6]
Dec 1 09:38:40 tbox kernel: [ 0.076328] pnp 00:09: [dma 2]
Dec 1 09:38:40 tbox kernel: [ 0.076386] pnp 00:09: Plug and Play ACPI device, IDs PNP0700 (active)
Dec 1 09:38:40 tbox kernel: [ 0.076509] pnp 00:0a: [io 0x03f8-0x03ff]
Dec 1 09:38:40 tbox kernel: [ 0.076513] pnp 00:0a: [irq 4]
Dec 1 09:38:40 tbox kernel: [ 0.076625] pnp 00:0a: Plug and Play ACPI device, IDs PNP0501 (active)
Dec 1 09:38:40 tbox kernel: [ 0.076781] pnp 00:0b: [io 0x03bc-0x03be]
Dec 1 09:38:40 tbox kernel: [ 0.076785] pnp 00:0b: [irq 7]
Dec 1 09:38:40 tbox kernel: [ 0.076887] pnp 00:0b: Plug and Play ACPI device, IDs PNP0400 (active)
Dec 1 09:38:40 tbox kernel: [ 0.077060] pnp 00:0c: Plug and Play ACPI device, IDs IBM0071 PNP0511 (disabled)
Dec 1 09:38:40 tbox kernel: [ 0.077716] pnp: PnP ACPI: found 13 devices
Dec 1 09:38:40 tbox kernel: [ 0.080456] ACPI: ACPI bus type pnp unregistered
Dec 1 09:38:40 tbox kernel: [ 0.080494] PnPBIOS: Disabled by ACPI PNP
Dec 1 09:38:40 tbox kernel: [ 0.118069] pci 0000:00:1f.1: BAR 5: assigned [mem 0xff7ffc00-0xff7fffff]
Dec 1 09:38:40 tbox kernel: [ 0.118114] pci 0000:00:1f.1: BAR 5: set to [mem 0xff7ffc00-0xff7fffff] (PCI address [0xff7ffc00-0xff7fffff])
Dec 1 09:38:40 tbox kernel: [ 0.118166] pci 0000:01:00.0: BAR 6: assigned [mem 0xc01e0000-0xc01fffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.118213] pci 0000:00:01.0: PCI bridge to [bus 01-01]
Dec 1 09:38:40 tbox kernel: [ 0.118250] pci 0000:00:01.0: bridge window [io 0x3000-0x3fff]
Dec 1 09:38:40 tbox kernel: [ 0.118290] pci 0000:00:01.0: bridge window [mem 0xc0100000-0xc01fffff]
Dec 1 09:38:40 tbox kernel: [ 0.118329] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe7ffffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.118382] pci 0000:02:00.0: BAR 15: assigned [mem 0xec000000-0xefffffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.118430] pci 0000:02:00.0: BAR 16: assigned [mem 0xcc000000-0xcfffffff]
Dec 1 09:38:40 tbox kernel: [ 0.118469] pci 0000:02:00.1: BAR 15: assigned [mem 0xe8000000-0xebffffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.118516] pci 0000:02:00.1: BAR 16: assigned [mem 0xc8000000-0xcbffffff]
Dec 1 09:38:40 tbox kernel: [ 0.118557] pci 0000:02:01.0: BAR 6: assigned [mem 0xc7ff0000-0xc7ffffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.118604] pci 0000:02:00.0: BAR 13: assigned [io 0x8c00-0x8cff]
Dec 1 09:38:40 tbox kernel: [ 0.118642] pci 0000:02:00.0: BAR 14: assigned [io 0x8800-0x88ff]
Dec 1 09:38:40 tbox kernel: [ 0.118680] pci 0000:02:00.1: BAR 13: assigned [io 0x8400-0x84ff]
Dec 1 09:38:40 tbox kernel: [ 0.118718] pci 0000:02:00.1: BAR 14: assigned [io 0x7c00-0x7cff]
Dec 1 09:38:40 tbox kernel: [ 0.118756] pci 0000:02:00.0: CardBus bridge to [bus 03-06]
Dec 1 09:38:40 tbox kernel: [ 0.118792] pci 0000:02:00.0: bridge window [io 0x8c00-0x8cff]
Dec 1 09:38:40 tbox kernel: [ 0.118832] pci 0000:02:00.0: bridge window [io 0x8800-0x88ff]
Dec 1 09:38:40 tbox kernel: [ 0.118871] pci 0000:02:00.0: bridge window [mem 0xec000000-0xefffffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.118920] pci 0000:02:00.0: bridge window [mem 0xcc000000-0xcfffffff]
Dec 1 09:38:40 tbox kernel: [ 0.118960] pci 0000:02:00.1: CardBus bridge to [bus 07-07]
Dec 1 09:38:40 tbox kernel: [ 0.118997] pci 0000:02:00.1: bridge window [io 0x8400-0x84ff]
Dec 1 09:38:40 tbox kernel: [ 0.119036] pci 0000:02:00.1: bridge window [io 0x7c00-0x7cff]
Dec 1 09:38:40 tbox kernel: [ 0.119075] pci 0000:02:00.1: bridge window [mem 0xe8000000-0xebffffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.119124] pci 0000:02:00.1: bridge window [mem 0xc8000000-0xcbffffff]
Dec 1 09:38:40 tbox kernel: [ 0.119164] pci 0000:00:1e.0: PCI bridge to [bus 02-08]
Dec 1 09:38:40 tbox kernel: [ 0.119202] pci 0000:00:1e.0: bridge window [io 0x4000-0x8fff]
Dec 1 09:38:40 tbox kernel: [ 0.119242] pci 0000:00:1e.0: bridge window [mem 0xc0200000-0xcfffffff]
Dec 1 09:38:40 tbox kernel: [ 0.119283] pci 0000:00:1e.0: bridge window [mem 0xe8000000-0xefffffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.119345] pci 0000:00:1e.0: setting latency timer to 64
Dec 1 09:38:40 tbox kernel: [ 0.119618] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
Dec 1 09:38:40 tbox kernel: [ 0.119656] PCI: setting IRQ 11 as level-triggered
Dec 1 09:38:40 tbox kernel: [ 0.119662] pci 0000:02:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
Dec 1 09:38:40 tbox kernel: [ 0.119943] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
Dec 1 09:38:40 tbox kernel: [ 0.119982] pci 0000:02:00.1: PCI INT B -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
Dec 1 09:38:40 tbox kernel: [ 0.120033] pci_bus 0000:00: resource 0 [io 0x0000-0xffff]
Dec 1 09:38:40 tbox kernel: [ 0.120037] pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffff]
Dec 1 09:38:40 tbox kernel: [ 0.120041] pci_bus 0000:01: resource 0 [io 0x3000-0x3fff]
Dec 1 09:38:40 tbox kernel: [ 0.120044] pci_bus 0000:01: resource 1 [mem 0xc0100000-0xc01fffff]
Dec 1 09:38:40 tbox kernel: [ 0.120048] pci_bus 0000:01: resource 2 [mem 0xe0000000-0xe7ffffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.120052] pci_bus 0000:02: resource 0 [io 0x4000-0x8fff]
Dec 1 09:38:40 tbox kernel: [ 0.120056] pci_bus 0000:02: resource 1 [mem 0xc0200000-0xcfffffff]
Dec 1 09:38:40 tbox kernel: [ 0.120059] pci_bus 0000:02: resource 2 [mem 0xe8000000-0xefffffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.120063] pci_bus 0000:02: resource 4 [io 0x0000-0xffff]
Dec 1 09:38:40 tbox kernel: [ 0.120067] pci_bus 0000:02: resource 5 [mem 0x00000000-0xffffffff]
Dec 1 09:38:40 tbox kernel: [ 0.120070] pci_bus 0000:03: resource 0 [io 0x8c00-0x8cff]
Dec 1 09:38:40 tbox kernel: [ 0.120074] pci_bus 0000:03: resource 1 [io 0x8800-0x88ff]
Dec 1 09:38:40 tbox kernel: [ 0.120077] pci_bus 0000:03: resource 2 [mem 0xec000000-0xefffffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.120081] pci_bus 0000:03: resource 3 [mem 0xcc000000-0xcfffffff]
Dec 1 09:38:40 tbox kernel: [ 0.120085] pci_bus 0000:07: resource 0 [io 0x8400-0x84ff]
Dec 1 09:38:40 tbox kernel: [ 0.120088] pci_bus 0000:07: resource 1 [io 0x7c00-0x7cff]
Dec 1 09:38:40 tbox kernel: [ 0.120092] pci_bus 0000:07: resource 2 [mem 0xe8000000-0xebffffff pref]
Dec 1 09:38:40 tbox kernel: [ 0.120096] pci_bus 0000:07: resource 3 [mem 0xc8000000-0xcbffffff]
Dec 1 09:38:40 tbox kernel: [ 0.120151] NET: Registered protocol family 2
Dec 1 09:38:40 tbox kernel: [ 0.120266] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
Dec 1 09:38:40 tbox kernel: [ 0.120679] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
Dec 1 09:38:40 tbox kernel: [ 0.122624] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
Dec 1 09:38:40 tbox kernel: [ 0.123826] TCP: Hash tables configured (established 131072 bind 65536)
Dec 1 09:38:40 tbox kernel: [ 0.123916] TCP reno registered
Dec 1 09:38:40 tbox kernel: [ 0.123957] UDP hash table entries: 512 (order: 2, 16384 bytes)
Dec 1 09:38:40 tbox kernel: [ 0.124028] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
Dec 1 09:38:40 tbox kernel: [ 0.124280] NET: Registered protocol family 1
Dec 1 09:38:40 tbox kernel: [ 0.124449] pci 0000:01:00.0: Boot video device
Dec 1 09:38:40 tbox kernel: [ 0.124468] PCI: CLS 32 bytes, default 64
Dec 1 09:38:40 tbox kernel: [ 0.124568] Unpacking initramfs...
Dec 1 09:38:40 tbox kernel: [ 0.546472] Freeing initrd memory: 9656k freed
Dec 1 09:38:40 tbox kernel: [ 0.562069] Simple Boot Flag at 0x35 set to 0x1
Dec 1 09:38:40 tbox kernel: [ 0.562525] audit: initializing netlink socket (disabled)
Dec 1 09:38:40 tbox kernel: [ 0.562583] type=2000 audit(1291196300.556:1): initialized
Dec 1 09:38:40 tbox kernel: [ 0.574593] highmem bounce pool size: 64 pages
Dec 1 09:38:40 tbox kernel: [ 0.574634] HugeTLB registered 4 MB page size, pre-allocated 0 pages
Dec 1 09:38:40 tbox kernel: [ 0.577413] VFS: Disk quotas dquot_6.5.2
Dec 1 09:38:40 tbox kernel: [ 0.577532] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Dec 1 09:38:40 tbox kernel: [ 0.577696] msgmni has been set to 1747
Dec 1 09:38:40 tbox kernel: [ 0.577987] alg: No test for stdrng (krng)
Dec 1 09:38:40 tbox kernel: [ 0.578099] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
Dec 1 09:38:40 tbox kernel: [ 0.578148] io scheduler noop registered
Dec 1 09:38:40 tbox kernel: [ 0.578182] io scheduler deadline registered
Dec 1 09:38:40 tbox kernel: [ 0.578237] io scheduler cfq registered (default)
Dec 1 09:38:40 tbox kernel: [ 0.578578] ERST: Table is not found!
Dec 1 09:38:40 tbox kernel: [ 0.578635] isapnp: Scanning for PnP cards...
Dec 1 09:38:40 tbox kernel: [ 0.931534] isapnp: No Plug & Play device found
Dec 1 09:38:40 tbox kernel: [ 0.931825] Linux agpgart interface v0.103
Dec 1 09:38:40 tbox kernel: [ 0.932007] agpgart-intel 0000:00:00.0: Intel 855PM Chipset
Dec 1 09:38:40 tbox kernel: [ 0.945619] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
Dec 1 09:38:40 tbox kernel: [ 0.945753] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
Dec 1 09:38:40 tbox kernel: [ 0.945896] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A
Dec 1 09:38:40 tbox kernel: [ 0.946416] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A
Dec 1 09:38:40 tbox kernel: [ 0.946576] serial 0000:00:1f.6: PCI INT B -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
Dec 1 09:38:40 tbox kernel: [ 0.946628] serial 0000:00:1f.6: PCI INT B disabled
Dec 1 09:38:40 tbox kernel: [ 0.946804] PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
Dec 1 09:38:40 tbox kernel: [ 0.952500] serio: i8042 KBD port at 0x60,0x64 irq 1
Dec 1 09:38:40 tbox kernel: [ 0.952546] serio: i8042 AUX port at 0x60,0x64 irq 12
Dec 1 09:38:40 tbox kernel: [ 0.952728] mice: PS/2 mouse device common for all mice
Dec 1 09:38:40 tbox kernel: [ 0.952804] rtc_cmos 00:06: RTC can wake from S4
Dec 1 09:38:40 tbox kernel: [ 0.952910] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
Dec 1 09:38:40 tbox kernel: [ 0.952963] rtc0: alarms up to one month, y3k, 114 bytes nvram
Dec 1 09:38:40 tbox kernel: [ 0.953011] cpuidle: using governor ladder
Dec 1 09:38:40 tbox kernel: [ 0.953046] cpuidle: using governor menu
Dec 1 09:38:40 tbox kernel: [ 0.953447] TCP cubic registered
Dec 1 09:38:40 tbox kernel: [ 0.953683] NET: Registered protocol family 10
Dec 1 09:38:40 tbox kernel: [ 0.954227] lo: Disabled Privacy Extensions
Dec 1 09:38:40 tbox kernel: [ 0.954544] Mobile IPv6
Dec 1 09:38:40 tbox kernel: [ 0.954578] NET: Registered protocol family 17
Dec 1 09:38:40 tbox kernel: [ 0.954616] Registering the dns_resolver key type
Dec 1 09:38:40 tbox kernel: [ 0.954672] Using IPI No-Shortcut mode
Dec 1 09:38:40 tbox kernel: [ 0.954825] PM: Hibernation image not present or could not be loaded.
Dec 1 09:38:40 tbox kernel: [ 0.954840] registered taskstats version 1
Dec 1 09:38:40 tbox kernel: [ 0.955112] rtc_cmos 00:06: setting system clock to 2010-12-01 09:38:21 UTC (1291196301)
Dec 1 09:38:40 tbox kernel: [ 0.955193] Initalizing network drop monitor service
Dec 1 09:38:40 tbox kernel: [ 0.958889] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
Dec 1 09:38:40 tbox kernel: [ 0.970906] Freeing unused kernel memory: 392k freed
Dec 1 09:38:40 tbox kernel: [ 0.971220] Write protecting the kernel text: 2668k
Dec 1 09:38:40 tbox kernel: [ 0.971288] Write protecting the kernel read-only data: 980k
Dec 1 09:38:40 tbox kernel: [ 0.996108] udev[45]: starting version 164
Dec 1 09:38:40 tbox kernel: [ 1.175446] Floppy drive(s): fd0 is 1.44M
Dec 1 09:38:40 tbox kernel: [ 1.195146] FDC 0 is a National Semiconductor PC87306
Dec 1 09:38:40 tbox kernel: [ 1.221841] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
Dec 1 09:38:40 tbox kernel: [ 1.221912] e1000: Copyright (c) 1999-2006 Intel Corporation.
Dec 1 09:38:40 tbox kernel: [ 1.222813] e1000 0000:02:01.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
Dec 1 09:38:40 tbox kernel: [ 1.223148] thermal LNXTHERM:00: registered as thermal_zone0
Dec 1 09:38:40 tbox kernel: [ 1.223185] ACPI: Thermal Zone [THM0] (50 C)
Dec 1 09:38:40 tbox kernel: [ 1.573822] usbcore: registered new interface driver usbfs
Dec 1 09:38:40 tbox kernel: [ 1.574044] usbcore: registered new interface driver hub
Dec 1 09:38:40 tbox kernel: [ 1.574145] usbcore: registered new device driver usb
Dec 1 09:38:40 tbox kernel: [ 1.579561] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Dec 1 09:38:40 tbox kernel: [ 1.579648] ehci_hcd 0000:00:1d.7: power state changed by ACPI to D0
Dec 1 09:38:40 tbox kernel: [ 1.579689] ehci_hcd 0000:00:1d.7: power state changed by ACPI to D0
Dec 1 09:38:40 tbox kernel: [ 1.580048] ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 11
Dec 1 09:38:40 tbox kernel: [ 1.580088] ehci_hcd 0000:00:1d.7: PCI INT D -> Link[LNKH] -> GSI 11 (level, low) -> IRQ 11
Dec 1 09:38:40 tbox kernel: [ 1.580160] ehci_hcd 0000:00:1d.7: setting latency timer to 64
Dec 1 09:38:40 tbox kernel: [ 1.580165] ehci_hcd 0000:00:1d.7: EHCI Host Controller
Dec 1 09:38:40 tbox kernel: [ 1.580230] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
Dec 1 09:38:40 tbox kernel: [ 1.580313] ehci_hcd 0000:00:1d.7: debug port 1
Dec 1 09:38:40 tbox kernel: [ 1.584243] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
Dec 1 09:38:40 tbox kernel: [ 1.585759] SCSI subsystem initialized
Dec 1 09:38:40 tbox kernel: [ 1.600146] ehci_hcd 0000:00:1d.7: irq 11, io mem 0xc0000000
Dec 1 09:38:40 tbox kernel: [ 1.609038] e1000 0000:02:01.0: eth0: (PCI:33MHz:32-bit) 00:0d:60:b0:62:87
Dec 1 09:38:40 tbox kernel: [ 1.609084] e1000 0000:02:01.0: eth0: Intel(R) PRO/1000 Network Connection
Dec 1 09:38:40 tbox kernel: [ 1.645381] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
Dec 1 09:38:40 tbox kernel: [ 1.645489] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Dec 1 09:38:40 tbox kernel: [ 1.645528] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Dec 1 09:38:40 tbox kernel: [ 1.645575] usb usb1: Product: EHCI Host Controller
Dec 1 09:38:40 tbox kernel: [ 1.645610] usb usb1: Manufacturer: Linux 2.6.37-rc4-686 ehci_hcd
Dec 1 09:38:40 tbox kernel: [ 1.645648] usb usb1: SerialNumber: 0000:00:1d.7
Dec 1 09:38:40 tbox kernel: [ 1.646583] libata version 3.00 loaded.
Dec 1 09:38:40 tbox kernel: [ 1.653417] hub 1-0:1.0: USB hub found
Dec 1 09:38:40 tbox kernel: [ 1.653459] hub 1-0:1.0: 6 ports detected
Dec 1 09:38:40 tbox kernel: [ 1.653611] ata_piix 0000:00:1f.1: version 2.13
Dec 1 09:38:40 tbox kernel: [ 1.653626] ata_piix 0000:00:1f.1: enabling device (0005 -> 0007)
Dec 1 09:38:40 tbox kernel: [ 1.653958] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
Dec 1 09:38:40 tbox kernel: [ 1.653998] ata_piix 0000:00:1f.1: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
Dec 1 09:38:40 tbox kernel: [ 1.654095] ata_piix 0000:00:1f.1: setting latency timer to 64
Dec 1 09:38:40 tbox kernel: [ 1.655553] scsi0 : ata_piix
Dec 1 09:38:40 tbox kernel: [ 1.657311] scsi1 : ata_piix
Dec 1 09:38:40 tbox kernel: [ 1.658214] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x1860 irq 14
Dec 1 09:38:40 tbox kernel: [ 1.658254] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x1868 irq 15
Dec 1 09:38:40 tbox kernel: [ 1.693570] uhci_hcd: USB Universal Host Controller Interface driver
Dec 1 09:38:40 tbox kernel: [ 1.693707] uhci_hcd 0000:00:1d.0: power state changed by ACPI to D0
Dec 1 09:38:40 tbox kernel: [ 1.693746] uhci_hcd 0000:00:1d.0: power state changed by ACPI to D0
Dec 1 09:38:40 tbox kernel: [ 1.693792] uhci_hcd 0000:00:1d.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
Dec 1 09:38:40 tbox kernel: [ 1.693851] uhci_hcd 0000:00:1d.0: setting latency timer to 64
Dec 1 09:38:40 tbox kernel: [ 1.693856] uhci_hcd 0000:00:1d.0: UHCI Host Controller
Dec 1 09:38:40 tbox kernel: [ 1.693906] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
Dec 1 09:38:40 tbox kernel: [ 1.693987] uhci_hcd 0000:00:1d.0: irq 11, io base 0x00001800
Dec 1 09:38:40 tbox kernel: [ 1.694079] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
Dec 1 09:38:40 tbox kernel: [ 1.694118] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Dec 1 09:38:40 tbox kernel: [ 1.694164] usb usb2: Product: UHCI Host Controller
Dec 1 09:38:40 tbox kernel: [ 1.694200] usb usb2: Manufacturer: Linux 2.6.37-rc4-686 uhci_hcd
Dec 1 09:38:40 tbox kernel: [ 1.694237] usb usb2: SerialNumber: 0000:00:1d.0
Dec 1 09:38:40 tbox kernel: [ 1.694542] hub 2-0:1.0: USB hub found
Dec 1 09:38:40 tbox kernel: [ 1.694581] hub 2-0:1.0: 2 ports detected
Dec 1 09:38:40 tbox kernel: [ 1.694714] uhci_hcd 0000:00:1d.1: power state changed by ACPI to D0
Dec 1 09:38:40 tbox kernel: [ 1.694753] uhci_hcd 0000:00:1d.1: power state changed by ACPI to D0
Dec 1 09:38:40 tbox kernel: [ 1.695074] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
Dec 1 09:38:40 tbox kernel: [ 1.695113] uhci_hcd 0000:00:1d.1: PCI INT B -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
Dec 1 09:38:40 tbox kernel: [ 1.695165] uhci_hcd 0000:00:1d.1: setting latency timer to 64
Dec 1 09:38:40 tbox kernel: [ 1.695170] uhci_hcd 0000:00:1d.1: UHCI Host Controller
Dec 1 09:38:40 tbox kernel: [ 1.695214] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
Dec 1 09:38:40 tbox kernel: [ 1.697999] uhci_hcd 0000:00:1d.1: irq 11, io base 0x00001820
Dec 1 09:38:40 tbox kernel: [ 1.698087] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
Dec 1 09:38:40 tbox kernel: [ 1.698125] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Dec 1 09:38:40 tbox kernel: [ 1.698172] usb usb3: Product: UHCI Host Controller
Dec 1 09:38:40 tbox kernel: [ 1.698207] usb usb3: Manufacturer: Linux 2.6.37-rc4-686 uhci_hcd
Dec 1 09:38:40 tbox kernel: [ 1.698244] usb usb3: SerialNumber: 0000:00:1d.1
Dec 1 09:38:40 tbox kernel: [ 1.698783] hub 3-0:1.0: USB hub found
Dec 1 09:38:40 tbox kernel: [ 1.698822] hub 3-0:1.0: 2 ports detected
Dec 1 09:38:40 tbox kernel: [ 1.698961] uhci_hcd 0000:00:1d.2: PCI INT C -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
Dec 1 09:38:40 tbox kernel: [ 1.699014] uhci_hcd 0000:00:1d.2: setting latency timer to 64
Dec 1 09:38:40 tbox kernel: [ 1.699019] uhci_hcd 0000:00:1d.2: UHCI Host Controller
Dec 1 09:38:40 tbox kernel: [ 1.699065] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
Dec 1 09:38:40 tbox kernel: [ 1.699134] uhci_hcd 0000:00:1d.2: irq 11, io base 0x00001840
Dec 1 09:38:40 tbox kernel: [ 1.699215] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
Dec 1 09:38:40 tbox kernel: [ 1.699254] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Dec 1 09:38:40 tbox kernel: [ 1.699300] usb usb4: Product: UHCI Host Controller
Dec 1 09:38:40 tbox kernel: [ 1.699336] usb usb4: Manufacturer: Linux 2.6.37-rc4-686 uhci_hcd
Dec 1 09:38:40 tbox kernel: [ 1.699373] usb usb4: SerialNumber: 0000:00:1d.2
Dec 1 09:38:40 tbox kernel: [ 1.699914] hub 4-0:1.0: USB hub found
Dec 1 09:38:40 tbox kernel: [ 1.699954] hub 4-0:1.0: 2 ports detected
Dec 1 09:38:40 tbox kernel: [ 1.816216] ata2.01: NODEV after polling detection
Dec 1 09:38:40 tbox kernel: [ 1.820556] ata1.00: HPA detected: current 110257519, native 117210240
Dec 1 09:38:40 tbox kernel: [ 1.820602] ata1.00: ATA-6: HTS726060M9AT00, MH4OA6BA, max UDMA/100
Dec 1 09:38:40 tbox kernel: [ 1.820641] ata1.00: 110257519 sectors, multi 16: LBA
Dec 1 09:38:40 tbox kernel: [ 1.824647] ata2.00: ATAPI: UJDA755yDVD/CDRW, 1.70, max UDMA/33
Dec 1 09:38:40 tbox kernel: [ 1.836426] ata1.00: configured for UDMA/100
Dec 1 09:38:40 tbox kernel: [ 1.836634] scsi 0:0:0:0: Direct-Access ATA HTS726060M9AT00 MH4O PQ: 0 ANSI: 5
Dec 1 09:38:40 tbox kernel: [ 1.840511] ata2.00: configured for UDMA/33
Dec 1 09:38:40 tbox kernel: [ 1.843419] scsi 1:0:0:0: CD-ROM MATSHITA UJDA755yDVD/CDRW 1.70 PQ: 0 ANSI: 5
Dec 1 09:38:40 tbox kernel: [ 1.879110] sd 0:0:0:0: [sda] 110257519 512-byte logical blocks: (56.4 GB/52.5 GiB)
Dec 1 09:38:40 tbox kernel: [ 1.879233] sd 0:0:0:0: [sda] Write Protect is off
Dec 1 09:38:40 tbox kernel: [ 1.879270] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Dec 1 09:38:40 tbox kernel: [ 1.879300] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 1 09:38:40 tbox kernel: [ 1.883492] sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
Dec 1 09:38:40 tbox kernel: [ 1.883533] cdrom: Uniform CD-ROM driver Revision: 3.20
Dec 1 09:38:40 tbox kernel: [ 1.883929] sr 1:0:0:0: Attached scsi CD-ROM sr0
Dec 1 09:38:40 tbox kernel: [ 1.939710] sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
Dec 1 09:38:40 tbox kernel: [ 1.940515] sd 0:0:0:0: [sda] Attached SCSI disk
Dec 1 09:38:40 tbox kernel: [ 1.956264] sd 0:0:0:0: Attached scsi generic sg0 type 0
Dec 1 09:38:40 tbox kernel: [ 1.956773] sr 1:0:0:0: Attached scsi generic sg1 type 5
Dec 1 09:38:40 tbox kernel: [ 2.020021] usb 1-4: new high speed USB device using ehci_hcd and address 3
Dec 1 09:38:40 tbox kernel: [ 2.152975] usb 1-4: New USB device found, idVendor=152d, idProduct=2329
Dec 1 09:38:40 tbox kernel: [ 2.153021] usb 1-4: New USB device strings: Mfr=10, Product=11, SerialNumber=3
Dec 1 09:38:40 tbox kernel: [ 2.153069] usb 1-4: Product: Storagebird 35EV821
Dec 1 09:38:40 tbox kernel: [ 2.153105] usb 1-4: Manufacturer: 0123456
Dec 1 09:38:40 tbox kernel: [ 2.153141] usb 1-4: SerialNumber: 000000000340
Dec 1 09:38:40 tbox kernel: [ 2.169486] Initializing USB Mass Storage driver...
Dec 1 09:38:40 tbox kernel: [ 2.169649] scsi2 : usb-storage 1-4:1.0
Dec 1 09:38:40 tbox kernel: [ 2.169868] usbcore: registered new interface driver usb-storage
Dec 1 09:38:40 tbox kernel: [ 2.169906] USB Mass Storage support registered.
Dec 1 09:38:40 tbox kernel: [ 2.392019] usb 3-1: new low speed USB device using uhci_hcd and address 2
Dec 1 09:38:40 tbox kernel: [ 2.542915] device-mapper: uevent: version 1.0.3
Dec 1 09:38:40 tbox kernel: [ 2.543608] device-mapper: ioctl: 4.18.0-ioctl (2010-06-29) initialised: dm-devel@redhat.com
Dec 1 09:38:40 tbox kernel: [ 2.571048] usb 3-1: New USB device found, idVendor=046d, idProduct=c00e
Dec 1 09:38:40 tbox kernel: [ 2.571091] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 1 09:38:40 tbox kernel: [ 2.571130] usb 3-1: Product: USB-PS/2 Optical Mouse
Dec 1 09:38:40 tbox kernel: [ 2.571166] usb 3-1: Manufacturer: Logitech
Dec 1 09:38:40 tbox kernel: [ 2.635561] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input1
Dec 1 09:38:40 tbox kernel: [ 2.635819] generic-usb 0003:046D:C00E.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.1-1/input0
Dec 1 09:38:40 tbox kernel: [ 2.636072] usbcore: registered new interface driver usbhid
Dec 1 09:38:40 tbox kernel: [ 2.636109] usbhid: USB HID core driver
Dec 1 09:38:40 tbox kernel: [ 2.855722] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
Dec 1 09:38:40 tbox kernel: [ 3.210220] scsi 2:0:0:0: Direct-Access WDC WD10 EAVS-00D7B0 PQ: 0 ANSI: 2 CCS
Dec 1 09:38:40 tbox kernel: [ 3.210900] sd 2:0:0:0: Attached scsi generic sg2 type 0
Dec 1 09:38:40 tbox kernel: [ 3.211308] sd 2:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Dec 1 09:38:40 tbox kernel: [ 3.212056] sd 2:0:0:0: [sdb] Write Protect is off
Dec 1 09:38:40 tbox kernel: [ 3.212093] sd 2:0:0:0: [sdb] Mode Sense: 34 00 00 00
Dec 1 09:38:40 tbox kernel: [ 3.212097] sd 2:0:0:0: [sdb] Assuming drive cache: write through
Dec 1 09:38:40 tbox kernel: [ 3.213677] sd 2:0:0:0: [sdb] Assuming drive cache: write through
Dec 1 09:38:40 tbox kernel: [ 3.296932] sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 >
Dec 1 09:38:40 tbox kernel: [ 3.299049] sd 2:0:0:0: [sdb] Assuming drive cache: write through
Dec 1 09:38:40 tbox kernel: [ 3.299089] sd 2:0:0:0: [sdb] Attached SCSI disk
Dec 1 09:38:40 tbox kernel: [ 4.860063] udev[258]: starting version 164
Dec 1 09:38:40 tbox kernel: [ 5.447784] input: PC Speaker as /devices/platform/pcspkr/input/input2
Dec 1 09:38:40 tbox kernel: [ 5.678188] Non-volatile memory driver v1.3
Dec 1 09:38:40 tbox kernel: [ 5.863739] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Dec 1 09:38:40 tbox kernel: [ 5.901679] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input3
Dec 1 09:38:40 tbox kernel: [ 5.902051] ACPI: Lid Switch [LID]
Dec 1 09:38:40 tbox kernel: [ 5.903811] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input4
Dec 1 09:38:40 tbox kernel: [ 5.904024] ACPI: Sleep Button [SLPB]
Dec 1 09:38:40 tbox kernel: [ 5.904579] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
Dec 1 09:38:40 tbox kernel: [ 5.904744] ACPI: Power Button [PWRF]
Dec 1 09:38:40 tbox kernel: [ 5.919420] ACPI: AC Adapter [AC] (on-line)
Dec 1 09:38:40 tbox kernel: [ 5.933580] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A03:00/device:03/LNXVIDEO:00/input/input6
Dec 1 09:38:40 tbox kernel: [ 5.934268] ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
Dec 1 09:38:40 tbox kernel: [ 5.943392] ACPI: acpi_idle registered with cpuidle
Dec 1 09:38:40 tbox kernel: [ 5.944555] Marking TSC unstable due to TSC halts in idle
Dec 1 09:38:40 tbox kernel: [ 5.946353] Switching to clocksource acpi_pm
Dec 1 09:38:40 tbox kernel: [ 6.060495] ACPI: Battery Slot [BAT0] (battery present)
Dec 1 09:38:40 tbox kernel: [ 6.064966] i801_smbus 0000:00:1f.3: PCI INT B -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
Dec 1 09:38:40 tbox kernel: [ 6.133576] NET: Registered protocol family 23
Dec 1 09:38:40 tbox kernel: [ 6.134765] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Dec 1 09:38:40 tbox kernel: [ 6.143464] parport_pc 00:0b: reported by Plug and Play ACPI
Dec 1 09:38:40 tbox kernel: [ 6.143547] parport0: PC-style at 0x3bc, irq 7 [PCSPP,TRISTATE]
Dec 1 09:38:40 tbox kernel: [ 6.296698] [drm] Initialized drm 1.1.0 20060810
Dec 1 09:38:40 tbox kernel: [ 6.510028] nsc-ircc 00:0c: [io 0x02f8-0x02ff]
Dec 1 09:38:40 tbox kernel: [ 6.510092] nsc-ircc 00:0c: [irq 3]
Dec 1 09:38:40 tbox kernel: [ 6.510097] nsc-ircc 00:0c: [dma 1]
Dec 1 09:38:40 tbox kernel: [ 6.510681] nsc-ircc 00:0c: activated
Dec 1 09:38:40 tbox kernel: [ 6.510887] nsc-ircc, chip->init
Dec 1 09:38:40 tbox kernel: [ 6.510927] nsc-ircc, Found chip at base=0x02e
Dec 1 09:38:40 tbox kernel: [ 6.510983] nsc-ircc, driver loaded (Dag Brattli)
Dec 1 09:38:40 tbox kernel: [ 6.512507] IrDA: Registered device irda0
Dec 1 09:38:40 tbox kernel: [ 6.512545] nsc-ircc, Using dongle: IBM31T1100 or Temic TFDS6000/TFDS6500
Dec 1 09:38:40 tbox kernel: [ 6.584584] intel_rng: FWH not detected
Dec 1 09:38:40 tbox kernel: [ 6.787336] yenta_cardbus 0000:02:00.0: CardBus bridge found [1014:0512]
Dec 1 09:38:40 tbox kernel: [ 6.787395] yenta_cardbus 0000:02:00.0: Using INTVAL to route CSC interrupts to PCI
Dec 1 09:38:40 tbox kernel: [ 6.787441] yenta_cardbus 0000:02:00.0: Routing CardBus interrupts to PCI
Dec 1 09:38:40 tbox kernel: [ 6.787481] yenta_cardbus 0000:02:00.0: TI: mfunc 0x01d21022, devctl 0x64
Dec 1 09:38:40 tbox kernel: [ 6.919633] cfg80211: Calling CRDA to update world regulatory domain
Dec 1 09:38:40 tbox kernel: [ 6.996087] Synaptics Touchpad, model: 1, fw: 5.9, id: 0x2c6ab1, caps: 0x884793/0x0/0x0
Dec 1 09:38:40 tbox kernel: [ 6.996146] serio: Synaptics pass-through port at isa0060/serio1/input0
Dec 1 09:38:40 tbox kernel: [ 7.020907] yenta_cardbus 0000:02:00.0: ISA IRQ mask 0x0438, PCI irq 11
Dec 1 09:38:40 tbox kernel: [ 7.020949] yenta_cardbus 0000:02:00.0: Socket status: 30000006
Dec 1 09:38:40 tbox kernel: [ 7.020995] yenta_cardbus 0000:02:00.0: pcmcia: parent PCI bridge window: [io 0x4000-0x8fff]
Dec 1 09:38:40 tbox kernel: [ 7.021044] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x4000-0x8fff: excluding 0x7c00-0x7cff 0x8000-0x803f 0x8400-0x84ff 0x8800-0x88ff 0x8c00-0x8cff
Dec 1 09:38:40 tbox kernel: [ 7.037318] yenta_cardbus 0000:02:00.0: pcmcia: parent PCI bridge window: [mem 0xc0200000-0xcfffffff]
Dec 1 09:38:40 tbox kernel: [ 7.037368] pcmcia_socket pcmcia_socket0: cs: memory probe 0xc0200000-0xcfffffff: excluding 0xc0200000-0xc09fffff 0xc7a00000-0xd01fffff
Dec 1 09:38:40 tbox kernel: [ 7.037522] yenta_cardbus 0000:02:00.0: pcmcia: parent PCI bridge window: [mem 0xe8000000-0xefffffff pref]
Dec 1 09:38:40 tbox kernel: [ 7.037572] pcmcia_socket pcmcia_socket0: cs: memory probe 0xe8000000-0xefffffff: excluding 0xe8000000-0xefffffff
Dec 1 09:38:40 tbox kernel: [ 7.038190] yenta_cardbus 0000:02:00.1: CardBus bridge found [1014:0512]
Dec 1 09:38:40 tbox kernel: [ 7.038243] yenta_cardbus 0000:02:00.1: Using INTVAL to route CSC interrupts to PCI
Dec 1 09:38:40 tbox kernel: [ 7.038290] yenta_cardbus 0000:02:00.1: Routing CardBus interrupts to PCI
Dec 1 09:38:40 tbox kernel: [ 7.038330] yenta_cardbus 0000:02:00.1: TI: mfunc 0x01d21022, devctl 0x64
Dec 1 09:38:40 tbox kernel: [ 7.038554] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input7
Dec 1 09:38:40 tbox kernel: [ 7.268730] yenta_cardbus 0000:02:00.1: ISA IRQ mask 0x0438, PCI irq 11
Dec 1 09:38:40 tbox kernel: [ 7.268778] yenta_cardbus 0000:02:00.1: Socket status: 30000006
Dec 1 09:38:40 tbox kernel: [ 7.268826] yenta_cardbus 0000:02:00.1: pcmcia: parent PCI bridge window: [io 0x4000-0x8fff]
Dec 1 09:38:40 tbox kernel: [ 7.268877] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x4000-0x8fff: excluding 0x7c00-0x7cff 0x8000-0x803f 0x8400-0x84ff 0x8800-0x88ff 0x8c00-0x8cff
Dec 1 09:38:40 tbox kernel: [ 7.301966] yenta_cardbus 0000:02:00.1: pcmcia: parent PCI bridge window: [mem 0xc0200000-0xcfffffff]
Dec 1 09:38:40 tbox kernel: [ 7.302020] pcmcia_socket pcmcia_socket1: cs: memory probe 0xc0200000-0xcfffffff: excluding 0xc0200000-0xc09fffff 0xc7a00000-0xd01fffff
Dec 1 09:38:40 tbox kernel: [ 7.302185] yenta_cardbus 0000:02:00.1: pcmcia: parent PCI bridge window: [mem 0xe8000000-0xefffffff pref]
Dec 1 09:38:40 tbox kernel: [ 7.302236] pcmcia_socket pcmcia_socket1: cs: memory probe 0xe8000000-0xefffffff: excluding 0xe8000000-0xefffffff
Dec 1 09:38:40 tbox kernel: [ 7.401522] ath5k 0000:02:02.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
Dec 1 09:38:40 tbox kernel: [ 7.401677] ath5k 0000:02:02.0: registered as 'phy0'
Dec 1 09:38:40 tbox kernel: [ 7.689793] ath: EEPROM regdomain: 0x61
Dec 1 09:38:40 tbox kernel: [ 7.689797] ath: EEPROM indicates we should expect a direct regpair map
Dec 1 09:38:40 tbox kernel: [ 7.689803] ath: Country alpha2 being used: 00
Dec 1 09:38:40 tbox kernel: [ 7.689805] ath: Regpair used: 0x61
Dec 1 09:38:40 tbox kernel: [ 8.127753] [drm] radeon kernel modesetting enabled.
Dec 1 09:38:40 tbox kernel: [ 8.127958] radeon 0000:01:00.0: power state changed by ACPI to D0
Dec 1 09:38:40 tbox kernel: [ 8.128031] radeon 0000:01:00.0: power state changed by ACPI to D0
Dec 1 09:38:40 tbox kernel: [ 8.131235] radeon 0000:01:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
Dec 1 09:38:40 tbox kernel: [ 8.136749] [drm] initializing kernel modesetting (RV250 0x1002:0x4C66).
Dec 1 09:38:40 tbox kernel: [ 8.136992] [drm] register mmio base: 0xC0100000
Dec 1 09:38:40 tbox kernel: [ 8.137028] [drm] register mmio size: 65536
Dec 1 09:38:40 tbox kernel: [ 8.137416] agpgart-intel 0000:00:00.0: AGP 2.0 bridge
Dec 1 09:38:40 tbox kernel: [ 8.137469] agpgart-intel 0000:00:00.0: putting AGP V2 device into 4x mode
Dec 1 09:38:40 tbox kernel: [ 8.137545] radeon 0000:01:00.0: putting AGP V2 device into 4x mode
Dec 1 09:38:40 tbox kernel: [ 8.137610] radeon 0000:01:00.0: GTT: 256M 0xD0000000 - 0xDFFFFFFF
Dec 1 09:38:40 tbox kernel: [ 8.137654] radeon 0000:01:00.0: VRAM: 128M 0xE0000000 - 0xE7FFFFFF (64M used)
Dec 1 09:38:40 tbox kernel: [ 8.137710] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
Dec 1 09:38:40 tbox kernel: [ 8.137748] [drm] Driver supports precise vblank timestamp query.
Dec 1 09:38:40 tbox kernel: [ 8.137803] [drm] radeon: irq initialized.
Dec 1 09:38:40 tbox kernel: [ 8.138621] [drm] Detected VRAM RAM=128M, BAR=128M
Dec 1 09:38:40 tbox kernel: [ 8.138664] [drm] RAM width 128bits DDR
Dec 1 09:38:40 tbox kernel: [ 8.138811] [TTM] Zone kernel: Available graphics memory: 447502 kiB.
Dec 1 09:38:40 tbox kernel: [ 8.138868] [TTM] Zone highmem: Available graphics memory: 516818 kiB.
Dec 1 09:38:40 tbox kernel: [ 8.138906] [TTM] Initializing pool allocator.
Dec 1 09:38:40 tbox kernel: [ 8.139224] [drm] radeon: 64M of VRAM memory ready
Dec 1 09:38:40 tbox kernel: [ 8.139261] [drm] radeon: 256M of GTT memory ready.
Dec 1 09:38:40 tbox kernel: [ 8.141028] radeon 0000:01:00.0: WB enabled
Dec 1 09:38:40 tbox kernel: [ 8.142220] [drm] Loading R200 Microcode
Dec 1 09:38:40 tbox kernel: [ 8.232093] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Dec 1 09:38:40 tbox kernel: [ 8.233067] Registered led device: ath5k-phy0::rx
Dec 1 09:38:40 tbox kernel: [ 8.233106] Registered led device: ath5k-phy0::tx
Dec 1 09:38:40 tbox kernel: [ 8.233119] ath5k phy0: Atheros AR5212 chip found (MAC: 0x56, PHY: 0x41)
Dec 1 09:38:40 tbox kernel: [ 8.233165] ath5k phy0: RF5111 5GHz radio found (0x17)
Dec 1 09:38:40 tbox kernel: [ 8.233202] ath5k phy0: RF2111 2GHz radio found (0x23)
Dec 1 09:38:40 tbox kernel: [ 8.276091] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x100-0x3af: excluding 0x170-0x177 0x1f0-0x1f7 0x2f8-0x2ff 0x370-0x377
Dec 1 09:38:40 tbox kernel: [ 8.277427] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3e0-0x4ff: excluding 0x3f0-0x3ff 0x4d0-0x4d7
Dec 1 09:38:40 tbox kernel: [ 8.278051] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x820-0x8ff: clean.
Dec 1 09:38:40 tbox kernel: [ 8.278536] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xc00-0xcf7: clean.
Dec 1 09:38:40 tbox kernel: [ 8.279058] pcmcia_socket pcmcia_socket1: cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xd3fff 0xdc000-0xfffff
Dec 1 09:38:40 tbox kernel: [ 8.279254] pcmcia_socket pcmcia_socket1: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Dec 1 09:38:40 tbox kernel: [ 8.279381] pcmcia_socket pcmcia_socket1: cs: memory probe 0x60000000-0x60ffffff: clean.
Dec 1 09:38:40 tbox kernel: [ 8.279515] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xa00-0xaff: clean.
Dec 1 09:38:40 tbox kernel: [ 8.280161] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding 0x170-0x177 0x1f0-0x1f7 0x2f8-0x2ff 0x370-0x377
Dec 1 09:38:40 tbox kernel: [ 8.281455] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x3f0-0x3ff 0x4d0-0x4d7
Dec 1 09:38:40 tbox kernel: [ 8.282079] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean.
Dec 1 09:38:40 tbox kernel: [ 8.290664] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean.
Dec 1 09:38:40 tbox kernel: [ 8.291367] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xd3fff 0xdc000-0xfffff
Dec 1 09:38:40 tbox kernel: [ 8.291680] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Dec 1 09:38:40 tbox kernel: [ 8.291849] pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff: clean.
Dec 1 09:38:40 tbox kernel: [ 8.292133] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean.
Dec 1 09:38:40 tbox kernel: [ 8.431984] [drm] radeon: ring at 0x00000000D0001000
Dec 1 09:38:40 tbox kernel: [ 8.432084] [drm] ring test succeeded in 1 usecs
Dec 1 09:38:40 tbox kernel: [ 8.432424] [drm] radeon: ib pool ready.
Dec 1 09:38:40 tbox kernel: [ 8.433065] [drm] ib test succeeded in 0 usecs
Dec 1 09:38:40 tbox kernel: [ 8.435203] [drm] Panel ID String: SXGA+ Single (85MHz)
Dec 1 09:38:40 tbox kernel: [ 8.435243] [drm] Panel Size 1400x1050
Dec 1 09:38:40 tbox kernel: [ 8.446362] [drm] radeon legacy LVDS backlight initialized
Dec 1 09:38:40 tbox kernel: [ 8.446731] [drm] No TV DAC info found in BIOS
Dec 1 09:38:40 tbox kernel: [ 8.446993] [drm] Radeon Display Connectors
Dec 1 09:38:40 tbox kernel: [ 8.447028] [drm] Connector 0:
Dec 1 09:38:40 tbox kernel: [ 8.447061] [drm] VGA
Dec 1 09:38:40 tbox kernel: [ 8.447094] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
Dec 1 09:38:40 tbox kernel: [ 8.447131] [drm] Encoders:
Dec 1 09:38:40 tbox kernel: [ 8.447164] [drm] CRT1: INTERNAL_DAC1
Dec 1 09:38:40 tbox kernel: [ 8.447198] [drm] Connector 1:
Dec 1 09:38:40 tbox kernel: [ 8.447231] [drm] DVI-D
Dec 1 09:38:40 tbox kernel: [ 8.447263] [drm] HPD1
Dec 1 09:38:40 tbox kernel: [ 8.447296] [drm] DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
Dec 1 09:38:40 tbox kernel: [ 8.447332] [drm] Encoders:
Dec 1 09:38:40 tbox kernel: [ 8.447365] [drm] DFP1: INTERNAL_TMDS1
Dec 1 09:38:40 tbox kernel: [ 8.447400] [drm] Connector 2:
Dec 1 09:38:40 tbox kernel: [ 8.447433] [drm] LVDS
Dec 1 09:38:40 tbox kernel: [ 8.447465] [drm] Encoders:
Dec 1 09:38:40 tbox kernel: [ 8.447497] [drm] LCD1: INTERNAL_LVDS
Dec 1 09:38:40 tbox kernel: [ 8.447531] [drm] Connector 3:
Dec 1 09:38:40 tbox kernel: [ 8.447564] [drm] S-video
Dec 1 09:38:40 tbox kernel: [ 8.447596] [drm] Encoders:
Dec 1 09:38:40 tbox kernel: [ 8.447629] [drm] TV1: INTERNAL_DAC2
Dec 1 09:38:40 tbox kernel: [ 8.451664] [drm] radeon: power management initialized
Dec 1 09:38:40 tbox kernel: [ 8.519403] [drm] fb mappable at 0xE0040000
Dec 1 09:38:40 tbox kernel: [ 8.519442] [drm] vram apper at 0xE0000000
Dec 1 09:38:40 tbox kernel: [ 8.519476] [drm] size 5914624
Dec 1 09:38:40 tbox kernel: [ 8.519508] [drm] fb depth is 24
Dec 1 09:38:40 tbox kernel: [ 8.519541] [drm] pitch is 5632
Dec 1 09:38:40 tbox kernel: [ 8.568699] thinkpad_acpi: ThinkPad ACPI Extras v0.24
Dec 1 09:38:40 tbox kernel: [ 8.568704] thinkpad_acpi: http://ibm-acpi.sf.net/
Dec 1 09:38:40 tbox kernel: [ 8.568706] thinkpad_acpi: ThinkPad BIOS 1RETDRWW (3.23 ), EC 1RHT71WW-3.04
Dec 1 09:38:41 tbox kernel: [ 8.568709] thinkpad_acpi: IBM ThinkPad T40p, model 2374SG6
Dec 1 09:38:41 tbox kernel: [ 8.570751] thinkpad_acpi: detected a 8-level brightness capable ThinkPad
Dec 1 09:38:41 tbox kernel: [ 8.611494] Console: switching to colour frame buffer device 175x65
Dec 1 09:38:41 tbox kernel: [ 8.652147] fb0: radeondrmfb frame buffer device
Dec 1 09:38:41 tbox kernel: [ 8.652312] drm: registered panic notifier
Dec 1 09:38:41 tbox kernel: [ 8.652584] [drm] Initialized radeon 2.8.0 20080528 for 0000:01:00.0 on minor 0
Dec 1 09:38:41 tbox kernel: [ 8.692212] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is blocked
Dec 1 09:38:41 tbox kernel: [ 8.693457] Registered led device: tpacpi::thinklight
Dec 1 09:38:41 tbox kernel: [ 8.693513] Registered led device: tpacpi::power
Dec 1 09:38:41 tbox kernel: [ 8.693549] Registered led device: tpacpi::standby
Dec 1 09:38:41 tbox kernel: [ 8.705930] thinkpad_acpi: Console audio control enabled, mode: monitor (read only)
Dec 1 09:38:41 tbox kernel: [ 8.715420] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input8
Dec 1 09:38:41 tbox kernel: [ 8.840657] Intel ICH Modem 0000:00:1f.6: PCI INT B -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
Dec 1 09:38:41 tbox kernel: [ 8.841024] Intel ICH Modem 0000:00:1f.6: setting latency timer to 64
Dec 1 09:38:41 tbox kernel: [ 8.869454] Intel ICH 0000:00:1f.5: PCI INT B -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
Dec 1 09:38:41 tbox kernel: [ 8.869815] Intel ICH 0000:00:1f.5: setting latency timer to 64
Dec 1 09:38:41 tbox kernel: [ 13.350330] IBM TrackPoint firmware: 0x0e, buttons: 3/3
Dec 1 09:38:41 tbox kernel: [ 13.578731] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input9
Dec 1 09:38:41 tbox kernel: [ 13.712041] intel8x0_measure_ac97_clock: measured 52517 usecs (2531 samples)
Dec 1 09:38:41 tbox kernel: [ 13.712307] intel8x0: clocking to 48000
Dec 1 09:38:41 tbox kernel: [ 14.373186] Adding 1052244k swap on /dev/sda2. Priority:-1 extents:1 across:1052244k
Dec 1 09:38:41 tbox kernel: [ 14.377564] EXT4-fs (sda5): re-mounted. Opts: (null)
Dec 1 09:38:41 tbox kernel: [ 14.569039] EXT4-fs (sda5): re-mounted. Opts: (null)
Dec 1 09:38:41 tbox kernel: [ 15.590071] EXT4-fs (sda3): warning: maximal mount count reached, running e2fsck is recommended
Dec 1 09:38:41 tbox kernel: [ 15.590756] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
Dec 1 09:38:41 tbox kernel: [ 16.753896] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 1 09:38:41 tbox kernel: [ 19.335864] fuse init (API version 7.16)
Dec 1 09:38:41 tbox acpid: starting up with netlink and the input layer
Dec 1 09:38:41 tbox acpid: 0 rules loaded
Dec 1 09:38:41 tbox acpid: waiting for events: event logging is off
Dec 1 09:38:42 tbox wpa_supplicant[972]: Trying to associate with 00:04:0e:e4:00:3d (SSID='myCastle-WLAN WPA (Wireless LAN)' freq=2442 MHz)
Dec 1 09:38:42 tbox kernel: [ 21.967986] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
Dec 1 09:38:42 tbox kernel: [ 21.970076] wlan0: authenticated
Dec 1 09:38:42 tbox kernel: [ 21.970094] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
Dec 1 09:38:42 tbox kernel: [ 21.975454] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411 status=0 aid=1)
Dec 1 09:38:42 tbox kernel: [ 21.975458] wlan0: associated
Dec 1 09:38:42 tbox kernel: [ 21.976415] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Dec 1 09:38:42 tbox wpa_supplicant[972]: Associated with 00:04:0e:e4:00:3d
Dec 1 09:38:42 tbox kernel: [ 22.291517] Intel AES-NI instructions are not detected.
Dec 1 09:38:42 tbox kernel: [ 22.357822] padlock: VIA PadLock not detected.
Dec 1 09:38:42 tbox wpa_supplicant[972]: WPA: Key negotiation completed with 00:04:0e:e4:00:3d [PTK=CCMP GTK=CCMP]
Dec 1 09:38:42 tbox wpa_supplicant[972]: CTRL-EVENT-CONNECTED - Connection to 00:04:0e:e4:00:3d completed (auth) [id=0 id_str=]
Dec 1 09:38:44 tbox anacron[1273]: Anacron 2.3 started on 2010-12-01
Dec 1 09:38:44 tbox anacron[1273]: Normal exit (0 jobs run)
Dec 1 09:38:44 tbox bluetoothd[1282]: Bluetooth deamon 4.70
Dec 1 09:38:44 tbox bluetoothd[1282]: Starting SDP server
Dec 1 09:38:44 tbox kernel: [ 24.117982] Bluetooth: Core ver 2.15
Dec 1 09:38:44 tbox kernel: [ 24.130944] NET: Registered protocol family 31
Dec 1 09:38:44 tbox kernel: [ 24.142439] Bluetooth: HCI device and connection manager initialized
Dec 1 09:38:44 tbox kernel: [ 24.153984] Bluetooth: HCI socket layer initialized
Dec 1 09:38:44 tbox kernel: [ 24.192195] Bluetooth: L2CAP ver 2.15
Dec 1 09:38:44 tbox kernel: [ 24.192198] Bluetooth: L2CAP socket layer initialized
Dec 1 09:38:44 tbox bluetoothd[1282]: Starting experimental netlink support
Dec 1 09:38:44 tbox bluetoothd[1282]: Failed to find Bluetooth netlink family
Dec 1 09:38:44 tbox bluetoothd[1282]: Failed to init netlink plugin
Dec 1 09:38:44 tbox kernel: [ 24.414223] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Dec 1 09:38:44 tbox kernel: [ 24.425470] Bluetooth: BNEP filters: protocol multicast
Dec 1 09:38:45 tbox kernel: [ 24.505020] Bluetooth: SCO (Voice Link) ver 0.6
Dec 1 09:38:45 tbox kernel: [ 24.515855] Bluetooth: SCO socket layer initialized
Dec 1 09:38:46 tbox acpid: client connected from 1269[0:0]
Dec 1 09:38:46 tbox acpid: 1 client rule loaded
Dec 1 09:38:46 tbox /usr/sbin/cron[1344]: (CRON) INFO (pidfile fd = 3)
Dec 1 09:38:46 tbox /usr/sbin/cron[1345]: (CRON) STARTUP (fork ok)
Dec 1 09:38:47 tbox /usr/sbin/cron[1345]: (CRON) INFO (Running @reboot jobs)
Dec 1 09:38:47 tbox kernel: [ 26.678982] lp0: using parport0 (interrupt-driven).
Dec 1 09:38:47 tbox kernel: [ 26.803519] ppdev: user-space parallel port driver
Dec 1 09:38:49 tbox /usr/sbin/gpm[1375]: *** info [daemon/startup.c(131)]:
Dec 1 09:38:49 tbox /usr/sbin/gpm[1375]: Started gpm successfully. Entered daemon mode.
Dec 1 09:38:52 tbox kernel: [ 32.126911] P-state transition latency capped at 20 uS
Dec 1 09:38:53 tbox kernel: [ 32.848041] wlan0: no IPv6 routers present
Dec 1 09:38:53 tbox kernel: [ 33.272611] sshd (1486): /proc/1486/oom_adj is deprecated, please use /proc/1486/oom_score_adj instead.
Dec 1 09:38:55 tbox ntpdate[1023]: step time server 192.53.103.108 offset -0.173609 sec
Dec 1 09:38:55 tbox kdm_greet[1395]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: Datei oder Verzeichnis nicht gefunden
Dec 1 09:38:56 tbox wpa_supplicant[972]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Dec 1 09:38:56 tbox kernel: [ 36.320070] ieee80211 phy0: wlan0: No probe response from AP 00:04:0e:e4:00:3d after 500ms, disconnecting.
Dec 1 09:38:56 tbox kernel: [ 36.320961] cfg80211: Calling CRDA to update world regulatory domain
Dec 1 09:39:00 tbox kdm: :0[1383]: pam_sm_authenticate: Called
Dec 1 09:39:00 tbox kdm: :0[1383]: pam_sm_authenticate: username = [sd]
Dec 1 09:39:00 tbox wpa_supplicant[972]: Trying to associate with 00:04:0e:e4:00:3d (SSID='myCastle-WLAN WPA (Wireless LAN)' freq=2442 MHz)
Dec 1 09:39:00 tbox kernel: [ 40.560309] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
Dec 1 09:39:00 tbox kernel: [ 40.562472] wlan0: authenticated
Dec 1 09:39:00 tbox kernel: [ 40.562514] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
Dec 1 09:39:00 tbox wpa_supplicant[972]: Associated with 00:04:0e:e4:00:3d
Dec 1 09:39:00 tbox kernel: [ 40.568705] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411 status=0 aid=1)
Dec 1 09:39:00 tbox kernel: [ 40.568717] wlan0: associated
Dec 1 09:39:01 tbox wpa_supplicant[972]: WPA: Key negotiation completed with 00:04:0e:e4:00:3d [PTK=CCMP GTK=CCMP]
Dec 1 09:39:01 tbox wpa_supplicant[972]: CTRL-EVENT-CONNECTED - Connection to 00:04:0e:e4:00:3d completed (reauth) [id=0 id_str=]
Dec 1 09:39:08 tbox acpid: client connected from 1734[105:112]
Dec 1 09:39:08 tbox acpid: 1 client rule loaded
Dec 1 09:39:09 tbox anacron[1780]: Anacron 2.3 started on 2010-12-01
Dec 1 09:39:09 tbox anacron[1780]: Normal exit (0 jobs run)
Dec 1 09:39:18 tbox wpa_supplicant[972]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Dec 1 09:39:18 tbox kernel: [ 58.320067] ieee80211 phy0: wlan0: No probe response from AP 00:04:0e:e4:00:3d after 500ms, disconnecting.
Dec 1 09:39:18 tbox kernel: [ 58.320478] cfg80211: Calling CRDA to update world regulatory domain
Dec 1 09:39:22 tbox wpa_supplicant[972]: Trying to associate with 00:04:0e:e4:00:3d (SSID='myCastle-WLAN WPA (Wireless LAN)' freq=2442 MHz)
Dec 1 09:39:22 tbox kernel: [ 62.491039] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
Dec 1 09:39:22 tbox kernel: [ 62.493128] wlan0: authenticated
Dec 1 09:39:22 tbox kernel: [ 62.493174] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
Dec 1 09:39:22 tbox kernel: [ 62.498507] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411 status=0 aid=1)
Dec 1 09:39:22 tbox kernel: [ 62.498519] wlan0: associated
Dec 1 09:39:22 tbox wpa_supplicant[972]: Associated with 00:04:0e:e4:00:3d
Dec 1 09:39:23 tbox wpa_supplicant[972]: WPA: Key negotiation completed with 00:04:0e:e4:00:3d [PTK=CCMP GTK=CCMP]
Dec 1 09:39:23 tbox wpa_supplicant[972]: CTRL-EVENT-CONNECTED - Connection to 00:04:0e:e4:00:3d completed (reauth) [id=0 id_str=]
Dec 1 09:39:47 tbox wpa_supplicant[972]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Dec 1 09:39:47 tbox kernel: [ 87.320066] ieee80211 phy0: wlan0: No probe response from AP 00:04:0e:e4:00:3d after 500ms, disconnecting.
Dec 1 09:39:47 tbox kernel: [ 87.320922] cfg80211: Calling CRDA to update world regulatory domain
Dec 1 09:39:51 tbox wpa_supplicant[972]: Trying to associate with 00:04:0e:e4:00:3d (SSID='myCastle-WLAN WPA (Wireless LAN)' freq=2442 MHz)
Dec 1 09:39:51 tbox kernel: [ 91.506684] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
Dec 1 09:39:51 tbox kernel: [ 91.508405] wlan0: authenticated
Dec 1 09:39:51 tbox kernel: [ 91.508451] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
Dec 1 09:39:51 tbox wpa_supplicant[972]: Associated with 00:04:0e:e4:00:3d
Dec 1 09:39:51 tbox kernel: [ 91.513585] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411 status=0 aid=1)
Dec 1 09:39:51 tbox kernel: [ 91.513590] wlan0: associated
Dec 1 09:39:51 tbox wpa_supplicant[972]: WPA: Key negotiation completed with 00:04:0e:e4:00:3d [PTK=CCMP GTK=CCMP]
Dec 1 09:39:51 tbox wpa_supplicant[972]: CTRL-EVENT-CONNECTED - Connection to 00:04:0e:e4:00:3d completed (reauth) [id=0 id_str=]
Dec 1 09:40:05 tbox kernel: [ 105.320063] ieee80211 phy0: wlan0: No probe response from AP 00:04:0e:e4:00:3d after 500ms, disconnecting.
Dec 1 09:40:05 tbox wpa_supplicant[972]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Dec 1 09:40:05 tbox kernel: [ 105.331360] cfg80211: Calling CRDA to update world regulatory domain
Dec 1 09:40:09 tbox wpa_supplicant[972]: Trying to associate with 00:04:0e:e4:00:3d (SSID='myCastle-WLAN WPA (Wireless LAN)' freq=2442 MHz)
Dec 1 09:40:09 tbox kernel: [ 109.499103] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
Dec 1 09:40:09 tbox kernel: [ 109.501201] wlan0: authenticated
Dec 1 09:40:09 tbox kernel: [ 109.501245] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
Dec 1 09:40:09 tbox kernel: [ 109.506179] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411 status=0 aid=1)
Dec 1 09:40:09 tbox kernel: [ 109.506190] wlan0: associated
Dec 1 09:40:09 tbox wpa_supplicant[972]: Associated with 00:04:0e:e4:00:3d
Dec 1 09:40:09 tbox wpa_supplicant[972]: WPA: Key negotiation completed with 00:04:0e:e4:00:3d [PTK=CCMP GTK=CCMP]
Dec 1 09:40:09 tbox wpa_supplicant[972]: CTRL-EVENT-CONNECTED - Connection to 00:04:0e:e4:00:3d completed (reauth) [id=0 id_str=]
Dec 1 09:40:36 tbox wpa_supplicant[972]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Dec 1 09:40:36 tbox kernel: [ 136.320066] ieee80211 phy0: wlan0: No probe response from AP 00:04:0e:e4:00:3d after 500ms, disconnecting.
Dec 1 09:40:36 tbox kernel: [ 136.320918] cfg80211: Calling CRDA to update world regulatory domain
Dec 1 09:40:40 tbox wpa_supplicant[972]: Trying to associate with 00:04:0e:e4:00:3d (SSID='myCastle-WLAN WPA (Wireless LAN)' freq=2442 MHz)
Dec 1 09:40:40 tbox kernel: [ 140.492586] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
Dec 1 09:40:40 tbox kernel: [ 140.494687] wlan0: authenticated
Dec 1 09:40:40 tbox kernel: [ 140.494734] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
Dec 1 09:40:40 tbox kernel: [ 140.499939] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411 status=0 aid=1)
Dec 1 09:40:40 tbox kernel: [ 140.499952] wlan0: associated
Dec 1 09:40:40 tbox wpa_supplicant[972]: Associated with 00:04:0e:e4:00:3d
Dec 1 09:40:40 tbox wpa_supplicant[972]: WPA: Key negotiation completed with 00:04:0e:e4:00:3d [PTK=CCMP GTK=CCMP]
Dec 1 09:40:40 tbox wpa_supplicant[972]: CTRL-EVENT-CONNECTED - Connection to 00:04:0e:e4:00:3d completed (reauth) [id=0 id_str=]
Dec 1 09:40:54 tbox wpa_supplicant[972]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Dec 1 09:40:54 tbox kernel: [ 154.320080] ieee80211 phy0: wlan0: No probe response from AP 00:04:0e:e4:00:3d after 500ms, disconnecting.
Dec 1 09:40:54 tbox kernel: [ 154.321003] cfg80211: Calling CRDA to update world regulatory domain
Dec 1 09:40:58 tbox wpa_supplicant[972]: Trying to associate with 00:04:0e:e4:00:3d (SSID='myCastle-WLAN WPA (Wireless LAN)' freq=2442 MHz)
Dec 1 09:40:58 tbox kernel: [ 158.491230] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
Dec 1 09:40:58 tbox kernel: [ 158.493360] wlan0: authenticated
Dec 1 09:40:58 tbox kernel: [ 158.493405] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
Dec 1 09:40:58 tbox kernel: [ 158.498113] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411 status=0 aid=1)
Dec 1 09:40:58 tbox kernel: [ 158.498126] wlan0: associated
Dec 1 09:40:58 tbox wpa_supplicant[972]: Associated with 00:04:0e:e4:00:3d
Dec 1 09:40:58 tbox wpa_supplicant[972]: WPA: Key negotiation completed with 00:04:0e:e4:00:3d [PTK=CCMP GTK=CCMP]
Dec 1 09:40:58 tbox wpa_supplicant[972]: CTRL-EVENT-CONNECTED - Connection to 00:04:0e:e4:00:3d completed (reauth) [id=0 id_str=]
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-01 10:56 ` Sedat Dilek
@ 2010-12-01 11:21 ` Sedat Dilek
0 siblings, 0 replies; 22+ messages in thread
From: Sedat Dilek @ 2010-12-01 11:21 UTC (permalink / raw)
To: Bruno Randolf; +Cc: wireless, John Linville, Nick Kossifidis, Stephen Rothwell
On Wed, Dec 1, 2010 at 11:56 AM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> On Wed, Dec 1, 2010 at 11:21 AM, Bruno Randolf <br1@einfach.org> wrote:
>> On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
>>> Hi,
>>>
>>> I have built today a linux-next (next-20101201) kernel which includes
>>> wireless-next-2.6 up to master-2010-11-30.
[ ... ]
>>> Unfortunately, my wlan network connection is totally unstable.
[ ... ]
>>> The block looks like this:
>>> [ 4436.504059] ieee80211 phy0: wlan0: No probe response from AP
>>> 00:04:0e:e4:00:3d after 500ms, disconnecting.
>>> [ 4436.504490] cfg80211: Calling CRDA to update world regulatory domain
>>> [ 4440.677020] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
>>> [ 4440.679096] wlan0: authenticated
>>> [ 4440.679158] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
>>> [ 4440.684667] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411
>>> status=0 aid=1)
>>> [ 4440.684673] wlan0: associated
>>>
>>> My wlan device is an ath5k:
>>>
>>> $ lspci -nnvv | grep "Ethernet controller" | grep -i ath
>>> 02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212
>>> 802.11abg NIC [168c:1014] (rev 01)
[ ...]
>> 1.) For identification of the chipset, please:
>> dmesg |grep "ath5.*chip"
# grep "Dec 1 09:38" /var/log/syslog | grep "ath5.*chip"
Dec 1 09:38:40 tbox kernel: [ 8.233119] ath5k phy0: Atheros AR5212
chip found (MAC: 0x56, PHY: 0x41)
>> 2.) Is there a problem when you don't use encryption?
How do I setup "dont-use-encryption"? Hardware-/Software-encyrption?
For ath5k? Change WLAN setup (in router-config)?
>> 3.) git bisect might help track it down.
Hunting another bug ATM...
Rebuilding right now with ath* debug options (might take a while).
- Sedat -
>
> When does it happen?
> Normal daily usage of Internet-ing... + kernel build with -j5
> (Pentium-M, 1G RAM)...
>
> I have set now as extra (just rebuilding):
> CONFIG_ATH_DEBUG=y
> CONFIG_ATH5K_DEBUG=y
>
> # egrep 'Dec 1 09:38' /var/log/syslog | egrep -i 'ath|80211|wlan'
> Dec 1 09:38:40 tbox kernel: [ 6.919633] cfg80211: Calling CRDA to
> update world regulatory domain
> Dec 1 09:38:40 tbox kernel: [ 7.401522] ath5k 0000:02:02.0: PCI
> INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
> Dec 1 09:38:40 tbox kernel: [ 7.401677] ath5k 0000:02:02.0:
> registered as 'phy0'
> Dec 1 09:38:40 tbox kernel: [ 7.689793] ath: EEPROM regdomain: 0x61
> Dec 1 09:38:40 tbox kernel: [ 7.689797] ath: EEPROM indicates we
> should expect a direct regpair map
> Dec 1 09:38:40 tbox kernel: [ 7.689803] ath: Country alpha2 being used: 00
> Dec 1 09:38:40 tbox kernel: [ 7.689805] ath: Regpair used: 0x61
> Dec 1 09:38:40 tbox kernel: [ 8.232093] ieee80211 phy0: Selected
> rate control algorithm 'minstrel_ht'
> Dec 1 09:38:40 tbox kernel: [ 8.233067] Registered led device:
> ath5k-phy0::rx
> Dec 1 09:38:40 tbox kernel: [ 8.233106] Registered led device:
> ath5k-phy0::tx
> Dec 1 09:38:40 tbox kernel: [ 8.233119] ath5k phy0: Atheros AR5212
> chip found (MAC: 0x56, PHY: 0x41)
> Dec 1 09:38:40 tbox kernel: [ 8.233165] ath5k phy0: RF5111 5GHz
> radio found (0x17)
> Dec 1 09:38:40 tbox kernel: [ 8.233202] ath5k phy0: RF2111 2GHz
> radio found (0x23)
> Dec 1 09:38:41 tbox kernel: [ 16.753896] ADDRCONF(NETDEV_UP):
> wlan0: link is not ready
> Dec 1 09:38:42 tbox wpa_supplicant[972]: Trying to associate with
> 00:04:0e:e4:00:3d (SSID='myCastle-WLAN WPA (Wireless LAN)' freq=2442
> MHz)
> Dec 1 09:38:42 tbox kernel: [ 21.967986] wlan0: authenticate with
> 00:04:0e:e4:00:3d (try 1)
> Dec 1 09:38:42 tbox kernel: [ 21.970076] wlan0: authenticated
> Dec 1 09:38:42 tbox kernel: [ 21.970094] wlan0: associate with
> 00:04:0e:e4:00:3d (try 1)
> Dec 1 09:38:42 tbox kernel: [ 21.975454] wlan0: RX AssocResp from
> 00:04:0e:e4:00:3d (capab=0x411 status=0 aid=1)
> Dec 1 09:38:42 tbox kernel: [ 21.975458] wlan0: associated
> Dec 1 09:38:42 tbox kernel: [ 21.976415] ADDRCONF(NETDEV_CHANGE):
> wlan0: link becomes ready
> Dec 1 09:38:53 tbox kernel: [ 32.848041] wlan0: no IPv6 routers present
> Dec 1 09:38:56 tbox kernel: [ 36.320070] ieee80211 phy0: wlan0: No
> probe response from AP 00:04:0e:e4:00:3d after 500ms, disconnecting.
> Dec 1 09:38:56 tbox kernel: [ 36.320961] cfg80211: Calling CRDA to
> update world regulatory domain
>
> Full syslog attached.
>
> - Sedat -
>
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-01 10:21 ` Bruno Randolf
2010-12-01 10:56 ` Sedat Dilek
@ 2010-12-01 21:04 ` Sedat Dilek
2010-12-02 17:33 ` Sedat Dilek
2 siblings, 0 replies; 22+ messages in thread
From: Sedat Dilek @ 2010-12-01 21:04 UTC (permalink / raw)
To: Bruno Randolf; +Cc: wireless, John Linville, Nick Kossifidis, Stephen Rothwell
[-- Attachment #1: Type: text/plain, Size: 2601 bytes --]
On Wed, Dec 1, 2010 at 11:21 AM, Bruno Randolf <br1@einfach.org> wrote:
> On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
>> Hi,
>>
>> I have built today a linux-next (next-20101201) kernel which includes
>> wireless-next-2.6 up to master-2010-11-30.
>>
>> >From tig utility:
>> 2010-11-30 15:33 Stanislaw Gruszka [wireless-next-2.6] iwlagn: fix
>> microcode error on 4965
>> [main] 61790c5f3c5f158821821a00797d94504531839f - commit 1929 of 226338
>> (0%)
>>
>> Unfortunately, my wlan network connection is totally unstable.
>>
>> $ dmesg | grep "RX AssocResp" | wc -l
>> 216
>>
>> The block looks like this:
>> [ 4436.504059] ieee80211 phy0: wlan0: No probe response from AP
>> 00:04:0e:e4:00:3d after 500ms, disconnecting.
>> [ 4436.504490] cfg80211: Calling CRDA to update world regulatory domain
>> [ 4440.677020] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
>> [ 4440.679096] wlan0: authenticated
>> [ 4440.679158] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
>> [ 4440.684667] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411
>> status=0 aid=1)
>> [ 4440.684673] wlan0: associated
>>
>> My wlan device is an ath5k:
>>
>> $ lspci -nnvv | grep "Ethernet controller" | grep -i ath
>> 02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212
>> 802.11abg NIC [168c:1014] (rev 01)
>>
>> Any idea what's wrong? (Just speculating on the last patch-set from
>> Nick...) How can I help to dig into this problem?
>> Debug-session with wpasupplicant? Which kernel-parameters (debug) to
>> be considered/set?
>
> 1.) For identification of the chipset, please:
> dmesg |grep "ath5.*chip"
>
> 2.) Is there a problem when you don't use encryption?
>
> 3.) git bisect might help track it down.
>
> bruno
>
Now, I have a debug-session via:
# modprobe -v ath5k debug=0xffffffff
Looks like I am using AES encryption here:
# lsmod | egrep -i 'ath|80211|aes'
aes_i586 6856 2
aes_generic 25758 1 aes_i586
ath5k 137422 0
ath 10977 1 ath5k
mac80211 150863 1 ath5k
cfg80211 97248 3 ath5k,ath,mac80211
rfkill 10754 4 bluetooth,thinkpad_acpi,cfg80211
Here the status via wpa_cli:
# wpa_cli status -i wlan0
bssid=00:04:0e:e4:00:3d
ssid=myCastle-WLAN WPA (Wireless LAN)
id=0
pairwise_cipher=CCMP
group_cipher=CCMP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED
ip_address=192.168.178.25
Hope the (filtered log helps)... I have more but it's 600KiB (xz-compressed).
Please, let me know.
- Sedat -
[-- Attachment #2: lsmod.txt --]
[-- Type: text/plain, Size: 347 bytes --]
# lsmod | egrep -i 'ath|80211|aes' > lsmod.txt
aes_i586 6856 2
aes_generic 25758 1 aes_i586
ath5k 137422 0
ath 10977 1 ath5k
mac80211 150863 1 ath5k
cfg80211 97248 3 ath5k,ath,mac80211
rfkill 10754 4 bluetooth,thinkpad_acpi,cfg80211
[-- Attachment #3: debug-session_ath5k_filtered.txt.xz --]
[-- Type: application/octet-stream, Size: 70504 bytes --]
[-- Attachment #4: debug-session_ath5k_filtered.txt.xz.sha256sum --]
[-- Type: application/octet-stream, Size: 102 bytes --]
ad900388ee59bed20dd5191beaa6727d774f3f521742d3794b8a2a9b7b46102b debug-session_ath5k_filtered.txt.xz
[-- Attachment #5: modprobe_ath5k-debug.sh --]
[-- Type: application/x-sh, Size: 153 bytes --]
[-- Attachment #6: lspci-nnvv.txt --]
[-- Type: text/plain, Size: 12259 bytes --]
00:00.0 Host bridge [0600]: Intel Corporation 82855PM Processor to I/O Controller [8086:3340] (rev 03)
Subsystem: IBM Thinkpad T40 series [1014:0529]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 0
Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M]
Capabilities: [e4] Vendor Specific Information: Len=04 <?>
Capabilities: [a0] AGP version 2.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x4
Kernel driver in use: agpgart-intel
00:01.0 PCI bridge [0604]: Intel Corporation 82855PM Processor to AGP Controller [8086:3341] (rev 03) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 96
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: 00003000-00003fff
Memory behind bridge: c0100000-c01fffff
Prefetchable memory behind bridge: e0000000-e7ffffff
Secondary status: 66MHz+ FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
00:1d.0 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 01) (prog-if 00 [UHCI])
Subsystem: IBM ThinkPad [1014:052d]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 11
Region 4: I/O ports at 1800 [size=32]
Kernel driver in use: uhci_hcd
00:1d.1 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 01) (prog-if 00 [UHCI])
Subsystem: IBM ThinkPad [1014:052d]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 11
Region 4: I/O ports at 1820 [size=32]
Kernel driver in use: uhci_hcd
00:1d.2 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 01) (prog-if 00 [UHCI])
Subsystem: IBM ThinkPad [1014:052d]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin C routed to IRQ 11
Region 4: I/O ports at 1840 [size=32]
Kernel driver in use: uhci_hcd
00:1d.7 USB Controller [0c03]: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 01) (prog-if 20 [EHCI])
Subsystem: IBM ThinkPad [1014:052e]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin D routed to IRQ 11
Region 0: Memory at c0000000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Debug port: BAR=1 offset=0080
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 81) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR+ INTx-
Latency: 0
Bus: primary=00, secondary=02, subordinate=08, sec-latency=168
I/O behind bridge: 00004000-00008fff
Memory behind bridge: c0200000-cfffffff
Prefetchable memory behind bridge: e8000000-efffffff
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat+ DiscTmrSERREn-
00:1f.0 ISA bridge [0601]: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge [8086:24cc] (rev 01)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
00:1f.1 IDE interface [0101]: Intel Corporation 82801DBM (ICH4-M) IDE Controller [8086:24ca] (rev 01) (prog-if 8a [Master SecP PriP])
Subsystem: IBM ThinkPad [1014:052d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at 01f0 [size=8]
Region 1: I/O ports at 03f4 [size=1]
Region 2: I/O ports at 0170 [size=8]
Region 3: I/O ports at 0374 [size=1]
Region 4: I/O ports at 1860 [size=16]
Region 5: Memory at ff7ffc00 (32-bit, non-prefetchable) [size=1K]
Kernel driver in use: ata_piix
00:1f.3 SMBus [0c05]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller [8086:24c3] (rev 01)
Subsystem: IBM ThinkPad [1014:052d]
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin B routed to IRQ 11
Region 4: I/O ports at 1880 [size=32]
Kernel driver in use: i801_smbus
00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 01)
Subsystem: IBM ThinkPad T41 [1014:0537]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 11
Region 0: I/O ports at 1c00 [size=256]
Region 1: I/O ports at 18c0 [size=64]
Region 2: Memory at c0000c00 (32-bit, non-prefetchable) [size=512]
Region 3: Memory at c0000800 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: Intel ICH
00:1f.6 Modem [0703]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller [8086:24c6] (rev 01) (prog-if 00 [Generic])
Subsystem: IBM ThinkPad [1014:0525]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 11
Region 0: I/O ports at 2400 [size=256]
Region 1: I/O ports at 2000 [size=128]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: Intel ICH Modem
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] [1002:4c66] (rev 02) (prog-if 00 [VGA controller])
Subsystem: IBM ThinkPad T41 [1014:054d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR+ FastB2B+ DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 66 (2000ns min), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
Region 1: I/O ports at 3000 [size=256]
Region 2: Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
[virtual] Expansion ROM at c01e0000 [disabled] [size=128K]
Capabilities: [58] AGP version 2.0
Status: RQ=48 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x4
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: radeon
02:00.0 CardBus bridge [0607]: Texas Instruments PCI1520 PC card Cardbus Controller [104c:ac55] (rev 01)
Subsystem: IBM ThinkPad T30/T40 [1014:0512]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 168, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at b0000000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=02, secondary=03, subordinate=06, sec-latency=176
Memory window 0: ec000000-effff000 (prefetchable)
Memory window 1: cc000000-cffff000
I/O window 0: 00008c00-00008cff
I/O window 1: 00008800-000088ff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
16-bit legacy interface ports at 0001
Kernel driver in use: yenta_cardbus
02:00.1 CardBus bridge [0607]: Texas Instruments PCI1520 PC card Cardbus Controller [104c:ac55] (rev 01)
Subsystem: IBM ThinkPad T30/T40 [1014:0512]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 168, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 11
Region 0: Memory at b1000000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=02, secondary=07, subordinate=07, sec-latency=176
Memory window 0: e8000000-ebfff000 (prefetchable)
Memory window 1: c8000000-cbfff000
I/O window 0: 00008400-000084ff
I/O window 1: 00007c00-00007cff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
16-bit legacy interface ports at 0001
Kernel driver in use: yenta_cardbus
02:01.0 Ethernet controller [0200]: Intel Corporation 82540EP Gigabit Ethernet Controller (Mobile) [8086:101e] (rev 03)
Subsystem: IBM Thinkpad [1014:0549]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (63750ns min), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at c0220000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at c0200000 (32-bit, non-prefetchable) [size=64K]
Region 2: I/O ports at 8000 [size=64]
[virtual] Expansion ROM at c7ff0000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [f0] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Kernel driver in use: e1000
02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212 802.11abg NIC [168c:1014] (rev 01)
Subsystem: Phillips Components Device [17ab:8331]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 168 (2500ns min, 7000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at c0210000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=2 PME-
Kernel driver in use: ath5k
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-01 10:09 [linux-next] next-20101201: ath5k permanently disconnecting Sedat Dilek
2010-12-01 10:21 ` Bruno Randolf
@ 2010-12-01 22:05 ` Nick Kossifidis
2010-12-01 23:08 ` Sedat Dilek
2010-12-01 23:26 ` Sedat Dilek
2010-12-02 12:17 ` Sedat Dilek
2 siblings, 2 replies; 22+ messages in thread
From: Nick Kossifidis @ 2010-12-01 22:05 UTC (permalink / raw)
To: sedat.dilek; +Cc: wireless, John Linville, Stephen Rothwell
2010/12/1 Sedat Dilek <sedat.dilek@googlemail.com>:
> Hi,
>
> I have built today a linux-next (next-20101201) kernel which includes
> wireless-next-2.6 up to master-2010-11-30.
>
> From tig utility:
> 2010-11-30 15:33 Stanislaw Gruszka [wireless-next-2.6] iwlagn: fix
> microcode error on 4965
> [main] 61790c5f3c5f158821821a00797d94504531839f - commit 1929 of 226338 (0%)
>
> Unfortunately, my wlan network connection is totally unstable.
>
> $ dmesg | grep "RX AssocResp" | wc -l
> 216
>
> The block looks like this:
> [ 4436.504059] ieee80211 phy0: wlan0: No probe response from AP
> 00:04:0e:e4:00:3d after 500ms, disconnecting.
> [ 4436.504490] cfg80211: Calling CRDA to update world regulatory domain
> [ 4440.677020] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
> [ 4440.679096] wlan0: authenticated
> [ 4440.679158] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
> [ 4440.684667] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411
> status=0 aid=1)
> [ 4440.684673] wlan0: associated
>
> My wlan device is an ath5k:
>
> $ lspci -nnvv | grep "Ethernet controller" | grep -i ath
> 02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212
> 802.11abg NIC [168c:1014] (rev 01)
>
> Any idea what's wrong? (Just speculating on the last patch-set from Nick...)
> How can I help to dig into this problem?
> Debug-session with wpasupplicant? Which kernel-parameters (debug) to
> be considered/set?
>
> Kind Regards,
> - Sedat -
>
That's weird I tested all patches for connectivity + iperf, maybe
something else also went on the tree that results such behavior...
1) Are you using NetworkManager ? If so disable it and connect manually.
2) Can you disable encryption on your AP and see if it works without it ?
3) Try and enable/disable hw encryption with nohwcrypt module parameter.
4) What's your signal strength/rate when you connect to the AP ?
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-01 22:05 ` Nick Kossifidis
@ 2010-12-01 23:08 ` Sedat Dilek
2010-12-01 23:26 ` Sedat Dilek
1 sibling, 0 replies; 22+ messages in thread
From: Sedat Dilek @ 2010-12-01 23:08 UTC (permalink / raw)
To: Nick Kossifidis; +Cc: wireless, John Linville, Stephen Rothwell
On Wed, Dec 1, 2010 at 11:05 PM, Nick Kossifidis <mickflemm@gmail.com> wrote:
> 2010/12/1 Sedat Dilek <sedat.dilek@googlemail.com>:
>> Hi,
>>
>> I have built today a linux-next (next-20101201) kernel which includes
>> wireless-next-2.6 up to master-2010-11-30.
>>
>> From tig utility:
>> 2010-11-30 15:33 Stanislaw Gruszka [wireless-next-2.6] iwlagn: fix
>> microcode error on 4965
>> [main] 61790c5f3c5f158821821a00797d94504531839f - commit 1929 of 226338 (0%)
>>
>> Unfortunately, my wlan network connection is totally unstable.
>>
>> $ dmesg | grep "RX AssocResp" | wc -l
>> 216
>>
>> The block looks like this:
>> [ 4436.504059] ieee80211 phy0: wlan0: No probe response from AP
>> 00:04:0e:e4:00:3d after 500ms, disconnecting.
>> [ 4436.504490] cfg80211: Calling CRDA to update world regulatory domain
>> [ 4440.677020] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
>> [ 4440.679096] wlan0: authenticated
>> [ 4440.679158] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
>> [ 4440.684667] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411
>> status=0 aid=1)
>> [ 4440.684673] wlan0: associated
>>
>> My wlan device is an ath5k:
>>
>> $ lspci -nnvv | grep "Ethernet controller" | grep -i ath
>> 02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212
>> 802.11abg NIC [168c:1014] (rev 01)
>>
>> Any idea what's wrong? (Just speculating on the last patch-set from Nick...)
>> How can I help to dig into this problem?
>> Debug-session with wpasupplicant? Which kernel-parameters (debug) to
>> be considered/set?
>>
>> Kind Regards,
>> - Sedat -
>>
>
> That's weird I tested all patches for connectivity + iperf, maybe
> something else also went on the tree that results such behavior...
>
> 1) Are you using NetworkManager ? If so disable it and connect manually.
No NM here, using "classic" /etc/network/interfaces with IP-static setup.
[ /etc/network/interfaces ]
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The wireless LAN interface
auto wlan0
iface wlan0 inet static
address 192.168.178.25
netmask 255.255.255.0
broadcast 192.168.178.255
gateway 192.168.178.1
dns-nameservers 192.168.178.1 208.67.222.222 208.67.220.220
wpa-ssid myCastle-WLAN WPA (Wireless LAN)
wpa-psk mySecretPWD
- EOF -
> 2) Can you disable encryption on your AP and see if it works without it ?
[ /etc/network/interfaces ]
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The wireless LAN interface
allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-key-mgmt NONE
wpa-ssid myCastle-WLAN WPA (Wireless LAN)
- EOF -
Router "open" and ath5k "normal":
Dec 1 23:49:26 tbox kernel: [ 8192.504060] ieee80211 phy0: wlan0: No
probe response from AP 00:04:0e:e4:00:3d after 500ms, disconnecting.
Dec 1 23:49:26 tbox wpa_supplicant[5472]: CTRL-EVENT-DISCONNECTED -
Disconnect event - remove keys
Dec 1 23:49:26 tbox kernel: [ 8192.517097] cfg80211: Calling CRDA to
update world regulatory domain
Dec 1 23:49:31 tbox wpa_supplicant[5472]: Trying to associate with
00:04:0e:e4:00:3d (SSID='myCastle-WLAN WPA (Wireless LAN)' freq=2442
MHz)
Dec 1 23:49:31 tbox kernel: [ 8196.683802] wlan0: authenticate with
00:04:0e:e4:00:3d (try 1)
Dec 1 23:49:31 tbox kernel: [ 8196.686256] wlan0: authenticated
Dec 1 23:49:31 tbox kernel: [ 8196.686302] wlan0: associate with
00:04:0e:e4:00:3d (try 1)
Dec 1 23:49:31 tbox kernel: [ 8196.688608] wlan0: RX AssocResp from
00:04:0e:e4:00:3d (capab=0x401 status=0 aid=1)
Dec 1 23:49:31 tbox kernel: [ 8196.688620] wlan0: associated
Dec 1 23:49:31 tbox wpa_supplicant[5472]: Associated with 00:04:0e:e4:00:3d
Dec 1 23:49:31 tbox wpa_supplicant[5472]: CTRL-EVENT-CONNECTED -
Connection to 00:04:0e:e4:00:3d completed (reauth) [id=0 id_str=]
Router "open" ath5k with nohwcrypt=1:
Dec 1 23:51:20 tbox kernel: [ 8306.504080] ieee80211 phy0: wlan0: No
probe response from AP 00:04:0e:e4:00:3d after 500ms, disconnecting.
Dec 1 23:51:20 tbox kernel: [ 8306.504968] cfg80211: Calling CRDA to
update world regulatory domain
Dec 1 23:51:22 tbox ntpdate[5739]: adjust time server 192.53.103.108
offset 0.001238 sec
Dec 1 23:51:25 tbox wpa_supplicant[5677]: Trying to associate with
00:04:0e:e4:00:3d (SSID='myCastle-WLAN WPA (Wireless LAN)' freq=2442
MHz)
Dec 1 23:51:25 tbox kernel: [ 8310.755922] wlan0: authenticate with
00:04:0e:e4:00:3d (try 1)
Dec 1 23:51:25 tbox kernel: [ 8310.758023] wlan0: authenticated
Dec 1 23:51:25 tbox kernel: [ 8310.758103] wlan0: associate with
00:04:0e:e4:00:3d (try 1)
Dec 1 23:51:25 tbox kernel: [ 8310.760738] wlan0: RX AssocResp from
00:04:0e:e4:00:3d (capab=0x401 status=0 aid=1)
Dec 1 23:51:25 tbox kernel: [ 8310.760750] wlan0: associated
Dec 1 23:51:25 tbox wpa_supplicant[5677]: Associated with 00:04:0e:e4:00:3d
Dec 1 23:51:25 tbox wpa_supplicant[5677]: CTRL-EVENT-CONNECTED -
Connection to 00:04:0e:e4:00:3d completed (reauth) [id=0 id_str=]
> 3) Try and enable/disable hw encryption with nohwcrypt module parameter.
# modinfo ath5k | grep nohwcrypt
parm: nohwcrypt:Disable hardware encryption. (bool)
# modprobe -v ath5k nohwcrypt=1
# lsmod | egrep -i 'ath|80211|aes'
ath5k 137422 0
ath 10977 1 ath5k
mac80211 150863 1 ath5k
cfg80211 97248 3 ath5k,ath,mac80211
aes_i586 6856 0
aes_generic 25758 1 aes_i586
rfkill 10754 4 cfg80211,bluetooth,thinkpad_acpi
Same error-messages AFAICS:
Dec 1 23:22:27 tbox kernel: [ 6573.500056] ieee80211 phy0: wlan0: No
probe response from AP 00:04:0e:e4:00:3d after 500ms, disconnecting.
Dec 1 23:22:27 tbox kernel: [ 6573.500541] cfg80211: Calling CRDA to
update world regulatory domain
Dec 1 23:22:32 tbox wpa_supplicant[3372]: Trying to associate with
00:04:0e:e4:00:3d (SSID='myCastle-WLAN WPA (Wireless LAN)' freq=2442
MHz)
Dec 1 23:22:32 tbox kernel: [ 6577.739895] wlan0: authenticate with
00:04:0e:e4:00:3d (try 1)
Dec 1 23:22:32 tbox kernel: [ 6577.741981] wlan0: authenticated
Dec 1 23:22:32 tbox kernel: [ 6577.742028] wlan0: associate with
00:04:0e:e4:00:3d (try 1)
Dec 1 23:22:32 tbox kernel: [ 6577.747151] wlan0: RX AssocResp from
00:04:0e:e4:00:3d (capab=0x411 status=0 aid=1)
Dec 1 23:22:32 tbox kernel: [ 6577.747163] wlan0: associated
Dec 1 23:22:32 tbox wpa_supplicant[3372]: Associated with 00:04:0e:e4:00:3d
Dec 1 23:22:33 tbox wpa_supplicant[3372]: WPA: Key negotiation
completed with 00:04:0e:e4:00:3d [PTK=CCMP GTK=CCMP]
Dec 1 23:22:33 tbox wpa_supplicant[3372]: CTRL-EVENT-CONNECTED -
Connection to 00:04:0e:e4:00:3d completed (reauth) [id=0 id_str=]
> 4) What's your signal strength/rate when you connect to the AP ?
[1] ath5k with nohwcrypt=1 (mostly 1MBps @ -55dBm)
# iw dev wlan0 station dump
Station 00:04:0e:e4:00:3d (on wlan0)
inactive time: 1876 ms
rx bytes: 28313
rx packets: 341
tx bytes: 4629
tx packets: 29
signal: -66 dBm
tx bitrate: 1.0 MBit/s
# iw dev wlan0 station dump
Station 00:04:0e:e4:00:3d (on wlan0)
inactive time: 708 ms
rx bytes: 26476
rx packets: 334
tx bytes: 2835
tx packets: 10
signal: -66 dBm
tx bitrate: 48.0 MBit/s
[2] ath5k (with no modules options):
# iw dev wlan0 station dump
Station 00:04:0e:e4:00:3d (on wlan0)
inactive time: 32 ms
rx bytes: 17987
rx packets: 197
tx bytes: 15193
tx packets: 56
signal: -64 dBm
tx bitrate: 18.0 MBit/s
- Sedat -
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-01 22:05 ` Nick Kossifidis
2010-12-01 23:08 ` Sedat Dilek
@ 2010-12-01 23:26 ` Sedat Dilek
1 sibling, 0 replies; 22+ messages in thread
From: Sedat Dilek @ 2010-12-01 23:26 UTC (permalink / raw)
To: Nick Kossifidis; +Cc: wireless, John Linville, Stephen Rothwell
On Wed, Dec 1, 2010 at 11:05 PM, Nick Kossifidis <mickflemm@gmail.com> wrote:
> 2010/12/1 Sedat Dilek <sedat.dilek@googlemail.com>:
>> Hi,
>>
>> I have built today a linux-next (next-20101201) kernel which includes
>> wireless-next-2.6 up to master-2010-11-30.
>>
>> From tig utility:
>> 2010-11-30 15:33 Stanislaw Gruszka [wireless-next-2.6] iwlagn: fix
>> microcode error on 4965
>> [main] 61790c5f3c5f158821821a00797d94504531839f - commit 1929 of 226338 (0%)
>>
>> Unfortunately, my wlan network connection is totally unstable.
>>
>> $ dmesg | grep "RX AssocResp" | wc -l
>> 216
>>
>> The block looks like this:
>> [ 4436.504059] ieee80211 phy0: wlan0: No probe response from AP
>> 00:04:0e:e4:00:3d after 500ms, disconnecting.
>> [ 4436.504490] cfg80211: Calling CRDA to update world regulatory domain
>> [ 4440.677020] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
>> [ 4440.679096] wlan0: authenticated
>> [ 4440.679158] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
>> [ 4440.684667] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411
>> status=0 aid=1)
>> [ 4440.684673] wlan0: associated
>>
>> My wlan device is an ath5k:
>>
>> $ lspci -nnvv | grep "Ethernet controller" | grep -i ath
>> 02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212
>> 802.11abg NIC [168c:1014] (rev 01)
>>
>> Any idea what's wrong? (Just speculating on the last patch-set from Nick...)
>> How can I help to dig into this problem?
>> Debug-session with wpasupplicant? Which kernel-parameters (debug) to
>> be considered/set?
>>
>> Kind Regards,
>> - Sedat -
>>
>
> That's weird I tested all patches for connectivity + iperf, maybe
> something else also went on the tree that results such behavior...
>
> 1) Are you using NetworkManager ? If so disable it and connect manually.
> 2) Can you disable encryption on your AP and see if it works without it ?
> 3) Try and enable/disable hw encryption with nohwcrypt module parameter.
> 4) What's your signal strength/rate when you connect to the AP ?
>
> --
> GPG ID: 0xD21DB2DB
> As you read this post global entropy rises. Have Fun ;-)
> Nick
>
Tested my usual ath5k setup also with a self-debianized wpasupplicant
0.7.3 (build against libnl-2.0):
# dpkg -l | grep wpa | cut -c-80
ii wpagui 0.7.3-1~dileks.1
ii wpasupplicant 0.7.3-1~dileks.1
Same error-messages:
Dec 2 00:24:53 tbox kernel: [10319.504083] ieee80211 phy0: wlan0: No
probe response from AP 00:04:0e:e4:00:3d after 500ms, disconnecting.
Dec 2 00:24:53 tbox kernel: [10319.504946] cfg80211: Calling CRDA to
update world regulatory domain
Dec 2 00:24:58 tbox wpa_supplicant[6955]: Trying to associate with
00:04:0e:e4:00:3d (SSID='myCastle-WLAN WPA (Wireless LAN)' freq=2442
MHz)
Dec 2 00:24:58 tbox kernel: [10323.677183] wlan0: authenticate with
00:04:0e:e4:00:3d (try 1)
Dec 2 00:24:58 tbox kernel: [10323.680850] wlan0: authenticated
Dec 2 00:24:58 tbox kernel: [10323.680907] wlan0: associate with
00:04:0e:e4:00:3d (try 1)
Dec 2 00:24:58 tbox kernel: [10323.687204] wlan0: RX AssocResp from
00:04:0e:e4:00:3d (capab=0x411 status=0 aid=1)
Dec 2 00:24:58 tbox kernel: [10323.687215] wlan0: associated
Dec 2 00:24:58 tbox wpa_supplicant[6955]: Associated with 00:04:0e:e4:00:3d
Dec 2 00:24:58 tbox wpa_supplicant[6955]: WPA: Key negotiation
completed with 00:04:0e:e4:00:3d [PTK=CCMP GTK=TKIP]
Dec 2 00:24:58 tbox wpa_supplicant[6955]: CTRL-EVENT-CONNECTED -
Connection to 00:04:0e:e4:00:3d completed (reauth) [id=0 id_str=]
- Sedat -
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-01 10:09 [linux-next] next-20101201: ath5k permanently disconnecting Sedat Dilek
2010-12-01 10:21 ` Bruno Randolf
2010-12-01 22:05 ` Nick Kossifidis
@ 2010-12-02 12:17 ` Sedat Dilek
2010-12-02 13:40 ` Sedat Dilek
2 siblings, 1 reply; 22+ messages in thread
From: Sedat Dilek @ 2010-12-02 12:17 UTC (permalink / raw)
To: wireless; +Cc: John Linville, Nick Kossifidis, Stephen Rothwell, Bruno Randolf
On Wed, Dec 1, 2010 at 11:09 AM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> Hi,
>
> I have built today a linux-next (next-20101201) kernel which includes
> wireless-next-2.6 up to master-2010-11-30.
>
[...]
> Unfortunately, my wlan network connection is totally unstable.
[...]
> My wlan device is an ath5k:
>
> $ lspci -nnvv | grep "Ethernet controller" | grep -i ath
> 02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212
> 802.11abg NIC [168c:1014] (rev 01)
>
> Any idea what's wrong? (Just speculating on the last patch-set from Nick...)
So it is definitely not Nick's patchset causing the troubles here.
I have built compat-wireless-2010-11-30 which does not contain this
ath5 patchset.
$ grep ath5k compat-wireless-2010-11-29_compat-wireless-2010-11-30.diff
$ grep ath5k compat-wireless-2010-11-30_compat-wireless-2010-12-01.diff | wc -l
1229
# modinfo ath5k | grep filename
filename:
/lib/modules/2.6.37-rc4-686/updates/drivers/net/wireless/ath/ath5k/ath5k.ko
So I try backwards the c-w-2.6 tarballs and report again.
- Sedat -
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-02 12:17 ` Sedat Dilek
@ 2010-12-02 13:40 ` Sedat Dilek
0 siblings, 0 replies; 22+ messages in thread
From: Sedat Dilek @ 2010-12-02 13:40 UTC (permalink / raw)
To: wireless; +Cc: John Linville, Nick Kossifidis, Stephen Rothwell, Bruno Randolf
On Thu, Dec 2, 2010 at 1:17 PM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> On Wed, Dec 1, 2010 at 11:09 AM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
>> Hi,
>>
>> I have built today a linux-next (next-20101201) kernel which includes
>> wireless-next-2.6 up to master-2010-11-30.
>>
> [...]
>> Unfortunately, my wlan network connection is totally unstable.
> [...]
>> My wlan device is an ath5k:
>>
>> $ lspci -nnvv | grep "Ethernet controller" | grep -i ath
>> 02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212
>> 802.11abg NIC [168c:1014] (rev 01)
>>
>> Any idea what's wrong? (Just speculating on the last patch-set from Nick...)
>
> So it is definitely not Nick's patchset causing the troubles here.
> I have built compat-wireless-2010-11-30 which does not contain this
> ath5 patchset.
>
> $ grep ath5k compat-wireless-2010-11-29_compat-wireless-2010-11-30.diff
>
> $ grep ath5k compat-wireless-2010-11-30_compat-wireless-2010-12-01.diff | wc -l
> 1229
>
> # modinfo ath5k | grep filename
> filename:
> /lib/modules/2.6.37-rc4-686/updates/drivers/net/wireless/ath/ath5k/ath5k.ko
>
> So I try backwards the c-w-2.6 tarballs and report again.
>
I am very very sorry to say this was a false "positive" (or negative?).
After 1st reboot and trying to restart networking, things look
different with c-w (2010-11-30):
# /etc/init.d/networking start
Configuring network interfaces...ioctl[SIOCGIFFLAGS]: No such device
Could not get interface 'wlan0' flags
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: No such device
ioctl[SIOCGIWMODE]: No such device
ioctl[SIOCSIWAP]: No such device
ioctl[SIOCSIWESSID]: No such device
ioctl[SIOCGIFINDEX]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCGIWMODE]: No such device
ioctl[SIOCSIWAP]: No such device
ioctl[SIOCSIWESSID]: No such device
ioctl[SIOCGIFFLAGS]: No such device
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
Failed to bring up wlan0.
done.
What is really working stable is compat-wireless-2.6.37-rc3-1
(confirmed after several reboots). I will stay on this as I need a
reliable network connection.
- Sedat -
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-01 10:21 ` Bruno Randolf
2010-12-01 10:56 ` Sedat Dilek
2010-12-01 21:04 ` Sedat Dilek
@ 2010-12-02 17:33 ` Sedat Dilek
2010-12-02 17:56 ` Nick Kossifidis
2 siblings, 1 reply; 22+ messages in thread
From: Sedat Dilek @ 2010-12-02 17:33 UTC (permalink / raw)
To: Bruno Randolf, Nick Kossifidis; +Cc: wireless, John Linville, Stephen Rothwell
[-- Attachment #1: Type: text/plain, Size: 4792 bytes --]
On Wed, Dec 1, 2010 at 11:21 AM, Bruno Randolf <br1@einfach.org> wrote:
> On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
>> Hi,
>>
>> I have built today a linux-next (next-20101201) kernel which includes
>> wireless-next-2.6 up to master-2010-11-30.
[...]
>> Unfortunately, my wlan network connection is totally unstable.
[...]
> 1.) For identification of the chipset, please:
> dmesg |grep "ath5.*chip"
>
> 2.) Is there a problem when you don't use encryption?
>
> 3.) git bisect might help track it down.
>
> bruno
OK, I did not a "classic" git-bisect, I created from linux-next
(next-20101202) GIT tree a revert-ath5k patchset (30 in total).
[1] VERY GOOD: Revertiing all 30 patches
...leads to a stable system.
[2] REDUCED DISCONNECTIONS DROPS: Reverting 0001..0008
This stabilizes the system, but... listening to a radio
broadcast-stream with VLC is a pain in the ass... permanent audio
dropouts. I had only 2 disconnections in the first 10mins when system
was up (normally I can see disconnects after loggin into my KDE
desktop).
[3] GOOD AUDIO STREAMING: Reverting 0001..0014
This is just fine, system like I am used to.
[4] CONCLUSION
So I played a bit with my revert-patchset.
Reverting 0001..0008 + a refreshed v2 of
0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch (patch attached) is
doing the job here.
Having a closer look into 0008 (parts of
drivers/net/wireless/ath/ath5k/reset.c):
$ grep AR5212 patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
- if (ah->ah_version == AR5K_AR5212)
+ * On AR5212 TSF is almost preserved across a
- * On AR5212 TSF is almost preserved across a
+ if (ah->ah_version == AR5K_AR5212) {
- if (ah->ah_version == AR5K_AR5212 &&
As I mentionned I have a AR5212 wlan device!
What to do with that parts?
Any idea?
Kind Regards,
- Sedat -
P.S.: I have added a list containing all commit-ids (chronological)
and a script how I reverted (documenting for myself).
$ ls patches/revert-wireless-patches/00*.patch
patches/revert-wireless-patches/0001-Revert-ath5k-Set-turbo-bit-on-rf-bank-2.patch
patches/revert-wireless-patches/0002-Revert-ath5k-Clean-up-turbo-mode-initvals-rfregs.patch
patches/revert-wireless-patches/0003-Revert-ath5k-Cleanup-turbo-channel-flags.patch
patches/revert-wireless-patches/0004-Revert-ath5k-Use-correct-clock-when-setting-ofdm-tim.patch
patches/revert-wireless-patches/0005-Revert-ath5k-Skip-tx-power-setting-on-AR5210-for-now.patch
patches/revert-wireless-patches/0006-Revert-ath5k-Tweak-phy-activate-to-rx-start-delay-ba.patch
patches/revert-wireless-patches/0007-Revert-ath5k-No-need-to-save-restore-staid-flags-on-.patch
patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
patches/revert-wireless-patches/0009-Revert-ath5k-Skip-powertable-setting-when-we-are-on-.patch
patches/revert-wireless-patches/0010-Revert-ath5k-Update-PLL-programming-for-turbo-half-q.patch
patches/revert-wireless-patches/0011-Revert-ath5k-Update-spur-mitigation-filter-for-turbo.patch
patches/revert-wireless-patches/0012-Revert-ath5k-Tweak-power-detector-delays-on-RF5111-R.patch
patches/revert-wireless-patches/0013-Revert-ath5k-Always-set-IFS-intervals-on-reset.patch
patches/revert-wireless-patches/0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch
patches/revert-wireless-patches/0015-Revert-ath5k-Set-all-IFS-intervals-not-just-slot-tim.patch
patches/revert-wireless-patches/0016-Revert-ath5k-Extend-rate_duration.patch
patches/revert-wireless-patches/0017-Revert-ath5k-Extend-get_default_sifs-slot_time.patch
patches/revert-wireless-patches/0018-Revert-ath5k-Move-tx-retries-setting-outside-reset_t.patch
patches/revert-wireless-patches/0019-Revert-ath5k-Increase-PHY-settling-parameters-for-tu.patch
patches/revert-wireless-patches/0020-Revert-ath5k-Small-cleanup-on-tweak_initvals.patch
patches/revert-wireless-patches/0021-Revert-ath5k-Put-core-clock-initialization-on-a-new-.patch
patches/revert-wireless-patches/0022-Revert-ath5k-Add-new-field-on-ath5k_hw-to-track-band.patch
patches/revert-wireless-patches/0023-Revert-ath5k-Use-new-function-to-stop-beacon-queue.patch
patches/revert-wireless-patches/0024-Revert-ath5k-Check-RXE-when-setting-RXDP.patch
patches/revert-wireless-patches/0025-Revert-ath5k-Use-DCU-early-termination-correctly.patch
patches/revert-wireless-patches/0026-Revert-ath5k-Debug-DMA-timeouts.patch
patches/revert-wireless-patches/0027-Revert-ath5k-Use-new-dma_stop-function-on-base.c.patch
patches/revert-wireless-patches/0028-Revert-ath5k-Stop-PCU-on-reset.patch
patches/revert-wireless-patches/0029-Revert-ath5k-Add-new-function-to-stop-rx-tx-DMA.patch
patches/revert-wireless-patches/0030-Revert-ath5k-Reset-cleanup-and-generic-cleanup.patch
[-- Attachment #2: 0014-Revert-ath5k-Use-turbo-flag-on-DCU-v2.patch --]
[-- Type: text/x-diff, Size: 630 bytes --]
Index: linux-next/drivers/net/wireless/ath/ath5k/qcu.c
===================================================================
--- linux-next.orig/drivers/net/wireless/ath/ath5k/qcu.c
+++ linux-next/drivers/net/wireless/ath/ath5k/qcu.c
@@ -647,11 +647,6 @@
* on ath5k_hw_set_ifs_intervals */
ath5k_hw_set_tx_retry_limits(ah, 0);
- /* Set the turbo flag when operating on 40MHz */
- if (ah->ah_bwmode == AR5K_BWMODE_40MHZ)
- AR5K_REG_ENABLE_BITS(ah, AR5K_DCU_GBL_IFS_MISC,
- AR5K_DCU_GBL_IFS_MISC_TURBO_MODE);
-
/* If we didn't set IFS timings through
* ath5k_hw_set_coverage_class make sure
* we set them here */
[-- Attachment #3: revert_ath5k_patches.list --]
[-- Type: application/octet-stream, Size: 1230 bytes --]
4352fab5c2a1a602447d711c84d149bf2f0bc7ba
8c2b418a07b4dc77d7efadb890ba9ad1a4161c3f
acb091d67c5c9649cf5d25055ef6fd64239a6762
73a06a683455f472cc09ad249064c66a41e29e39
3bb17654605965226e5b322dbc22ece5ff354ac5
b02f5d1a17c652a74098f2a04db7fb8e6220057e
c2b0ebef262e0a9b64f7ea8ec837cfc29605bef7
8aec7af99b1e4594c4bb9e1c48005e6111f97e8e
4c57581d939fd0f8f244b9730812069f4dac308a
f08fbf6cf4a31c8df52b21440c7a7e6fbe474b28
a2677fe4298c61f0e93c063e59815bf21c530c4a
b2b4c69f682a2868411899a77842061dd745884f
71ba1c30851575b43ba76b0f9c26ff5567e8136c
473cae27620c27377e278a6f92aaa483060e3c19
eeb8832b3181d6ca8593051b68c466e5d2653bb3
61cde037234c4b8e6497a23f5f236c64cbf9d41d
3017fcab416d8d1ee48ca16aa9a3062f600dab8e
25ddfa195735934256fda55bb4f2d749c19386ff
b405086ba47678a5b8f6e7cd835a3d27ebb6f744
325089ab5847f5c1e43f42bb90d32f981867c4c1
c297560206adf0cda8ce38ef9b20b0a025754c4d
fa3d2feeff4723cce8d4722902492d60b7f75fcc
14fae2d4b61b890cea58d63091406b86ec9bafcd
e8325ed87457e07b9ceeb1e7a31df787dd7ee106
f7317ba2d669c1b54fb31ed7834361a700a79217
b3a28e68d5c8d788a4e538a119a5d326545add8a
80dac9eecbdb95f61b9b3c7081e02412155982b7
e088f23be166635b3938571c00c686094efa7cc4
d41174fabdae348c6583cf05aeb329da232c342c
9320b5c4a7260d9593102f378201d17e3f030739
[-- Attachment #4: revert_ath5k-patches.sh --]
[-- Type: application/x-sh, Size: 233 bytes --]
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-02 17:33 ` Sedat Dilek
@ 2010-12-02 17:56 ` Nick Kossifidis
2010-12-02 18:23 ` Nick Kossifidis
0 siblings, 1 reply; 22+ messages in thread
From: Nick Kossifidis @ 2010-12-02 17:56 UTC (permalink / raw)
To: sedat.dilek; +Cc: Bruno Randolf, wireless, John Linville, Stephen Rothwell
2010/12/2 Sedat Dilek <sedat.dilek@googlemail.com>:
> On Wed, Dec 1, 2010 at 11:21 AM, Bruno Randolf <br1@einfach.org> wrote:
>> On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
>>> Hi,
>>>
>>> I have built today a linux-next (next-20101201) kernel which includes
>>> wireless-next-2.6 up to master-2010-11-30.
> [...]
>>> Unfortunately, my wlan network connection is totally unstable.
> [...]
>> 1.) For identification of the chipset, please:
>> dmesg |grep "ath5.*chip"
>>
>> 2.) Is there a problem when you don't use encryption?
>>
>> 3.) git bisect might help track it down.
>>
>> bruno
>
> OK, I did not a "classic" git-bisect, I created from linux-next
> (next-20101202) GIT tree a revert-ath5k patchset (30 in total).
>
> [1] VERY GOOD: Revertiing all 30 patches
>
> ...leads to a stable system.
>
> [2] REDUCED DISCONNECTIONS DROPS: Reverting 0001..0008
>
> This stabilizes the system, but... listening to a radio
> broadcast-stream with VLC is a pain in the ass... permanent audio
> dropouts. I had only 2 disconnections in the first 10mins when system
> was up (normally I can see disconnects after loggin into my KDE
> desktop).
>
> [3] GOOD AUDIO STREAMING: Reverting 0001..0014
>
> This is just fine, system like I am used to.
>
> [4] CONCLUSION
>
> So I played a bit with my revert-patchset.
>
> Reverting 0001..0008 + a refreshed v2 of
> 0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch (patch attached) is
> doing the job here.
>
> Having a closer look into 0008 (parts of
> drivers/net/wireless/ath/ath5k/reset.c):
>
> $ grep AR5212 patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
> - if (ah->ah_version == AR5K_AR5212)
> + * On AR5212 TSF is almost preserved across a
> - * On AR5212 TSF is almost preserved across a
> + if (ah->ah_version == AR5K_AR5212) {
> - if (ah->ah_version == AR5K_AR5212 &&
>
> As I mentionned I have a AR5212 wlan device!
> What to do with that parts?
> Any idea?
>
> Kind Regards,
> - Sedat -
>
> P.S.: I have added a list containing all commit-ids (chronological)
> and a script how I reverted (documenting for myself).
>
> $ ls patches/revert-wireless-patches/00*.patch
> patches/revert-wireless-patches/0001-Revert-ath5k-Set-turbo-bit-on-rf-bank-2.patch
> patches/revert-wireless-patches/0002-Revert-ath5k-Clean-up-turbo-mode-initvals-rfregs.patch
> patches/revert-wireless-patches/0003-Revert-ath5k-Cleanup-turbo-channel-flags.patch
> patches/revert-wireless-patches/0004-Revert-ath5k-Use-correct-clock-when-setting-ofdm-tim.patch
> patches/revert-wireless-patches/0005-Revert-ath5k-Skip-tx-power-setting-on-AR5210-for-now.patch
> patches/revert-wireless-patches/0006-Revert-ath5k-Tweak-phy-activate-to-rx-start-delay-ba.patch
> patches/revert-wireless-patches/0007-Revert-ath5k-No-need-to-save-restore-staid-flags-on-.patch
> patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
> patches/revert-wireless-patches/0009-Revert-ath5k-Skip-powertable-setting-when-we-are-on-.patch
> patches/revert-wireless-patches/0010-Revert-ath5k-Update-PLL-programming-for-turbo-half-q.patch
> patches/revert-wireless-patches/0011-Revert-ath5k-Update-spur-mitigation-filter-for-turbo.patch
> patches/revert-wireless-patches/0012-Revert-ath5k-Tweak-power-detector-delays-on-RF5111-R.patch
> patches/revert-wireless-patches/0013-Revert-ath5k-Always-set-IFS-intervals-on-reset.patch
> patches/revert-wireless-patches/0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch
> patches/revert-wireless-patches/0015-Revert-ath5k-Set-all-IFS-intervals-not-just-slot-tim.patch
> patches/revert-wireless-patches/0016-Revert-ath5k-Extend-rate_duration.patch
> patches/revert-wireless-patches/0017-Revert-ath5k-Extend-get_default_sifs-slot_time.patch
> patches/revert-wireless-patches/0018-Revert-ath5k-Move-tx-retries-setting-outside-reset_t.patch
> patches/revert-wireless-patches/0019-Revert-ath5k-Increase-PHY-settling-parameters-for-tu.patch
> patches/revert-wireless-patches/0020-Revert-ath5k-Small-cleanup-on-tweak_initvals.patch
> patches/revert-wireless-patches/0021-Revert-ath5k-Put-core-clock-initialization-on-a-new-.patch
> patches/revert-wireless-patches/0022-Revert-ath5k-Add-new-field-on-ath5k_hw-to-track-band.patch
> patches/revert-wireless-patches/0023-Revert-ath5k-Use-new-function-to-stop-beacon-queue.patch
> patches/revert-wireless-patches/0024-Revert-ath5k-Check-RXE-when-setting-RXDP.patch
> patches/revert-wireless-patches/0025-Revert-ath5k-Use-DCU-early-termination-correctly.patch
> patches/revert-wireless-patches/0026-Revert-ath5k-Debug-DMA-timeouts.patch
> patches/revert-wireless-patches/0027-Revert-ath5k-Use-new-dma_stop-function-on-base.c.patch
> patches/revert-wireless-patches/0028-Revert-ath5k-Stop-PCU-on-reset.patch
> patches/revert-wireless-patches/0029-Revert-ath5k-Add-new-function-to-stop-rx-tx-DMA.patch
> patches/revert-wireless-patches/0030-Revert-ath5k-Reset-cleanup-and-generic-cleanup.patch
>
OK this doesn't make any sense, based on your logs you have an
AR5212+RF5111+RF2111 combination, synth-only channel change (0008) is
only executed on AR2413 and AR5413 so you don't even run that code,
setting turbo flag on DCU (0014) is also unrelated since we never
enable turbo mode and if we did you wouldn't be able to receive
anything non-turbo.
I am going to test 2 cards like yours a CM6 and an older one from
Atheros and come back to you ASAP...
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-02 17:56 ` Nick Kossifidis
@ 2010-12-02 18:23 ` Nick Kossifidis
2010-12-02 22:33 ` Nick Kossifidis
0 siblings, 1 reply; 22+ messages in thread
From: Nick Kossifidis @ 2010-12-02 18:23 UTC (permalink / raw)
To: sedat.dilek
Cc: Bruno Randolf, wireless, John Linville, Stephen Rothwell,
Jonathan Guerin
2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
> 2010/12/2 Sedat Dilek <sedat.dilek@googlemail.com>:
>> On Wed, Dec 1, 2010 at 11:21 AM, Bruno Randolf <br1@einfach.org> wrote:
>>> On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
>>>> Hi,
>>>>
>>>> I have built today a linux-next (next-20101201) kernel which includes
>>>> wireless-next-2.6 up to master-2010-11-30.
>> [...]
>>>> Unfortunately, my wlan network connection is totally unstable.
>> [...]
>>> 1.) For identification of the chipset, please:
>>> dmesg |grep "ath5.*chip"
>>>
>>> 2.) Is there a problem when you don't use encryption?
>>>
>>> 3.) git bisect might help track it down.
>>>
>>> bruno
>>
>> OK, I did not a "classic" git-bisect, I created from linux-next
>> (next-20101202) GIT tree a revert-ath5k patchset (30 in total).
>>
>> [1] VERY GOOD: Revertiing all 30 patches
>>
>> ...leads to a stable system.
>>
>> [2] REDUCED DISCONNECTIONS DROPS: Reverting 0001..0008
>>
>> This stabilizes the system, but... listening to a radio
>> broadcast-stream with VLC is a pain in the ass... permanent audio
>> dropouts. I had only 2 disconnections in the first 10mins when system
>> was up (normally I can see disconnects after loggin into my KDE
>> desktop).
>>
>> [3] GOOD AUDIO STREAMING: Reverting 0001..0014
>>
>> This is just fine, system like I am used to.
>>
>> [4] CONCLUSION
>>
>> So I played a bit with my revert-patchset.
>>
>> Reverting 0001..0008 + a refreshed v2 of
>> 0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch (patch attached) is
>> doing the job here.
>>
>> Having a closer look into 0008 (parts of
>> drivers/net/wireless/ath/ath5k/reset.c):
>>
>> $ grep AR5212 patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>> - if (ah->ah_version == AR5K_AR5212)
>> + * On AR5212 TSF is almost preserved across a
>> - * On AR5212 TSF is almost preserved across a
>> + if (ah->ah_version == AR5K_AR5212) {
>> - if (ah->ah_version == AR5K_AR5212 &&
>>
>> As I mentionned I have a AR5212 wlan device!
>> What to do with that parts?
>> Any idea?
>>
>> Kind Regards,
>> - Sedat -
>>
>> P.S.: I have added a list containing all commit-ids (chronological)
>> and a script how I reverted (documenting for myself).
>>
>> $ ls patches/revert-wireless-patches/00*.patch
>> patches/revert-wireless-patches/0001-Revert-ath5k-Set-turbo-bit-on-rf-bank-2.patch
>> patches/revert-wireless-patches/0002-Revert-ath5k-Clean-up-turbo-mode-initvals-rfregs.patch
>> patches/revert-wireless-patches/0003-Revert-ath5k-Cleanup-turbo-channel-flags.patch
>> patches/revert-wireless-patches/0004-Revert-ath5k-Use-correct-clock-when-setting-ofdm-tim.patch
>> patches/revert-wireless-patches/0005-Revert-ath5k-Skip-tx-power-setting-on-AR5210-for-now.patch
>> patches/revert-wireless-patches/0006-Revert-ath5k-Tweak-phy-activate-to-rx-start-delay-ba.patch
>> patches/revert-wireless-patches/0007-Revert-ath5k-No-need-to-save-restore-staid-flags-on-.patch
>> patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>> patches/revert-wireless-patches/0009-Revert-ath5k-Skip-powertable-setting-when-we-are-on-.patch
>> patches/revert-wireless-patches/0010-Revert-ath5k-Update-PLL-programming-for-turbo-half-q.patch
>> patches/revert-wireless-patches/0011-Revert-ath5k-Update-spur-mitigation-filter-for-turbo.patch
>> patches/revert-wireless-patches/0012-Revert-ath5k-Tweak-power-detector-delays-on-RF5111-R.patch
>> patches/revert-wireless-patches/0013-Revert-ath5k-Always-set-IFS-intervals-on-reset.patch
>> patches/revert-wireless-patches/0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch
>> patches/revert-wireless-patches/0015-Revert-ath5k-Set-all-IFS-intervals-not-just-slot-tim.patch
>> patches/revert-wireless-patches/0016-Revert-ath5k-Extend-rate_duration.patch
>> patches/revert-wireless-patches/0017-Revert-ath5k-Extend-get_default_sifs-slot_time.patch
>> patches/revert-wireless-patches/0018-Revert-ath5k-Move-tx-retries-setting-outside-reset_t.patch
>> patches/revert-wireless-patches/0019-Revert-ath5k-Increase-PHY-settling-parameters-for-tu.patch
>> patches/revert-wireless-patches/0020-Revert-ath5k-Small-cleanup-on-tweak_initvals.patch
>> patches/revert-wireless-patches/0021-Revert-ath5k-Put-core-clock-initialization-on-a-new-.patch
>> patches/revert-wireless-patches/0022-Revert-ath5k-Add-new-field-on-ath5k_hw-to-track-band.patch
>> patches/revert-wireless-patches/0023-Revert-ath5k-Use-new-function-to-stop-beacon-queue.patch
>> patches/revert-wireless-patches/0024-Revert-ath5k-Check-RXE-when-setting-RXDP.patch
>> patches/revert-wireless-patches/0025-Revert-ath5k-Use-DCU-early-termination-correctly.patch
>> patches/revert-wireless-patches/0026-Revert-ath5k-Debug-DMA-timeouts.patch
>> patches/revert-wireless-patches/0027-Revert-ath5k-Use-new-dma_stop-function-on-base.c.patch
>> patches/revert-wireless-patches/0028-Revert-ath5k-Stop-PCU-on-reset.patch
>> patches/revert-wireless-patches/0029-Revert-ath5k-Add-new-function-to-stop-rx-tx-DMA.patch
>> patches/revert-wireless-patches/0030-Revert-ath5k-Reset-cleanup-and-generic-cleanup.patch
>>
>
> OK this doesn't make any sense, based on your logs you have an
> AR5212+RF5111+RF2111 combination, synth-only channel change (0008) is
> only executed on AR2413 and AR5413 so you don't even run that code,
> setting turbo flag on DCU (0014) is also unrelated since we never
> enable turbo mode and if we did you wouldn't be able to receive
> anything non-turbo.
>
> I am going to test 2 cards like yours a CM6 and an older one from
> Atheros and come back to you ASAP...
>
I just reproduced it on a CM6 and a CM9 (AR5212 + RF5112), problem
occurs when card is idle (no traffic) that's why my automated test
didn't catch it I can still run iperf after connecting and leave it
running without problems, when traffic stops it soon gets
disconnected. I suspect it's something related to IFS timings/ACK
timeout (0013 on your reverted series), maybe Jonathan Guerin was
correct about ACK timeout...
I'll try something and come back to you with code ;-)
Thanks for reporting !
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-02 18:23 ` Nick Kossifidis
@ 2010-12-02 22:33 ` Nick Kossifidis
2010-12-02 22:39 ` Nick Kossifidis
0 siblings, 1 reply; 22+ messages in thread
From: Nick Kossifidis @ 2010-12-02 22:33 UTC (permalink / raw)
To: sedat.dilek
Cc: Bruno Randolf, wireless, John Linville, Stephen Rothwell,
Jonathan Guerin
2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>> 2010/12/2 Sedat Dilek <sedat.dilek@googlemail.com>:
>>> On Wed, Dec 1, 2010 at 11:21 AM, Bruno Randolf <br1@einfach.org> wrote:
>>>> On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
>>>>> Hi,
>>>>>
>>>>> I have built today a linux-next (next-20101201) kernel which includes
>>>>> wireless-next-2.6 up to master-2010-11-30.
>>> [...]
>>>>> Unfortunately, my wlan network connection is totally unstable.
>>> [...]
>>>> 1.) For identification of the chipset, please:
>>>> dmesg |grep "ath5.*chip"
>>>>
>>>> 2.) Is there a problem when you don't use encryption?
>>>>
>>>> 3.) git bisect might help track it down.
>>>>
>>>> bruno
>>>
>>> OK, I did not a "classic" git-bisect, I created from linux-next
>>> (next-20101202) GIT tree a revert-ath5k patchset (30 in total).
>>>
>>> [1] VERY GOOD: Revertiing all 30 patches
>>>
>>> ...leads to a stable system.
>>>
>>> [2] REDUCED DISCONNECTIONS DROPS: Reverting 0001..0008
>>>
>>> This stabilizes the system, but... listening to a radio
>>> broadcast-stream with VLC is a pain in the ass... permanent audio
>>> dropouts. I had only 2 disconnections in the first 10mins when system
>>> was up (normally I can see disconnects after loggin into my KDE
>>> desktop).
>>>
>>> [3] GOOD AUDIO STREAMING: Reverting 0001..0014
>>>
>>> This is just fine, system like I am used to.
>>>
>>> [4] CONCLUSION
>>>
>>> So I played a bit with my revert-patchset.
>>>
>>> Reverting 0001..0008 + a refreshed v2 of
>>> 0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch (patch attached) is
>>> doing the job here.
>>>
>>> Having a closer look into 0008 (parts of
>>> drivers/net/wireless/ath/ath5k/reset.c):
>>>
>>> $ grep AR5212 patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>> - if (ah->ah_version == AR5K_AR5212)
>>> + * On AR5212 TSF is almost preserved across a
>>> - * On AR5212 TSF is almost preserved across a
>>> + if (ah->ah_version == AR5K_AR5212) {
>>> - if (ah->ah_version == AR5K_AR5212 &&
>>>
>>> As I mentionned I have a AR5212 wlan device!
>>> What to do with that parts?
>>> Any idea?
>>>
>>> Kind Regards,
>>> - Sedat -
>>>
>>> P.S.: I have added a list containing all commit-ids (chronological)
>>> and a script how I reverted (documenting for myself).
>>>
>>> $ ls patches/revert-wireless-patches/00*.patch
>>> patches/revert-wireless-patches/0001-Revert-ath5k-Set-turbo-bit-on-rf-bank-2.patch
>>> patches/revert-wireless-patches/0002-Revert-ath5k-Clean-up-turbo-mode-initvals-rfregs.patch
>>> patches/revert-wireless-patches/0003-Revert-ath5k-Cleanup-turbo-channel-flags.patch
>>> patches/revert-wireless-patches/0004-Revert-ath5k-Use-correct-clock-when-setting-ofdm-tim.patch
>>> patches/revert-wireless-patches/0005-Revert-ath5k-Skip-tx-power-setting-on-AR5210-for-now.patch
>>> patches/revert-wireless-patches/0006-Revert-ath5k-Tweak-phy-activate-to-rx-start-delay-ba.patch
>>> patches/revert-wireless-patches/0007-Revert-ath5k-No-need-to-save-restore-staid-flags-on-.patch
>>> patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>> patches/revert-wireless-patches/0009-Revert-ath5k-Skip-powertable-setting-when-we-are-on-.patch
>>> patches/revert-wireless-patches/0010-Revert-ath5k-Update-PLL-programming-for-turbo-half-q.patch
>>> patches/revert-wireless-patches/0011-Revert-ath5k-Update-spur-mitigation-filter-for-turbo.patch
>>> patches/revert-wireless-patches/0012-Revert-ath5k-Tweak-power-detector-delays-on-RF5111-R.patch
>>> patches/revert-wireless-patches/0013-Revert-ath5k-Always-set-IFS-intervals-on-reset.patch
>>> patches/revert-wireless-patches/0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch
>>> patches/revert-wireless-patches/0015-Revert-ath5k-Set-all-IFS-intervals-not-just-slot-tim.patch
>>> patches/revert-wireless-patches/0016-Revert-ath5k-Extend-rate_duration.patch
>>> patches/revert-wireless-patches/0017-Revert-ath5k-Extend-get_default_sifs-slot_time.patch
>>> patches/revert-wireless-patches/0018-Revert-ath5k-Move-tx-retries-setting-outside-reset_t.patch
>>> patches/revert-wireless-patches/0019-Revert-ath5k-Increase-PHY-settling-parameters-for-tu.patch
>>> patches/revert-wireless-patches/0020-Revert-ath5k-Small-cleanup-on-tweak_initvals.patch
>>> patches/revert-wireless-patches/0021-Revert-ath5k-Put-core-clock-initialization-on-a-new-.patch
>>> patches/revert-wireless-patches/0022-Revert-ath5k-Add-new-field-on-ath5k_hw-to-track-band.patch
>>> patches/revert-wireless-patches/0023-Revert-ath5k-Use-new-function-to-stop-beacon-queue.patch
>>> patches/revert-wireless-patches/0024-Revert-ath5k-Check-RXE-when-setting-RXDP.patch
>>> patches/revert-wireless-patches/0025-Revert-ath5k-Use-DCU-early-termination-correctly.patch
>>> patches/revert-wireless-patches/0026-Revert-ath5k-Debug-DMA-timeouts.patch
>>> patches/revert-wireless-patches/0027-Revert-ath5k-Use-new-dma_stop-function-on-base.c.patch
>>> patches/revert-wireless-patches/0028-Revert-ath5k-Stop-PCU-on-reset.patch
>>> patches/revert-wireless-patches/0029-Revert-ath5k-Add-new-function-to-stop-rx-tx-DMA.patch
>>> patches/revert-wireless-patches/0030-Revert-ath5k-Reset-cleanup-and-generic-cleanup.patch
>>>
>>
>> OK this doesn't make any sense, based on your logs you have an
>> AR5212+RF5111+RF2111 combination, synth-only channel change (0008) is
>> only executed on AR2413 and AR5413 so you don't even run that code,
>> setting turbo flag on DCU (0014) is also unrelated since we never
>> enable turbo mode and if we did you wouldn't be able to receive
>> anything non-turbo.
>>
>> I am going to test 2 cards like yours a CM6 and an older one from
>> Atheros and come back to you ASAP...
>>
>
> I just reproduced it on a CM6 and a CM9 (AR5212 + RF5112), problem
> occurs when card is idle (no traffic) that's why my automated test
> didn't catch it I can still run iperf after connecting and leave it
> running without problems, when traffic stops it soon gets
> disconnected. I suspect it's something related to IFS timings/ACK
> timeout (0013 on your reverted series), maybe Jonathan Guerin was
> correct about ACK timeout...
>
> I'll try something and come back to you with code ;-)
>
> Thanks for reporting !
>
Nope, it's PHY related and only affects RF5111/RF5112, AR2413 and
above work fine...
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-02 22:33 ` Nick Kossifidis
@ 2010-12-02 22:39 ` Nick Kossifidis
2010-12-03 2:10 ` Nick Kossifidis
0 siblings, 1 reply; 22+ messages in thread
From: Nick Kossifidis @ 2010-12-02 22:39 UTC (permalink / raw)
To: sedat.dilek
Cc: Bruno Randolf, wireless, John Linville, Stephen Rothwell,
Jonathan Guerin
2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>>> 2010/12/2 Sedat Dilek <sedat.dilek@googlemail.com>:
>>>> On Wed, Dec 1, 2010 at 11:21 AM, Bruno Randolf <br1@einfach.org> wrote:
>>>>> On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I have built today a linux-next (next-20101201) kernel which includes
>>>>>> wireless-next-2.6 up to master-2010-11-30.
>>>> [...]
>>>>>> Unfortunately, my wlan network connection is totally unstable.
>>>> [...]
>>>>> 1.) For identification of the chipset, please:
>>>>> dmesg |grep "ath5.*chip"
>>>>>
>>>>> 2.) Is there a problem when you don't use encryption?
>>>>>
>>>>> 3.) git bisect might help track it down.
>>>>>
>>>>> bruno
>>>>
>>>> OK, I did not a "classic" git-bisect, I created from linux-next
>>>> (next-20101202) GIT tree a revert-ath5k patchset (30 in total).
>>>>
>>>> [1] VERY GOOD: Revertiing all 30 patches
>>>>
>>>> ...leads to a stable system.
>>>>
>>>> [2] REDUCED DISCONNECTIONS DROPS: Reverting 0001..0008
>>>>
>>>> This stabilizes the system, but... listening to a radio
>>>> broadcast-stream with VLC is a pain in the ass... permanent audio
>>>> dropouts. I had only 2 disconnections in the first 10mins when system
>>>> was up (normally I can see disconnects after loggin into my KDE
>>>> desktop).
>>>>
>>>> [3] GOOD AUDIO STREAMING: Reverting 0001..0014
>>>>
>>>> This is just fine, system like I am used to.
>>>>
>>>> [4] CONCLUSION
>>>>
>>>> So I played a bit with my revert-patchset.
>>>>
>>>> Reverting 0001..0008 + a refreshed v2 of
>>>> 0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch (patch attached) is
>>>> doing the job here.
>>>>
>>>> Having a closer look into 0008 (parts of
>>>> drivers/net/wireless/ath/ath5k/reset.c):
>>>>
>>>> $ grep AR5212 patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>>> - if (ah->ah_version == AR5K_AR5212)
>>>> + * On AR5212 TSF is almost preserved across a
>>>> - * On AR5212 TSF is almost preserved across a
>>>> + if (ah->ah_version == AR5K_AR5212) {
>>>> - if (ah->ah_version == AR5K_AR5212 &&
>>>>
>>>> As I mentionned I have a AR5212 wlan device!
>>>> What to do with that parts?
>>>> Any idea?
>>>>
>>>> Kind Regards,
>>>> - Sedat -
>>>>
>>>> P.S.: I have added a list containing all commit-ids (chronological)
>>>> and a script how I reverted (documenting for myself).
>>>>
>>>> $ ls patches/revert-wireless-patches/00*.patch
>>>> patches/revert-wireless-patches/0001-Revert-ath5k-Set-turbo-bit-on-rf-bank-2.patch
>>>> patches/revert-wireless-patches/0002-Revert-ath5k-Clean-up-turbo-mode-initvals-rfregs.patch
>>>> patches/revert-wireless-patches/0003-Revert-ath5k-Cleanup-turbo-channel-flags.patch
>>>> patches/revert-wireless-patches/0004-Revert-ath5k-Use-correct-clock-when-setting-ofdm-tim.patch
>>>> patches/revert-wireless-patches/0005-Revert-ath5k-Skip-tx-power-setting-on-AR5210-for-now.patch
>>>> patches/revert-wireless-patches/0006-Revert-ath5k-Tweak-phy-activate-to-rx-start-delay-ba.patch
>>>> patches/revert-wireless-patches/0007-Revert-ath5k-No-need-to-save-restore-staid-flags-on-.patch
>>>> patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>>> patches/revert-wireless-patches/0009-Revert-ath5k-Skip-powertable-setting-when-we-are-on-.patch
>>>> patches/revert-wireless-patches/0010-Revert-ath5k-Update-PLL-programming-for-turbo-half-q.patch
>>>> patches/revert-wireless-patches/0011-Revert-ath5k-Update-spur-mitigation-filter-for-turbo.patch
>>>> patches/revert-wireless-patches/0012-Revert-ath5k-Tweak-power-detector-delays-on-RF5111-R.patch
>>>> patches/revert-wireless-patches/0013-Revert-ath5k-Always-set-IFS-intervals-on-reset.patch
>>>> patches/revert-wireless-patches/0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch
>>>> patches/revert-wireless-patches/0015-Revert-ath5k-Set-all-IFS-intervals-not-just-slot-tim.patch
>>>> patches/revert-wireless-patches/0016-Revert-ath5k-Extend-rate_duration.patch
>>>> patches/revert-wireless-patches/0017-Revert-ath5k-Extend-get_default_sifs-slot_time.patch
>>>> patches/revert-wireless-patches/0018-Revert-ath5k-Move-tx-retries-setting-outside-reset_t.patch
>>>> patches/revert-wireless-patches/0019-Revert-ath5k-Increase-PHY-settling-parameters-for-tu.patch
>>>> patches/revert-wireless-patches/0020-Revert-ath5k-Small-cleanup-on-tweak_initvals.patch
>>>> patches/revert-wireless-patches/0021-Revert-ath5k-Put-core-clock-initialization-on-a-new-.patch
>>>> patches/revert-wireless-patches/0022-Revert-ath5k-Add-new-field-on-ath5k_hw-to-track-band.patch
>>>> patches/revert-wireless-patches/0023-Revert-ath5k-Use-new-function-to-stop-beacon-queue.patch
>>>> patches/revert-wireless-patches/0024-Revert-ath5k-Check-RXE-when-setting-RXDP.patch
>>>> patches/revert-wireless-patches/0025-Revert-ath5k-Use-DCU-early-termination-correctly.patch
>>>> patches/revert-wireless-patches/0026-Revert-ath5k-Debug-DMA-timeouts.patch
>>>> patches/revert-wireless-patches/0027-Revert-ath5k-Use-new-dma_stop-function-on-base.c.patch
>>>> patches/revert-wireless-patches/0028-Revert-ath5k-Stop-PCU-on-reset.patch
>>>> patches/revert-wireless-patches/0029-Revert-ath5k-Add-new-function-to-stop-rx-tx-DMA.patch
>>>> patches/revert-wireless-patches/0030-Revert-ath5k-Reset-cleanup-and-generic-cleanup.patch
>>>>
>>>
>>> OK this doesn't make any sense, based on your logs you have an
>>> AR5212+RF5111+RF2111 combination, synth-only channel change (0008) is
>>> only executed on AR2413 and AR5413 so you don't even run that code,
>>> setting turbo flag on DCU (0014) is also unrelated since we never
>>> enable turbo mode and if we did you wouldn't be able to receive
>>> anything non-turbo.
>>>
>>> I am going to test 2 cards like yours a CM6 and an older one from
>>> Atheros and come back to you ASAP...
>>>
>>
>> I just reproduced it on a CM6 and a CM9 (AR5212 + RF5112), problem
>> occurs when card is idle (no traffic) that's why my automated test
>> didn't catch it I can still run iperf after connecting and leave it
>> running without problems, when traffic stops it soon gets
>> disconnected. I suspect it's something related to IFS timings/ACK
>> timeout (0013 on your reverted series), maybe Jonathan Guerin was
>> correct about ACK timeout...
>>
>> I'll try something and come back to you with code ;-)
>>
>> Thanks for reporting !
>>
>
> Nope, it's PHY related and only affects RF5111/RF5112, AR2413 and
> above work fine...
>
Got it, patch on the way...
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-02 22:39 ` Nick Kossifidis
@ 2010-12-03 2:10 ` Nick Kossifidis
2010-12-03 4:16 ` Nick Kossifidis
0 siblings, 1 reply; 22+ messages in thread
From: Nick Kossifidis @ 2010-12-03 2:10 UTC (permalink / raw)
To: sedat.dilek
Cc: Bruno Randolf, wireless, John Linville, Stephen Rothwell,
Jonathan Guerin
2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>>> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>>>> 2010/12/2 Sedat Dilek <sedat.dilek@googlemail.com>:
>>>>> On Wed, Dec 1, 2010 at 11:21 AM, Bruno Randolf <br1@einfach.org> wrote:
>>>>>> On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have built today a linux-next (next-20101201) kernel which includes
>>>>>>> wireless-next-2.6 up to master-2010-11-30.
>>>>> [...]
>>>>>>> Unfortunately, my wlan network connection is totally unstable.
>>>>> [...]
>>>>>> 1.) For identification of the chipset, please:
>>>>>> dmesg |grep "ath5.*chip"
>>>>>>
>>>>>> 2.) Is there a problem when you don't use encryption?
>>>>>>
>>>>>> 3.) git bisect might help track it down.
>>>>>>
>>>>>> bruno
>>>>>
>>>>> OK, I did not a "classic" git-bisect, I created from linux-next
>>>>> (next-20101202) GIT tree a revert-ath5k patchset (30 in total).
>>>>>
>>>>> [1] VERY GOOD: Revertiing all 30 patches
>>>>>
>>>>> ...leads to a stable system.
>>>>>
>>>>> [2] REDUCED DISCONNECTIONS DROPS: Reverting 0001..0008
>>>>>
>>>>> This stabilizes the system, but... listening to a radio
>>>>> broadcast-stream with VLC is a pain in the ass... permanent audio
>>>>> dropouts. I had only 2 disconnections in the first 10mins when system
>>>>> was up (normally I can see disconnects after loggin into my KDE
>>>>> desktop).
>>>>>
>>>>> [3] GOOD AUDIO STREAMING: Reverting 0001..0014
>>>>>
>>>>> This is just fine, system like I am used to.
>>>>>
>>>>> [4] CONCLUSION
>>>>>
>>>>> So I played a bit with my revert-patchset.
>>>>>
>>>>> Reverting 0001..0008 + a refreshed v2 of
>>>>> 0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch (patch attached) is
>>>>> doing the job here.
>>>>>
>>>>> Having a closer look into 0008 (parts of
>>>>> drivers/net/wireless/ath/ath5k/reset.c):
>>>>>
>>>>> $ grep AR5212 patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>>>> - if (ah->ah_version == AR5K_AR5212)
>>>>> + * On AR5212 TSF is almost preserved across a
>>>>> - * On AR5212 TSF is almost preserved across a
>>>>> + if (ah->ah_version == AR5K_AR5212) {
>>>>> - if (ah->ah_version == AR5K_AR5212 &&
>>>>>
>>>>> As I mentionned I have a AR5212 wlan device!
>>>>> What to do with that parts?
>>>>> Any idea?
>>>>>
>>>>> Kind Regards,
>>>>> - Sedat -
>>>>>
>>>>> P.S.: I have added a list containing all commit-ids (chronological)
>>>>> and a script how I reverted (documenting for myself).
>>>>>
>>>>> $ ls patches/revert-wireless-patches/00*.patch
>>>>> patches/revert-wireless-patches/0001-Revert-ath5k-Set-turbo-bit-on-rf-bank-2.patch
>>>>> patches/revert-wireless-patches/0002-Revert-ath5k-Clean-up-turbo-mode-initvals-rfregs.patch
>>>>> patches/revert-wireless-patches/0003-Revert-ath5k-Cleanup-turbo-channel-flags.patch
>>>>> patches/revert-wireless-patches/0004-Revert-ath5k-Use-correct-clock-when-setting-ofdm-tim.patch
>>>>> patches/revert-wireless-patches/0005-Revert-ath5k-Skip-tx-power-setting-on-AR5210-for-now.patch
>>>>> patches/revert-wireless-patches/0006-Revert-ath5k-Tweak-phy-activate-to-rx-start-delay-ba.patch
>>>>> patches/revert-wireless-patches/0007-Revert-ath5k-No-need-to-save-restore-staid-flags-on-.patch
>>>>> patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>>>> patches/revert-wireless-patches/0009-Revert-ath5k-Skip-powertable-setting-when-we-are-on-.patch
>>>>> patches/revert-wireless-patches/0010-Revert-ath5k-Update-PLL-programming-for-turbo-half-q.patch
>>>>> patches/revert-wireless-patches/0011-Revert-ath5k-Update-spur-mitigation-filter-for-turbo.patch
>>>>> patches/revert-wireless-patches/0012-Revert-ath5k-Tweak-power-detector-delays-on-RF5111-R.patch
>>>>> patches/revert-wireless-patches/0013-Revert-ath5k-Always-set-IFS-intervals-on-reset.patch
>>>>> patches/revert-wireless-patches/0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch
>>>>> patches/revert-wireless-patches/0015-Revert-ath5k-Set-all-IFS-intervals-not-just-slot-tim.patch
>>>>> patches/revert-wireless-patches/0016-Revert-ath5k-Extend-rate_duration.patch
>>>>> patches/revert-wireless-patches/0017-Revert-ath5k-Extend-get_default_sifs-slot_time.patch
>>>>> patches/revert-wireless-patches/0018-Revert-ath5k-Move-tx-retries-setting-outside-reset_t.patch
>>>>> patches/revert-wireless-patches/0019-Revert-ath5k-Increase-PHY-settling-parameters-for-tu.patch
>>>>> patches/revert-wireless-patches/0020-Revert-ath5k-Small-cleanup-on-tweak_initvals.patch
>>>>> patches/revert-wireless-patches/0021-Revert-ath5k-Put-core-clock-initialization-on-a-new-.patch
>>>>> patches/revert-wireless-patches/0022-Revert-ath5k-Add-new-field-on-ath5k_hw-to-track-band.patch
>>>>> patches/revert-wireless-patches/0023-Revert-ath5k-Use-new-function-to-stop-beacon-queue.patch
>>>>> patches/revert-wireless-patches/0024-Revert-ath5k-Check-RXE-when-setting-RXDP.patch
>>>>> patches/revert-wireless-patches/0025-Revert-ath5k-Use-DCU-early-termination-correctly.patch
>>>>> patches/revert-wireless-patches/0026-Revert-ath5k-Debug-DMA-timeouts.patch
>>>>> patches/revert-wireless-patches/0027-Revert-ath5k-Use-new-dma_stop-function-on-base.c.patch
>>>>> patches/revert-wireless-patches/0028-Revert-ath5k-Stop-PCU-on-reset.patch
>>>>> patches/revert-wireless-patches/0029-Revert-ath5k-Add-new-function-to-stop-rx-tx-DMA.patch
>>>>> patches/revert-wireless-patches/0030-Revert-ath5k-Reset-cleanup-and-generic-cleanup.patch
>>>>>
>>>>
>>>> OK this doesn't make any sense, based on your logs you have an
>>>> AR5212+RF5111+RF2111 combination, synth-only channel change (0008) is
>>>> only executed on AR2413 and AR5413 so you don't even run that code,
>>>> setting turbo flag on DCU (0014) is also unrelated since we never
>>>> enable turbo mode and if we did you wouldn't be able to receive
>>>> anything non-turbo.
>>>>
>>>> I am going to test 2 cards like yours a CM6 and an older one from
>>>> Atheros and come back to you ASAP...
>>>>
>>>
>>> I just reproduced it on a CM6 and a CM9 (AR5212 + RF5112), problem
>>> occurs when card is idle (no traffic) that's why my automated test
>>> didn't catch it I can still run iperf after connecting and leave it
>>> running without problems, when traffic stops it soon gets
>>> disconnected. I suspect it's something related to IFS timings/ACK
>>> timeout (0013 on your reverted series), maybe Jonathan Guerin was
>>> correct about ACK timeout...
>>>
>>> I'll try something and come back to you with code ;-)
>>>
>>> Thanks for reporting !
>>>
>>
>> Nope, it's PHY related and only affects RF5111/RF5112, AR2413 and
>> above work fine...
>>
>
> Got it, patch on the way...
>
First the problem is with patch 22 (0009), we still need to write the
power table on hw, that fixes transmission and my CM9 works just fine
after that. Now my 2 RF5111 based cards seem to also have some problem
with stuck tx queues, after some time of fine operation (nearly
28Mbits with iperf). It might be a hw failure or something but i want
to try and debug this further in case there is something i can do to
fix it. I also found some other things, eg. i report RX dma stop
failure when i shouldn't etc. Anyway back to debuging ;-)
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-03 2:10 ` Nick Kossifidis
@ 2010-12-03 4:16 ` Nick Kossifidis
2010-12-03 6:15 ` Sedat Dilek
0 siblings, 1 reply; 22+ messages in thread
From: Nick Kossifidis @ 2010-12-03 4:16 UTC (permalink / raw)
To: sedat.dilek
Cc: Bruno Randolf, wireless, John Linville, Stephen Rothwell,
Jonathan Guerin
2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>>> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>>>> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>>>>> 2010/12/2 Sedat Dilek <sedat.dilek@googlemail.com>:
>>>>>> On Wed, Dec 1, 2010 at 11:21 AM, Bruno Randolf <br1@einfach.org> wrote:
>>>>>>> On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I have built today a linux-next (next-20101201) kernel which includes
>>>>>>>> wireless-next-2.6 up to master-2010-11-30.
>>>>>> [...]
>>>>>>>> Unfortunately, my wlan network connection is totally unstable.
>>>>>> [...]
>>>>>>> 1.) For identification of the chipset, please:
>>>>>>> dmesg |grep "ath5.*chip"
>>>>>>>
>>>>>>> 2.) Is there a problem when you don't use encryption?
>>>>>>>
>>>>>>> 3.) git bisect might help track it down.
>>>>>>>
>>>>>>> bruno
>>>>>>
>>>>>> OK, I did not a "classic" git-bisect, I created from linux-next
>>>>>> (next-20101202) GIT tree a revert-ath5k patchset (30 in total).
>>>>>>
>>>>>> [1] VERY GOOD: Revertiing all 30 patches
>>>>>>
>>>>>> ...leads to a stable system.
>>>>>>
>>>>>> [2] REDUCED DISCONNECTIONS DROPS: Reverting 0001..0008
>>>>>>
>>>>>> This stabilizes the system, but... listening to a radio
>>>>>> broadcast-stream with VLC is a pain in the ass... permanent audio
>>>>>> dropouts. I had only 2 disconnections in the first 10mins when system
>>>>>> was up (normally I can see disconnects after loggin into my KDE
>>>>>> desktop).
>>>>>>
>>>>>> [3] GOOD AUDIO STREAMING: Reverting 0001..0014
>>>>>>
>>>>>> This is just fine, system like I am used to.
>>>>>>
>>>>>> [4] CONCLUSION
>>>>>>
>>>>>> So I played a bit with my revert-patchset.
>>>>>>
>>>>>> Reverting 0001..0008 + a refreshed v2 of
>>>>>> 0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch (patch attached) is
>>>>>> doing the job here.
>>>>>>
>>>>>> Having a closer look into 0008 (parts of
>>>>>> drivers/net/wireless/ath/ath5k/reset.c):
>>>>>>
>>>>>> $ grep AR5212 patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>>>>> - if (ah->ah_version == AR5K_AR5212)
>>>>>> + * On AR5212 TSF is almost preserved across a
>>>>>> - * On AR5212 TSF is almost preserved across a
>>>>>> + if (ah->ah_version == AR5K_AR5212) {
>>>>>> - if (ah->ah_version == AR5K_AR5212 &&
>>>>>>
>>>>>> As I mentionned I have a AR5212 wlan device!
>>>>>> What to do with that parts?
>>>>>> Any idea?
>>>>>>
>>>>>> Kind Regards,
>>>>>> - Sedat -
>>>>>>
>>>>>> P.S.: I have added a list containing all commit-ids (chronological)
>>>>>> and a script how I reverted (documenting for myself).
>>>>>>
>>>>>> $ ls patches/revert-wireless-patches/00*.patch
>>>>>> patches/revert-wireless-patches/0001-Revert-ath5k-Set-turbo-bit-on-rf-bank-2.patch
>>>>>> patches/revert-wireless-patches/0002-Revert-ath5k-Clean-up-turbo-mode-initvals-rfregs.patch
>>>>>> patches/revert-wireless-patches/0003-Revert-ath5k-Cleanup-turbo-channel-flags.patch
>>>>>> patches/revert-wireless-patches/0004-Revert-ath5k-Use-correct-clock-when-setting-ofdm-tim.patch
>>>>>> patches/revert-wireless-patches/0005-Revert-ath5k-Skip-tx-power-setting-on-AR5210-for-now.patch
>>>>>> patches/revert-wireless-patches/0006-Revert-ath5k-Tweak-phy-activate-to-rx-start-delay-ba.patch
>>>>>> patches/revert-wireless-patches/0007-Revert-ath5k-No-need-to-save-restore-staid-flags-on-.patch
>>>>>> patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>>>>> patches/revert-wireless-patches/0009-Revert-ath5k-Skip-powertable-setting-when-we-are-on-.patch
>>>>>> patches/revert-wireless-patches/0010-Revert-ath5k-Update-PLL-programming-for-turbo-half-q.patch
>>>>>> patches/revert-wireless-patches/0011-Revert-ath5k-Update-spur-mitigation-filter-for-turbo.patch
>>>>>> patches/revert-wireless-patches/0012-Revert-ath5k-Tweak-power-detector-delays-on-RF5111-R.patch
>>>>>> patches/revert-wireless-patches/0013-Revert-ath5k-Always-set-IFS-intervals-on-reset.patch
>>>>>> patches/revert-wireless-patches/0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch
>>>>>> patches/revert-wireless-patches/0015-Revert-ath5k-Set-all-IFS-intervals-not-just-slot-tim.patch
>>>>>> patches/revert-wireless-patches/0016-Revert-ath5k-Extend-rate_duration.patch
>>>>>> patches/revert-wireless-patches/0017-Revert-ath5k-Extend-get_default_sifs-slot_time.patch
>>>>>> patches/revert-wireless-patches/0018-Revert-ath5k-Move-tx-retries-setting-outside-reset_t.patch
>>>>>> patches/revert-wireless-patches/0019-Revert-ath5k-Increase-PHY-settling-parameters-for-tu.patch
>>>>>> patches/revert-wireless-patches/0020-Revert-ath5k-Small-cleanup-on-tweak_initvals.patch
>>>>>> patches/revert-wireless-patches/0021-Revert-ath5k-Put-core-clock-initialization-on-a-new-.patch
>>>>>> patches/revert-wireless-patches/0022-Revert-ath5k-Add-new-field-on-ath5k_hw-to-track-band.patch
>>>>>> patches/revert-wireless-patches/0023-Revert-ath5k-Use-new-function-to-stop-beacon-queue.patch
>>>>>> patches/revert-wireless-patches/0024-Revert-ath5k-Check-RXE-when-setting-RXDP.patch
>>>>>> patches/revert-wireless-patches/0025-Revert-ath5k-Use-DCU-early-termination-correctly.patch
>>>>>> patches/revert-wireless-patches/0026-Revert-ath5k-Debug-DMA-timeouts.patch
>>>>>> patches/revert-wireless-patches/0027-Revert-ath5k-Use-new-dma_stop-function-on-base.c.patch
>>>>>> patches/revert-wireless-patches/0028-Revert-ath5k-Stop-PCU-on-reset.patch
>>>>>> patches/revert-wireless-patches/0029-Revert-ath5k-Add-new-function-to-stop-rx-tx-DMA.patch
>>>>>> patches/revert-wireless-patches/0030-Revert-ath5k-Reset-cleanup-and-generic-cleanup.patch
>>>>>>
>>>>>
>>>>> OK this doesn't make any sense, based on your logs you have an
>>>>> AR5212+RF5111+RF2111 combination, synth-only channel change (0008) is
>>>>> only executed on AR2413 and AR5413 so you don't even run that code,
>>>>> setting turbo flag on DCU (0014) is also unrelated since we never
>>>>> enable turbo mode and if we did you wouldn't be able to receive
>>>>> anything non-turbo.
>>>>>
>>>>> I am going to test 2 cards like yours a CM6 and an older one from
>>>>> Atheros and come back to you ASAP...
>>>>>
>>>>
>>>> I just reproduced it on a CM6 and a CM9 (AR5212 + RF5112), problem
>>>> occurs when card is idle (no traffic) that's why my automated test
>>>> didn't catch it I can still run iperf after connecting and leave it
>>>> running without problems, when traffic stops it soon gets
>>>> disconnected. I suspect it's something related to IFS timings/ACK
>>>> timeout (0013 on your reverted series), maybe Jonathan Guerin was
>>>> correct about ACK timeout...
>>>>
>>>> I'll try something and come back to you with code ;-)
>>>>
>>>> Thanks for reporting !
>>>>
>>>
>>> Nope, it's PHY related and only affects RF5111/RF5112, AR2413 and
>>> above work fine...
>>>
>>
>> Got it, patch on the way...
>>
>
> First the problem is with patch 22 (0009), we still need to write the
> power table on hw, that fixes transmission and my CM9 works just fine
> after that. Now my 2 RF5111 based cards seem to also have some problem
> with stuck tx queues, after some time of fine operation (nearly
> 28Mbits with iperf). It might be a hw failure or something but i want
> to try and debug this further in case there is something i can do to
> fix it. I also found some other things, eg. i report RX dma stop
> failure when i shouldn't etc. Anyway back to debuging ;-)
>
>
> --
> GPG ID: 0xD21DB2DB
> As you read this post global entropy rises. Have Fun ;-)
> Nick
>
Done, works fine for me now, check it out ;-)
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-03 4:16 ` Nick Kossifidis
@ 2010-12-03 6:15 ` Sedat Dilek
2010-12-03 6:19 ` Sedat Dilek
2010-12-03 6:31 ` Nick Kossifidis
0 siblings, 2 replies; 22+ messages in thread
From: Sedat Dilek @ 2010-12-03 6:15 UTC (permalink / raw)
To: Nick Kossifidis
Cc: Bruno Randolf, wireless, John Linville, Stephen Rothwell,
Jonathan Guerin
On Fri, Dec 3, 2010 at 5:16 AM, Nick Kossifidis <mickflemm@gmail.com> wrote:
> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>>> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>>>> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>>>>> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>>>>>> 2010/12/2 Sedat Dilek <sedat.dilek@googlemail.com>:
>>>>>>> On Wed, Dec 1, 2010 at 11:21 AM, Bruno Randolf <br1@einfach.org> wrote:
>>>>>>>> On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I have built today a linux-next (next-20101201) kernel which includes
>>>>>>>>> wireless-next-2.6 up to master-2010-11-30.
>>>>>>> [...]
>>>>>>>>> Unfortunately, my wlan network connection is totally unstable.
>>>>>>> [...]
>>>>>>>> 1.) For identification of the chipset, please:
>>>>>>>> dmesg |grep "ath5.*chip"
>>>>>>>>
>>>>>>>> 2.) Is there a problem when you don't use encryption?
>>>>>>>>
>>>>>>>> 3.) git bisect might help track it down.
>>>>>>>>
>>>>>>>> bruno
>>>>>>>
>>>>>>> OK, I did not a "classic" git-bisect, I created from linux-next
>>>>>>> (next-20101202) GIT tree a revert-ath5k patchset (30 in total).
>>>>>>>
>>>>>>> [1] VERY GOOD: Revertiing all 30 patches
>>>>>>>
>>>>>>> ...leads to a stable system.
>>>>>>>
>>>>>>> [2] REDUCED DISCONNECTIONS DROPS: Reverting 0001..0008
>>>>>>>
>>>>>>> This stabilizes the system, but... listening to a radio
>>>>>>> broadcast-stream with VLC is a pain in the ass... permanent audio
>>>>>>> dropouts. I had only 2 disconnections in the first 10mins when system
>>>>>>> was up (normally I can see disconnects after loggin into my KDE
>>>>>>> desktop).
>>>>>>>
>>>>>>> [3] GOOD AUDIO STREAMING: Reverting 0001..0014
>>>>>>>
>>>>>>> This is just fine, system like I am used to.
>>>>>>>
>>>>>>> [4] CONCLUSION
>>>>>>>
>>>>>>> So I played a bit with my revert-patchset.
>>>>>>>
>>>>>>> Reverting 0001..0008 + a refreshed v2 of
>>>>>>> 0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch (patch attached) is
>>>>>>> doing the job here.
>>>>>>>
>>>>>>> Having a closer look into 0008 (parts of
>>>>>>> drivers/net/wireless/ath/ath5k/reset.c):
>>>>>>>
>>>>>>> $ grep AR5212 patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>>>>>> - if (ah->ah_version == AR5K_AR5212)
>>>>>>> + * On AR5212 TSF is almost preserved across a
>>>>>>> - * On AR5212 TSF is almost preserved across a
>>>>>>> + if (ah->ah_version == AR5K_AR5212) {
>>>>>>> - if (ah->ah_version == AR5K_AR5212 &&
>>>>>>>
>>>>>>> As I mentionned I have a AR5212 wlan device!
>>>>>>> What to do with that parts?
>>>>>>> Any idea?
>>>>>>>
>>>>>>> Kind Regards,
>>>>>>> - Sedat -
>>>>>>>
>>>>>>> P.S.: I have added a list containing all commit-ids (chronological)
>>>>>>> and a script how I reverted (documenting for myself).
>>>>>>>
>>>>>>> $ ls patches/revert-wireless-patches/00*.patch
>>>>>>> patches/revert-wireless-patches/0001-Revert-ath5k-Set-turbo-bit-on-rf-bank-2.patch
>>>>>>> patches/revert-wireless-patches/0002-Revert-ath5k-Clean-up-turbo-mode-initvals-rfregs.patch
>>>>>>> patches/revert-wireless-patches/0003-Revert-ath5k-Cleanup-turbo-channel-flags.patch
>>>>>>> patches/revert-wireless-patches/0004-Revert-ath5k-Use-correct-clock-when-setting-ofdm-tim.patch
>>>>>>> patches/revert-wireless-patches/0005-Revert-ath5k-Skip-tx-power-setting-on-AR5210-for-now.patch
>>>>>>> patches/revert-wireless-patches/0006-Revert-ath5k-Tweak-phy-activate-to-rx-start-delay-ba.patch
>>>>>>> patches/revert-wireless-patches/0007-Revert-ath5k-No-need-to-save-restore-staid-flags-on-.patch
>>>>>>> patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>>>>>> patches/revert-wireless-patches/0009-Revert-ath5k-Skip-powertable-setting-when-we-are-on-.patch
>>>>>>> patches/revert-wireless-patches/0010-Revert-ath5k-Update-PLL-programming-for-turbo-half-q.patch
>>>>>>> patches/revert-wireless-patches/0011-Revert-ath5k-Update-spur-mitigation-filter-for-turbo.patch
>>>>>>> patches/revert-wireless-patches/0012-Revert-ath5k-Tweak-power-detector-delays-on-RF5111-R.patch
>>>>>>> patches/revert-wireless-patches/0013-Revert-ath5k-Always-set-IFS-intervals-on-reset.patch
>>>>>>> patches/revert-wireless-patches/0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch
>>>>>>> patches/revert-wireless-patches/0015-Revert-ath5k-Set-all-IFS-intervals-not-just-slot-tim.patch
>>>>>>> patches/revert-wireless-patches/0016-Revert-ath5k-Extend-rate_duration.patch
>>>>>>> patches/revert-wireless-patches/0017-Revert-ath5k-Extend-get_default_sifs-slot_time.patch
>>>>>>> patches/revert-wireless-patches/0018-Revert-ath5k-Move-tx-retries-setting-outside-reset_t.patch
>>>>>>> patches/revert-wireless-patches/0019-Revert-ath5k-Increase-PHY-settling-parameters-for-tu.patch
>>>>>>> patches/revert-wireless-patches/0020-Revert-ath5k-Small-cleanup-on-tweak_initvals.patch
>>>>>>> patches/revert-wireless-patches/0021-Revert-ath5k-Put-core-clock-initialization-on-a-new-.patch
>>>>>>> patches/revert-wireless-patches/0022-Revert-ath5k-Add-new-field-on-ath5k_hw-to-track-band.patch
>>>>>>> patches/revert-wireless-patches/0023-Revert-ath5k-Use-new-function-to-stop-beacon-queue.patch
>>>>>>> patches/revert-wireless-patches/0024-Revert-ath5k-Check-RXE-when-setting-RXDP.patch
>>>>>>> patches/revert-wireless-patches/0025-Revert-ath5k-Use-DCU-early-termination-correctly.patch
>>>>>>> patches/revert-wireless-patches/0026-Revert-ath5k-Debug-DMA-timeouts.patch
>>>>>>> patches/revert-wireless-patches/0027-Revert-ath5k-Use-new-dma_stop-function-on-base.c.patch
>>>>>>> patches/revert-wireless-patches/0028-Revert-ath5k-Stop-PCU-on-reset.patch
>>>>>>> patches/revert-wireless-patches/0029-Revert-ath5k-Add-new-function-to-stop-rx-tx-DMA.patch
>>>>>>> patches/revert-wireless-patches/0030-Revert-ath5k-Reset-cleanup-and-generic-cleanup.patch
>>>>>>>
>>>>>>
>>>>>> OK this doesn't make any sense, based on your logs you have an
>>>>>> AR5212+RF5111+RF2111 combination, synth-only channel change (0008) is
>>>>>> only executed on AR2413 and AR5413 so you don't even run that code,
>>>>>> setting turbo flag on DCU (0014) is also unrelated since we never
>>>>>> enable turbo mode and if we did you wouldn't be able to receive
>>>>>> anything non-turbo.
>>>>>>
>>>>>> I am going to test 2 cards like yours a CM6 and an older one from
>>>>>> Atheros and come back to you ASAP...
>>>>>>
>>>>>
>>>>> I just reproduced it on a CM6 and a CM9 (AR5212 + RF5112), problem
>>>>> occurs when card is idle (no traffic) that's why my automated test
>>>>> didn't catch it I can still run iperf after connecting and leave it
>>>>> running without problems, when traffic stops it soon gets
>>>>> disconnected. I suspect it's something related to IFS timings/ACK
>>>>> timeout (0013 on your reverted series), maybe Jonathan Guerin was
>>>>> correct about ACK timeout...
>>>>>
>>>>> I'll try something and come back to you with code ;-)
>>>>>
>>>>> Thanks for reporting !
>>>>>
>>>>
>>>> Nope, it's PHY related and only affects RF5111/RF5112, AR2413 and
>>>> above work fine...
>>>>
>>>
>>> Got it, patch on the way...
>>>
>>
>> First the problem is with patch 22 (0009), we still need to write the
>> power table on hw, that fixes transmission and my CM9 works just fine
>> after that. Now my 2 RF5111 based cards seem to also have some problem
>> with stuck tx queues, after some time of fine operation (nearly
>> 28Mbits with iperf). It might be a hw failure or something but i want
>> to try and debug this further in case there is something i can do to
>> fix it. I also found some other things, eg. i report RX dma stop
>> failure when i shouldn't etc. Anyway back to debuging ;-)
>>
>>
>> --
>> GPG ID: 0xD21DB2DB
>> As you read this post global entropy rises. Have Fun ;-)
>> Nick
>>
>
> Done, works fine for me now, check it out ;-)
>
> --
> GPG ID: 0xD21DB2DB
> As you read this post global entropy rises. Have Fun ;-)
> Nick
>
Hi Nick,
I have applied the 6 patches you sent to linux-wireless list.
$ cd $HOME/src/linux-2.6/linux-2.6.37-rc4/debian/build/source_i386_none
$ cat .pc/applied-patches
from_nkossifidis/1-6-ath5k-Always-write-tx-powertable-on-hw.patch
from_nkossifidis/2-6-ath5k-Always-free-tx-buffers-before-reset.patch
from_nkossifidis/3-6-ath5k-Disable-ANI-during-reset.patch
from_nkossifidis/4-6-ath5k-Fix-reporting-of-RX-dma-stop-failure.patch
from_nkossifidis/5-6-ath5k-Update-version-string.patch
from_nkossifidis/6-6-ath5k-Include-tx-ack-reporting-on-hw-flags.patch
No more disconnects and no more audio-dropouts when listening to live-radio.
A big big big thank you!
Shall I add to each of your patches a "Tested-by: Sedat Dilek
<sedat.dilek@gmail.com>?
Kind Regards,
- Sedat -
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-03 6:15 ` Sedat Dilek
@ 2010-12-03 6:19 ` Sedat Dilek
2010-12-03 6:31 ` Nick Kossifidis
1 sibling, 0 replies; 22+ messages in thread
From: Sedat Dilek @ 2010-12-03 6:19 UTC (permalink / raw)
To: Nick Kossifidis
Cc: Bruno Randolf, wireless, John Linville, Stephen Rothwell,
Jonathan Guerin
On Fri, Dec 3, 2010 at 7:15 AM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> On Fri, Dec 3, 2010 at 5:16 AM, Nick Kossifidis <mickflemm@gmail.com> wrote:
>> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>>> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>>>> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>>>>> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>>>>>> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>>>>>>> 2010/12/2 Sedat Dilek <sedat.dilek@googlemail.com>:
>>>>>>>> On Wed, Dec 1, 2010 at 11:21 AM, Bruno Randolf <br1@einfach.org> wrote:
>>>>>>>>> On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I have built today a linux-next (next-20101201) kernel which includes
>>>>>>>>>> wireless-next-2.6 up to master-2010-11-30.
>>>>>>>> [...]
>>>>>>>>>> Unfortunately, my wlan network connection is totally unstable.
>>>>>>>> [...]
>>>>>>>>> 1.) For identification of the chipset, please:
>>>>>>>>> dmesg |grep "ath5.*chip"
>>>>>>>>>
>>>>>>>>> 2.) Is there a problem when you don't use encryption?
>>>>>>>>>
>>>>>>>>> 3.) git bisect might help track it down.
>>>>>>>>>
>>>>>>>>> bruno
>>>>>>>>
>>>>>>>> OK, I did not a "classic" git-bisect, I created from linux-next
>>>>>>>> (next-20101202) GIT tree a revert-ath5k patchset (30 in total).
>>>>>>>>
>>>>>>>> [1] VERY GOOD: Revertiing all 30 patches
>>>>>>>>
>>>>>>>> ...leads to a stable system.
>>>>>>>>
>>>>>>>> [2] REDUCED DISCONNECTIONS DROPS: Reverting 0001..0008
>>>>>>>>
>>>>>>>> This stabilizes the system, but... listening to a radio
>>>>>>>> broadcast-stream with VLC is a pain in the ass... permanent audio
>>>>>>>> dropouts. I had only 2 disconnections in the first 10mins when system
>>>>>>>> was up (normally I can see disconnects after loggin into my KDE
>>>>>>>> desktop).
>>>>>>>>
>>>>>>>> [3] GOOD AUDIO STREAMING: Reverting 0001..0014
>>>>>>>>
>>>>>>>> This is just fine, system like I am used to.
>>>>>>>>
>>>>>>>> [4] CONCLUSION
>>>>>>>>
>>>>>>>> So I played a bit with my revert-patchset.
>>>>>>>>
>>>>>>>> Reverting 0001..0008 + a refreshed v2 of
>>>>>>>> 0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch (patch attached) is
>>>>>>>> doing the job here.
>>>>>>>>
>>>>>>>> Having a closer look into 0008 (parts of
>>>>>>>> drivers/net/wireless/ath/ath5k/reset.c):
>>>>>>>>
>>>>>>>> $ grep AR5212 patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>>>>>>> - if (ah->ah_version == AR5K_AR5212)
>>>>>>>> + * On AR5212 TSF is almost preserved across a
>>>>>>>> - * On AR5212 TSF is almost preserved across a
>>>>>>>> + if (ah->ah_version == AR5K_AR5212) {
>>>>>>>> - if (ah->ah_version == AR5K_AR5212 &&
>>>>>>>>
>>>>>>>> As I mentionned I have a AR5212 wlan device!
>>>>>>>> What to do with that parts?
>>>>>>>> Any idea?
>>>>>>>>
>>>>>>>> Kind Regards,
>>>>>>>> - Sedat -
>>>>>>>>
>>>>>>>> P.S.: I have added a list containing all commit-ids (chronological)
>>>>>>>> and a script how I reverted (documenting for myself).
>>>>>>>>
>>>>>>>> $ ls patches/revert-wireless-patches/00*.patch
>>>>>>>> patches/revert-wireless-patches/0001-Revert-ath5k-Set-turbo-bit-on-rf-bank-2.patch
>>>>>>>> patches/revert-wireless-patches/0002-Revert-ath5k-Clean-up-turbo-mode-initvals-rfregs.patch
>>>>>>>> patches/revert-wireless-patches/0003-Revert-ath5k-Cleanup-turbo-channel-flags.patch
>>>>>>>> patches/revert-wireless-patches/0004-Revert-ath5k-Use-correct-clock-when-setting-ofdm-tim.patch
>>>>>>>> patches/revert-wireless-patches/0005-Revert-ath5k-Skip-tx-power-setting-on-AR5210-for-now.patch
>>>>>>>> patches/revert-wireless-patches/0006-Revert-ath5k-Tweak-phy-activate-to-rx-start-delay-ba.patch
>>>>>>>> patches/revert-wireless-patches/0007-Revert-ath5k-No-need-to-save-restore-staid-flags-on-.patch
>>>>>>>> patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>>>>>>> patches/revert-wireless-patches/0009-Revert-ath5k-Skip-powertable-setting-when-we-are-on-.patch
>>>>>>>> patches/revert-wireless-patches/0010-Revert-ath5k-Update-PLL-programming-for-turbo-half-q.patch
>>>>>>>> patches/revert-wireless-patches/0011-Revert-ath5k-Update-spur-mitigation-filter-for-turbo.patch
>>>>>>>> patches/revert-wireless-patches/0012-Revert-ath5k-Tweak-power-detector-delays-on-RF5111-R.patch
>>>>>>>> patches/revert-wireless-patches/0013-Revert-ath5k-Always-set-IFS-intervals-on-reset.patch
>>>>>>>> patches/revert-wireless-patches/0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch
>>>>>>>> patches/revert-wireless-patches/0015-Revert-ath5k-Set-all-IFS-intervals-not-just-slot-tim.patch
>>>>>>>> patches/revert-wireless-patches/0016-Revert-ath5k-Extend-rate_duration.patch
>>>>>>>> patches/revert-wireless-patches/0017-Revert-ath5k-Extend-get_default_sifs-slot_time.patch
>>>>>>>> patches/revert-wireless-patches/0018-Revert-ath5k-Move-tx-retries-setting-outside-reset_t.patch
>>>>>>>> patches/revert-wireless-patches/0019-Revert-ath5k-Increase-PHY-settling-parameters-for-tu.patch
>>>>>>>> patches/revert-wireless-patches/0020-Revert-ath5k-Small-cleanup-on-tweak_initvals.patch
>>>>>>>> patches/revert-wireless-patches/0021-Revert-ath5k-Put-core-clock-initialization-on-a-new-.patch
>>>>>>>> patches/revert-wireless-patches/0022-Revert-ath5k-Add-new-field-on-ath5k_hw-to-track-band.patch
>>>>>>>> patches/revert-wireless-patches/0023-Revert-ath5k-Use-new-function-to-stop-beacon-queue.patch
>>>>>>>> patches/revert-wireless-patches/0024-Revert-ath5k-Check-RXE-when-setting-RXDP.patch
>>>>>>>> patches/revert-wireless-patches/0025-Revert-ath5k-Use-DCU-early-termination-correctly.patch
>>>>>>>> patches/revert-wireless-patches/0026-Revert-ath5k-Debug-DMA-timeouts.patch
>>>>>>>> patches/revert-wireless-patches/0027-Revert-ath5k-Use-new-dma_stop-function-on-base.c.patch
>>>>>>>> patches/revert-wireless-patches/0028-Revert-ath5k-Stop-PCU-on-reset.patch
>>>>>>>> patches/revert-wireless-patches/0029-Revert-ath5k-Add-new-function-to-stop-rx-tx-DMA.patch
>>>>>>>> patches/revert-wireless-patches/0030-Revert-ath5k-Reset-cleanup-and-generic-cleanup.patch
>>>>>>>>
>>>>>>>
>>>>>>> OK this doesn't make any sense, based on your logs you have an
>>>>>>> AR5212+RF5111+RF2111 combination, synth-only channel change (0008) is
>>>>>>> only executed on AR2413 and AR5413 so you don't even run that code,
>>>>>>> setting turbo flag on DCU (0014) is also unrelated since we never
>>>>>>> enable turbo mode and if we did you wouldn't be able to receive
>>>>>>> anything non-turbo.
>>>>>>>
>>>>>>> I am going to test 2 cards like yours a CM6 and an older one from
>>>>>>> Atheros and come back to you ASAP...
>>>>>>>
>>>>>>
>>>>>> I just reproduced it on a CM6 and a CM9 (AR5212 + RF5112), problem
>>>>>> occurs when card is idle (no traffic) that's why my automated test
>>>>>> didn't catch it I can still run iperf after connecting and leave it
>>>>>> running without problems, when traffic stops it soon gets
>>>>>> disconnected. I suspect it's something related to IFS timings/ACK
>>>>>> timeout (0013 on your reverted series), maybe Jonathan Guerin was
>>>>>> correct about ACK timeout...
>>>>>>
>>>>>> I'll try something and come back to you with code ;-)
>>>>>>
>>>>>> Thanks for reporting !
>>>>>>
>>>>>
>>>>> Nope, it's PHY related and only affects RF5111/RF5112, AR2413 and
>>>>> above work fine...
>>>>>
>>>>
>>>> Got it, patch on the way...
>>>>
>>>
>>> First the problem is with patch 22 (0009), we still need to write the
>>> power table on hw, that fixes transmission and my CM9 works just fine
>>> after that. Now my 2 RF5111 based cards seem to also have some problem
>>> with stuck tx queues, after some time of fine operation (nearly
>>> 28Mbits with iperf). It might be a hw failure or something but i want
>>> to try and debug this further in case there is something i can do to
>>> fix it. I also found some other things, eg. i report RX dma stop
>>> failure when i shouldn't etc. Anyway back to debuging ;-)
>>>
>>>
>>> --
>>> GPG ID: 0xD21DB2DB
>>> As you read this post global entropy rises. Have Fun ;-)
>>> Nick
>>>
>>
>> Done, works fine for me now, check it out ;-)
>>
>> --
>> GPG ID: 0xD21DB2DB
>> As you read this post global entropy rises. Have Fun ;-)
>> Nick
>>
>
> Hi Nick,
>
> I have applied the 6 patches you sent to linux-wireless list.
>
> $ cd $HOME/src/linux-2.6/linux-2.6.37-rc4/debian/build/source_i386_none
>
> $ cat .pc/applied-patches
> from_nkossifidis/1-6-ath5k-Always-write-tx-powertable-on-hw.patch
> from_nkossifidis/2-6-ath5k-Always-free-tx-buffers-before-reset.patch
> from_nkossifidis/3-6-ath5k-Disable-ANI-during-reset.patch
> from_nkossifidis/4-6-ath5k-Fix-reporting-of-RX-dma-stop-failure.patch
> from_nkossifidis/5-6-ath5k-Update-version-string.patch
> from_nkossifidis/6-6-ath5k-Include-tx-ack-reporting-on-hw-flags.patch
>
> No more disconnects and no more audio-dropouts when listening to live-radio.
> A big big big thank you!
>
> Shall I add to each of your patches a "Tested-by: Sedat Dilek
> <sedat.dilek@gmail.com>?
>
> Kind Regards,
> - Sedat -
>
Bitrates now seem to be fine, too (36-48MBps).
- Sedat -
# iw dev wlan0 station dump
Station 00:04:0e:e4:00:3d (on wlan0)
inactive time: 12 ms
rx bytes: 16446860
rx packets: 36582
tx bytes: 1353803
tx packets: 14138
signal: -60 dBm
tx bitrate: 36.0 MBit/s
# iw dev wlan0 station dump
Station 00:04:0e:e4:00:3d (on wlan0)
inactive time: 72 ms
rx bytes: 16459615
rx packets: 36613
tx bytes: 1354835
tx packets: 14150
signal: -60 dBm
tx bitrate: 48.0 MBit/s
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-03 6:15 ` Sedat Dilek
2010-12-03 6:19 ` Sedat Dilek
@ 2010-12-03 6:31 ` Nick Kossifidis
2010-12-03 6:49 ` Sedat Dilek
2010-12-03 16:24 ` Sedat Dilek
1 sibling, 2 replies; 22+ messages in thread
From: Nick Kossifidis @ 2010-12-03 6:31 UTC (permalink / raw)
To: sedat.dilek
Cc: Bruno Randolf, wireless, John Linville, Stephen Rothwell,
Jonathan Guerin
2010/12/3 Sedat Dilek <sedat.dilek@googlemail.com>:
> On Fri, Dec 3, 2010 at 5:16 AM, Nick Kossifidis <mickflemm@gmail.com> wrote:
>> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>>> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>>>> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>>>>> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>>>>>> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>>>>>>> 2010/12/2 Sedat Dilek <sedat.dilek@googlemail.com>:
>>>>>>>> On Wed, Dec 1, 2010 at 11:21 AM, Bruno Randolf <br1@einfach.org> wrote:
>>>>>>>>> On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I have built today a linux-next (next-20101201) kernel which includes
>>>>>>>>>> wireless-next-2.6 up to master-2010-11-30.
>>>>>>>> [...]
>>>>>>>>>> Unfortunately, my wlan network connection is totally unstable.
>>>>>>>> [...]
>>>>>>>>> 1.) For identification of the chipset, please:
>>>>>>>>> dmesg |grep "ath5.*chip"
>>>>>>>>>
>>>>>>>>> 2.) Is there a problem when you don't use encryption?
>>>>>>>>>
>>>>>>>>> 3.) git bisect might help track it down.
>>>>>>>>>
>>>>>>>>> bruno
>>>>>>>>
>>>>>>>> OK, I did not a "classic" git-bisect, I created from linux-next
>>>>>>>> (next-20101202) GIT tree a revert-ath5k patchset (30 in total).
>>>>>>>>
>>>>>>>> [1] VERY GOOD: Revertiing all 30 patches
>>>>>>>>
>>>>>>>> ...leads to a stable system.
>>>>>>>>
>>>>>>>> [2] REDUCED DISCONNECTIONS DROPS: Reverting 0001..0008
>>>>>>>>
>>>>>>>> This stabilizes the system, but... listening to a radio
>>>>>>>> broadcast-stream with VLC is a pain in the ass... permanent audio
>>>>>>>> dropouts. I had only 2 disconnections in the first 10mins when system
>>>>>>>> was up (normally I can see disconnects after loggin into my KDE
>>>>>>>> desktop).
>>>>>>>>
>>>>>>>> [3] GOOD AUDIO STREAMING: Reverting 0001..0014
>>>>>>>>
>>>>>>>> This is just fine, system like I am used to.
>>>>>>>>
>>>>>>>> [4] CONCLUSION
>>>>>>>>
>>>>>>>> So I played a bit with my revert-patchset.
>>>>>>>>
>>>>>>>> Reverting 0001..0008 + a refreshed v2 of
>>>>>>>> 0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch (patch attached) is
>>>>>>>> doing the job here.
>>>>>>>>
>>>>>>>> Having a closer look into 0008 (parts of
>>>>>>>> drivers/net/wireless/ath/ath5k/reset.c):
>>>>>>>>
>>>>>>>> $ grep AR5212 patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>>>>>>> - if (ah->ah_version == AR5K_AR5212)
>>>>>>>> + * On AR5212 TSF is almost preserved across a
>>>>>>>> - * On AR5212 TSF is almost preserved across a
>>>>>>>> + if (ah->ah_version == AR5K_AR5212) {
>>>>>>>> - if (ah->ah_version == AR5K_AR5212 &&
>>>>>>>>
>>>>>>>> As I mentionned I have a AR5212 wlan device!
>>>>>>>> What to do with that parts?
>>>>>>>> Any idea?
>>>>>>>>
>>>>>>>> Kind Regards,
>>>>>>>> - Sedat -
>>>>>>>>
>>>>>>>> P.S.: I have added a list containing all commit-ids (chronological)
>>>>>>>> and a script how I reverted (documenting for myself).
>>>>>>>>
>>>>>>>> $ ls patches/revert-wireless-patches/00*.patch
>>>>>>>> patches/revert-wireless-patches/0001-Revert-ath5k-Set-turbo-bit-on-rf-bank-2.patch
>>>>>>>> patches/revert-wireless-patches/0002-Revert-ath5k-Clean-up-turbo-mode-initvals-rfregs.patch
>>>>>>>> patches/revert-wireless-patches/0003-Revert-ath5k-Cleanup-turbo-channel-flags.patch
>>>>>>>> patches/revert-wireless-patches/0004-Revert-ath5k-Use-correct-clock-when-setting-ofdm-tim.patch
>>>>>>>> patches/revert-wireless-patches/0005-Revert-ath5k-Skip-tx-power-setting-on-AR5210-for-now.patch
>>>>>>>> patches/revert-wireless-patches/0006-Revert-ath5k-Tweak-phy-activate-to-rx-start-delay-ba.patch
>>>>>>>> patches/revert-wireless-patches/0007-Revert-ath5k-No-need-to-save-restore-staid-flags-on-.patch
>>>>>>>> patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>>>>>>> patches/revert-wireless-patches/0009-Revert-ath5k-Skip-powertable-setting-when-we-are-on-.patch
>>>>>>>> patches/revert-wireless-patches/0010-Revert-ath5k-Update-PLL-programming-for-turbo-half-q.patch
>>>>>>>> patches/revert-wireless-patches/0011-Revert-ath5k-Update-spur-mitigation-filter-for-turbo.patch
>>>>>>>> patches/revert-wireless-patches/0012-Revert-ath5k-Tweak-power-detector-delays-on-RF5111-R.patch
>>>>>>>> patches/revert-wireless-patches/0013-Revert-ath5k-Always-set-IFS-intervals-on-reset.patch
>>>>>>>> patches/revert-wireless-patches/0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch
>>>>>>>> patches/revert-wireless-patches/0015-Revert-ath5k-Set-all-IFS-intervals-not-just-slot-tim.patch
>>>>>>>> patches/revert-wireless-patches/0016-Revert-ath5k-Extend-rate_duration.patch
>>>>>>>> patches/revert-wireless-patches/0017-Revert-ath5k-Extend-get_default_sifs-slot_time.patch
>>>>>>>> patches/revert-wireless-patches/0018-Revert-ath5k-Move-tx-retries-setting-outside-reset_t.patch
>>>>>>>> patches/revert-wireless-patches/0019-Revert-ath5k-Increase-PHY-settling-parameters-for-tu.patch
>>>>>>>> patches/revert-wireless-patches/0020-Revert-ath5k-Small-cleanup-on-tweak_initvals.patch
>>>>>>>> patches/revert-wireless-patches/0021-Revert-ath5k-Put-core-clock-initialization-on-a-new-.patch
>>>>>>>> patches/revert-wireless-patches/0022-Revert-ath5k-Add-new-field-on-ath5k_hw-to-track-band.patch
>>>>>>>> patches/revert-wireless-patches/0023-Revert-ath5k-Use-new-function-to-stop-beacon-queue.patch
>>>>>>>> patches/revert-wireless-patches/0024-Revert-ath5k-Check-RXE-when-setting-RXDP.patch
>>>>>>>> patches/revert-wireless-patches/0025-Revert-ath5k-Use-DCU-early-termination-correctly.patch
>>>>>>>> patches/revert-wireless-patches/0026-Revert-ath5k-Debug-DMA-timeouts.patch
>>>>>>>> patches/revert-wireless-patches/0027-Revert-ath5k-Use-new-dma_stop-function-on-base.c.patch
>>>>>>>> patches/revert-wireless-patches/0028-Revert-ath5k-Stop-PCU-on-reset.patch
>>>>>>>> patches/revert-wireless-patches/0029-Revert-ath5k-Add-new-function-to-stop-rx-tx-DMA.patch
>>>>>>>> patches/revert-wireless-patches/0030-Revert-ath5k-Reset-cleanup-and-generic-cleanup.patch
>>>>>>>>
>>>>>>>
>>>>>>> OK this doesn't make any sense, based on your logs you have an
>>>>>>> AR5212+RF5111+RF2111 combination, synth-only channel change (0008) is
>>>>>>> only executed on AR2413 and AR5413 so you don't even run that code,
>>>>>>> setting turbo flag on DCU (0014) is also unrelated since we never
>>>>>>> enable turbo mode and if we did you wouldn't be able to receive
>>>>>>> anything non-turbo.
>>>>>>>
>>>>>>> I am going to test 2 cards like yours a CM6 and an older one from
>>>>>>> Atheros and come back to you ASAP...
>>>>>>>
>>>>>>
>>>>>> I just reproduced it on a CM6 and a CM9 (AR5212 + RF5112), problem
>>>>>> occurs when card is idle (no traffic) that's why my automated test
>>>>>> didn't catch it I can still run iperf after connecting and leave it
>>>>>> running without problems, when traffic stops it soon gets
>>>>>> disconnected. I suspect it's something related to IFS timings/ACK
>>>>>> timeout (0013 on your reverted series), maybe Jonathan Guerin was
>>>>>> correct about ACK timeout...
>>>>>>
>>>>>> I'll try something and come back to you with code ;-)
>>>>>>
>>>>>> Thanks for reporting !
>>>>>>
>>>>>
>>>>> Nope, it's PHY related and only affects RF5111/RF5112, AR2413 and
>>>>> above work fine...
>>>>>
>>>>
>>>> Got it, patch on the way...
>>>>
>>>
>>> First the problem is with patch 22 (0009), we still need to write the
>>> power table on hw, that fixes transmission and my CM9 works just fine
>>> after that. Now my 2 RF5111 based cards seem to also have some problem
>>> with stuck tx queues, after some time of fine operation (nearly
>>> 28Mbits with iperf). It might be a hw failure or something but i want
>>> to try and debug this further in case there is something i can do to
>>> fix it. I also found some other things, eg. i report RX dma stop
>>> failure when i shouldn't etc. Anyway back to debuging ;-)
>>>
>>>
>>> --
>>> GPG ID: 0xD21DB2DB
>>> As you read this post global entropy rises. Have Fun ;-)
>>> Nick
>>>
>>
>> Done, works fine for me now, check it out ;-)
>>
>> --
>> GPG ID: 0xD21DB2DB
>> As you read this post global entropy rises. Have Fun ;-)
>> Nick
>>
>
> Hi Nick,
>
> I have applied the 6 patches you sent to linux-wireless list.
>
> $ cd $HOME/src/linux-2.6/linux-2.6.37-rc4/debian/build/source_i386_none
>
> $ cat .pc/applied-patches
> from_nkossifidis/1-6-ath5k-Always-write-tx-powertable-on-hw.patch
> from_nkossifidis/2-6-ath5k-Always-free-tx-buffers-before-reset.patch
> from_nkossifidis/3-6-ath5k-Disable-ANI-during-reset.patch
> from_nkossifidis/4-6-ath5k-Fix-reporting-of-RX-dma-stop-failure.patch
> from_nkossifidis/5-6-ath5k-Update-version-string.patch
> from_nkossifidis/6-6-ath5k-Include-tx-ack-reporting-on-hw-flags.patch
>
> No more disconnects and no more audio-dropouts when listening to live-radio.
> A big big big thank you!
>
> Shall I add to each of your patches a "Tested-by: Sedat Dilek
> <sedat.dilek@gmail.com>?
>
> Kind Regards,
> - Sedat -
>
Sure, again thanks a lot for reporting this and testing ;-)
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-03 6:31 ` Nick Kossifidis
@ 2010-12-03 6:49 ` Sedat Dilek
2010-12-03 16:24 ` Sedat Dilek
1 sibling, 0 replies; 22+ messages in thread
From: Sedat Dilek @ 2010-12-03 6:49 UTC (permalink / raw)
To: Nick Kossifidis, John Linville
Cc: Bruno Randolf, wireless, Stephen Rothwell, Jonathan Guerin
On Fri, Dec 3, 2010 at 7:31 AM, Nick Kossifidis <mickflemm@gmail.com> wrote:
> 2010/12/3 Sedat Dilek <sedat.dilek@googlemail.com>:
>> On Fri, Dec 3, 2010 at 5:16 AM, Nick Kossifidis <mickflemm@gmail.com> wrote:
>>> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>>>> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>>>>> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>>>>>> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>>>>>>> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>>>>>>>> 2010/12/2 Sedat Dilek <sedat.dilek@googlemail.com>:
>>>>>>>>> On Wed, Dec 1, 2010 at 11:21 AM, Bruno Randolf <br1@einfach.org> wrote:
>>>>>>>>>> On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I have built today a linux-next (next-20101201) kernel which includes
>>>>>>>>>>> wireless-next-2.6 up to master-2010-11-30.
>>>>>>>>> [...]
>>>>>>>>>>> Unfortunately, my wlan network connection is totally unstable.
>>>>>>>>> [...]
>>>>>>>>>> 1.) For identification of the chipset, please:
>>>>>>>>>> dmesg |grep "ath5.*chip"
>>>>>>>>>>
>>>>>>>>>> 2.) Is there a problem when you don't use encryption?
>>>>>>>>>>
>>>>>>>>>> 3.) git bisect might help track it down.
>>>>>>>>>>
>>>>>>>>>> bruno
>>>>>>>>>
>>>>>>>>> OK, I did not a "classic" git-bisect, I created from linux-next
>>>>>>>>> (next-20101202) GIT tree a revert-ath5k patchset (30 in total).
>>>>>>>>>
>>>>>>>>> [1] VERY GOOD: Revertiing all 30 patches
>>>>>>>>>
>>>>>>>>> ...leads to a stable system.
>>>>>>>>>
>>>>>>>>> [2] REDUCED DISCONNECTIONS DROPS: Reverting 0001..0008
>>>>>>>>>
>>>>>>>>> This stabilizes the system, but... listening to a radio
>>>>>>>>> broadcast-stream with VLC is a pain in the ass... permanent audio
>>>>>>>>> dropouts. I had only 2 disconnections in the first 10mins when system
>>>>>>>>> was up (normally I can see disconnects after loggin into my KDE
>>>>>>>>> desktop).
>>>>>>>>>
>>>>>>>>> [3] GOOD AUDIO STREAMING: Reverting 0001..0014
>>>>>>>>>
>>>>>>>>> This is just fine, system like I am used to.
>>>>>>>>>
>>>>>>>>> [4] CONCLUSION
>>>>>>>>>
>>>>>>>>> So I played a bit with my revert-patchset.
>>>>>>>>>
>>>>>>>>> Reverting 0001..0008 + a refreshed v2 of
>>>>>>>>> 0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch (patch attached) is
>>>>>>>>> doing the job here.
>>>>>>>>>
>>>>>>>>> Having a closer look into 0008 (parts of
>>>>>>>>> drivers/net/wireless/ath/ath5k/reset.c):
>>>>>>>>>
>>>>>>>>> $ grep AR5212 patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>>>>>>>> - if (ah->ah_version == AR5K_AR5212)
>>>>>>>>> + * On AR5212 TSF is almost preserved across a
>>>>>>>>> - * On AR5212 TSF is almost preserved across a
>>>>>>>>> + if (ah->ah_version == AR5K_AR5212) {
>>>>>>>>> - if (ah->ah_version == AR5K_AR5212 &&
>>>>>>>>>
>>>>>>>>> As I mentionned I have a AR5212 wlan device!
>>>>>>>>> What to do with that parts?
>>>>>>>>> Any idea?
>>>>>>>>>
>>>>>>>>> Kind Regards,
>>>>>>>>> - Sedat -
>>>>>>>>>
>>>>>>>>> P.S.: I have added a list containing all commit-ids (chronological)
>>>>>>>>> and a script how I reverted (documenting for myself).
>>>>>>>>>
>>>>>>>>> $ ls patches/revert-wireless-patches/00*.patch
>>>>>>>>> patches/revert-wireless-patches/0001-Revert-ath5k-Set-turbo-bit-on-rf-bank-2.patch
>>>>>>>>> patches/revert-wireless-patches/0002-Revert-ath5k-Clean-up-turbo-mode-initvals-rfregs.patch
>>>>>>>>> patches/revert-wireless-patches/0003-Revert-ath5k-Cleanup-turbo-channel-flags.patch
>>>>>>>>> patches/revert-wireless-patches/0004-Revert-ath5k-Use-correct-clock-when-setting-ofdm-tim.patch
>>>>>>>>> patches/revert-wireless-patches/0005-Revert-ath5k-Skip-tx-power-setting-on-AR5210-for-now.patch
>>>>>>>>> patches/revert-wireless-patches/0006-Revert-ath5k-Tweak-phy-activate-to-rx-start-delay-ba.patch
>>>>>>>>> patches/revert-wireless-patches/0007-Revert-ath5k-No-need-to-save-restore-staid-flags-on-.patch
>>>>>>>>> patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>>>>>>>> patches/revert-wireless-patches/0009-Revert-ath5k-Skip-powertable-setting-when-we-are-on-.patch
>>>>>>>>> patches/revert-wireless-patches/0010-Revert-ath5k-Update-PLL-programming-for-turbo-half-q.patch
>>>>>>>>> patches/revert-wireless-patches/0011-Revert-ath5k-Update-spur-mitigation-filter-for-turbo.patch
>>>>>>>>> patches/revert-wireless-patches/0012-Revert-ath5k-Tweak-power-detector-delays-on-RF5111-R.patch
>>>>>>>>> patches/revert-wireless-patches/0013-Revert-ath5k-Always-set-IFS-intervals-on-reset.patch
>>>>>>>>> patches/revert-wireless-patches/0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch
>>>>>>>>> patches/revert-wireless-patches/0015-Revert-ath5k-Set-all-IFS-intervals-not-just-slot-tim.patch
>>>>>>>>> patches/revert-wireless-patches/0016-Revert-ath5k-Extend-rate_duration.patch
>>>>>>>>> patches/revert-wireless-patches/0017-Revert-ath5k-Extend-get_default_sifs-slot_time.patch
>>>>>>>>> patches/revert-wireless-patches/0018-Revert-ath5k-Move-tx-retries-setting-outside-reset_t.patch
>>>>>>>>> patches/revert-wireless-patches/0019-Revert-ath5k-Increase-PHY-settling-parameters-for-tu.patch
>>>>>>>>> patches/revert-wireless-patches/0020-Revert-ath5k-Small-cleanup-on-tweak_initvals.patch
>>>>>>>>> patches/revert-wireless-patches/0021-Revert-ath5k-Put-core-clock-initialization-on-a-new-.patch
>>>>>>>>> patches/revert-wireless-patches/0022-Revert-ath5k-Add-new-field-on-ath5k_hw-to-track-band.patch
>>>>>>>>> patches/revert-wireless-patches/0023-Revert-ath5k-Use-new-function-to-stop-beacon-queue.patch
>>>>>>>>> patches/revert-wireless-patches/0024-Revert-ath5k-Check-RXE-when-setting-RXDP.patch
>>>>>>>>> patches/revert-wireless-patches/0025-Revert-ath5k-Use-DCU-early-termination-correctly.patch
>>>>>>>>> patches/revert-wireless-patches/0026-Revert-ath5k-Debug-DMA-timeouts.patch
>>>>>>>>> patches/revert-wireless-patches/0027-Revert-ath5k-Use-new-dma_stop-function-on-base.c.patch
>>>>>>>>> patches/revert-wireless-patches/0028-Revert-ath5k-Stop-PCU-on-reset.patch
>>>>>>>>> patches/revert-wireless-patches/0029-Revert-ath5k-Add-new-function-to-stop-rx-tx-DMA.patch
>>>>>>>>> patches/revert-wireless-patches/0030-Revert-ath5k-Reset-cleanup-and-generic-cleanup.patch
>>>>>>>>>
>>>>>>>>
>>>>>>>> OK this doesn't make any sense, based on your logs you have an
>>>>>>>> AR5212+RF5111+RF2111 combination, synth-only channel change (0008) is
>>>>>>>> only executed on AR2413 and AR5413 so you don't even run that code,
>>>>>>>> setting turbo flag on DCU (0014) is also unrelated since we never
>>>>>>>> enable turbo mode and if we did you wouldn't be able to receive
>>>>>>>> anything non-turbo.
>>>>>>>>
>>>>>>>> I am going to test 2 cards like yours a CM6 and an older one from
>>>>>>>> Atheros and come back to you ASAP...
>>>>>>>>
>>>>>>>
>>>>>>> I just reproduced it on a CM6 and a CM9 (AR5212 + RF5112), problem
>>>>>>> occurs when card is idle (no traffic) that's why my automated test
>>>>>>> didn't catch it I can still run iperf after connecting and leave it
>>>>>>> running without problems, when traffic stops it soon gets
>>>>>>> disconnected. I suspect it's something related to IFS timings/ACK
>>>>>>> timeout (0013 on your reverted series), maybe Jonathan Guerin was
>>>>>>> correct about ACK timeout...
>>>>>>>
>>>>>>> I'll try something and come back to you with code ;-)
>>>>>>>
>>>>>>> Thanks for reporting !
>>>>>>>
>>>>>>
>>>>>> Nope, it's PHY related and only affects RF5111/RF5112, AR2413 and
>>>>>> above work fine...
>>>>>>
>>>>>
>>>>> Got it, patch on the way...
>>>>>
>>>>
>>>> First the problem is with patch 22 (0009), we still need to write the
>>>> power table on hw, that fixes transmission and my CM9 works just fine
>>>> after that. Now my 2 RF5111 based cards seem to also have some problem
>>>> with stuck tx queues, after some time of fine operation (nearly
>>>> 28Mbits with iperf). It might be a hw failure or something but i want
>>>> to try and debug this further in case there is something i can do to
>>>> fix it. I also found some other things, eg. i report RX dma stop
>>>> failure when i shouldn't etc. Anyway back to debuging ;-)
>>>>
>>>>
>>>> --
>>>> GPG ID: 0xD21DB2DB
>>>> As you read this post global entropy rises. Have Fun ;-)
>>>> Nick
>>>>
>>>
>>> Done, works fine for me now, check it out ;-)
>>>
>>> --
>>> GPG ID: 0xD21DB2DB
>>> As you read this post global entropy rises. Have Fun ;-)
>>> Nick
>>>
>>
>> Hi Nick,
>>
>> I have applied the 6 patches you sent to linux-wireless list.
>>
>> $ cd $HOME/src/linux-2.6/linux-2.6.37-rc4/debian/build/source_i386_none
>>
>> $ cat .pc/applied-patches
>> from_nkossifidis/1-6-ath5k-Always-write-tx-powertable-on-hw.patch
>> from_nkossifidis/2-6-ath5k-Always-free-tx-buffers-before-reset.patch
>> from_nkossifidis/3-6-ath5k-Disable-ANI-during-reset.patch
>> from_nkossifidis/4-6-ath5k-Fix-reporting-of-RX-dma-stop-failure.patch
>> from_nkossifidis/5-6-ath5k-Update-version-string.patch
>> from_nkossifidis/6-6-ath5k-Include-tx-ack-reporting-on-hw-flags.patch
>>
>> No more disconnects and no more audio-dropouts when listening to live-radio.
>> A big big big thank you!
>>
>> Shall I add to each of your patches a "Tested-by: Sedat Dilek
>> <sedat.dilek@gmail.com>?
>>
>> Kind Regards,
>> - Sedat -
>>
>
> Sure, again thanks a lot for reporting this and testing ;-)
>
> --
> GPG ID: 0xD21DB2DB
> As you read this post global entropy rises. Have Fun ;-)
> Nick
>
Hi Nick, Hi John,
Hey, approx 48hrs to get this fixed is quite good!
Can the patchset go into wireless-next-2.6?
As you remember I am on linux-next and discovered the bug from there.
OK, next linux-next refresh will be on Monday...
Regards,
- Sedat -
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [linux-next] next-20101201: ath5k permanently disconnecting
2010-12-03 6:31 ` Nick Kossifidis
2010-12-03 6:49 ` Sedat Dilek
@ 2010-12-03 16:24 ` Sedat Dilek
1 sibling, 0 replies; 22+ messages in thread
From: Sedat Dilek @ 2010-12-03 16:24 UTC (permalink / raw)
To: Nick Kossifidis
Cc: Bruno Randolf, wireless, John Linville, Stephen Rothwell,
Jonathan Guerin
On Fri, Dec 3, 2010 at 7:31 AM, Nick Kossifidis <mickflemm@gmail.com> wrote:
> 2010/12/3 Sedat Dilek <sedat.dilek@googlemail.com>:
>> On Fri, Dec 3, 2010 at 5:16 AM, Nick Kossifidis <mickflemm@gmail.com> wrote:
>>> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>>>> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>>>>> 2010/12/3 Nick Kossifidis <mickflemm@gmail.com>:
>>>>>> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>>>>>>> 2010/12/2 Nick Kossifidis <mickflemm@gmail.com>:
>>>>>>>> 2010/12/2 Sedat Dilek <sedat.dilek@googlemail.com>:
>>>>>>>>> On Wed, Dec 1, 2010 at 11:21 AM, Bruno Randolf <br1@einfach.org> wrote:
>>>>>>>>>> On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I have built today a linux-next (next-20101201) kernel which includes
>>>>>>>>>>> wireless-next-2.6 up to master-2010-11-30.
>>>>>>>>> [...]
>>>>>>>>>>> Unfortunately, my wlan network connection is totally unstable.
>>>>>>>>> [...]
>>>>>>>>>> 1.) For identification of the chipset, please:
>>>>>>>>>> dmesg |grep "ath5.*chip"
>>>>>>>>>>
>>>>>>>>>> 2.) Is there a problem when you don't use encryption?
>>>>>>>>>>
>>>>>>>>>> 3.) git bisect might help track it down.
>>>>>>>>>>
>>>>>>>>>> bruno
>>>>>>>>>
>>>>>>>>> OK, I did not a "classic" git-bisect, I created from linux-next
>>>>>>>>> (next-20101202) GIT tree a revert-ath5k patchset (30 in total).
>>>>>>>>>
>>>>>>>>> [1] VERY GOOD: Revertiing all 30 patches
>>>>>>>>>
>>>>>>>>> ...leads to a stable system.
>>>>>>>>>
>>>>>>>>> [2] REDUCED DISCONNECTIONS DROPS: Reverting 0001..0008
>>>>>>>>>
>>>>>>>>> This stabilizes the system, but... listening to a radio
>>>>>>>>> broadcast-stream with VLC is a pain in the ass... permanent audio
>>>>>>>>> dropouts. I had only 2 disconnections in the first 10mins when system
>>>>>>>>> was up (normally I can see disconnects after loggin into my KDE
>>>>>>>>> desktop).
>>>>>>>>>
>>>>>>>>> [3] GOOD AUDIO STREAMING: Reverting 0001..0014
>>>>>>>>>
>>>>>>>>> This is just fine, system like I am used to.
>>>>>>>>>
>>>>>>>>> [4] CONCLUSION
>>>>>>>>>
>>>>>>>>> So I played a bit with my revert-patchset.
>>>>>>>>>
>>>>>>>>> Reverting 0001..0008 + a refreshed v2 of
>>>>>>>>> 0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch (patch attached) is
>>>>>>>>> doing the job here.
>>>>>>>>>
>>>>>>>>> Having a closer look into 0008 (parts of
>>>>>>>>> drivers/net/wireless/ath/ath5k/reset.c):
>>>>>>>>>
>>>>>>>>> $ grep AR5212 patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>>>>>>>> - if (ah->ah_version == AR5K_AR5212)
>>>>>>>>> + * On AR5212 TSF is almost preserved across a
>>>>>>>>> - * On AR5212 TSF is almost preserved across a
>>>>>>>>> + if (ah->ah_version == AR5K_AR5212) {
>>>>>>>>> - if (ah->ah_version == AR5K_AR5212 &&
>>>>>>>>>
>>>>>>>>> As I mentionned I have a AR5212 wlan device!
>>>>>>>>> What to do with that parts?
>>>>>>>>> Any idea?
>>>>>>>>>
>>>>>>>>> Kind Regards,
>>>>>>>>> - Sedat -
>>>>>>>>>
>>>>>>>>> P.S.: I have added a list containing all commit-ids (chronological)
>>>>>>>>> and a script how I reverted (documenting for myself).
>>>>>>>>>
>>>>>>>>> $ ls patches/revert-wireless-patches/00*.patch
>>>>>>>>> patches/revert-wireless-patches/0001-Revert-ath5k-Set-turbo-bit-on-rf-bank-2.patch
>>>>>>>>> patches/revert-wireless-patches/0002-Revert-ath5k-Clean-up-turbo-mode-initvals-rfregs.patch
>>>>>>>>> patches/revert-wireless-patches/0003-Revert-ath5k-Cleanup-turbo-channel-flags.patch
>>>>>>>>> patches/revert-wireless-patches/0004-Revert-ath5k-Use-correct-clock-when-setting-ofdm-tim.patch
>>>>>>>>> patches/revert-wireless-patches/0005-Revert-ath5k-Skip-tx-power-setting-on-AR5210-for-now.patch
>>>>>>>>> patches/revert-wireless-patches/0006-Revert-ath5k-Tweak-phy-activate-to-rx-start-delay-ba.patch
>>>>>>>>> patches/revert-wireless-patches/0007-Revert-ath5k-No-need-to-save-restore-staid-flags-on-.patch
>>>>>>>>> patches/revert-wireless-patches/0008-Revert-ath5k-Support-synth-only-channel-change-for-A.patch
>>>>>>>>> patches/revert-wireless-patches/0009-Revert-ath5k-Skip-powertable-setting-when-we-are-on-.patch
>>>>>>>>> patches/revert-wireless-patches/0010-Revert-ath5k-Update-PLL-programming-for-turbo-half-q.patch
>>>>>>>>> patches/revert-wireless-patches/0011-Revert-ath5k-Update-spur-mitigation-filter-for-turbo.patch
>>>>>>>>> patches/revert-wireless-patches/0012-Revert-ath5k-Tweak-power-detector-delays-on-RF5111-R.patch
>>>>>>>>> patches/revert-wireless-patches/0013-Revert-ath5k-Always-set-IFS-intervals-on-reset.patch
>>>>>>>>> patches/revert-wireless-patches/0014-Revert-ath5k-Use-turbo-flag-on-DCU.patch
>>>>>>>>> patches/revert-wireless-patches/0015-Revert-ath5k-Set-all-IFS-intervals-not-just-slot-tim.patch
>>>>>>>>> patches/revert-wireless-patches/0016-Revert-ath5k-Extend-rate_duration.patch
>>>>>>>>> patches/revert-wireless-patches/0017-Revert-ath5k-Extend-get_default_sifs-slot_time.patch
>>>>>>>>> patches/revert-wireless-patches/0018-Revert-ath5k-Move-tx-retries-setting-outside-reset_t.patch
>>>>>>>>> patches/revert-wireless-patches/0019-Revert-ath5k-Increase-PHY-settling-parameters-for-tu.patch
>>>>>>>>> patches/revert-wireless-patches/0020-Revert-ath5k-Small-cleanup-on-tweak_initvals.patch
>>>>>>>>> patches/revert-wireless-patches/0021-Revert-ath5k-Put-core-clock-initialization-on-a-new-.patch
>>>>>>>>> patches/revert-wireless-patches/0022-Revert-ath5k-Add-new-field-on-ath5k_hw-to-track-band.patch
>>>>>>>>> patches/revert-wireless-patches/0023-Revert-ath5k-Use-new-function-to-stop-beacon-queue.patch
>>>>>>>>> patches/revert-wireless-patches/0024-Revert-ath5k-Check-RXE-when-setting-RXDP.patch
>>>>>>>>> patches/revert-wireless-patches/0025-Revert-ath5k-Use-DCU-early-termination-correctly.patch
>>>>>>>>> patches/revert-wireless-patches/0026-Revert-ath5k-Debug-DMA-timeouts.patch
>>>>>>>>> patches/revert-wireless-patches/0027-Revert-ath5k-Use-new-dma_stop-function-on-base.c.patch
>>>>>>>>> patches/revert-wireless-patches/0028-Revert-ath5k-Stop-PCU-on-reset.patch
>>>>>>>>> patches/revert-wireless-patches/0029-Revert-ath5k-Add-new-function-to-stop-rx-tx-DMA.patch
>>>>>>>>> patches/revert-wireless-patches/0030-Revert-ath5k-Reset-cleanup-and-generic-cleanup.patch
>>>>>>>>>
>>>>>>>>
>>>>>>>> OK this doesn't make any sense, based on your logs you have an
>>>>>>>> AR5212+RF5111+RF2111 combination, synth-only channel change (0008) is
>>>>>>>> only executed on AR2413 and AR5413 so you don't even run that code,
>>>>>>>> setting turbo flag on DCU (0014) is also unrelated since we never
>>>>>>>> enable turbo mode and if we did you wouldn't be able to receive
>>>>>>>> anything non-turbo.
>>>>>>>>
>>>>>>>> I am going to test 2 cards like yours a CM6 and an older one from
>>>>>>>> Atheros and come back to you ASAP...
>>>>>>>>
>>>>>>>
>>>>>>> I just reproduced it on a CM6 and a CM9 (AR5212 + RF5112), problem
>>>>>>> occurs when card is idle (no traffic) that's why my automated test
>>>>>>> didn't catch it I can still run iperf after connecting and leave it
>>>>>>> running without problems, when traffic stops it soon gets
>>>>>>> disconnected. I suspect it's something related to IFS timings/ACK
>>>>>>> timeout (0013 on your reverted series), maybe Jonathan Guerin was
>>>>>>> correct about ACK timeout...
>>>>>>>
>>>>>>> I'll try something and come back to you with code ;-)
>>>>>>>
>>>>>>> Thanks for reporting !
>>>>>>>
>>>>>>
>>>>>> Nope, it's PHY related and only affects RF5111/RF5112, AR2413 and
>>>>>> above work fine...
>>>>>>
>>>>>
>>>>> Got it, patch on the way...
>>>>>
>>>>
>>>> First the problem is with patch 22 (0009), we still need to write the
>>>> power table on hw, that fixes transmission and my CM9 works just fine
>>>> after that. Now my 2 RF5111 based cards seem to also have some problem
>>>> with stuck tx queues, after some time of fine operation (nearly
>>>> 28Mbits with iperf). It might be a hw failure or something but i want
>>>> to try and debug this further in case there is something i can do to
>>>> fix it. I also found some other things, eg. i report RX dma stop
>>>> failure when i shouldn't etc. Anyway back to debuging ;-)
>>>>
>>>>
>>>> --
>>>> GPG ID: 0xD21DB2DB
>>>> As you read this post global entropy rises. Have Fun ;-)
>>>> Nick
>>>>
>>>
>>> Done, works fine for me now, check it out ;-)
>>>
>>> --
>>> GPG ID: 0xD21DB2DB
>>> As you read this post global entropy rises. Have Fun ;-)
>>> Nick
>>>
>>
>> Hi Nick,
>>
>> I have applied the 6 patches you sent to linux-wireless list.
>>
>> $ cd $HOME/src/linux-2.6/linux-2.6.37-rc4/debian/build/source_i386_none
>>
>> $ cat .pc/applied-patches
>> from_nkossifidis/1-6-ath5k-Always-write-tx-powertable-on-hw.patch
>> from_nkossifidis/2-6-ath5k-Always-free-tx-buffers-before-reset.patch
>> from_nkossifidis/3-6-ath5k-Disable-ANI-during-reset.patch
>> from_nkossifidis/4-6-ath5k-Fix-reporting-of-RX-dma-stop-failure.patch
>> from_nkossifidis/5-6-ath5k-Update-version-string.patch
>> from_nkossifidis/6-6-ath5k-Include-tx-ack-reporting-on-hw-flags.patch
>>
>> No more disconnects and no more audio-dropouts when listening to live-radio.
>> A big big big thank you!
>>
>> Shall I add to each of your patches a "Tested-by: Sedat Dilek
>> <sedat.dilek@gmail.com>?
>>
>> Kind Regards,
>> - Sedat -
>>
>
> Sure, again thanks a lot for reporting this and testing ;-)
>
> --
> GPG ID: 0xD21DB2DB
> As you read this post global entropy rises. Have Fun ;-)
> Nick
>
Hi Nick,
any idea why I lost my pci aliases when doing a modinfo ath5k?
# modinfo ath5k
filename:
/lib/modules/2.6.37-rc4-686/kernel/drivers/net/wireless/ath/ath5k/ath5k.ko
version: 0.7.0
license: Dual BSD/GPL
description: Support for 5xxx series of Atheros 802.11 wireless LAN cards.
author: Nick Kossifidis
author: Jiri Slaby
srcversion: FB060B275A94A4A185E9AC7
depends: mac80211,cfg80211,ath
vermagic: 2.6.37-rc4-686 SMP mod_unload modversions 686
parm: debug:uint
parm: nohwcrypt:Disable hardware encryption. (bool)
parm: all_channels:Expose all channels the device can use. (bool)
Versus (paste provided by someone from IRC)
filename:
/lib/modules/2.6.32-5-openvz-amd64/kernel/drivers/net/wireless/ath/ath5k/ath5k.ko
version: 0.6.0 (EXPERIMENTAL)
license: Dual BSD/GPL
description: Support for 5xxx series of Atheros 802.11 wireless LAN cards.
author: Nick Kossifidis
author: Jiri Slaby
srcversion: 5A81CAB958F60B02DE47E18
alias: pci:v0000168Cd0000001Dsv*sd*bc*sc*i*
alias: pci:v0000168Cd0000001Csv*sd*bc*sc*i*
alias: pci:v0000168Cd0000001Bsv*sd*bc*sc*i*
alias: pci:v0000168Cd0000001Asv*sd*bc*sc*i*
alias: pci:v0000168Cd00000019sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000018sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000017sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000016sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000015sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000014sv*sd*bc*sc*i*
alias: pci:v0000168Cd00001014sv*sd*bc*sc*i*
alias: pci:v000010B7d00000013sv*sd*bc*sc*i*
alias: pci:v0000A727d00000013sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000013sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000012sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000011sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000007sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000207sv*sd*bc*sc*i*
depends: mac80211,led-class,cfg80211,ath
vermagic: 2.6.32-5-openvz-amd64 SMP mod_unload modversions
parm: nohwcrypt:Disable hardware encryption. (bool)
parm: all_channels:Expose all channels the device can use. (bool)
How do I re-create the aliases? depmod -a (did not help)?
Problem is on startup I have no wlan, I unload/reload ath5k
kernel-module and then start networking.
Uncool :-)
- Sedat -
^ permalink raw reply [flat|nested] 22+ messages in thread
end of thread, other threads:[~2010-12-03 16:24 UTC | newest]
Thread overview: 22+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-12-01 10:09 [linux-next] next-20101201: ath5k permanently disconnecting Sedat Dilek
2010-12-01 10:21 ` Bruno Randolf
2010-12-01 10:56 ` Sedat Dilek
2010-12-01 11:21 ` Sedat Dilek
2010-12-01 21:04 ` Sedat Dilek
2010-12-02 17:33 ` Sedat Dilek
2010-12-02 17:56 ` Nick Kossifidis
2010-12-02 18:23 ` Nick Kossifidis
2010-12-02 22:33 ` Nick Kossifidis
2010-12-02 22:39 ` Nick Kossifidis
2010-12-03 2:10 ` Nick Kossifidis
2010-12-03 4:16 ` Nick Kossifidis
2010-12-03 6:15 ` Sedat Dilek
2010-12-03 6:19 ` Sedat Dilek
2010-12-03 6:31 ` Nick Kossifidis
2010-12-03 6:49 ` Sedat Dilek
2010-12-03 16:24 ` Sedat Dilek
2010-12-01 22:05 ` Nick Kossifidis
2010-12-01 23:08 ` Sedat Dilek
2010-12-01 23:26 ` Sedat Dilek
2010-12-02 12:17 ` Sedat Dilek
2010-12-02 13:40 ` Sedat Dilek
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).