On Fri, Feb 05, 2021 at 11:54:07AM +0100, GomoR wrote:
> On 2021-02-05 09:11, GomoR wrote:
> >> The first step I would do if possible would be to bisect between the
> >> last
> >> known working version and the version that is known to be broken to
> >> determine which commit introduced the
On Fri, Jan 29, 2021 at 10:12:03AM -0700, Alan Somers wrote:
> What does "camcontrol devlist" show?
Only 2 disk: usb-flash and da1 (isci connected)
(I am currently just boot from 12.2 install)
> On Fri, Jan 29, 2021 at 10:06 AM Slawa Olhovchenkov wrote:
>
> > On F
ch drives are
> installed in which slots.
For me sesutil failed w/ "No SES device found"
>
> On Fri, Jan 29, 2021 at 9:44 AM Slawa Olhovchenkov wrote:
>
> > On Fri, Jan 29, 2021 at 09:22:47AM -0700, Alan Somers wrote:
> >
> > > The short story is: SGPIO sucks. It do
at additional drivers need?
> On Fri, Jan 29, 2021 at 9:02 AM Slawa Olhovchenkov wrote:
>
> > I am have Supermicro MB X9DBU-iF connected to bcakplane BPN-SAS-825TQ
> > by T-SGPIO cables. sesutil don't found any SES device.
> >
> >
I am have Supermicro MB X9DBU-iF connected to bcakplane BPN-SAS-825TQ
by T-SGPIO cables. sesutil don't found any SES device.
Is this posible to have control to this backplane?
___
freebsd-stable@freebsd.org mailing list
Before ncurses update emcas tramp mode got next echo string
_echo^H ^H^H ^H^H ^H^H ^H^H ^Hstty
after ncurses update echo string is different:
_echo^M#$ _ech ^H^M#$ _ec ^H^M#$ _e ^H^M#$ _ ^H^M#$ ^Hstty icanon erase ^H
cols 32767_echo
i.e. ncurses on `dumb` terminal still do refresh all line,
On Sun, Apr 12, 2020 at 07:08:06PM +0200, Stefan Bethke wrote:
> Am 12.04.2020 um 19:03 schrieb Slawa Olhovchenkov :
> >
> > On Sun, Apr 12, 2020 at 06:38:10PM +0200, Stefan Bethke wrote:
> >
> >>
> >>
> >>> Am 12.04.2020 um 18:31 schrieb Sla
On Sun, Apr 12, 2020 at 06:38:10PM +0200, Stefan Bethke wrote:
>
>
> > Am 12.04.2020 um 18:31 schrieb Slawa Olhovchenkov :
> >
> > On Sun, Apr 12, 2020 at 06:24:09PM +0200, Stefan Bethke wrote:
> >
> >> Am 12.04.2020 um 17:43 schrieb Slawa Olhovchen
On Sun, Apr 12, 2020 at 06:24:09PM +0200, Stefan Bethke wrote:
> Am 12.04.2020 um 17:43 schrieb Slawa Olhovchenkov :
> >
> > On Sun, Apr 12, 2020 at 04:37:06PM +0200, Stefan Bethke wrote:
> >
> >> I have a server I don't have physical access to right now, whic
On Sun, Apr 12, 2020 at 04:37:06PM +0200, Stefan Bethke wrote:
> I have a server I don't have physical access to right now, which has a broken
> SATA disk that produces mostly errors (but not entirely).
>
> The disk has two partitions that are part of a zpool each. I can't bring the
> system
On Mon, Nov 25, 2019 at 03:36:21PM -0500, Ryan Stone wrote:
> Remove "using namespace std;" from your program.
I am don't have "using namespace std;".
Example:
===
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
===
Yes, only
Is this posible (now) for access to NETAMP from C++?
I am see headers conflict:
In file included from /usr/include/net/netmap_user.h:104:
In file included from /usr/include/net/netmap.h:812:
/usr/include/stdatomic.h:141:21: error: reference to 'memory_order' is ambiguous
On Mon, Jun 24, 2019 at 05:42:39PM +0300, Slawa Olhovchenkov wrote:
> On Mon, Jun 24, 2019 at 10:35:03AM -0400, Paul Mather wrote:
>
> > On Jun 24, 2019, at 10:17 AM, Slawa Olhovchenkov wrote:
> >
> > > I am use haproxy logged to syslog and have log lines like this:
On Mon, Jun 24, 2019 at 10:35:03AM -0400, Paul Mather wrote:
> On Jun 24, 2019, at 10:17 AM, Slawa Olhovchenkov wrote:
>
> > I am use haproxy logged to syslog and have log lines like this:
> >
> > Jun 24 17:04:25 ha01 haproxy[32508]: 193.34.87.146:57625
> > [24/J
I am use haproxy logged to syslog and have log lines like this:
Jun 24 17:04:25 ha01 haproxy[32508]: 193.34.87.146:57625
[24/Jun/2019:17:04:23.277] balancer~ default-pool/main 0/0/0/-1/2012 504 194 -
- sH-- 888/888/4/4/0 0/0 "POST /vs HTTP/1.1"
Is this posible to learn syslogd to use
On Mon, Jun 10, 2019 at 03:13:31PM +, Glen Barber wrote:
> On Sat, Jun 08, 2019 at 01:39:49PM +0300, Slawa Olhovchenkov wrote:
> > On Fri, Jun 07, 2019 at 10:26:34PM +, Glen Barber wrote:
> >
> > > The third BETA build of the 11.3-RELEASE release cycle is now avai
On Fri, Jun 07, 2019 at 10:26:34PM +, Glen Barber wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> The third BETA build of the 11.3-RELEASE release cycle is now available.
Can some one from re@ do MFC r348772 to 11.3-RELEASE before release?
This is important fix.
Thanks
On Wed, Feb 27, 2019 at 11:54:20PM +0300, Slawa Olhovchenkov wrote:
> Is this known issuse?
>
> Fatal trap 9: general protection fault while in kernel mode
> cpuid = 13; apic id = 2a
> instruction pointer = 0x20:0x806b6a94
> stack pointer = 0x28:0xfe
Is this known issuse?
Fatal trap 9: general protection fault while in kernel mode
cpuid = 13; apic id = 2a
instruction pointer = 0x20:0x806b6a94
stack pointer = 0x28:0xfe2026e274f0
frame pointer = 0x28:0xfe2026e274f0
code segment= base 0x0,
1. gptzfsboot from 12 incompatible w/ loader from 11 ("kernel not found")
2. loader from 12 incomatibe w/ kernel from 11 (ZFS file system unknown)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
1. How I can build release media of FreeBSD-12 on FreeBSD-11 system?
Currenly process failed by 'Abort trap'.
585191 121 -rw---1 root wheel
8962048 Dec 5 18:58 ./ldconfig.core
585199 121 -rw---1 root
On Wed, Jun 20, 2018 at 07:37:20PM +0200, Miroslav Lachman wrote:
> > %busy comes from the devstat layer. It's defined as the percent of the
> > time over the polling interval in which at least one transaction was
> > awaiting completion by the lower layers. It's an imperfect measure of
> >
On Thu, Jun 07, 2018 at 07:04:29PM +0930, Shane Ambler wrote:
> On 07/06/2018 16:09, Peter Jeremy wrote:
> > I've noticed that 11-stable/amd64 has been wiring seemingly excessive
> > amounts of RAM for some time (the problem goes back at least 6 months).
> > This extends to getting ENOMEM errors
# vmstat -m|grep temp
Type InUse MemUse HighUse Requests Size(s)
temp60 18014398509481829K - 32350974
16,32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536
Is this normal?
SVN rev: r328463
___
On Wed, Mar 28, 2018 at 11:25:08PM -0700, Kevin Oberman wrote:
> > > > r325665 is previos point and is good.
> > > > r331615 crashed.
> > > > Can I use some script for bisect?
> > >
> > > I'm not aware of a script for this. The only tool I've used is "git
> > > bisect", which is very handy if
On Wed, Mar 28, 2018 at 10:29:10AM -0500, Eric van Gyzen wrote:
> On 03/28/2018 08:09, Slawa Olhovchenkov wrote:
> > I am upgrade system to latest -STABLE and now see kernel crash:
> >
> > - loading virtualbox modules build on 11.1-RELEASE-p6
> > - loading nvidia modu
On Wed, Mar 28, 2018 at 05:13:48PM +0200, Gregory Byshenk wrote:
> On Wed, Mar 28, 2018 at 05:35:51PM +0300, Slawa Olhovchenkov wrote:
> > On Wed, Mar 28, 2018 at 03:39:46PM +0200, Gregory Byshenk wrote:
> > >
> > > Did you rebuild your virtualbox and nvidia module
On Wed, Mar 28, 2018 at 03:39:46PM +0200, Gregory Byshenk wrote:
> On Wed, Mar 28, 2018 at 04:09:04PM +0300, Slawa Olhovchenkov wrote:
> > I am upgrade system to latest -STABLE and now see kernel crash:
> >
> > - loading virtualbox modules build on 11.1-RELEASE-p6
> &
I am upgrade system to latest -STABLE and now see kernel crash:
- loading virtualbox modules build on 11.1-RELEASE-p6
- loading nvidia module build on 11.1-RELEASE-p6 and start xdm
Is this expected? I am mean about loading modules builded on
11.1-RELEASE on any 11.1-STABLE.
On Mon, Mar 19, 2018 at 03:53:03PM +0100, Patrick M. Hausen wrote:
> Hi all,
>
> any ideas why a current RELENG_11_1 system with ixl(4)
> onboard interfaces might not negotiate with a switch that
> has only fast ethernet?
>
> status: no carrieron the host
>
On Tue, Aug 08, 2017 at 01:49:08PM +0200, Hans Petter Selasky wrote:
> On 08/08/17 13:33, Slawa Olhovchenkov wrote:
> > TW_RUNLOCK(V_tw_lock);
> > and
> > if (INP_INFO_TRY_WLOCK(_tcbinfo)) {
> >
> > `inp` can be invalidated, freed and this pointer may be inva
On Tue, Aug 08, 2017 at 10:31:33AM +0200, Hans Petter Selasky wrote:
> Here is the conclusion:
>
> The following code is going in an infinite loop:
>
>
> > for (;;) {
> > TW_RLOCK(V_tw_lock);
> > tw = TAILQ_FIRST(_twq_2msl);
> > if (tw ==
On Thu, Jul 27, 2017 at 04:29:52PM +0300, Alexander Motin wrote:
> Hi Mike,
>
> On 27.07.2017 16:21, Mike Tancsa wrote:
> > I noticed quite a few MFCs to RELENG_11 around zfs yesterday and today.
> > First off, thank you for all these fixes/enhancements! Of the some 60
> > MFCs, are there
can be inc/dec (obviously >1, ie not in
> a state where you can dec to 0) via atomics, without grabbing a lock.
> That'll make this particular use case mch faster.
>
> (dfbsd does this.)
I can try you patch.
> -a
>
>
> On 21 March 2017 at 09:42, Slawa Olhovchenkov
I am have strange issuse on stable/10:
# devinfo -v
nexus0
apic0
ram0
acpi0
[...]
pcib0 pnpinfo _HID=PNP0A08 _UID=0 at handle=\_SB_.PCI0
pci0
hostb0 pnpinfo vendor=0x8086 device=0xd130 subvendor=0x1014
subdevice=0x03ce class=0x06 at slot=0 function=0 dbsf=pci0:0:0:0
I am see lock contetntion cuased by aio read (same file segment from
multiple process simultaneous):
07.74% [26756]lock_delay @ /boot/kernel/kernel
92.21% [24671] __mtx_lock_sleep
52.14% [12864] vm_page_enqueue
100.0% [12864] vm_fault_hold
87.71% [11283]
On Wed, Mar 08, 2017 at 09:00:34AM +0500, Eugene M. Zheganin wrote:
> Hi.
>
> Some have probably seen this already -
> http://lists.dragonflybsd.org/pipermail/users/2017-March/313254.html
>
> So, could anyone explain why FreeBSD was owned that much. Test is split
> into two parts, one is
On Tue, Mar 07, 2017 at 10:19:35AM +0800, Erich Dollansky wrote:
> Hi,
>
> I wonder about the slow speed of my machine while top shows ample
> inactive memory:
>
> last pid: 85287; load averages: 2.56, 2.44, 1.68
> up 6+10:24:45 10:13:36 191 processes: 5 running, 186 sleeping
> CPU 0:
On Wed, Feb 22, 2017 at 11:47:42PM +0300, Lev Serebryakov wrote:
> Hello Freebsd-stable,
>
>Now if you build zfs.ko with -O0 it panics on boot.
>
>If you use default optimization level, a lot of fbt DTreace probes are
> missing.
Is this related to
On Wed, Feb 01, 2017 at 07:25:18AM -0700, Jakub Lach wrote:
> I would think so, if only I would not clone the disk/system via the same USB
> port mere weeks ago.
> Moreover, sysutils/f3 fully writes and validates (checksums) 30G+ memory
> cards via the same port without problems.
In my case
On Wed, Feb 01, 2017 at 06:52:01AM -0700, Jakub Lach wrote:
> Yes, HDD and card reader was USB mounted.
>
> This time, I've copied about 12G from 38G from internal SSD (UFS2) to
> HDD via USB (FAT32), then system panicked with CAM errors.
I am have like issuse on laptop w/ broken USB
I am got panic on recent stable:
Fatal trap 18: integer divide fault while in kernel mode
cpuid = 3; apic id = 06
instruction pointer = 0x20:0x81453230
stack pointer = 0x28:0xfe3e56f46480
frame pointer = 0x28:0xfe3e56f464a0
code segment= base
On Wed, Jan 18, 2017 at 02:48:19PM +0500, Eugene M. Zheganin wrote:
> Hi.
>
> Could someone recommend a decent 40Gbit adapter that are proven to be
> working under FreeBSD ? The intended purpose - iSCSI traffic, not much
> pps, but rates definitely above 10G. I've tried Supermicro-manufactured
>
On Sun, Jan 15, 2017 at 10:40:42AM -0600, Dan Mack wrote:
> I have a system which builds world, kernel, install, boot, installworld,
> reboot several times per week. I just noticed that my build times
> increased from about (just cherry picking a couple build logs):
>
>Starting build of
I am have stable/11 and E5v4.
I am don't see cpufreq support by sysctl:
# sysctl dev.cpu.0
dev.cpu.0.cx_method: C1/hlt
dev.cpu.0.cx_usage_counters: 61755
dev.cpu.0.cx_usage: 100.00% last 1us
dev.cpu.0.cx_lowest: C2
dev.cpu.0.cx_supported: C1/1/1
dev.cpu.0.%parent: acpi0
dev.cpu.0.%pnpinfo:
On Sat, Dec 17, 2016 at 05:12:13PM +1100, Ian Smith wrote:
> On Fri, 16 Dec 2016 18:08:34 +0100, Fernando Herrero Carrón wrote:
> > Hi everyone,
>
> Hi,
>
> you've had plenty of helpful responses, but nobody has commented on:
>
> > My only reason for wanting to boot with UEFI is faster boot,
On Fri, Dec 16, 2016 at 11:43:18AM -0600, Eric van Gyzen wrote:
> On 12/16/2016 11:39, Slawa Olhovchenkov wrote:
> > On Fri, Dec 16, 2016 at 06:08:34PM +0100, Fernando Herrero Carrón wrote:
> >
> >> Hi everyone,
> >>
> >> A few months ago I got myself
On Fri, Dec 16, 2016 at 06:08:34PM +0100, Fernando Herrero Carrón wrote:
> Hi everyone,
>
> A few months ago I got myself a new box and I have been happily running
> FreeBSD on it ever since. I noticed that the boot was not as fast as I had
> expected and I've realized that, while my disk is GPT
On Thu, Dec 08, 2016 at 07:56:03PM +0200, Andriy Gapon wrote:
> On 08/12/2016 18:57, Slawa Olhovchenkov wrote:
> > kgdb7111 don't find .debug under /usr/lib/debug/
> > gdb found it.
>
> $ gdb7111 bhyve /var/coredumps/bhyve.0.0.core
> GNU gdb (GDB) 7.11.1 [GDB v7.11.1 for
On Thu, Dec 08, 2016 at 04:52:35PM +, K. Macy wrote:
> kgdb7111 is what you use for kernel. It works fine for me.
kgdb7111 don't find .debug under /usr/lib/debug/
gdb found it.
> On Thu, Dec 8, 2016 at 08:29 Slawa Olhovchenkov <s...@zxy.spb.ru> wrote:
>
> > On Thu,
1. gdb7111 badly integrated w/ 11 and up (don't see kernel debug
symbols)
2. all included in base systems can't be core dumped.
> On Thu, Dec 8, 2016 at 06:53 Slawa Olhovchenkov <s...@zxy.spb.ru> wrote:
>
> > % gdb ./edge_stat
> >
> > GNU gdb 6.1.1 [FreeBSD]
>
% gdb ./edge_stat
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is
On Fri, Oct 21, 2016 at 01:47:08PM +0100, Pete French wrote:
> > In bad case metadata of every file will be placed in random place of disk.
> > ls need access to metadata of every file before start of output listing.
>
> Umm, are we not talkong abut an issue where the directoyr no longer
On Fri, Oct 21, 2016 at 04:51:36PM +0500, Eugene M. Zheganin wrote:
> Hi.
>
> On 21.10.2016 15:20, Slawa Olhovchenkov wrote:
> >
> > ZFS prefetch affect performance dpeneds of workload (independed of RAM
> > size): for some workloads wins, for some workloads lose (f
On Fri, Oct 21, 2016 at 11:02:57AM +0100, Steven Hartland wrote:
> > Mem: 21M Active, 646M Inact, 931M Wired, 2311M Free
> > ARC: 73M Total, 3396K MFU, 21M MRU, 545K Anon, 1292K Header, 47M Other
> > Swap: 4096M Total, 4096M Free
> >
> > PID USERNAME PRI NICE SIZERES STATE C TIME
On Thu, Oct 20, 2016 at 08:54:05AM -0600, Alan Somers wrote:
> On Wed, Oct 19, 2016 at 11:10 AM, Slawa Olhovchenkov <s...@zxy.spb.ru> wrote:
> > tcsh called by sshd for invocation of scp: `tcsh -c scp -f Расписание.pdf`
> > At this time no any LC_* is set.
> > tcsh r
tcsh called by sshd for invocation of scp: `tcsh -c scp -f Расписание.pdf`
At this time no any LC_* is set.
tcsh read .cshrc and set LC_CTYPE=ru_RU.UTF-8 LC_COLLATE=ru_RU.UTF-8.
After this invocation of scp will be incorrect:
7ab0 20 2d 66 20 c3 90 c2 a0 c3 90 c2 b0 c3 91 c2 81 | -f
@ CPU_CLK_UNHALTED_CORE [271718 samples]
22.48% [61081]lock_delay @ /boot/kernel/kernel
99.72% [60908] __mtx_lock_sleep
67.69% [41230] zone_fetch_slab
100.0% [41230] zone_import
100.0% [41230]zone_alloc_item
99.99% [41226] uma_zalloc_arg
On Fri, Oct 14, 2016 at 11:48:38AM +0200, Julien Charbon wrote:
> >>> Also, using dtrace too complex in production (need complex startup
> >>> under screen and capture output) and for many peoples.
> >>> kdb_backtrace() have too less administrative overhead.
> >>
> >> I still think it is
On Thu, Oct 13, 2016 at 06:14:29PM +0200, Julien Charbon wrote:
> On 10/13/16 5:17 PM, Slawa Olhovchenkov wrote:
> > On Thu, Oct 13, 2016 at 05:06:00PM +0200, Julien Charbon wrote:
> >
> >>>> will give you that trace in the core, and without INVARIANT then it
On Thu, Oct 13, 2016 at 05:06:00PM +0200, Julien Charbon wrote:
> >> will give you that trace in the core, and without INVARIANT then it is
> >> better to use dtrace:
> >>
> >> $ cat tcp-twstart-dropped.d
> >> fbt::tcp_twstart:entry
> >> /args[0]->t_inpcb->inp_flags & 0x0400/
> >> {
> >>
On Thu, Oct 13, 2016 at 01:56:21PM +0200, Julien Charbon wrote:
> >> Something like:
> >
> > Yes, thanks!
>
> Proposed changes added in the review:
>
> https://reviews.freebsd.org/D8211
>
> tell me when you have three days without issue with this change.
>
> >> tcp_detach() {
> >>
> >>
On Wed, Oct 12, 2016 at 05:17:35PM +0200, Julien Charbon wrote:
> I see, thus just for the context: The TCP stack in sys/dev/cxgb*
> is a
> TOE (TCP Offload Engine?) TCP stack for Chelsio NICs, it is a
> separate/side TCP stack that is used only with
On Wed, Oct 12, 2016 at 02:35:11PM +0200, Julien Charbon wrote:
>
> Hi Slawa,
>
> On 10/12/16 2:13 PM, Slawa Olhovchenkov wrote:
> > On Wed, Oct 12, 2016 at 02:06:59PM +0200, Julien Charbon wrote:
> >>>>>>> sofree() call tcp_usr_detach() and in tcp
On Wed, Oct 12, 2016 at 02:06:59PM +0200, Julien Charbon wrote:
> > sofree() call tcp_usr_detach() and in tcp_usr_detach() we have
> > unexpected INP_TIMEWAIT.
>
> I see, thus just for the context: The TCP stack in sys/dev/cxgb* is a
> TOE (TCP Offload Engine?) TCP stack
On Wed, Oct 12, 2016 at 11:42:38AM +0200, Julien Charbon wrote:
> On 10/12/16 11:29 AM, Slawa Olhovchenkov wrote:
> > On Wed, Oct 12, 2016 at 11:19:48AM +0200, Julien Charbon wrote:
> >
> >>> if INP_WLOCK is like spinlock -- this is dead lock.
> >>>
On Wed, Oct 12, 2016 at 11:19:48AM +0200, Julien Charbon wrote:
> > if INP_WLOCK is like spinlock -- this is dead lock.
> > if INP_WLOCK is like mutex -- thread1 resheduled.
>
> Thanks, I understand you question now. No an interrupt cannot bypass a
> lock: Here INP_WLOCK is like mutex --
On Wed, Oct 12, 2016 at 10:18:18AM +0200, Julien Charbon wrote:
>
> Hi Slawa,
>
> On 10/11/16 2:11 PM, Slawa Olhovchenkov wrote:
> > On Tue, Oct 11, 2016 at 09:20:17AM +0200, Julien Charbon wrote:
> >> Then threads are competing for the INP_WLOCK lock. For
On Tue, Oct 11, 2016 at 09:20:17AM +0200, Julien Charbon wrote:
> Then threads are competing for the INP_WLOCK lock. For the example,
> let's say the thread A wants to run tcp_input()/in_pcblookup_mbuf() and
> racing for this INP_WLOCK:
>
>
On Mon, Oct 10, 2016 at 05:44:21PM +0200, Julien Charbon wrote:
> >> can check the current other usages of goto findpcb in tcp_input(). The
> >> rational here being:
> >>
> >> - Behavior before the patch: If the inp we found was deleted then goto
> >> findpcb.
> >> - Behavior after the patch:
On Mon, Oct 10, 2016 at 04:03:39PM +0200, Julien Charbon wrote:
>
> Hi Slawa,
>
> On 10/10/16 3:32 PM, Slawa Olhovchenkov wrote:
> > On Mon, Oct 10, 2016 at 01:26:12PM +0200, Julien Charbon wrote:
> >> On 10/6/16 1:10 PM, Slawa Olhovchenkov wrote:
> >>> O
On Mon, Oct 10, 2016 at 01:26:12PM +0200, Julien Charbon wrote:
>
> Hi,
>
> On 10/6/16 1:10 PM, Slawa Olhovchenkov wrote:
> > On Thu, Oct 06, 2016 at 09:28:06AM +0200, Julien Charbon wrote:
> >
> >> 2. thread1: In tcp_close() the inp is marked with I
On Mon, Oct 10, 2016 at 01:26:12PM +0200, Julien Charbon wrote:
>
> Hi,
>
> On 10/6/16 1:10 PM, Slawa Olhovchenkov wrote:
> > On Thu, Oct 06, 2016 at 09:28:06AM +0200, Julien Charbon wrote:
> >
> >> 2. thread1: In tcp_close() the inp is marked with I
Has anybody comment on this?
During debug tcp-related freeze I am collect starnge mbuf-related
freeze (this is like recursive lock to UMA Slabs keg) and trace:
last pid: 49575; load averages: 2.00, 2.05, 3.75up 1+01:12:08 22:13:42
853 processes: 15 running, 769 sleeping, 35 waiting, 34
On Thu, Oct 06, 2016 at 09:28:06AM +0200, Julien Charbon wrote:
> Thanks again to Slawa, for his numerous debug reports and always
> questioning my explanations. His last question directly led to this
> finding. He is testing a quick workaround patch to check if there is more.
Thanks very
On Thu, Oct 06, 2016 at 09:28:06AM +0200, Julien Charbon wrote:
> 2. thread1: In tcp_close() the inp is marked with INP_DROPPED flag, the
> process continues and calls INP_WUNLOCK() here:
>
> https://github.com/freebsd/freebsd/blob/releng/11.0/sys/netinet/tcp_subr.c#L1568
Look also to
On Wed, Sep 28, 2016 at 12:06:47PM +0200, Julien Charbon wrote:
> > Tracing command intr pid 12 tid 100026 td 0xf8011424b500
> > sched_switch() at 0x804c956d = sched_switch+0x6ad/frame
> > 0xfe3876f0
> > mi_switch() at 0x804a8d92 = mi_switch+0xd2/frame
On Mon, Sep 26, 2016 at 11:33:12AM +0200, Julien Charbon wrote:
>
> Hi Slawa,
>
> On 9/25/16 2:46 PM, Slawa Olhovchenkov wrote:
> > On Fri, Sep 23, 2016 at 11:01:43PM +0300, Slawa Olhovchenkov wrote:
> >>> On 9/21/16 9:51 PM, Slawa Olhovchenkov wrote:
> >&g
On Mon, Sep 26, 2016 at 06:20:42PM +0300, Konstantin Belousov wrote:
> On Thu, Sep 22, 2016 at 12:33:55PM +0300, Slawa Olhovchenkov wrote:
> > OK, try this patch.
>
> Was the patch tested ?
No more AIO related issused/nginx core dumps.
I Can't get long uptime by other iss
On Mon, Sep 26, 2016 at 01:57:03PM +0200, Julien Charbon wrote:
>
> Hi Slawa,
>
> On 9/25/16 2:46 PM, Slawa Olhovchenkov wrote:
> > On Fri, Sep 23, 2016 at 11:01:43PM +0300, Slawa Olhovchenkov wrote:
> >> On Wed, Sep 21, 2016 at 11:25:18PM +0200, Julien Charbon wrot
On Mon, Sep 26, 2016 at 11:33:12AM +0200, Julien Charbon wrote:
> >>> - tcp_input()/tcp_twstart()/tcp_tw_2msl_scan(reuse=1)
> >>
> >> My current hypothesis:
> >>
> >> nginx do write() (or may be close()?) to socket, kernel lock
> >> first inp in V_twq_2msl, happen callout for pfslowtimo() on the
On Mon, Sep 26, 2016 at 10:51:07AM +0200, Julien Charbon wrote:
> > 1049 kqread- I 145:58.35 nginx: worker process (nginx)
> > 1050 kqread- I 136:33.36 nginx: worker process (nginx)
> > 1051 kqread- I 140:59.73 nginx: worker process (nginx)
> > 1052 kqread-
On Fri, Sep 23, 2016 at 10:16:56PM +0300, Slawa Olhovchenkov wrote:
> On Thu, Sep 22, 2016 at 01:20:45PM +0300, Slawa Olhovchenkov wrote:
>
> > On Thu, Sep 22, 2016 at 12:04:40PM +0200, Julien Charbon wrote:
> >
> > > >> These paths can indeed compe
On Fri, Sep 23, 2016 at 11:01:43PM +0300, Slawa Olhovchenkov wrote:
> On Wed, Sep 21, 2016 at 11:25:18PM +0200, Julien Charbon wrote:
>
> >
> > Hi Slawa,
> >
> > On 9/21/16 9:51 PM, Slawa Olhovchenkov wrote:
> > > On Wed, Sep 21, 2016 at 09:11:24AM +0200
On Wed, Sep 21, 2016 at 11:25:18PM +0200, Julien Charbon wrote:
>
> Hi Slawa,
>
> On 9/21/16 9:51 PM, Slawa Olhovchenkov wrote:
> > On Wed, Sep 21, 2016 at 09:11:24AM +0200, Julien Charbon wrote:
> >> You can also use Dtrace and lockstat (especially with
On Thu, Sep 22, 2016 at 01:20:45PM +0300, Slawa Olhovchenkov wrote:
> On Thu, Sep 22, 2016 at 12:04:40PM +0200, Julien Charbon wrote:
>
> > >> These paths can indeed compete for the same INP lock, as both
> > >> tcp_tw_2msl_scan() calls always start with the firs
On Thu, Sep 22, 2016 at 04:56:53PM +0500, Eugene M. Zheganin wrote:
> Hi.
>
> I should mention from the start that this is a question about an
> engineering task, not a question about FreeBSD issue.
>
> I have a set of zvol clones that I redistribute over iSCSI. Several
> Windows VMs use these
On Thu, Sep 22, 2016 at 12:04:40PM +0200, Julien Charbon wrote:
> >> These paths can indeed compete for the same INP lock, as both
> >> tcp_tw_2msl_scan() calls always start with the first inp found in
> >> twq_2msl list. But in both cases, this first inp should be quickly used
> >> and its
On Wed, Sep 21, 2016 at 11:25:18PM +0200, Julien Charbon wrote:
>
> Hi Slawa,
>
> On 9/21/16 9:51 PM, Slawa Olhovchenkov wrote:
> > On Wed, Sep 21, 2016 at 09:11:24AM +0200, Julien Charbon wrote:
> >> You can also use Dtrace and lockstat (especially with
On Thu, Sep 22, 2016 at 11:28:38AM +0200, Julien Charbon wrote:
> >>> What purpose to not skip locked tcptw in this loop?
> >>
> >> If I understand your question correctly: According to your pmcstat
> >> result, tcp_tw_2msl_scan() currently struggles with a write lock
> >> (__rw_wlock_hard) and
On Thu, Sep 22, 2016 at 11:53:20AM +0300, Konstantin Belousov wrote:
> On Thu, Sep 22, 2016 at 11:34:24AM +0300, Slawa Olhovchenkov wrote:
> > On Thu, Sep 22, 2016 at 11:27:40AM +0300, Konstantin Belousov wrote:
> >
> > > On Thu, Sep 22, 2016 at 11:25:27AM +0300,
On Thu, Sep 22, 2016 at 11:27:40AM +0300, Konstantin Belousov wrote:
> On Thu, Sep 22, 2016 at 11:25:27AM +0300, Slawa Olhovchenkov wrote:
> > On Thu, Sep 22, 2016 at 10:59:33AM +0300, Konstantin Belousov wrote:
> > > Below is, I believe, the committable fix, o
On Thu, Sep 22, 2016 at 10:59:33AM +0300, Konstantin Belousov wrote:
> On Wed, Sep 21, 2016 at 12:15:17AM +0300, Konstantin Belousov wrote:
> > > > diff --git a/sys/vm/vm_map.c b/sys/vm/vm_map.c
> > > > index a23468e..f754652 100644
> > > > --- a/sys/vm/vm_map.c
> > > > +++ b/sys/vm/vm_map.c
> >
On Wed, Sep 21, 2016 at 09:11:24AM +0200, Julien Charbon wrote:
>
> You can also use Dtrace and lockstat (especially with the lockstat -s
> option):
>
> https://wiki.freebsd.org/DTrace/One-Liners#Kernel_Locks
> https://www.freebsd.org/cgi/man.cgi?query=lockstat=FreeBSD+11.0-RELEASE
>
> But I
On Wed, Sep 21, 2016 at 09:11:24AM +0200, Julien Charbon wrote:
>
> Hi Slawa,
>
> On 9/20/16 10:26 PM, Slawa Olhovchenkov wrote:
> > On Tue, Sep 20, 2016 at 10:00:25PM +0200, Julien Charbon wrote:
> >> On 9/19/16 10:43 PM, Slawa Olhovchenkov wrote:
> >>
On Tue, Sep 20, 2016 at 04:00:10PM -0600, Warner Losh wrote:
> >> > > Is this sandy bridge ?
> >> >
> >> > Sandy Bridge EP
> >> >
> >> > > Show me first 100 lines of the verbose dmesg,
> >> >
> >> > After day or two, after end of this test run -- I am need to enable
> >> > verbose.
> >> >
> >> >
On Wed, Sep 21, 2016 at 12:15:17AM +0300, Konstantin Belousov wrote:
> On Tue, Sep 20, 2016 at 11:38:54PM +0300, Slawa Olhovchenkov wrote:
> > On Tue, Sep 20, 2016 at 11:19:25PM +0300, Konstantin Belousov wrote:
> >
> > > On Tue, Sep 20, 2016 at 10:20:53PM +0300,
On Tue, Sep 20, 2016 at 11:19:25PM +0300, Konstantin Belousov wrote:
> On Tue, Sep 20, 2016 at 10:20:53PM +0300, Slawa Olhovchenkov wrote:
> > On Tue, Sep 20, 2016 at 09:52:44AM +0300, Slawa Olhovchenkov wrote:
> >
> > > On Mon, Sep 19, 2016 at 06:05:46PM -
On Tue, Sep 20, 2016 at 10:00:25PM +0200, Julien Charbon wrote:
>
> Hi Slawa,
>
> On 9/19/16 10:43 PM, Slawa Olhovchenkov wrote:
> > On Mon, Sep 19, 2016 at 10:32:13PM +0200, Julien Charbon wrote:
> >>
> >>> @ CPU_CLK_UNHALTED_CORE [4653445 samples]
&g
On Tue, Sep 20, 2016 at 09:52:44AM +0300, Slawa Olhovchenkov wrote:
> On Mon, Sep 19, 2016 at 06:05:46PM -0700, John Baldwin wrote:
>
> > > > If this panics, then vmspace_switch_aio() is not working for
> > > > some reason.
> > >
> > > I am try us
1 - 100 of 336 matches
Mail list logo
