> Could you check the values of the following sysctl variables:
>
> vfs.zfs.vdev.cache_size
> vfs.zfs.vdev.cache_bshift
> vfs.zfs.vdev.cache_max
> kstat.zfs.misc.vdev_cache_stats.misses
> kstat.zfs.misc.vdev_cache_stats.hits
> kstat.zfs.misc.vdev_cache_stats.delegations
As predicted, all zero,
Am just upgrading my machiens, and have noticed an oddity.
This is on a machine runnign 12.2
# zfs-stats -D
ZFS Subsystem ReportFri May 14 08:30:50 2021
On 17/04/2021 21:18, Karl Denninger wrote:
This also makes "geli groups" trivial in /etc/rc.conf for attachment at
boot time irrespective of whether they physically come up in the same
place (again typically yes, but in the case of a failure or you plug it
into a different adapter.)
On 17/04/2021 21:06, Alan Somers wrote:
The answer depends on why you want to partition in the first place.
What do you intend to store on those disks besides ZFS? If the answer
is nothing, then don't bother partitioning; just write ZFS over GELI
over the whole disk.
Well, actually thats
So, am building a zpool on some encrypted discs - and what I have done
is to partition the disc with GPT add a single big partition, and
encrypt that. So the pool is on nda1p1.eli.
But I could, of course, encrypt the disc first, and then partition the
encrypted disc, or indded just put the
On 19/02/2021 22:30, Matthew D. Fuller wrote:
e.g., on one system BIOS-booting system, /boot/rewrite-bootcode.sh:
--
#!/bin/sh -x
for i in /dev/nda0 /dev/nda1; do
gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ${i}
done
On 10/02/2021 23:50, Eugene Grosbein wrote:
Try changing your command a bit:
/sbin/ifconfig $1 ether d0:bf:9c:46:a3:7c up
So, this worked. I also turned off the cable modem for five minuets
before rebooting as well, but I suspect it was simply this which did the
trick.
thanks,
-pete.
On 10/02/2021 23:50, Eugene Grosbein wrote:
Try changing your command a bit:
/sbin/ifconfig $1 ether d0:bf:9c:46:a3:7c up
Ah, interesting, yes - I did wonder about that, but looking inside
network.subr it seemed to run ifconfig_up regardless of the result from
ifcsript_up - but theres a
I have a machine runnign 12-STABLE, which gets its upstream IP address
from my ISP using DHCP over a cable modem. What I just tried to do was
to set the MAC address on that interface at boot time, but if I do that
then it no longer acquires a DHCP address from the upstream.
Is there something
On 06/01/2021 15:47, Ulrich Spörlein wrote:
That's not entirely correct. The packfile will only be rewritten if
a) enough other stuff has accumulated
b) you force a repack.
You are fighting against git's GC mechanism a bit here, but you can
still make it work. On your source of truth host,
On 05/01/2021 15:58, Chris wrote:
Brilliant minds think alike. I use nearly the same routine. ;-)
Always good to know that I am not doing something completely idiotic ;)
OTOH it won't be (easily) possible to "up" the repo(s) from the
receiving hosts w/o the .git.
Yes, this is my issue
So, for me the switch to git went very smoothly. I havent moved to
etcupdate yet, but will probably do that soon. Hopwever I did hit one
issue. What I do is to build on a single machine, and then send that to
a number of places using rsync.
But what seems to happen wuth git is that it has a
On 09/07/2020 14:36, Kyle Evans wrote:
We haven't quite standardized on a good process yet, IMO, but for
right now the correct process is to just mount the ESP and replace
loader.efi with your system's updated /boot/loader.efi. At some point
we'll standardize a mountpoint for the ESP and
On 09/07/2020 14:24, Kyle Evans wrote:
gpart bootcode -p /boot/boot1.efifat -i 1 ada0
gpart bootcode -p /boot/boot1.efifat -i 1 ada1
This method of updating the ESP is no longer recommended for new 12.x
installations -- we now more carefully construct the ESP with an
On 22/Mar/2020 16:16, Alexander Leidinger via freebsd-stable wrote:
This is now available as a port: biology/linux-foldingathome (thanks 0mp@).
Thankyou! However I dont seem to be able to make it work - I get this in
the log:
19:16:54:
19:16:54:
19:16:54:
19:16:54:
19:16:54:
On 25/Feb/2020 13:28, Mario Olofo wrote:
Good morning all,
@Pete French, you have trim activated on your SSDs right? I heard that
if its not activated, the SSD disc can stop working very quickly.
On the curent dfives, yes, but I have run with trim disabled in the
past, It kinds
On 25/Feb/2020 10:52, Daniel Kalchev wrote:
It might well be, that FreeBSD is more agressive with your motherboard/chipset
or does not implement known quirk of that — which might trigger some edge cases
for the SSD. Ultimately, if you can move that SSD to another motherboard and
test it, it
On 18/Feb/2020 17:19, Tomasz CEDRO wrot> But also as this DRM user (for
Intel and AMD) I have experienced the
related hiccups, problems, and problems solutions. It does not look
like a FreeBSD way, but more like Linux way. I never noticed anything
like this before. Sure, I can see this only as
On 28/Nov/2019 07:03, Eugene Grosbein wrote:
28.11.2019 13:46, Eugene Grosbein wrote:
Hi!
Is it normal that "zfs destroy" for one ZVOL with attribute "used" equal to
2112939808 bytes (~2GB)
takes over two minutes waiting on "tx_sync_done_cv"? The pool is RAID1 over
five SSDs encrypted
I have a very similar setup to you for serving files to my Mac from a
FreeBSD server. I haven't seen the unmount problem, but I di have a few
oddities until I added the 'fruit' module on the Samba side, which helps
with compatbiloty with the Mac. The appropriate bit of my config looks
like
On 10/Nov/2019 22:20, Kevin P. Neal wrote:
The rc script must have a function that starts the python program, right?
Actually, no. It just looks like this:
#!/bin/sh
# PROVIDE: waagent
# REQUIRE: sshd netif dhclient
# KEYWORD: nojail
.
On 04/Nov/2019 23:45, O'Connor, Daniel wrote:
This would also capture the stderr output, and should be pretty easy to shoe
horn into the rc.d file.
Nice thinking!
Just picking this up again, I have tried a few things, but am unable to
actually get this to work in the rc.d file, any
Soo, I tried this on my desktop machine, and it doesnt coredump, but
nor does it try and lauch the second python process, so a bit of a failed
test there!
-pete.
___
freebsd-stable@freebsd.org mailing list
> Ah, does python get run before the ldconfig service runs?
Nope, this is comming way after ldconfig has run - also the first python
interpretter runs fine, is the one which that python script then tries to
launch which fails.
Thats the bit which really puzzles me - if it was python dying then
Thanks for the ideas, running through these in order...
> Check "rcorder /etc/rc.d/* /usr/local/etc/rc.d/*"
So, its running directly after sshd and before swaplate and the
local stuff.
> Check if ldconfig is runable (I ended up with permissions 0444 on=20
> /etc/rc.d/ldconfig after some
> Shot in the dark: Is it possible that python is trying to dynamically
> load a shared library that isn't available yet due to being on a not-yet
> mounted filesystem?
I wondered about that, but I have these boxes confiured with only one filesystem
for everything apart from mysql data.
> Just a
> Hmm, does changing the command_args line to this work:
> command_args=3D"start 2>/tmp/waagent.log"
> work?
That is byte-for-byte identical to what I tried :-) It creates the file
in /tmp, but the file remains empty.
I think I need to look at the source code to work out whats up with it (on
the
> Hmm very odd..
> Does the tool depend on something else running?
No, not at all. Earlier versions of the tool dont do this either.
On a machine running the tool started by hand the two processes look like this:
0 86918 1 0 20 03426823860 wait I 0- 0:00.92
python
> Does it crash if you run it from the command line with 'env -i' in front?
>
> That clears out the environment and will be a lot closer to the rc.d
> environment.
Interesting idea, but no, that works fine. Annoyingly!
> If that doesn't show anything then you will have to try capturing stderr
>
So heres an oddity - I have a service which runs under python3. It
works fine if I start it from a terminal as root, but when it is
started at boot the python interpretter itself coredumps.
The program in question is the latest Microsoft 'waagent' form
machines running in Azure. This apparently
Does anyone have any pointers to how to make bootable AWS volumes
for FreeBSD ? I did this once, a long time ago, but its eluding me now.
Am just trying to simply clone a machine I have deployed from the 12.1
AMI for now, just to see where I am going wrong.
I ceate the machine, I attach a new
> > Any opinions or things people would ike me to check ?
>
> netstat -p tcp -ss
> tcpdump -i $interface -npvs0 icmp or 'tcp[tcpflags] & (tcp-rst) !=3D 0'
I havent had a chnace to look at this for a couple of days, but I thought
I would give it mor testing now (doing the above). Updated to the
This is odd - I have six FreeBSD boxes on the local ether here. Five are
HP Microservers, one is an AMD Ryzen. They are all running 12.1 r352847
built yesterday - and its one compilation I did which is rsynced out to
all the machines, so an identical build.
I was running iperf3 -s on one machine
On 20/06/2019 17:22, Glen Barber wrote:
Dear FreeBSD community:
As I have a highly-visible role within the community, I want to share
some news. I have decided the time has come to move on from my role
with the FreeBSD Foundation, this Friday being my last day. I have
accepted a position
Just to follow up on this thread from April, where people were talking about
graphics/drm-kmod hanging on boot with an older Radeon card. I had the same
issue and have bene using graphics/drm-legacy-kmod since then, but the
changes to the Linux KPI which have come into STABLE in the last few
On 09/05/2019 00:17, Miroslav Lachman wrote:
Time for some scripting :) This is what I have on the machine with weird
controller
# cat bin/zfs_bootcode_update.sh
#!/bin/sh
devs="ada0 ada1 ada2 ada3"
for dev in $devs
do
echo -n "Updating ZFS bootcode on ${dev} ..."
if !
On 05/05/2019 04:06, Michelle Sullivan wrote:
Which I find interesting in itself as I have a machine running 9.3 which
started life as a 5.x (which tells you how old it is) and it’s still running on
the same *compaq* raid5 with UFS on it... with the original drives, with a hot
spare that
On 04/05/2019 01:05, Michelle Sullivan wrote:
New batteries are only $19 on eBay for most battery types...
Indeed, my problem is actual physical access to the machine, which I
havent seen in ten years :-) I even have a relacement server sitting
behind my desk which we never quite got
On 03/05/2019 14:07, Michelle Sullivan wrote:
I don’t think it will do that in write through.. it will everytime in write
back.
Yes, it really shouldnt do that.
My server is so old that the battery on the RAID has failed, which
definitely makes it go into write though mode. However not an
On 03/05/2019 13:11, Miroslav Lachman wrote:
I had this problem in the past too. I am not sure if it was on Dell or
HP machine - controller presents first disk only in the boot time so I
created small (10 - 15GB partition) on each disk and use them all in 4
way mirror. Cannot say if it was
Hmm What happens when you do a “camcontrol devlist”?
root@toybox:/usr/local/etc # camcontrol devlist
at scbus0 target 0 lun 0 (pass0,da0)
at scbus0 target 1 lun 0 (pass1,da1)
at scbus0 target 2 lun 0 (pass2,da2)
On 03/05/2019 08:09, Borja Marcos via freebsd-stable wrote:
The right way to use disks is to give ZFS access to the plain CAM devices, not
thorugh some so-called JBOD on a RAID
controller which, at least for a long time, has been a *logical* “RAID0” volume
on a single disk. That additional
On 25/04/2019 15:07, Filippo Moretti via freebsd-stable wrote:
Did you build world yesterday and now drm-kmod is working again?The only
problem I have with legacy both drm and ati is that smplayer crashes the system
and I have to reset via power switch.Filippo
Si, I just tried this
On 19/04/2019 12:46, k...@ixsystems.com wrote:
FreeBSD Developers,
We're pleased to make available images allowing testing of FreeBSD using ZFS
on Linux. During this development cycle, the ZoL code has been made
portable, and available in the ports tree as sysutils/zol and
I have a radeon graphics card, too. Recently, I had a problem with the
graphics/drm-kmod hanging on boot in multi-user. My fix was to switch
to graphics/drm-legacy-kmod, which at least lets the system boot again.
I figure the newer graphics/drm-kmod no longer supports my old radeon card.
On 05/04/2019 16:01, Kris von Mach wrote:
I've upgraded from Stable 11 to Stable 12, and noticed that igb has been
removed and is now part of em driver. However, the performance seems a
lot worse. This is using HP 366FLR which is just HP's version of Intel
i350 I believe.
Something odd
On 17/03/2019 21:57, Eugene Grosbein wrote:
I agree. Recently I've found kind-of-workaround for this problem:
increase vm.v_free_min so when "FREE" memory goes low,
page daemon wakes earlier and shrinks UMA (and ZFS ARC too) moving some
memory
from WIRED to FREE quick enough so it can be
On 15/02/2019 08:06, Patrick M. Hausen wrote:
We build from sources centrally, then zfs send/receive /usr/src and
/usr/obj to all of the machines, then just do the install(kernel|world)
part on all of them.
I do this occasionally, but in the main I sumply NFS mount /usr/src and
/usr/obj
On 14/02/2019 01:43, Jason Tubnor wrote:
I also have hit this IPv6 issue (I thought I was going crazy until I worked
it out) and other iflib issues in 12.0, which have been fixed in -STABLE
that really should be patched in 12.0 or bring forward an early 12.1
release. For our use case, 12.0 is
Thanks guys! That was fast
On 12/02/2019 20:13, Kristof Provost wrote:
On 2019-02-12 13:54:21 (-0600), Eric van Gyzen wrote:
> I see the same behavior on head (and stable/12).
>
> (kgdb) f
> #16 0x80ce5331 in ether_output_frame (ifp=0xf80003672800,
> m=0xf8000c88b100)
I found my panic. If I take everything out of rc.conf and loader.conf
and sysctl.conf and boot the system it works fine when I add an IP
address. If I add this one line to sysctl.conf
net.link.ether.inet.garp_rexmit_count=2
Then I get a panic when I configure the interface:
So, another datapoint on this - I just PXE booted the 12.0-RELEASE image
downloaded from https://mfsbsd.vx.sk/ and that works fine. Which means
that it siether something which has crept in since 12.0-RELEASE or its
something to do with my config on that machine.
I did try and buld an mfsroot
On 06/02/2019 12:16, Andrey V. Elsukov wrote:
Hi,
this doesn't look very useful.
Do you have some specificity with this host except carp? Some
modifications to kernel config, lagg, jails, etc.
No, none of those. Its a supermicro motherboard, runs FreeBSD
GENERIC and mysql+redis on top,
> Hi,
>
> What branch and revision do you use? Can you install gdb and then obtain
> this information:
The branch and revision is 12.0-STABLE r343538 GENERIC
> # kgdb
>
> (kgdb) list *ether_output+0x6b6
trying to do this on the actual box is hard, as it panics, but on another
machine running
Just to get the subject correct, as I tested this disabling CARP and I
still see the panic when going multi-user. It netwprking related as the
panic is in the ARP code, and seems to happen when the network
interfaces are configured. The machine was using a mix of em and igb
interfaces, but
> > To point out the obvious, booting a 12.0 kernel with 11.0 userland to
> > multiuser mode is seriously unsupported. You really need to boot to
> > single user and install 12.0 userland to really expect things to work.
>
> Yes, good point. This has worked on every other machine I have upgraded
On 26/01/2019 16:43, tech-lists wrote:
OK, thanks. I thought this might be the case. Just wanted to make sure I
wasn't trying to reinvent the wheel ;)
We use Azure extensivley with FreeBSD, and I havent installed from an
image since the first one. Everything I do is taking a copy of an
To point out the obvious, booting a 12.0 kernel with 11 userland to
multiuser mode is seriously unsupported. You really need to boot to
single user and install 12.0 userland to really expect things to work.
Yes, good point. This has worked on every other machine I have upgraded
from 11 to
so, having got a workaround for yesterdays problems, I now went to upgrade my
other pair of boxes using CARP. No 'pf' on these, just one shared address.
This is the setup I have tested in development and it works fine.
I install the new kenel and do the first reboot - and I get the panic
below.
> I have confirmed that pfsync is the culprit. Read on for details.
Excellent work. I;m home now, so won't get a chnace to out this into
practice until tomorrow unfortunately, but it's brilliant that you have
confirmed it.
> I tried disabling pfsync and rebooting both nodes, they came up as
>
> I can't see how any of those would impact carp unless pf is now
> incorrectly blocking carp packets, which seems unlikely from that commit.
Just looking at the code it does seem unlikely, true - but my working
system does not run pf+pfsync and the non working one does, so it is
suspiciously in
> Indeed. I am seeing the same thing. Which revision of 12 are you running?
Ah, now that is very interesting - I wasnt expecting a reply so fast!
I am running r342847 - not though, that this is also the version I am running
on the two test systems which do work.
> I am currently (yesterday and
I just upgraded my pair of firewalls from 11 to 12, and am now in the
situation where CARP no longer works between them to faiilover the
virtual addresse. Both machines come up thinking that they
are the master. If I manually set the advskew on the interfaces to
a high number on what should be
On 15/01/2019 14:48, Matt Garber wrote:
For what it’s worth, HAProxy has the PROXY protocol for exactly the scenario
you’re describing; I’ve heard it’s very straightforward and powerful to use,
although haven’t had to use it on any of my HAProxy instances which are
primarily doing L7.
On 15/01/2019 10:24, Mark Blackman wrote:
On 14 Jan 2019, at 18:44, Dave Cottlehuber wrote:
haproxy does proper failover and allows custom health checks either via
URL or real world traffic of external scripts. Traefik has lots of
container oriented features.
Dave
There’s also the very
So, until the middle of this afternoon I was, doing my load balancing using
relayd from ports and PF. My own fault for not checking, but I upgraded
one of the firewall pair to 12 and then discovered that the relayd port is
no longer available.
Am now puzzling over solutions to this - I dont
> Glen,
> It is just a bit shy of 25 years and 1 month that I shipped
> the 1.0 Release. Its been a long road, but we are here now!
Its alwasy really nice to see poeple who have been with the project since
the start still around :-) So, time to start upgrading everything to 12.0!
well
On 04/12/2018 18:26, Mike Tancsa wrote:
I think I will downgrade the box that was having issues to RELENG11 to
see if the problem is there too. Unfortunately, the issue took ~ 10
days to show itself
My issues showed up on releng 11 as well as releng 12 - I didnt ry the
last 11 stable for
On 04/12/2018 15:04, Mike Tancsa wrote:
Well, another lockup. This time after ~ 10 days of uptime. Box was idle
at the time and just a solid freeze. This is an ASUS PRIME X370-PRO
running BIOS from 09/07/2018 (latest). Not sure if BIOS related or OS
related. I have another motherboard (MSI)
On 26/11/2018 16:30, Mike Tancsa wrote:
Interesting, I too have noticed my one test box have the odd lockup. I
think it started around the BETA series. Is it possible something
"undid" one of the fixes ? I brought the box in question upto
12.0-PRERELEASE FreeBSD 12.0-PRERELEASE r340724 and
On 26/11/2018 16:28, Eric van Gyzen wrote:
My Ryzen has never run 11, but I have never seen a single problem on 12.
As you suggest, it's probably due to the particular hardware
combination. If updating the BIOS doesn't help, I agree that lowering
the memory clock is the best next step.
I
Foolwing up an old thread I know, but my ssystem ahs been pretty stable
until recently, when it started locking up about one a week at least.
This co-incided with me doing two things to it:
1) Doubling the amount of RAM in it to 16 gig, using RAM which runs a
bit faster than the original
On 12/11/2018 22:12, Dimitry Andric wrote:
If you are on amd64, ld is now LLVM's lld. You can check this with "ld -v":
$ ld -v
LLD 6.0.1 (FreeBSD 335540-125) (compatible with GNU linkers)
Ah, yes, I am on amd64 - that would be it then, thanks!
Worth menioning in the release notes
Just trying out the BETA4 version of 12, updating from 11-STABLE. All went
nice and smoothly, but when compiing coe I had to make some tweaks to the
arhuments I am passing to 'ld' when part-linking objects against static
libraries. Did something chnage here ? Its not on the release notes that I
, xrandr only showed one outout on
the card, which puzzled me (there are 4 outputs).
-pete. [copying to -stable so others know the outcome]
On 16/10/2018 12:39, Niclas Zeising wrote:
On 10/9/18 12:32 PM, Pete French wrote:
So this is kind of interesting - I posted here last month about trying
So this is kind of interesting - I posted here last month about trying to
use drm-next and it not finding my 2nd monitor properly. I did try and
subscribe to x11@ but for some reaosn that didnt work, and I didnt worry
abotu it too much so didnt investigate further as I wont be running 12.0
for a
> Been testing various kernels since I posted this, currently at r338931
> which runs fine. Will continue on Friday as am not inf ront of the
> machine tomorrow.
Just to uodate this, I have tried the update from this morning, r339193, and
tthat works fine. I noticed some more ZFS stuff went in,
On 04/10/2018 20:54, Doug Hardie wrote:
I have a number of production servers that only have bge and I don't see that
listed in either category. None of them are running FreeBSD 12 yet as it has
not been released. Also there are some with rl. Those are add-on boards so
they could be
On 03/10/2018 15:16, Pete French wrote:
The machine is booting ZFS (unencrypted) and is a Ryzen CPU. I will
start trying to work out where the offending commit is, but if anyone
has an insight which might help shortcut the process then please let me know.
Been testing various kernels since
I just upgraded to STABLE, having been running r338093 since the end of August,
and was su[psised when it locked up on boot for me. By which I mean the keyboard
is unresponsible and the SATA drive access LED is on permamently.
I have a small encryopted partition, and the boot gets as far as
> I would like to build a Ryzen desktop.? Can anyone recommend a good
> motherboard?
I have oe of these:
https://www.msi.com/Motherboard/X370-XPOWER-GAMING-TITANIUM
but I just saw how much they are charging for it these days! I got one
at about half that. I did originally get a B370 based
it's from the xorg-server port/pkg:
$ pkg list xorg-server|grep modes
/usr/local/lib/xorg/modules/drivers/modesetting_drv.so
/usr/local/man/man4/modesetting.4.gz
Ah, OK, in that case I would have had it when I did my experiment with
remiving all the existing xf86-* drivers. I wont be able
I believe your best bet is to let Xorg probe your devices automatically
- i.e. don't have an xorg.conf in place when starting X.
Yes, I dont have an xorg to conf - I was a bit unclear, I meant which
drivers should I instal from the xorg-drivers package as I dont
generally install all of
Starting from the beginning:
how the "drm.ko" is loaded ?
Thats a very good question! I am not loading it myself
explicitly anyhere, so my guess is that xorg is loading it.
On the machine right now (which I was using with X11 yesterday)
it only has drm2 loaded - again, I assume from
can you post your dmesg output from when you've set
kld_list="/boot/modules/amdgpu.ko"? also, please verify that your user
is in the "video" group. but from what you've described it sounds like
a conflict is popping up between the base amdgpu.ko and the one
available in the ports tree.
I'd try a make deinstall inside drm-stable-kmod and drm-legacy-kmod
directories and see if that fixes anything.
On Tue, 11 Sep 2018 13:50:24 +0100
Pete French wrote:
So, I was trying to switch to using this, as I realise its where
things are heading, and I rather like the look of it. But I cant
On 11/09/2018 14:42, Pete French wrote:
I think you have to use kld_list="/boot/modules/amdgpu.ko" to get the
new one.
Will give it a try - I think its unnecessary as the name doesnt clash,
but worth a go...
-pete. [quick reboot comming up]
I tired this, it doesnt hel
I think you have to use kld_list="/boot/modules/amdgpu.ko" to get the
new one.
Will give it a try - I think its unnecessary as the name doesnt clash,
but worth a go...
-pete. [quick reboot comming up]
___
freebsd-stable@freebsd.org mailing list
So, I was trying to switch to using this, as I realise its where things
are heading, and I rather like the look of it. But I cant get it to see my
multiple monitors. I install the port, set 'kld_list="amdgpu"' and it boots
up with the new modules, and appears to find all my displays in dmesg. But
So, having been stable for quite sme time, I have had three lockups on
my Ryzen in the last week. two were whilst I was in X11, but one
happened over the weekend whilst I was looged out, and thus I could get
a screenshot of what was on the console when I got in this morning:
Hmm. First, make sure that it isn't running (service local_unbound
stop, etc).
Then look at your /etc/resolv.conf -- unbound tends to rewrite that
on initial
startup, taking some of it's settings and inserting itself into the
middle as a
caching DNS server. At the
having enabled local_unbound in /etc/rc.d how do I remove that
and go back to using just DHCP delivered nameservers ? I
set it to 'NO' but yet the machine still seems to have traces of
the config in other places and keeps trying to use them, for reasons I
dont understand.
Is there a quyick guide
> Mark Johnston fixed this. See
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230196
Thanks - I saw the commit go in earlier, but I hadnt checked my email
until now. Sorry I didnt investigate this myself, as I am perfectly capable
of doing so, to be honest, just very short of time :-(
I just brought everything upto date and re-tested and same issue.
FreeBSD 11.2-STABLE #1 r336761
# mount | grep -v zfs
devfs on /dev (devfs, local, multilabel)
linprocfs on /compat/linux/proc (linprocfs, local)
linsysfs on /compat/linux/sys (linsysfs, local)
tmpfs on /compat/linux/dev/shm
On 27/07/2018 14:10, Mike Tancsa wrote:
I havent used the linux emulator in ages. What is the easiest way to try
this out ?
in rc.conf have
linux_enable="YES"
when you boot. then
pkg install linux_base-c7
/compat/linux/bin/bash
and you should see a bash pprompt
I highly doubt that this can be related.
Well, yes, it suroprised me too :-) Admittedly I dont have a very big
samle set - I nly have one Ryzen box and a pair of Epyc boxes in Azure.
but I cant make it run on any of them. I take the same OS and run it on
Intel and its fine (literally I am
So, I have been running the patched kernel for quiet a while now, and it
works fine for me, but last night I did hit a surprising issue - the
Linux emulator does not work on Ryzen / Epyc. I tried this on two
machines (both with the patches) and it coredumps when simply running
bash on both of
> Hmm, I gte a core dump trying to run any Linux binary at the moment (stable
> from Tuesday - r336665). I have remoed all packages and re-installed
> and running /compat/linux/bin/bash coredumps. Running ldd on it coredumps
> too, and gdb gets e nowhre.
I did a bit more testing on this. It only
Hmm, I gte a core dump trying to run any Linux binary at the moment (stable
from Tuesday - r336665). I have remoed all packages and re-installed
and running /compat/linux/bin/bash coredumps. Running ldd on it coredumps
too, and gdb gets e nowhre.
Unfortunately I have no idea when it last worked,
On 22/07/2018 02:48, George Mitchell wrote:
Based on people's recent Ryzen experiences, is it fair to say that
FreeBSD 11.2 is now believed to work on Ryzens, if you have a recent
enough Ryzen and your motherboard has been updated to the latest BIOS?
I would still use the patches provided
1 - 100 of 783 matches
Mail list logo
