What's new

Release Asuswrt-Merlin 384.19 is now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Sourceforge looks to have come back up now :)
Keep this link handy to check outages.
 
Hi, I keep seeing this in the log, is this an issue?

Aug 30 10:28:26 smbd[16860]: [2020/08/30 10:28:26.916349, 0] passdb/pdb_smbpasswd.c:1252(build_sam_account)
Aug 30 10:28:26 smbd[16860]: build_sam_account: smbpasswd database is corrupt!

Thanks
 
OK, I'm copying modifying @L&LD excellent earlier posting with the process I think is needed for a 384.19 to work well with the AC-86U + jffs required format! As was stated earlier, there are some combinations of scripts and tooling which these steps might not work well for - YMMV! I posted this detail for the benefit of users who may not know their way around the ASUS/Merlin GUI very well.

Warning: Before you upgrade an AC86U to 384.19, please read the rest of this forum thread. My final results are here -> https://www.snbforums.com/threads/r...19-is-now-available.65801/page-30#post-617059

@L&LD original posting -> https://www.snbforums.com/threads/b...eta-is-now-available.65581/page-6#post-608612

Mods -> g>

The update process from 384.18_0 release final or from one of the 384.19 Alpha releases to the 384.19 production release:

Gotchas:
  1. Some users have reported that when the JFFS is formatted, and they have changed the default login ID from admin to something else, they had issues logging in afterwards or were unable to format the JFFS except from the SSH. As a precaution, you may want to change the login ID to the default of admin before starting this update and then set it back to what you want after you have completed the upgrade.
  2. I do not use a VPN yet so I have no idea what gotchas are in that setup.
  3. ...
An Upgrade Path for 384.19 (modified on 05 Sep 2020)
  1. Verify / Update all scripts installed first, including amtm and Entware, if necessary.
    • g> amtm > u
  2. Login via SSH and "rm /jffs/.sys/nc/nt_center.db" (This is a hidden file in .sys which appears to cause issues...) It will be recreated by the router.
  3. For the RT-AC86U routers (and others as a best upgrade practice), save a 'Backup JFFS Partition' config file using the GUI
    • g > Administration > Restore/Save/Upload Settings > Backup JFFS Partition > Supply a filename
    • g > Administration > Restore/Save/Upload Settings > Enable JFFS custom scripts and configs > NO
  4. g > Backup the router's config using the GUI
    • g> Administration > Restore/Save/Upload Settings > Save Setting
    • See Note: 1 above.
  5. Safely remove USB drive(s) via the GUI (no need to physically remove the drive(s) though). (See Step 6)
    • g > Network Map > Select each USB(s) Disk > Safely Remove Disk > Remove
  6. g > With all the A86U issues I've had with CRC errors, I am also disconnecting the USB SSD physically until step #12 below.
  7. g> Flash the 384.19 firmware, then reboot the router and let it sit for maybe 5 mins after rebooting.
  8. g> if you SSH into the router and run "df -h" then JFFS should look similar to this BEFORE restoring it. It is important that it be 47M (not 48M) b/c that is the new size with this firmware version. -> /dev/mtdblock9 47.0M 1.4M 45.6M 3% /jffs
  9. g > Login > Administration > System > Format JFFS partition at next boot > hit APPLY (Do not miss this step as I did my first pass...) These next steps allow the router to format the JFFS properly.
  10. g > Do For I =1 to 3 (per 5-10 mins, with the USB disconnected) (This is per multiple @L&LD postings WRT formatting the JFFS properly.)
    1. g> login > Reboot the router.
    2. g> Wait 5-10 minutes with the router up/running
    3. end
  11. g > Login > Administration > Restore/Save/Upload Settings > Enable JFFS custom scripts and configs > YES
  12. g > Reboot router. Wait 5 mins.
  13. g > Login > Administration > Restore/Save/Upload Settings > Restore JFFS partition > Choose File > Upload
    • g > When you login before restoring the JFFS, you will notice the Addons tab is not be present b/c the JFFS has been formatted and not yet restored.
  14. g > Reconnect the USB now
  15. g > Reboot the router after the JFFS has been restored. Wait 5 minutes.
  16. Verify that the update was successful, and all scripts worked after 10 minutes or more after the reboot.
    • g > Check the Addons tab is now present with the JFFS and restored.
    • g > If you SSH into the router, the JFFS should be repopulated from your backup
    • g > The JFFS size should reflect more "in use" -> /dev/mtdblock9 47.0M 8.3M 38.7M 18% /jffs
    • g > See Note: 1 above about the default userid of admin
  17. After 15 minutes (or more) uptime, reboot the router.
  18. After an additional hour (or more) uptime, reboot the router one last time.
  19. g> After 1-2 hours, Login to the router and check the "Addons" tab
    • g > Open / Verify each amtm utility's scripts are running and that the scripts are graphing the data in the GUI to the current time/datapoints. If it you are seeing current graphs, then the scripts are likely GTG. (In my first upgrade, I did not check this until about 2 days later. That is when I saw no graphs.)
    • If you are not seeing graphs, manually run the scripts with the "Update Stats" option integrated into each tool. Then verify the update ran as there should be a recent data point. Continue to monitor as the scripts which is my case seem OK now and continue running.
  20. g > Check the router again after 24 hours to verify your scripts are still running.
  21. g > Also I suggest logging in via SSH and running AMTM > u to verify there are no recent updates and that the AMTM setup looks "normal".
  22. In addition to the above, some of the routers needed the Unbound Manager script to be updated and/or re-installed for Unbound to work correctly (the 'error' show was it wasn't running. Some, but not all (therefore why we test).
Comment welcome. I copied and modified @L&LD post since that thread is locked now per earlier posts here.

After restoring JFFS
Code:
df -h
Filesystem                Size      Used Available Use% Mounted on
ubi:rootfs_ubifs         77.2M     60.6M     16.6M  79% /
devtmpfs                214.9M         0    214.9M   0% /dev
tmpfs                   215.0M    192.0K    214.8M   0% /var
tmpfs                   215.0M    984.0K    214.1M   0% /tmp/mnt
mtd:bootfs                4.4M      3.3M      1.1M  75% /bootfs
tmpfs                   215.0M    984.0K    214.1M   0% /tmp/mnt
mtd:data                  8.0M    716.0K      7.3M   9% /data
tmpfs                   215.0M    984.0K    214.1M   0% /tmp
/dev/mtdblock9           47.0M      1.4M     45.6M  3% /jffs
/dev/sda                 58.4G      2.9G     52.5G   5% /tmp/mnt/123-ASUS-AC86U
tmpfs                   215.0M    984.0K    214.1M   0% /www/index_style.css
tmpfs                   215.0M    984.0K    214.1M   0% /www/require/modules/menuTree.js

Before restoring JFFS
Code:
df -h
Filesystem                Size      Used Available Use% Mounted on
ubi:rootfs_ubifs         77.2M     60.6M     16.6M  79% /
devtmpfs                214.9M         0    214.9M   0% /dev
tmpfs                   215.0M    192.0K    214.8M   0% /var
tmpfs                   215.0M    984.0K    214.1M   0% /tmp/mnt
mtd:bootfs                4.4M      3.3M      1.1M  75% /bootfs
tmpfs                   215.0M    984.0K    214.1M   0% /tmp/mnt
mtd:data                  8.0M    716.0K      7.3M   9% /data
tmpfs                   215.0M    984.0K    214.1M   0% /tmp
/dev/mtdblock9           47.0M      8.3M     38.7M  18% /jffs
/dev/sda                 58.4G      2.9G     52.5G   5% /tmp/mnt/123-ASUS-AC86U
tmpfs                   215.0M    984.0K    214.1M   0% /www/index_style.css
tmpfs                   215.0M    984.0K    214.1M   0% /www/require/modules/menuTree.js

I think this finally straightened out my AC86 setup. Stay safe, stay alive! Peace.
 
Last edited:
The AC66u is no longer supported by Merlin:,

The following models are no longer officially supported:
  • RT-N16
  • RT-N66U
  • RT-AC66U
  • RT-AC56U
I'm running John's fork of the firmware on my AC66u, it's very stable in my experience and is frequently updated http://www.snbforums.com/threads/fork-asuswrt-merlin-374-43-lts-releases-v44ea.18914/post-615166

I am aware of that again i have not use that AC66U in years cause it at another location that i no longer manager. the F@st 5260 is refernce to another location that I gona replace the router with one new asus router supported.

I was mostly curious about my original questions
 
I'm not seeing the addons tab but it looks like the size of jffs is correct?
ubi:rootfs_ubifs 77.2M 60.6M 16.6M 79% /
devtmpfs 214.9M 0 214.9M 0% /dev
tmpfs 215.0M 448.0K 214.6M 0% /var
tmpfs 215.0M 1.7M 213.4M 1% /tmp/mnt
mtd:bootfs 4.4M 3.3M 1.1M 75% /bootfs
tmpfs 215.0M 1.7M 213.4M 1% /tmp/mnt
mtd:data 8.0M 644.0K 7.4M 8% /data
tmpfs 215.0M 1.7M 213.4M 1% /tmp
/dev/mtdblock9 47.0M 6.5M 40.5M 14% /jffs
/dev/mtdblock9 47.0M 6.5M 40.5M 14% /www/QoS_Stats.asp
ubi:rootfs_ubifs 77.2M 60.6M 16.6M 79% /usr/sbin/tc
/dev/sda1 9.1T 3.9T 5.2T 42% /tmp/mnt/easystore
 
I am aware of that again i have not use that AC66U in years cause it at another location that i no longer manager. the F@st 5260 is refernce to another location that I gona replace the router with one new asus router supported.

I was mostly curious about my original questions


 
Started the day with no internet. Quickly blamed 384.19 and flashed Asus stock. Did not help. Discovered Centurylink had a failure that shut down a lot of the East coast. A quick reflash of 384.19, restore settings and jffs and a wait for the internet to get back up and happiness! Was good to have backups!
 
Huge issues with wireless clients after updating my RT-AC86U (in router mode) and RT-AC68U (in router mode) after updating.

Did the JFFS format after the update and it all worked ok. Didn't bother copying back the backup, I just let it set up the certs again etc. and that was all fine.

Externally, it's all good. VPN's work and it's online etc.

Internally... it's not so good. Wireless clients disconnect after a minute (sometimes less) and my log gets spammed with the following:

Aug 31 17:16:24 syslog: WLCEVENTD wlceventd_proc_event(466): eth2: Deauth_ind [MAC], status: 0, reason: Class 3 frame received from nonassociated station (7)

I've also seen a few of these, but nowhere near as many as the above:

Aug 31 17:17:24 syslog: WLCEVENTD wlceventd_proc_event(466): eth2: Deauth_ind [MAC], status: 0, reason: Class 2 frame received from nonauthenticated station (6)

The clients are kicked off before they can even do anything. Very frustrating!

Any help would be greatly appreciated.

Cheers

P.S. I've updated my RT-AX88U (Router) and my RT-AC86U (AP) with no issues at all, but but the 86U as a router (in the above example) has problems...? Weird!
 
This weekend I tried again to install .19 but after format jffs and didn't install any script, the VPN didn't run. Only connect but not run. I'm going to wait for the next version. Now in the log i see this:
Code:
Aug 31 11:34:29 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
 
Well, I clearly see you are an italian dude (ciao amico! Sono argentino, è quasi lo stesso!) dealing with a double NAT environment cascading from a FASTGate DGA4131 router.
The images don't clarify anything else to me except that simple fact. Now let's work with that and the comment from your post, which is that you have a fixed IP Address. For sure that static IP ought to make the use of DDNS unnecessary, doesn't it? You can access your cameras (you mention CAM so I guess that's what it is) just by using the ip address. You could also find out what's the hostname associated with that address by going to a command prompt in windows and doing a ping -a 2.229.xxx.xxx or online at https://whatismyipaddress.com/ip-hostname. It may or may not be there, and it may also be complicated so not sure if this would help but it might. You are using the ASUS DDNS service... there are alternatives that may be better suited for your environment. We can discuss that later if relevant.
If you don't use the DGA4131 for connecting other clients in your network, only the Asus AC68U, you may simply put your AC68U lan IP address in the DMZ of the DGA router. This will make all incoming ports to be redirected to the AC68U so it would be less affected by the double NAT. The DMZ entry is usually found in the firewall pages of your main router configuration.
You may also need to have proper port redirection set up at the AC68U for the camera you are using. If you decide to do something like this, then for sure you need your firewall up in your AC68U.

Hi boy, (it's true I'm an old Italian) I prefer not to touch anything as for now everything works, both the remote control of the cameras, both the house alarm system and the VOL.
In fact my AC68U lan IP address is connected in the DMZ of the DGA router!
Anyway thanks for your interest ...
Ciao
 
^^^ Yes 47M is the correctly reformatted size. The Addons tab will not reappear until you reboot the router after restoring the JFFS. I had all of that in one Step 8, I just separated the Reboot into it's own step 9... too easy to miss.

I will report that my steps above did not appear to save something correctly. The stats in connmon, ntp daemon, uidivstats, and speedtest do not appear to be running and updating this AM. :( I've just rebooted one more time to see if that brings'm back to life, if not I'm guessing the only way to get these back will be to remove and then reinstall each using AMTM. I also checked the /jffs/scripts/services-start file and I found them present.. so IDK where the glitch is hiding or why they are not collecting data. Restoring the JFFS does not appear to be 100%. Anyyone have any idea on the scripts not running - yell!!

No longer on hold. I just rebooted the router about 24 hours after I did all the above and it appears the J* scripts may have started running... at least I see a few datapoints. Will report back later.

Reporting back after about 9 hours..
All the J* tooling remains broken.. nothing updated about 11:00 AM.. so they ran for a couple hours... and this looks very bad. I wonder if my JFFS is now fried on this router..?

Aug 31 15:46:27 kernel: jffs2: read_cache_page() returned error: -5
Aug 31 15:46:27 kernel: jffs2: Error garbage collecting node at 025c1510!
Aug 31 15:47:27 kernel: jffs2: Data CRC c80a47a2 != calculated CRC 777bca84 for node at 025c1510
Aug 31 15:47:27 kernel: jffs2: read_cache_page() returned error: -5
Aug 31 15:47:27 kernel: jffs2: Error garbage collecting node at 025c1510!
Aug 31 15:47:27 kernel: jffs2: Data CRC c80a47a2 != calculated CRC 777bca84 for node at 025c1510
Aug 31 15:47:27 kernel: jffs2: read_cache_page() returned error: -5
Aug 31 15:47:27 kernel: jffs2: Error garbage collecting node at 025c1510!

On the positive note, Diversion and Skynet appear to be behaving better in that I'm not having weird blocking issues (so far) I was seeing before with sites I had "authorized/whitelisted"

Code:
#
/jffs/scripts/connmon startup & # connmon
/jffs/scripts/ntpmerlin startup & # ntpMerlin
/jffs/scripts/uiDivStats startup & # uiDivStats
/jffs/scripts/spdmerlin startup & # spdMerlin
#
 
Last edited:
Hi everybody.

I seam to have problems with OpenVPN server not starting correctly on RT-AC68U. Reboot and powercycle would not solve the problem. I tested on two different routers, same model to make sure it’s not hardware related. The server would just get stuck in startup. Deactivating the server and activating it again got it running. Already happened in three separate occasions, so not a fluke.
I know (and appreciate) that the code has been rewritten and this might be related. Just want to know if this is a known issue.

Keep up the great work Merlin.
 
Anyone else having issues changing USB speed from 3.0 back to 2.0? I get prompted to add a new admin username each time I hit apply.


1598899134564.png
 
Anyone else having issues changing USB speed from 3.0 back to 2.0? I get prompted to add a new admin username each time I hit apply.


View attachment 25906
See here:

To fix involves rewriting a couple nvram variables.
 
I seam to have problems with OpenVPN server not starting correctly on RT-AC68U. Reboot and powercycle would not solve the problem. I tested on two different routers, same model to make sure it’s not hardware related. The server would just get stuck in startup. Deactivating the server and activating it again got it running. Already happened in three separate occasions, so not a fluke.

Check your system log.
 
I updated my post above. This from the logs looks very, very bad.

Update: All the tooling stopped running after ~ 11:00 AM. They ran for a couple hours after the last reboot. CRC errors on the JFFS2!!! Yikes.. This AC86U was running perfectly until this 384.19 update where ASUS *@(@* with the JFFS size. They should be warned - this is not good.

Any suggestions welcome - please. Is it time for a new router? This one is barely 18 months old. YMMV.

Scanning the forums, I see at 3 others who've reported a similar issue with 384.19.... and this is a "known issue on 384.19"... OH my you have been warned... now.


Did by chance we "wear out" this flash with all the neat utilities? :( An no to overheating, she's clam cool with a fan on the rear.

GROWLING very, very loudly at ASUS for mucking with the JFFS! :mad:

Aug 31 15:46:27 kernel: jffs2: read_cache_page() returned error: -5
Aug 31 15:46:27 kernel: jffs2: Error garbage collecting node at 025c1510!
Aug 31 15:47:27 kernel: jffs2: Data CRC c80a47a2 != calculated CRC 777bca84 for node at 025c1510
Aug 31 15:47:27 kernel: jffs2: read_cache_page() returned error: -5
Aug 31 15:47:27 kernel: jffs2: Error garbage collecting node at 025c1510!
Aug 31 15:47:27 kernel: jffs2: Data CRC c80a47a2 != calculated CRC 777bca84 for node at 025c1510
Aug 31 15:47:27 kernel: jffs2: read_cache_page() returned error: -5
Aug 31 15:47:27 kernel: jffs2: Error garbage collecting node at 025c1510!


/root# df -hT
Filesystem Type Size Used Available Use% Mounted on
ubi:rootfs_ubifs ubifs 77.2M 60.6M 16.6M 79% /
devtmpfs devtmpfs 214.9M 0 214.9M 0% /dev
tmpfs tmpfs 215.0M 220.0K 214.8M 0% /var
tmpfs tmpfs 215.0M 1.2M 213.8M 1% /tmp/mnt
mtd:bootfs jffs2 4.4M 3.3M 1.1M 75% /bootfs
tmpfs tmpfs 215.0M 1.2M 213.8M 1% /tmp/mnt
mtd:data jffs2 8.0M 716.0K 7.3M 9% /data
tmpfs tmpfs 215.0M 1.2M 213.8M 1% /tmp
/dev/mtdblock9 jffs2 47.0M 10.9M 36.1M 23% /jffs
/dev/sda ext4 58.4G 3.0G 52.5G 5% /tmp/mnt/3622-ASUS-AC86U
tmpfs tmpfs 215.0M 1.2M 213.8M 1% /www/index_style.css
tmpfs tmpfs 215.0M 1.2M 213.8M 1% /www/require/modules/menuTree.js
 
Last edited:
One issue I have is when I go to log on to the router, my 2g wifi ssid and password is saved in the logon?!?!?!

also not sure if this is normal?

Aug 27 21:09:41 kernel: ------------[ cut here ]------------
Aug 27 21:09:41 kernel: WARNING: at include/linux/skbuff.h:1478 fa_process_tx+0x188/0x194 [et]()
Aug 27 21:09:41 kernel: module: usblp bf779000 10321
Aug 27 21:09:41 kernel: module: thfsplus bf75c000 84702
Aug 27 21:09:41 kernel: module: tntfs bf6d5000 493645
Aug 27 21:09:41 kernel: module: tfat bf69d000 186782
Aug 27 21:09:41 kernel: module: ext2 bf689000 52776
Aug 27 21:09:41 kernel: module: nf_nat_sip bf682000 5031
Aug 27 21:09:41 kernel: module: nf_conntrack_sip bf679000 15713
Aug 27 21:09:41 kernel: module: ext4 bf631000 221674
Aug 27 21:09:41 kernel: module: nf_nat_h323 bf672000 4761
Aug 27 21:09:41 kernel: module: nf_conntrack_h323 bf623000 33807
Aug 27 21:09:41 kernel: module: nf_nat_rtsp bf61d000 3202
Aug 27 21:09:41 kernel: module: nf_conntrack_rtsp bf617000 4067
Aug 27 21:09:41 kernel: module: crc16 bf611000 1007
Aug 27 21:09:41 kernel: module: nf_nat_ftp bf60b000 1144
Aug 27 21:09:41 kernel: module: jbd2 bf5f8000 48993
Aug 27 21:09:41 kernel: module: nf_conntrack_ftp bf5f1000 4909
Aug 27 21:09:41 kernel: module: ext3 bf5cf000 106409
Aug 27 21:09:41 kernel: module: jbd bf5be000 42367
Aug 27 21:09:41 kernel: module: ip6table_mangle bf5b8000 934
Aug 27 21:09:41 kernel: module: mbcache bf5b1000 4599
Aug 27 21:09:41 kernel: module: usb_storage bf5a2000 34290
Aug 27 21:09:41 kernel: module: sg bf597000 19855
Aug 27 21:09:41 kernel: module: sd_mod bf58b000 21983
Aug 27 21:09:41 kernel: module: scsi_wait_scan bf585000 416
Aug 27 21:09:41 kernel: module: scsi_mod bf560000 108738
Aug 27 21:09:41 kernel: module: ohci_hcd bf556000 17926
Aug 27 21:09:41 kernel: module: ehci_hcd bf548000 32382
Aug 27 21:09:41 kernel: module: xhci_hcd bf535000 51132
Aug 27 21:09:41 kernel: module: cdc_mbim bf52f000 3137
Aug 27 21:09:41 kernel: module: qmi_wwan bf528000 5792
Aug 27 21:09:41 kernel: module: cdc_wdm bf521000 7252
Aug 27 21:09:41 kernel: module: cdc_ncm bf519000 8762
Aug 27 21:09:41 kernel: module: rndis_host bf512000 5256
Aug 27 21:09:41 kernel: module: cdc_ether bf50c000 4036
Aug 27 21:09:41 kernel: module: asix bf504000 10856
Aug 27 21:09:41 kernel: module: cdc_acm bf4fb000 12614
Aug 27 21:09:41 kernel: module: usbnet bf4f2000 11900
Aug 27 21:09:41 kernel: module: usbcore bf4ce000 102572
Aug 27 21:09:41 kernel: module: mii bf4c8000 3367
Aug 27 21:09:41 kernel: module: ip6t_LOG bf4c1000 4494
Aug 27 21:09:41 kernel: module: ip6table_filter bf4bb000 750
Aug 27 21:09:41 kernel: module: jffs2 bf49d000 91274
Aug 27 21:09:41 kernel: module: zlib_deflate bf493000 19489
Aug 27 21:09:41 kernel: module: nf_nat_pptp bf48d000 1602
Aug 27 21:09:41 kernel: module: nf_conntrack_pptp bf487000 3355
Aug 27 21:09:41 kernel: module: nf_nat_proto_gre bf481000 887
Aug 27 21:09:41 kernel: module: nf_conntrack_proto_gre bf47b000 3296
Aug 27 21:09:41 kernel: module: wl bf03c000 4201581
Aug 27 21:09:41 kernel: module: dpsta bf033000 12782
Aug 27 21:09:41 kernel: module: et bf01c000 65134
Aug 27 21:09:41 kernel: module: igs bf014000 11887
Aug 27 21:09:41 kernel: module: emf bf00b000 15225
Aug 27 21:09:41 kernel: module: ctf bf000000 21199
Aug 27 21:09:41 kernel: Modules linked in: usblp thfsplus tntfs(P) tfat(P) ext2 nf_nat_sip nf_conntrack_sip ext4 nf_nat_h323 nf_conntrack_h323 nf_nat_rtsp nf_conntrack_rtsp crc16 nf_nat_ftp jbd2 nf_conntrack_ftp ext3 jbd ip6table_mangle mbcache usb_storage sg sd_mod scsi_wait_scan scsi_mod ohci_hcd ehci_hcd xhci_hcd cdc_mbim qmi_wwan cdc_wdm cdc_ncm rndis_host cdc_ether asix cdc_acm usbnet usbcore mii ip6t_LOG ip6table_filter jffs2 zlib_deflate nf_nat_pptp nf_conntrack_pptp nf_nat_proto_gre nf_conntrack
Aug 27 21:09:41 kernel: [<c0043ff8>] (unwind_backtrace+0x0/0xf8) from [<c0061d70>] (warn_slowpath_common+0x4c/0x64)
Aug 27 21:09:41 kernel: [<c0061d70>] (warn_slowpath_common+0x4c/0x64) from [<c0061da4>] (warn_slowpath_null+0x1c/0x24)
Aug 27 21:09:41 kernel: [<c0061da4>] (warn_slowpath_null+0x1c/0x24) from [<bf02550c>] (fa_process_tx+0x188/0x194 [et])
Aug 27 21:09:41 kernel: [<bf02550c>] (fa_process_tx+0x188/0x194 [et]) from [<bf0265f8>] (et_isr+0x2fc/0x488 [et])
Aug 27 21:09:41 kernel: unwind: Index not found bf0265f8
Aug 27 21:09:41 kernel: ---[ end trace 394cc2e662e6151d ]---
 
Last edited:
Status
Not open for further replies.

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top