Samba and Sonos crash on r43171 on Linksys WRT3200ACM

Post new topic   Reply to topic    DD-WRT Forum Index -> Marvell MVEBU based Hardware (WRT1900AC etc.)
Author Message
dissonant
DD-WRT Novice


Joined: 24 May 2019
Posts: 9

PostPosted: Sat Apr 16, 2022 21:03    Post subject: Samba and Sonos crash on r43171 on Linksys WRT3200ACM Reply with quote
Hi everyone! I have a Linksys WRT3200ACM running r43171. I was running a newer build, but when researching my issues with Samba, found several posts pointing to build r43171 as being "THE" build with stable Samba. I've been running it maybe a month now and the Samba does not seem stable. Most times if I log into the router and click on "Apply Settings", Samba is back up and running. This also seems to fix issues when not connecting to my Sonos wireless speakers. I could go into the specifics of my issues, post the logs and whatever, but really I just want to know what is the most stable build for my hardware. I don't think its my config because it works until it doesn't and then a reboot fixes it and then it works again....

Thanks everyone for your time in advance!
Sponsor
dissonant
DD-WRT Novice


Joined: 24 May 2019
Posts: 9

PostPosted: Sun Apr 17, 2022 0:13    Post subject: logs from event last night Reply with quote
Last night I had issues accessing the Samba share so rebooting it fixed it. But I noticed later today an alert for a logging rate increase. Papertrail shows normally ~600 events in 12 minutes, but jumped up to 1.2M last night. Here is what kicked it off:

logger : Caught SIGSEGV (11) in strcmp
logger : Fault at memory location 0x00000000 due to address not mapped to object (1).
logger : Thread 18606: ksmbd.mountd
logger : === Context:
logger : TRAPNO:0000000e ERRCODE:00000017 OLDMASK:00000000 R0:b6f6bfc0
logger : R1:00000000 R2:00000010 R3:0000006d R4:00035f20
logger : R5:0003175c R6:00000000 R7:00000000 R8:b6ed494c
logger : R9:00000000 R10:00035de8 FP:b6f6b24c IP:00031050
logger : SP:b6e6bc90 LR:00018418 PC:b6f3b758 CPSR:60000010
logger : FAULTADDR:00000000
logger : === Backtrace:
logger : # Searching frame 0 (FP=0xb6f6b24c, PC=0xb6f3b758)
logger : # PC-9f4[0xb6f3ad64]: 0xe92d4ff0 stmfd sp!
logger : # FP-00[0xb6f6b24c]: 0x00000000 {LR}
logger : # FP-04[0xb6f6b248]: 0x00001000 {FP}
logger : # FP-08[0xb6f6b244]: 0x00000001 {R10}
logger : # FP-0c[0xb6f6b240]: 0x00000004 {R9}
logger : # FP-10[0xb6f6b23c]: 0x000000d0 {R8}
logger : # FP-14[0xb6f6b238]: 0xb6f697d4 {R7}
logger : # FP-18[0xb6f6b234]: 0xbe8e5ce8 {R6}
logger : # FP-1c[0xb6f6b230]: 0x00000001 {R5}
logger : # FP-20[0xb6f6b22c]: 0x00000000 {R4}
logger : # Crashed at /lib/ld-musl-armhf.so.1[0xb6ef1000](strcmp+0x00000004)[0xb6f3b758]
logger : # Searching frame 1 (FP=0x00001000, PC=0x00000000)
logger : # Instruction at 0x00000000 is not mapped; terminating backtrace.
logger : /lib/ld-musl-armhf.so.1[0xb6ef1000](strcmp+0x00000004)[0xb6f3b758]
logger : ???(+0)[0x00000000]
logger : === Code:
logger : b6f3b718: 0afffff6 e5d03000 e3530000 08bd8070 e1530001 08bd8070 e5f03001 e3530000
logger : b6f3b738: 08bd8070 e1530001 1afffffa e8bd8070 eb0000d9 e0840000 e8bd8070 e5d03000
logger : b6f3b758: >e5d12000 e1520003 0a000004 ea000005 e5f03001 e5f12001 e1530002 1a000001
logger : b6f3b778: e3530000 1afffff9 e0430002 e12fff1e e92d4010 e1a04000 ebfffef6 e1a00004
ksmbd [ksmbd-worker/2001]: ERROR: Child received signal: 11 (Segmentation fault)
ksmbd [ksmbd-worker/2001]: ERROR: Recv() error Bad socket [-3]
logger : Caught SIGILL (4) in free
logger : Fault at memory location 0xb6f19688 due to illegal opcode (1).
logger : Thread 2001: ksmbd.mountd
logger : === Context:
logger : TRAPNO:00000006 ERRCODE:00000000 OLDMASK:00000000 R0:b6ed4957
logger : R1:00000061 R2:00000020 R3:b6ed49a0 R4:b6ed47c0
logger : R5:b6ed4b4c R6:0001b2bc R7:00000000 R8:00000000
logger : R9:0003134c R10:0001fa79 FP:be8e5adc IP:0003115c
logger : SP:be8e5a60 LR:00018488 PC:b6f19688 CPSR:20000010
logger : FAULTADDR:00000000
logger : === Backtrace:
logger : # Searching frame 0 (FP=0xbe8e5adc, PC=0xb6f19688)
logger : # PC-7a0[0xb6f18ee8]: 0xe92d4ff0 stmfd sp!
logger : # FP-00[0xbe8e5adc]: 0x0001547c {LR}
logger : # FP-04[0xbe8e5ad8]: 0x00008000 {FP}
logger : # FP-08[0xbe8e5ad4]: 0x00008000 {R10}
logger : # FP-0c[0xbe8e5ad0]: 0x000315a0 {R9}
logger : # FP-10[0xbe8e5acc]: 0x00000000 {R8}
logger : # FP-14[0xbe8e5ac8]: 0x00000001 {R7}
logger : # FP-18[0xbe8e5ac4]: 0x00000000 {R6}
logger : # FP-1c[0xbe8e5ac0]: 0xbe8e5ba4 {R5}
logger : # FP-20[0xbe8e5abc]: 0xfffffffd {R4}
logger : # Crashed at /lib/ld-musl-armhf.so.1[0xb6ef1000](free+0x00000030)[0xb6f19688]
logger : # Searching frame 1 (FP=0x00008000, PC=0x0001547c)
logger : # PC-f98[0x000144e4]: 0xe92d4ff8 stmfd sp!
logger : # Stack at 0x00008000 is not mapped; terminating backtrace.
logger : /lib/ld-musl-armhf.so.1[0xb6ef1000](free+0x00000030)[0xb6f19688]
logger : /usr/sbin/ksmbd.mountd[0x00010000](+0x0000547c)[0x0001547c]
logger : === Code:
logger : b6f19648: 1afffff4 eaffffeb 00051cc4 00051c64 e2503000 012fff1e e5132004 e2430008
logger : b6f19668: e3120001 1a000007 e5131008 e3c22001 e3110001 e0400001 e0821001 0a000000
logger : b6f19688: >e7f000f0 ea001bf8 eafffcb1 e92d4ff0 e2505000 e24dd00c 0a000069 e59f0204
logger : b6f196a8: e30f3fef e3473fff e2412001 e08f0000 e5900024 e0433000 e1530002 3a000023
ksmbd [ksmbd-worker/2001]: ERROR: Child received signal: 4 (Illegal instruction)
blkt
DD-WRT Guru


Joined: 20 Jan 2019
Posts: 5660

PostPosted: Sun Apr 17, 2022 2:00    Post subject: Reply with quote
r43171 may have been a build to use May 2020 certainly not the case today or from any perspective.
Unfortunately, nobody can help to solve deprecated builds with security problems etc. r48607 r48646

If concerned about bleeding edge builds and want to avoid a recent ksmbd changeset choose r48567.
Flash a build, allow reboot, then reset: GUI factory defaults, reset button 10 seconds or nvram erase.
dissonant
DD-WRT Novice


Joined: 24 May 2019
Posts: 9

PostPosted: Sun Apr 17, 2022 2:31    Post subject: Reply with quote
I have no problem updating to a newer build. My main desire is that the build have stable Samba. When I was searching the forums, it sounded like there were issues with Samba in the later builds. I didn't see newer posts saying the Samba issue was finally resolved. Does r48567 have stable Samba?
dissonant
DD-WRT Novice


Joined: 24 May 2019
Posts: 9

PostPosted: Sun Apr 17, 2022 23:33    Post subject: Reply with quote
OK, updated to r48567 as you suggested. Having strange issues with the mounting of drives in this build. I have a USB HD attached that has 3 partitions. I have volume labels for SDA1->3 as Share, BAD, and Video (I have a section of the disk with bad sectors that I located and partitioned off so I don't use it). For some reason, this build mounted the SDA2 as Video partition and mounted the video partition as SDA3. So I pulled the drive, deleted the file system of the bad partition and remounted. Now its showing SDA2 mounted to Video and SDA3 also mounted to Video. It shows both SDA 2 and SDA3 as the size of SDA3. Strange stuff. But at least when I mount the Video Samba share it does load up the correct drive. I'll see how stable it is.
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT 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