New Build 36330 (BS):07-16-2018-r36330

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page 1, 2, 3, 4  Next
Author Message
flood404
DD-WRT User


Joined: 18 Dec 2013
Posts: 227

PostPosted: Mon Jul 16, 2018 22:42    Post subject: New Build 36330 (BS):07-16-2018-r36330 Reply with quote
Downloads at: ftp://ftp.dd-wrt.com/betas/2018/07-16-2018-r36330/


Notes:
1. SFE accelerated NAT is in 33006+ builds but only in kernel 3.10 and newer
2. krack fixes for Broadcom were completed in r33678, including k26 (33655) & k24 (33656); use build 33772 or later.
3. Bridge modes on k4.4 devices may sometimes work in some configurations in certain builds but are not supported by the bcmdhd driver. Use client or repeater instead as WDS doesn't work with Broadcom ARM either (see Issue #4 below).

Tickets closed as 'fixed' (Broadcom-related and general):

Issues, observations, and/or workarounds reported:
1. (egc) Policy-Based Routing broken if SFE enabled: http://svn.dd-wrt.com/ticket/5900
quarkysg's PBR+SFE fix: http://svn.dd-wrt.com/ticket/5986
2. Trendnet 81*DRU models are missing factory-to-flash, and 811/812v2 are too big to flash: http://svn.dd-wrt.com/ticket/6144
Sizes since build 36233 are reduced for the 8MB models, 811 might be ok now; 812 appears to need more:
trendnet-811dru-webflash.bin 26-Jun-2018 7987220 7.6172MB
trendnet-812dru-webflash.bin 26-Jun-2018 8134676 7.7578MB
3. DNScrypt is mostly only using v2 protocols now, but requires Golang that DD can't use:
http://svn.dd-wrt.com/ticket/6246
4. WDS does not work on ARM devices (only MIPS<->MIPS)

Important: if any issues are found, please provide log info (GUI syslog, `dmesg`, `cat /var/log/messages`).
Or put in SVN ticket. For firewall issues, also provide "iptables" info (`iptables -L`, `iptables -t nat -L`, & the /tmp/.ipt file).

Template to copy (after "Code:") for posting a reply, be sure to include the mode in use (gateway, AP, CB, etc.):
Code:
Router/Version:
File:
Kernel:
Mode:
Status:

WARNING: This build thread is for reporting success and/or problems with loading this experimental test build.
This is important info for developers and users. Always state your hardware model, version, mode (e.g. Repeater) and SPECIFIC build (e.g. 33555_NEWD-2_K3.x_mega-nv64k.bin). Create a new thread to discuss specific problems or questions, and refrain to respond as this thread is for reporting, not support. Posts not meeting this criteria may be deleted or moved to keep this thread manageable and useful. If you don't understand the risks or what to flash and how, with a means of recovery if it bricks, do NOT flash this experimental test build.
_________________



Router/Version: 3700v3
File: dd-wrt.v24-36330_NEWD-2_K3.x_mega-nv64k.bin
Kernel: k3.x
Mode: AP
Status: Working

Router/Version: WRT320N
File: dd-wrt.v24-36330_NEWD-2_K2.6_mini_wrt320n.bin
Kernel: k2.6x
Mode: AP
Status: Working


So far its fine on a X64 system also.


Last edited by flood404 on Wed Jul 18, 2018 5:38; edited 2 times in total
Sponsor
chenshaoju
DD-WRT User


Joined: 10 Apr 2008
Posts: 93
Location: Chinese Mainland

PostPosted: Tue Jul 17, 2018 2:31    Post subject: Reply with quote
Router/Version: Netgear R7000
File: Netgear-r7000-webflash.bin
Kernel: Linux 4.4.140 #3516 SMP Mon Jul 16 11:58:39 CEST 2018 armv7l
Mode: Router/AP/VAP
Reset: no
Status: VAP not working.

The VAP still not working, After boot, The VAP SSID can see in the client wifi list, But unable connect, If waiting for few minutes, The VAP SSID is disappeared.

This issue last knows the good version is 35531.

Here is dmesg and messages logs from 36330.



dmesg.txt
 Description:

Download
 Filename:  dmesg.txt
 Filesize:  9.94 KB
 Downloaded:  427 Time(s)


messages.txt
 Description:

Download
 Filename:  messages.txt
 Filesize:  27.48 KB
 Downloaded:  468 Time(s)


_________________
NetGear R7000
DD-WRT v3.0-r35531 std ( 03/26/18 )
Mile-Lile
DD-WRT Guru


Joined: 24 Feb 2013
Posts: 1521
Location: Belgrade

PostPosted: Tue Jul 17, 2018 7:00    Post subject: Reply with quote
Router Model Netgear R6250
Firmware Version DD-WRT v3.0-r36330 std (07/16/1Cool
Kernel Version Linux 4.4.140 #3516 SMP Mon Jul 16 11:58:39 CEST 2018 armv7l


Mode: Gateway PPPoE, AP 2.4 + 5
Fetures: Unbound + dhcpd, LAN Domain, QoS (HTB + Fq_CoDel + nDPi Services Priority A+,A,A+), Remote logging, Remote Access (Web+SSH)

Status: Working
Reset: No
Errors: Can't make HFSC + PIE work no matter what I do...

Thx BS and Chris, you really do amazing work with ddwrt!
mwchang
DD-WRT Guru


Joined: 26 Mar 2013
Posts: 739
Location: Hung Hom, Hong Kong

PostPosted: Tue Jul 17, 2018 15:36    Post subject: Re: New Build 36247 (BS):07-16-2018-r36330 Reply with quote
flood404 wrote:
New Build 36247 (BS):07-16-2018-r36330

Why is "Build 36247" mentioned in the subject line for this build "r36330"? Careless mistake?

Should we just skip this build because of this little mistake? It could be an omen... Meow!!! >@.@<


_________________
Router: Asus RT-N18U (rev. A1)

May the Force and farces be with you! Live long and proper!

Facebook: https://www.facebook.com/changmanwai
Website: https://sites.google.com/site/changmw
SETI@Home profile: http://setiathome.berkeley.edu/view_profile.php?userid=211832
MvEICT
DD-WRT Novice


Joined: 11 Jul 2018
Posts: 24

PostPosted: Tue Jul 17, 2018 18:28    Post subject: VAP still not working Reply with quote
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r36330 (07/16/1Cool
Mode: Router, WAN disabled
Status: Not working properly with virtual interfaces

Indeed, VAP is still not working on 2.4 GHz radio.

I tested this new firmware (reset before and after installation) and wl0 and wl1 are working properly until you add a virtual interface.....then wl0.1 is visible but wl0 disappears....

What I noticed is that with newer firmware versions, the VAP get the mac address of wl0/eth1 (the 2.4 GHz radio) and with an older working firmware version the VAP get the mac address of wl1/eth2 (5GHz radio).
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 5398
Location: Texas

PostPosted: Tue Jul 17, 2018 19:38    Post subject: Reply with quote
E2500
DD-WRT v3.0-r36330 [07/16/18]
Linux 3.10.108-d3 #20116 Mon Jul 16 18:34:44 CEST 2018 mips

VAP still don't work... it broadcast a MAC now but can't connect and after few seconds physical (wl0) will disapear.
flyzipper
DD-WRT User


Joined: 21 Feb 2016
Posts: 452

PostPosted: Tue Jul 17, 2018 21:06    Post subject: Reply with quote
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r36330 std ( 07/16/18 )
Kernel: Linux 4.4.140 #3516 SMP Mon Jul 16 11:58:39 CEST 2018 armv7l
Previous: r36247
Mode/Status: Gateway / working
Reset: no
Issues/Errors: None so far.

Uptime: 14m
Temperatures: CPU 74.7 °C / WL0 50.5 °C / WL1 54.0 °C

Brimmy
DD-WRT User


Joined: 29 Mar 2015
Posts: 381

PostPosted: Tue Jul 17, 2018 21:16    Post subject: Reply with quote
Router/Version: Buffalo WZR-1750DHP/DHPD
Firmware:DD-WRT v3.0-r36330 std (07/16/18
Kernel: Linux 4.4.140 #3516 SMP Mon Jul 16 11:58:39 CEST 2018 armv7l
Previous: BSr34760
Mode/Status: Gateway / WIFI = AP / Seems ok
CPU overclocked to 1200mhz from default 800mhz via r33006
Reset: no
Issues/Errors: DNSCrypt V1 kills internet connection
UpTime: 30min

What i have noticed:-
1) with builds higher than r34760, i cannot telnet to the router after a flash even when i reset to factory defaults and reset the CPU OC to default and too, when i run the erase nvram in the WebGUI, i always get this message in CMD....C:\Windows\system32>telnet 192.168.1.1
Connecting To 192.168.1.1...Could not open connection to the host, on port 23: Connect failed. BS r34760 uses BusyBox v1.28.0 (2018-01-30 10:34:39 CET) built-in shell (ash)
2) throuth put is buggy with CTF and QoS enabled and if you disable CTF and leave QoS, however CTF gives full bandwidth with lowest consistant ping times. I used dslreports, speedtest.net (html5) and speedof.me.
3) while testing the throughput on each site, speedof.me seems to give a more true realtime assessment of the through put and it almost always shows a rapid decline in bandwidth when it reaches the 64mb download sample when CTF and QoS are enabled.
4) on the wzr 1750DHP/DHPD the bridge is always bridge name=br0 STP=no Interface=eth1 eth2 vlan1 and on the wzr 1750DHP, the bridge is bridge name=br0 STP=no Interface=eth1 eth2 vlan1 and then changes to bridge name=br0 STP=no Interface=vlan1 eth1 eth2 and i have no idea how or why this happens. I have never changed nor tampered with the vlan and have always left it default. I only noticed this one today and i am currently checking to see what past builds present this issue.
pci 0000:00:10.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)

This time i will only give the dmesg because i see different readings for the 1750DHP and the 1750DHPD and maybe this can help in finding any issues.

1) wzr-1750dhp dmesg
pci 0000:00:08.0: [14e4:0501] type 00 class 0xffffff
pci 0000:00:08.0: reg 0x10: [mem 0x18013000-0x18013fff]
pci 0000:00:08.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:09.0: [14e4:0501] type 00 class 0xffffff
pci 0000:00:09.0: reg 0x10: [mem 0x18014000-0x18014fff]
pci 0000:00:09.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0a.0: [14e4:0510] type 00 class 0xffffff
pci 0000:00:0a.0: reg 0x10: [mem 0x1800b000-0x1800bfff]
pci 0000:00:0a.0: reg 0x14: [mem 0x1800c000-0x1800cfff]
pci 0000:00:0a.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0b.0: [14e4:471a] type 00 class 0x0c0310
pci 0000:00:0b.0: reg 0x10: [mem 0x18022000-0x18022fff]
pci 0000:00:0b.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0b.1: [14e4:471a] type 00 class 0x0c0320
pci 0000:00:0b.1: reg 0x10: [mem 0x18021000-0x18021fff]
pci 0000:00:0b.1: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0c.0: [14e4:472a] type 00 class 0x0c0330
pci 0000:00:0c.0: reg 0x10: [mem 0x18023000-0x18023fff]
pci 0000:00:0c.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0d.0: [14e4:0503] type 00 class 0xffffff
pci 0000:00:0d.0: reg 0x10: [mem 0x18020000-0x18020fff]
pci 0000:00:0d.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0e.0: [14e4:0506] type 00 class 0xffffff
pci 0000:00:0e.0: reg 0x10: [mem 0x18210000-0x1821ffff]
pci 0000:00:0e.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0f.0: [14e4:0507] type 00 class 0xffffff
pci 0000:00:0f.0: reg 0x10: [mem 0x18010000-0x18010fff]
pci 0000:00:0f.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:10.0: [14e4:0508] type 00 class 0xffffff
pci 0000:00:10.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)
pci 0000:00:10.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:11.0: [14e4:0509] type 00 class 0xffffff
pci 0000:00:11.0: reg 0x10: [mem 0x18028000-0x18028fff]
pci 0000:00:11.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:12.0: [14e4:050a] type 00 class 0xffffff
pci 0000:00:12.0: reg 0x10: [mem 0x18029000-0x18029fff]
pci 0000:00:12.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
PCI: Fixing up bus 0 domain 0
PCIE1 link=1
PCIE1 switching to GEN2
PCIE1 link=1
PCI host bridge to bus 0001:00
pci_bus 0001:00: root bus resource [mem 0x08000000-0x0fffffff]
pci_bus 0001:00: No busn resource found for root bus, will use [bus 00-ff]
pci 0001:00:00.0: [14e4:8011] type 01 class 0x060400
pci 0001:00:00.0: PME# supported from D0 D3hot D3cold
PCI: Fixing up bus 0 domain 1
PCI: bus0: Fast back to back transfers disabled
pci 0001:01:00.0: [14e4:4360] type 00 class 0x028000
pci 0001:01:00.0: reg 0x10: [mem 0x08000000-0x08007fff 64bit]
pci 0001:01:00.0: Max Payload Size set to 512 (was 128, max 512)
pci 0001:01:00.0: supports D1 D2
PCI: Fixing up bus 1 domain 1
PCI: bus1: Fast back to back transfers disabled
pci_bus 0001:01: busn_res: [bus 01-ff] end is updated to 01
pci_bus 0001:00: busn_res: [bus 00-ff] end is updated to 01
pci 0001:00:00.0: BAR 8: assigned [mem 0x08000000-0x080fffff]
pci 0001:01:00.0: BAR 0: assigned [mem 0x08000000-0x08007fff 64bit]
pci 0001:00:00.0: PCI bridge to [bus 01]
pci 0001:00:00.0: bridge window [mem 0x08000000-0x080fffff]
PCIE2 link=1
PCIE2 switching to GEN2
PCIE2 link=1
PCI host bridge to bus 0002:00
pci_bus 0002:00: root bus resource [mem 0x40000000-0x47ffffff]
pci_bus 0002:00: No busn resource found for root bus, will use [bus 00-ff]
pci 0002:00:00.0: [14e4:8011] type 01 class 0x060400
pci 0002:00:00.0: PME# supported from D0 D3hot D3cold
PCI: Fixing up bus 0 domain 2
PCI: bus0: Fast back to back transfers disabled
pci 0002:01:00.0: [14e4:4331] type 00 class 0x028000
pci 0002:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
pci 0002:01:00.0: can't set Max Payload Size to 512; if necessary, use "pci=pcie_bus_safe" and report a bug
pci 0002:01:00.0: supports D1 D2
PCI: Fixing up bus 1 domain 2
PCI: bus1: Fast back to back transfers disabled
pci_bus 0002:01: busn_res: [bus 01-ff] end is updated to 01
pci_bus 0002:00: busn_res: [bus 00-ff] end is updated to 01
pci 0002:00:00.0: BAR 8: assigned [mem 0x40000000-0x400fffff]
pci 0002:01:00.0: BAR 0: assigned [mem 0x40000000-0x40003fff 64bit]
pci 0002:00:00.0: PCI bridge to [bus 01]
pci 0002:00:00.0: bridge window [mem 0x40000000-0x400fffff]
PCIE3 link=0
squashfs: version 4.0 (2009/01/31) Phillip Lougher
io scheduler noop registered (default)
io scheduler cfq registered
serial8250_init
Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
console [ttyS0] disabled
serial8250.0: ttyS0 at MMIO 0x18000300 (irq = 117, base_baud = 6250000) is a 16550
console [ttyS0] enabled
serial8250.0: ttyS1 at MMIO 0x18000400 (irq = 117, base_baud = 6250000) is a 16550
brd: module loaded
loop: module loaded
Boot partition size = 2097152(0x200000)
Creating 3 MTD partitions on "bcmsflash":
0x000000000000-0x000000200000 : "boot"
mtd: partition "boot" extends beyond the end of device "bcmsflash" -- size truncated to 0x100000
0x0000000f0000-0x000000100000 : "nvram_cfe"
0x0000000e0000-0x0000000f0000 : "nvram"
Found a Esmt NAND flash:
Total size: 128MB
Block size: 128KB
Page Size: 2048B
OOB Size: 64B
Sector size: 512B
Spare size: 16B
ECC level: 8 (8-bit)
Device ID: 0x92 0xf1 0x80 0x95 0x40 0x7f
lookup_nflash_rootfs_offset: offset = 0x0 size = 0x2000000, 0x20000
found TRX Header on nflash!
nflash: squash filesystem with lzma found at block 13
Creating 2 MTD partitions on "nflash":
0x000000000000-0x000002000000 : "linux"
0x0000001a0000-0x000002000000 : "rootfs"
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
GACT probability NOT on
Mirror/redirect action on
Simple TC action Loaded
netem: version 1.3
u32 classifier
Performance counters on
input device check on
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (8036 buckets, 32144 max)
nf_conntrack_rtsp v0.7 loading
xt_time: kernel timezone is -0000
ip_set: protocol 6
gre: GRE over IPv4 demultiplexor driver
nf_nat_rtsp v0.7 loading
ip_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 17
bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
Registering SWP/SWPB emulation handler
found cfe nvram
check if nvram copy is required CFE Size is 65536
nvram copy magic is 48534C46
max nvram space = 131072
read 65536 bytes to offset 0
Key type encrypted registered
Northstar brcmnand NAND Flash Controller driver, Version 0.1 (c) Broadcom Inc. 2012
nand: device found, Manufacturer ID: 0x92, Chip ID: 0xf1
nand: Eon NAND 128MiB 3,3V 8-bit
nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Spare area=64 eccbytes 56, ecc bytes located at:
2 3 4 5 6 7 8 9 10 11 12 13 14 15 18 19 20 21 22 23 24 25 26 27 28 29 30 31 34 35 36 37 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 60 61 62 63
Available 7 bytes at (off,len):
(1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0)
Scanning device for bad blocks
Bad eraseblock 1023 at 0x000007fe0000
Options: NO_SUBPAGE_WRITE,
Creating 1 MTD partitions on "brcmnand":
0x000002000000-0x000008000000 : "ddwrt"
VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
Freeing unused kernel memory: 348K
et: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
et_module_init: passivemode set to 0x0
et_module_init: txworkq set to 0x0
et_module_init: et_txq_thresh set to 0x400
et_module_init: et_rxlazy_timeout set to 0x3e8
et_module_init: et_rxlazy_framecnt set to 0x20
et_module_init: et_rxlazy_dyn_thresh set to 0
ET Corerev 5
eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.89.21 (r524987)
roboswitch: Probing device 'eth0'
roboswitch: trying a 53011! at eth0
detected CPU Port is 5
roboswitch: found a 53011! at eth0
detected CPU Port is 5
wl_module_init: passivemode set to 0x0
wl_module_init: txworkq set to 0x0
eth1: Broadcom BCM4360 802.11 Wireless Controller 7.14.89.21 (r524987)
PCI: Enabling device 0002:01:00.0 (0140 -> 0142)
eth2: Broadcom BCM4331 802.11 Wireless Controller 7.14.89.21 (r524987)
eth0: mixed HW and IP checksum settings.
device br0 entered promiscuous mode
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
br0: port 1(vlan1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
device eth1 entered promiscuous mode
br0: port 2(eth1) entered forwarding state
br0: port 2(eth1) entered forwarding state
device eth2 entered promiscuous mode
br0: port 3(eth2) entered forwarding state
br0: port 3(eth2) entered forwarding state
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
device vlan2 entered promiscuous mode
IMQ: use 2 as queue number
IMQ driver loaded successfully. (numdevs = 2, numqueues = 2, imq_dev_accurate_stats = 1)
Hooking IMQ before NAT on PREROUTING.
Hooking IMQ after NAT on POSTROUTING.
random: dnsmasq: uninitialized urandom read (128 bytes read, 95 bits of entropy available)
random: dnsmasq: uninitialized urandom read (48 bytes read, 95 bits of entropy available)
device vlan2 left promiscuous mode
random: nonblocking pool is initialized
IMQ driver unloaded successfully.
IMQ: use 2 as queue number
IMQ driver loaded successfully. (numdevs = 2, numqueues = 2, imq_dev_accurate_stats = 1)
Hooking IMQ before NAT on PREROUTING.
Hooking IMQ after NAT on POSTROUTING.
IMQ driver unloaded successfully.
IMQ: use 2 as queue number
IMQ driver loaded successfully. (numdevs = 2, numqueues = 2, imq_dev_accurate_stats = 1)
Hooking IMQ before NAT on PREROUTING.
Hooking IMQ after NAT on POSTROUTING.
br0: port 1(vlan1) entered forwarding state
br0: port 2(eth1) entered forwarding state
br0: port 3(eth2) entered forwarding state

~~~~~~~~~~~~~~~

wzr-1750dhpd dmesg
pci 0000:00:08.0: [14e4:0501] type 00 class 0xffffff
pci 0000:00:08.0: reg 0x10: [mem 0x18013000-0x18013fff]
pci 0000:00:08.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:09.0: [14e4:0501] type 00 class 0xffffff
pci 0000:00:09.0: reg 0x10: [mem 0x18014000-0x18014fff]
pci 0000:00:09.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0a.0: [14e4:0510] type 00 class 0xffffff
pci 0000:00:0a.0: reg 0x10: [mem 0x1800b000-0x1800bfff]
pci 0000:00:0a.0: reg 0x14: [mem 0x1800c000-0x1800cfff]
pci 0000:00:0a.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0b.0: [14e4:471a] type 00 class 0x0c0310
pci 0000:00:0b.0: reg 0x10: [mem 0x18022000-0x18022fff]
pci 0000:00:0b.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0b.1: [14e4:471a] type 00 class 0x0c0320
pci 0000:00:0b.1: reg 0x10: [mem 0x18021000-0x18021fff]
pci 0000:00:0b.1: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0c.0: [14e4:472a] type 00 class 0x0c0330
pci 0000:00:0c.0: reg 0x10: [mem 0x18023000-0x18023fff]
pci 0000:00:0c.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0d.0: [14e4:0503] type 00 class 0xffffff
pci 0000:00:0d.0: reg 0x10: [mem 0x18020000-0x18020fff]
pci 0000:00:0d.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0e.0: [14e4:0506] type 00 class 0xffffff
pci 0000:00:0e.0: reg 0x10: [mem 0x18210000-0x1821ffff]
pci 0000:00:0e.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0f.0: [14e4:0507] type 00 class 0xffffff
pci 0000:00:0f.0: reg 0x10: [mem 0x18010000-0x18010fff]
pci 0000:00:0f.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:10.0: [14e4:0508] type 00 class 0xffffff
pci 0000:00:10.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)
pci 0000:00:10.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:11.0: [14e4:0509] type 00 class 0xffffff
pci 0000:00:11.0: reg 0x10: [mem 0x18028000-0x18028fff]
pci 0000:00:11.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:12.0: [14e4:050a] type 00 class 0xffffff
pci 0000:00:12.0: reg 0x10: [mem 0x18029000-0x18029fff]
pci 0000:00:12.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
PCI: Fixing up bus 0 domain 0
PCIE1 link=1
PCIE1 switching to GEN2
PCIE1 link=1
PCI host bridge to bus 0001:00
pci_bus 0001:00: root bus resource [mem 0x08000000-0x0fffffff]
pci_bus 0001:00: No busn resource found for root bus, will use [bus 00-ff]
pci 0001:00:00.0: [14e4:8011] type 01 class 0x060400
pci 0001:00:00.0: PME# supported from D0 D3hot D3cold
PCI: Fixing up bus 0 domain 1
PCI: bus0: Fast back to back transfers disabled
pci 0001:01:00.0: [14e4:4360] type 00 class 0x028000
pci 0001:01:00.0: reg 0x10: [mem 0x08000000-0x08007fff 64bit]
pci 0001:01:00.0: Max Payload Size set to 512 (was 128, max 512)
pci 0001:01:00.0: supports D1 D2
PCI: Fixing up bus 1 domain 1
PCI: bus1: Fast back to back transfers disabled
pci_bus 0001:01: busn_res: [bus 01-ff] end is updated to 01
pci_bus 0001:00: busn_res: [bus 00-ff] end is updated to 01
pci 0001:00:00.0: BAR 8: assigned [mem 0x08000000-0x080fffff]
pci 0001:01:00.0: BAR 0: assigned [mem 0x08000000-0x08007fff 64bit]
pci 0001:00:00.0: PCI bridge to [bus 01]
pci 0001:00:00.0: bridge window [mem 0x08000000-0x080fffff]
PCIE2 link=1
PCIE2 switching to GEN2
PCIE2 link=1
PCI host bridge to bus 0002:00
pci_bus 0002:00: root bus resource [mem 0x40000000-0x47ffffff]
pci_bus 0002:00: No busn resource found for root bus, will use [bus 00-ff]
pci 0002:00:00.0: [14e4:8011] type 01 class 0x060400
pci 0002:00:00.0: PME# supported from D0 D3hot D3cold
PCI: Fixing up bus 0 domain 2
PCI: bus0: Fast back to back transfers disabled
pci 0002:01:00.0: [14e4:4331] type 00 class 0x028000
pci 0002:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
pci 0002:01:00.0: can't set Max Payload Size to 512; if necessary, use ff]
pci 0002:01:00.0: supports D1 D2
PCI: Fixing up bus 1 domain 2
PCI: bus1: Fast back to back transfers disabled
pci_bus 0002:01: busn_res: [bus 01-ff] end is updated to 01
pci_bus 0002:00: busn_res: [bus 00-ff] end is updated to 01
pci 0002:00:00.0: BAR 8: assigned [mem 0x40000000-0x400fffff]
pci 0002:01:00.0: BAR 0: assigned [mem 0x40000000-0x40003fff 64bit]
pci 0002:00:00.0: PCI bridge to [bus 01]
pci 0002:00:00.0: bridge window [mem 0x40000000-0x400fffff]
PCIE3 link=0
squashfs: version 4.0 (2009/01/31) Phillip Lougher
io scheduler noop registered (default)
io scheduler cfq registered
serial8250_init
Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
console [ttyS0] disabled
serial8250.0: ttyS0 at MMIO 0x18000300 (irq = 117, base_baud = 6250000) is a 16550
console [ttyS0] enabled
serial8250.0: ttyS1 at MMIO 0x18000400 (irq = 117, base_baud = 6250000) is a 16550
brd: module loaded
loop: module loaded
Boot partition size = 2097152(0x200000)
Creating 3 MTD partitions on (0x200bcmsflash= 117,:
0x000000000000-0x000000200000 : 200bcmboott;= 11
mtd: partition 0x0000boott;00 : extends beyond the end of device 50000)bcmsflash50
0x0000000f0000-0x000000100000 : extendnvram_cfethe en
0x0000000e0000-0x0000000f0000 : extendnvram;cfeth
Found a Esmt NAND flash:
Total size: 128MB
Block size: 128KB
Page Size: 2048B
OOB Size: 64B
Sector size: 512B
Spare size: 16B
ECC level: 8 (8-bit)
Device ID: 0x92 0xf1 0x80 0x95 0x40 0x7f
lookup_nflash_rootfs_offset: offset = 0x0 size = 0x2000000, 0x20000
found TRX Header on nflash!
nflash: squash filesystem with lzma found at block 13
Creating 2 MTD partitions on h lzmanflash at bl:
0x000000000000-0x000002000000 : zmanfllinux; bl:
0x0000001a0000-0x000002000000 : zmanflrootfs bl:
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
GACT probability NOT on
Mirror/redirect action on
Simple TC action Loaded
netem: version 1.3
u32 classifier
Performance counters on
input device check on
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (8036 buckets, 32144 max)
nf_conntrack_rtsp v0.7 loading
xt_time: kernel timezone is -0000
ip_set: protocol 6
gre: GRE over IPv4 demultiplexor driver
nf_nat_rtsp v0.7 loading
ip_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 17
bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
Registering SWP/SWPB emulation handler
found cfe nvram
check if nvram copy is required CFE Size is 65536
nvram copy magic is 48534C46
max nvram space = 131072
read 65536 bytes to offset 0
Key type encrypted registered
Northstar brcmnand NAND Flash Controller driver, Version 0.1 (c) Broadcom Inc. 2012
nand: device found, Manufacturer ID: 0x92, Chip ID: 0xf1
nand: Eon NAND 128MiB 3,3V 8-bit
nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Spare area=64 eccbytes 56, ecc bytes located at:
2 3 4 5 6 7 8 9 10 11 12 13 14 15 18 19 20 21 22 23 24 25 26 27 28 29 30 31 34 35 36 37 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 60 61 62 63
Available 7 bytes at (off,len):
(1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0)
Scanning device for bad blocks
Bad eraseblock 1023 at 0x000007fe0000
Options: NO_SUBPAGE_WRITE,
Creating 1 MTD partitions on 07fe00brcmnand) (0,0:
0x000002000000-0x000008000000 : e00brcddwrt; (0,0
VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
Freeing unused kernel memory: 344K
et: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
et_module_init: passivemode set to 0x0
et_module_init: txworkq set to 0x0
et_module_init: et_txq_thresh set to 0x400
et_module_init: et_rxlazy_timeout set to 0x3e8
et_module_init: et_rxlazy_framecnt set to 0x20
et_module_init: et_rxlazy_dyn_thresh set to 0
ET Corerev 5
eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.89.21 (r524987)
roboswitch: Probing device 'eth0'
roboswitch: trying a 53011! at eth0
detected CPU Port is 5
roboswitch: found a 53011! at eth0
detected CPU Port is 5
wl_module_init: passivemode set to 0x0
wl_module_init: txworkq set to 0x0
eth1: Broadcom BCM4360 802.11 Wireless Controller 7.14.89.21 (r524987)
PCI: Enabling device 0002:01:00.0 (0140 -> 0142)
eth2: Broadcom BCM4331 802.11 Wireless Controller 7.14.89.21 (r524987)
eth0: mixed HW and IP checksum settings.
device br0 entered promiscuous mode
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
br0: port 1(vlan1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
device eth1 entered promiscuous mode
br0: port 2(eth1) entered forwarding state
br0: port 2(eth1) entered forwarding state
device eth2 entered promiscuous mode
br0: port 3(eth2) entered forwarding state
br0: port 3(eth2) entered forwarding state
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
IMQ: use 2 as queue number
IMQ driver loaded successfully. (numdevs = 2, numqueues = 2, imq_dev_accurate_stats = 1)
Hooking IMQ before NAT on PREROUTING.
Hooking IMQ after NAT on POSTROUTING.
device vlan2 entered promiscuous mode
random: httpd: uninitialized urandom read (32 bytes read, 113 bits of entropy available)
random: nonblocking pool is initialized
device vlan2 left promiscuous mode
IMQ driver unloaded successfully.
IMQ: use 2 as queue number
IMQ driver loaded successfully. (numdevs = 2, numqueues = 2, imq_dev_accurate_stats = 1)
Hooking IMQ before NAT on PREROUTING.
Hooking IMQ after NAT on POSTROUTING.
IMQ driver unloaded successfully.
IMQ: use 2 as queue number
IMQ driver loaded successfully. (numdevs = 2, numqueues = 2, imq_dev_accurate_stats = 1)
Hooking IMQ before NAT on PREROUTING.
Hooking IMQ after NAT on POSTROUTING.
br0: port 1(vlan1) entered forwarding state
br0: port 2(eth1) entered forwarding state
br0: port 3(eth2) entered forwarding state
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 8104
Location: Texas, USA

PostPosted: Wed Jul 18, 2018 4:03    Post subject: Linksys E4200 v1 Reply with quote
Router/Version:  Linksys E4200 v1
Firmware:  DD-WRT v3.0-r36330 mega ( 07/16/18 )
Kernel:  Linux 3.10.108-d3 #20116 Mon Jul 16 18:34:44 CEST 2018 mips
Previous: DD-WRT v3.0-r36168 mega ( 06/20/18 )
Firmware file used: dd-wrt.v24-36330_NEWD-2_K3.x_mega-e4200.bin
Reset; Yes; Reset via webUI (reboot), Firmware upgrade (httpd crash!), 30/30/30 (reboot), configured previous settings manually (reboot)
Mode: Gateway/AP
Status: OK
Uptime: ~13 hours
Issues/Errors:

Other than httpd crashing before telling me that the upgrade was successful and that the router was rebooting and prompting me to do a 30/30/30, so far so good, except this message on the serial console that popped up before the gratuitous 'use CT helpers instead' message was not logged to syslog (I had serial console running during the entire process, log attached):

Code:
get_wl_instance doesnt return the right value 1


Some POSITIVES during initial re-configuration to present:

Kept default DNSMasq and GTK re-key interval settings as they are 'out-of-the-box' and there have been NO issues, in fact, connectivity has been much smoother and faster in this build.

I have not tried testing anything like VAPs, VPN, Hotspots, etc. ad nauseum, have never had a need to. Here's where I plug for a K3x mini build without a whole lot of the extra stuff I don't use... Rolling Eyes But so far, overall, this build has been a good experience. Thanks BS, Kong, and everyone who has been involved in testing for your hard work and patience! I'm sure there were folks just watching and waiting for me to post in this thread.... Laughing



r36330_syslog.txt
 Description:

Download
 Filename:  r36330_syslog.txt
 Filesize:  25.85 KB
 Downloaded:  446 Time(s)


r36168_r36330_serial.log.txt
 Description:

Download
 Filename:  r36168_r36330_serial.log.txt
 Filesize:  92.84 KB
 Downloaded:  454 Time(s)

flood404
DD-WRT User


Joined: 18 Dec 2013
Posts: 227

PostPosted: Wed Jul 18, 2018 5:39    Post subject: Re: New Build 36247 (BS):07-16-2018-r36330 Reply with quote
mwchang wrote:
flood404 wrote:
New Build 36247 (BS):07-16-2018-r36330

Why is "Build 36247" mentioned in the subject line for this build "r36330"? Careless mistake?

Should we just skip this build because of this little mistake? It could be an omen... Meow!!! >@.@<




I totally messed that up. I corrected that. I was doing this when I was tired.
Twisti3s
DD-WRT Novice


Joined: 18 Jul 2018
Posts: 2

PostPosted: Wed Jul 18, 2018 9:06    Post subject: Reply with quote
Router/Version:Asus RT-AC68U
Firmware: DD-WRT v3.0-r36330 std ( 07/16/18 )
Kernel: 4.4.140 #3516 SMP Mon Jul 16 11:58:39 CEST 2018 armv7l DD-WRT
Previous: r36247
Mode/Status: Gateway / working
Reset: no just Lockups
Issues/Errors: Works fine until random within a day it drops this and the freezes up.
Have to power down to get it to run again this is from my paper trail

Jul 18 16:05:38 120.157.64.27 kernel: skbuff: skb_under_panic: text:8034df10 len:1434 put:14 head:8622ac00 data:8622abf6 tail:0x8622b190 end:0x8622b240 dev:eth1
Jul 18 16:06:38 120.157.64.27 kernel: INFO: rcu_sched self-detected stall on CPU
Jul 18 16:06:38 120.157.64.27 kernel: 0-...: (1 GPs behind) idle=aed/140000000000001/0 softirq=708790/708792 fqs=5996
Jul 18 16:06:38 120.157.64.27 kernel: (t=6000 jiffies g=193372 c=193371 q=5670)
Jul 18 16:06:38 120.157.64.27 kernel: Task dump for CPU 0:
Jul 18 16:06:38 120.157.64.27 kernel: ksoftirqd/0 R running 0 3 2 0x00000002
Jul 18 16:06:38 120.157.64.27 kernel: Backtrace:
Jul 18 16:06:38 120.157.64.27 kernel: [<8001b9c0>] (dump_backtrace) from [<8001bc48>] (show_stack+0x18/0x1c)
Jul 18 16:06:38 120.157.64.27 kernel: r7:805067c0 r6:804f9908 r5:00000000 r4:87826400
Jul 18 16:06:38 120.157.64.27 kernel: [<8001bc30>] (show_stack) from [<8005ad18>] (sched_show_task+0xd4/0xdc)
Jul 18 16:06:38 120.157.64.27 kernel: [<8005ac44>] (sched_show_task) from [<8005c0c4>] (dump_cpu_task+0x40/0x44)
Jul 18 16:06:38 120.157.64.27 kernel: r5:00000000 r4:00000000
Jul 18 16:06:38 120.157.64.27 kernel: [<8005c084>] (dump_cpu_task) from [<8007a7b8>] (rcu_dump_cpu_stacks+0x74/0xac)
Jul 18 16:06:38 120.157.64.27 kernel: r5:00000000 r4:805067c0
Jul 18 16:06:38 120.157.64.27 kernel: [<8007a744>] (rcu_dump_cpu_stacks) from [<8007d8c4>] (rcu_check_callbacks+0x290/0x71c)
Jul 18 16:06:38 120.157.64.27 kernel: r9:80506a40 r8:805067c0 r7:068ee000 r6:804e8e80 r5:805067c0 r4:86dd6e80
Jul 18 16:06:38 120.157.64.27 kernel: [<8007d634>] (rcu_check_callbacks) from [<8007f844>] (update_process_times+0x44/0x6c)
Jul 18 16:06:38 120.157.64.27 kernel: r10:00000000 r9:00000000 r8:00000000 r7:87801cc0 r6:00000000 r5:87826400
Jul 18 16:06:38 120.157.64.27 kernel: r4:ffffe000
Jul 18 16:06:38 120.157.64.27 kernel: [<8007f800>] (update_process_times) from [<8008b0a4>] (tick_periodic+0xc0/0xc8)
Jul 18 16:06:38 120.157.64.27 kernel: r7:87801cc0 r6:7fffffff r5:86dd9800 r4:804f8140
Jul 18 16:06:38 120.157.64.27 kernel: [<8008afe4>] (tick_periodic) from [<8008b0e0>] (tick_handle_periodic+0x34/0xac)
Jul 18 16:06:38 120.157.64.27 kernel: r5:86dd9800 r4:ffffffff
Jul 18 16:06:38 120.157.64.27 kernel: [<8008b0ac>] (tick_handle_periodic) from [<8001de04>] (twd_handler+0x38/0x48)
Jul 18 16:06:38 120.157.64.27 kernel: r9:00000000 r8:0000001d r7:87801cc0 r6:8050afbc r5:804ed6c0 r4:00000001
Jul 18 16:06:38 120.157.64.27 kernel: [<8001ddcc>] (twd_handler) from [<80076fb8>] (handle_percpu_devid_irq+0x78/0x90)
Jul 18 16:06:38 120.157.64.27 kernel: r5:804ed6c0 r4:86dd9800
Jul 18 16:06:38 120.157.64.27 kernel: [<80076f40>] (handle_percpu_devid_irq) from [<800734b4>] (__handle_domain_irq+0xb8/0xd4)
Jul 18 16:06:38 120.157.64.27 kernel: r9:00000000 r8:87804800 r7:00000001 r6:00000000 r5:804e6fc4 r4:00000000
Jul 18 16:06:38 120.157.64.27 kernel: [<800733fc>] (__handle_domain_irq) from [<80009368>] (gic_handle_irq+0x50/0x7c)
Jul 18 16:06:38 120.157.64.27 kernel: r9:00000000 r8:b0101100 r7:b0100100 r6:87831b08 r5:b010010c r4:804f9b18
Jul 18 16:06:38 120.157.64.27 kernel: [<80009318>] (gic_handle_irq) from [<80009ea0>] (__irq_svc+0x40/0x54)
Jul 18 16:06:38 120.157.64.27 kernel: Exception stack(0x87831b08 to 0x87831b50)
Jul 18 16:06:38 120.157.64.27 kernel: 1b00: 0000007a 86dd4230 86dd4d48 00000000 8622abf6 8622b190
Jul 18 16:06:38 120.157.64.27 kernel: 1b20: 8622ac00 00000000 14037c33 00000000 00000000 87831b7c 00000000 87831b58
Jul 18 16:06:38 120.157.64.27 kernel: 1b40: 00000000 80237b2c 60000013 ffffffff
Jul 18 16:06:38 120.157.64.27 kernel: r9:00000000 r8:14037c33 r7:87831b3c r6:ffffffff r5:60000013 r4:80237b2c
Jul 18 16:06:38 120.157.64.27 kernel: [<80237ac8>] (skb_panic) from [<80237bfc>] (skb_push+0x44/0x4c)
Jul 18 16:06:38 120.157.64.27 kernel: [<80237bb8>] (skb_push) from [<8034df10>] (br_dev_queue_push_xmit+0x30/0x134)
Jul 18 16:06:38 120.157.64.27 kernel: r7:00000000 r6:87230000 r5:805149c0 r4:872a3900
Jul 18 16:06:38 120.157.64.27 kernel: [<8034dee0>] (br_dev_queue_push_xmit) from [<8034e4f0>] (br_forward_finish+0x114/0x11c)
Jul 18 16:06:38 120.157.64.27 kernel: r7:00000000 r6:87230000 r5:805149c0 r4:872a3900
Jul 18 16:06:38 120.157.64.27 kernel: [<8034e3dc>] (br_forward_finish) from [<8034e56c>] (br_deliver+0x74/0xf4)
Jul 18 16:06:38 120.157.64.27 kernel: r7:866c5000 r6:8622abf6 r5:87230000 r4:872a3900
Jul 18 16:06:38 120.157.64.27 kernel: [<8034e4f8>] (br_deliver) from [<8034c1f8>] (br_dev_xmit+0x230/0x248)
Jul 18 16:06:38 120.157.64.27 kernel: r6:8622abf6 r5:872a3900 r4:866c5480
Jul 18 16:06:38 120.157.64.27 kernel: [<8034bfc8>] (br_dev_xmit) from [<80248570>] (dev_hard_start_xmit+0x2a8/0x324)
Jul 18 16:06:38 120.157.64.27 kernel: r9:872a3900 r8:87b73c00 r7:87b73c00 r6:804e8264 r5:866c5000 r4:872a3900
Jul 18 16:06:38 120.157.64.27 kernel: [<802482c8>] (dev_hard_start_xmit) from [<8024b59c>] (__dev_queue_xmit+0x49c/0x5ec)
Jul 18 16:06:38 120.157.64.27 kernel: r10:0000058c r9:8622ac04 r8:00000000 r7:87b73c00 r6:804e8264 r5:866c5000
Jul 18 16:06:38 120.157.64.27 kernel: r4:872a3900
Jul 18 16:06:38 120.157.64.27 kernel: [<8024b100>] (__dev_queue_xmit) from [<8024b700>] (dev_queue_xmit+0x14/0x18)
Jul 18 16:06:38 120.157.64.27 kernel: r10:0000058c r9:8622ac04 r8:00000014 r7:8622ac18 r6:8718e040 r5:00000004
Jul 18 16:06:38 120.157.64.27 kernel: r4:872a3900
Jul 18 16:06:38 120.157.64.27 kernel: [<8024b6ec>] (dev_queue_xmit) from [<7f4eaedc>] (_17+0x898/0xaa4 [shortcut_fe])
Jul 18 16:06:38 120.157.64.27 kernel: [<7f4ea660>] (_17 [shortcut_fe]) from [<7f4eb230>] (_34+0xb0/0x724 [shortcut_fe])
Jul 18 16:06:38 120.157.64.27 kernel: r10:8608a000 r9:00000040 r8:804f9d88 r7:02080020 r6:00000001 r5:872a3900
Jul 18 16:06:38 120.157.64.27 kernel: r4:00000000
Jul 18 16:06:38 120.157.64.27 kernel: [<7f4eb180>] (_34 [shortcut_fe]) from [<80248b80>] (__netif_receive_skb_core+0x128/0xaa0)
Jul 18 16:06:38 120.157.64.27 kernel: r5:00000000 r4:872a3900
Jul 18 16:06:38 120.157.64.27 kernel: [<80248a58>] (__netif_receive_skb_core) from [<80249574>] (__netif_receive_skb+0x7c/0x80)
Jul 18 16:06:38 120.157.64.27 kernel: r10:804f8100 r9:00000040 r8:86dd71b0 r7:86dd7148 r6:86dd71a4 r5:00000000
Jul 18 16:06:38 120.157.64.27 kernel: r4:86dd71b8
Jul 18 16:06:38 120.157.64.27 kernel: [<802494f8>] (__netif_receive_skb) from [<8024a174>] (process_backlog+0x98/0x148)
Jul 18 16:06:38 120.157.64.27 kernel: r5:00000000 r4:86dd71b8
Jul 18 16:06:38 120.157.64.27 kernel: [<8024a0dc>] (process_backlog) from [<80249934>] (net_rx_action+0x11c/0x280)
Jul 18 16:06:38 120.157.64.27 kernel: r9:0000012c r8:87831e88 r7:00000040 r6:86dd7140 r5:001062bb r4:86dd71b8
Jul 18 16:06:38 120.157.64.27 kernel: [<80249818>] (net_rx_action) from [<8003d634>] (__do_softirq+0x100/0x208)
Jul 18 16:06:38 120.157.64.27 kernel: r10:ffffe000 r9:00000000 r8:00000100 r7:40000003 r6:804ec080 r5:00000003
Jul 18 16:06:38 120.157.64.27 kernel: r4:804ec08c
Jul 18 16:06:38 120.157.64.27 kernel: [<8003d534>] (__do_softirq) from [<8003d774>] (run_ksoftirqd+0x38/0x58)
Jul 18 16:06:38 120.157.64.27 kernel: r10:00000000 r9:00000000 r8:00000000 r7:00000001 r6:80504950 r5:8780d340
Jul 18 16:06:38 120.157.64.27 kernel: r4:ffffe000
Jul 18 16:06:38 120.157.64.27 kernel: [<8003d73c>] (run_ksoftirqd) from [<80055018>] (smpboot_thread_fn+0x184/0x198)
Jul 18 16:06:38 120.157.64.27 kernel: [<80054e94>] (smpboot_thread_fn) from [<800527f8>] (kthread+0xf8/0x100)
Jul 18 16:06:38 120.157.64.27 kernel: r9:00000000 r8:00000000 r7:80054e94 r6:8780d340 r5:8780d300 r4:00000000
Jul 18 16:06:38 120.157.64.27 kernel: [<80052700>] (kthread) from [<80009600>] (ret_from_fork+0x14/0x34)
Jul 18 16:06:38 120.157.64.27 kernel: r7:00000000 r6:00000000 r5:80052700 r4:8780d300
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 8104
Location: Texas, USA

PostPosted: Wed Jul 18, 2018 10:40    Post subject: Re: New Build 36247 (BS):07-16-2018-r36330 Reply with quote
flood404 wrote:
I totally messed that up. I corrected that. I was doing this when I was tired.


It happens! I at least sent you a PM instead of publicly heckling you Rolling Eyes

Still running fine @ almost 20 hrs of uptime here Mr. Green
Per Yngve Berg
DD-WRT Guru


Joined: 13 Aug 2013
Posts: 5974
Location: Romerike, Norway

PostPosted: Wed Jul 18, 2018 11:26    Post subject: Reply with quote
Router: Asus RT-AC66U A1
Firmware Version: DD-WRT v3.0-r36330 giga (07/16/1Cool
Kernel Version: Linux 3.10.108-d3 #20100 Mon Jul 16 18:18:13 CEST 2018 mips

Previous: 36242
Reset: No
Status: Working

Note: Have not tried VAP yet.
mwchang
DD-WRT Guru


Joined: 26 Mar 2013
Posts: 739
Location: Hung Hom, Hong Kong

PostPosted: Wed Jul 18, 2018 14:38    Post subject: Analog hack? Reply with quote
kernel-panic69 wrote:
It happens! I at least sent you a PM instead of publicly heckling you Rolling Eyes

I am and was not hacking anyone's analog brain! It's just a meow reminder! Meow.... Wink

Analog hack.... courtesy of a Japanese anime Beatless!
http://beatless.wikia.com/wiki/Analog_Hack


_________________
Router: Asus RT-N18U (rev. A1)

May the Force and farces be with you! Live long and proper!

Facebook: https://www.facebook.com/changmanwai
Website: https://sites.google.com/site/changmw
SETI@Home profile: http://setiathome.berkeley.edu/view_profile.php?userid=211832
wishmasterf
DD-WRT Novice


Joined: 02 Nov 2010
Posts: 15

PostPosted: Wed Jul 18, 2018 17:09    Post subject: Reply with quote
Oh no... we wait that long for a new build knowing ther is a fix for vap and now we see it is notworking. Thats so bad. Is there a workaround? What was the last build knowing vap working without other big bugs...? I am using WNR3500Lv1.
Goto page 1, 2, 3, 4  Next Display posts from previous:    Page 1 of 4
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum