Adrian Chadd wrote:
> ok, can you post the full dmesg? I'd like to know which CPU this is.
>
Ok, here it is (Kostik already asked, so I have it right here;-):
Copyright (c) 1992-2015 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents
ok, can you post the full dmesg? I'd like to know which CPU this is.
Thanks,
-a
On 8 December 2015 at 13:19, Rick Macklem wrote:
> Adrian Chadd wrote:
>> Hi,
>>
>> Yea - try setting hw.acpi.cpu.cx_lowest=C1 and re-test.
>>
> Yep, with this setting, LAPIC seems to work fine.
>
> rick
>
>>
>> -a
Adrian Chadd wrote:
> Hi,
>
> Yea - try setting hw.acpi.cpu.cx_lowest=C1 and re-test.
>
Yep, with this setting, LAPIC seems to work fine.
rick
>
> -a
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebs
Hi,
Yea - try setting hw.acpi.cpu.cx_lowest=C1 and re-test.
-a
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
John Baldwin wrote:
> On Monday, December 07, 2015 06:01:08 PM Rick Macklem wrote:
> > Adrian Chadd wrote:
> > > Hi,
> > >
> > > ok. please file a bug for that. It may be something to do with the
> > > hardware and sleep states and skipping wakeups/interrupts or
> > > something.
> > >
> > > Pleas
John Baldwin wrote:
> On Monday, December 07, 2015 06:01:08 PM Rick Macklem wrote:
> > Adrian Chadd wrote:
> > > Hi,
> > >
> > > ok. please file a bug for that. It may be something to do with the
> > > hardware and sleep states and skipping wakeups/interrupts or
> > > something.
> > >
> > > Pleas
On Monday, December 07, 2015 06:01:08 PM Rick Macklem wrote:
> Adrian Chadd wrote:
> > Hi,
> >
> > ok. please file a bug for that. It may be something to do with the
> > hardware and sleep states and skipping wakeups/interrupts or
> > something.
> >
> > Please try using the default again (LAPIC?)
Adrian Chadd wrote:
> Hi,
>
> ok. please file a bug for that. It may be something to do with the
> hardware and sleep states and skipping wakeups/interrupts or
> something.
>
> Please try using the default again (LAPIC?) and set
> kern.eventtimer.periodic=1. See if that fixes it.
>
Actually made
Hi,
ok. please file a bug for that. It may be something to do with the
hardware and sleep states and skipping wakeups/interrupts or
something.
Please try using the default again (LAPIC?) and set
kern.eventtimer.periodic=1. See if that fixes it.
(i've had to debug this a few times before.)
-a
Alexander Kabaev wrote:
> On Mon, 7 Dec 2015 09:02:35 -0500 (EST)
> Rick Macklem wrote:
>
> > Hi,
> >
> > When running FreeBSD-current on an old i386 laptop, the console
> > screen is intermittently slow to display output. The hesitations
> > can be several seconds.
> > Sometimes it shows up whe
On Mon, 7 Dec 2015 09:02:35 -0500 (EST)
Rick Macklem wrote:
> Hi,
>
> When running FreeBSD-current on an old i386 laptop, the console
> screen is intermittently slow to display output. The hesitations
> can be several seconds.
> Sometimes it shows up when I'm typing such that it takes seconds
>
Hi,
When running FreeBSD-current on an old i386 laptop, the console
screen is intermittently slow to display output. The hesitations
can be several seconds.
Sometimes it shows up when I'm typing such that it takes seconds
for the characters to echo.
I think it is the display/output side, since I'v
12 matches
Mail list logo
