hese I had
>>> last night would have added up to 135, and that worked
>>>
>>> --
>>> Thanks,
>>> Dean E. Weimer
>>> http://www.dweimer.net/
>>>
>>
>>
>> This may be related:
>>
>> http://iocage.readthedocs.io/en/latest/known-issues.html#cha
>> racter-mount-path-limitation
>>
>> Priyadarshan
>>
>
>
Having run into this before in nfs exports , and pulling my hair out; I ran
into this fix . I know its from a long time ago; but I am willing to put up
a bounty to get this bumped to 512
http://www.secnetix.de/olli/FreeBSD/mnamelen.hawk
> Thanks, that's probably it, the original snapshot name with its full data
> set path added up to 89, with that in mind I can edit my script to throw a
> warning if this limit is hit so that my backup logs will let me know if a
> data set gets missed. I need to edit it anyways so that a warning gets
> logged on the mount failure which was already occurring. It looks like I
> escaped the errors, so that the script returned successful and didn't make
> the Bacula backup job fail so that the data that did get mounted would be
> backed up, but forgot to write the error to the log.
>
> --
> Thanks,
>Dean E. Weimer
>http://www.dweimer.net/
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
--
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
my cross builds. I've no head (CURRENT)
activities going on at this point.
===
Mark Millard
markmi at dsl-only.net
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
means though.
Regards,
Mark
signature.asc
Description: This is a digitally signed message part
On Thu, Oct 6, 2016 at 5:39 AM, Mark Dixon wrote:
> If I load the module on my laptop (Lenovo Thinkpad X1 Carbon), I get:
>
> iicsmb0: on iicbus0
> iicsmb1: on iicbus1
> iicsmb2: on iicbus2
> iicsmb3: on iicbus3
> iicsmb4: on iicbus4
> iicsmb5: on iicbus5
> iic
tient, or is the update.FreeBSD.org hosed?
Mark
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Whatever you did, it started to work now normally. Thank you!
(no changes at our side)
Mark
2016-10-12 16:29, Mark Martinec wrote:
Trying to upgrade a couple of hosts (11.0-RC2, 11.0-RC3,
10.3-RELEASE-p10)
to 11.0 (using: freebsd-update upgrade -r 11.0-RELEASE), and it seems
the fetch(1
Perhaps it's time to replace Apache httpd/2.2.16 (released 6+ years ago)
running on update.FreeBSD.org with something lighter and more agile
like nginx (or at least with a fresher version of Apache httpd).
The accf_http(9) (with: accept_filter=httpready) may help too.
Mark
2016-10-12
On Fri, Oct 21, 2016 at 10:14:26AM +0200, Andrea Venturoli wrote:
> I've tried this way, but altough I'm quite proficient with [k]gdb I tend to
> get lost in FreeBSD's kernel's source code, which, unfortunately, I'm not
> familiar with.
>
> BTW, I had read that book years ago; I searched for it no
PU
> dev.cpu.1.%parent: cpulist0
> dev.cpu.1.%location:
> dev.cpu.1.%driver: cpu
> dev.cpu.1.%desc: Open Firmware CPU
> dev.cpu.0.%parent: cpulist0
> dev.cpu.0.%pnpinfo: name=cpu@0 compat=arm,cortex-a7
> dev.cpu.0.%location:
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%desc: Open Firmware CPU
> dev.cpu.0.%parent: cpulist0
> dev.cpulist.0.%parent: ofwbus0
> dev.cpulist.0.%pnpinfo: name=cpus
> dev.cpulist.0.%location:
> dev.cpulist.0.%driver: cpulist
> dev.cpulist.0.%desc: Open Firmware CPU Group
> dev.cpulist.%parent:
> dev.aw_cpusclk.0.%parent: aw_ccu0
> dev.aw_cpusclk.0.%pnpinfo: name=clk@01f0140inner,sun8i-a83t-cpus-clk
> dev.aw_cpusclk.0.%location:
> dev.aw_cpusclk.0.%driver: aw_cpusclk
> dev.aw_cpusclk.0.%desc: Allwinner CPUS Clock
> dev.aw_cpusclk.%parent:
> security.jail.param.cpuset.id: 0
===
Mark Millard
markmi at dsl-only.net
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
dling power and heat issues).
> On Mon, 24 Oct 2016 15:42:40 -0700
> Mark Millard wrote:
>
>> On 2016-Oct-24, at 2:00 PM, Emmanuel Vadot wrote:
>>
>>
>>> Hello Mark,
>>>
>>> The A83T is BIG/Little IIRC and we don't support that. That's
On 2016-Oct-24, at 2:00 PM, Emmanuel Vadot wrote:
> Hello Mark,
>
> The A83T is BIG/Little IIRC and we don't support that. That's why you
> only see 4 cores on the 8.
That is not what I get from reading the A83T documentation. All the CPU
references are to the same t
BSD bananapi-m3 11.0-STABLE FreeBSD 11.0-STABLE #0 r307797M: Mon Oct 24
00:41:16 PDT 2016
markmi@FreeBSDx64:/usr/local/src/crochet/work/obj/arm.armv6/usr/src/sys/ALLWINNER
arm armv6 1100505 1100505
===
Mark Millard
markmi at dsl-only.net
__
BSD bananapi-m3 11.0-STABLE FreeBSD 11.0-STABLE #0 r307797M: Mon Oct 24
00:41:16 PDT 2016
markmi@FreeBSDx64:/usr/local/src/crochet/work/obj/arm.armv6/usr/src/sys/ALLWINNER
arm armv6 1100505 1100505
===
Mark Millard
markmi at dsl-only.net
__
1 root wheel 0 Oct 25 16:57 libgcc2.s
-rw-r--r-- 1 root wheel108880 Oct 25 16:57 libgcc2.i
-rw-r--r-- 1 root wheel 7636 Oct 25 16:57 _muldi3.dep
-rw-r--r-- 1 root wheel 560 Oct 25 10:16 _ucmpdi2.o
-rw-r--r-- 1 root wheel 560 Oct 25 10:16 _cmpdi2.o
-rw-r--r-- 1
0
34699 as CALL close(0)
34699 as RET close 0
-25840 in 2's complement is: 0xF...F9B10
Here doing the gdb truss instead reports:
(gdb) print t->cs.number
$1 = 580819728
and 580819728 = 0x229E9B10
and the 229E part matches several PFLT's in the area, including just bef
specific to FreeBSD:
https://www.virtualbox.org/ticket/16084
Mark
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On 2016-Oct-28, at 7:29 AM, John Baldwin wrote:
> On Tuesday, October 25, 2016 11:40:38 AM Mark Millard wrote:
>> [The following has been reported in:
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213778 .]
>>
>> In trying to build lang/gcc6 xgcc's
On 2016-Oct-28, at 4:02 PM, Mark Millard wrote:
> On 2016-Oct-28, at 7:29 AM, John Baldwin wrote:
>
>> On Tuesday, October 25, 2016 11:40:38 AM Mark Millard wrote:
>>> [The following has been reported in:
>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=2
[I re-established the crotchet-build based failure context finally.
Unfortunately truss just dies in a new place.]
On 2016-Oct-28, at 7:29 AM, John Baldwin wrote:
> On Tuesday, October 25, 2016 11:40:38 AM Mark Millard wrote:
>> [The following has been reported in:
>> https://b
t;/usr/obj/rpi2_clang" \
make $*
# more ~/src.configs/src.conf.rpi2-clang-bootstrap.amd64-host
TO_TYPE=armv6
#
KERNCONF=RPI2-NODBG
TARGET=arm
.if ${.MAKE.LEVEL} == 0
TARGET_ARCH=${TO_TYPE}
.export TARGET_ARCH
.endif
#
WITH_CROSS_COMPILER=
WITHOUT_SYSTEM_COMPILER=
#
#CPUTYPE=soft
g make buildkernel
completed the rest of the build just fine, creating the previously-missing file
before trying to use it.
===
Mark Millard
markmi at dsl-only.net
On 2016-Nov-2, at 3:13 AM, Mark Millard wrote:
> Lack of dependency? Race? (I've not isolated why this happened y
y checks of internal
structures, required by INVARIANTS
nooptions WITNESS # Enable checks to detect deadlocks and
cycles
nooptions WITNESS_SKIPSPIN# Don't run witness on spinlocks for
speed
nooptions DIAGNOSTIC
nooptions MALLOC_DEBUG_MAXZONES #
able/11 context to head (12-CURRENT).
If this is intentional then I think the man src.conf references and such should
be explicit about the /etc/make.conf vs. /etc/src.conf distinction for
__MAKE_CONF= vs. SRC_ENV_CONF= .
===
Mark Millard
markmi at dsl-only.net
___
only
For regrexp for example one should use the classes: :upper: or :lower:.
It is a good idea to keep LC_COLLATE and LC_NUMERIC (and LC_MONETARY?)
at "C"
when LANG or LC_CTYPE is set to something else, otherwise unexpected
things may happen.
Mark
On Sat, Nov 05, 2016 at 08:23:
[The original of this message was not delivered to two of the places it was
sent to. This retries sending to just those places.]
On 2016-Nov-4, at 9:40 AM, Bryan Drewery wrote:
> On 11/3/2016 5:28 PM, Mark Millard wrote:
>> I just had a case of "odd" command text in a buildw
et/work/obj/arm64.aarch64/usr/src/sys/GENERIC-NODBG
> arm64 aarch64 1200014 1200014
> # svnlite info /usr/ports | grep "Re[lv]"
> Relative URL: ^/head
> Revision: 424540
> Last Changed Rev: 424540
===
Mark Millard
markmi at dsl-only.net
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
. The LANG sets a default, but the
LC_COLLATE, LC_TIME, LC_NUMERIC and LC_MONETARY should better
be set to "C" to overrule the LANG in their domains.
Leave the LC_ALL undefined or empty, as this one overrules
every other locale setting (unless you really want everything
to be set to &qu
On 2016-Nov-7, at 1:16 PM, Brad Davis wrote:
> On Mon, Nov 07, 2016 at 12:19:24PM -0800, Mark Millard wrote:
>> It looks like http://pkg.freebsd.org is still back as of head being
>> 11-CURRENT: http://pkg.freebsd.org shows only
>
> Correct. I wrote up some details
h: 2979 byte(s)
> Diff to previous 305419
> Add generic device-tree cpufreq driver.
Such things might determine if I stick with stable/11 vs. switch to head for
a BPi-M3.
===
Mark Millard
markmi at dsl-only.net
___
freebsd-stable@freebsd.or
h: 2979 byte(s)
> Diff to previous 305419
> Add generic device-tree cpufreq driver.
Such things might determine if I stick with stable/11 vs. switch to head for
a BPi-M3.
===
Mark Millard
markmi at dsl-only.net
___
freebsd-stable@freebsd.or
On 2016-Nov-2, at 12:16 PM, Mark Millard wrote:
> Quick top post reporting that a build-order-race for -j use seems likely: the
> clean-then-build sequence
>
>> Command: env __MAKE_CONF=/root/src.configs/make.conf
>> SRC_ENV_CONF=/root/src.configs/src.conf.rpi2-clang
able@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
--
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
l the case in FreeBSD 11.0 ???
I remember hearing rumors that the System V namespace
no longer is (will?) be shared across jails.
(Couldn't find it being mentioned in release notes.)
Mark
___
freebsd-stable@freebsd.org mailing list
https://lists.f
; xxx
ERROR: Unsupported property: sysvmsg!
I guess I should file a bug report.
Mark
man 8 jail
...
allow.sysvipc
A process within the jail has access to System V IPC
primitives. This is deprecated in favor of the per-
module parameters (see below). When this paramete
eason it hasn't been merged is
because it can't (yet) be made to work correctly on the develop branch
of iocage. But it works fine on the master branch.
https://github.com/iocage/iocage/pull/370
-Alan
Superb, appreciated!
Mark
On Tue, Dec 13, 2016 at 8:08 AM, Mark Martinec
wrote
On Thu, Dec 29, 2016 at 12:04:56PM +0100, Trond Endrestøl wrote:
> I keep getting these warnings whenever I run svn, perl, and other
> programs.
>
> WARNING: number of probes fixed does not match the number of defined probes
> (16 != 18, respectively)
> WARNING: some probes might not fire or you
On Sat, Jan 14, 2017 at 02:21:23AM +0700, Eugene Grosbein wrote:
> Hi!
>
> I'm struggling to debug a panic in 11.0-STABLE/i386 that successfully
> produces crashdump
> but I want more information. So I've rebuilt my custom kernel to include
> options INVARIANTS, WITNESS and DEADLKRES. Now any pan
Poudriere still reports success for these builds.
The host where poudriere is running does not have linux.ko loaded.
Does building such packages really require linuxilator configured
on the build host ???
Mark
[00:23:56] >> [02][00:00:00] Starting build of
www/linux-c6-qt47-webkit
[00:
On Sat, Jan 14, 2017 at 06:40:02PM +0700, Eugene Grosbein wrote:
>
> > I suspect that this is because we only stop the scheduler upon a panic
> > if SMP is configured. Can you retest with the patch below applied?
> >
> > Index: sys/kern/kern_shutdown.c
> >
amp;& needfs="${needfs} tmpfs"
Great, that seems to do the trick! (actually, I just loaded the linux64
kmodule, did not try to apply the patch). Thanks!
Looks like the poudriere/common.sh needs this patch.
Mark
___
freebsd-stab
are
pretty squashed and ugly to my eyes).
What puzzles me is what has changed recently, as both hosts were happily
using vt consoles in graphical mode until the upgrade.
(btw, I do have nvidia-modeset.ko and nvidia.ko loaded)
Mark
___
freebsd-s
cious)
Mark
Connection attempt to UDP 193.2.4.2:53 from 95.87.1521242:26375
Connection attempt to UDP 193.2.4.2:53 from 95.87.1521242:55806
Connection attempt to UDP 193.2.4.2:53 from 95.823154.242:54530
Connection attempt to UDP 193.2.4.2:53 from 95.823154.242:55504
Connection attempt t
On 2017-02-02 12:55, Mark Martinec wrote:
11.0-RELEASE-p7, net.inet.udp.log_in_vain=1
The following syslog entries seem to indicate some buffer overruns
in the reporting code (not all log lines are broken, just some).
(the actual failed connection attempts were indeed there,
it's just tha
asize: 11453243392 (11G)
Sectorsize: 4096
Mode: r1w1e0
Consumers:
1. Name: gpt/sw1
Mediasize: 12884901888 (12G)
Sectorsize: 512
Stripesize: 4096
Stripeoffset: 0
Mode: r1w1e1
Mark
___
freebsd-stable@freebsd.org mailing
2017-02-06 18:04, Eric van Gyzen wrote:
On 02/06/2017 10:19, Mark Martinec wrote:
Hope the fix finds its way into 11.1 (or better yet, as a patch level
in 10.0). Should I open a bug report?
It will quite likely get into 11.1. As for a 10.x patch, you would
have
to ask re@ (I think), but
; be shipped without it. There is no intention of merge of the removal.
> The stable@ mailing list added for wider audience.
Can we presume no invalidation of the TARGET_ARCH=powerpc ABI?
It is SVR4 based as I remember (unlike TARGET_ARCH=powerpc64 ).
===
Mark Millard
markmi
nested examples before I
existed the one that only had the su --at which point it detected
the Failed assertion: "tsd_booted" as well (su and sh, su first).
In other experiments I found that it was when buildworld activity
caused swapping out of the failing processes that there were t
On 2017-Feb-27, at 7:21 PM, Mark Millard wrote:
> [I've added a variant of this material to bugzilla 217138.]
>
> I've reduced the testing context to the following
> type of example (no longer involving buildworld
> buildkernel):
>
> # sh
> # sh
> # sh
>
swap_testing.c
0x20488 <+320>: adrp x8, 51
0x2048c <+324>: addx8, x8, #0x808; =0x808
0x20490 <+328>: ldrb w9, [x8]
0x20494 <+332>: tbzw9, #0x0, 0x204a4 ; <+348> at swap_testing.c
0x20498 <+336>: orrw0, wzr, #0x6
0x2049c <+340>: bl 0x205c0 ; symbol stub for: raise
0x204a0 <+344>: strw0, [sp, #0x4]
0x204a4 <+348>: adrp x8, 51
0x204a8 <+352>: addx8, x8, #0x818; =0x818
0x204ac <+356>: ldrb w9, [x8]
0x204b0 <+360>: tbzw9, #0x0, 0x204c0 ; <+376> at
swap_testing.c:105
0x204b4 <+364>: orrw0, wzr, #0x6
0x204b8 <+368>: bl 0x205c0 ; symbol stub for: raise
-> 0x204bc <+372>: strw0, [sp]
0x204c0 <+376>: ldpx29, x30, [sp, #0x10]
0x204c4 <+380>: addsp, sp, #0x20 ; =0x20
0x204c8 <+384>: ret
# uname -apKU
FreeBSD pine64 12.0-CURRENT FreeBSD 12.0-CURRENT r314638M arm64 aarch64
1200023 1200023
buildworld buildlkernel did not have MALLOC_PRODUCTION= defined. The kernel is a
non-debug kernel. (Previous to these experiments my other corruption examples
were not caught by a debug kernel. I'm not hopeful that this simpler context
would either.)
===
Mark Millard
markmi at dsl-only.net
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On 2017-Mar-13, at 11:52 PM, Mark Millard wrote:
> I'm still at a loss about how to figure out what stages are messed
> up. (Memory coherency? Some memory not swapped out? Bad data swapped
> out? Wrong data swapped in?)
>
> But at least I've found a much smaller/simpl
[Another correction I'm afraid --about alternative program variations
this time.]
On 2017-Mar-13, at 11:52 PM, Mark Millard wrote:
> I'm still at a loss about how to figure out what stages are messed
> up. (Memory coherency? Some memory not swapped out? Bad data swapped
&
[This is just a correction to the subject-line text to say arm64
instead of amd64.]
On 2017-Mar-14, at 12:58 AM, Mark Millard wrote:
[Another correction I'm afraid --about alternative program variations
this time.]
On 2017-Mar-13, at 11:52 PM, Mark Millard wrote:
> I'm still at
[test_check() between the fork and the wait/sleep prevents the
failure from occurring. Even a small access to the memory at
that stage prevents the failure. Details follow.]
On 2017-Mar-14, at 11:07 AM, Mark Millard wrote:
> [This is just a correction to the subject-line text to say ar
On 2017-Mar-14, at 4:44 PM, Bernd Walter wrote:
> On Tue, Mar 14, 2017 at 03:28:53PM -0700, Mark Millard wrote:
>> [test_check() between the fork and the wait/sleep prevents the
>> failure from occurring. Even a small access to the memory at
>> that stage prevents the fa
A single Byte access to a 4K Byte aligned region between
the fork and wait/sleep/swap-out prevents that specific
4K Byte region from having the (bad) zeros.
Sounds like a page sized unit of behavior to me.
Details follow.
On 2017-Mar-14, at 3:28 PM, Mark Millard wrote:
> [test_check() betw
[Something strange happened to the automatic CC: fill-in for my original
reply. Also I should have mentioned that for my test program if a
variant is made that does not fork the swapping works fine.]
On 2017-Mar-15, at 9:37 AM, Mark Millard wrote:
> On 2017-Mar-15, at 6:15 AM, Scott Benn
On 2017-Mar-15, at 11:07 PM, Scott Bennett wrote:
> Mark Millard wrote:
>
>> [Something strange happened to the automatic CC: fill-in for my original
>> reply. Also I should have mentioned that for my test program if a
>> variant is made that does not fork the swappin
[Summary: I've now tested on a rpi3 in addition to a
pine64+ 2GB. Both contexts show the problem.]
On 2017-Mar-16, at 2:07 AM, Mark Millard wrote:
> On 2017-Mar-15, at 11:07 PM, Scott Bennett wrote:
>
>> Mark Millard wrote:
>>
>>> [Something strange happened
y: the small allocation size also matters.
Be warned that I can not eliminate the possibility that
the trashing changed what region of memory it trashed
for larger allocations or when tcache is disabled.
===
Mark Millard
markmi at dsl-only.net
___
f
On 2017-Mar-18, at 5:53 PM, Mark Millard wrote:
> A new, significant discovery follows. . .
>
> While checking out use of procstat -v I ran
> into the following common property for the 3
> programs that I looked at:
>
> A) My small test program that fails for
> a dyn
those ssh sessions (from a
macOS environment).
I discovered that if I typed ^C it would output a new prompt and
start taking/displaying input normally.
I've not had such an issue in a while.
I never managed to isolate what contributed to it happening.
===
Mark Millard
markmi at dsl-only.net
On 2017-Mar-18, at 9:10 PM, Mark Millard wrote:
>
> On 2017-Mar-18, at 5:53 PM, Mark Millard wrote:
>
>> A new, significant discovery follows. . .
>>
>> While checking out use of procstat -v I ran
>> into the following common property for the 3
>>
On 2017-Mar-21, at 7:21 PM, Mark Millard wrote:
> On 2017-Mar-18, at 9:10 PM, Mark Millard wrote:
>
>>
>> On 2017-Mar-18, at 5:53 PM, Mark Millard wrote:
>>
>>> A new, significant discovery follows. . .
>>>
>>> While checking out use
are known
to already be gcc compliant).
This still leaves the limits.h and gsystemlimits.h and
syslimits.h code in place but does block most of the
activity.
===
Mark Millard
markmi at dsl-only.net
___
freebsd-stable@freebsd.org mailing list
https://li
E.
>
> Thank you!
> George
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
This would work if you haven't converted 9 to use
pkgng .
https://svnweb.freebsd.org/ports/tags/RELEASE_9_EOL/
https://www.pkgsrc.org/
---
Mark Saad | nones...@longcount.org
> On Jun 3, 2017, at 11:39 AM, Howard Leadmon wrote:
>
> I know 9.3 is kinda dated, but it had bee
> On Jun 3, 2017, at 2:24 PM, Adam Vande More wrote:
>
>> On Sat, Jun 3, 2017 at 12:19 PM, Howard Leadmon wrote:
>>Thanks for the update, I had the feeling the issue was from it being to
>> old. I have a question, not sure if you know, but I will toss it out. As
>> I mentioned I upda
> On Jun 3, 2017, at 3:10 PM, Mark Saad wrote:
>
>
>
>> On Jun 3, 2017, at 2:24 PM, Adam Vande More wrote:
>>
>>> On Sat, Jun 3, 2017 at 12:19 PM, Howard Leadmon wrote:
>>>Thanks for the update, I had the feeling the issue was from it being to
On Sat, Jun 24, 2017 at 09:18:26PM +, Thomas Mueller wrote:
> excerpt from Glen Barber's announcement:
>
> > A list of changes since 11.1-RELEASE are available in the stable/11
> > release notes:
probably meant 11.1-BETA2 ?
mcl
___
freebsd-stable@f
area: 10.x continues to get separate
lang/gcc* package builds from 11.x and later.
No problem for this context as far as I know.
Note: To simplify I choose to not be explicit
about what authors wrote what original text.
If that becomes an issue, it is correctable.
Blame me for
0, 0x30
dimensions 1024 x 768
stride 1024
masks0x00ff, 0xff00, 0x00ff, 0xff00
bi_load_efi_data: GetMemoryMap error 5
_
Any one have any ideas here ?
--
mark saad | nones...@longcount.org
___
freebsd-s
ng which specific handling needs to be made.
But the vm_ooffset_t and vm_pindex_t changes did not even
make the UPDATING notes. Right now things look to have
the worst combination for lang/gcc* when release/11.1.0/
becomes official: lang/gcc* 's break without notification
or suggestion of a workaro
l need whatever
technique is used. Some, such as lang/gcc6-aux, need
more done because of binary bootstrap materials being
downloaded and used and so the build of lang/gcc6-aux
gets the problem and fails before staging happens: the
binary-bootstrap materials need to avoid the adjusted
headers th
On 2017-Jun-29, at 3:10 AM, Gerald Pfeifer wrote:
> Am 28. Juni 2017 22:38:52 GMT+08:00 schrieb Mark Millard dsl-only.net>:
>> A primary test is building lang/gcc5-devel under release/11.0.1
>> and then using it under stable/11 or some draft of release/11.1.0 .
>
>
On Thu, Jul 06, 2017 at 07:55:07PM -0500, Chris Watson wrote:
> Pefs is in ports under security I believe.
http://www.freshports.org/sysutils/pefs-kmod/
mcl
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-s
40811b zfs`___lldb_unnamed_symbol18$$zfs + 635
frame #9: 0x004059c2 zfs`___lldb_unnamed_symbol5$$zfs + 834
frame #10: 0x0040552f zfs`___lldb_unnamed_symbol1$$zfs + 383
Mark
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.o
On Mon, Jul 10, 2017 at 09:47:50PM +0200, José G. Juanino wrote:
> El Monday 10 de July a las 21:24:41 CEST, José G. Juanino escribió:
> >El Sunday 09 de July a las 23:48:29 CEST, David Boyd escribió:
> >>With latest VM-IMAGE (vmdk) for 11.1-RC2 system panics. I haven't
> >>been able to process t
On Thu, Jul 13, 2017 at 01:06:30PM +, Glen Barber wrote:
> On Wed, Jul 12, 2017 at 11:29:05PM -0700, jungle boogie wrote:
> > On 07/10/2017 10:48 PM, Konstantin Belousov wrote:
> > > On Mon, Jul 10, 2017 at 01:00:05PM -0700, Mark Johnston wrote:
> > > > I su
rst public description of the problem's details.)
I agree that you did not get an answer for the other
part:
> I simply asked if it's safe to assume the sysctl to be an integer in
> 11.1
I've not gone through any draft 11.1-release code
a 2-core CPU, with various symptoms, including:
(
https://lists.freebsd.org/pipermail/freebsd-hackers/2017-July/051260.html
)
Feeding entropy: .
spin lock 0x80db45c0 (smp rendezvous) held by
0xf80004378560
(tid 100074) too long
timeout stopping cpus
panic: spin lo
On Tue, Jul 18, 2017 at 01:01:16AM +0200, Mark Martinec wrote:
> Upgrading 11.0-RELEASE-p11 to 11.1-RC3 using the usual freebsd-update
> upgrade
> method I ended up with a system which gets stuck while trying to attach
> the second set of disks. This happened already after the fi
2017-07-18 01:24, Mark Johnston wrote:
Are you able to break into the debugger at this point? Try setting
debug.kdb.break_to_debugger=1 and debug.kdb.alt_break_to_debugger=1 at
the loader prompt, and hit the break key, or the key sequence
~ ctrl-b once the hang occurs. At the debugger prompt
esc do not activate kernel debugger. Loader "Safe mode"
avoids the problem (presumably by disabling SMP).
Meanwhile I have successfully upgraded two other similar
hosts from 11.0 to 11.1-RC3, no surprises there (but they do not
have the same disk controller).
Not sure what to try next.
M
On Thu, Jul 20, 2017 at 01:46:33AM +0200, Mark Martinec wrote:
> More news on the matter. As reported yesterday the locally built
> kernel with options INVARIANTS and DDB works fine and somehow avoids
> the trouble at attaching the da (mps) disks on an LSI controller, so
> today I w
2017-07-20 02:03, Mark Johnston wrote:
One thing to try at this point would be to disable EARLY_AP_STARTUP in
the kernel config. That is, take a configuration with which you're able
to reproduce the hang during boot, and remove "options
EARLY_AP_STARTUP".
Done. And it avo
On Sun, Jul 23, 2017 at 04:26:45PM +0700, Eugene Grosbein wrote:
> On 14.01.2017 18:40, Eugene Grosbein wrote:
> >
> >> I suspect that this is because we only stop the scheduler upon a panic
> >> if SMP is configured. Can you retest with the patch below applied?
> >>
> >> Index: sys/kern/kern_shut
On Thu, Jul 20, 2017 at 03:45:39PM +0200, Mark Martinec wrote:
> 2017-07-20 02:03, Mark Johnston wrote:
> > One thing to try at this point would be to disable EARLY_AP_STARTUP in
> > the kernel config. That is, take a configuration with which you're able
> > to reproduce
2017-07-24 04:15, Mark Johnston wrote:
Could you try re-enabling EARLY_AP_STARTUP, applying the patch at the
end of this email, and see if the message "sleeping before eventtimer
init" appears in the boot output? If it does, it'll be followed by a
backtrace that might be useful fo
This host never hung during normal work when EARLY_AP_STARTUP
was disabled (or with 11.0 and earlier).
Mark
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to &quo
that hangs if called just
> before
> crashdump generation but works just fine during normal system shutdown.
I think graid probably needs a treatment similar to r301173/r316032.
g_raid_shutdown_post_sync() appears to be quite similar to the
corresponding gmirror handler. In particular, it just
2017-07-24 18:25, Ken Merry wrote:
It is possible that the change I MFCed today (r321207 in head, r321415
in stable/11) is related, but Mark will have to boot his machine with
the fix to see if it makes any difference.
What happened in my case on one particular machine (not on most
machines in
But this is all for 11.0, on 11.1 it hangs and I cannot look it up:
Does it also hang if you choose 'Safe mode" in the loader dialog?
Mark
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd
17h45m28s
[00:00:05] Loading MOVED
make: "/usr/ports/Mk/bsd.port.mk" line 1177: UNAME_r () and OSVERSION (1101501)
do not agree on major version number.
[00:00:06] Error: Error looking up pre-build ports vars
[00:00:06] Cleaning up
[00:00:09] Unmounting file systems
And at this point we are
the C11 _Static_assert, with or
> without the include, going well outside the C++ language definition.
>
> . . .
>
> Fixed in r297299 .
(The context was a C++ file head/contrib/libcxxrt/guard.cc so C++'s
static_assert was used instead and -std=c++11 was added for the
libra
On 2017-Aug-25, at 12:14 AM, David Chisnall wrote:
> On 25 Aug 2017, at 07:32, Mark Millard wrote:
>>
>> As I remember _Static_assert is from C11, not
>> the older C99.
>
> In pre-C11 dialects of C, _Static_assert is an identifier reserved for the
> implement
On 2017-Aug-27, at 11:54 PM, Ed Schouten wrote:
> 2017-08-25 14:53 GMT+02:00 Ed Schouten :
>> 2017-08-25 9:46 GMT+02:00 Mark Millard :
>>> It appears that at least 11.1-STABLE -r322807 does not handle
>>> -std=c++98 styles of use of _Static_assert for g++7 in tha
in the (alphabetically)
*last* file there are taken into account, all other entries in
remaining included files are just ignored.
[...]
Details at:
Bug 221742
syslogd include directive reads but disregards all but the last
included .conf file
https://bugs.freebsd.org/bugzilla
Last Changed Rev: 323012
===
Mark Millard
markmi at dsl-only.net
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Nevermind, stupid mistake on my part: armv6 was not actually
updated yet.
> On 2017-Aug-29, at 8:42 PM, Mark Millard wrote:
>
> installworld for -r323012 is getting things like (at least with the likes of
> -j14):
>
> --- pwd_test.install ---
> --- _proginstall ---
>
All
Also don't forget to is install cciss_vol_status to monitor the array .
---
Mark Saad | nones...@longcount.org
On Sep 2, 2017, at 11:41 AM, sth...@nethelp.no wrote:
>>> I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in it. I
>>> have a HP smart arr
601 - 700 of 1357 matches
Mail list logo
