Adrian Chadd writes:
> Dag-Erling Smørgrav writes:
> > Could you check if network activity (e.g. downloading an ISO) triggers
> > it, and if so, if it goes away when you set the kern.eventtimer.idletick
> > sysctl to 0?
> Don't you mean 'set it to 1' ?
Uh, yes :)
DES
--
Dag-Erling Smørgrav - d
In message <86lisp9dzn@ds4.des.no>, =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= wr
ites:
>"Poul-Henning Kamp" writes:
>> For what it's worth, I regularly (=3Devery 10-12 days or so) see all
>> timer activity in the system die and have to use the 4-sec
>> power-switch to get the system down.
>
>Could
2011/10/13 Dag-Erling Smørgrav :
> "Poul-Henning Kamp" writes:
>> For what it's worth, I regularly (=every 10-12 days or so) see all
>> timer activity in the system die and have to use the 4-sec
>> power-switch to get the system down.
>
> Could you check if network activity (e.g. downloading an IS
"Poul-Henning Kamp" writes:
> For what it's worth, I regularly (=every 10-12 days or so) see all
> timer activity in the system die and have to use the 4-sec
> power-switch to get the system down.
Could you check if network activity (e.g. downloading an ISO) triggers
it, and if so, if it goes awa
In message <86lispaztm@ds4.des.no>, =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= wr
ites:
>Dag-Erling Sm=C3=B8rgrav writes:
>> I've just built a kernel with KTR support, and with KTR_SPARE2, KTR_INTR
>> and KTR_SCHED enabled by default. I'll see what turns up. I'm also
>> going to try machdep.idle=3
Dag-Erling Smørgrav writes:
> I've just built a kernel with KTR support, and with KTR_SPARE2, KTR_INTR
> and KTR_SCHED enabled by default. I'll see what turns up. I'm also
> going to try machdep.idle=hlt with kern.eventtimer.idletick=0, and using
> a PCI re(4) instead of the on-board msk(4) whil
2011/10/12 Dag-Erling Smørgrav :
> BTW, can I suggest appropriating one of KTR_SPARE[234] and renaming it
> to KTR_CLOCK? I don't see why cxgb should use them, let alone all
> three; it should use KTR_DEV or KTR_NET instead.
KTR_MALLOC has been completely unused in the tree since at least
FreeBSD
Alexander Motin writes:
> If short freezes you've descrived happens often enough, you may try to
> log them down with enabling KTR_SPARE2 ktr event type and disabling
> logging within few seconds after such freeze happened.
I've been working with adri to try to isolate it. We've eliminated nfs
a
Dag-Erling Smørgrav wrote:
> I have a box running a GENERIC kernel from September 25th that freezes
> completely for a few seconds, up to a minute or so, at random intervals.
> Sooner or later it freezes permanently (or at least longer than I am
> willing to wait for it to unfreeze) and must be pow
