Jeff Roberson wrote:
quoted text
>=20
> On Tue, 18 Mar 2008, Ivan Voras wrote:
>=20
>> Ivan Voras wrote:
>>> Hi,
>>> I cannot boot a very recent build (minutes ago) of 8-CURRENT on=20
>>> VMWare Server. Panic ("integer divide fault" - is this division by=20
>>> zero?) is in sched_rr_interval().
>>>
>>> More info here:
>>> http://ivoras.sharanet.org/stuff/panic/
>>>
>>> It might be because I'm trying to run without WITNESS+INVARIANTS.
>>
>> No, building a GENERIC kernel doesn't change anything. It's also not a=
=20
quoted text
>> cvsup glitch - todays sources panic in exactly the same way.
>>
>>
> Can you tell me what the values of:
>=20
> sysctl kern.sched.slice
>=20
> and
>=20
> sysctl kern.clockrate
>=20
> are?

The machine doesn't finish booting the kernel (i.e. init isn't executed) =

and fetching sysctls apparently isn't supported by the kernel debugger=20
(though it would be nice if it did work, at least for simple variables).

The only old kernel I have is 7.0RC1, and in it I can only access=20
kern.clockrate, which is { hz=3D50, tick=3D20000, profhz=3D33, stathz=3D6=
 }.

Since you brought up the issue of clocks, I removed the tuning of=20
kern.hz (it was present there practically forever) and the panic's gone. =

I use low values for kern.hz in VMWare to (noticably) reduce problems=20
with clock drift and context switches, so it would be nice to not have=20
the kernel panic with it :)

Apparently lowering kern.hz works upto about 75 - anything lower=20
triggers the integer divide fault.