Date: Sun, 22 Jul 2007 23:29:25 +0300 From: Chris Dionissopoulos <dionch@freemail.gr> To: Thomas Hurst <tom.hurst@clara.net> Cc: Jeff Roberson <jroberson@chesapeake.net>, current@freebsd.org Subject: Re[2]: ULE status, invalid load, buildkernel times. Message-ID: <751338143.20070722232925@freemail.gr> In-Reply-To: <20070722160935.GA18069@voi.aagh.net> References: <20070721174631.S561@10.0.0.1> <1807103749.20070722111025@freemail.gr> <20070722014208.G561@10.0.0.1> <684796249.20070722134105@freemail.gr> <20070722160935.GA18069@voi.aagh.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Thomas, Sunday, July 22, 2007, 7:09:35 PM, you wrote: > * Chris Dionissopoulos (dionch@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@freemail.gr
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?751338143.20070722232925>