Help with testing the AP+Client Bug
Moderator: Moderators
Re: Help with testing the AP+Client Bug
13708 works out of the box
- DoesItMatter
- Moderator
- Posts: 1373
- Joined: Thu May 21, 2009 3:56 pm
Re: Help with testing the AP+Client Bug
13708 seems to be working quite well!
8+ hours uptime - connection stayed up - no drop.
8+ hours uptime - connection stayed up - no drop.
- Attachments
-
- madwifi-13708.png (14.54 KiB) Viewed 7650 times


2x Asus RT-N16 = Asus 3.0.0.4.374.43 Merlin
2x Buffalo WZR-HP-G300NH V1 A0D0 = Gargoyle 1.9.x / LEDE 17.01.x
2x Engenius - ESR900 Stock 1.4.0 / OpenWRT Trunk 49400
- DoesItMatter
- Moderator
- Posts: 1373
- Joined: Thu May 21, 2009 3:56 pm
Re: Help with testing the AP+Client Bug
Didn't want to edit the prior post...
Uptime 24+ hours and counting with build 13708!
Looks like this one is a keeper!
Uptime 24+ hours and counting with build 13708!
Looks like this one is a keeper!
- Attachments
-
- 13708-uptime.png (5.81 KiB) Viewed 7622 times


2x Asus RT-N16 = Asus 3.0.0.4.374.43 Merlin
2x Buffalo WZR-HP-G300NH V1 A0D0 = Gargoyle 1.9.x / LEDE 17.01.x
2x Engenius - ESR900 Stock 1.4.0 / OpenWRT Trunk 49400
Re: Help with testing the AP+Client Bug
Ok, here's the deal. No more one-revision-at a time. Time for a shotgun approach!
There are a bunch of revisions below. These revisions isolate changes in the madwifi package. There's at most one commit that makes changes to madwifi between revisions. If we can find between which of these revision ap+client breaks, it will be possible to isolate the cause of the bug.
Pick one in the middle of the list. If it works we eliminate the need to test everything before it. If it breaks we eliminate everything after it. Then repeat, picking a revision in the middle of the remaining list. I'll eliminate revisions for which the need to test has been eliminated as testing proceeds. Ideally I'd like two people to confirm a release works/breaks before eliminating anything from the list. As soon as you get results for a release post below (in this thread!).
There's a bunch of releases here, so it may take some time. As always, all of your help is very much appreciated!
m13761
gargoyle_1.0.2_m13761-atheros-root.squashfs
gargoyle_1.0.2_m13761-atheros-vmlinux.lzma
gargoyle_1.0.2_m13761-atheros-vmlinux.gz
m13794
gargoyle_1.0.2_m13794-atheros-root.squashfs
gargoyle_1.0.2_m13794-atheros-vmlinux.lzma
gargoyle_1.0.2_m13794-atheros-vmlinux.gz
m13796
gargoyle_1.0.2_m13796-atheros-root.squashfs
gargoyle_1.0.2_m13796-atheros-vmlinux.lzma
gargoyle_1.0.2_m13796-atheros-vmlinux.gz
m14000
gargoyle_1.0.2_m14000-atheros-root.squashfs
gargoyle_1.0.2_m14000-atheros-vmlinux.lzma
gargoyle_1.0.2_m14000-atheros-vmlinux.gz
m14200
gargoyle_1.0.2_m14200-atheros-root.squashfs
gargoyle_1.0.2_m14200-atheros-vmlinux.lzma
gargoyle_1.0.2_m14200-atheros-vmlinux.gz
m14400
gargoyle_1.0.2_m14400-atheros-root.squashfs
gargoyle_1.0.2_m14400-atheros-vmlinux.lzma
gargoyle_1.0.2_m14400-atheros-vmlinux.gz
m15408
gargoyle_1.0.2_m15408-atheros-root.squashfs
gargoyle_1.0.2_m15408-atheros-vmlinux.lzma
gargoyle_1.0.2_m15408-atheros-vmlinux.gz
m15409
gargoyle_1.0.2_m15409-atheros-root.squashfs
gargoyle_1.0.2_m15409-atheros-vmlinux.lzma
gargoyle_1.0.2_m15409-atheros-vmlinux.gz
There are a bunch of revisions below. These revisions isolate changes in the madwifi package. There's at most one commit that makes changes to madwifi between revisions. If we can find between which of these revision ap+client breaks, it will be possible to isolate the cause of the bug.
Pick one in the middle of the list. If it works we eliminate the need to test everything before it. If it breaks we eliminate everything after it. Then repeat, picking a revision in the middle of the remaining list. I'll eliminate revisions for which the need to test has been eliminated as testing proceeds. Ideally I'd like two people to confirm a release works/breaks before eliminating anything from the list. As soon as you get results for a release post below (in this thread!).
There's a bunch of releases here, so it may take some time. As always, all of your help is very much appreciated!
m13761
gargoyle_1.0.2_m13761-atheros-root.squashfs
gargoyle_1.0.2_m13761-atheros-vmlinux.lzma
gargoyle_1.0.2_m13761-atheros-vmlinux.gz
m13794
gargoyle_1.0.2_m13794-atheros-root.squashfs
gargoyle_1.0.2_m13794-atheros-vmlinux.lzma
gargoyle_1.0.2_m13794-atheros-vmlinux.gz
m13796
gargoyle_1.0.2_m13796-atheros-root.squashfs
gargoyle_1.0.2_m13796-atheros-vmlinux.lzma
gargoyle_1.0.2_m13796-atheros-vmlinux.gz
m14000
gargoyle_1.0.2_m14000-atheros-root.squashfs
gargoyle_1.0.2_m14000-atheros-vmlinux.lzma
gargoyle_1.0.2_m14000-atheros-vmlinux.gz
m14200
gargoyle_1.0.2_m14200-atheros-root.squashfs
gargoyle_1.0.2_m14200-atheros-vmlinux.lzma
gargoyle_1.0.2_m14200-atheros-vmlinux.gz
m14400
gargoyle_1.0.2_m14400-atheros-root.squashfs
gargoyle_1.0.2_m14400-atheros-vmlinux.lzma
gargoyle_1.0.2_m14400-atheros-vmlinux.gz
m15408
gargoyle_1.0.2_m15408-atheros-root.squashfs
gargoyle_1.0.2_m15408-atheros-vmlinux.lzma
gargoyle_1.0.2_m15408-atheros-vmlinux.gz
m15409
gargoyle_1.0.2_m15409-atheros-root.squashfs
gargoyle_1.0.2_m15409-atheros-vmlinux.lzma
gargoyle_1.0.2_m15409-atheros-vmlinux.gz
- DoesItMatter
- Moderator
- Posts: 1373
- Joined: Thu May 21, 2009 3:56 pm
Re: Help with testing the AP+Client Bug
Build 14000 loaded and running on Fonera 2201+
Running 2 hours so far - no issues.
Anyone else test this to verify?
I'll leave it another 2 hours, if its 4+ hours, I'll consider it OK, as any
prior bad builds usually flaked out in 30 mins or less.
I'll try build 14400 next and see if any issues with that build.
-------------------
Edit - 4+ hours and still going - this build looks good - flashing 14400 now
Running 2 hours so far - no issues.
Anyone else test this to verify?
I'll leave it another 2 hours, if its 4+ hours, I'll consider it OK, as any
prior bad builds usually flaked out in 30 mins or less.
I'll try build 14400 next and see if any issues with that build.
-------------------
Edit - 4+ hours and still going - this build looks good - flashing 14400 now
- Attachments
-
- madwifi-14000.png (5.77 KiB) Viewed 7585 times
Last edited by DoesItMatter on Tue Aug 04, 2009 5:06 am, edited 1 time in total.


2x Asus RT-N16 = Asus 3.0.0.4.374.43 Merlin
2x Buffalo WZR-HP-G300NH V1 A0D0 = Gargoyle 1.9.x / LEDE 17.01.x
2x Engenius - ESR900 Stock 1.4.0 / OpenWRT Trunk 49400
Re: Help with testing the AP+Client Bug
my 14000 failed
will test again
will test again
Re: Help with testing the AP+Client Bug
I rebooted my meraki router and this time it worked
I'm not sure what to do now?
I'm not sure what to do now?
- DoesItMatter
- Moderator
- Posts: 1373
- Joined: Thu May 21, 2009 3:56 pm
Re: Help with testing the AP+Client Bug
----------ispyisail wrote:I rebooted my meraki router and this time it worked
I'm not sure what to do now?
I'm trying the 14400 build next since 14000 worked.
------------
OK, 14400 has been up for 8 + hours now.
SEEMS to be working, but I do notice pauses and the connection
seems to hang after about 8 hours. It will pause like there's no
internet connection, and then it starts to work again.
The AP and Client never show disconnection, but there are some
pauses in the internet after 8 hours.
Maybe we're getting close to the problem build?
I will re-load build 14000 and see if after 8+ hours there are pauses
in the internet and streaming video.
- Attachments
-
- madwifi-14400.jpg (12.47 KiB) Viewed 7574 times


2x Asus RT-N16 = Asus 3.0.0.4.374.43 Merlin
2x Buffalo WZR-HP-G300NH V1 A0D0 = Gargoyle 1.9.x / LEDE 17.01.x
2x Engenius - ESR900 Stock 1.4.0 / OpenWRT Trunk 49400
Re: Help with testing the AP+Client Bug
14000 has been up for 11 hours now and with no problems. Tonight I will re flash 14000 to double check my first results