Hi Bastian,

I did some tests with and without traffic on Ethernet. And your guess on
problem with Ethernet PHY is most likely right. The router never freezes
when there is no traffic coming from Ethernet. It is fine with the traffic
going out of Ethernet. It is fine with wlan0 traffic as well. It's only the
incoming Ethernet traffic that causes the freeze.
I've raised a ticket for this problem in Openwrt. Hopefully the problem
will be solved.

I've added CONFIG_SWAP=y to trunk/target/linux/atheros/config3.3 and I
still can't see zram in the base system. Am I missing something?

Regards,
Siva.

On Fri, Mar 8, 2013 at 6:00 AM, <openwrt-devel-requ...@lists.openwrt.org>wrote:

> Send openwrt-devel mailing list submissions to
>         openwrt-devel@lists.openwrt.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> or, via email, send a message with subject or body 'help' to
>         openwrt-devel-requ...@lists.openwrt.org
>
> You can reach the person managing the list at
>         openwrt-devel-ow...@lists.openwrt.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of openwrt-devel digest..."
>
>
> Today's Topics:
>
>    1. [PATCH v2 003/003] [ar71xx] add profile support for
>       dir-835-a1 (Alexander Stadler)
>    2. Re: Init script (Sivateja Patibandla)
>    3. Re: om2p-hs: System lockup with 'ath: phy0: PLL4 meaurement
>       not done' error (Paul van Gool)
>    4. Re: om2p-hs: System lockup with 'ath: phy0: PLL4  meaurement
>       not done' error (Marek Lindner)
>    5. Re: Init script (Bastian Bittorf)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 07 Mar 2013 19:45:31 +0100
> From: Alexander Stadler <sa.open...@univie.ac.at>
> To: OpenWrt Development List <openwrt-devel@lists.openwrt.org>
> Subject: [OpenWrt-Devel] [PATCH v2 003/003] [ar71xx] add profile
>         support for     dir-835-a1
> Message-ID: <5138e04b.3080...@univie.ac.at>
> Content-Type: text/plain; charset=ISO-8859-15
>
> From: Alexander Stadler <sa.mailli...@univie.ac.at>
>
> profile support for dir-835-a1
>
> Signed-off-by: Alexander Stadler <sa.mailli...@univie.ac.at>
> ---
> support implemented within the mach-dir-825-c1.c like requested
> diff -urN 
> a/target/linux/ar71xx/generic/profiles/d-link.mkb/target/linux/ar71xx/generic/profiles/
> d-link.mk
> --- a/target/linux/ar71xx/generic/profiles/d-link.mk    2013-02-24
> 18:43:51.000000000 +0100
> +++ b/target/linux/ar71xx/generic/profiles/d-link.mk    2013-02-24
> 18:55:12.000000000 +0100
> @@ -72,3 +72,14 @@
>  endef
>
>  $(eval $(call Profile,DIR825C1))
> +
> +define Profile/DIR835A1
> +       NAME:=D-Link DIR-835 rev. A1
> +       PACKAGES:=kmod-usb-core kmod-usb2
> +endef
> +
> +define Profile/DIR835A1/Description
> +       Package set optimized for the D-Link DIR-835 rev. A1.
> +endef
> +
> +$(eval $(call Profile,DIR835A1))
> diff -urN a/target/linux/ar71xx/image/Makefile
> b/target/linux/ar71xx/image/Makefile
> --- a/target/linux/ar71xx/image/Makefile        2013-03-05
> 17:53:43.000000000 +0100
> +++ b/target/linux/ar71xx/image/Makefile        2013-03-05
> 19:49:38.000000000 +0100
> @@ -859,6 +859,7 @@
>  $(eval $(call
> SingleProfile,Cameo933x,$(fs_squash),TEW712BR,tew-712br,TEW-712BR,ttyATH0,115200,"HORNET-RT-TEW712BR-3"))
>
>  $(eval $(call
> SingleProfile,Cameo934x,$(fs_64k),DIR825C1,dir-825-c1,DIR-825-C1,ttyS0,115200,"00DB120AR9344-RT-101214-00"))
> +$(eval $(call
> SingleProfile,Cameo934x,$(fs_64k),DIR835A1,dir-835-a1,DIR-835-A1,ttyS0,115200,"00DB120AR9344-RT-101214-00"))
>
>  $(eval $(call
> SingleProfile,CyberTAN,$(fs_64k),WRT160NL,wrt160nl,WRT160NL,ttyS0,115200,1.00.01))
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 7 Mar 2013 20:41:51 -0500
> From: Sivateja Patibandla <patibandl...@vcu.edu>
> To: OpenWrt Development List <openwrt-devel@lists.openwrt.org>
> Subject: Re: [OpenWrt-Devel] Init script
> Message-ID:
>         <
> ca+lehhgpjfmnlwrey8+rjkic95_kjbst4hvrflhnmi-dotr...@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Bastian,
>
> Thank you for the information. I enabled "paging of anonymous memory"
> option and now I'm able to see the swap memory being used.
>
> But the system still freezes at least 40% of the times I tested. It freezes
> in the first 5 min of the boot up or it will never freeze. I also see that
> most of the times for the same set of programs running, swap space used is
> not more than 4-16 KB out of total available 6140 KB. I tried with
> different swappiness values ranging from 10-100 but all had the same
> problems. Does it mean that the swap space is actually not playing a role
> at all? If so,  is there a way to force the system to use swap space as
> much as possible (other than setting swappiness)?
>
> I'd love to send a patch but I'm not really sure about the changes that I
> have to make here? Do I just change the .config in /trunk directory and add
> CONFIG_SWAP=y. I tried that, but could not see the zram option in
> menuconfig->base system. I also added CONFIG_SWAP=y to
> trunk/target/linux/config-3.8 but the zram does not show up in base system.
> Is there something that I'm missing? Sorry, I'm new to the build process
> and patches.
>
> I appreciate your time. Thank you.
>
> Regards,
> Siva.
>
> On Thu, Mar 7, 2013 at 7:57 AM, Bastian Bittorf <bitt...@bluebottle.com
> >wrote:
>
> > * Sivateja Patibandla <patibandl...@vcu.edu> [07.03.2013 13:49]:
> > > Hi Bastian,
> > >
> > > I tried the revisions 35863-35865 but I can't see zram under make
> > > menuconfig->base system when the Target System is Atheros AR231X. Zram
> > > option shows up for the target system AR7XXX but I'm working with
> AR231X.
> > > Any comments or suggestions?
> >
> > yes, for the atheros target "swap" is not activated in kernelconfig:
> >
> https://lists.openwrt.org/pipermail/openwrt-devel/2013-January/018217.html
> >
> > activate and look again into menuconfig.
> > btw: send a patch for this...
> >
> > bye, bastian
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.openwrt.org/pipermail/openwrt-devel/attachments/20130307/a6a23bfe/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Thu, 7 Mar 2013 18:28:01 -0800
> From: Paul van Gool <pvang...@gmail.com>
> To: Marek Lindner <lindner_ma...@yahoo.de>
> Cc: openwrt-devel@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] om2p-hs: System lockup with 'ath: phy0:
>         PLL4 meaurement not done' error
> Message-ID:
>         <
> camd4qhnc_mgguvn8va6-cafzbdujzn3bect-+stu+xg88tv...@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Marek,
>
> I have verified that r35506 does not have that problem. No more of that
> messages in dmesg, and I can see SSID beacons.
>
> Thanks!
>
> Paul
>
> On Thu, Mar 7, 2013 at 6:43 AM, Paul van Gool <pvang...@gmail.com> wrote:
>
> > Thanks, Marek! I will try that revision.
> >
> > Paul
> >
> >
> > On Thu, Mar 7, 2013 at 2:13 AM, Marek Lindner <lindner_ma...@yahoo.de
> >wrote:
> >
> >> On Thursday, March 07, 2013 07:51:00 Paul van Gool wrote:
> >> > so I built r35506 and flashed my OM2P-HS with it. As before booting
> the
> >> > device work fine (which is different than what Petr observed).
> >> >
> >> > [..]
> >> >
> >> > And I never see any SSID beacons.
> >> >
> >> > So do you have wifi up on your OM2P-HS?
> >>
> >> You are right - I forgot that OpenWrt disables wifi per default. After
> >> enabling it I do see the same problem. I checked out revision 33803 and
> >> built
> >> a new image. This is the revision when my platform OM2P-HS patches were
> >> merged. That version works perfectly fine with wifi enabled.
> >>
> >> This smells like an ath9k regression potentially introduced by this
> patch:
> >>
> >> f18e3c6b67f448ec47b3a5b242789bd3d5644879
> >> Author: Mohammed Shafi Shajakhan <moham...@qca.qualcomm.com>
> >> Date:   Mon Jun 18 13:13:30 2012 +0530
> >>
> >>     ath9k_hw: avoid possible infinite loop in ar9003_get_pll_sqsum_dvc
> >>
> >>     "ath9k: Fix softlockup in AR9485" with commit id
> >>     64bc1239c790e051ff677e023435d770d2ffa174 fixed the reported
> >>     issue, yet its better to avoid the possible infinite loop
> >>     in ar9003_get_pll_sqsum_dvc by having a timeout as suggested
> >>     by ath9k maintainers.
> >>     http://www.spinics.net/lists/linux-wireless/msg92126.html.
> >>     Based on my testing PLL's locking measurement is done in
> >>     ~200us (2 iterations).
> >>
> >>     Cc: sta...@vger.kernel.org
> >>     Cc: Rolf Offermanns <rolf.offerma...@gmx.net>
> >>     Cc: Sujith Manoharan <c_man...@qca.qualcomm.com>
> >>     Cc: Senthil Balasubramanian <senth...@qca.qualcomm.com>
> >>     Signed-off-by: Mohammed Shafi Shajakhan <moham...@qca.qualcomm.com>
> >>     Signed-off-by: John W. Linville <linvi...@tuxdriver.com>
> >>
> >> You might want to bring this issue to the ath9k / linux wireless mailing
> >> list.
> >>
> >> Cheers,
> >> Marek
> >>
> >>
> >
> >
> > --
> > Paul van Gool
> > pvang...@gmail.com
> >
>
>
>
> --
> Paul van Gool
> pvang...@gmail.com
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.openwrt.org/pipermail/openwrt-devel/attachments/20130307/2d588eea/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 4
> Date: Fri, 8 Mar 2013 11:38:48 +0800
> From: Marek Lindner <lindner_ma...@yahoo.de>
> To: openwrt-devel@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] om2p-hs: System lockup with 'ath: phy0:
>         PLL4    meaurement not done' error
> Message-ID: <201303081138.48883.lindner_ma...@yahoo.de>
> Content-Type: Text/Plain;  charset="iso-8859-15"
>
> On Friday, March 08, 2013 10:28:01 Paul van Gool wrote:
> > I have verified that r35506 does not have that problem. No more of that
> > messages in dmesg, and I can see SSID beacons.
>
> You are welcome. I think AA could be fixed too if you contact the mac80211
> maintainer to let him know about this regression.
>
> Cheers,
> Marek
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 8 Mar 2013 08:29:30 +0100
> From: Bastian Bittorf <bitt...@bluebottle.com>
> To: OpenWrt Development List <openwrt-devel@lists.openwrt.org>
> Subject: Re: [OpenWrt-Devel] Init script
> Message-ID: <20130308072930.gg8...@medion.lan>
> Content-Type: text/plain; charset=us-ascii
>
> * Sivateja Patibandla <patibandl...@vcu.edu> [08.03.2013 08:12]:
> >
> > But the system still freezes at least 40% of the times I tested. It
> freezes
>
> we also see freezes on all our atheros nodes, at least once a day,
> no matter if swap is used or not (we have some 32mb nodes also).
>
> > problems. Does it mean that the swap space is actually not playing a
> > role at all?
>
> looks like it.
>
> > If so,  is there a way to force the system to use swap space as
> > much as possible (other than setting swappiness)?
>
> you can set swappincess to 100, but i think this is not
> your/our problem. i bet it has something to to with the ehternet-phy
> and or the missing watchdog or an compile/toolchain issue (bad generated
> code). can you open a ticket about this and share your problems?
>
> > I'd love to send a patch but I'm not really sure about the changes that I
> > have to make here? Do I just change the .config in /trunk directory and
> add
> > CONFIG_SWAP=y. I tried that, but could not see the zram option in
> > menuconfig->base system. I also added CONFIG_SWAP=y to
> > trunk/target/linux/config-3.8 but the zram does not show up in base
> system.
>
> use trunk/target/linux/config-3.3, IMHO atheros is still at 3.3.8
>
> bye, bastian
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
>
> ------------------------------
>
> End of openwrt-devel Digest, Vol 87, Issue 20
> *********************************************
>
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to