On Tue, Jan 30, 2018 at 07:54:41AM -0600, Mike Karels wrote:
> > On 30.01.2018 13:59, Andre Albsmeier wrote:
>
> > >> Also, I'd like to know reasons that made you stick to 32 bit OS
> > >> as we have pretty good support for 32 bit applications running under 64
> > >> bit system.
> > >
> > > I (s
On Sun, Dec 31, 2017 at 03:49:13PM +, Gary Palmer wrote:
> On Sun, Dec 31, 2017 at 04:51:47PM +0200, Konstantin Belousov wrote:
> > On Sun, Dec 31, 2017 at 02:17:08PM +, Gary Palmer wrote:
> > >
> > > Hi,
> > >
> > > I recently updated to
On Sun, Dec 31, 2017 at 02:17:08PM +, Gary Palmer wrote:
>
> Hi,
>
> I recently updated to 11.1-RELEASE-p6 and on the most recent reboot
> (after rebuilding all the necessary packages) the clock was running
> slow and NTP wouldn't sync. I looked in /var/log/messages and I found
> that for
On Fri, Dec 22, 2017 at 10:26:07AM +0100, Peter Holm wrote:
> Here's some more info, using the original scenario:
> https://people.freebsd.org/~pho/stress/log/kostik1070.txt
This is somewhat weird but also not too puzzling.
The vmdaemon (pid 41) is running, it tries to reduce the count of residen
On Mon, Dec 11, 2017 at 07:09:31AM +1100, Peter Jeremy wrote:
> I was experimenting with ports/devel/libmill (which is a library that
> provides Go-styly functionality for C programs) and managed to create
> an unkillable process by spawning 100 "goroutines" (think very
> cheap "thread" or "cor
On Fri, Oct 27, 2017 at 04:12:54AM -0700, David Wolfskill wrote:
> This is observed on systems (both my laptop & my build machine) running
> stable/11 @r325003, after updating sources to r325033:
>
> --- libprocstat.o ---
> In file included from /usr/src/lib/libprocstat/libprocstat.c:69:
> /usr/ob
On Thu, Sep 28, 2017 at 01:17:24AM +0200, Hans Petter Selasky wrote:
> Hi,
>
> I just upgraded and hit these SEGFAULTs too. First of all you need to
> install GDB 8.0 from ports to get the right backtrace (important). This
> leads straight into LibUnwind in libgcc:
>
> (gdb) bt
> #0 uw_frame_s
On Fri, Sep 01, 2017 at 06:21:00PM +0300, Paul wrote:
>
> It seems that a lot of CPU resources are spend when trying to get exclusive
> lock on file from multiple processes concurrently. By multiple i mean
> hundreds.
> It seems that there's an initial cost of fcntl() call. Each process that
>
On Tue, Aug 15, 2017 at 04:48:06PM -0400, Mike Tancsa wrote:
> Not sure if this is just me or not, but on a nanobsd i386 image, this
> breaks building the image.
>
> ---Mike
>
> --- all_subdir_geom_journal ---
> --- g_journal.o ---
> /usr/src/sys/modules/geom/geom_journal/../../../geom/jour
On Fri, Aug 04, 2017 at 06:10:48PM -0700, Kevin Oberman wrote:
> multimedia/avidemux_qt4 has started dumping core with segfaults and other
> errors in libthread called from Qt4. I am suspicious that the real problem
> is in Qt4 and those errors were previously not detected and usually not
> causing
On Thu, Jul 27, 2017 at 10:06:53PM +0700, Eugene Grosbein wrote:
> Hi!
>
> Very recently stable/11 got a problem somewhere between r321073 and r321459:
> /bin/sh crashes with SIGSYS at boot time:
>
> Trying to mount root from ufs:/dev/ada0s1a [ro]...
> start_init: trying /sbin/init
> ppid 21 (sh)
On Sat, Jul 22, 2017 at 10:51:42PM -0700, Don Lewis wrote:
> > The stack is aligned to a 4096 (0x1000) boundary. The first access to a
> > local variable below 0xfe085cfa5000 is what triggered the trap. The
> > other end of the stack must be at 0xfe085cfa9000 less a bit. I don't
> > know
On Sat, Jul 22, 2017 at 03:37:30PM +0700, Eugene Grosbein wrote:
> On 22.07.2017 15:00, Konstantin Belousov wrote:
> > On Sat, Jul 22, 2017 at 02:40:59PM +0700, Eugene Grosbein wrote:
> >> Also, I've always wondered what load pattern one should have
> >> to exhibi
On Sat, Jul 22, 2017 at 02:40:59PM +0700, Eugene Grosbein wrote:
> Also, I've always wondered what load pattern one should have
> to exhibit real kernel stack problems due to KVA fragmentation
> and KSTACK_PAGES>2 on i386?
In fact each stack consumes 3 contigous pages because there is also
the guar
On Sat, Jul 22, 2017 at 12:51:01PM +0700, Eugene Grosbein wrote:
> Also, there is https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219476
I strongly disagree with the idea of increasing the default kernel
stack size, it will cause systematic problems for all users instead of
current state where s
On Fri, Jul 21, 2017 at 10:42:42PM -0700, Don Lewis wrote:
> Your best bet for a quick workaround for the stack overflow would be to
> rebuild the kernel with a larger value of KSTACK_PAGES. You can find
> teh default in /usr/src/sys//conf/NOTES.
Or set the tunable kern.kstack_pages to the desired
On Mon, Jul 17, 2017 at 11:54:06AM +0200, Vlad K. wrote:
> Hello list,
>
> the stack_guard hardening option in bsdinstall is now setting 512 pages
> of it in CURRENT, as of r320674. It's said to MFC after 1 day (on Jul
> 5th), but STABLE hasn't got it yet. Is this simply an omission
> (understa
On Fri, Jul 14, 2017 at 02:31:15PM +0500, Eugene M. Zheganin wrote:
> Hi.
>
>
> Is there any chance to mount UDF filesystem under FreeBSD with mdconfig
> and ISO image ? Mount -t cd9660 /dev/md0 /mnt/cdrom gives me the
> readme.txt with "This is UDF, you idiot" and mount -t udf /dev/md0
> /mnt
On Fri, Jul 14, 2017 at 07:28:58PM +1000, Dewayne Geraghty wrote:
> On 14/07/2017 5:56 PM, Konstantin Belousov wrote:
> > On Fri, Jul 14, 2017 at 01:53:40PM +1000, Dewayne Geraghty wrote:
> >> Can someone advise how I can enable extended attributes in a "system"
> &
On Fri, Jul 14, 2017 at 01:53:40PM +1000, Dewayne Geraghty wrote:
> Can someone advise how I can enable extended attributes in a "system"
> namespace within a jailed (or bhyve) environment? There was no guidance
> in "man jail" nor "man jail.conf".
Mentioning jails and bhyve in a single sentence c
On Mon, Jul 10, 2017 at 01:00:05PM -0700, Mark Johnston wrote:
> I suspect that this is a result of r320763. That change removed a field
> from struct vm_map_entry, which is embedded in struct vm_map. Virtualbox
> does not reference the fields of struct vm_map directly, but it does
> call vm_map_pm
On Sun, Jul 09, 2017 at 01:53:24PM +0200, Jan Kokem??ller wrote:
> Same here on -CURRENT r320620. r319481 (I think) was working fine.
>
> I'm using the i386-wine-devel package from the official repository.
This should fix creation of the unkillable processes, but untested.
After that, if wine st
On Wed, Jun 14, 2017 at 11:39:39PM +0700, Eugene Grosbein wrote:
> 14.06.2017 21:12, Konstantin Belousov wrote:
>
> > If the issue is that mpd5 cancels logging thread, and this leaves the
> > mutex in the locked state, the right solution is to establish a cleanup
> > h
On Wed, Jun 14, 2017 at 08:49:36PM +0700, Eugene Grosbein wrote:
> Hi!
>
> Our [v]syslog() implementation in src/lib/libc/gen/syslog.c
> tries to be thread-safe and uses "syslog_mutex".
>
> It may lock this mutex then call blocking system calls like sendto().
> If a thread owning this mutex is pt
On Sun, Jun 11, 2017 at 11:12:25AM -0700, David Wolfskill wrote:
> 2811 rpc.lockd CALL nlm_syscall(0,0x1e,0x4,0x801015040)
> 2811 rpc.lockd RET nlm_syscall -1 errno 14 Bad address
If you revert r319614 on stable/11, does the problem go away ?
___
On Wed, May 10, 2017 at 03:29:39PM -0700, Olivier Cinquin wrote:
> Hi,
> I'm getting the following kernel panics on recent 11-STABLE (r317883):
>
> spin lock 0x81df43d0 (smp rendezvous) held by 0xf8019c7a7000 (tid
> 100845) too long
> timeout stopping cpus
> panic: spin lock held too
On Sat, Apr 29, 2017 at 07:55:24PM +0200, Dimitry Andric wrote:
> On 29 Apr 2017, at 19:00, Gerald Pfeifer wrote:
> >
> > On Thu, 27 Apr 2017, Jung-uk Kim wrote:
> >>> I found the problem, but I do not know how to resolve this. When you
> >>> install the GCC compiler from the PKG reposi
On Tue, Apr 18, 2017 at 01:28:33PM +0500, Eugene M. Zheganin wrote:
> Hi,
>
>
> I need to install FreBSD on an Intel system with s5000pal mainboard. The
> problem is, that on the kernel loading stage, FreeBSD reboots the
> server. Like, always and silently, without trapping. I have plugged out
On Thu, Mar 09, 2017 at 10:49:01PM +, Rick Macklem wrote:
> Konstantin Belousov wrote:
> > I did not touched unionfs, and have no plans to. It is equally broken in
> > all relevant versions of FreeBSD.
> Heh, heh. I chuckled when I read this. I think he's trying to s
all relevant versions of FreeBSD.
>
> rick
>
> From: Harry Schmalzbauer
> Sent: Tuesday, March 7, 2017 2:45:40 PM
> To: Rick Macklem
> Cc: Konstantin Belousov; FreeBSD Stable; Mark Johnston; k...@freebsd.org
> Subject: Re: unionfs
On Wed, Feb 01, 2017 at 04:05:41PM +, hartmut.bra...@dlr.de wrote:
> The problem is not the memory but the 2GB process limit.
Did you configured PAE ? Normal (non-PAE) kernels with default configuration
of U/K split provide 3G to userspace.
On amd64 kernel running 32bit processes, you get 4G
On Wed, Feb 01, 2017 at 07:16:28AM -0700, Jakub Lach wrote:
> I'm not sure if it's the same thing. Most of the times the corruption was
> silent
> then.
>
> Nonetheless, the outcome was the same after newfs HDD with UFS2-
>
> http://www.pastebin.ca/3762661
>
> I would 'blame' USB now, if only I
On Wed, Feb 01, 2017 at 06:02:45AM -0700, Jakub Lach wrote:
> Yes, it has happened also with another device. Which was not a card reader
> (HDD
> mounted by USB), and I have used the same card reader configuration to copy
> the memory card content with iMac.
Is your card reader USB-attached, sam
On Wed, Feb 01, 2017 at 05:38:07AM -0700, Jakub Lach wrote:
> As it shows your interest, I appreciate your answer very much.
>
> I was a bit let down then, I had to (using the same card reader),
> cp -r using borrowed Apple iMac. It worked as it should.
>
> It was FreeBSD 11.0-STABLE #0 r310265
On Sun, Dec 04, 2016 at 04:23:00PM +0300, Andrey Chernov wrote:
> It seems counter.h is included before systm.h where critical_* are declared.
It is more weird, since sys/counter.h was added in the stable/10
merge, but the header is not used in the HEAD sources. It is indeed
needed for stable/10 dr
On Tue, Nov 29, 2016 at 12:32:28PM +1100, Dewayne Geraghty wrote:
> Is WITHOUT_SSP actually honoured and is building a world and/or ports
> without SSP possible? Advise/suggestions appreciated.
>
> Amongst the 9 different server configurations that we build/support, we've
> been asked to build a m
On Sat, Nov 26, 2016 at 02:37:45PM -0800, Jason Harmening wrote:
> I can confirm this patch works. HPET is now chosen over LAPIC as the
> eventtimer source, and the system works smoothly without disabling C2 or
> mwait.
Thank you for the testing.
The change was committed to HEAD as r309189.
On Wed, Nov 02, 2016 at 06:28:08PM +0200, Konstantin Belousov wrote:
> On Wed, Nov 02, 2016 at 09:18:15AM -0700, Jason Harmening wrote:
> > I think you are probably right. Hacking out the Intel-specific
> > additions to C-state parsing in acpi_cpu_cx_cst() from r282678 (thus
> &
On Tue, Nov 15, 2016 at 10:59:57AM -0500, George Mitchell wrote:
> ... is a topic I just marginally understand. But pkg 1.9.3 fails
> on FreeBSD 10.1-RELEASE-p35 because /lib/libc.so.7 contains no
> definition for "openat", though /lib/libc.so.7 on 10.3-RELEASE-p11
> does define it. I confess to
On Wed, Nov 02, 2016 at 09:18:15AM -0700, Jason Harmening wrote:
> I think you are probably right. Hacking out the Intel-specific
> additions to C-state parsing in acpi_cpu_cx_cst() from r282678 (thus
> going back to sti;hlt instead of monitor+mwait at C1) fixed the problem
> for me. But r282678
On Tue, Nov 01, 2016 at 02:29:13PM -0700, Jason Harmening wrote:
> repro code is at http://pastebin.com/B68N4AFY if anyone's interested.
>
> On 11/01/16 13:58, Jason Harmening wrote:
> > Hi everyone,
> >
> > I recently upgraded my main amd64 server from 10.3-stable (r302011) to
> > 11.0-stable (r
On Fri, Oct 07, 2016 at 08:32:24AM +1000, Andy Farkas wrote:
> With your latest patch applied, I ran through my procedure more
> than a dozen times and no panics!
>
> Any explanation why sleep(STALL_TIMEOUT) as apposed to a
> bunch of sleep(1)'s tickles the panic?
What happened was sleep() got int
On Thu, Oct 06, 2016 at 06:31:59PM +1000, Andy Farkas wrote:
> Reverted your patch then changed line 1011 of init.c to _exit(97):
>
> --- init.c-orig 2016-10-05 18:52:24.02291 +1000
> +++ init.c 2016-10-06 17:02:33.714624000 +1000
> @@ -1008,7 +1008,7 @@
> */
> warning("single user shell t
On Wed, Oct 05, 2016 at 07:32:33PM +1000, Andy Farkas wrote:
> On 05/10/2016 18:43, Konstantin Belousov wrote:
>
> > Apply the following patch. I am interested if anything additional appear
> > on the console. Screenshot is good enough.
>
> Patch applied. Panic (
On Wed, Oct 05, 2016 at 05:32:18AM +1000, Andy Farkas wrote:
> On 04/10/2016 23:11, Andy Farkas wrote:
> > On 04/10/2016 21:24, Konstantin Belousov wrote:
> >> On Tue, Oct 04, 2016 at 11:14:38AM +1000, Andy Farkas wrote:
> >>> Is it just me or
> >>>
On Tue, Oct 04, 2016 at 11:14:38AM +1000, Andy Farkas wrote:
> Is it just me or
>
> Step 1: boot
> Step 2: login as root
> Step 3: type "w" *
> Step 4: type "shutdown now; logout"
> Step 5: press at the 'Enter full pathname of shell or RETURN for
> /bin/sh:' prompt
> Step 6: type "reboot"
> S
On Mon, Oct 03, 2016 at 04:29:01AM -0700, David Wolfskill wrote:
> This is for a src-based in-place upgrade of stable/11 (amd64) from
> r306576 to r306629; both my laptop and build machine show errors,
> starting with:
>
> ...
> >>> stage 4.3: building everything
> ...
> --- all_subdir_usr.bin ---
On Thu, Sep 22, 2016 at 12:33:55PM +0300, Slawa Olhovchenkov wrote:
> OK, try this patch.
Was the patch tested ?
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freeb
On Thu, Sep 22, 2016 at 12:33:55PM +0300, Slawa Olhovchenkov wrote:
> Do you still need first 100 lines from verbose boot?
No.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any m
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, Slawa Olhovchenkov wrote:
> > > On Thu, Sep 22, 2016 at 10:59:33AM +0300, Kons
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, of course supposing that
> > the patch above worked. If you want to retest it on stable/11, ign
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
> > > @@ -481,6 +481,7 @@ vmspace
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, Slawa Olhovchenkov wrote:
> > > On Tue, Sep 20, 2016 at 09:52:44AM +0300, Sla
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 -0700, John Baldwin wrote:
> >
> > > > > If this panics, then vmspace_switch_aio() is not working for
> > > > > some r
On Thu, Sep 15, 2016 at 11:54:12AM -0700, John Baldwin wrote:
> On Thursday, September 15, 2016 08:49:48 PM Slawa Olhovchenkov wrote:
> > On Thu, Sep 15, 2016 at 10:28:11AM -0700, John Baldwin wrote:
> >
> > > On Thursday, September 15, 2016 05:41:03 PM Slawa Olhovchenkov wrote:
> > > > On Wed, Se
On Thu, Sep 15, 2016 at 12:35:04AM +0300, Slawa Olhovchenkov wrote:
> On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote:
>
> > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote:
> > > I am try using 11.0 on Dual E5-2620 (no X2APIC).
> > > Under high network load and may be addtional c
On Wed, Sep 14, 2016 at 05:02:21PM +0300, Andriy Gapon wrote:
> On 14/09/2016 15:49, Slawa Olhovchenkov wrote:
> > MSR_APICBASE = 0xfee00d00
> > x2APIC is prohibited but turned on by BIOS
>
> Kostik, ^
Well, the following might work, but I have no good idea what to do
when BIOS does h
On Tue, Sep 13, 2016 at 06:52:19PM +0300, Andriy Gapon wrote:
> On 13/09/2016 18:22, Konstantin Belousov wrote:
> > Any access
> > to the LAPIC registers page in x2APIC mode faults.
>
> Is this a fact?
> I read the following in the specification:
>
> In x2APIC mod
On Tue, Sep 13, 2016 at 05:54:26PM +0300, Andriy Gapon wrote:
> On 13/09/2016 17:21, Slawa Olhovchenkov wrote:
> > boot failed:
> >
> > set hw.x2apic_enable=0
> > loading required module 'krpc'
> > /boot/kernel.VSTREAM/krpc.ko size 0x2a210 at 0x134e000
> > loading required module 'opensolaris'
> >
On Tue, Sep 06, 2016 at 04:13:05PM +0300, Slawa Olhovchenkov wrote:
> On Sun, Sep 04, 2016 at 11:19:16AM +0300, Andriy Gapon wrote:
>
> > On 01/09/2016 15:13, Slawa Olhovchenkov wrote:
> > > DMAR: Found table at 0x79b32798
> > > x2APIC available but disabled by DMAR table
> >
> > > Event timer "L
On Mon, Sep 05, 2016 at 02:26:30PM -0600, Alan Somers wrote:
> Just to get your webserver out of the picture, could you please try
> running the aio test suite on an NFS share? Do it like this:
> $ cd /usr/tests/sys/aio
> $ export TMPFS=/path/to/some/nfs/share
> $ kyua test
By default, unsafe aio
On Sun, Sep 04, 2016 at 06:49:43PM +0300, Andriy Gapon wrote:
> On 04/09/2016 18:14, Konstantin Belousov wrote:
> > On Sun, Sep 04, 2016 at 11:19:16AM +0300, Andriy Gapon wrote:
> >> Kostik, I see one strange thing which is common to both successful and
> >> unsuccessfu
On Sun, Sep 04, 2016 at 11:19:16AM +0300, Andriy Gapon wrote:
> On 01/09/2016 15:13, Slawa Olhovchenkov wrote:
> > DMAR: Found table at 0x79b32798
> > x2APIC available but disabled by DMAR table
>
> > Event timer "LAPIC" quality 600
> > LAPIC: ipi_wait() us multiplier 1 (r 116268019 tsc 2200043851
On Sun, Sep 04, 2016 at 04:11:39PM +0300, Andriy Gapon wrote:
> On 04/09/2016 11:24, Andriy Gapon wrote:
> > On 27/08/2016 22:09, Frederic Chardon wrote:
> >>> Anybody is able to reproduce this behavior or is it a local problem?
> >> Reverting 303970 solves this issue. gcore and adb works again, an
On Thu, Sep 01, 2016 at 09:00:14PM +0300, Slawa Olhovchenkov wrote:
> Sorry, don't cleanly understund, what combination of BIOS setting I am need
> to probe?
> And what I am need to check?
Set 'Hyper-Threading' to Enabled.
Set 'X2APIC_OPT_OUT' to Enabled.
Try to boot.
On Thu, Sep 01, 2016 at 08:31:49PM +0300, Slawa Olhovchenkov wrote:
> On Thu, Sep 01, 2016 at 08:26:32PM +0300, Konstantin Belousov wrote:
>
> > On Thu, Sep 01, 2016 at 03:13:00PM +0300, Slawa Olhovchenkov wrote:
> > > On Thu, Sep 01, 2016 at 02:45:00PM +0300, Konstantin Bel
On Thu, Sep 01, 2016 at 03:13:00PM +0300, Slawa Olhovchenkov wrote:
> On Thu, Sep 01, 2016 at 02:45:00PM +0300, Konstantin Belousov wrote:
> As I point before: 'X2APIC_OPT_OUT Flag'.
> Hidden before 'X2APIC' set to '[Enable]'
>
> https://s15.postimg.o
On Thu, Sep 01, 2016 at 02:27:24PM +0300, Slawa Olhovchenkov wrote:
> On Sat, Dec 12, 2015 at 03:35:13PM +0200, Konstantin Belousov wrote:
>
> > On Sat, Dec 12, 2015 at 04:06:15PM +0300, Slawa Olhovchenkov wrote:
> > > Does STABLE support X2APIC?
> > > I see X2A
On Tue, Aug 23, 2016 at 09:27:56AM +0200, Frederic Chardon wrote:
> Le 20 ao??t 2016 22:03, "Frederic Chardon" a
> ??crit :
> >
> > Hi
> >
> > I see a strange interaction between zfs on root and kern.proc.pathname
> > on my laptop. Whenever I try to use gcore it fails with:
> > gcore 1023
> > gcor
On Thu, Aug 18, 2016 at 12:03:33AM +, Rick Macklem wrote:
> Kostik wrote:
> [stuff snipped]
> >insmnque() performs the cleanup on its own, and that default cleanup isnot
> >suitable >for the situation. I think that insmntque1() would betterfit your
> >requirements, your >need to move the co
On Thu, Aug 11, 2016 at 10:53:03PM +, Rick Macklem wrote:
> Harry Schmalzbauer wrote:
> Bez??glich Mark Johnston's Nachricht vom 09.08.2016 08:02 (localtime):
> ???
> >>
> >> Just for anybody else needing unionfs:
> >> https://people.freebsd.org/~attilio/unionfs_missing_insmntque_lock.patch
> >
On Wed, Aug 10, 2016 at 06:11:39PM +0300, Dmitry Sivachenko wrote:
>
> > On 10 Aug 2016, at 17:55, Konstantin Belousov wrote:
> >
> > On Wed, Aug 10, 2016 at 05:29:31PM +0300, Dmitry Sivachenko wrote:
> >> Hello,
> >>
> >> I am running FreeBSD
On Wed, Aug 10, 2016 at 05:29:31PM +0300, Dmitry Sivachenko wrote:
> Hello,
>
> I am running FreeBSD 10.3-STABLE #0 r299261M
>
> After unclean reboot I am unable to fsck my UFS filesystem:
>
> # fsck /dev/mfid0p1
> ** /dev/mfid0p1
> ** Last Mounted on /opt
> ** Phase 1 - Check Blocks and Sizes
On Tue, Aug 02, 2016 at 01:57:49PM -0600, Ian Lepore wrote:
> On Tue, 2016-08-02 at 22:25 +0300, Konstantin Belousov wrote:
> > Below is the merge of some high-profile virtual memory subsystem bug
> > fixes from stable/10 to 10.3.
> I run 10-stable on my everyday desktop/bui
On Tue, Aug 02, 2016 at 12:47:23PM -0700, pete wright wrote:
> On Aug 2, 2016 12:26 PM, "Konstantin Belousov" wrote:
> >
> > Below is the merge of some high-profile virtual memory subsystem bug
> > fixes from stable/10 to 10.3. I merged fixes for bugs reported by
&
Below is the merge of some high-profile virtual memory subsystem bug
fixes from stable/10 to 10.3. I merged fixes for bugs reported by
users, issues which are even theoretically unlikely to occur in real
world loads, are not included into the patch set. The later is mostly
corrections for the handl
On Thu, Jul 28, 2016 at 12:38:51PM +0200, Johan Hendriks wrote:
> Hello all.
>
> Lately I noticed above (error) when I reboot machine.
>
> It looks like this.
>
> Stopping cron.
> Waiting for PIDS: 1183
> swapoff: /dev/gpt/swap-9M286954: Cannot allocate memory
> stopping zfsd.
> Waiti..
>
>
On Wed, Jul 06, 2016 at 02:21:20PM -0400, David Cross wrote:
> (kgdb) up 5
> #5 0x804aafa1 in brelse (bp=0xfe00f77457d0) at buf.h:428
> 428 (*bioops.io_deallocate)(bp);
> Current language: auto; currently minimal
> (kgdb) p/x *(struct buf *)0xfe00f77457d0
> $1
On Wed, Jul 06, 2016 at 12:02:00PM -0400, David Cross wrote:
> Oh, whoops; how do I printout the buffer?
In kgdb, p/x *(struct buf *)address
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscr
On Wed, Jul 06, 2016 at 10:51:28AM -0400, David Cross wrote:
> Ok.. to reply to my own message, I using ktr and debugging printfs I have
> found the culprit.. but I am still at a loss to 'why', or what the
> appropriate fix is.
>
> Lets go back to the panic (simplified)
>
> #0 0x8043f160
On Mon, Jul 04, 2016 at 10:26:25PM -0700, Maxim Sobolev wrote:
> Hi all, investigating some random postgresql-9.1.21 server crashes on
> FreeBSD 10.3, we've started seeing those after upgrading from postgres
> 9.1.18 on more than one system, so hardware (e.g. RAM issues) are very
> unlikely. I susp
On Thu, Jun 30, 2016 at 01:57:32PM +0200, Patrick Lamaiziere wrote:
> Hello,
>
> I'm building a pair of firewall with 10.3 and I see some rare
> segmentation faults (5 in a week) in processes like wc, sh or ifstated.
>
> wc, sh are used by some scripts who check the state of the interfaces
> and
On Mon, Mar 28, 2016 at 08:52:03AM -0700, Maxim Sobolev wrote:
> Done some head scratching, it looks like it's got page fault in the
> copyin() (cp(1) AFAIK mmaps source file). There might be some interlock
> issue between competing write to the same ZFS, the md0 device is locked
> forever waiting
On Sat, Mar 05, 2016 at 07:42:51PM +0300, Dmitry Sivachenko wrote:
>
> > On 05 Mar 2016, at 19:27, Konstantin Belousov wrote:
> >
> > On Sat, Mar 05, 2016 at 05:24:26PM +0300, Dmitry Sivachenko wrote:
> >>>
> >>> Again, error 4 is EIN
On Sat, Mar 05, 2016 at 05:24:26PM +0300, Dmitry Sivachenko wrote:
> >
> > Again, error 4 is EINTR so you could disable both "soft" and "intr" options
> > for test.
>
>
> "soft" is meaningless in such setup, because "file system calls will fail
> after retrycnt round trip timeout intervals" bu
On Wed, Mar 02, 2016 at 03:02:02AM -0800, Maxim Sobolev wrote:
> Thanks, Konstantin.
>
> Re: md(4) state:
>
>0 88688 0 0 -8 0 0 16 tx->tx_s DL- 0:45.43
> [md0]
>
> Its backtrace:
So md is stuck in ZFS.
___
freebsd-stabl
On Wed, Mar 02, 2016 at 01:12:31AM -0800, Maxim Sobolev wrote:
> Hi, I've encountered cp(1) process stuck in the vnread state on one of my
> build machines that got recently upgraded to 10.3.
>
>0 79596 1 0 20 0 170921396 wait I 1 0:00.00
> /bin/sh /usr/local/bin/au
On Wed, Feb 24, 2016 at 02:26:19PM +1000, Paul Koch wrote:
>
> Occasionally we see a process get stuck in an unkillable state and
> the only solution is a hard reboot.
>
> Occasionally == once every two weeks across 60+ servers, which are spread
> across the globe in customer sites. We have no r
On Sun, Feb 14, 2016 at 09:42:24PM +, Mark Dixon wrote:
> Konstantin Belousov gmail.com> writes:
>
>
> > On Sat, Feb 13, 2016 at 03:46:16PM +, Mark Dixon wrote:
> > Might be, try the following (mostly debugging) change.
> >
>
> Tried it, the onl
On Sat, Feb 13, 2016 at 03:46:16PM +, Mark Dixon wrote:
> I don't think I can clock it down, although the UEFI bios screens are
> massively confusing so I could be wrong.
>
> Verbose dmesg:
Might be, try the following (mostly debugging) change.
diff --git a/sys/boot/i386/libi386/time.c b/sys
On Fri, Feb 12, 2016 at 09:15:49PM +, Mark Dixon wrote:
> > Can you put a dmesg.boot from the server ? An pciconf -lvb ?
> >
>
> I have the exact same issue on the forum, so I can:
As a blind shot, try to lower the CPU frequency in the BIOS, to 3 or even
to 2 Ghz. If you can try a dos (real
On Sat, Feb 06, 2016 at 11:40:50PM +0900, Hajimu UMEMOTO wrote:
> Hi,
>
> >>>>> On Tue, 2 Feb 2016 14:52:37 +0200
> >>>>> Konstantin Belousov said:
>
> kostikbel> Please gather the information listed at
> kostikbel>
> https://w
On Tue, Feb 02, 2016 at 02:33:27PM +0100, Henrik Lidstr??m wrote:
> Just want to chip in that I also experience the same issue. This is my
The same ? So did you diagnosed the problem and can explain, from the
evidence provided by you and Hajimu, what is the cause and why the
issues are the same ?
On Tue, Feb 02, 2016 at 06:28:58PM +0900, Hajimu UMEMOTO wrote:
> Hi,
>
> > On Tue, 2 Feb 2016 08:54:17 +
> > Steven Hartland said:
>
> killing> Some more information about your enviroment would be helpful:
> killing> 1. What revision of stable/10 are you running?
>
> It occurs on r
On Sat, Dec 12, 2015 at 04:06:15PM +0300, Slawa Olhovchenkov wrote:
> Does STABLE support X2APIC?
> I see X2APIC related commits in CURRENT, what is status for STABLE?
> I am try to enable X2APIC support on X10DRi and see kernel trap on
> boot.
x2APIC is only supported in HEAD. The code to parse
the exiting process) is possible, but is
somewhat questionable.
>
> Regards,
> Gavin Mu
>
>
> ------ Original --
> From: "Gavin Mu";;
> Date: Sun, Dec 6, 2015 08:14 AM
> To: "Konstantin Belousov";
> Cc: "freebsd-stable";
>
ES keeps increasing to
> 1GB. From my testing, if the memory is allocated by malloc(), then RES will
> keep increasing in both 7.0 and 10.1. only sysv_shm in 7.0 has different
> behavior. I have checked coredump() code but did not find any clue why it is
> different.
>
>
On Fri, Dec 04, 2015 at 09:35:54AM +0800, Gavin Mu wrote:
> Hi,
>
> We have an application running on old FreeBSD 7.0, and we are upgrading the
> base system to FreeBSD 10.1. The application uses sysv_shm, and will allocate
> a lot of share memory, though most of time only a part of the allocate
On Wed, Oct 14, 2015 at 03:52:47PM +0200, Frank Razenberg wrote:
> After upgrading from 9.2 to 10.1 I first started noticing panics. They
> occurred roughly weekly and since this storage machine isn't frequently
> used I didn't look into it much further. After updating for 10.2-STABLE
> the pani
On Tue, Oct 06, 2015 at 01:38:28PM +0100, krad wrote:
> Sorry but it appears I dont have the core so am not able to match it up.
> Mostly likely another will happen later today though as ive now fixed
> dumpdev on the box
You do not need core to get the line number.
kgdb kernel.debug
list *functio
101 - 200 of 395 matches
Mail list logo
