Date: Thu, 10 Jan 2019 22:22:05 +0100 From: "O. Hartmann" <ohartmann@walstatt.org> To: Cy Schubert <Cy.Schubert@cschubert.com> Cc: Michael Zhilin <mizhka@gmail.com>, Michael Butler <imb@protected-networks.net>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: kernel panic in wireless-related sysctl walk Message-ID: <20190110222232.47fab190@thor.intern.walstatt.dynvpn.de> In-Reply-To: <201901102002.x0AK2FVN007747@slippy.cwsent.com> References: <20190110164201.DFD951E1F@spqr.komquats.com> <201901102002.x0AK2FVN007747@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Am Thu, 10 Jan 2019 12:02:15 -0800 Cy Schubert <Cy.Schubert@cschubert.com> 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-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190110222232.47fab190>