Re: vio(4): fixup crash on up/down

2016-11-22 Thread sf
On Tue, 22 Nov 2016, Mike Belopuhov wrote: > vmd hackers and users seem to be able to trigger the assertion > below every time they do down and then up (with a dhclient for > instance): > > panic: kernel diagnostic assertion "m != NULL" failed: file > "/usr/src/sys/dev/pci/if_vio.c", line

Re: use x2apic if it is enabled by BIOS

2016-10-15 Thread sf
On Fri, 14 Oct 2016, Mike Larkin wrote: > On Fri, Oct 14, 2016 at 04:49:31PM +0900, YASUOKA Masahiko wrote: > > Hi, > > > > I'm working on NEC Express5800/R110h-1 (dmesg is attached). On this > > machine, our kernel panics with following message. > > > > cpu0 at mainbus0panic: cpu at apic

Re: use x2apic if it is enabled by BIOS

2016-10-14 Thread sf
On Fri, 14 Oct 2016, YASUOKA Masahiko wrote: > I'm working on NEC Express5800/R110h-1 (dmesg is attached). On this > machine, our kernel panics with following message. > > cpu0 at mainbus0panic: cpu at apic id 0 already attached? > > This seems to happen since x2APIC on the machine is enabled

Re: Possible bug in timecounter code

2012-09-02 Thread sf
On Sun, 2 Sep 2012, Mark Kettenis wrote: ntp_update_second() subtracts some amount of time from adjtimedelta and sets th-th_adjustment accordingly. However, if ntp_update_second is called more than once in a row, only the last value of th-th_adjustment is actually applied. Shouldn't the

Re: Possible bug in timecounter code

2012-09-02 Thread sf
On Sun, 2 Sep 2012, Mark Kettenis wrote: On Sun, 2 Sep 2012, Mark Kettenis wrote: ntp_update_second() subtracts some amount of time from adjtimedelta and sets th-th_adjustment accordingly. However, if ntp_update_second is called more than once in a row, only the last value of th-th_adjustment