On Mon, Aug 03, 2015 at 05:28:58PM +0200, O. Hartmann wrote: > Am Sat, 1 Aug 2015 05:26:36 -0700 > David Wolfskill <david_at_catwhisker.org> schrieb: > > > On Thu, Jul 30, 2015 at 12:11:22PM -0700, Navdeep Parhar wrote: > > > A kernel built from head as of today panics with this on loading a module. > > > Does anyone else see this too? > > > .... > > > > Sorry for the delay -- but no; I have not seen it. > > > > Each of the builds listed in > > <http://www.catwhisker.org/~david/FreeBSD/history/laptop_uname_amd64.11.txt> > > also involves loading (at minimum) nvidia.ko and geom_eli.ko; usually, a > > few more -- successfully. > > > > Peace, > > david > > Including FreeBSD 11.0-CURRENT #28 r286232: Mon Aug 3 16:55:05 CEST 2015 amd64, I can > bring down any of my CURRENT boxes (>= IvyBridge) by the issue of > > sysctl -a|grep tempe > > for looking after the recent temperature (all kernel have the Intel specific driver for > the temperature senors compiled in, like > > [...] > coretemp0: <CPU On-Die Thermal Sensors> on cpu0 > est0: <Enhanced SpeedStep Frequency Control> on cpu0 > coretemp1: <CPU On-Die Thermal Sensors> on cpu1 > est1: <Enhanced SpeedStep Frequency Control> on cpu1 > coretemp2: <CPU On-Die Thermal Sensors> on cpu2 > est2: <Enhanced SpeedStep Frequency Control> on cpu2 > coretemp3: <CPU On-Die Thermal Sensors> on cpu3 > est3: <Enhanced SpeedStep Frequency Control> on cpu3 > > > I haven't tried issuing the crashing command with kernsl without this module compiled in. The grep in question has no relation to whatever panic you are seeing. What you can do is show your panic (at least the backtrace) and preferably narrow the problem down to the exact revision which introduced it. -- Mateusz Guzik <mjguzik gmail.com>Received on Mon Aug 03 2015 - 13:44:37 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:59 UTC