From owner-freebsd-current@freebsd.org Thu Jan 10 16:42:15 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 761B5149197B for ; Thu, 10 Jan 2019 16:42:15 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A1A68B4A7 for ; Thu, 10 Jan 2019 16:42:14 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id hdP9g6eehMRX3hdPBgM167; Thu, 10 Jan 2019 09:42:07 -0700 X-Authority-Analysis: v=2.3 cv=TL87tGta c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=3JhidrIBZZsA:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=pGLkceISAAAA:8 a=zxA2vyXaAAAA:8 a=a6jSseMrPDomPGwWWVEA:9 a=cFkQbExWlAKOErlC:21 a=PfYrB5TaTSHI8t-E:21 a=CjuIK1q_8ugA:10 a=uo3pI9vGLFKeQ1DzcpwA:9 a=Mh7EvCmd4V8KQBLv:21 a=GpSpQbDJ3-cdjW-D:21 a=kzB1xdqqNWkTQPm6:21 a=_W_S_7VecoQA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=nK2txNHJmq7TfjpuLlwI:22 Received: from [10.168.100.68] (S0106788a207e2972.gv.shawcable.net [70.66.154.233]) by spqr.komquats.com (Postfix) with ESMTPSA id DFD951E1F; Thu, 10 Jan 2019 08:42:01 -0800 (PST) MIME-Version: 1.0 From: Cy Schubert Subject: RE: kernel panic in wireless-related sysctl walk Date: Thu, 10 Jan 2019 08:42:10 -0800 To: Michael Zhilin , Michael Butler CC: freebsd-current Message-Id: <20190110164201.DFD951E1F@spqr.komquats.com> X-CMAE-Envelope: MS4wfMQtHbTtNs0Hr7kPUM1ExxtyVkEpBFw1RRc/YRhYhbzLuFqibKkT+tbK76wjGeGnJ7ZcUosVoZm2EVoW7rk3YwkME5YWwESF1MYsJ1//UIAwGf2wDGv5 tIZtaHOps/KWnDHE8aiGLVdpha2sz1FrPUIkbDZ0wOv+uIEjXeLtwbUavUyE78OwyPICmT7RwhAbtNZAeD9oACzaJ0AcRFXPYIFnSU3t4uZoPp0UhGC3ft9C QzXTtUUORrtGs5Bq/mvsag== X-Rspamd-Queue-Id: 6A1A68B4A7 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-4.05 / 15.00]; ARC_NA(0.00)[]; FAKE_REPLY(1.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(-1.88)[ip: (-5.12), ipnet: 64.59.128.0/20(-2.32), asn: 6327(-1.86), country: CA(-0.09)]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: spqr.komquats.com]; NEURAL_HAM_SHORT(-0.96)[-0.959,0]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.zen.spamhaus.org : 127.0.0.11]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_IN_DNSWL_LOW(-0.10)[12.134.59.64.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jan 2019 16:42:15 -0000 I'll add a me too, though I haven't found the time to dig further, as no du= mp is produced nor a panic string printed. I currently have iwn and will try to reproduce at noon. --- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Apologies. Cy Schubert or The need of the many outweighs the greed of the few. --- -----Original Message----- From: Michael Zhilin Sent: 10/01/2019 08:00 To: Michael Butler Cc: freebsd-current Subject: Re: kernel panic in wireless-related sysctl walk I'm not lucky to reproduce it even if i use iwn and "sysctl net.wlan.0.rate_stats" Problem is related to 802.11n, but all my networks are 11g. BR On Thu, Jan 10, 2019 at 6:53 PM Michael Zhilin wrote: > Hi, > > Is it possible to print out any local variables of frame #8? > > Thx! > > On Thu, Jan 10, 2019 at 6:31 PM Michael Butler > wrote: > >> With 'device iwn' and all the related wireless bits compiled into a >> custom kernel for a laptop, executing 'sysctl -a' yields a kernel panic >> of the form .. >> >> Fatal trap 12: page fault while in kernel mode >> cpuid =3D 1; apic id =3D 01 >> fault virtual address =3D 0x8 >> fault code =3D supervisor read data, page not present >> instruction pointer =3D 0x20:0xffffffff809bf22c >> stack pointer =3D 0x28:0xfffffe0097fb7660 >> frame pointer =3D 0x28:0xfffffe0097fb7670 >> code segment =3D base 0x0, limit 0xfffff, type 0x1b >> =3D DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags =3D interrupt enabled, resume, IOPL =3D 0 >> current process =3D 11053 (sysctl) >> trap number =3D 12 >> panic: page fault >> cpuid =3D 1 >> time =3D 1547129798 >> Uptime: 3d10h27m14s >> Dumping 3840 out of 16258 >> MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% >> >> [ .. ] >> >> (kgdb) #0 doadump (textdump=3D) at pcpu.h:230 >> #1 0xffffffff808704eb in kern_reboot (howto=3D260) >> at /usr/src/sys/kern/kern_shutdown.c:451 >> #2 0xffffffff80870920 in vpanic (fmt=3D, >> ap=3D) at /usr/src/sys/kern/kern_shutdown.c:877 >> #3 0xffffffff80870753 in panic (fmt=3D) >> at /usr/src/sys/kern/kern_shutdown.c:804 >> #4 0xffffffff80c63b5b in trap_fatal (frame=3D0xfffffe0097fb75a0, eva=3D= 8) >> at /usr/src/sys/amd64/amd64/trap.c:929 >> #5 0xffffffff80c63f10 in trap_pfault (frame=3D0xfffffe0097fb75a0, >> usermode=3D0) >> at /usr/src/sys/amd64/amd64/trap.c:839 >> #6 0xffffffff80c632be in trap (frame=3D0xfffffe0097fb75a0) >> at /usr/src/sys/amd64/amd64/trap.c:441 >> #7 0xffffffff80c40535 in calltrap () >> at /usr/src/sys/amd64/amd64/exception.S:232 >> #8 0xffffffff809bf22c in amrr_node_stats (ni=3D0xfffffe008cf83000, >> s=3D0xfffffe0097fb76f0) at /usr/src/sys/net80211/ieee80211_amrr.c:46= 4 >> #9 0xffffffff809ef9f4 in ieee80211_ratectl_sysctl_stats_node_iter ( >> arg=3D0xfffffe0097fb76f0, ni=3D0xfffffe008cf83000) at >> ieee80211_ratectl.h:170 >> #10 0xffffffff809e42b0 in ieee80211_iterate_nodes_vap ( >> nt=3D, vap=3D, >> f=3D0xffffffff809ef9b0 , >> arg=3D0xfffffe0097fb76f0) at /usr/src/sys/net80211/ieee80211_node.c:= 2558 >> #11 0xffffffff809ef941 in ieee80211_ratectl_sysctl_stats ( >> oidp=3D, arg1=3D, >> arg2=3D, req=3D) >> at /usr/src/sys/net80211/ieee80211_ratectl.c:99 >> #12 0xffffffff8087f8ab in sysctl_root_handler_locked >> (oid=3D0xfffff80016697d00, >> arg1=3D0xfffff80007bef000, arg2=3D0, req=3D0xfffffe0097fb7840, >> tracker=3D0xfffffe0097fb77b8) at /usr/src/sys/kern/kern_sysctl.c:166 >> #13 0xffffffff8087ef4f in sysctl_root (arg1=3D0xfffff80007bef000, arg2= =3D0, >> req=3D0xfffffe0097fb7840) at /usr/src/sys/kern/kern_sysctl.c:2080 >> #14 0xffffffff8087f5ca in userland_sysctl (td=3D0xfffff80007d96000, >> name=3D0xfffffe0097fb7900, namelen=3D4, old=3D, >> oldlenp=3D, inkernel=3D, >> new=3D0x0, >> newlen=3D0, retval=3D0xfffffe0097fb7968, flags=3D0) >> at /usr/src/sys/kern/kern_sysctl.c:2175 >> #15 0xffffffff8087f40f in sys___sysctl (td=3D0xfffff80007d96000, >> uap=3D0xfffff80007d963c0) at /usr/src/sys/kern/kern_sysctl.c:2110 >> #16 0xffffffff80c64742 in amd64_syscall (td=3D0xfffff80007d96000, traced= =3D0) >> at subr_syscall.c:135 >> #17 0xffffffff80c40e1d in fast_syscall_common () >> at /usr/src/sys/amd64/amd64/exception.S:504 >> >> What other data should I capture to assist in identifying and resolving >> this? >> >> imb >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g >> " >> > _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"