On 05/11/2011 04:33, Alexander Motin wrote:
On 11.05.2011 08:17, Doug Barton wrote:
I had an interesting result doing nothing but switching from HPET to
LAPIC ... no crash. Still on the same version of -current (r221566) the
only thing I've done is to add kern.eventtimer.timer=LAPIC to
On 05/11/2011 04:33, Alexander Motin wrote:
On 11.05.2011 08:17, Doug Barton wrote:
I had an interesting result doing nothing but switching from HPET to
LAPIC ... no crash. Still on the same version of -current (r221566) the
only thing I've done is to add kern.eventtimer.timer=LAPIC to
On 11.05.2011 08:17, Doug Barton wrote:
I had an interesting result doing nothing but switching from HPET to
LAPIC ... no crash. Still on the same version of -current (r221566) the
only thing I've done is to add kern.eventtimer.timer=LAPIC to
/boot/loader.conf, and so far I haven't been able to
Hi.
On 10.05.2011 05:05, Jason Hellenthal wrote:
On Tue, May 10, 2011 at 04:29:25AM +0300, Alexander Motin wrote:
On 10.05.2011 02:48, Doug Barton wrote:
Ok, so kern.eventtimer.timer=LAPIC in /boot/loader.conf should do
that, right?
Yes. You can do it in run-time also.
Not quite
on 10/05/2011 05:05 Jason Hellenthal said the following:
Alexander,
On Tue, May 10, 2011 at 04:29:25AM +0300, Alexander Motin wrote:
On 10.05.2011 02:48, Doug Barton wrote:
Ok, so kern.eventtimer.timer=LAPIC in /boot/loader.conf should do
that, right?
Yes. You can do it in run-time
Alexander,
On Tue, May 10, 2011 at 11:05:04AM +0300, Alexander Motin wrote:
Hi.
On 10.05.2011 05:05, Jason Hellenthal wrote:
On Tue, May 10, 2011 at 04:29:25AM +0300, Alexander Motin wrote:
On 10.05.2011 02:48, Doug Barton wrote:
Ok, so kern.eventtimer.timer=LAPIC in
I had an interesting result doing nothing but switching from HPET to
LAPIC ... no crash. Still on the same version of -current (r221566) the
only thing I've done is to add kern.eventtimer.timer=LAPIC to
/boot/loader.conf, and so far I haven't been able to get it to crash no
matter how much I
On 10.05.2011 02:48, Doug Barton wrote:
I would start from most obvious problems. I need to know more about
crashes. As usual: how to trigger, stack backtraces, etc.
Triggering is easy, I can start a buildworld with -j2, and a build of
ports/www/firefox with FORCE_MAKE_JOBS, and within 30
Alexander,
On Tue, May 10, 2011 at 04:29:25AM +0300, Alexander Motin wrote:
On 10.05.2011 02:48, Doug Barton wrote:
Ok, so kern.eventtimer.timer=LAPIC in /boot/loader.conf should do
that, right?
Yes. You can do it in run-time also.
Not quite absolutely sure here but IIRC the last time
New symptom, today (still running r221566) I compiled a small port, that
worked without any freezes or interactivity problems. Then I tried
compiling a larger port (java/openjdk6 if anyone cares) and still no
interactivity problems, but I got the system wedge requiring power
cycle problem I was
On 05/05/2011 13:55, Alexander Motin wrote:
Doug Barton wrote:
Alexander suggested some knobs to twist for the timers, and I'll be glad
to do that once he gets back to me with more concrete suggestions now
that he knows more about my specific problems.
OK, I am all here. While this post is
Doug Barton wrote:
On 05/05/2011 13:55, Alexander Motin wrote:
I see several possibly unrelated problems there:
- crashes are always crashes. They should be debugged.
- calcru going backwards could have the same roots as lost wall clock
time.
I think you're right about that. What
This is long, sorry. I wish I could condense things down to just the
answer, or even just the question, but here goes. I've used HEAD on my
main workstation(s) for many years. It's common for there to be ups and
downs, and that's fine. Lately however the problems have been debilitating.
First
Doug Barton wrote:
Alexander suggested some knobs to twist for the timers, and I'll be glad
to do that once he gets back to me with more concrete suggestions now
that he knows more about my specific problems.
OK, I am all here. While this post is indeed larger then previous, it is
not much
14 matches
Mail list logo
