from:"camden lindsay"

[OpenWrt-Devel] Archer C7 CC 15.05-rc1 Ath9K phy1: Failed to stop TX DMA, queues=0x002!

2015-07-09 Thread camden lindsay

Hello-

Thought I should report this, since there was so much discussion and
confusion on tracker https://dev.openwrt.org/ticket/11862  causing a
lot of work for some folks here.


root@HACKEDBOXII.'':~# cat /etc/banner
  ___ __
 |   |.-.-.-.|  |  |  |..|  |_
 |   -   ||  _  |  -__| ||  |  |  ||   _||   _|
 |___||   __|_|__|__||||__|  ||
  |__| W I R E L E S S   F R E E D O M
 -
 CHAOS CALMER (15.05-rc1, r45695)
 -
  * 1 1/2 oz GinShake with a glassful
  * 1/4 oz Triple Sec   of broken ice and pour
  * 3/4 oz Lime Juice   unstrained into a goblet.
  * 1 1/2 oz Orange Juice
  * 1 tsp. Grenadine Syrup
 -
root@HACKEDBOXII.'':~#




root@HACKEDBOXII.'':~# iw phy phy1 info
Wiphy phy1
max # scan SSIDs: 4
max scan IEs length: 2257 bytes
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Device supports T-DLS.
Available Antennas: TX 0x7 RX 0x7
Configured Antennas: TX 0x7 RX 0x7
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* WDS
* monitor
* mesh point
* P2P-client
* P2P-GO
Band 1:
Capabilities: 0x11ef
RX LDPC
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-23
Frequencies:
* 2412 MHz [1] (23.0 dBm)
* 2417 MHz [2] (25.0 dBm)
* 2422 MHz [3] (25.0 dBm)
* 2427 MHz [4] (25.0 dBm)
* 2432 MHz [5] (25.0 dBm)
* 2437 MHz [6] (25.0 dBm)
* 2442 MHz [7] (25.0 dBm)
* 2447 MHz [8] (25.0 dBm)
* 2452 MHz [9] (25.0 dBm)
* 2457 MHz [10] (25.0 dBm)
* 2462 MHz [11] (24.0 dBm)
* 2467 MHz [12] (disabled)
* 2472 MHz [13] (disabled)
* 2484 MHz [14] (disabled)
valid interface combinations:
* #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client,
P2P-GO } <= 1, #{ IBSS } <= 1,
  total <= 2048, #channels <= 1, STA/AP BI must match
* #{ WDS } <= 2048,
  total <= 2048, #channels <= 1, STA/AP BI must match
* #{ IBSS, AP, mesh point } <= 1,
  total <= 1, #channels <= 1, STA/AP BI must match, radar detect
widths: { 20 MHz (no HT), 20 MHz, 40 MHz }

HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
root@HACKEDBOXII.'':~#


...snip...
...
[2060235.46] ath: phy1: Failed to stop TX DMA, queues=0x002!
[2060265.46] ath: phy1: Failed to stop TX DMA, queues=0x002!
[2061047.18] ath: phy1: Failed to stop TX DMA, queues=0x002!
[2104015.84] ath: phy1: Unable to reset channel, reset status -5
[2145012.92] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2145013.03] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2145013.13] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2145013.23] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2145013.33] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2145013.43] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2145013.54] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2145013.64] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2145013.74] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2158242.79] ath10k_warn: 18 callbacks suppressed
[2158242.80] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2158242.89] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2158243.00] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2158243.10] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2158243.20] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2158243.30] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2158243.41] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2158243.51] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2158243.61] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2158243.71] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
skipped old beacon
[2158245.62] [ cut here ]
[2158245.62] WARNING: CPU: 0 PID: 1302 at
/home/buildbot/slave-local/ar71xx_generic/build/build_dir/target-mips_34kc_uClibc-0.9.33.2/linux-ar71xx_generic/compat-wireless-2015-03-09/net/mac80211/sta_info.c:909
sta_set_sinfo+0x7f4/0x88c [mac80211]()
[2158245.64] Modules linked in: pppoe ppp_async iptable_nat ath9k
pppox ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_c

Re: [OpenWrt-Devel] Archer C7 CC 15.05-rc1 Ath9K phy1: Failed to stop TX DMA, queues=0x002!

2015-07-09 Thread camden lindsay

I'm sorry, i said ath9k in the subject but the above seems more likely
to be ath10k.

On Thu, Jul 9, 2015 at 7:03 PM, camden lindsay
 wrote:
> Hello-
>
> Thought I should report this, since there was so much discussion and
> confusion on tracker https://dev.openwrt.org/ticket/11862  causing a
> lot of work for some folks here.
>
>
> root@HACKEDBOXII.'':~# cat /etc/banner
>   ___ __
>  |   |.-.-.-.|  |  |  |..|  |_
>  |   -   ||  _  |  -__| ||  |  |  ||   _||   _|
>  |___||   __|_|__|__||||__|  ||
>   |__| W I R E L E S S   F R E E D O M
>  -
>  CHAOS CALMER (15.05-rc1, r45695)
>  -
>   * 1 1/2 oz GinShake with a glassful
>   * 1/4 oz Triple Sec   of broken ice and pour
>   * 3/4 oz Lime Juice   unstrained into a goblet.
>   * 1 1/2 oz Orange Juice
>   * 1 tsp. Grenadine Syrup
>  -
> root@HACKEDBOXII.'':~#
>
>
>
>
> root@HACKEDBOXII.'':~# iw phy phy1 info
> Wiphy phy1
> max # scan SSIDs: 4
> max scan IEs length: 2257 bytes
> Retry short limit: 7
> Retry long limit: 4
> Coverage class: 0 (up to 0m)
> Device supports AP-side u-APSD.
> Device supports T-DLS.
> Available Antennas: TX 0x7 RX 0x7
> Configured Antennas: TX 0x7 RX 0x7
> Supported interface modes:
> * IBSS
> * managed
> * AP
> * AP/VLAN
> * WDS
> * monitor
> * mesh point
> * P2P-client
> * P2P-GO
> Band 1:
> Capabilities: 0x11ef
> RX LDPC
> HT20/HT40
> SM Power Save disabled
> RX HT20 SGI
> RX HT40 SGI
> TX STBC
> RX STBC 1-stream
> Max AMSDU length: 3839 bytes
> DSSS/CCK HT40
> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
> Minimum RX AMPDU time spacing: 8 usec (0x06)
> HT TX/RX MCS rate indexes supported: 0-23
> Frequencies:
> * 2412 MHz [1] (23.0 dBm)
> * 2417 MHz [2] (25.0 dBm)
> * 2422 MHz [3] (25.0 dBm)
> * 2427 MHz [4] (25.0 dBm)
> * 2432 MHz [5] (25.0 dBm)
> * 2437 MHz [6] (25.0 dBm)
> * 2442 MHz [7] (25.0 dBm)
> * 2447 MHz [8] (25.0 dBm)
> * 2452 MHz [9] (25.0 dBm)
> * 2457 MHz [10] (25.0 dBm)
> * 2462 MHz [11] (24.0 dBm)
> * 2467 MHz [12] (disabled)
> * 2472 MHz [13] (disabled)
> * 2484 MHz [14] (disabled)
> valid interface combinations:
> * #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client,
> P2P-GO } <= 1, #{ IBSS } <= 1,
>   total <= 2048, #channels <= 1, STA/AP BI must match
> * #{ WDS } <= 2048,
>   total <= 2048, #channels <= 1, STA/AP BI must match
> * #{ IBSS, AP, mesh point } <= 1,
>   total <= 1, #channels <= 1, STA/AP BI must match, radar detect
> widths: { 20 MHz (no HT), 20 MHz, 40 MHz }
>
> HT Capability overrides:
> * MCS: ff ff ff ff ff ff ff ff ff ff
> * maximum A-MSDU length
> * supported channel width
> * short GI for 40 MHz
> * max A-MPDU length exponent
> * min MPDU start spacing
> root@HACKEDBOXII.'':~#
>
>
> ...snip...
> ...
> [2060235.46] ath: phy1: Failed to stop TX DMA, queues=0x002!
> [2060265.46] ath: phy1: Failed to stop TX DMA, queues=0x002!
> [2061047.18] ath: phy1: Failed to stop TX DMA, queues=0x002!
> [2104015.84] ath: phy1: Unable to reset channel, reset status -5
> [2145012.92] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
> skipped old beacon
> [2145013.03] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
> skipped old beacon
> [2145013.13] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
> skipped old beacon
> [2145013.23] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
> skipped old beacon
> [2145013.33] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
> skipped old beacon
> [2145013.43] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
> skipped old beacon
> [2145013.54] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
> skipped old beacon
> [2145013.64] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
> skipped old beacon
> [2145013.74] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
> skipped old beacon
> [2158242.79] ath10k_warn: 18 callbacks suppressed
> [2158242.80] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
> skipped old beacon
> [2158242.89] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
> skipped old beacon
> [2158243.00] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
> skipped old beacon
> [2158243.10] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
> skipped old beacon
> [2158243.20] ath10k_pci :01:00.0: SWBA overrun on

Re: [OpenWrt-Devel] Archer C7 CC 15.05-rc1 Ath9K phy1: Failed to stop TX DMA, queues=0x002!

2015-07-13 Thread camden lindsay

Thank you for noting this, Roman.
c

On Fri, Jul 10, 2015 at 10:55 PM, Roman Yeryomin  wrote:
> On 10 July 2015 at 05:07, camden lindsay
>  wrote:
>> I'm sorry, i said ath9k in the subject but the above seems more likely
>> to be ath10k.
>>
>> On Thu, Jul 9, 2015 at 7:03 PM, camden lindsay
>>  wrote:
>>> Hello-
>>>
>>> Thought I should report this, since there was so much discussion and
>>> confusion on tracker https://dev.openwrt.org/ticket/11862  causing a
>>> lot of work for some folks here.
>>>
>>> ...snip...
>>> ...
>>> [2060235.46] ath: phy1: Failed to stop TX DMA, queues=0x002!
>>> [2060265.46] ath: phy1: Failed to stop TX DMA, queues=0x002!
>>> [2061047.18] ath: phy1: Failed to stop TX DMA, queues=0x002!
>>> [2104015.84] ath: phy1: Unable to reset channel, reset status -5
>>> [2145012.92] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
>>> skipped old beacon
>>> [2145013.03] ath10k_pci :01:00.0: SWBA overrun on vdev 0,
>>> skipped old beacon
>
> It was fixed in trunk (by using newer firmware and driver).
>
> Regards,
> Roman
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] downloads.openwrt.org NOT accessible!!!

2016-02-17 Thread camden lindsay

Seems back up now...

On Sat, Feb 13, 2016 at 12:46 AM, Jakub Jančo  wrote:
> Accessible:
> $ host wiki.openwrt.org
> wiki.openwrt.org has address 188.40.166.25
>
> Not accessible:
> $ host openwrt.org
> openwrt.org has address 78.24.191.177
> openwrt.org mail is handled by 10 mail.openwrt.org.
>
> --
> S pozdravom Jakub Janco
>
>
> On Sat, Feb 13, 2016 at 9:44 AM, Jakub Jančo  wrote:
>> Hello,
>>
>> I cant access to downloads.openwrt.org.
>> This problem persist for about 3-4days.
>> Maybe it is "local" problem, but I tried 2places in SK and 1place from
>> CZ country, 2 machines, many routers.
>>
>>
>> $ host downloads.openwrt.org
>> downloads.openwrt.org has address 78.24.191.177
>>
>> $ ping 78.24.191.177
>> PING 78.24.191.177 (78.24.191.177) 56(84) bytes of data.
>> ^C
>> --- 78.24.191.177 ping statistics ---
>> 2 packets transmitted, 0 received, 100% packet loss, time 999ms
>>
>> $ wget https://downloads.openwrt.org
>> --2016-02-13 09:39:06--  https://downloads.openwrt.org/
>> Resolving downloads.openwrt.org (downloads.openwrt.org)... 78.24.191.177
>> Connecting to downloads.openwrt.org
>> (downloads.openwrt.org)|78.24.191.177|:443... failed: Connection timed
>> out.
>> Retrying.
>>
>> $ wget http://downloads.openwrt.org
>> --2016-02-13 09:39:18--  http://downloads.openwrt.org/
>> Resolving downloads.openwrt.org (downloads.openwrt.org)... 78.24.191.177
>> Connecting to downloads.openwrt.org
>> (downloads.openwrt.org)|78.24.191.177|:80... failed: Connection timed
>> out.
>> Retrying.
>>
>>
>>
>>
>> --
>> S pozdravom Jakub Janco
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Issues with Intel Wifi 7260 AC

2015-11-30 Thread camden lindsay

I use an intel 7260 with few or no problems.
I'm wondering if this line has something to do with your crashing problems
'[   23.187368] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-7260-17.ucode failed with error -2'

I'll try to remember to look tonight at my dmesg to see what it looks like.



On Mon, Nov 30, 2015 at 10:35 AM, Carlos Ferreira  wrote:
> Does anyone had any issues with the Intel 7260 AC Wi-Fi Mini-PCI Express
> card?
>
> After selecting the proper iwlwifi modules with support for the 7260 model,
> I'm plagued with this issue.
> After booting, I keep getting this output. I'm also unable to activate a
> regular configuration because the kernel module crashes.
>
> [   31.289674] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
> [   31.296625] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
> [   61.312508] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
> [   61.319333] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
> [   91.335959] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
> [   91.342763] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
> [  121.359299] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
> [  121.366101] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
> [  151.382738] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
> [  151.389539] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
>
>
>
> Below follows the full dmesg output:
> [0.00] Initializing cgroup subsys cpuset
> [0.00] Initializing cgroup subsys cpu
> [0.00] Initializing cgroup subsys cpuacct
> [0.00] Linux version 3.18.23 (claymore@manjaro) (gcc version 5.2.0
> (OpenWrt GCC 5.2.0 r47516) ) #6 SMP Mon Nov 30 01:54:01 WET 2015
> [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz
> root=PARTUUID=99c24a18-02 rootfstype=ext4 rootwait console=tty0
> console=ttyS0,115200n8 noinitrd intel_iommu=on
> [0.00] KERNEL supported cpus:
> [0.00]   Intel GenuineIntel
> [0.00] e820: BIOS-provided physical RAM map:
> [0.00] BIOS-e820: [mem 0x-0x0009abff] usable
> [0.00] BIOS-e820: [mem 0x0009ac00-0x0009]
> reserved
> [0.00] BIOS-e820: [mem 0x000e-0x000f]
> reserved
> [0.00] BIOS-e820: [mem 0x0010-0x7e1c] usable
> [0.00] BIOS-e820: [mem 0x7e1d-0x7ec06fff]
> reserved
> [0.00] BIOS-e820: [mem 0x7ec07000-0x7ed74fff] usable
> [0.00] BIOS-e820: [mem 0x7ed75000-0x7f2e] ACPI
> NVS
> [0.00] BIOS-e820: [mem 0x7f2f-0x7f647fff]
> reserved
> [0.00] BIOS-e820: [mem 0x7f648000-0x7f7f] usable
> [0.00] BIOS-e820: [mem 0xe000-0xe3ff]
> reserved
> [0.00] BIOS-e820: [mem 0xfed01000-0xfed03fff]
> reserved
> [0.00] BIOS-e820: [mem 0xfed08000-0xfed08fff]
> reserved
> [0.00] BIOS-e820: [mem 0xfed0c000-0xfed0]
> reserved
> [0.00] BIOS-e820: [mem 0xfed1c000-0xfed1cfff]
> reserved
> [0.00] BIOS-e820: [mem 0xfef0-0xfeff]
> reserved
> [0.00] BIOS-e820: [mem 0xff80-0x]
> reserved
> [0.00] BIOS-e820: [mem 0x0001-0x00027fff] usable
> [0.00] NX (Execute Disable) protection: active
> [0.00] SMBIOS 2.8 present.
> [0.00] DMI: Supermicro A1SAi/A1SAi, BIOS 1.1a 08/27/2015
> [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
> [0.00] e820: remove [mem 0x000a-0x000f] usable
> [0.00] e820: last_pfn = 0x28 max_arch_pfn = 0x4
> [0.00] MTRR default type: write-back
> [0.00] MTRR fixed ranges enabled:
> [0.00]   0-9 write-back
> [0.00]   A-B uncachable
> [0.00]   C-F write-protect
> [0.00] MTRR variable ranges enabled:
> [0.00]   0 base 08000 mask F8000 uncachable
> [0.00]   1 base 28000 mask F8000 uncachable
> [0.00]   2 base 3 mask F uncachable
> [0.00]   3 base 4 mask C uncachable
> [0.00]   4 base 8 mask 8 uncachable
> [0.00]   5 base 07F80 mask FFF80 uncachable
> [0.00]   6 disabled
> [0.00]   7 disabled
> [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new
> 0x7010600070106
> [0.00] e820: last_pfn = 0x7f800 max_arch_pfn = 0x4
> [0.00] found SMP MP-table at [mem 0x000fd8d0-0x000fd8df] mapped at
> [880fd8d0]
> [0.00] Scanning 1 areas for low memory corruption
> [0.00] Base memory trampoline at [88094000] 94000 size 24576
> [0.00] init_memory_mapping: [mem 0x-0x000f]
> [0.00]  [m

Re: [OpenWrt-Devel] Issues with Intel Wifi 7260 AC

2015-11-30 Thread camden lindsay

Here are basically all of my iwlwifi notes in dmesg, although I find
it interesting that yours calls out the interrupt. must have to do
with log level somewhere or something.

Ah, i missed before that you eventually seem to get one to load,
albeit with an error:
[   23.210567] firmware iwlwifi-7260-14.ucode: firmware_loading_store:
map pages failed

Sorry, not sure how to look further and don't know what that means.
Not good enough with source code to figure it, either.

c



[dylan@zenbook src]$ dmesg | grep -e iwlwifi -e iwlmvm | grep -i -C 6 firmware
[0.00] Linux version 4.0.4-2-iwlwifidebug (dylan@zenbook) (gcc
version 5.1.0 (GCC) ) #1 SMP PREEMPT Mon Jun 15 00:00:56 PDT 2015
[0.00] Command line:
BOOT_IMAGE=/boot/vmlinuz-linux-iwlwifidebug
root=UUID=3aefb1c6-c861-44f2-bba0-f2b3275ca492 rw
i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1
i915.semaphores=1 "acpi_osi=!Windows 2012"
[0.00] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-linux-iwlwifidebug
root=UUID=3aefb1c6-c861-44f2-bba0-f2b3275ca492 rw
i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1
i915.semaphores=1 "acpi_osi=!Windows 2012"
[3.717096] iwlwifi :02:00.0: loaded firmware version
25.17.12.0 op_mode iwlmvm
[3.749436] iwlwifi :02:00.0: Detected Intel(R) Dual Band
Wireless AC 7260, REV=0x144
[3.749581] iwlwifi :02:00.0: L1 Enabled - LTR Disabled
[3.750029] iwlwifi :02:00.0: L1 Enabled - LTR Disabled
[   11.965259] iwlwifi :02:00.0: L1 Enabled - LTR Disabled

On Mon, Nov 30, 2015 at 4:05 PM, camden lindsay
 wrote:
> I use an intel 7260 with few or no problems.
> I'm wondering if this line has something to do with your crashing problems
> '[   23.187368] iwlwifi :04:00.0: Direct firmware load for
> iwlwifi-7260-17.ucode failed with error -2'
>
> I'll try to remember to look tonight at my dmesg to see what it looks like.
>
>
>
> On Mon, Nov 30, 2015 at 10:35 AM, Carlos Ferreira  
> wrote:
>> Does anyone had any issues with the Intel 7260 AC Wi-Fi Mini-PCI Express
>> card?
>>
>> After selecting the proper iwlwifi modules with support for the 7260 model,
>> I'm plagued with this issue.
>> After booting, I keep getting this output. I'm also unable to activate a
>> regular configuration because the kernel module crashes.
>>
>> [   31.289674] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
>> [   31.296625] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
>> [   61.312508] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
>> [   61.319333] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
>> [   91.335959] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
>> [   91.342763] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
>> [  121.359299] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
>> [  121.366101] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
>> [  151.382738] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
>> [  151.389539] iwlwifi :04:00.0: iwl_trans_send_cmd bad state = 0
>>
>>
>>
>> Below follows the full dmesg output:
>> [0.00] Initializing cgroup subsys cpuset
>> [0.00] Initializing cgroup subsys cpu
>> [0.00] Initializing cgroup subsys cpuacct
>> [0.00] Linux version 3.18.23 (claymore@manjaro) (gcc version 5.2.0
>> (OpenWrt GCC 5.2.0 r47516) ) #6 SMP Mon Nov 30 01:54:01 WET 2015
>> [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz
>> root=PARTUUID=99c24a18-02 rootfstype=ext4 rootwait console=tty0
>> console=ttyS0,115200n8 noinitrd intel_iommu=on
>> [0.00] KERNEL supported cpus:
>> [0.00]   Intel GenuineIntel
>> [0.00] e820: BIOS-provided physical RAM map:
>> [0.00] BIOS-e820: [mem 0x-0x0009abff] usable
>> [0.00] BIOS-e820: [mem 0x0009ac00-0x0009]
>> reserved
>> [0.00] BIOS-e820: [mem 0x000e-0x000f]
>> reserved
>> [0.00] BIOS-e820: [mem 0x0010-0x7e1c] usable
>> [0.00] BIOS-e820: [mem 0x7e1d-0x7ec06fff]
>> reserved
>> [0.00] BIOS-e820: [mem 0x7ec07000-0x7ed74fff] usable
>> [0.00] BIOS-e820: [mem 0x7ed75000-0x7f2e] ACPI
>> NVS
>> [0.00] BIOS-e820: [mem 0x7f2f-0x7f647fff]
>> reserved
>> [0.00] BIOS-e820: [mem 0x7f648000-0x7f7f] usable
>> [0.00] BIOS-e820: [mem 0xe000-0xe3ff]
>> reserved
>> [0.00] BIOS-e820: [mem 0xfed01000-0xfed03ff

Re: [OpenWrt-Devel] [PATCH] ath79: Add SUPPORTED_DEVICES for Archer C7 v1/v2

2019-04-29 Thread camden lindsay

Adrian-
I have a C7V2 and can do some testing on it if you'd explain exactly what
you're looking for...  I don't quite follow what is needed in the above
thread.  Something about looking at PCI paths before and after an upgrade
from one version to another...
Camden

On Mon, Apr 22, 2019 at 4:45 AM  wrote:

> Hi all,
>
> > -Original Message-
> > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> > On Behalf Of David Bauer
> > Sent: Sonntag, 21. April 2019 15:19
> > To: Christian Lamparter 
> > Cc: Adrian Schmutzler ; openwrt-
> > de...@lists.openwrt.org; Tomasz Maciej Nowak 
> > Subject: Re: [OpenWrt-Devel] [PATCH] ath79: Add SUPPORTED_DEVICES for
> > Archer C7 v1/v2
> >
> > Hello Christian,
> >
> > On 21.04.19 14:17, Christian Lamparter wrote:
> > > Hello David,
> > >
> > > On Sunday, April 21, 2019 11:42:52 AM CEST David Bauer wrote:
> > >> On 20.04.19 20:59, Christian Lamparter wrote:
> > >>> On Wednesday, April 17, 2019 3:45:52 PM CEST Adrian Schmutzler wrote:
> >  The identifier for both devices is "archer-c7" on ar71xx, set here:
> > 
> > https://github.com/openwrt/openwrt/blob/master/target/linux/ar71xx/
> >  base-files/lib/ar71xx.sh#L348
> > 
> > https://github.com/openwrt/openwrt/blob/master/target/linux/ar71xx/
> >  base-files/lib/ar71xx.sh#L511
> > 
> >  Signed-off-by: Adrian Schmutzler 
> >  ---
> >    target/linux/ath79/image/generic-tp-link.mk | 2 ++
> >    1 file changed, 2 insertions(+)
> > 
> >  diff --git a/target/linux/ath79/image/generic-tp-link.mk
> >  b/target/linux/ath79/image/generic-tp-link.mk
> >  index 6853f12341..db1eabd420 100644
> >  --- a/target/linux/ath79/image/generic-tp-link.mk
> >  +++ b/target/linux/ath79/image/generic-tp-link.mk
> >  @@ -70,6 +70,7 @@ define Device/tplink_archer-c7-v1
> >  DEVICE_TITLE := TP-Link Archer C7 v1
> >  DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-
> > usbport kmod-ath10k-ct ath10k-firmware-qca988x-ct
> >  TPLINK_HWID := 0x7501
> >  +  SUPPORTED_DEVICES += archer-c7
> >    endef
> >    TARGET_DEVICES += tplink_archer-c7-v1
> > 
> >  @@ -79,6 +80,7 @@ define Device/tplink_archer-c7-v2
> >  DEVICE_TITLE := TP-Link Archer C7 v2
> >  DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-
> > usbport kmod-ath10k-ct ath10k-firmware-qca988x-ct
> >  TPLINK_HWID := 0xc702
> >  +  SUPPORTED_DEVICES += archer-c7
> > >>> In case of the v2, I think there's still the problem that a straight
> > >>> up upgrade from ar71xx to ath79 will affect the 5GHz ath10k wireless
> > >>> because it now has a new device path and hence a new default
> > >>> configuration (where the card is
> > >>> disabled) is created.
> > >>
> > >> I recall upgrading my OCEDO Koala (which uses the same 9558/9880
> > >> combo) from ar71xx to ath79 and the PCIe path being consistent on both
> > platforms.
> > >>
> > >> This however might have changed in the meantime, so someone should
> > >> probably confirm this with a real C7.
> > >
> > > On my C7 v1 with a QCA9880v2 the ar71xx installation back in
> > > 2018-08-17 looked like this:
> > >
> > > config wifi-device 'radio0'
> > >  option type 'mac80211'
> > >  option country  'DE'
> > >  option channel  'auto'
> > >  option hwmode   '11g'
> > >  option path 'platform/qca955x_wmac'
> > >  option htmode   'HT20'
> > >  option disabled '0'
> > >  option txpower  '10'
> > >
> > > config wifi-device 'radio1'
> > >  option type 'mac80211'
> > >  option channel  '52'
> > >  option country  'DE'
> > >  option hwmode   '11a'
> > >  option path 'pci:01/:01:00.0'
> > >  option htmode   'VHT80'
> > >  option disabled '0'
> > >  option txpower  '14'
> > >
> > > vs ath79 (today):
> > >
> > > config wifi-device 'radio0'
> > >  option type 'mac80211'
> > >  option country  'DE'
> > >  option channel  'auto'
> > >  option hwmode   '11g'
> > >  option path 'platform/ahb/ahb:apb/1810.wmac'
> > >  option htmode   'HT20'
> > >  option disabled '0'
> > >  option txpower  '10'
> > >
> > > config wifi-device 'radio1'
> > >  option type 'mac80211'
> > >  option channel  '52'
> > >  option country  'DE'
> > >  option hwmode   '11a'
> > >  option path 'pci:00/:00:00.0'
> > >  option htmode   'VHT80'
> > >  option disabled '0'
> > >  option txpower  '14'
> > >
> > > so the path changed from "pci:01/:01:00.0" to
>

Re: [OpenWrt-Devel] [PATCH] ath79: Add SUPPORTED_DEVICES for Archer C7 v1/v2

2019-05-01 Thread camden lindsay

Hmmm; well, i've got this; Fresh 'firstboot' on an archer c7 V2, following
version info:
root@LEDE:~# cat /etc/openwrt_*
DISTRIB_ID='LEDE'
DISTRIB_RELEASE='SNAPSHOT'
DISTRIB_REVISION='r3189-12db207'
DISTRIB_CODENAME='reboot'
DISTRIB_TARGET='ar71xx/generic'
DISTRIB_ARCH='mips_24kc'
DISTRIB_DESCRIPTION='LEDE Reboot SNAPSHOT r3189-12db207'
DISTRIB_TAINTS='no-all'
r3189-12db207
root@LEDE:~#

/etc/config/wifi has this in it:
root@LEDE:~# cat /etc/config/wireless

config wifi-device 'radio0'
option type 'mac80211'
option channel '36'
option hwmode '11a'
option path 'pci:01/:01:00.0'
option htmode 'VHT80'
option disabled '1'

config wifi-iface 'default_radio0'
option device 'radio0'
option network 'lan'
option mode 'ap'
option ssid 'LEDE'
option encryption 'none'

config wifi-device 'radio1'
option type 'mac80211'
option channel '11'
option hwmode '11g'
option path 'platform/qca955x_wmac'
option htmode 'HT20'
option disabled '1'

config wifi-iface 'default_radio1'
option device 'radio1'
option network 'lan'
option mode 'ap'
option ssid 'LEDE'
option encryption 'none'

and
root@LEDE:/sys/class/ieee80211# ls -al /sys/class/ieee80211/
drwxr-xr-x2 root root 0 Jan 27 22:39 .
drwxr-xr-x   21 root root 0 Jan  1  1970 ..
lrwxrwxrwx1 root root 0 Jan 27 22:39 phy0 ->
../../devices/pci:01/:01:00.0/ieee80211/phy0
lrwxrwxrwx1 root root 0 Jan 27 22:39 phy1 ->
../../devices/platform/qca955x_wmac/ieee80211/phy1


After upgrading using sysupgrade to stable ar71xx:
http://downloads.openwrt.org/releases/18.06.2/targets/ar71xx/generic/openwrt-18.06.2-ar71xx-generic-archer-c7-v2-squashfs-sysupgrade.bin
root@LEDE:~# cat /etc/openwrt_*
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='18.06.2'
DISTRIB_REVISION='r7676-cddd7b4c77'
DISTRIB_TARGET='ar71xx/generic'
DISTRIB_ARCH='mips_24kc'
DISTRIB_DESCRIPTION='OpenWrt 18.06.2 r7676-cddd7b4c77'
DISTRIB_TAINTS=''
r7676-cddd7b4c77
root@LEDE:~#

I should have double checked wireless config but didn't :-/  derp. I'll
rollback to this at the end and post a firstboot'd wireless config from
18.06.2.

PCI paths:
root@LEDE:~# ls -al /sys/class/ieee80211/
drwxr-xr-x2 root root 0 Jan 30 12:21 .
drwxr-xr-x   22 root root 0 Jan  1  1970 ..
lrwxrwxrwx1 root root 0 Jan 30 12:21 phy0 ->
../../devices/pci:01/:01:00.0/ieee80211/phy0
lrwxrwxrwx1 root root 0 Jan 30 12:21 phy1 ->
../../devices/platform/qca955x_wmac/ieee80211/phy1

Attempting to sysupgrade to ath79 brings this on:
root@LEDE:~# sysupgrade
/tmp/openwrt-ath79-generic-tplink_archer-c7-v2-squashfs-sysupgrade.bin
Device archer-c7 not supported by this image
Supported devices: tplink,archer-c7-v2
Image check 'fwtool_check_image' failed.
root@LEDE:~#

Forcing upgrade with -f ... After upgrading using sysupgrade to snapshot
ath79:
http://downloads.openwrt.org/snapshots/targets/ath79/generic/openwrt-ath79-generic-tplink_archer-c7-v2-squashfs-sysupgrade.bin

root@LEDE:~# cat /etc/openwrt_*
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='SNAPSHOT'
DISTRIB_REVISION='r9915-d6643aca34'
DISTRIB_TARGET='ath79/generic'
DISTRIB_ARCH='mips_24kc'
DISTRIB_DESCRIPTION='OpenWrt SNAPSHOT r9915-d6643aca34'
DISTRIB_TAINTS=''
r9915-d6643aca34
root@LEDE:~#


root@LEDE:~# ls -al /sys/class/ieee80211/
drwxr-xr-x2 root root 0 May  1 05:25 .
drwxr-xr-x   24 root root 0 Jan  1  1970 ..
lrwxrwxrwx1 root root 0 May  1 05:25 phy0 ->
../../devices/pci:00/:00:00.0/ieee80211/phy0
lrwxrwxrwx1 root root 0 May  1 05:25 phy1 ->
../../devices/platform/ahb/ahb:apb/1810.wmac/ieee80211/phy1
root@LEDE:~#

wireless config seems to have both new and old paths..
root@LEDE:~# cat /etc/config/wireless

config wifi-device 'radio0'
option type 'mac80211'
option channel '36'
option hwmode '11a'
option path 'pci:01/:01:00.0'
option htmode 'VHT80'
option disabled '1'

config wifi-iface 'default_radio0'
option device 'radio0'
option network 'lan'
option mode 'ap'
option ssid 'LEDE'
option encryption 'none'

config wifi-device 'radio1'
option type 'mac80211'
option channel '11'
option hwmode '11g'
option htmode 'HT20'
option disabled '1'
option path 'platform/ahb/ahb:apb/1810.wmac'

config wifi-iface 'default_radio1'
option device 'radio1'
option network 'lan'
option mode 'ap'
option ssid 'LEDE'
option encryption 'none'

config wifi-device 'radio2'
option type 'mac80211'
option channel '36'
option hwmode '11a'
option path 'pci:00/:00:00.0'
option htmode 'VHT80'
option disabled '1'

config wifi-iface 'default_radio2'
option device 'radio2'
option network 'lan'
option mode 'ap'
option ssid 'OpenWrt'
option encryption 'none'

root@LEDE:~#


And .. sorry its out of order, after downgrading using sysupgrade -F  to
18.06.2, then firstbooting,see as follows
root@OpenWrt:~# grep 18 /etc/openwrt_*
/etc/openwrt_release:DISTRIB_RELEASE='18.06.2'
/etc/openwrt_r

Re: [OpenWrt-Devel] [OpenWrt-Users] Is there anybody can find /var/log/dmesg in OpenWRT ?

2016-12-28 Thread camden lindsay

I believe you have to use logread-

https://wiki.openwrt.org/doc/howto/log.essentials

On Wed, Dec 28, 2016 at 10:53 PM, Tymon  wrote:
> Hi all,
>
>Why can't I find the /var/log/dmesg file under openwrt (the busybox
> built-in tool 'dmesg' is work fine)  ???
>
>Any hint will be appreciated!
>
> --
> Regards,
>
> banglang huang
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
>
> ___
> openwrt-users mailing list
> openwrt-us...@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] gigabit router !

2014-08-29 Thread camden lindsay

I was seeing >400 on the old wndr3700v2 with r29614

http://www.c-j-l.net/Home/computers/netgear_vs_buffalo_router


On Fri, Aug 29, 2014 at 1:25 PM, Weedy  wrote:

> On 29 Aug 2014 15:26, "Daniel Petre"  wrote:
> >
> > Hello,
> > is there any OpenWrt compatible gigabit router that can do more than 400
> Mbit/s WAN to LAN except linksys wrt1900ac ?
> > I know netgear wndr3700/wndr3800 and tp-link wr1043nd do around 380-400
> Mbit/s but is there any other hardware more powerful with OpenWrt support?
> > Thanks!
>
> If you benched a wr1043nd at 380mbit, the wdr4300 has a faster CPU. Same
> with the wdr4900 and wdr7500.
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] desperately seeking info on this weird MT7620A/MT7610EN dev board

2014-10-07 Thread camden lindsay

Another thought-
Are you reading the version number from the chip themselves (hardware)?
How does the current openwrt bootlog identify them?  Same way?

On Tue, Oct 7, 2014 at 5:51 PM, Aaron Z  wrote:

> On Tue, Oct 7, 2014 at 7:06 PM, Robert P. J. Day 
> wrote:
> >   finally, given that this board looks like *someone's* dev board,
> > would anyone know where it might have come from? there's no
> > manufacturer name on it anywhere. in the ramips dts file MT7620a.dts,
> > i can see a reference to a "Ralink MT7620a + MT7610e evaluation
> > board". might that be it? i'd post a pic but i signed an NDA, although
> > since no one has any idea where the board came from, i'm not sure what
> > i'd be disclosing by posting a pic.
> >
> >   i'm open to any information i can get, particularly support for that
> > MT7610EN radio chip. thanks muchly.
> Any chance that it has an FCC ID, chip model numbers or other
> regulatory body unique number on it that you could share?
> I realize that you are in Canada and its a off brand board but you
> never know, the OEM might have used the same FCC number when they
> cloned the board...
>
>
> Aaron Z
> A human being should be able to change a diaper, plan an invasion,
> butcher a hog, conn a ship, design a building, write a sonnet, balance
> accounts, build a wall, set a bone, comfort the dying, take orders,
> give orders, cooperate, act alone, solve equations, analyze a new
> problem, pitch manure, program a computer, cook a tasty meal, fight
> efficiently, die gallantly. Specialization is for insects.
> — Robert Heinlein, Time Enough for Love
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [OpenWrt-Users] note: grep-2.21 now treats ISO-8859 text files as "binary"

2014-12-11 Thread camden lindsay

Devs-

What is the proper resolution to this?

A newer version of grep breaks the feeds script for (at least ) one package
(clearsilver) in oldpackages because it recognizes the file as being binary
and reports such... ending up breaking the pattern matching in the
following script lines.

What is the appropriate way to fix this?
- Add the -a flag to offending line  to allow binary files to be treated as
text
- Set environmental flag (somehow) to force locale to C (LC_ALL=C); another
suggestion from the GNU.org folks
- Contact package maintainer and request the file locale be changed to
ASCII (If i'm not wrong the only character in it not ASCII is the
'MAINTAINER:=' field)

This will break build for anyone enabling oldpackages in their
feeds.conf(.default)

thanks
Camden


On Thu, Dec 11, 2014 at 12:49 PM, Robert P. J. Day 
wrote:

> On Thu, 11 Dec 2014, camden lindsay wrote:
>
> > If i'm reading that thread correctly, this is a 'feature' rather
> > than a 'bug'.. From that discussion:
>
> > " This is another side effect of using a multibyte locale. As long
> > as there are no NUL bytes in your input, you can work around the
> > issue by running grep in the C locale:
> >
> >   LC_ALL=C grep ...
> > "
> > "Yes, the C locale has the nice effect of EVERY byte being a valid single
> > byte character, leaving only NUL bytes and a non-empty file not ending
> > in newline as the only reasons for a file to be marked binary.
> > "
>
>   i won't argue that it's a feature, only that it has the potential to
> catch the occasional person unawares. :-P
>
> > I wonder if this is something that the devs would consider
> > patching... i'm not sure what the proper way to declare a variable
> > would be (or if they woudl want to do it)... or if it would be
> > better to use -a in that grep line.
>
>   the only gotcha i've run across is a single Makefile being
> interpreted as ISO-8859, so just fixing *that* call to "grep" would be
> sufficient.
>
> rday
>
> --
>
> 
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter:   http://twitter.com/rpjday
> LinkedIn:   http://ca.linkedin.com/in/rpjday
> 
> ___
> openwrt-users mailing list
> openwrt-us...@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
>
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Designated Driver

2015-04-07 Thread camden lindsay

+1

On Tue, Apr 7, 2015 at 12:47 PM, Hartmut Knaack  wrote:

> That Doodle poll turned out to be spamed/trolled, and everyone could even
> change or delete other votes. Since this was just communicated over this
> mailing list, and subscribers are at least basically verified, why not
> have a
> good old fashioned poll?
>
> Give your +1 answer on this mail if you prefer "Designated Driver".
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] router inaccessible in failsafe mode!!

2013-06-23 Thread camden lindsay

What device is this?
What version of OpenWRT are you running?

There is a bug open here: https://dev.openwrt.org/ticket/7502



On Sun, Jun 23, 2013 at 1:08 PM, Tomislav Požega
wrote:

> cannot access router even in failsafe mode, most likely due to roboswitch
> errors
>
> someone else reported exact same problem here -
> http://eko.one.pl/forum/viewtopic.php?id=6363
>
> log file shows errors only when entering failsafe mode:
>
> Press the [f] key and hit [enter] to enter failsafe mode
> f
> [8.056000] b44 ssb0:0: eth0: powering down PHY
> [8.064000] roboswitch: failed to write mdio reg: 24 with err -22.
> [8.072000] roboswitch: failed to write mdio reg: 16 with err -22.
> [8.08] roboswitch: failed to write mdio reg: 17 with err -22.
> [8.084000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.092000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.096000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.104000] roboswitch: timeout in robo_reg on page 52 and reg 16 with
> op 1.
> [8.112000] roboswitch: failed to write mdio reg: 24 with err -22.
> [8.116000] roboswitch: failed to write mdio reg: 16 with err -22.
> [8.124000] roboswitch: failed to write mdio reg: 17 with err -22.
> [8.132000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.136000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.144000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.148000] roboswitch: timeout in robo_reg on page 52 and reg 18 with
> op 1.
> [8.156000] roboswitch: failed to write mdio reg: 24 with err -22.
> [8.164000] roboswitch: failed to write mdio reg: 16 with err -22.
> [8.172000] roboswitch: failed to write mdio reg: 17 with err -22.
> [8.176000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.184000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.188000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.196000] roboswitch: timeout in robo_reg on page 52 and reg 20 with
> op 1.
> [8.204000] roboswitch: failed to write mdio reg: 24 with err -22.
> [8.208000] roboswitch: failed to write mdio reg: 16 with err -22.
> [8.216000] roboswitch: failed to write mdio reg: 17 with err -22.
> [8.224000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.228000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.236000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.244000] roboswitch: timeout in robo_reg on page 52 and reg 22 with
> op 1.
> [8.248000] roboswitch: failed to write mdio reg: 24 with err -22.
> [8.256000] roboswitch: failed to write mdio reg: 16 with err -22.
> [8.264000] roboswitch: failed to write mdio reg: 17 with err -22.
> [8.268000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.276000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.28] roboswitch: failed to read mdio reg 17 with err -22.
> [8.288000] roboswitch: timeout in robo_reg on page 52 and reg 24 with
> op 1.
> [8.296000] roboswitch: failed to write mdio reg: 24 with err -22.
> [8.304000] roboswitch: failed to write mdio reg: 16 with err -22.
> [8.308000] roboswitch: failed to write mdio reg: 17 with err -22.
> [8.316000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.32] roboswitch: failed to read mdio reg 17 with err -22.
> [8.328000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.336000] roboswitch: timeout in robo_reg on page 52 and reg 26 with
> op 1.
> [8.34] roboswitch: failed to write mdio reg: 24 with err -22.
> [8.348000] roboswitch: failed to write mdio reg: 25 with err -22.
> [8.356000] roboswitch: failed to write mdio reg: 16 with err -22.
> [8.36] roboswitch: failed to write mdio reg: 17 with err -22.
> [8.368000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.376000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.38] roboswitch: failed to read mdio reg 17 with err -22.
> [8.388000] roboswitch: timeout in robo_reg on page 52 and reg 8 with
> op 1.
> [8.396000] roboswitch: failed to write mdio reg: 24 with err -22.
> [8.40] roboswitch: failed to write mdio reg: 16 with err -22.
> [8.408000] roboswitch: failed to write mdio reg: 17 with err -22.
> [8.412000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.42] roboswitch: failed to read mdio reg 17 with err -22.
> [8.428000] roboswitch: failed to read mdio reg 17 with err -22.
> [8.432000] roboswitch: timeout in robo_reg on page 52 and reg 6 with
> op 1.
> [8.484000] b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex
> [8.488000] b44 ssb0:0: eth0: Flow control is off for TX and off for RX
> - failsafe -
>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openw

Re: [OpenWrt-Devel] LUCI works extremely slow...

2013-08-01 Thread camden lindsay

I am by no means an expert, but i recently did up/downgrades from 12.09 to
trunk and back (after finding 12.09 would oom during boot) using the
suggestions here:

http://wiki.openwrt.org/doc/howto/generic.sysupgrade#free.up.ram

In addition to that, i spent quite some time figureing out what all
processes i could kill without killing the router.

Good luck!



On Thu, Aug 1, 2013 at 5:55 AM, Gabriele Pinzauti <
gabriele.pinza...@witech.it> wrote:

> Hello,
> I unfortunately flashed my WRT54GL with 12.09 and then I realize that the
> web interface is now extremely slow.
> What is, in your opinion, the best practice to downgrade from 12.09 to
> 10.03.1? I am able to connect to the shell, via SSH, but I am afraid mtd
> process will be broken due to the lack of memory.
> I also would be able to TFTP a new firmware, since boot_wait should be on.
>
> root@OpenWrt:/# nvram get boot_wait
> on
> root@OpenWrt:/#
>
> Suggestions are strongly appreciated.
>
> Thanks.
> Gabriele
>
> 2013/6/12 Wojciech Kromer 
>
>> W dniu 12.06.2013 10:55, Wojciech Kromer pisze:
>>
>>
>>> With my rt3052,16MB RAM,4MB SPI-FLASH so far
>>> - trunk is unusable
>>> - AA seems to work even with LUCI
>>>
>>> Anyway
>>> - in AA rt3052 wifi crashes at start,
>>>   this was solved in trunk, but I do not know how to backport it
>>>
>>
>> OK, there is quick and dirty workaround here https://dev.openwrt.org/**
>> ticket/13532 
>>
>> After enabling WiFi everything slows down, especially LUCI.
>>
>>
>>
>> Best regards.
>>
>> __**_
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.**org 
>> https://lists.openwrt.org/**mailman/listinfo/openwrt-devel
>>
>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Trunk build no /etc/init.d/firewall, uci firewall references

2013-11-17 Thread camden lindsay

Hello-
Has something changed with options during build required to have the
firewall scripts in the base image?

I built an image from trunk this morning to upgrade my router.
I am not doing anything special in make menuconfig other than setting
target system and profile.


But once i do an mtd write of the image, there does not appear to be any
configuration for the firewall in uci, (/etc/config) nor in startup scripts
(/etc/init.d)

root@OpenWrt:/tmp# mtd write -r
openwrt-ar71xx-generic-wzr-hp-ag300h-squashfs-sysupgrade.bin firmware
Unlocking firmware ...

Writing from openwrt-ar71xx-generic-wzr-hp-ag300h-squashfs-sysupgrade.bin
to firmware ...
Rebooting ...
Write failed: Broken pipe
dylan@BigBox ~ $ telnet 192.168.1.1
Trying 192.168.1.1...
Connected to 192.168.1.1.
Escape character is '^]'.
 === IMPORTANT 
  Use 'passwd' to set your login password
  this will disable telnet and enable SSH
 --


BusyBox v1.19.4 (2013-11-17 08:55:26 PST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  ___ __
 |   |.-.-.-.|  |  |  |..|  |_
 |   -   ||  _  |  -__| ||  |  |  ||   _||   _|
 |___||   __|_|__|__||||__|  ||
  |__| W I R E L E S S   F R E E D O M
 -
 BARRIER BREAKER (Bleeding Edge, r38840)
 -
  * 1/2 oz Galliano Pour all ingredients into
  * 4 oz cold Coffeean irish coffee mug filled
  * 1 1/2 oz Dark Rum   with crushed ice. Stir.
  * 2 tsp. Creme de Cacao
 -
root@OpenWrt:/# uci show firewall
uci: Entry not found
root@OpenWrt:/# uci show | grep firewall
root@OpenWrt:/#
root@OpenWrt:/# ls -l /etc/config
-rw-r--r--1 root root   687 Nov 17  2013 6relayd
-rw-r--r--1 root root   885 Nov 17  2013 dhcp
-rw-r--r--1 root root   134 Nov 17  2013 dropbear
-rw---1 root root   675 Jan  1 00:00 network
-rw---1 root root   659 Jan  1 00:00 system
-rw---1 root root   115 Jan  1 00:00 ubootenv
-rw-r--r--1 root root   884 Jan  1 00:00 wireless
root@OpenWrt:/#

root@OpenWrt:/# ls -l /etc/init.d/
-rwxr-xr-x1 root root  4096 Nov 17  2013 6relayd
-rwxr-xr-x1 root root  1988 Nov 16  2013 boot
-rwxr-xr-x1 root root   418 Nov 17  2013 cron
-rwxr-xr-x1 root root   318 May 14  2013 defconfig
-rwxr-xr-x1 root root 13151 Nov 17  2013 dnsmasq
-rwxr-xr-x1 root root   308 May 14  2013 done
-rwxr-xr-x1 root root  3920 Nov 17  2013 dropbear
-rwxr-xr-x1 root root  2015 May 14  2013 led
-rwxr-xr-x1 root root  1389 Nov 17  2013 log
-rwxr-xr-x1 root root   729 Nov 16  2013 network
-rwxr-xr-x1 root root   126 May 14  2013 sysctl
-rwxr-xr-x1 root root   742 Nov 17  2013 sysntpd
-rwxr-xr-x1 root root   926 Nov 17  2013 telnet
-rwxr-xr-x1 root root   102 May 14  2013 umount
root@OpenWrt:/#

What am I missing?

Thank you
Camden
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Trunk build no /etc/init.d/firewall, uci firewall references

2013-11-18 Thread camden lindsay

I found this must have been an error on my part.
I cleared everythign out and re-synced.
Somehow OpenWrt C Firewall  had been cleared in my .config.

Sorry for the disturbance.
Camden


On Sun, Nov 17, 2013 at 11:24 AM, camden lindsay <
camden.lindsay+open...@gmail.com> wrote:

> Hello-
> Has something changed with options during build required to have the
> firewall scripts in the base image?
>
> I built an image from trunk this morning to upgrade my router.
> I am not doing anything special in make menuconfig other than setting
> target system and profile.
>
>
> But once i do an mtd write of the image, there does not appear to be any
> configuration for the firewall in uci, (/etc/config) nor in startup scripts
> (/etc/init.d)
>
> root@OpenWrt:/tmp# mtd write -r
> openwrt-ar71xx-generic-wzr-hp-ag300h-squashfs-sysupgrade.bin firmware
> Unlocking firmware ...
>
> Writing from openwrt-ar71xx-generic-wzr-hp-ag300h-squashfs-sysupgrade.bin
> to firmware ...
> Rebooting ...
> Write failed: Broken pipe
> dylan@BigBox ~ $ telnet 192.168.1.1
> Trying 192.168.1.1...
> Connected to 192.168.1.1.
> Escape character is '^]'.
>  === IMPORTANT 
>   Use 'passwd' to set your login password
>   this will disable telnet and enable SSH
>  --
>
>
> BusyBox v1.19.4 (2013-11-17 08:55:26 PST) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
>
>   ___ __
>  |   |.-.-.-.|  |  |  |..|  |_
>  |   -   ||  _  |  -__| ||  |  |  ||   _||   _|
>  |___||   __|_|__|__||||__|  ||
>   |__| W I R E L E S S   F R E E D O M
>  -
>  BARRIER BREAKER (Bleeding Edge, r38840)
>  -
>   * 1/2 oz Galliano Pour all ingredients into
>   * 4 oz cold Coffeean irish coffee mug filled
>   * 1 1/2 oz Dark Rum   with crushed ice. Stir.
>   * 2 tsp. Creme de Cacao
>  -
> root@OpenWrt:/# uci show firewall
> uci: Entry not found
> root@OpenWrt:/# uci show | grep firewall
> root@OpenWrt:/#
> root@OpenWrt:/# ls -l /etc/config
> -rw-r--r--1 root root   687 Nov 17  2013 6relayd
> -rw-r--r--1 root root   885 Nov 17  2013 dhcp
> -rw-r--r--1 root root   134 Nov 17  2013 dropbear
> -rw---1 root root   675 Jan  1 00:00 network
> -rw---1 root root   659 Jan  1 00:00 system
> -rw---1 root root   115 Jan  1 00:00 ubootenv
> -rw-r--r--1 root root   884 Jan  1 00:00 wireless
> root@OpenWrt:/#
>
> root@OpenWrt:/# ls -l /etc/init.d/
> -rwxr-xr-x1 root root  4096 Nov 17  2013 6relayd
> -rwxr-xr-x1 root root  1988 Nov 16  2013 boot
> -rwxr-xr-x1 root root   418 Nov 17  2013 cron
> -rwxr-xr-x1 root root   318 May 14  2013 defconfig
> -rwxr-xr-x1 root root 13151 Nov 17  2013 dnsmasq
> -rwxr-xr-x1 root root   308 May 14  2013 done
> -rwxr-xr-x1 root root  3920 Nov 17  2013 dropbear
> -rwxr-xr-x1 root root  2015 May 14  2013 led
> -rwxr-xr-x1 root root  1389 Nov 17  2013 log
> -rwxr-xr-x1 root root   729 Nov 16  2013 network
> -rwxr-xr-x1 root root   126 May 14  2013 sysctl
> -rwxr-xr-x1 root root   742 Nov 17  2013 sysntpd
> -rwxr-xr-x1 root root   926 Nov 17  2013 telnet
> -rwxr-xr-x1 root root   102 May 14  2013 umount
> root@OpenWrt:/#
>
> What am I missing?
>
> Thank you
> Camden
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Keep settings broken on NetGear WNDR3800

2012-12-04 Thread camden lindsay

Hello, John

I'm no expert, but think there should be some additional information, if
you could include it.

--Are you upgrading using luci, or using sysupgrade?

If using luci, could you show the output of:
uci show luci.flash_keep

If using sysupgrade, could you show output of:
cat /etc/sysupgrade.conf

You may have already checked these files, but without posting the
information in your intial email, its hard to know.

take care--
c
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Trunk build no /etc/init.d/firewall, uci firewall references

2013-11-30 Thread camden lindsay

Thank you for the pointers.

c


On Tue, Nov 26, 2013 at 3:40 PM, Weedy  wrote:

> After using OpenWRT for years with almost 0 issues this is my workflow.
>
> weedy@HAF ~/projects/openwrt $ svn up . && make V=3 package/symlinks
> weedy@HAF ~/projects/openwrt $ cat configs/tl-wdr4300-home.config
> CONFIG_TARGET_ar71xx=y
> CONFIG_TARGET_ar71xx_generic=y
> CONFIG_TARGET_ar71xx_generic_TLWDR4300=y
> weedy@HAF ~/projects/openwrt $ cat configs/base-no-LUCI.config
> CONFIG_PACKAGE_bmon=y
> CONFIG_PACKAGE_darkstat=y
> CONFIG_PACKAGE_ddns-scripts=y
> CONFIG_PACKAGE_iftop=y
> CONFIG_PACKAGE_iperf=y
> CONFIG_PACKAGE_iptables-mod-conntrack-extra=y
> CONFIG_PACKAGE_iwinfo=y
> CONFIG_PACKAGE_kmod-ipt-conntrack-extra=y
> CONFIG_PACKAGE_miniupnpd=y
> CONFIG_PACKAGE_muninlite=y
> CONFIG_PACKAGE_qos-scripts=y
> CONFIG_PACKAGE_screen=y
> CONFIG_PACKAGE_tcpdump=y
> CONFIG_PACKAGE_uhttpd=y
> CONFIG_PACKAGE_wpad=y
> weedy@HAF ~/projects/openwrt $ cp -p configs/tl-wdr4300-home.config
> .config
> weedy@HAF ~/projects/openwrt $ cat configs/base-no-LUCI.config >> .config
> weedy@HAF ~/projects/openwrt $ make V=99 defconfig && nice -n 15 make V=s
> -j2
>
> Forcing deps to be resolved every time I update SVN has removed all "well
> shit" moments from updates.
> You can add a "make V=99 oldconfig" after the package/symlinks if you want
> to see changes, but normally skimming over the svn output is enough to keep
> on top of things.
>
> Your "seed config" should be top level changes only. Do not add deps, just
> the packages you want in the final image. jow/mbm/nbd have done a very good
> job of making the build system resolve deps.
>
> Hope this makes your life easier.
>
> On Mon, Nov 18, 2013 at 7:55 PM, camden lindsay <
> camden.lindsay+open...@gmail.com> wrote:
>
>> I found this must have been an error on my part.
>> I cleared everythign out and re-synced.
>> Somehow OpenWrt C Firewall  had been cleared in my .config.
>>
>> Sorry for the disturbance.
>> Camden
>>
>>
>> On Sun, Nov 17, 2013 at 11:24 AM, camden lindsay <
>> camden.lindsay+open...@gmail.com> wrote:
>>
>>> Hello-
>>> Has something changed with options during build required to have the
>>> firewall scripts in the base image?
>>>
>>> I built an image from trunk this morning to upgrade my router.
>>> I am not doing anything special in make menuconfig other than setting
>>> target system and profile.
>>>
>>>
>>> But once i do an mtd write of the image, there does not appear to be any
>>> configuration for the firewall in uci, (/etc/config) nor in startup scripts
>>> (/etc/init.d)
>>>
>>> root@OpenWrt:/tmp# mtd write -r
>>> openwrt-ar71xx-generic-wzr-hp-ag300h-squashfs-sysupgrade.bin firmware
>>> Unlocking firmware ...
>>>
>>> Writing from
>>> openwrt-ar71xx-generic-wzr-hp-ag300h-squashfs-sysupgrade.bin to firmware ...
>>> Rebooting ...
>>> Write failed: Broken pipe
>>> dylan@BigBox ~ $ telnet 192.168.1.1
>>> Trying 192.168.1.1...
>>> Connected to 192.168.1.1.
>>> Escape character is '^]'.
>>>  === IMPORTANT 
>>>   Use 'passwd' to set your login password
>>>   this will disable telnet and enable SSH
>>>  --
>>>
>>>
>>> BusyBox v1.19.4 (2013-11-17 08:55:26 PST) built-in shell (ash)
>>> Enter 'help' for a list of built-in commands.
>>>
>>>   ___ __
>>>  |   |.-.-.-.|  |  |  |..|  |_
>>>  |   -   ||  _  |  -__| ||  |  |  ||   _||   _|
>>>  |___||   __|_|__|__||||__|  ||
>>>   |__| W I R E L E S S   F R E E D O M
>>>  -
>>>  BARRIER BREAKER (Bleeding Edge, r38840)
>>>  -
>>>   * 1/2 oz Galliano Pour all ingredients into
>>>   * 4 oz cold Coffeean irish coffee mug filled
>>>   * 1 1/2 oz Dark Rum   with crushed ice. Stir.
>>>   * 2 tsp. Creme de Cacao
>>>  -
>>> root@OpenWrt:/# uci show firewall
>>> uci: Entry not found
>>> root@OpenWrt:/# uci show | grep firewall
>>> root@OpenWrt:/#
>>> root@OpenWrt:/# ls -l /etc/config
>>> -rw-r--r--1 root root   687 Nov 17  2013 6relayd
>

Re: [OpenWrt-Devel] Android connectivity issues - MyNet n600

2014-01-28 Thread camden lindsay

I'm no expert, but you could try running hostapd in debug mode and 'Capture
Management Traffic' to see what you can find:
See http://wiki.openwrt.org/doc/devel/debugging




On Tue, Jan 28, 2014 at 4:59 AM, omggo  wrote:

> Hi all,
>
> I've come up against an issue with my "MyNet n600" on both the 5ghz and
> 2.4ghz radios. I'm currently using the latest trunk (r39406).
>
> I have an Android phone which will authenticate and stay connected but
> loses all network connectivity. Any other non Android device will stay
> connected and continue to work.
>
> This is similar to the fixed issue "AR9344 wifi dying on WD N600 routers"
> but it's happening on both radios and only with the Android device.
>
> Restarting the device restores connectivity to the Android device for a
> moment but then it loses it again.
>
> There are no messages in the logs to indicate that something has gone
> wrong.
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] How to use ethernet port as lan or wan port in WR703N

2014-02-17 Thread camden lindsay

It sounds like you have to re-configure the switch, to have the port
that is currently 'wan' on the same vlan as the LAN.

see http://wiki.openwrt.org/doc/uci/network/switch

On Mon, Feb 17, 2014 at 2:04 PM, jonsm...@gmail.com  wrote:
> On Mon, Feb 17, 2014 at 4:48 PM, Hartmut Knaack  wrote:
>> jonsm...@gmail.com schrieb:
>>> The switch (esw) configuration separates the LAN and WAN ports.
>> But according to the wiki, the 703n has only one ethernet port and no switch.
>
> AR9331 has the switch on chip.
> http://www.eeboard.com/wp-content/uploads/downloads/2013/08/AR9331.pdf
>
>
>>>
>>> On Mon, Feb 17, 2014 at 4:07 PM, Hartmut Knaack  wrote:
 bjzhougong schrieb:
> Dear Sirs.
>
>>> As we know, we can configure "network.lan.interface" or 
>>> "network.wan.interface" as eth0 to use ethernet port as lan or wan port 
>>> on WR703N.
>>> I think it should need to do anything in driver for switch ethernet 
>>> port,
>>> and I want to know what happened between user space and kernel space 
>>> after we run "/etc/init.d/network restart",
>>> Thanks for any idea about this!
> If there is any help? Thanks!
 Not sure, what exactly you want to know. When running "/etc/init.d/network 
 restart", all the configured options in /etc/config/network get 
 configured. See http://wiki.openwrt.org/doc/uci/network for more 
 information about available options.
 When changing a certain network device from WAN to LAN, it is mainly about 
 switching the configuration from being DHCP master or slave, and some 
 routing configurations.
> --
> bjzhougong
>
>
>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>>>
>>>
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
>
>
> --
> Jon Smirl
> jonsm...@gmail.com
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] dev.openwrt.org frequently gives 504 Gateway Time-out or 502 Bad Gateway errors

2014-03-05 Thread camden lindsay

Look forward to not having to fight the spam-captcha issue as much anymore heh.
Thank you for your efforts, Jow.


On Tue, Mar 4, 2014 at 3:26 AM, Jo-Philipp Wich  wrote:
> Hi.
>
>> It is really annoying that dev.openwrt.org frequently gives "504 Gateway
>> Time-out" or "502 Bad Gateway" errors. During the last few days it seems
>> that the bug tracker is unreachable half of the time.
>>
>> Typical error is just:
>>
>> 502 Bad Gateway
>> nginx/1.1.19
>>
>> Is there some problem connectivity problem between the front-end and
>> back-end servers?
>
> It is a problem with python. So far we used an ordinary tracd-fcgi setup
> behind an nginx frontend. Problem was that tracd instances gobbled up
> memory like crazy - up to 5GB of reserved memory after a runtime of ~1
> hour was not unusual. Furthermore the observed cpu consumption on the
> server was 90-350% (!) for single trac processes.
>
> Additionally trac runs into threading deadlocks after a while, resulting
> in a total unavailabily of the backend, thus leading to the infamous 50x
> errors. This seems to be a general thread locking issue either due to a
> bug in python or in the trac codebase.
>
> I reworked the trac-fcgi launcher now and applied a number of threading
> fixes to it, so far it seems to be way more responsive and both memory
> consumption and cpu load plummeted to 50MB RAM / 10% CPU per instance.
>
> On a first glance the result seems promising and the site is way more
> responsive now. I also fixed the ticket captcha mechanism so submitting
> tickets erroneously flagged as spam should work properly now.
>
>
> Regards,
> Jow
>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Archer C7 CC 15.05-rc1 Ath9K phy1: Failed to stop TX DMA, queues=0x002!

Re: [OpenWrt-Devel] Archer C7 CC 15.05-rc1 Ath9K phy1: Failed to stop TX DMA, queues=0x002!

Re: [OpenWrt-Devel] Archer C7 CC 15.05-rc1 Ath9K phy1: Failed to stop TX DMA, queues=0x002!

Re: [OpenWrt-Devel] downloads.openwrt.org NOT accessible!!!

Re: [OpenWrt-Devel] Issues with Intel Wifi 7260 AC

Re: [OpenWrt-Devel] Issues with Intel Wifi 7260 AC

Re: [OpenWrt-Devel] [PATCH] ath79: Add SUPPORTED_DEVICES for Archer C7 v1/v2

Re: [OpenWrt-Devel] [PATCH] ath79: Add SUPPORTED_DEVICES for Archer C7 v1/v2

Re: [OpenWrt-Devel] [OpenWrt-Users] Is there anybody can find /var/log/dmesg in OpenWRT ?

Re: [OpenWrt-Devel] gigabit router !

Re: [OpenWrt-Devel] desperately seeking info on this weird MT7620A/MT7610EN dev board

Re: [OpenWrt-Devel] [OpenWrt-Users] note: grep-2.21 now treats ISO-8859 text files as "binary"

Re: [OpenWrt-Devel] Designated Driver

Re: [OpenWrt-Devel] router inaccessible in failsafe mode!!

Re: [OpenWrt-Devel] LUCI works extremely slow...

[OpenWrt-Devel] Trunk build no /etc/init.d/firewall, uci firewall references

Re: [OpenWrt-Devel] Trunk build no /etc/init.d/firewall, uci firewall references

Re: [OpenWrt-Devel] Keep settings broken on NetGear WNDR3800

Re: [OpenWrt-Devel] Trunk build no /etc/init.d/firewall, uci firewall references

Re: [OpenWrt-Devel] Android connectivity issues - MyNet n600

Re: [OpenWrt-Devel] How to use ethernet port as lan or wan port in WR703N

Re: [OpenWrt-Devel] dev.openwrt.org frequently gives 504 Gateway Time-out or 502 Bad Gateway errors

22 matches

Site Navigation

Mail list logo

Footer information