ULE status, invalid load, buildkernel times.

Chris Dionissopoulos dionch at freemail.gr
Sun Jul 22 20:32:07 UTC 2007


Hello Thomas,

Sunday, July 22, 2007, 7:09:35 PM, you wrote:

> * Chris Dionissopoulos (dionch at freemail.gr) wrote:

>> But looking more carefully I found that I can reproduce PANIC anytime
>> using command:
>> 
>> mail# sysctl dev.cpu.0.freq=1596
>> 
>> -- where 1596 is valid Hz option as shown in:
>> dev.cpu.0.freq: 1862
>> dev.cpu.0.freq_levels: 1862/89000 1629/77875 1596/63546 1396/55602 1197/47659 997/39716 798/31773 598/23829 399/15886 199/7943

> It looks like you're running acpi_throttle, which I've seen cause
> problems before.  Try adding:

> hint.acpi_throttle.0.disabled="1"

> To /boot/device.hints so you're left with just the powernow frequencies
> (assuming this is an AMD64, going by the 89W max TDP).


Its an Intel c2d-6300 (see prev. messages) using cpufreq(4).
Everything works fine (for 6 months or more) with 4BSD or
ULE2/3(unpatched) scheduler.

AFAIK, the problem Jeff trying to resolve is why a ULE3(+last patch)
kernel, produces panics when a process touches cpufreq(4) context.

We are definitely talking about Jeff's ULE3 last patch right now and
not general. No other circumstance produce panic in my environment
(ULE-3 unpatched included).

-- 
Best regards,
 Chris                            mailto:dionch at freemail.gr



More information about the freebsd-current mailing list