On Wed, 26 Mar 2025 18:37:00 +0000
ABC DEF <ms4se...@hotmail.com> wrote:

> Hello,
> 
> There's a new problem related to this issue.
> 
> In dnsmasq v2.92test1, we have a proper date (so we have already working 
> connection), but dnsmasq still sigsegv after first DHCPREQUEST...
> 
> Logs:
> Mar 26 16:04:37 router daemon.info dnsmasq-dhcp[3384]: DHCPREQUEST(br0) 
> 192.168.1.1 XX:XX:XX
> Mar 26 16:04:37 router daemon.info dnsmasq-dhcp[3384]: DHCPACK(br0) 
> 192.168.1.1 XX:XX:XX user
> Mar 26 16:13:15 router kern.warn kernel: dnsmasq/11994: potentially 
> unexpected fatal signal 11.

IIIRC, in my experience over the years, signal 11 usually indicated a memory 
problem. In my cases, it was usually a flaky or inadequate power supply causing 
the CPU to misbehave. As I recall, it mostly happened when compiling GCC which 
typically gave the memory subsystem a good workout.

My fingers remain sheathed, not pointing anywhere in particular. I bring it up 
as a possible alternative explanation. Case in point, many less expensive power 
supplies have two 12VDC rails that supply, mmm, 22W or so each. I have a few 
systems that were marginal with these. On today's systems, the CPU can demand a 
good deal more than that. That's why my power supplies have a single 12V rail 
that supplies 60W or more. Just a bit of neural food.

N


> Mar 26 16:13:15 router kern.warn kernel: Pid: 11994, comm: dnsmasq
> Mar 26 16:13:15 router kern.warn kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm 
> #2)
> Mar 26 16:13:15 router kern.warn kernel: PC is at 0x2a93c
> Mar 26 16:13:15 router kern.warn kernel: LR is at 0x4bd24
> Mar 26 16:13:15 router kern.warn kernel: pc : [<0002a93c>] lr : [<0004bd24>] 
> psr: 20000010
> Mar 26 16:13:15 router kern.warn kernel: sp : bed8fa30 ip : 00010000 fp : 
> 400dfb04
> Mar 26 16:13:15 router daemon.warn dnsmasq[3384]: TCP helper process 11994 
> died unexpectedly
> Mar 26 16:13:15 router kern.warn kernel: r10: 666f2e73 r9 : 008878e2 r8 : 
> 008878e0
> Mar 26 16:13:15 router kern.warn kernel: r7 : 00091e3c r6 : 666f2e73 r5 : 
> 00093830 r4 : 00040000
> Mar 26 16:13:15 router kern.warn kernel: r3 : 40137008 r2 : 00000000 r1 : 
> 008878e2 r0 : 400dfb04
> Mar 26 16:13:15 router kern.warn kernel: Flags: nzCv IRQs on FIQs on Mode 
> USER_32 ISA ARM Segment user
> Mar 26 16:13:15 router kern.warn kernel: Control: 10c53c7d Table: 8df1004a 
> DAC: 00000015
> Mar 26 16:13:15 router kern.warn kernel: dnsmasq/12041: potentially 
> unexpected fatal signal 11.
> Mar 26 16:13:15 router kern.warn kernel: Pid: 12041, comm: dnsmasq
> Mar 26 16:13:15 router kern.warn kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm 
> #2)
> Mar 26 16:13:15 router daemon.warn dnsmasq[3384]: TCP helper process 12041 
> died unexpectedly
> Mar 26 16:13:15 router kern.warn kernel: PC is at 0x2a93c
> Mar 26 16:13:15 router kern.warn kernel: LR is at 0x4bd24
> Mar 26 16:13:15 router kern.warn kernel: pc : [<0002a93c>] lr : [<0004bd24>] 
> psr: 20000010
> Mar 26 16:13:15 router kern.warn kernel: sp : bed8fa30 ip : 00010000 fp : 
> 400dfb04
> Mar 26 16:13:15 router kern.warn kernel: r10: 666f2e73 r9 : 008878e2 r8 : 
> 008878e0
> Mar 26 16:13:15 router kern.warn kernel: r7 : 00091e3c r6 : 666f2e73 r5 : 
> 00093830 r4 : 00040000
> Mar 26 16:13:15 router kern.warn kernel: r3 : 40137008 r2 : 00000000 r1 : 
> 008878e2 r0 : 400dfb04
> Mar 26 16:13:15 router kern.warn kernel: Flags: nzCv IRQs on FIQs on Mode 
> USER_32 ISA ARM Segment user
> Mar 26 16:13:15 router kern.warn kernel: Control: 10c53c7d Table: 8df1004a 
> DAC: 00000015
> Mar 26 16:13:15 router kern.warn kernel: dnsmasq/3384: potentially unexpected 
> fatal signal 11.
> Mar 26 16:13:15 router kern.warn kernel: Pid: 3384, comm: dnsmasq
> Mar 26 16:13:15 router kern.warn kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm 
> #2)
> Mar 26 16:13:15 router kern.warn kernel: PC is at 0x2e404
> Mar 26 16:13:15 router kern.warn kernel: LR is at 0x92c18
> Mar 26 16:13:15 router kern.warn kernel: pc : [<0002e404>] lr : [<00092c18>] 
> psr: 00000010
> Mar 26 16:13:15 router kern.warn kernel: sp : bed8faf0 ip : 00029e54 fp : 
> 0000000e
> Mar 26 16:13:15 router kern.warn kernel: r10: 00000000 r9 : bed8fb2c r8 : 
> 00091e3c
> Mar 26 16:13:15 router kern.warn kernel: r7 : 00091e3c r6 : 00000000 r5 : 
> 00095f20 r4 : 00870c30
> Mar 26 16:13:15 router kern.warn kernel: r3 : 00092c18 r2 : 40137008 r1 : 
> 40137008 r0 : 666f2e73
> Mar 26 16:13:15 router kern.warn kernel: Flags: nzcv IRQs on FIQs on Mode 
> USER_32 ISA ARM Segment user
> Mar 26 16:13:15 router kern.warn kernel: Control: 10c53c7d Table: 8ec2404a 
> DAC: 00000015
> Mar 26 16:23:05 router daemon.err mdu[21440]: libcurl error (6) - Could not 
> resolve host: ipecho.net.
> Mar 26 16:35:04 router daemon.err mdu[1167]: libcurl error (6) - Could not 
> resolve host: ip.changeip.com.
> Mar 26 16:49:04 router daemon.err mdu[14931]: libcurl error (6) - Could not 
> resolve host: checkip.dyndns.org.
> 
> 
> Thank you :-)


_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

Reply via email to