Dear FreeBSD folks,
I am Qi Zhang from VMware Guest OS Validation team. And I am doing some
investigation about NVDIMM supporint in FreeBSD. I heard from George
Neville-Neil that NVDIMM support in FreeBSD has been moving along for a while.
But I couldn't find detail project description from free
On Tue, Dec 13, 2016 at 11:07:19AM -0500, Michael Butler wrote:
M> >> Any hints as to why all of my -current equipment is complaining like
below. Is
M> >> there a sysctl to moderate/turn this off?
M> >>
M> >> Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to
200
M> >> packe
On 12/13/16 12:07, Konstantin Belousov wrote:
On Tue, Dec 13, 2016 at 11:49:37AM -0500, Michael Butler wrote:
I've been bitten by this twice on a KDE desktop in the last 24 hours ..
same error on both occasions :-(
error: [drm:pid1197:i915_gem_object_pin] *ERROR* WARN ON: obj->pin_count
== DRM_
On 2016-12-13 10:24, Michael Butler wrote:
> Any hints as to why all of my -current equipment is complaining like
> below. Is there a sysctl to moderate/turn this off?
>
> Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to
> 200 packets/sec
> Dec 13 10:00:21 archive last mess
On Tue, Dec 13, 2016 at 07:25:29PM +0200, Konstantin Belousov wrote:
> This is not what I expected.
> Also, I realized that I mis-read the memory test code. It does not
> obliterate memory, old content is preserved.
>
> Please do exactly the same testing with another patch, at the end of the
> m
On Tue, Dec 13, 2016 at 06:28:38PM +0300, Slawa Olhovchenkov wrote:
> On Tue, Dec 13, 2016 at 05:01:39PM +0200, Konstantin Belousov wrote:
> KDB: debugger backends: ddb
> KDB: current backend: ddb
> SMAP type=01 base= len=00099c00
> SMAP type=02 base=00099c00 len=000
On Tue, Dec 13, 2016 at 11:19:18AM -0500, Michael Butler wrote:
> On 12/13/16 11:15, Gary Palmer wrote:
> > On Tue, Dec 13, 2016 at 10:43:27AM -0500, Michael Butler wrote:
> >> On 12/13/16 10:29, Dimitry Andric wrote:
> >>
> >>> Somebody is most likely port scanning your machines. I see this all t
On Tue, Dec 13, 2016 at 11:49:37AM -0500, Michael Butler wrote:
> I've been bitten by this twice on a KDE desktop in the last 24 hours ..
> same error on both occasions :-(
>
> error: [drm:pid1197:i915_gem_object_pin] *ERROR* WARN ON: obj->pin_count
> == DRM_I915_GEM_OBJECT_MAX_PIN_COUNT
> pid 1
I've been bitten by this twice on a KDE desktop in the last 24 hours ..
same error on both occasions :-(
error: [drm:pid1197:i915_gem_object_pin] *ERROR* WARN ON: obj->pin_count
== DRM_I915_GEM_OBJECT_MAX_PIN_COUNT
pid 1197 (Xorg), uid 0: exited on signal 6 (core dumped)
[ .. ]
error: [drm:
On Tue, Dec 13, 2016 at 11:07:19AM -0500, Michael Butler wrote:
M> On 12/13/16 10:48, Eric van Gyzen wrote:
M> > On 12/13/2016 09:24, Michael Butler wrote:
M> >> Any hints as to why all of my -current equipment is complaining like
below. Is
M> >> there a sysctl to moderate/turn this off?
M> >>
M>
On 12/13/16 11:15, Gary Palmer wrote:
On Tue, Dec 13, 2016 at 10:43:27AM -0500, Michael Butler wrote:
On 12/13/16 10:29, Dimitry Andric wrote:
Somebody is most likely port scanning your machines. I see this all the
time on boxes connected to the internet.
As are mine. I wouldn't mind so muc
On Tue, Dec 13, 2016 at 10:43:27AM -0500, Michael Butler wrote:
> On 12/13/16 10:29, Dimitry Andric wrote:
>
> > Somebody is most likely port scanning your machines. I see this all the
> > time on boxes connected to the internet.
>
> As are mine. I wouldn't mind so much if the message contained
On 12/13/16 10:48, Eric van Gyzen wrote:
On 12/13/2016 09:24, Michael Butler wrote:
Any hints as to why all of my -current equipment is complaining like below. Is
there a sysctl to moderate/turn this off?
Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to 200
packets/sec
D
On 2016/12/13 15:43, Michael Butler wrote:
> On 12/13/16 10:29, Dimitry Andric wrote:
>
>> Somebody is most likely port scanning your machines. I see this all the
>> time on boxes connected to the internet.
>
> As are mine. I wouldn't mind so much if the message contained sufficient
> useful inf
On 12/13/2016 09:24, Michael Butler wrote:
> Any hints as to why all of my -current equipment is complaining like below. Is
> there a sysctl to moderate/turn this off?
>
> Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to 200
> packets/sec
> Dec 13 10:00:21 archive last mess
On 12/13/16 10:29, Dimitry Andric wrote:
Somebody is most likely port scanning your machines. I see this all the
time on boxes connected to the internet.
As are mine. I wouldn't mind so much if the message contained sufficient
useful information that could be acted on, e.g. originating IP ad
On 13 Dec 2016, at 16:24, Michael Butler wrote:
>
> Any hints as to why all of my -current equipment is complaining like below.
Somebody is most likely port scanning your machines. I see this all the
time on boxes connected to the internet.
> Is there a sysctl to moderate/turn this off?
>
>
On Tue, Dec 13, 2016 at 05:01:39PM +0200, Konstantin Belousov wrote:
> > KDB: debugger backends: ddb
> > KDB: current backend: ddb
> > SMAP type=01 base= len=00099c00
> > SMAP type=02 base=00099c00 len=6400
> > SMAP type=02 base=000e len=
Any hints as to why all of my -current equipment is complaining like
below. Is there a sysctl to moderate/turn this off?
Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to
200 packets/sec
Dec 13 10:00:21 archive last message repeated 13 times
Dec 13 10:02:21 archive last
On Tue, Dec 13, 2016 at 05:34:01PM +0300, Slawa Olhovchenkov wrote:
> On Tue, Dec 13, 2016 at 05:11:14PM +0300, Slawa Olhovchenkov wrote:
>
> > On Tue, Dec 13, 2016 at 03:57:59PM +0200, Konstantin Belousov wrote:
> >
> > > On Tue, Dec 13, 2016 at 03:49:32PM +0300, Slawa Olhovchenkov wrote:
> > >
On Tue, Dec 13, 2016 at 05:11:14PM +0300, Slawa Olhovchenkov wrote:
> On Tue, Dec 13, 2016 at 03:57:59PM +0200, Konstantin Belousov wrote:
>
> > On Tue, Dec 13, 2016 at 03:49:32PM +0300, Slawa Olhovchenkov wrote:
> > > > Boot with NUMA enabled and interleave off.
> > >
> > > Already with patched
On Tue, Dec 13, 2016 at 03:57:59PM +0200, Konstantin Belousov wrote:
> On Tue, Dec 13, 2016 at 03:49:32PM +0300, Slawa Olhovchenkov wrote:
> > > Boot with NUMA enabled and interleave off.
> >
> > Already with patched kernel
> >
> > > Patch kernel with the 'if (1 || ...)' patch.
> > > Reboot, ent
On Tue, Dec 13, 2016 at 03:49:32PM +0300, Slawa Olhovchenkov wrote:
> > Boot with NUMA enabled and interleave off.
>
> Already with patched kernel
>
> > Patch kernel with the 'if (1 || ...)' patch.
> > Reboot, enter BIOS setup and enable interleave there.
> > Try to boot - does it boot ?
>
> No.
On Sun, Dec 11, 2016 at 12:07 AM, Andrey V. Elsukov wrote:
> Hi All,
>
> I am pleased to announce that projects/ipsec, that I started several
> months ago is ready for testing and review.
> The main goals were:
> * rework locking to make IPsec code more friendly for concurrent
> processing;
On Tue, Dec 13, 2016 at 01:23:40PM +0200, Konstantin Belousov wrote:
> On Tue, Dec 13, 2016 at 02:14:37PM +0300, Slawa Olhovchenkov wrote:
> > On Tue, Dec 13, 2016 at 01:05:35PM +0200, Konstantin Belousov wrote:
> >
> > > On Tue, Dec 13, 2016 at 02:37:14AM +0300, Slawa Olhovchenkov wrote:
> > > >
FreeBSD_HEAD_amd64_gcc - Build #1731 - Still Failing:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1731/
Full change log:
https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1731/changes
Full build log:
https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1731/c
Hi FreeBSD Current Team, I need help with a few things:
1. I tried getting help from all kinds of irc chats but still no dice.
2. I cannot get my soundcard to work on FreeBSD. It is the Soundblaster
Z(SB1500, SB1502) with the CA0132 codec.
3.Also i tried to get pipelight to work but doesnt work w
On Tue, Dec 13, 2016 at 02:14:37PM +0300, Slawa Olhovchenkov wrote:
> On Tue, Dec 13, 2016 at 01:05:35PM +0200, Konstantin Belousov wrote:
>
> > On Tue, Dec 13, 2016 at 02:37:14AM +0300, Slawa Olhovchenkov wrote:
> > > On Mon, Dec 12, 2016 at 04:20:33PM -0600, A. Wilcox wrote:
> > >
> > > >
On Tue, Dec 13, 2016 at 01:05:35PM +0200, Konstantin Belousov wrote:
> On Tue, Dec 13, 2016 at 02:37:14AM +0300, Slawa Olhovchenkov wrote:
> > On Mon, Dec 12, 2016 at 04:20:33PM -0600, A. Wilcox wrote:
> >
> > > Try the debugging patch below, which unconditionally disables import
> > >
On Tue, Dec 13, 2016 at 02:37:14AM +0300, Slawa Olhovchenkov wrote:
> On Mon, Dec 12, 2016 at 04:20:33PM -0600, A. Wilcox wrote:
>
> > Try the debugging patch below, which unconditionally disables import of
> > previous buffer. To test, you would need to boot, then frob options in
> > >
30 matches
Mail list logo
