On Mon, Oct 25, 2021 at 09:47:18AM -0700, Maxim Sobolev wrote:
> Just in case someone thinks this is something useful, I've got a PR filed
> against git to implement custom $Id$. There are no technical issues with
> the change but Git developers are not very keen on merging it in, since
> they see
On Wed, Apr 07, 2021 at 02:33:57PM +, Poul-Henning Kamp wrote:
> > T.e. if all system eat 985 ticks of CPU each second and getty eat 15
> > ticks of CPU each second -- top show 1.5% for getty.
>
> That may be, but getty should not wake up at all in this situation,
> it should be sleeping, wai
On Wed, Apr 07, 2021 at 05:22:40AM +, Poul-Henning Kamp wrote:
> I have two 12.2-R systems where the serial console is attached to a terminal
> server.
>
> When there are no TCP connections to the terminal server, getty soaks up 1.5%
> of the
> CPU in the kernel (sleeping in "ttyin"), ktrac
On Fri, Oct 30, 2020 at 04:00:55PM -0700, Cy Schubert wrote:
> > > > More stresses memory usually refers to performance penalty.
> > > > Usually way for better performance is reduce memory access.
> > >
> > > The reason filesystems (UFS, ZFS, EXT4, etc.) cache is to avoid disk
> > > accesses. Na
On Fri, Oct 30, 2020 at 03:34:10PM -0700, Cy Schubert wrote:
> In message <20201030220809.gg2...@zxy.spb.ru>, Slawa Olhovchenkov writes:
> > On Fri, Oct 30, 2020 at 01:53:10PM -0700, Cy Schubert wrote:
> >
> > > In message <20201030204622.gf2...@zxy.spb.ru>, S
On Fri, Oct 30, 2020 at 01:53:10PM -0700, Cy Schubert wrote:
> In message <20201030204622.gf2...@zxy.spb.ru>, Slawa Olhovchenkov writes:
> > On Thu, Oct 29, 2020 at 08:13:00PM -0700, Cy Schubert wrote:
> >
> > > In message , qroxana
> > > writes
> &g
On Thu, Oct 29, 2020 at 08:13:00PM -0700, Cy Schubert wrote:
> In message , qroxana
> writes
> :
> >
> > Hi,
> >
> > I have an old i386 machine running r364479. After upgrading to
> > r367045, running kldload zfs.ko freezes the whole system.
> >
> > I also tried to replace the 4GB memory with an
On Thu, Sep 17, 2020 at 08:55:26AM -0700, Cy Schubert wrote:
> In message <451538de-9427-4584-987b-8e4aa26c2...@freebsd.org>, Daniel
> Eischen w
> rites:
> >
> >
> > > On Sep 17, 2020, at 11:20 AM, Maxim Sobolev wrote:
> > >
> > > Re: removing HTTP client please no!!! The current drive to "
On Wed, Sep 09, 2020 at 11:55:14AM -0400, Ryan Moeller wrote:
>
> On 9/8/20 4:31 PM, Niclas Zeising wrote:
> > On 2020-05-02 02:20, Matthew Macy wrote:
> >> OpenZFS doesn't have the same ashift optimization logic that FreeBSD
> >> has. It's something that needs to be resolved before the code can
On Tue, May 05, 2020 at 02:29:00PM +0200, Baptiste Daroussin wrote:
> On Tue, May 05, 2020 at 03:24:15PM +0300, Slawa Olhovchenkov wrote:
> > On Thu, Apr 30, 2020 at 03:04:49PM +0200, Baptiste Daroussin wrote:
> >
> > > > > This way ports with random termcap info
On Thu, Apr 30, 2020 at 03:04:49PM +0200, Baptiste Daroussin wrote:
> > > This way ports with random termcap info to add would be able to do it
> > > witho=
> > > ut
> > > the requirement to wait for a commit in base and a MFC.
> >
> > This is probably outside of my scope at the moment but, yes,
I am looked to code control kernel free memory /p ressure and see some
strange points:
- vm.v_free_target is RW but do nothing. You can set it to any value
and this is don't have any effect.
- vmd_free_target (as vm.domain.N.stats.free_target) is RD and don't
have any sysctl to tune
Same for
On Fri, Sep 20, 2019 at 01:06:29PM -0400, Garrett Wollman wrote:
> In article <20190920155304.gn3...@zxy.spb.ru>, s...@zxy.spb.ru writes:
>
> >Location of device in multi-chassis storage system is different story.
> >I am don't know how to field engineer insert disks in chassis.
> >For me simple
On Fri, Sep 20, 2019 at 08:29:08AM -0700, Freddie Cash wrote:
> On Fri, Sep 20, 2019 at 7:35 AM Slawa Olhovchenkov wrote:
>
> > On Thu, Sep 19, 2019 at 06:04:54PM +0200, Michael Gmelin wrote:
> > > What about gpart output of the pool drives?
> > >
> > > I
On Thu, Sep 19, 2019 at 06:04:54PM +0200, Michael Gmelin wrote:
>
>
> > On 19. Sep 2019, at 17:57, Kurt Jaeger wrote:
> >
> > Hi!
> >
> >>> We have a system with 10 SATA disks. 2 disks are for the system,
> >>> 8 disks drive a data pool 'bck', configured as raidz2, for backup
> >>> purposes:
On Tue, Mar 19, 2019 at 04:07:45PM +0200, Andriy Gapon wrote:
> On 19/03/2019 15:02, Slawa Olhovchenkov wrote:
> > On Mon, Mar 18, 2019 at 11:00:10PM +0200, Andriy Gapon wrote:
> >
> >> On 18/03/2019 20:01, Andrey Fesenko wrote:
> >>> Not this? ZFS
On Mon, Mar 18, 2019 at 11:00:10PM +0200, Andriy Gapon wrote:
> On 18/03/2019 20:01, Andrey Fesenko wrote:
> > Not this? ZFS use wired and not clean only reboot?
> > https://reviews.freebsd.org/D7538?id=25108
>
> Wired memory surely has nothing to do with swap.
Wired memory can pressure to swapa
On Wed, Oct 10, 2018 at 02:57:39PM +0100, tech-lists wrote:
> On 10/10/2018 13:45, Slawa Olhovchenkov wrote:
> > for 4K@60FPS you need DP connection.
>
> problem is monitor only has HDMI. I'm not sure it'll 4k@30fps is an
> acceptable mode for it; need to ch
On Wed, Oct 10, 2018 at 11:17:03AM +0100, tech-lists wrote:
>
> so would this indicate the card is 4k capable but the HDMI port on the
> card is not? Or the port on the monitor? Or something else?
for 4K@60FPS you need DP connection.
___
freebsd-curre
On Thu, Jul 12, 2018 at 02:42:29PM +0200, Alexander Leidinger wrote:
> __curthread () at ./machine/pcpu.h:230
> 230 __asm("movq %%gs:%1,%0" : "=r" (td)
> (kgdb) bt
> #0 __curthread () at ./machine/pcpu.h:230
> #1 doadump (textdump=1) at /usr/src/sys/kern/kern_shutdown.c:366
> #2 0xf
On Sun, Jun 03, 2018 at 09:14:50PM +0200, Alexander Leidinger wrote:
> Quoting Alexander Leidinger (from Mon, 28
> May 2018 09:02:01 +0200):
>
> > Quoting Slawa Olhovchenkov (from Mon, 28 May 2018
> > 01:06:12 +0300):
> >
> >> On Sun, May 27, 2018 a
On Mon, May 28, 2018 at 09:02:01AM +0200, Alexander Leidinger wrote:
> Quoting Slawa Olhovchenkov (from Mon, 28 May 2018
> 01:06:12 +0300):
>
> > On Sun, May 27, 2018 at 09:41:59PM +0200, Kirill Ponomarev wrote:
> >
> >> On 05/22, Slawa Olhovchenkov wrote:
> &
On Sun, May 27, 2018 at 09:41:59PM +0200, Kirill Ponomarev wrote:
> On 05/22, Slawa Olhovchenkov wrote:
> > > It has been a while since I tried Karl's patch the last time, and I
> > > stopped because it didn't apply to -current anymore at some point.
> > >
On Tue, May 22, 2018 at 04:16:32PM +0200, Alexander Leidinger wrote:
>
> Quoting Slawa Olhovchenkov (from Tue, 22 May 2018
> 15:29:24 +0300):
>
> > On Tue, May 22, 2018 at 08:17:00AM -0400, Steve Wills wrote:
> >
> >> I may be seeing similar issues. Have y
On Tue, May 22, 2018 at 08:17:00AM -0400, Steve Wills wrote:
> I may be seeing similar issues. Have you tried leaving top -SHa running
> and seeing what threads are using CPU when it hangs? I did and saw pid
> 17 [zfskern{txg_thread_enter}] using lots of CPU but no disk activity
> happening. Do
On Sat, May 19, 2018 at 08:38:20PM +0200, Jan Beich wrote:
> Slawa Olhovchenkov writes:
>
> > On Fri, May 18, 2018 at 07:58:10PM +0200, Niclas Zeising wrote:
> >
> >> [ Cross posted to freebsd-current@ and freebsd-x11@. Please respect
> >> reply-to
On Fri, May 18, 2018 at 07:58:10PM +0200, Niclas Zeising wrote:
> [ Cross posted to freebsd-current@ and freebsd-x11@. Please respect
> reply-to and send all replies to freebsd-x11@. Thanks! ]
>
>
> Hi!
> I propose that we remove the old drm2 driver (sys/dev/drm2) from
> FreeBSD. I suggest
On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote:
> > Check the Makefiles
> >
> > % more /usr/ports/graphics/drm-next-kmod/Makefile
> >
> > ONLY_FOR_ARCHS= amd64
> > ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on amd64
> >
> > Not to ia32 friendly.
> >
>
> So do p
On Fri, Mar 23, 2018 at 04:21:32PM -0700, Bryan Drewery wrote:
> On 3/20/2018 12:07 AM, Peter Jeremy wrote:
> >
> > On 2018-Mar-11 10:43:58 -1000, Jeff Roberson
> > wrote:
> >> Also, if you could try going back to r328953 or r326346 and let me know if
> >> the problem exists in either. That w
patch.
10x!
.2 is is before pti patch and .4 is after pti patch?
This is like pti patch (w/ pti off) do small speed up (about 1%)?
> On Fri, Mar 9, 2018 at 10:16 AM, Slawa Olhovchenkov wrote:
>
> > On Fri, Mar 09, 2018 at 09:58:55AM -0500, Ed Maste wrote:
> >
> &g
On Fri, Mar 09, 2018 at 09:58:55AM -0500, Ed Maste wrote:
> On 9 March 2018 at 07:01, Slawa Olhovchenkov wrote:
> > On Thu, Mar 08, 2018 at 05:04:11PM -0500, Arshan Khanifar wrote:
> >
> >> Executive Summary:
> >> - The PTI feature increases the system call tim
On Thu, Mar 08, 2018 at 05:04:11PM -0500, Arshan Khanifar wrote:
> Executive Summary:
> - The PTI feature increases the system call times by more than 100%.
> - As a macrobenchmark, buildworld was used. Wall clock and user time
> showed no statistically-significant changes, while system time
> inc
On Sat, Sep 02, 2017 at 10:02:57PM -0400, Johannes M Dieterich wrote:
> Dear current/x11,
>
> please CC me on responses.
>
> I am writing you on behalf of the FreeBSDDesktop team concerning the
> future of drm1 in base.
>
> drm1 in base supports the following GPUs:
> * 3dfx Banshee/Voodoo3+ (td
On Sat, Jun 03, 2017 at 11:49:01PM -0600, Warner Losh wrote:
> > Netflix runs MAXPHYS of 8MB. There's issues with something this big, to be
> > sure, especially on memory limited systems. Lots of hardware can't do this
> > big an I/O, and some drivers can't cope, even if the underlying hardware
>
On Sat, Jun 03, 2017 at 11:55:51PM -0400, Allan Jude wrote:
> On 2017-06-03 22:35, Julian Elischer wrote:
> > On 4/6/17 4:59 am, Colin Percival wrote:
> >> On January 24, 1998, in what was later renumbered to SVN r32724, dyson@
> >> wrote:
> >>> Add better support for larger I/O clusters, includin
On Sun, May 14, 2017 at 01:12:11AM +, Rick Macklem wrote:
> >> It is also the case that mountd.c doesn't look "nobody" up in the password
> >> database
> >> to set the default. It would be nice to do this, but it could result in
> >> the mountd daemon
> >> getting "stuck" during a boot waiti
On Mon, May 08, 2017 at 11:45:46AM +, Rick Macklem wrote:
> Hi,
>
> Five years ago (yea, it slipped through a crack;-), Slawa reported that files
> created by root would end up owned by uid 2**32-2 (-2 as uint32_t).
> This happens if there is no "-maproot=" in the /etc/exports line.
>
> The
On Wed, Apr 05, 2017 at 04:15:41PM +, Alexey Dokuchaev wrote:
> > I've also tried without WITH_DEBUG= and now. . .
> >
> > # pkg delete llvm40
> > Checking integrity... done (0 conflicting)
> > Deinstallation has been requested for the following 1 packages (of 0
> > packages in the universe):
On Wed, Mar 22, 2017 at 10:25:24PM +0100, O. Hartmann wrote:
> Am Wed, 22 Mar 2017 21:10:51 +0100
> Michael Gmelin schrieb:
>
> > > On 22 Mar 2017, at 21:02, O. Hartmann wrote:
> > >
> > > CURRENT (FreeBSD 12.0-CURRENT #82 r315720: Wed Mar 22 18:49:28 CET 2017
> > > amd64) is
> > > annoyingly
On Sun, Mar 19, 2017 at 06:07:33PM +0200, Konstantin Belousov wrote:
> On Sun, Mar 19, 2017 at 04:58:40PM +0100, Dimitry Andric wrote:
> > On 19 Mar 2017, at 13:36, Rozhuk Ivan wrote:
> > >
> > > On Fri, 17 Mar 2017 17:53:24 +0100
> > > "O. Hartmann" wrote:
> > >
> > >>> Other OS detect AES-NI
On Sun, Mar 19, 2017 at 04:58:40PM +0100, Dimitry Andric wrote:
> On 19 Mar 2017, at 13:36, Rozhuk Ivan wrote:
> >
> > On Fri, 17 Mar 2017 17:53:24 +0100
> > "O. Hartmann" wrote:
> >
> >>> Other OS detect AES-NI on this server?
> >>
> >> I havn't ried so far, the box is in heavy use. I'd like
On Fri, Mar 17, 2017 at 06:31:11PM +0100, O. Hartmann wrote:
> Am Fri, 17 Mar 2017 20:07:35 +0300
> Slawa Olhovchenkov schrieb:
>
> > On Fri, Mar 17, 2017 at 05:53:24PM +0100, O. Hartmann wrote:
> >
> > > Am Fri, 17 Mar 2017 15:04:29 +0300
> > > Slawa Olh
On Fri, Mar 17, 2017 at 05:53:24PM +0100, O. Hartmann wrote:
> Am Fri, 17 Mar 2017 15:04:29 +0300
> Slawa Olhovchenkov schrieb:
>
> > On Fri, Mar 17, 2017 at 12:36:25PM +0100, O. Hartmann wrote:
> >
> > > Running recent CURRENT on a Fujitsu Celsius M740 equipted
On Fri, Mar 17, 2017 at 12:36:25PM +0100, O. Hartmann wrote:
> Running recent CURRENT on a Fujitsu Celsius M740 equipted with an Intel(R)
> Xeon(R) CPU E5-1650 v3 @ 3.50GHz CPU makes me some trouble.
>
> FreeBSD does not report the existence or availability of AES-NI feature, which
> is supposed
On Wed, Jan 18, 2017 at 10:19:15AM +0100, O. Hartmann wrote:
> Hello Daniel,
>
> thank you very much for responding!
>
> I just looked into "makeing release". I have a lot of NanoBSD images and build
> environments for our purpose at work, but I always strip off the compiler,
> too :-(
>
> I wa
On Mon, Jan 16, 2017 at 05:25:26PM +0100, Baptiste Daroussin wrote:
> On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote:
> > I noticed that suddenly vim is grabbing mouse movements, which makes life
> > really hard.
> >
> > Was there a specific revision that brought in this change,
On Mon, Dec 26, 2016 at 10:29:33PM +0300, Subbsd wrote:
> Hi,
>
> On recent FreeBSD version (tested on two host: one from
> svn://svn.freebsd.org/base/head ( r310507 now) and second from
> https://github.com/FreeBSDDesktop/freebsd-base-graphics.git /
> drm-next-4.7 ) and latest firefox ( firefox-
On Fri, Dec 23, 2016 at 09:37:40PM +0100, Willem Jan Withagen wrote:
> On 23-12-2016 20:30, Slawa Olhovchenkov wrote:
> > On Fri, Dec 23, 2016 at 08:16:39PM +0100, Willem Jan Withagen wrote:
> >
> >> On 23-12-2016 14:26, Slawa Olhovchenkov wrote:
> >>> On T
On Fri, Dec 23, 2016 at 08:16:39PM +0100, Willem Jan Withagen wrote:
> On 23-12-2016 14:26, Slawa Olhovchenkov wrote:
> > On Thu, Dec 22, 2016 at 09:26:02PM +0100, Willem Jan Withagen wrote:
> >
> >> On 16-12-2016 00:57, Adrian Chadd wrote:
> >>> heh, an updat
On Thu, Dec 22, 2016 at 09:26:02PM +0100, Willem Jan Withagen wrote:
> On 16-12-2016 00:57, Adrian Chadd wrote:
> > heh, an updated BIOS that solves the problem will solve the problem. :)
> >
> > I think you have enough information to provide to supermicro. Ie,
> > "SMAP says X, when physical mem
On Sat, Dec 17, 2016 at 10:43:52AM +0100, Olivier Cochard-Labbé wrote:
> On Sat, Dec 17, 2016 at 10:19 AM, Slawa Olhovchenkov wrote:
>
> >
> > ===
> > On FreeBSD older than 11.0, use more compact ip_fastfoward routine. It
> > processes most packets falling back t
On Sat, Dec 17, 2016 at 04:06:40PM +0800, Julian Elischer wrote:
> Hi
>
> I'm looking for recent information regarding profiling and tuning in
> FreeBSD.
>
> Google has turned up some links but I think that the best leads are
> still hiding..
> for example I only found
> https://wiki.freebs
On Fri, Dec 16, 2016 at 03:17:19AM +0100, Luigi Rizzo wrote:
> TL;DR; is there any way a userspace thread in FreeBSD can tell
> on which CPU it is (was) running ? I know the thread can migrate
> at any time but as long as the event is rare I can live with
> the occasionally wrong information.
> Li
On Thu, Dec 15, 2016 at 03:56:56PM +0200, Konstantin Belousov wrote:
> > > Possibly, the dmesg of the boot (with late_console=0) with this and only
> > > this patch applied against stock HEAD. This might be long.
> >
> > Do you need all (262144?) lines?
> >
> > Testing system
> > memory
On Thu, Dec 15, 2016 at 02:33:30PM +0200, Konstantin Belousov wrote:
> On Thu, Dec 15, 2016 at 01:51:18PM +0300, Slawa Olhovchenkov wrote:
> > On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote:
> >
> > > So my opinion did not changed, this sounds like f
On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote:
> So my opinion did not changed, this sounds like firmware problem.
> I do not see how can I drill into it more.
I am don't know how it related. msgbufp mapped different with and w/o
memory test:
w/o memory test, hang:
msgbufp=
On Wed, Dec 14, 2016 at 09:43:24PM +0200, Konstantin Belousov wrote:
> On Wed, Dec 14, 2016 at 10:29:43PM +0300, Slawa Olhovchenkov wrote:
> > On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote:
> >
> > > On Wed, Dec 14, 2016 at 06:26:27PM +0300,
On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote:
> On Wed, Dec 14, 2016 at 06:26:27PM +0300, Slawa Olhovchenkov wrote:
> > On Wed, Dec 14, 2016 at 03:13:36PM +0300, Slawa Olhovchenkov wrote:
> >
> > > On Wed, Dec 14, 2016 at 01:39:27PM +0200, K
On Wed, Dec 14, 2016 at 03:13:36PM +0300, Slawa Olhovchenkov wrote:
> On Wed, Dec 14, 2016 at 01:39:27PM +0200, Konstantin Belousov wrote:
>
> > In other words, it is almost certainly the hang and not a fault causing
> > hang. This means that the machine is not compl
On Wed, Dec 14, 2016 at 04:40:33PM +0200, Konstantin Belousov wrote:
> On Wed, Dec 14, 2016 at 03:13:36PM +0300, Slawa Olhovchenkov wrote:
> > On Wed, Dec 14, 2016 at 01:39:27PM +0200, Konstantin Belousov wrote:
> >
> > > In other words, it is almost certainly the hang
On Wed, Dec 14, 2016 at 01:39:27PM +0200, Konstantin Belousov wrote:
> In other words, it is almost certainly the hang and not a fault causing
> hang. This means that the machine is not compliant with the IA32
> architecture, in particular, the region reported as normal memory by
> E820 BIOS servi
On Wed, Dec 14, 2016 at 12:27:11PM +0200, Konstantin Belousov wrote:
> On Wed, Dec 14, 2016 at 11:53:50AM +0200, Konstantin Belousov wrote:
> > On Tue, Dec 13, 2016 at 08:43:45PM +0300, Slawa Olhovchenkov wrote:
> > > On Tue, Dec 13, 2016 at 07:25:29PM +0200, Konstan
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 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=
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.
&
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
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,
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, w
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
> BIOS, reboot, again frob etc.
> >>>
> >>> still need test patch? if yes, w
On Mon, Dec 12, 2016 at 08:36:47PM +0200, Konstantin Belousov wrote:
> On Mon, Dec 12, 2016 at 08:43:11PM +0300, Slawa Olhovchenkov wrote:
> > On Mon, Dec 12, 2016 at 07:24:18PM +0200, Konstantin Belousov wrote:
> >
> > > On Mon, Dec 12, 2016 at 08:16:34PM +0300,
On Mon, Dec 12, 2016 at 07:24:18PM +0200, Konstantin Belousov wrote:
> On Mon, Dec 12, 2016 at 08:16:34PM +0300, Slawa Olhovchenkov wrote:
> > On Mon, Dec 12, 2016 at 06:54:57PM +0200, Konstantin Belousov wrote:
> >
> > > On Mon, Dec 12, 2016 at 07:21:53PM +0300,
On Mon, Dec 12, 2016 at 06:54:57PM +0200, Konstantin Belousov wrote:
> On Mon, Dec 12, 2016 at 07:21:53PM +0300, Slawa Olhovchenkov wrote:
> > On Mon, Dec 12, 2016 at 04:54:18PM +0200, Konstantin Belousov wrote:
> >
> > > On Sun, Dec 11, 2016 at 11:47:09PM +0300,
On Mon, Dec 12, 2016 at 04:54:18PM +0200, Konstantin Belousov wrote:
> On Sun, Dec 11, 2016 at 11:47:09PM +0300, Slawa Olhovchenkov wrote:
> > Booting...
> > ESC[01;00H8+0x8+0xe9bdc]
> > KDB: debugger backends:
On Mon, Dec 12, 2016 at 01:46:21AM +0300, Slawa Olhovchenkov wrote:
> > > > > > Can you show the verbose dmesg up to the failure point ?
> > > > > > In particular, the SMAP lines should be relevant.
> > > > >
> > > > &g
On Mon, Dec 12, 2016 at 12:15:53AM +0300, Slawa Olhovchenkov wrote:
> On Sun, Dec 11, 2016 at 11:47:09PM +0300, Slawa Olhovchenkov wrote:
>
> > On Sun, Dec 11, 2016 at 10:06:54PM +0200, Konstantin Belousov wrote:
> >
> > > On Sun, Dec 11, 2016 at 10:45:59PM +030
On Sun, Dec 11, 2016 at 11:47:09PM +0300, Slawa Olhovchenkov wrote:
> On Sun, Dec 11, 2016 at 10:06:54PM +0200, Konstantin Belousov wrote:
>
> > On Sun, Dec 11, 2016 at 10:45:59PM +0300, Slawa Olhovchenkov wrote:
> > > On Sun, Dec 11, 2016 at 09:26:56PM +0200, Kons
On Sun, Dec 11, 2016 at 10:06:54PM +0200, Konstantin Belousov wrote:
> On Sun, Dec 11, 2016 at 10:45:59PM +0300, Slawa Olhovchenkov wrote:
> > On Sun, Dec 11, 2016 at 09:26:56PM +0200, Konstantin Belousov wrote:
> >
> > > On Sun, Dec 11, 2016 at 10:16:26PM +0300,
On Sun, Dec 11, 2016 at 09:26:56PM +0200, Konstantin Belousov wrote:
> On Sun, Dec 11, 2016 at 10:16:26PM +0300, Slawa Olhovchenkov wrote:
> > On Sun, Dec 11, 2016 at 09:21:11PM +0300, Slawa Olhovchenkov wrote:
> >
> > > On Sat, Nov 26, 2016 at 05:57:47PM +0200, K
On Sun, Dec 11, 2016 at 09:21:11PM +0300, Slawa Olhovchenkov wrote:
> On Sat, Nov 26, 2016 at 05:57:47PM +0200, Konstantin Belousov wrote:
>
> > On Sat, Nov 26, 2016 at 12:21:24PM +0300, Slawa Olhovchenkov wrote:
> > > I am try to enable NUMA in bios and can't boot
On Sat, Nov 26, 2016 at 05:57:47PM +0200, Konstantin Belousov wrote:
> On Sat, Nov 26, 2016 at 12:21:24PM +0300, Slawa Olhovchenkov wrote:
> > I am try to enable NUMA in bios and can't boot FreeBSD.
> > Boot stoped after next messages:
> >
> > ===
> > Boot
On Tue, Dec 06, 2016 at 06:53:03AM -0800, Navdeep Parhar wrote:
> On Tue, Dec 06, 2016 at 05:43:38PM +0300, Slawa Olhovchenkov wrote:
> > On Tue, Dec 06, 2016 at 06:41:14AM -0800, Navdeep Parhar wrote:
> >
> > > On Tue, Dec 06, 2016 at 05:34:56PM +0300, Slawa Olhovchenk
On Tue, Dec 06, 2016 at 06:41:14AM -0800, Navdeep Parhar wrote:
> On Tue, Dec 06, 2016 at 05:34:56PM +0300, Slawa Olhovchenkov wrote:
> > On Tue, Dec 06, 2016 at 06:25:44AM -0800, Navdeep Parhar wrote:
> >
> > > On Tue, Dec 06, 2016 at 02:47:15PM +0300, Slawa Olhovchenkov
On Tue, Dec 06, 2016 at 06:25:44AM -0800, Navdeep Parhar wrote:
> On Tue, Dec 06, 2016 at 02:47:15PM +0300, Slawa Olhovchenkov wrote:
> > Now I am try to update fw in chelsio card.
> > Firmware can't be updated if card was running (interface go to UP).
> > I am try
On Tue, Dec 06, 2016 at 12:50:40PM +0100, Hans Petter Selasky wrote:
> On 12/06/16 12:47, Slawa Olhovchenkov wrote:
> > Now I am try to update fw in chelsio card.
> > Firmware can't be updated if card was running (interface go to UP).
> > I am try to unload if_cxgbe mod
Now I am try to update fw in chelsio card.
Firmware can't be updated if card was running (interface go to UP).
I am try to unload if_cxgbe module, check module unloaded... and after
short time see module loaded again!
How is this possible?
___
freebsd-cur
Is support for QLogic FastLinQ QL45000 planed in FreeBSD?
___
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"
On Sat, Nov 26, 2016 at 01:55:14PM -0800, Adrian Chadd wrote:
> ok, hm. then i don' know offhand, not without putting in printf debugging. :)
I am not expert in this code, I am need you patches for printf debugging.
> On 26 November 2016 at 13:51, Slawa Olhovchenkov wrote:
> &g
On Sat, Nov 26, 2016 at 01:49:00PM -0800, Adrian Chadd wrote:
> Ok. So boot verbose and let's see what it says.
See first message: it's already verbose boot.
Yes, only 3 lines.
>
> On 26 November 2016 at 10:39, Slawa Olhovchenkov wrote:
> > On Sat, Nov 26, 2016 at
On Sat, Nov 26, 2016 at 09:44:49AM -0800, Adrian Chadd wrote:
> The ACPI SRAT parsing code - sys/x86/acpica/srat.c .
>
> I'd start by enabling bootverbose - adds one echo (SLIT.Localities and
> the table); adds CPU affinity info (legacy, XAPIC, ACPI) and other
> locality stuff.
I am use r308809
On Sat, Nov 26, 2016 at 09:35:08AM -0800, Adrian Chadd wrote:
> It may be something to do with memory topology parsing. Maybe we need
> some more debugging there to try and catch it.
What debug you need?
> On 26 November 2016 at 01:21, Slawa Olhovchenkov wrote:
> > I am try to
On Sat, Nov 26, 2016 at 07:07:20PM +0300, Slawa Olhovchenkov wrote:
> On Sat, Nov 26, 2016 at 05:57:47PM +0200, Konstantin Belousov wrote:
>
> > On Sat, Nov 26, 2016 at 12:21:24PM +0300, Slawa Olhovchenkov wrote:
> > > I am try to enable NUMA in bios and can't boot
On Sat, Nov 26, 2016 at 05:57:47PM +0200, Konstantin Belousov wrote:
> On Sat, Nov 26, 2016 at 12:21:24PM +0300, Slawa Olhovchenkov wrote:
> > I am try to enable NUMA in bios and can't boot FreeBSD.
> > Boot stoped after next messages:
> >
> > ===
> > Boot
I am try to enable NUMA in bios and can't boot FreeBSD.
Boot stoped after next messages:
===
Booting...
KDB: debugger backends: ddb
KDB: current backend: ddb
===
This is verbose boot.
No reaction to ~^B, NMI.
Same for head and 10.3-RELEASE.
Hardware is Supermicro X10DRi, Dual E5-2650v4, 256GB R
On Mon, Jul 18, 2016 at 12:39:46PM -0400, Jung-uk Kim wrote:
> On 07/18/16 08:12 AM, Mathieu Arnold wrote:
> > Hi,
> >
> > +--On 11 juillet 2016 22:56:00 +0300 Slawa Olhovchenkov
> > wrote:
> > | On Mon, Jul 11, 2016 at 03:00:39PM -0400, Jung-uk Kim wrote:
&g
On Thu, Oct 06, 2016 at 07:57:57AM -0600, Sean Bruno wrote:
> I'm doing a large amount of change to ixgbe(4) in support of IFLIB
> implementations and running into failures when trying to apply large
> diffs. This is causing phabricator reviews to be unuseable as well.
>
> I've setup two trees t
On Wed, Sep 14, 2016 at 10:07:15PM -0400, Garrett Wollman wrote:
> <
> said:
>
> > Well, it's definitely too late for 11, now.
>
> > But, Debian is preparing to remove their heimdal package entirely,
> > imminently: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837728
>
> The primary issue
On Thu, Sep 01, 2016 at 09:10:00PM +, Glen Barber wrote:
> As some of you may be aware, a few last-minute showstoppers appeared
> since 11.0-RC1 (and before RC1).
>
> One of the showstoppers has been fixed in 12-CURRENT, and merged to
> stable/11 and releng/11.0 that affected booting from lar
On Mon, Aug 01, 2016 at 02:16:59PM +0300, Andriy Gapon wrote:
>
> Mateusz,
>
> just out of curiosity, have you tried to explore alternative spinlock
> implementations like a ticket lock? It would be interesting to see if
> there are any improvements to be gained there.
Effective ticket lock i
On Wed, Jul 20, 2016 at 07:38:09AM +0300, Konstantin Belousov wrote:
> On Tue, Jul 19, 2016 at 05:35:59PM +0200, Hartmut Brandt wrote:
> > Hi,
> >
> > I'm trying to use asio (that's boost::asio without boost) to handle
> > listening sockets asynchronuosly. This appears not to work. There are als
On Tue, Jul 12, 2016 at 02:05:32PM -0700, Chris H wrote:
> On Tue, 12 Jul 2016 16:09:10 +0930 Shane Ambler wrote
>
> > On 12/07/2016 06:54, Conrad Meyer wrote:
> > > DVD-R dates to 1997; cheap USB flash devices are now pervasive. Maybe
> > > it's time to move on from CD.
> >
> > +1 on dropping
1 - 100 of 328 matches
Mail list logo