WRT3200ACM??

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Marvell MVEBU based Hardware (WRT1900AC etc.)
Goto page Previous  1, 2, 3 ... , 197, 198, 199  Next
Author Message
cybrnook
DD-WRT User


Joined: 08 Jan 2014
Posts: 288

PostPosted: Thu Jun 28, 2018 18:48    Post subject: Reply with quote
Are you two being paid every time you mention Asus or Netgear routers? Smile Seem to do it in every post lately, pointing out the issues you had with the WRT series and how they are garbage.

There are still lot's of units out there, and people still want to try and work with what they have instead of buying another unit. Just wanted to mention that.

I have many of these units out in the wild, and nobody is complaining back to me about them. Every user and user case is different, you guys know that. So the issues someone may face, others may not. Dirty flashes vs factory resets, different wifi clients, different neighboring AP's on same channels....
Sponsor
05dyna
DD-WRT Guru


Joined: 25 Jan 2008
Posts: 874

PostPosted: Thu Jun 28, 2018 19:30    Post subject: Reply with quote
@ myersw running Merlin's current version. I think it is going to be one of those YMMV scenarios. Last time I checked the log didn't show anything jumping out so may need to contact Asus.

We do push a lot of traffic thru with speedtest and streaming so volume alone might be causing some grief for it. According to the traffic counter since 06/18/2018 its documented over 311GB after resetting to defaults. I may give the stock FW a chance before doing anything else.

BTW I order the WRT32X off eBay so stay tuned...

_________________

ASRock J3455B-ITX Quad Core / 8-GB of Ram pfsense 2.4.5-RELEASE <--Speedtest
Linksys EA8500 - DD-WRT v3.0-r42803 std (03/25/20)as OpenVPN client behind pfsense box
Linksys EA8500 - DD-WRT v3.0-r42803 std (03/25/20)as Access Point
ISP info: optimum |ARRIS SURFboard SB8200
XPEnology DS3615xs
Not a Guru, just a dd-wrt aficionado...


Last edited by 05dyna on Thu Jun 28, 2018 19:33; edited 1 time in total
gufus
DD-WRT Guru


Joined: 04 Aug 2012
Posts: 612
Location: behind the screen

PostPosted: Thu Jun 28, 2018 19:32    Post subject: Reply with quote
htismaqe wrote:


Using a year old firmware and never upgrading, especially given the speed at which cyber threats move today, really isn't a great option. Just saying. My WRT1900ACv1 is still on r31924 and can't be upgraded because the new builds don't work for various reasons. It will become a dedicated AP sometime next week.


The wifi driver is a memory pig..

_________________
WRT3200ACM openwrt 18.06.5
WRT3200ACM dd-wrt r41791
WRT54GL dd-wrt r21676
Dariusz
DD-WRT Novice


Joined: 15 May 2017
Posts: 18

PostPosted: Thu Jun 28, 2018 19:46    Post subject: Reply with quote
Sam1789 wrote:
Dariusz

You need to include your basic information in your posts to start with. It will help you get responses.

what router, what build #, type of setup (WiFi, anything "fancy") etc

Also imgur.com is not the best place to share images. It seems to DEMAND that one allow ad-sites thru in order to even see the images. For instance, all I see is black from that link.

hth


Oh dear, where should I upload images instead?

Firmware data
Firmware: DD-WRT v3.0-r36168 std (06/20/1Cool
Time: 21:47:19 up 10:01, load average: 0.00, 0.00, 0.00

Its pretty basic setup. Nothing fancy. Just 2 networks, 1 guest 1 private.
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7276
Location: Columbus, Ohio

PostPosted: Fri Jun 29, 2018 9:30    Post subject: Reply with quote
Do I need to start deleting posts?
_________________
I am far from a guru, I'm barely a novice.
ATHF
DD-WRT Guru


Joined: 14 Dec 2015
Posts: 704
Location: 127.0.0.1

PostPosted: Fri Jun 29, 2018 10:15    Post subject: Reply with quote
There are a lot of, "I switched to this or that replies", not just on this thread.

I just have this to say, if it works for your setup, good, just don't reply to something you used to use, saying it sucks or mine just runs whatever. As the opposite is true for us, it works for us and our setups.

I was about to give up on my WRT1900AC, it was just connected to music streamers due to the bandwidth slowing down over time, but this last release brought it back to life.

*Anyone else notice more furious posters in other forums today as well? I did.

_________________
Tutorial for flashing WRT series
WRT Installation,Upgrade & Basic Setup–Cliff Notes
DD-WRT Firmware: r42054: WRT3200ACM, WRT1200ACv1, WRT1900ACv1
Velop:3 WHW0101, RE6500, RE9000
TWC/Spectrum - 300/25
SysLog Watcher 5, Security Onion on Virtual Box, Fingboxes, PiHoles
htismaqe
DD-WRT User


Joined: 05 Nov 2015
Posts: 471

PostPosted: Fri Jun 29, 2018 14:24    Post subject: Reply with quote
ATHF wrote:
There are a lot of, "I switched to this or that replies", not just on this thread.

I just have this to say, if it works for your setup, good, just don't reply to something you used to use, saying it sucks or mine just runs whatever. As the opposite is true for us, it works for us and our setups.

I was about to give up on my WRT1900AC, it was just connected to music streamers due to the bandwidth slowing down over time, but this last release brought it back to life.

*Anyone else notice more furious posters in other forums today as well? I did.


This latest release killed my WRT1900ACv1 and the only responses I seem to get are "it's working for me". That's why I posted that I was getting a Netgear router, not because I'm pro-Netgear (I actually promised myself I would never buy Netgear again but that's another story) but because installing the latest release cause my eth0 to die and I can't figure out why. I'm stuck on r31924 from a year ago and I've just given up hope.

For me, I've been on DD-WRT for quite some time on the WRT1900ACv1 and it works great. I'm just not keen on being a year (and counting) behind on security updates and the like.

_________________
Routing:.......Asus RT-AX88U (Asuswrt-Merlin 384.14)
Switching:....Netgear GS608_V3 & GS605_V4, TrendNet TEG-S82G & TEG-S50G
ATHF
DD-WRT Guru


Joined: 14 Dec 2015
Posts: 704
Location: 127.0.0.1

PostPosted: Sat Jun 30, 2018 6:26    Post subject: Reply with quote
htismaqe wrote:


This latest release killed my WRT1900ACv1 and the only responses I seem to get are "it's working for me". That's why I posted that I was getting a Netgear router, not because I'm pro-Netgear (I actually promised myself I would never buy Netgear again but that's another story) but because installing the latest release cause my eth0 to die and I can't figure out why. I'm stuck on r31924 from a year ago and I've just given up hope.

For me, I've been on DD-WRT for quite some time on the WRT1900ACv1 and it works great. I'm just not keen on being a year (and counting) behind on security updates and the like.


Was it you that posted about it killing all ethernet connections? If it was, do you go from factory to DD-WRT? I am asking because I had to use the webflash, as the factory file would just kick back to stock.

As far as Netgear, if I was getting something else I would get one of them as I kind of like Kongs releases. And sorry for going off, it was a bad night.

_________________
Tutorial for flashing WRT series
WRT Installation,Upgrade & Basic Setup–Cliff Notes
DD-WRT Firmware: r42054: WRT3200ACM, WRT1200ACv1, WRT1900ACv1
Velop:3 WHW0101, RE6500, RE9000
TWC/Spectrum - 300/25
SysLog Watcher 5, Security Onion on Virtual Box, Fingboxes, PiHoles
myersw
DD-WRT Guru


Joined: 13 Jun 2006
Posts: 1609
Location: SE Michigan USA

PostPosted: Sat Jun 30, 2018 17:35    Post subject: Reply with quote
cybrnook wrote:
Are you two being paid every time you mention Asus or Netgear routers? Smile Seem to do it in every post lately, pointing out the issues you had with the WRT series and how they are garbage.


Not I, just speaking the truth based on my experiences. YMMV.

What I do know is when I was using the wrt3200acm running dd-wrt I had stability issues. Gave up on Belkin/Linksys/Marvell ever getting a good driver, which I guess they have moved closer to lately, and got a Netgear r8000p. It ran circles around the wrt3200acm in my simple iperf test, but the firmware from a stability standpoint was crap. Therefore the move to Asus rt-ac86u. For me with Merlin firmware the ac86u just runs. No issues and no need to reboot except for firmware update. Have a wrt1900acs v1 should you want it. Already unloaded the wrt3200acm.

As was stated YMMV. No router fits all circumstances. I have both 2.4 and 5 gig channels close by. Also the house I am in is wet plaster with metal lath, not the most desirable of building materials from a wireless standpoint.

--bill

_________________
Unifi Security Gateway: Unifi Firmware
Netgear r7800: Voxel Firmware
Modem:Netgear CM500V voice and Data.
ISP:Comcast
tutorial for flashing "WRT" series:
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=287813
DD-WRT Installation, Upgrade & Basic Setup–Cliff Notes:
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=311117
Kong DD-WRT Config Tutorial:
http://www.instructables.com/id/Install-and-Configure-a-DD-WRT-Kong-Router/
I tried to be normal once. Worst 2 minutes ever.


Last edited by myersw on Sat Jun 30, 2018 19:20; edited 1 time in total
htismaqe
DD-WRT User


Joined: 05 Nov 2015
Posts: 471

PostPosted: Sat Jun 30, 2018 17:58    Post subject: Reply with quote
ATHF wrote:
htismaqe wrote:


This latest release killed my WRT1900ACv1 and the only responses I seem to get are "it's working for me". That's why I posted that I was getting a Netgear router, not because I'm pro-Netgear (I actually promised myself I would never buy Netgear again but that's another story) but because installing the latest release cause my eth0 to die and I can't figure out why. I'm stuck on r31924 from a year ago and I've just given up hope.

For me, I've been on DD-WRT for quite some time on the WRT1900ACv1 and it works great. I'm just not keen on being a year (and counting) behind on security updates and the like.


Was it you that posted about it killing all ethernet connections? If it was, do you go from factory to DD-WRT? I am asking because I had to use the webflash, as the factory file would just kick back to stock.

As far as Netgear, if I was getting something else I would get one of them as I kind of like Kongs releases. And sorry for going off, it was a bad night.


Yeah, that was me. I flashed the BIN file from within DD-WRT (I haven't had stock FW in either partition for a long time). It came up fine but the switch ports were all dead. Not even a link light. So I did the 3 off/on reset sequence, booted back to r31924 and tried it again. Same result.

I didn't do a factory reset but at that point I was frustrated enough that I was done messing with it and just wanted to get something that was newer and more supported. I prefer Kong's builds but he stopped building for the WRTAC1900v1 like 2 years ago now.

_________________
Routing:.......Asus RT-AX88U (Asuswrt-Merlin 384.14)
Switching:....Netgear GS608_V3 & GS605_V4, TrendNet TEG-S82G & TEG-S50G
cybrnook
DD-WRT User


Joined: 08 Jan 2014
Posts: 288

PostPosted: Sat Jun 30, 2018 19:20    Post subject: Reply with quote
myersw wrote:
cybrnook wrote:
Are you two being paid every time you mention Asus or Netgear routers? Smile Seem to do it in every post lately, pointing out the issues you had with the WRT series and how they are garbage.


Not I, just speaking the truth based on my experiences. YMMV.

What I do know is when I was using the wrt3200acm running dd-wrt I had stability issues. Gave up on Belkin/Linksys/Marvell ever getting a good driver, which I guess they have moved closer to lately, and got a Netgear r8000p. It ran circles around the wrt3200acm in my simple iperf test, but the firmware from a stability standpoint was carp. Therefore the move to Asus rt-ac86u. For me with Merlin firmware the ac86u just runs. No issues and no need to reboot except for firmware update. Have a wrt1900acs v1 should you want it. Already unloaded the wrt3200acm.

As was stated YMMV. No router fits all circumstances. I have both 2.4 and 5 gig channels close by. Also the house I am in is wet plaster with metal lath, not the most desirable of building materials from a wireless standpoint.

--bill


Oh I know buddy, just busting your balls. If your looking to unload, I would take that acs v1, pm me.
myersw
DD-WRT Guru


Joined: 13 Jun 2006
Posts: 1609
Location: SE Michigan USA

PostPosted: Sun Jul 01, 2018 16:07    Post subject: Reply with quote
cybrnook wrote:
Oh I know buddy, just busting your balls. If your looking to unload, I would take that acs v1, pm me.


I knew that.

I have started twice to pm and I keep forgetting to hit send. Wink Yes it is yours for the asking.

Will give it another go.

--bill

_________________
Unifi Security Gateway: Unifi Firmware
Netgear r7800: Voxel Firmware
Modem:Netgear CM500V voice and Data.
ISP:Comcast
tutorial for flashing "WRT" series:
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=287813
DD-WRT Installation, Upgrade & Basic Setup–Cliff Notes:
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=311117
Kong DD-WRT Config Tutorial:
http://www.instructables.com/id/Install-and-Configure-a-DD-WRT-Kong-Router/
I tried to be normal once. Worst 2 minutes ever.
cybrnook
DD-WRT User


Joined: 08 Jan 2014
Posts: 288

PostPosted: Mon Jul 02, 2018 12:16    Post subject: Reply with quote
myersw wrote:
cybrnook wrote:
Oh I know buddy, just busting your balls. If your looking to unload, I would take that acs v1, pm me.


I knew that.

I have started twice to pm and I keep forgetting to hit send. Wink Yes it is yours for the asking.

Will give it another go.

--bill


Loud and clear, see you tomorrow Smile
ox400
DD-WRT Novice


Joined: 06 Jul 2018
Posts: 2

PostPosted: Fri Jul 06, 2018 12:29    Post subject: WRT3200ACM stability Reply with quote
Hello community.

I have been a fan of DD-WRT ever since my days using the WRT54GL which was rock solid. I had limited success installing onto WRT160NL - it just kept conking out after about a week.

I've now bought myself the WRT3200ACM and now wondering if I've bought a lemon.

So I've flashed with the r36247 beta and I seem to have the following issues:

- Router stability seems poor - having flashed and setup I left the unit switched on and when I come back next day uptime indicates it's rebooted at least once.
- At one point it appeared to have reset back to defaults
- There doesn't appear to be any support for mass storage filesystems - ext2/3, vfat etc nothing in /proc/filesystems do I need to manually load kernel mods.

Have I bought a lemon (hardware wise)?
If not can someone point in the right direction regarding ext2/3, vfat support and/or potential issues regarding reboots I should be aware of?

I'm happy to try and contribute to fixes if it'll help the cause!

EDIT - Twice now I've returned to the router only to find all my config has been erased and reset to defaults - luckily I backed them up but seriously what's going on with this unit?

Further EDIT - Managed to slurp the logs and figured out a number of kmod's weren't loading and added the following

insmod /lib/modules/4.9.110/nls_cp437.ko
insmod /lib/modules/4.9.110/exfat.ko
insmod /lib/modules/4.9.110/jbd2.ko
insmod /lib/modules/4.9.110/mbcache.ko
insmod /lib/modules/4.9.110/ext4.ko

to my startup script and now I can at least mount FAT and EXT partitions.

So my concern is still around the problems of resetting itself back to blank/factory settings and random reboots.

I've got syslogd connected and will monitor.
ox400
DD-WRT Novice


Joined: 06 Jul 2018
Posts: 2

PostPosted: Fri Jul 06, 2018 17:22    Post subject: Reply with quote
Ok so I got another unexpected reboot with the following trace in the logs
Code:

4>Jan  1 01:34:56 kernel: [ 5696.869573] [EXFAT] trying to mount...
<6>Jan  1 01:35:19 kernel: [ 5719.876324] device eth0 entered promiscuous mode
<4>Jan  1 01:35:20 kernel: [ 5720.149672] [<c011074c>] (__dma_alloc) from [<c01108b0>] (arm_coherent_dma_alloc+0x34/0x3c)
<4>Jan  1 01:35:20 kernel: [ 5720.158062] [<c01108b0>] (arm_coherent_dma_alloc) from [<c03bf9b0>] (mvneta_setup_txqs+0x314/0x4b8)
<4>Jan  1 01:35:20 kernel: [ 5720.167150] [<c03bf9b0>] (mvneta_setup_txqs) from [<c03bfb94>] (mvneta_open+0x40/0x194)
<4>Jan  1 01:35:20 kernel: [ 5720.175192] [<c03bfb94>] (mvneta_open) from [<c040b6cc>] (__dev_open+0xac/0x104)
<4>Jan  1 01:35:20 kernel: [ 5720.182623] [<c040b6cc>] (__dev_open) from [<c040b954>] (__dev_change_flags+0xb0/0x140)
<4>Jan  1 01:35:20 kernel: [ 5720.190663] [<c040b954>] (__dev_change_flags) from [<c040b9fc>] (dev_change_flags+0x18/0x48)
<4>Jan  1 01:35:20 kernel: [ 5720.199143] [<c040b9fc>] (dev_change_flags) from [<c04d0aa8>] (devinet_ioctl+0x2cc/0x744)
<4>Jan  1 01:35:20 kernel: [ 5720.207360] [<c04d0aa8>] (devinet_ioctl) from [<c03ef838>] (sock_ioctl+0x280/0x2c0)
<4>Jan  1 01:35:20 kernel: [ 5720.215054] [<c03ef838>] (sock_ioctl) from [<c01e8af0>] (do_vfs_ioctl+0x8c4/0x940)
<4>Jan  1 01:35:20 kernel: [ 5720.222658] [<c01e8af0>] (do_vfs_ioctl) from [<c01e8ba0>] (SyS_ioctl+0x34/0x58)
<4>Jan  1 01:35:20 kernel: [ 5720.296899] Normal free:7564kB min:2856kB low:3568kB high:4280kB active_anon:2536kB inactive_anon:0kB active_file:9868kB inactive_file:7124kB unevictable:16kB writepending:0kB present:524288kB managed:511848kB mlocked:0kB sla
<6>Jan  1 01:35:20 kernel: lowmem_reserve[]: 0 0 0
<4>Jan  1 01:35:20 kernel: [ 5720.332665] Normal: 355*4kB (UM) 274*8kB (UM) 193*16kB (UM) 15*32kB (UM) 6*64kB (UM) 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 7564kB
<6>Jan  1 01:35:20 kernel: 4252 total pagecache pages
<4>Jan  1 01:35:20 kernel: [ 5720.348317] 0 pages in swap cache
<4>Jan  1 01:35:20 kernel: [ 5720.351653] Swap cache stats: add 0, delete 0, find 0/0
<4>Jan  1 01:35:20 kernel: [ 5720.356928] Free swap  = 0kB
<4>Jan  1 01:35:20 kernel: [ 5720.359818] Total swap = 0kB
<4>Jan  1 01:35:20 kernel: [ 5720.362742] 131072 pages RAM
<4>Jan  1 01:35:20 kernel: [ 5720.365638] 0 pages HighMem/MovableOnly
<4>Jan  1 01:35:20 kernel: [ 5720.369488] 3110 pages reserved
<3>Jan  1 01:35:20 kernel: [ 5720.372658] mvneta f1034000.ethernet eth0: mvneta_setup_txqs: can't create txq=2
<4>Jan  1 01:35:20 kernel: [ 5720.380105] ------------[ cut here ]------------
<4>Jan  1 01:35:20 kernel: [ 5720.384762] WARNING: CPU: 0 PID: 15092 at arch/arm/mm/dma-mapping.c:916 __arm_dma_free.constprop.2+0xf4/0x128
<4>Jan  1 01:35:20 kernel: [ 5720.394729] Freeing invalid buffer c1370000
<4>Jan  1 01:35:20 kernel: [ 5720.398927] Modules linked in: ext4 mbcache jbd2 exfat nls_cp437 shortcut_fe jffs2 ledtrig_usbport pwrseq_simple pwrseq_emmc ahci_mvebu ahci_platform ahci libahci_platform libahci ehci_orion sata_mv usb_storage sd_mod xhci_pl
<4>Jan  1 01:35:20 kernel: [ 5720.445463] CPU: 0 PID: 15092 Comm: redial Tainted: P                4.9.110 #178
<4>Jan  1 01:35:20 kernel: [ 5720.452977] Hardware name: Marvell Armada 380/385 (Device Tree)
<4>Jan  1 01:35:20 kernel: [ 5720.458929] [<c010ed78>] (unwind_backtrace) from [<c010abdc>] (show_stack+0x10/0x14)
<4>Jan  1 01:35:20 kernel: [ 5720.466708] [<c010abdc>] (show_stack) from [<c02b5270>] (dump_stack+0x88/0x9c)
<4>Jan  1 01:35:20 kernel: [ 5720.473964] [<c02b5270>] (dump_stack) from [<c0122c24>] (__warn+0xe4/0x100)
<4>Jan  1 01:35:20 kernel: [ 5720.480957] [<c0122c24>] (__warn) from [<c0122c78>] (warn_slowpath_fmt+0x38/0x48)
<4>Jan  1 01:35:20 kernel: [ 5720.488474] [<c0122c78>] (warn_slowpath_fmt) from [<c01104e4>] (__arm_dma_free.constprop.2+0xf4/0x128)
<4>Jan  1 01:35:20 kernel: [ 5720.497825] [<c01104e4>] (__arm_dma_free.constprop.2) from [<c03bd458>] (mvneta_cleanup_txqs+0x1e8/0x2b0)
<4>Jan  1 01:35:20 kernel: [ 5720.507436] [<c03bd458>] (mvneta_cleanup_txqs) from [<c03bfb28>] (mvneta_setup_txqs+0x48c/0x4b8)
<4>Jan  1 01:35:20 kernel: [ 5720.516261] [<c03bfb28>] (mvneta_setup_txqs) from [<c03bfb94>] (mvneta_open+0x40/0x194)
<4>Jan  1 01:35:20 kernel: [ 5720.524302] [<c03bfb94>] (mvneta_open) from [<c040b6cc>] (__dev_open+0xac/0x104)
<4>Jan  1 01:35:20 kernel: [ 5720.531732] [<c040b6cc>] (__dev_open) from [<c040b954>] (__dev_change_flags+0xb0/0x140)
<4>Jan  1 01:35:20 kernel: [ 5720.539773] [<c040b954>] (__dev_change_flags) from [<c040b9fc>] (dev_change_flags+0x18/0x48)
<4>Jan  1 01:35:20 kernel: [ 5720.548252] [<c040b9fc>] (dev_change_flags) from [<c04d0aa8>] (devinet_ioctl+0x2cc/0x744)
<4>Jan  1 01:35:20 kernel: [ 5720.556468] [<c04d0aa8>] (devinet_ioctl) from [<c03ef838>] (sock_ioctl+0x280/0x2c0)
<4>Jan  1 01:35:20 kernel: [ 5720.610314] Modules linked in: ext4 mbcache jbd2 exfat nls_cp437 shortcut_fe jffs2 ledtrig_usbport pwrseq_simple pwrseq_emmc ahci_mvebu ahci_platform ahci libahci_platform libahci ehci_orion sata_mv usb_storage sd_mod xhci_pl
<4>Jan  1 01:35:20 kernel: [ 5720.656831] CPU: 0 PID: 15092 Comm: redial Tainted: P        W       4.9.110 #178
<4>Jan  1 01:35:20 kernel: [ 5720.664346] Hardware name: Marvell Armada 380/385 (Device Tree)
<4>Jan  1 01:35:20 kernel: [ 5720.670297] [<c010ed78>] (unwind_backtrace) from [<c010abdc>] (show_stack+0x10/0x14)
<4>Jan  1 01:35:20 kernel: [ 5720.678078] [<c010abdc>] (show_stack) from [<c02b5270>] (dump_stack+0x88/0x9c)
<4>Jan  1 01:35:20 kernel: [ 5720.685332] [<c02b5270>] (dump_stack) from [<c0122c24>] (__warn+0xe4/0x100)
<4>Jan  1 01:35:20 kernel: [ 5720.692324] [<c0122c24>] (__warn) from [<c0122c78>] (warn_slowpath_fmt+0x38/0x48)
<4>Jan  1 01:35:20 kernel: [ 5720.699841] [<c0122c78>] (warn_slowpath_fmt) from [<c01104e4>] (__arm_dma_free.constprop.2+0xf4/0x128)
<4>Jan  1 01:35:20 kernel: [ 5720.709192] [<c01104e4>] (__arm_dma_free.constprop.2) from [<c03bd394>] (mvneta_cleanup_txqs+0x124/0x2b0)
<4>Jan  1 01:35:20 kernel: [ 5720.718803] [<c03bd394>] (mvneta_cleanup_txqs) from [<c03bfb28>] (mvneta_setup_txqs+0x48c/0x4b8)
<4>Jan  1 01:35:20 kernel: [ 5720.727627] [<c03bfb28>] (mvneta_setup_txqs) from [<c03bfb94>] (mvneta_open+0x40/0x194)
<4>Jan  1 01:35:20 kernel: [ 5720.735668] [<c03bfb94>] (mvneta_open) from [<c040b6cc>] (__dev_open+0xac/0x104)
<4>Jan  1 01:35:20 kernel: [ 5720.743098] [<c040b6cc>] (__dev_open) from [<c040b954>] (__dev_change_flags+0xb0/0x140)
<4>Jan  1 01:35:20 kernel: [ 5720.751137] [<c040b954>] (__dev_change_flags) from [<c040b9fc>] (dev_change_flags+0x18/0x48)
<4>Jan  1 01:35:20 kernel: [ 5720.759615] [<c040b9fc>] (dev_change_flags) from [<c04d0aa8>] (devinet_ioctl+0x2cc/0x744)
<4>Jan  1 01:35:20 kernel: [ 5720.767831] [<c04d0aa8>] (devinet_ioctl) from [<c03ef838>] (sock_ioctl+0x280/0x2c0)
<4>Jan  1 01:35:21 kernel: [ 5720.986867] [<c03ef838>] (sock_ioctl) from [<c01e8af0>] (do_vfs_ioctl+0x8c4/0x940)
<4>Jan  1 01:35:21 kernel: [ 5720.994472] [<c01e8af0>] (do_vfs_ioctl) from [<c01e8ba0>] (SyS_ioctl+0x34/0x58)
<4>Jan  1 01:35:21 kernel: [ 5721.001814] [<c01e8ba0>] (SyS_ioctl) from [<c0107580>] (ret_fast_syscall+0x0/0x48)
<4>Jan  1 01:35:21 kernel: [ 5721.009475] ---[ end trace c107883cf4668d94 ]---
<4>Jan  1 01:35:21 kernel: [ 5721.014216] ------------[ cut here ]------------
<4>Jan  1 01:35:21 kernel: [ 5721.018858] WARNING: CPU: 0 PID: 15092 at arch/arm/mm/dma-mapping.c:916 __arm_dma_free.constprop.2+0xf4/0x128
<4>Jan  1 01:35:21 kernel: [ 5721.028828] Freeing invalid buffer df300000
<4>Jan  1 01:35:21 kernel: [ 5721.033037] Modules linked in: ext4 mbcache jbd2 exfat nls_cp437 shortcut_fe jffs2 ledtrig_usbport pwrseq_simple pwrseq_emmc ahci_mvebu ahci_platform ahci libahci_platform libahci ehci_orion sata_mv usb_storage sd_mod xhci_pl
<4>Jan  1 01:35:21 kernel: [ 5721.079586] CPU: 0 PID: 15092 Comm: redial Tainted: P        W       4.9.110 #178
<4>Jan  1 01:35:21 kernel: [ 5721.087099] Hardware name: Marvell Armada 380/385 (Device Tree)
<4>Jan  1 01:35:21 kernel: [ 5721.093050] [<c010ed78>] (unwind_backtrace) from [<c010abdc>] (show_stack+0x10/0x14)
<4>Jan  1 01:35:21 kernel: [ 5721.100830] [<c010abdc>] (show_stack) from [<c02b5270>] (dump_stack+0x88/0x9c)
<4>Jan  1 01:35:21 kernel: [ 5721.108085] [<c02b5270>] (dump_stack) from [<c0122c24>] (__warn+0xe4/0x100)
<4>Jan  1 01:35:21 kernel: [ 5721.115078] [<c0122c24>] (__warn) from [<c0122c78>] (warn_slowpath_fmt+0x38/0x48)
<4>Jan  1 01:35:21 kernel: [ 5721.122596] [<c0122c78>] (warn_slowpath_fmt) from [<c01104e4>] (__arm_dma_free.constprop.2+0xf4/0x128)
<4>Jan  1 01:35:21 kernel: [ 5721.131946] [<c01104e4>] (__arm_dma_free.constprop.2) from [<c03bd394>] (mvneta_cleanup_txqs+0x124/0x2b0)
<4>Jan  1 01:35:21 kernel: [ 5721.141557] [<c03bd394>] (mvneta_cleanup_txqs) from [<c03bfb28>] (mvneta_setup_txqs+0x48c/0x4b8)
<4>Jan  1 01:35:21 kernel: [ 5721.150383] [<c03bfb28>] (mvneta_setup_txqs) from [<c03bfb94>] (mvneta_open+0x40/0x194)
<4>Jan  1 01:35:21 kernel: [ 5721.158425] [<c03bfb94>] (mvneta_open) from [<c040b6cc>] (__dev_open+0xac/0x104)
<4>Jan  1 01:35:21 kernel: [ 5721.165855] [<c040b6cc>] (__dev_open) from [<c040b954>] (__dev_change_flags+0xb0/0x140)
<4>Jan  1 01:35:21 kernel: [ 5721.173894] [<c040b954>] (__dev_change_flags) from [<c040b9fc>] (dev_change_flags+0x18/0x48)
<4>Jan  1 01:35:21 kernel: [ 5721.182372] [<c040b9fc>] (dev_change_flags) from [<c04d0aa8>] (devinet_ioctl+0x2cc/0x744)
<4>Jan  1 01:35:21 kernel: [ 5721.190588] [<c04d0aa8>] (devinet_ioctl) from [<c03ef838>] (sock_ioctl+0x280/0x2c0)
<4>Jan  1 01:35:21 kernel: [ 5721.409606] [<c03ef838>] (sock_ioctl) from [<c01e8af0>] (do_vfs_ioctl+0x8c4/0x940)
<4>Jan  1 01:35:21 kernel: [ 5721.417211] [<c01e8af0>] (do_vfs_ioctl) from [<c01e8ba0>] (SyS_ioctl+0x34/0x58)
<4>Jan  1 01:35:21 kernel: [ 5721.424554] [<c01e8ba0>] (SyS_ioctl) from [<c0107580>] (ret_fast_syscall+0x0/0x48)
<4>Jan  1 01:35:21 kernel: [ 5721.432196] ---[ end trace c107883cf4668d96 ]---
<4>Jan  1 01:35:21 kernel: [ 5721.436923] ------------[ cut here ]------------
<4>Jan  1 01:35:21 kernel: [ 5721.441571] WARNING: CPU: 0 PID: 15092 at arch/arm/mm/dma-mapping.c:916 __arm_dma_free.constprop.2+0xf4/0x128
<4>Jan  1 01:35:21 kernel: [ 5721.451539] Freeing invalid buffer df340000
<4>Jan  1 01:35:21 kernel: [ 5721.455738] Modules linked in: ext4 mbcache jbd2 exfat nls_cp437 shortcut_fe jffs2 ledtrig_usbport pwrseq_simple pwrseq_emmc ahci_mvebu ahci_platform ahci libahci_platform libahci ehci_orion sata_mv usb_storage sd_mod xhci_pl
<4>Jan  1 01:35:21 kernel: [ 5721.502268] CPU: 0 PID: 15092 Comm: redial Tainted: P        W       4.9.110 #178
<4>Jan  1 01:35:21 kernel: [ 5721.509782] Hardware name: Marvell Armada 380/385 (Device Tree)
<4>Jan  1 01:35:21 kernel: [ 5721.515731] [<c010ed78>] (unwind_backtrace) from [<c010abdc>] (show_stack+0x10/0x14)
<4>Jan  1 01:35:21 kernel: [ 5721.523511] [<c010abdc>] (show_stack) from [<c02b5270>] (dump_stack+0x88/0x9c)
<4>Jan  1 01:35:21 kernel: [ 5721.530766] [<c02b5270>] (dump_stack) from [<c0122c24>] (__warn+0xe4/0x100)
<4>Jan  1 01:35:21 kernel: [ 5721.537758] [<c0122c24>] (__warn) from [<c0122c78>] (warn_slowpath_fmt+0x38/0x48)
<4>Jan  1 01:35:21 kernel: [ 5721.545276] [<c0122c78>] (warn_slowpath_fmt) from [<c01104e4>] (__arm_dma_free.constprop.2+0xf4/0x128)
<4>Jan  1 01:35:21 kernel: [ 5721.554625] [<c01104e4>] (__arm_dma_free.constprop.2) from [<c03bd394>] (mvneta_cleanup_txqs+0x124/0x2b0)
<4>Jan  1 01:35:21 kernel: [ 5721.564236] [<c03bd394>] (mvneta_cleanup_txqs) from [<c03bfb28>] (mvneta_setup_txqs+0x48c/0x4b8)
<4>Jan  1 01:35:21 kernel: [ 5721.573061] [<c03bfb28>] (mvneta_setup_txqs) from [<c03bfb94>] (mvneta_open+0x40/0x194)
<4>Jan  1 01:35:21 kernel: [ 5721.581101] [<c03bfb94>] (mvneta_open) from [<c040b6cc>] (__dev_open+0xac/0x104)
<4>Jan  1 01:35:21 kernel: [ 5721.588531] [<c040b6cc>] (__dev_open) from [<c040b954>] (__dev_change_flags+0xb0/0x140)
<4>Jan  1 01:35:21 kernel: [ 5721.596571] [<c040b954>] (__dev_change_flags) from [<c040b9fc>] (dev_change_flags+0x18/0x48)
<4>Jan  1 01:35:21 kernel: [ 5721.605048] [<c040b9fc>] (dev_change_flags) from [<c04d0aa8>] (devinet_ioctl+0x2cc/0x744)
<4>Jan  1 01:35:21 kernel: [ 5721.613264] [<c04d0aa8>] (devinet_ioctl) from [<c03ef838>] (sock_ioctl+0x280/0x2c0)
<4>Jan  1 01:34:56 kernel: [ 5696.869573] [EXFAT] trying to mount...
<6>Jan  1 01:35:19 kernel: [ 5719.876324] device eth0 entered promiscuous mode
<4>Jan  1 01:35:20 kernel: [ 5720.149672] [<c011074c>] (__dma_alloc) from [<c01108b0>] (arm_coherent_dma_alloc+0x34/0x3c)
<4>Jan  1 01:35:20 kernel: [ 5720.158062] [<c01108b0>] (arm_coherent_dma_alloc) from [<c03bf9b0>] (mvneta_setup_txqs+0x314/0x4b8)
<4>Jan  1 01:35:20 kernel: [ 5720.167150] [<c03bf9b0>] (mvneta_setup_txqs) from [<c03bfb94>] (mvneta_open+0x40/0x194)
<4>Jan  1 01:35:20 kernel: [ 5720.175192] [<c03bfb94>] (mvneta_open) from [<c040b6cc>] (__dev_open+0xac/0x104)


I was attempting to mount a USB device a few seconds previously
Goto page Previous  1, 2, 3 ... , 197, 198, 199  Next Display posts from previous:    Page 198 of 199
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Marvell MVEBU based Hardware (WRT1900AC etc.) 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 cannot attach files in this forum
You cannot download files in this forum