Date: Thu, 10 Jan 2019 08:42:10 -0800 From: Cy Schubert <Cy.Schubert@cschubert.com> To: Michael Zhilin <mizhka@gmail.com>, Michael Butler <imb@protected-networks.net> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: RE: kernel panic in wireless-related sysctl walk Message-ID: <20190110164201.DFD951E1F@spqr.komquats.com>
next in thread | raw e-mail | index | archive | help
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 <Cy.Schubert@cschubert.com> or <cy@freebsd.org> 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 <mizhka@gmail.com> 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 <imb@protected-networks.ne= t> > 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<value optimized out>) 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<value optimized out>, >> ap=3D<value optimized out>) at /usr/src/sys/kern/kern_shutdown.c:877 >> #3 0xffffffff80870753 in panic (fmt=3D<value optimized out>) >> 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<value optimized out>, vap=3D<value optimized out>, >> f=3D0xffffffff809ef9b0 <ieee80211_ratectl_sysctl_stats_node_iter>, >> arg=3D0xfffffe0097fb76f0) at /usr/src/sys/net80211/ieee80211_node.c:= 2558 >> #11 0xffffffff809ef941 in ieee80211_ratectl_sysctl_stats ( >> oidp=3D<value optimized out>, arg1=3D<value optimized out>, >> arg2=3D<value optimized out>, req=3D<value optimized out>) >> 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<value optimized out>, >> oldlenp=3D<value optimized out>, inkernel=3D<value optimized out>, >> 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190110164201.DFD951E1F>