Re: kernel panic in wireless-related sysctl walk
On 1/12/19 5:12 AM, O. Hartmann wrote: > Am Thu, 10 Jan 2019 22:22:05 +0100 > "O. Hartmann" schrieb: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 > >> Am Thu, 10 Jan 2019 12:02:15 -0800 >> Cy Schubert schrieb: > >>> I'm not able to reproduce this at the moment. I can confirm that SVN r342966 fixes it for me - thanks! imb ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kernel panic in wireless-related sysctl walk
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Thu, 10 Jan 2019 22:22:05 +0100 "O. Hartmann" schrieb: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Am Thu, 10 Jan 2019 12:02:15 -0800 > Cy Schubert schrieb: > > > I'm not able to reproduce this at the moment. > > > > > > I have a oldish Lenovo R500 Notebook running FreeBSD-12 STABLE. I'm not sure > what WiFi > Interface driver the system is using right now; the WiFi is combined with the > NIC to > form a lagg-interface. I can 100% reproduce the crash described above via > "sysctl -a". > Just in case the phenomenon I discovered shortly after Christmas is of the > same source > as the initial poster has reported, how can I be of help? The system is a > "pkg system" > completely, so I have to switch on debugging without kernel rebuilds. Any > advice? > > Kind regards, > > O. Hartmann > > - -- > O. Hartmann > > Ich widerspreche der Nutzung oder Übermittlung meiner Daten für > Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). > -BEGIN PGP SIGNATURE- > > iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXDe3mAAKCRA4N1ZZPba5 > R27kAQD7rB6h7Y21ycCWxAjYDb98x2k+y/uWsoBCXBfRAvpYswEA7yO9cj7wno8L > 05KxBEbLbrUjn8cLhowYwe0d14EMeAE= > =5VUr > -END PGP SIGNATURE- > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" I checked for the problem on last Friday after rebuilding pkgBase with 12-STABLE - sorry having not the revision number at hand, it is at work - but after a recent update und trying to bring down the notebook via "sysctl -a" as described didn't work anymore. The driver for an oldish Intel wireless adapter (I can't remember the exact spec, its 4500 or 5000 or similar) is iwn. oh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXDm9tQAKCRA4N1ZZPba5 R+4BAQDZ7Z9FrDSQ13ncksBphGPrcT/7pdaaLkXSLntwijUXBwD+LXv0LNOJqIM6 8V6OjgqrH7f5y4BnQK7bnkDE6cegdA8= =XNpM -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
RE: kernel panic in wireless-related sysctl walk
Hi I have a Lenovo T510 running FreeBSD-12 STABLE. After configuring for lagg interface (combined from em - Intel gigabit ethernet adapter and iwn - intel wireless adapter) I can cause the system to panic with sysctl -a. Using either the em interface or the wireless I can safely use sysctl -a, the system does not panic. best regards András Krasznai -Original Message- From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of O. Hartmann Sent: Thursday, January 10, 2019 10:22 PM To: Cy Schubert Cc: Michael Zhilin; Michael Butler; freebsd-current Subject: Re: kernel panic in wireless-related sysctl walk -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Thu, 10 Jan 2019 12:02:15 -0800 Cy Schubert schrieb: > I'm not able to reproduce this at the moment. > > I have a oldish Lenovo R500 Notebook running FreeBSD-12 STABLE. I'm not sure what WiFi Interface driver the system is using right now; the WiFi is combined with the NIC to form a lagg-interface. I can 100% reproduce the crash described above via "sysctl -a". Just in case the phenomenon I discovered shortly after Christmas is of the same source as the initial poster has reported, how can I be of help? The system is a "pkg system" completely, so I have to switch on debugging without kernel rebuilds. Any advice? Kind regards, O. Hartmann - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXDe3mAAKCRA4N1ZZPba5 R27kAQD7rB6h7Y21ycCWxAjYDb98x2k+y/uWsoBCXBfRAvpYswEA7yO9cj7wno8L 05KxBEbLbrUjn8cLhowYwe0d14EMeAE= =5VUr -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kernel panic in wireless-related sysctl walk
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Thu, 10 Jan 2019 12:02:15 -0800 Cy Schubert schrieb: > I'm not able to reproduce this at the moment. > > I have a oldish Lenovo R500 Notebook running FreeBSD-12 STABLE. I'm not sure what WiFi Interface driver the system is using right now; the WiFi is combined with the NIC to form a lagg-interface. I can 100% reproduce the crash described above via "sysctl -a". Just in case the phenomenon I discovered shortly after Christmas is of the same source as the initial poster has reported, how can I be of help? The system is a "pkg system" completely, so I have to switch on debugging without kernel rebuilds. Any advice? Kind regards, O. Hartmann - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXDe3mAAKCRA4N1ZZPba5 R27kAQD7rB6h7Y21ycCWxAjYDb98x2k+y/uWsoBCXBfRAvpYswEA7yO9cj7wno8L 05KxBEbLbrUjn8cLhowYwe0d14EMeAE= =5VUr -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kernel panic in wireless-related sysctl walk
I'm not able to reproduce this at the moment. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. In message <20190110164201.dfd951...@spqr.komquats.com>, Cy Schubert writes: > --_E525281E-4037-9802-70D9-783B79B148EC_ > Content-Transfer-Encoding: quoted-printable > Content-Type: text/plain; charset="us-ascii" > > 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 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:0x809bf22c > >> stack pointer =3D 0x28:0xfe0097fb7660 > >> frame pointer =3D 0x28:0xfe0097fb7670 > >> code segment=3D base 0x0, limit 0xf, 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 0x808704eb in kern_reboot (howto=3D260) > >> at /usr/src/sys/kern/kern_shutdown.c:451 > >> #2 0x80870920 in vpanic (fmt=3D, > >> ap=3D) at /usr/src/sys/kern/kern_shutdown.c:877 > >> #3 0x80870753 in panic (fmt=3D) > >> at /usr/src/sys/kern/kern_shutdown.c:804 > >> #4 0x80c63b5b in trap_fatal (frame=3D0xfe0097fb75a0, eva=3D= > 8) > >> at /usr/src/sys/amd64/amd64/trap.c:929 > >> #5 0x80c63f10 in trap_pfault (frame=3D0xfe0097fb75a0, > >> usermode=3D0) > >> at /usr/src/sys/amd64/amd64/trap.c:839 > >> #6 0x80c632be in trap (frame=3D0xfe0097fb75a0) > >> at /usr/src/sys/amd64/amd64/trap.c:441 > >> #7 0x80c40535 in calltrap () > >> at /usr/src/sys/amd64/amd64/exception.S:232 > >> #8 0x809bf22c in amrr_node_stats (ni=3D0xfe008cf83000, > >> s=3D0xfe0097fb76f0) at /usr/src/sys/net80211/ieee80211_amrr.c:46= > 4 > >> #9 0x809ef9f4 in ieee80211_ratectl_sysctl_stats_node_iter ( > >> arg=3D0xfe0097fb76f0, ni=3D0xfe008cf83000) at > >> ieee80211_ratectl.h:170 > >> #10 0x809e42b0 in ieee80211_iterate_nodes_vap ( > >> nt=3D, vap=3D, > >> f=3D0x809ef9b0 , > >> arg=3D0xfe0097fb76f0) at /usr/src/sys/net80211/ieee80211_node.c:= > 2558 > >> #11 0x809ef941 in ieee80211_ratectl_sysctl_stats ( > >> oidp=3D, arg1=3D, > >> arg2=3D, req=3D) > >> at /usr/src/sys/net80211/ieee80211_ratectl.c:99 > >> #12 0x8087f8ab in sysctl_root_handler_locked > >> (oid=3D0xf80016697d00, > >> arg1=3D0xf80007bef000, arg2=3D0, req=3D0xfe0097fb7840, > >> tracker=3D0xfe0097fb77b8) at /usr/src/sys/kern/kern_sysctl.c:166 > >> #13 0x8087ef4f in sysctl_root (arg1=3D0xf80007bef000, arg2= &
RE: kernel panic in wireless-related sysctl walk
I'll add a me too, though I haven't found the time to dig further, as no dump 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 = 1; apic id = 01 >> fault virtual address = 0x8 >> fault code = supervisor read data, page not present >> instruction pointer = 0x20:0x809bf22c >> stack pointer = 0x28:0xfe0097fb7660 >> frame pointer = 0x28:0xfe0097fb7670 >> code segment= base 0x0, limit 0xf, type 0x1b >> = DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags= interrupt enabled, resume, IOPL = 0 >> current process = 11053 (sysctl) >> trap number = 12 >> panic: page fault >> cpuid = 1 >> time = 1547129798 >> Uptime: 3d10h27m14s >> Dumping 3840 out of 16258 >> MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% >> >> [ .. ] >> >> (kgdb) #0 doadump (textdump=) at pcpu.h:230 >> #1 0x808704eb in kern_reboot (howto=260) >> at /usr/src/sys/kern/kern_shutdown.c:451 >> #2 0x80870920 in vpanic (fmt=, >> ap=) at /usr/src/sys/kern/kern_shutdown.c:877 >> #3 0x80870753 in panic (fmt=) >> at /usr/src/sys/kern/kern_shutdown.c:804 >> #4 0x80c63b5b in trap_fatal (frame=0xfe0097fb75a0, eva=8) >> at /usr/src/sys/amd64/amd64/trap.c:929 >> #5 0x80c63f10 in trap_pfault (frame=0xfe0097fb75a0, >> usermode=0) >> at /usr/src/sys/amd64/amd64/trap.c:839 >> #6 0x80c632be in trap (frame=0xfe0097fb75a0) >> at /usr/src/sys/amd64/amd64/trap.c:441 >> #7 0x80c40535 in calltrap () >> at /usr/src/sys/amd64/amd64/exception.S:232 >> #8 0x809bf22c in amrr_node_stats (ni=0xfe008cf83000, >> s=0xfe0097fb76f0) at /usr/src/sys/net80211/ieee80211_amrr.c:464 >> #9 0x809ef9f4 in ieee80211_ratectl_sysctl_stats_node_iter ( >> arg=0xfe0097fb76f0, ni=0xfe008cf83000) at >> ieee80211_ratectl.h:170 >> #10 0x809e42b0 in ieee80211_iterate_nodes_vap ( >> nt=, vap=, >> f=0x809ef9b0 , >> arg=0xfe0097fb76f0) at /usr/src/sys/net80211/ieee80211_node.c:2558 >> #11 0x809ef941 in ieee80211_ratectl_sysctl_stats ( >> oidp=, arg1=, >> arg2=, req=) >> at /usr/src/sys/net80211/ieee80211_ratectl.c:99 >> #12 0x8087f8ab in sysctl_root_handler_locked >> (oid=0xf80016697d00, >> arg1=0xf80007bef000, arg2=0, req=0xfe0097fb7840, >> tracker=0xfe0097fb77b8) at /usr/src/sys/kern/kern_sysctl.c:166 >> #13 0x8087ef4f in sysctl_root (arg1=0xf80007bef000, arg2=0, >> req=0xfe0097fb7840) at /usr/src/sys/kern/kern_sysctl.c:2080 >> #14 0x8087f5ca in userland_sysctl (td=0xf80007d96000, >> name=0xfe0097fb7900, namelen=4, old=, >> oldlenp=, inkernel=, >> new=0x0, >> newlen=0, retval=0xfe0097fb7968, flags=0) >> at /usr/src/sys/kern/kern_sysctl.c:2175 >> #15 0x8087f40f in sys___sysctl (td=0xf80007d96000, >> uap=0xf80007d963c0) at /usr/src/sys/kern/kern_sysctl.c:2110 >> #16 0x80c64742 in amd64_syscall (td=0xf80007d96000, traced=0) >> at subr_syscall.c:135 >> #17 0x80c40e1d 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.f
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 = 1; apic id = 01 >> fault virtual address = 0x8 >> fault code = supervisor read data, page not present >> instruction pointer = 0x20:0x809bf22c >> stack pointer = 0x28:0xfe0097fb7660 >> frame pointer = 0x28:0xfe0097fb7670 >> code segment= base 0x0, limit 0xf, type 0x1b >> = DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags= interrupt enabled, resume, IOPL = 0 >> current process = 11053 (sysctl) >> trap number = 12 >> panic: page fault >> cpuid = 1 >> time = 1547129798 >> Uptime: 3d10h27m14s >> Dumping 3840 out of 16258 >> MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% >> >> [ .. ] >> >> (kgdb) #0 doadump (textdump=) at pcpu.h:230 >> #1 0x808704eb in kern_reboot (howto=260) >> at /usr/src/sys/kern/kern_shutdown.c:451 >> #2 0x80870920 in vpanic (fmt=, >> ap=) at /usr/src/sys/kern/kern_shutdown.c:877 >> #3 0x80870753 in panic (fmt=) >> at /usr/src/sys/kern/kern_shutdown.c:804 >> #4 0x80c63b5b in trap_fatal (frame=0xfe0097fb75a0, eva=8) >> at /usr/src/sys/amd64/amd64/trap.c:929 >> #5 0x80c63f10 in trap_pfault (frame=0xfe0097fb75a0, >> usermode=0) >> at /usr/src/sys/amd64/amd64/trap.c:839 >> #6 0x80c632be in trap (frame=0xfe0097fb75a0) >> at /usr/src/sys/amd64/amd64/trap.c:441 >> #7 0x80c40535 in calltrap () >> at /usr/src/sys/amd64/amd64/exception.S:232 >> #8 0x809bf22c in amrr_node_stats (ni=0xfe008cf83000, >> s=0xfe0097fb76f0) at /usr/src/sys/net80211/ieee80211_amrr.c:464 >> #9 0x809ef9f4 in ieee80211_ratectl_sysctl_stats_node_iter ( >> arg=0xfe0097fb76f0, ni=0xfe008cf83000) at >> ieee80211_ratectl.h:170 >> #10 0x809e42b0 in ieee80211_iterate_nodes_vap ( >> nt=, vap=, >> f=0x809ef9b0 , >> arg=0xfe0097fb76f0) at /usr/src/sys/net80211/ieee80211_node.c:2558 >> #11 0x809ef941 in ieee80211_ratectl_sysctl_stats ( >> oidp=, arg1=, >> arg2=, req=) >> at /usr/src/sys/net80211/ieee80211_ratectl.c:99 >> #12 0x8087f8ab in sysctl_root_handler_locked >> (oid=0xf80016697d00, >> arg1=0xf80007bef000, arg2=0, req=0xfe0097fb7840, >> tracker=0xfe0097fb77b8) at /usr/src/sys/kern/kern_sysctl.c:166 >> #13 0x8087ef4f in sysctl_root (arg1=0xf80007bef000, arg2=0, >> req=0xfe0097fb7840) at /usr/src/sys/kern/kern_sysctl.c:2080 >> #14 0x8087f5ca in userland_sysctl (td=0xf80007d96000, >> name=0xfe0097fb7900, namelen=4, old=, >> oldlenp=, inkernel=, >> new=0x0, >> newlen=0, retval=0xfe0097fb7968, flags=0) >> at /usr/src/sys/kern/kern_sysctl.c:2175 >> #15 0x8087f40f in sys___sysctl (td=0xf80007d96000, >> uap=0xf80007d963c0) at /usr/src/sys/kern/kern_sysctl.c:2110 >> #16 0x80c64742 in amd64_syscall (td=0xf80007d96000, traced=0) >> at subr_syscall.c:135 >> #17 0x80c40e1d 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-unsubscr...@freebsd.org >> " >> > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kernel panic in wireless-related sysctl walk
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 = 1; apic id = 01 > fault virtual address = 0x8 > fault code = supervisor read data, page not present > instruction pointer = 0x20:0x809bf22c > stack pointer = 0x28:0xfe0097fb7660 > frame pointer = 0x28:0xfe0097fb7670 > code segment= base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags= interrupt enabled, resume, IOPL = 0 > current process = 11053 (sysctl) > trap number = 12 > panic: page fault > cpuid = 1 > time = 1547129798 > Uptime: 3d10h27m14s > Dumping 3840 out of 16258 > MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% > > [ .. ] > > (kgdb) #0 doadump (textdump=) at pcpu.h:230 > #1 0x808704eb in kern_reboot (howto=260) > at /usr/src/sys/kern/kern_shutdown.c:451 > #2 0x80870920 in vpanic (fmt=, > ap=) at /usr/src/sys/kern/kern_shutdown.c:877 > #3 0x80870753 in panic (fmt=) > at /usr/src/sys/kern/kern_shutdown.c:804 > #4 0x80c63b5b in trap_fatal (frame=0xfe0097fb75a0, eva=8) > at /usr/src/sys/amd64/amd64/trap.c:929 > #5 0x80c63f10 in trap_pfault (frame=0xfe0097fb75a0, > usermode=0) > at /usr/src/sys/amd64/amd64/trap.c:839 > #6 0x80c632be in trap (frame=0xfe0097fb75a0) > at /usr/src/sys/amd64/amd64/trap.c:441 > #7 0x80c40535 in calltrap () > at /usr/src/sys/amd64/amd64/exception.S:232 > #8 0x809bf22c in amrr_node_stats (ni=0xfe008cf83000, > s=0xfe0097fb76f0) at /usr/src/sys/net80211/ieee80211_amrr.c:464 > #9 0x809ef9f4 in ieee80211_ratectl_sysctl_stats_node_iter ( > arg=0xfe0097fb76f0, ni=0xfe008cf83000) at > ieee80211_ratectl.h:170 > #10 0x809e42b0 in ieee80211_iterate_nodes_vap ( > nt=, vap=, > f=0x809ef9b0 , > arg=0xfe0097fb76f0) at /usr/src/sys/net80211/ieee80211_node.c:2558 > #11 0x809ef941 in ieee80211_ratectl_sysctl_stats ( > oidp=, arg1=, > arg2=, req=) > at /usr/src/sys/net80211/ieee80211_ratectl.c:99 > #12 0x8087f8ab in sysctl_root_handler_locked > (oid=0xf80016697d00, > arg1=0xf80007bef000, arg2=0, req=0xfe0097fb7840, > tracker=0xfe0097fb77b8) at /usr/src/sys/kern/kern_sysctl.c:166 > #13 0x8087ef4f in sysctl_root (arg1=0xf80007bef000, arg2=0, > req=0xfe0097fb7840) at /usr/src/sys/kern/kern_sysctl.c:2080 > #14 0x8087f5ca in userland_sysctl (td=0xf80007d96000, > name=0xfe0097fb7900, namelen=4, old=, > oldlenp=, inkernel=, new=0x0, > newlen=0, retval=0xfe0097fb7968, flags=0) > at /usr/src/sys/kern/kern_sysctl.c:2175 > #15 0x8087f40f in sys___sysctl (td=0xf80007d96000, > uap=0xf80007d963c0) at /usr/src/sys/kern/kern_sysctl.c:2110 > #16 0x80c64742 in amd64_syscall (td=0xf80007d96000, traced=0) > at subr_syscall.c:135 > #17 0x80c40e1d 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-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
