ch really solves the
problem.
Now kernel generates crashdump just fine in case of panic. Please commit the
fix, thanks!
Eugene Grosbein
___
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"
Hi!
My 11.0-STABLE/i386 r311924 debugging kernel catches _rm_assert(rm, RA_RLOCKED,
file, line)
in sys/netpfil/ipfw:ipfw_chk() function trying to do IPFW_PF_RUNLOCK(chain) on
an object
that was not rlocked but wlocked:
#17 0xc06b0255 in _rm_runlock_debug (rm=0xc0bce37c, file=,
line=) at /home/
Hi!
My 11.0-STABLE/i386 r311924 debugging kernel catches _rm_assert(rm, RA_RLOCKED,
file, line)
in sys/netpfil/ipfw:ipfw_chk() function trying to do IPFW_PF_RUNLOCK(chain) on
an object
that was not rlocked but wlocked:
#17 0xc06b0255 in _rm_runlock_debug (rm=0xc0bce37c, file=,
line=) at /home/
23.02.2017 3:47, Lev Serebryakov пишет:
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.
If you use it with i386 (32 bits), you must use loader.conf tunnable:
kern.kstack_pages
> Is there anyway to get the VGA fonts back. I never want any characters
> outside of Latin I.
>
> Text programs are the only reason I use FreeBSD
Have you tried putting "kern.vty=sc" to /boot/loader.conf
to make kernel use traditional VGA text mode (syscons driver)
and good old VGA fonts?
__
On 18.04.2017 18:59, tech-lists wrote:
> Hello stable@
>
> I have an up-to-date 10.3 server that is randomly rebooting, after being
> up for days. Previously it had been up for many months. The problem is,
> nothing seems to be left in the logs to indicate why it's doing this. I
> have all.log and
Hi!
11.1 code freeze is already in effect but a regression in syslogd reported in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215335 and fixed in HEAD
still not MFC'd ti stable branches and PR Assignee seems to be unresponding.
Is it possible to get that simple MFC happen so 11.1-RELEASE be
31.05.2017 4:19, CBL пишет:
> Updated a box to 11.0 with a legacy 3ware 9690SA using the twe driver.
> Now the tw_cli utility is now throwing "Bad system call (core dumped).
>
> Anybody have any suggestions? Was working fine on 10.3.
Perhaps, you use custom kernel (not GENERIC) and forgot to add
6114, 214482).
Please take a look.
Eugene Grosbein
___
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"
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
> handler around the locked region. Note that this can only work if the
> cancellation is in deferred mode
15.06.2017 0:09, Konstantin Belousov wrote:
> 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 locke
It would probably be a good idea to compute the differences in the stack
> pointer values between adjacent stack frames to see of any of them are
> consuming an excessive amount of stack space.
Also, there is https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219476
Eugene Grosbein
_
22.07.2017 14:05, Konstantin Belousov wrote:
> 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 wil
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 exhibit real kernel stack problems due to KVA fragmentation
>> and KSTACK_PAGES>2
On 22.07.2017 16:57, Konstantin Belousov wrote:
>>From this description, I would be not even surprised if your machine
> load fits into the kstacks cache, despite cache' quite conservative
> settings. In other words, almost definitely your machine is not
> representative for the problematic load.
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?
>>
>> Inde
Hi!
Long story short: stable/11 r321371 started to panic at the moment of smartd
invocation
after my SSD died.
I have Intel motherboard with graid-supported pseudo-raid.
I use it in RAID1 mode with one HDD and one SSD.
Yesterday the SSD has died: it is not detected by BIOS nor FreeBSD kernel
(
On 23.07.2017 20:02, Eugene Grosbein wrote:
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00
> fault virtual address = 0xa
> fault code = supervisor read data, page not present
> instruction pointer = 0x20:0x80e494e1
On 24.07.2017 08:44, Mark Johnston wrote:
>> Sadly, this time 11.1-STABLE r321371 SMP hangs instead of doing crashdump:
>
> Is this amd64 GENERIC, or something else?
Custom kernel, amd64.
>
>>
>> - "call doadump" from DDB prompt works just fine;
>> - "shutdown -r now" reboots the system withou
CCing mav@ as graid expert.
On 24.07.2017 08:44, Mark Johnston wrote:
>> Sadly, this time 11.1-STABLE r321371 SMP hangs instead of doing crashdump:
>>
>> - "call doadump" from DDB prompt works just fine;
>> - "shutdown -r now" reboots the system without problems;
>> - "sysctl debug.kdb.panic=1" t
On 25.07.2017 00:22, Mark Johnston wrote:
> On Tue, Jul 25, 2017 at 12:03:05AM +0700, Eugene Grosbein wrote:
>> Thanks, this helped:
>>
>> $ addr2line -f -e kernel.debug 0x80919c00
>> g_raid_shutdown_post_sync
>> /home/src/sys/geom/raid/g_raid
On 23.07.2017 20:02, Eugene Grosbein wrote:
> Hi!
>
> Long story short: stable/11 r321371 started to panic at the moment of smartd
> invocation
> after my SSD died.
>
> I have Intel motherboard with graid-supported pseudo-raid.
> I use it in RAID1 mode with one HDD and
On 26.07.2017 21:28, Frank Steinborn wrote:
> Can someone tell me if this got fixed before 11.1-RELEASE?
Yes, the fix was MFC'd to the release branch and is present in the 11.1-RELEASE:
https://svnweb.freebsd.org/base?view=revision&revision=320904
__
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), uid 0: exited on signal 12
id 21 comm sh: nosys 42
Jul 27 14:30:23 init: /bin/s
On 27.07.2017 23:28, Konstantin Belousov wrote:
> Take your /bin/sh, libraries and rtld to some other machine and try to
> catch where the pipe(2) call come from. I do not see any other way
> forward, assuming your build env is not contaminated somehow.
>
> I did the following on the today stabl
On 27.07.2017 23:28, Konstantin Belousov wrote:
>> Trying to mount root from ufs:/dev/ada0s1a [ro]...
>> start_init: trying /sbin/init
>> ppid 21 (sh), uid 0: exited on signal 12
>> id 21 comm sh: nosys 42
>> Jul 27 14:30:23 init: /bin/sh on /etc/rc terminated abnormally, going to
>> single user
06.10.2017 22:17, Rostislav Krasny wrote:
> I consider this as a critical bug. But maybe there is some workaround
> that allows me to install the FreeBSD 11.1 as a second OS without
> repartitioning the entire disk?
>
> My hardware is an Intel Core i7 4790 3.6GHz based machine with 16GB
> RAM. Th
07.10.2017 22:26, Warner Losh wrote:
> Sorry for top posting. Sounds like your BIOS will read the botox64.efi from
> the removable USB drive,
> but won't from the hard drive. Force BIOS booting instead of UEFI and it will
> install correctly.
> However, it may not boot Windows, which I think req
09.10.2017 1:23, grarpamp пишет:
> Here is a report of a repeatable unrecoverable problem.
>
> 11.0 release amd64 r306420
>
> kern.geom.debugflags=0 (unmodified)
>
> # dd if=/dev/zero of=/dev/ada0s1 seek=2048 count=1 bs=1m
> 1+0 records in
> 1+0 records out
> 1048576 bytes transferred
>
> # reb
10.10.2017 15:06, grarpamp пишет:
> On Sun, Oct 8, 2017 at 3:05 PM, Eugene Grosbein wrote:
>> The problem is known and already fixed. You should upgrade.
>
> Was there a ticket and revision number to look into that?
> Because this issue is still present in 11.1 and r324300.
On 26.10.2017 04:10, Mike Tancsa wrote:
> On 10/25/2017 4:54 PM, Mike Tancsa wrote:
>> While testing out our nanobsd RELENG11 images, I noticed a strange
>> routing issue. Using a standard pppoe config that has been working fine
>> on RELENG8,9,10 I am getting bogus routing entries.
>> having the
On 26.10.2017 20:45, Mike Tancsa wrote:
> vs
>
> got message of size 124 on Thu Oct 26 09:37:40 2017
> RTM_ADD: Add Route: len 124, pid: 24236, seq 1, errno 0,
> flags:
> locks: inits:
> sockaddrs:
> 192.168.136.1 64.7.128.7
>
> got message of size 196 on Thu Oct 26 09:37:40 2017
> RTM_CHANGE
26.10.2017 21:25, Mike Tancsa wrote:
> On 10/26/2017 9:59 AM, Eugene Grosbein wrote:
>> On 26.10.2017 20:45, Mike Tancsa wrote:
>>
>>> vs
>>>
>>> got message of size 124 on Thu Oct 26 09:37:40 2017
>>> RTM_ADD: Add Route: len 124, pid:
27.10.2017 1:04, Mike Tancsa пишет:
> On 10/26/2017 12:01 PM, Eugene Grosbein wrote:
>>
>> I would re-run ppp under ktrace to make sure while having "route monitor"
>> running around.
>> Then compare pids with kdump output.
>
> I wonder if I copie
On 30.10.2017 20:57, Mike Tancsa wrote:
> On 10/26/2017 6:16 PM, Eugene Grosbein wrote:
>>
>> That makes sense: ppp send bogus request to the routing socket and
>> the request has not RTF_HOST flag nor RTA_NETMASK address.
>> It seems, earlier kernel code masked this
On 01.11.2017 22:35, Lev Serebryakov wrote:
>
> Now 11-STABLE (and 12-CURRENT too) have this:
>
> sys/netinet/udp_usrreq.c:#define UDBHASHSIZE 128
>
> Looks like such low value could lead to 100% consumption of CPU by
> interrupt threads (igb queues in my case) on heavy incoming UDP traf
22.11.2017 21:08, Adam Vande More wrote:
>> I have a droplet in DO with very light load, currently
>> running 11.0-RELEASE-p15 amd64 GENERIC kernel + zfs (1 GB Memory / 30 GB
>> Disk / FRA1 - FreeBSD 11.0 zfs)
>>
>> I know ZFS needs more memory, but the load is really light. Unfortunatelly
>> last
23.12.2017 1:16, Kirill Ponomarev via freebsd-stable wrote:
> I've recently purchased Zotac CI327 nano:
> https://www.zotac.com/product/mini_pcs/ci327-nano
>
> and tried to install FreeBSD-11.1 RELEASE on it, installation just
> hangs and I can't get into debugger. Here is verbose output:
> http
23.12.2017 2:16, Kirill Ponomarev wrote:
>> Can you break into the loader prompt before starting a kernel and do this?
>>
>> set kern.eventtimer.periodic=1
>> boot -v
>
> Yes, did it, the same output as before.
This can be some kind of interrupt routing problem.
Try: set hw.pci.enable_msix=0
At
23.12.2017 2:16, Kirill Ponomarev пишет:
> On 12/23, Eugene Grosbein wrote:
>> 23.12.2017 1:16, Kirill Ponomarev via freebsd-stable wrote:
>>
>>> I've recently purchased Zotac CI327 nano:
>>> https://www.zotac.com/product/mini_pcs/ci327-nano
>>>
>
e system, I see that idprio'd bzip2 takes all cycles of first core
and two "normal" bzip2's share cycles of second core each taking ~50% of CPU
time.
It is expected that idprio'd bzip2 get no CPU time at all and each of "normal"
bzip2's
get ~100% of
On 26.12.2017 16:10, Eugene Grosbein wrote:
> Is idprio(1) broken in stable/11?
>
> As root, start one bzip2 instance with idprio and one additional bzip2
> intance per CPU core:
>
> # idprio 5 bzip2 -9 /dev/null &
> # n=$(sysctl -n kern.smp.cpus)
> # i=1; while [ $
On 26.12.2017 18:37, Andriy Gapon wrote:
>>> Is idprio(1) broken in stable/11?
>>>
>>> As root, start one bzip2 instance with idprio and one additional bzip2
>>> intance per CPU core:
>>>
>>> # idprio 5 bzip2 -9 /dev/null &
>>> # n=$(sysctl -n kern.smp.cpus)
>>> # i=1; while [ $i -le $n ]; do bzi
On 26.12.2017 18:37, Andriy Gapon wrote:
>>> It is expected that idprio'd bzip2 get no CPU time at all and each of
>>> "normal" bzip2's
>>> get ~100% of single CPU core for such setup.
>>
>> This works as expected for stable/10.
>
> Seems to work as expected on head as well.
I've updated my old
09.01.2018 14:11, wishmaster wrote:
> Jan 5 09:49:40 server kernel: swap_pager_getswapspace(32): failed
> Jan 5 09:49:40 server kernel: swap_pager_getswapspace(24): failed
> Jan 5 09:49:40 server kernel: swap_pager_getswapspace(18): failed
[skip]
This has nothing to do with netgraph, dummynet
09.01.2018 16:30, wishmaster wrote:
>>> Jan 5 09:49:40 server kernel: swap_pager_getswapspace(32): failed
>>> Jan 5 09:49:40 server kernel: swap_pager_getswapspace(24): failed
>>> Jan 5 09:49:40 server kernel: swap_pager_getswapspace(18): failed
[skip]
> # swapinfo
> Device 1K-blocks
15.01.2018 16:31, Marko Cupać wrote:
> Hi,
>
> one of my ageing servers, HP DL380g5, which is serving a bunch of
> non-critical production jails on FreeBSD 11.1, bacame inaccessible over
> weekend. I have physical access, its disks and NICs are showing
> activity, but it doesn't send anything to m
28.01.2018 21:57, Andre Albsmeier wrote:
> I have a lot of machines running with 4 GB physical RAM and, for
> some reasons, I still have to use a 32 bits OS.
>
> All of them show something between 3 and 3.5 GB of RAM available
> in dmesg but the brand new Supermicro A2SAV really shocked me:
>
>
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 (still) have 32 bit machines and don't want to maintain 2 userlands.
> Each machine has i
31.01.2018 4:36, Mike Tancsa пишет:
> On 1/30/2018 2:51 PM, Mike Tancsa wrote:
>>
>> And sadly, I am still able to hang the compile in about the same place.
>> However, if I set
>
>
> OK, here is a sort of work around. If I have the box a little more busy,
> I can avoid whatever deadlock is going
04.02.2018 4:18, Brandon Allbery wrote:
> (I'm not sure "W" status even means swap; I thought whole-process swapping
> wasn't even supported any more.)
Kernel may decide to swap out entire processes if vm.swap_enabled=1 (default)
and its free page pool heavily stressed or system was configured by
04.02.2018 5:09, Mark Millard via freebsd-stable wrote:
> I do not know if a W after the first letter in state (STAT) for
> "ps auxww" track the kernel-stacks' resident-vs-not status for the
> process or not. (Matching your not sure status.)
A process has specific flag P_INMEM that is normally 1
04.02.2018 5:32, Brandon Allbery wrote:
> Also worth noting is that likely candidates for such pageouts include
> long-lived daemons that are only needed, or which only need certain pages,
> during startup/shutdown. So evicting only those pages to swap allows
> optimal use of memory that would oth
04.02.2018 4:14, Michael Voorhis wrote:
> I've got an amd64 system running 11.1-STABLE r325027, with something
> like 20G of swap. "swapinfo" shows that half the swap is used.
>
> So of course I'm curious to know which processes have been swapped
> out. I'm not using any "tmpfs" filesystems; no Z
04.02.2018 6:42, Michael Voorhis wrote:
> 1 frame of your requested "top" output, sorted as specified:
>
>> last pid: 47195; load averages: 0.17, 0.37, 0.44 up 99+20:40:41 18:37:07
>> 369 processes: 1 running, 368 sleeping
>> CPU: 0.2% user, 0.0% nice, 0.2% system, 0.0% interrupt, 99.7%
12.02.2018 11:56, Ask Bjørn Hansen пишет:
> Hi,
>
> I have an old Soekris system with 64MB memory that I upgraded from 10.3 to
> 11.1 recently. Since then it’s started hanging every few days.
>
> Today I happened to have a “top” instance running on the serial console. The
> system is minimally
13.02.2018 0:38, Ask Bjørn Hansen wrote:
>>> I have an old Soekris system with 64MB memory that I upgraded from 10.3 to
>>> 11.1 recently. Since then it’s started hanging every few days.
>> Please show output of commands:
>>
>> grep memory /var/run/dmesg.boot
>
> real memory = 67108864 (64 MB)
13.02.2018 1:30, Ian Lepore wrote:
>>> PID USERNAME THR PRI NICE SIZERES STATETIMEWCPU COMMAND
>>> 911 root1 220 8816K 8844K select 0:39 4.20% ntpd
>> Your Soekris system can live without bloated ntpd, use ntpdate or try sntp
>> to periodically check your cloc
27.02.2018 5:47, Konstantin Belousov wrote:
> I put the snapshot of the WIP of the merge to 11.1 at
> https://kib.kiev.ua/kib/amd64_11.1_meltdown.1.patch
>
> I only compiled this on the stable/11, not even booted. I suspect that
> it is not compilable on 11.1 because apparently the patch depends
03.03.2018 19:56, Bruce Evans wrote:
> On Sat, 3 Mar 2018, tech-lists wrote:
>
>> On 03/03/2018 00:23, Dimitry Andric wrote:
>>> Indeed. I have had the following for a few years now, due to USB drives
>>> with ZFS pools:
>>>
>>> --- /usr/src/etc/rc.d/zfs2016-11-08 10:21:29.820131000 +0100
>>
03.03.2018 23:11, Julian H. Stacey wrote:
> Oops! I got Subject & body wrong s/inetd/init/ !
>
> Was:memory leak in inetd 10.3-STABLE .svn_revision 304147 ?
> Should be: memory leak in init 10.3-STABLE .svn_revision 304147 ?
There is no evidence that /sbin/init has memory leak (nor ine
03.03.2018 23:33, Julian H. Stacey wrote:
> Eugene Grosbein wrote:
>> 03.03.2018 23:11, Julian H. Stacey wrote:
>>
>>> Oops! I got Subject & body wrong s/inetd/init/ !
>>>
>>> Was:memory leak in inetd 10.3-STABLE .svn_revision 304147 ?
&
05.03.2018 19:10, Dimitry Andric wrote:
>> When no boot drive is detected early enough, the kernel goes to the
>> mountroot prompt. That seems to hold a Giant lock which inhibits
>> further progress being made. Sometimes progress can be made by trying
>> to mount unmountable partitions on other
Hi!
Let's create a stripe and GPT over it using test files as backing store:
truncate -s 1G d0
truncate -s 1G d1
mdconfig -af d0 # gives md0
mdconfig -af d1 # gives md1
gpart create -s GPT md0
gpart create -s GPT md1
gpart destroy -F md1
gpart destroy -F md0# no errors still
On 13.03.2018 17:39, Andriy Gapon wrote:
> On 13/03/2018 11:37, Eugene Grosbein wrote:
>> Hi!
>>
>> Let's create a stripe and GPT over it using test files as backing store:
>>
>> truncate -s 1G d0
>> truncate -s 1G d1
>> mdconfig
Hi!
Please consider bumping __FreeBSD_version after
https://svnweb.freebsd.org/base?view=revision&revision=327597
for head and stable/11 to ease port maintainers life,
so that port's Makefile could differentiate systems having
CPUCTL_EVAL_CPU_FEATURES.
__
On 20.03.2018 21:10, Eugene Grosbein wrote:
> Please consider bumping __FreeBSD_version after
>
> https://svnweb.freebsd.org/base?view=revision&revision=327597
>
> for head and stable/11 to ease port maintainers life,
> so that port's Makefile could d
02.04.2018 5:00, Mark Knight wrote:
> I'm trying to do the usual src code upgrade from FreeBSD 10.3 to 10.4, as
> I've done many times before with earlier version bumps.
>
> However, for some reason the 10.4 kernel seems to break my system, either
> with the 10.3 or 10.4 userland.
>
> The main
On 02.04.2018 19:27, Mark Knight wrote:
>> What does it show if you press "CTRL-T" to see a status of "hung" process?
>
> Typically CTRL-T shows [sysctl mem]. In some circumstances I can CTRL-C
> (e.g. if su hangs), in others I cannot (e.g. with sudo).
>
>> Does it help if you comment out the l
02.04.2018 23:41, Mark Knight пишет:
> On 02/04/2018 14:44, Eugene Grosbein wrote:
>> 3. Boot new kernel using nextboot(8) and see if it will crash instead of
>> deadlock
>> and if so, fill the PR to Bugzilla.
>
> Thanks again. Drat, no crash. The only difference
04.04.2018 21:16, Peter wrote:
> // With nCPU compute-bound processes running, with SCHED_ULE, any other
> // process that is interactive (which to me means frequently waiting for
> // I/O) gets ABYSMAL performance -- over an order of magnitude worse
> // than it gets with SCHED_4BSD under the sam
Hi!
I've just updated my desktop from early 11.1-STABLE to recent one 11.1-STABLE
and found that non-absolute paths do not work anymore, like this:
libevent-2.0.so.5 compat/pkg/libevent-2.0.so.5.1.10
With luck, this still works:
libevent-2.0.so.5 /usr/local/lib/compat/pkg/libevent-2.0.so.5.1.10
16.04.2018 18:35, Christian Jachmann wrote:
> But on i386 it seems to be broken.
Why don't you rebuild src/usr/bin/w with debugging symbols, generate core and
show backtrace?
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/ma
16.04.2018 19:04, Christian Jachmann wrote:
> #0 ifree (tsd=0x2800) at arena.h:799
> 799 return (*mapbitsp);
> (gdb) bt
> #0 ifree (tsd=0x2800) at arena.h:799
> #1 0x28155316 in __free (ptr=0x280601ef) at tsd.h:716
> #2 0x28095b07 in xo_do_emit_fields ()
> at /usr/src/c
Hi!
I have a server that was running stable/11 rock-stable for many months.
A week ago I've updates it to 11.1-STABLE r332356 and today it paniced and I
have crashdump.
Any thoughts?
Unread portion of the kernel message buffer:
Sleeping thread (tid 100444, pid 28400) owns a non-sleepable lock
KD
On 17.04.2018 16:30, Eugene Grosbein wrote:
CCing mjoras@ as author of suspicious change
https://svnweb.freebsd.org/base?view=revision&revision=323477
> I have a server that was running stable/11 rock-stable for many months.
It was running stable/11 r314043 before last update.
>
19.04.2018 0:59, Peter wrote:
> thank You very much for Your commenting and reports!
>
> From what I see, we have (at least) two rather different demands here:
> while George looks at the over-all speed of compute throughput, others are
> concerned about interactive response.
>
> My own issue
26.04.2018 14:50, Andriy Gapon wrote:
> You can try to use zdb -l to find the stale labels.
> And then zpool labelclear to clear them.
Our "zpool labelclear" implementation destroys everything (literally).
Have you really tried it?
___
freebsd-stable@f
08.05.2018 12:08, O'Connor, Daniel wrote:
> Hi,
> I have several FreeBSD machines setup as routers connected to ADSL modems in
> bridge mode. ie the FreeBSD box terminates the PPP connection and the ADSL
> modem doesn't do much.
>
> This worked well for many moons but a while ago I found issues
30.07.2017 12:08, Nenhum_de_Nos wrote:
> I was running 10.3-p7 on Atom hardware and using old samba36-3.6.25_1. All
> was fine.
>
> Then I updated to 11.1-R by recompiling from svn, using the same
> kernelconfig from 10.3, and now my windows client shows timeouts and
> really slow connection. Fil
14.05.2018 8:06, Mike Karels wrote:
> So the freebsd-update version is not in sync with the -stable branch?
> That was not at all obvious to me. I upgrade from source on my -current
> test system, but normally use freebsd-update on my production systems
> (until it failed to update the kernel).
20.05.2018 18:49, tech-lists wrote:
> Hi,
>
> context: 11.2-BETA2 #0 r333924/amd64
>
> I'm trying to get chrooted ftpd (in base) to write files uploaded to the user
> dir as mode 666 (umask 111).
> I have a line in inetd.conf that looks like this:
>
> ftp stream tcp nowait root /usr/libexec/f
On 19.05.2018 20:46, Gary Palmer wrote:
>
> Hi,
>
> I haven't tried building an i386 image with nanobsd since 8.x or 9.x,
> so apologies if this is a known issue
>
> I've tried to build an i386 nanobsd using nanobsd on an amd64 host,
> and when that didn't work in an i386 jail on an amd64 host,
24.05.2018 21:41, tech-lists wrote:
> If I then run 'agent', prompts me for the keyphrase, then it works normally.
> But I have to repeat this in every single opened terminal.
You may like security/keychain port (or package). I use it because of its
universal way to run ssh-agent:
no matter wha
27.05.2018 5:29, Jonathan Chen wrote:
> I'm running 11.2-BETA3/amd64 at r334236, and I've noticed that
> "ldconfig -m" doesn't behave as expected (or perhaps it's my
> understanding).
>
> This is what I'm seeing when building security/nss in a chrooted environment:
>
> # ldconfig -r | grep nss
27.05.2018 16:26, Eugene Grosbein wrote:
> 27.05.2018 5:29, Jonathan Chen wrote:
>
>> I'm running 11.2-BETA3/amd64 at r334236, and I've noticed that
>> "ldconfig -m" doesn't behave as expected (or perhaps it's my
>> understanding).
>>
04.06.2018 7:59, David Samms wrote:
> Hello,
>
> Background:
> -
> System was originally installed with an 11.0 CD. At the time I tried to get
> UEFI to work, but ended up booting in legacy/BIOS mode. Upgrading to 11.1 was
> uneventful. The system has a single SSD with full disk enc
13.07.2018 1:14, Matt Smith wrote:
> I run acme.sh with it configured to log to syslog. I use this syslog.conf
> structure to log to a specific log file:
>
> !-acme.sh
> ... other syslog.conf entries ...
> !acme.sh
> *.*/var/log/acme.log
> !*
>
> This has worked for ages, but I've just
13.08.2018 20:52, Alexander Lochmann wrote:
> Hi folks!
>
> We are doing some automatic experiments using FreeBSD running in a
> virtual machine.
> To control the experiment from the outside, we use serial ports to
> communicate with an userspace program.
> The communication via serial does work
14.08.2018 3:15, Alexander Lochmann wrote:
>> You should not rely on defaults and make sure you disable modem control/CD
>> either explicitly (using stty(1) etc.) or implicitly by switching to
>> /dev/cuau0
>> instead of /dev/ttyu0. Flow control settings should match too, for both sides
>> of vir
14.08.2018 9:47, Kurt Jaeger wrote:
>> 14.08.2018 3:15, Alexander Lochmann wrote:
>>
You should not rely on defaults and make sure you disable modem control/CD
either explicitly (using stty(1) etc.) or implicitly by switching to
/dev/cuau0
instead of /dev/ttyu0. Flow control s
On 15.08.2018 18:06, Alexander Lochmann wrote:
> I've to correct myself. It works if I activate the boot console
> (console="vidconsole,comconsole").
> If I change the mentioned line to console="vidconsole", neither writing
> to /dev/ttyu0 nor reading from /dev/cuau1 works.
> It seems that the Free
20.08.2018 21:47, Stefan Bethke wrote:
> I have a Go program (acme-dns) that wants to bind 53, 80, and 443, and I’d
> rather have it run as a non-privileged user. The program doesn’t provide a
> facility to drop privs after binding the ports. I’m planning to run it in a
> jail.
>
> After some
20.08.2018 22:02, Stefan Bethke wrote:
>> The trick is that mac_portacl provides a way to selectively give permission
>> for non-root UID
>> to bind low ports:
>>
>> security.mac.portacl.rules=uid:88:tcp:80,uid:88:tcp:443,uid:53:tcp:53,uid:53:udp:53
>>
>> It works just fine for a host and I use i
20.08.2018 23:22, Stefan Bethke wrote:
> Do you feel it’s OK to enable VIMAGE in -stable? When I tried last in 2016, I
> had stability issues, I think related to pf.
It is already in HEAD's GENERIC and will be in 12.0-RELEASE soon, so in -stable
too.
I use it with stable/11 without problems bu
21.08.2018 1:37, Charles Sprickman via freebsd-stable wrote:
> I am so behind on all the new toys in the system. I was very embarrassed
> to find out about this feature from someone who’s primarily working
> with Linux in his day job. He was just looking to bind an Elixir app to
> 80/443
> with
21.08.2018 2:15, Mike Tancsa wrote:
> I was trying to create a single partition on a 16G mSata drive and
> whenever I add a partition, all of a sudden the secondary GPT partion is
> borked. Any idea whats going on here ?
>
>
>
> 0# gpart destroy -F ada0
> ada0 destroyed
> 0# gpart create -s GP
21.08.2018 20:20, Mike Tancsa wrote:
> On 8/20/2018 11:34 PM, Eugene Grosbein wrote:
>>> I was trying to create a single partition on a 16G mSata drive and
>>> whenever I add a partition, all of a sudden the secondary GPT partion is
>>> borked. Any idea whats goin
31.08.2018 23:08, Samuel Chow wrote:
> I am running 11-STABLE, and I am experiencing kernel panics when I am
> destroying a VIMAGE-based jail. Naturally, I flipped to the chapter about
> 'Kernel Debugging' to learn about 'Obtaining a Kernel Crash Dump'.
>
> However, I am finding that my permane
09.09.2018 5:35, Rainer Duffner wrote:
> Hi,
>
> I got a kernel panic
>
> This a a HP Gen10 system.
> It has this new Microsemi SAS HBA that only got the driver with 11.2.
>
> It’s running a syslog-server (syslog-ng)
>
> I have attached a screenshot of the panic, hopefully it comes through.
>
401 - 500 of 597 matches
Mail list logo
