d to have ctfconvert installed. This
does mean you need to use a custom kernel instead of GENERIC.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Rick Macklem wrote this message on Thu, Mar 26, 2020 at 14:33 +:
> John-Mark Gurney wrote:
> [lots of stuff snipped]
> >Rick Macklem wrote:
> >> I had originally planned on some "secret" in the certificate (like a CN
> >> name
> >> that sat
-U
1300085
Is the magic awk that the virtualbox port is using to generate a kernel
module from userspace code broken?
A clue stick gently or harshly applied to my noggin would be very much
appreciated.
John
groenv...@acm.org
___
freebsd-curr
Rick Macklem wrote this message on Wed, Mar 25, 2020 at 23:50 +:
> John-Mark Gurney wrote:
> >Rick Macklem wrote this message on Mon, Mar 23, 2020 at 23:53 +:
> >> Alexander Leidinger wrote:
> >> John-Mark Gurney wrote:
> >> >>Rick Mackl
Rick Macklem wrote this message on Mon, Mar 23, 2020 at 23:53 +:
> Alexander Leidinger wrote:
> John-Mark Gurney wrote:
> >>Rick Macklem wrote:
> >>> to be the best solution. The server can verify that the certificate
> >>> was issued by
> >
e vs IPsec limiting itself to packet size, usually
1500, though possibly 9k if you're using jumbo frames...
I fully support doing NFS over TLS.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Rick Macklem wrote this message on Thu, Mar 19, 2020 at 23:41 +:
> John-Mark Gurney wrote:
> >Rick Macklem wrote this message on Wed, Mar 04, 2020 at 03:15 +:
> >> I am slowly trying to understand TLS certificates and am trying to figure
> >>
ges to a DNS server, and I now use DNS
challenges for everything, including https.
> Thanks for any help with this, rick
Let me know if you'd like to hop on a call about this.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do,
linker_load_file: /boot/modules/vboxvfs.ko - unsupported file type
Unsure if this is compiler/linker or kernel bug.
John
groenv...@acm.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
On 1/28/20 8:57 AM, John F Carr wrote:
> I use emacs tramp mode, which opens an ssh connection to a remote machine for
> file access. It works to Linux and FreeBSD 12.1, but not to CURRENT. There
> has been a change in the way characters are echoed by the shell, with 12.1
&
I use emacs tramp mode, which opens an ssh connection to a remote machine for
file access. It works to Linux and FreeBSD 12.1, but not to CURRENT. There
has been a change in the way characters are echoed by the shell, with 12.1
treating a consecutive run of backspace as an atomic unit and
On 1/26/20 8:08 PM, Rick Macklem wrote:
John Baldwin wrote:
[stuff snipped]
Hmmm, this might be a fair bit of work indeed.
Right now KTLS only works for transmit (though I have some WIP for receive).
KTLS does assumes that the initial handshake and key negotiation is handled by
OpenSSL
On 1/12/20 8:23 PM, Benjamin Kaduk wrote:
> On Thu, Jan 09, 2020 at 10:53:38PM +, Rick Macklem wrote:
>> John Baldwin wrote:
>>> On 1/7/20 3:02 PM, Rick Macklem wrote:
>>>> Hi,
>>>>
>>>> Now that I've completed NFSv4.2 I'm on to the next
s = SSL_new(...);
/* fd is the existing TCP socket */
SSL_set_fd(s, fd);
OpenSSL_connect(s);
if (BIO_get_ktls_send(SSL_get_wbio(s)) {
/* Can use KTLS for transmit. */
}
if (BIO_get_ktls_recv(SSL_get_rbio(s)) {
/* Can use KTLS for receive. */
}
--
John Baldwin
___
On 12/19/19 12:06 PM, Ryan Libby wrote:
> On Wed, Dec 18, 2019 at 1:49 PM John Baldwin wrote:
>>
>> In the interest of supporting newer versions of GCC for a base system
>> toolchain, I've renamed the external GCC packages from -gcc
>> to -gcc6. These are built as fla
On 12/18/19 4:16 PM, Mark Millard wrote:
>
>
> On 2019-Dec-18, at 13:48, John Baldwin wrote:
>
>> In the interest of supporting newer versions of GCC for a base system
>> toolchain, I've renamed the external GCC packages from -gcc
>> to -gcc6. These are built as
on
newer FreeBSD releases (e.g gcc9 for 13.0 and gcc6 for 12.x).
I do plan to switch the default toolchains for make universe/tinderbox
for targets using -xtoolchain-gcc based on GCC 6 over to the
freebsd-gcc6 variants in the next week or so.
--
John Baldwin
56060040
> >>
> >> I haven't used FreeBSD since 4.4-RELEASE, and I think 12-stable would
> >> probably be a better option ... I am willing to try out 13-CURRENT though.
> >>
> >> Does anyone have advice? Could someone point me to snapshot of 13-CURRENT
> &g
On 10/22/19 8:42 PM, Alexey Dokuchaev wrote:
> On Tue, Oct 22, 2019 at 04:34:53PM -0700, John Baldwin wrote:
>> On 10/18/19 10:05 AM, Alexey Dokuchaev wrote:
>>> hi there,
>>>
>>> i've made my -CURRENT world and installed, but "make delete-old"
hing, or ObsoleteFiles.inc lacks a few entries?
These are from the OpenSSL 1.1.1 commit. However, they are tagged as
OLD_LIBS and check-old-libs and delete-old-libs should be automatically
deleting these? Does 'make check-old' report these files as
old libraries?
--
John Baldwin
On 9/25/19 10:33 AM, Sergey Kandaurov wrote:
> On Sat, Sep 21, 2019 at 08:43:58PM -0400, Ryan Stone wrote:
>> I have written a short test program that runs unlinkat(2) in
>> capability mode and fails due to not having the write capabilities:
>>
>> https://people.freebsd.org/~rstone/src/unlink.c
>>
e compiles that can take
many GB's of memory and if they recently exited, there hasn't been time
to swap stuff back in... or is this the steady state over the entire
compile?
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All t
On 8/30/19 10:42 AM, Kyle Evans wrote:
> On Fri, Aug 16, 2019 at 7:38 PM John Baldwin wrote:
>>
>> On 8/16/19 3:05 AM, Gary Jennejohn wrote:
>>> I tried to build a kernel today and it failed in modules-all even
>>> though I had LOCAL_MODULES=""
On 8/16/19 5:33 PM, Rozhuk Ivan wrote:
> On Fri, 16 Aug 2019 17:23:08 -0700
> John Baldwin wrote:
>
>>> I use better way:
>>> /etc/make.conf:
>>> # Modules to build with kernel.
>>> PORTS_MODULES+= graphics/drm-fbsd12.0-kmod
>>> graphics/gpu
ule}
(${target:S/^reinstall$/install/:S/^clobber$/cleandir/})"
@cd ${LOCAL_MODULES_DIR}/${module}; ${MKMODULESENV} ${MAKE} \
@@ -83,6 +84,7 @@ modules-${target}:
${target:S/^reinstall$/install/:S/^clobber$/cleandir/}
.endfor
.endif
+.endif
.endfor
# Handle ports (as def
ing (you have to just use
LOCAL_MODULES=) this already exists. You can set it in
/etc/src.conf, in a kernel config, or on the command line.
> Rather than a default to on with an opt out mechanism perhaps
> while we gain experience change this to a default to off with
> an opt in mechanism?
It'
On 8/16/19 3:52 PM, Rozhuk Ivan wrote:
> On Fri, 16 Aug 2019 15:40:24 -0700
> I use better way:
> /etc/make.conf:
> # Modules to build with kernel.
> PORTS_MODULES+= graphics/drm-fbsd12.0-kmod graphics/gpu-firmware-kmod
This doesn't work for folks who use pre-built packages.
-
On 8/14/19 1:19 PM, Ian Lepore wrote:
> On Wed, 2019-08-14 at 13:59 -0600, Warner Losh wrote:
>> On Wed, Aug 14, 2019 at 1:56 PM Ian Lepore wrote:
>>
>>> On Wed, 2019-08-14 at 12:00 -0700, John Baldwin wrote:
>>>> On 8/14/19 11:06 AM, Kyle Evans wrote:
&
only one /usr/local/sys/modules? Do I need multiple port trees
> just to pull in out of tree module sources?
In some ways, installing sources for DRM is a compromise for the fact that we
can't have DRM in the base source anymore (for various reasons). However,
virtualbox is also probably in t
derr output. Can you try doing that to see
if bhyve is reporting an error? Alternatively, can you see if the bhyve
process is still running?
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/fr
options, and
we need to figure out how to handle other options.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Also, the 'make tinderbox' use case is a legit use case
that some folks want (for CI, etc.)
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "fre
On 8/14/19 10:23 AM, Emmanuel Vadot wrote:
> On Wed, 14 Aug 2019 10:13:48 -0700
> John Baldwin wrote:
>
>> On 8/14/19 9:22 AM, Ian Lepore wrote:
>>> This all sounds vaguely wrong, backwards, to me. A developer who is
>>> using a given module on their bu
r of people doing
> crossbuilding is small enough that nobody else is going to object to
> this "the whole world is amd64" automation.
You assume DRM is amd64-only when it is definitely not. It also has
suitable guards in its Makefile to only build the relevant ke
On 8/13/19 3:17 PM, Ian Lepore wrote:
> On Tue, 2019-08-13 at 14:58 -0700, John Baldwin wrote:
>> For developers this means even if you are doing testing on a box
>> that doesn't use DRM, you can install the package so that kernel
>> builds will try to compile it and hopefully
es and try to build them if the package is installed.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
quot; while loading my core
> file.
Usually this means that your vmcore file is not from the same kernel you are
passing to kgdb. In the case of ports gdb the reason it crashes is that gdb
is finding that the value of 'dumptid' from the vmcore is 0 and normally
dumptid is t
Toomas Soome wrote:
> have you checked if current image still does crash on your hw?
Thanks for picking this up.
I haven't recently booted current so I don't know if some other
check avoids the problem there.
-- J
chance of the patch being reviewed in time for the FreeBSD 11.3 release?
-- John
-
| Feith Systems | Voice: 1-215-646-8000 | Email: j...@feith.com |
|John Wehle| Fax: 1-215-540-5495
n' to force a rescan of a PCI bus as
Ian noted. For native PCI-express hotplug you should not need to
do manual rescans (though FreeBSD does not support PCI-e hotplug
via Thunderbolt).
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https
have max ULP of 2.9 (the
> desired result); with the latter you have a max ULP of 23.xxx.
> I have observed a 6 billion ULP issue when running my testsuite.
> As pointed out by John Baldwin, GCC is aware of the FPU setting.
> The problem with clang is that it seems to unconditiona
t is gcc doing different than clang
in this case. I assume neither GCC _nor_ clang are adjusting the FPU in
compiler-generated code, and in fact as Steve's earlier tests shows, the
precision is set to PD by default when a clang-built binary is run.
--
John Baldwin
On 3/13/19 9:40 AM, Steve Kargl wrote:
> On Wed, Mar 13, 2019 at 09:32:57AM -0700, John Baldwin wrote:
>> On 3/13/19 8:16 AM, Steve Kargl wrote:
>>> On Tue, Mar 12, 2019 at 07:45:41PM -0700, Steve Kargl wrote:
>>>>
>>>> gcc8 --version
>>>> gcc
nt
>> main(void)
>> {
>>double re, im, u, ur, ui;
>>float complex f;
>>float x, y;
>
> this line to "volatile float x, y".
So it seems to be a regression in clang 7 vs clang 6?
--
John Baldwin
__
, not
> just core deciding what is or is not a tier 1 and/or how to fix our
> tier 1 situation with i386 (which I do agree needs to change, but
> to what I have not a solid idea.)
As you are well aware, core@ has talked to some stakeholders already
(including you) which has already resulted in
removing per my other mail. While there is some cruft in a
few files for older CPUs (mostly just initcpu.c and identcpu.c) it is quite
small and in code that doesn't change. To effect any type of substantial "win"
in reducing code complexity for i38
; thinking of removing the workarounds like F00F. Are there any processors that
> are still vulnerable to this?
We have only removed support for 386 since it didn't support cmpxchg. We still
nominally support 486s. I don't know how well FreeBS
On 2/28/19 10:32 AM, Steve Kargl wrote:
> On Thu, Feb 28, 2019 at 09:09:38AM -0800, John Baldwin wrote:
>> You can do all your tests directly on amd64 by just adding
>> "-m32" to compile i386 binaries against the libraries in /usr/lib32
>> and you will generate t
for testing i386 things. I also run i386 VMs under bhyve on
amd64 hosts. I'm not sure your laptop's CPU can run i386 VMs though, and you
don't
need a VM to test userland-only changes (I'm usually trying to test kernel
changes).
However, an amd64 kernel is going to
On 2/14/19 12:38 PM, Steve Kargl wrote:
> On Thu, Feb 14, 2019 at 12:26:01PM -0800, John Baldwin wrote:
>> On 2/13/19 6:47 PM, Steve Kargl wrote:
>>> #16 0x00ff58bb in trap (frame=0x2e7b6880) at
>>> /usr/src/sys/i386/i386/trap.c:519
>>> #17 0xffc0315d in ?? ()
24 syscall (frame=0x2e7b6ce8) at /usr/src/sys/i386/i386/trap.c:1144
> #25 0xffc033a7 in ?? ()
> #26 0x2e7b6ce8 in ?? ()
> Backtrace stopped: Cannot access memory at address 0xfbafbbbc
> (kgdb)
Frame 18 is probably the root problem, though it doesn't look like kgdb is
able t
On 1/3/19 10:40 PM, Kevin Oberman wrote:
> On Wed, Jan 2, 2019 at 5:02 PM Robert Huff wrote:
>
>>
>> John Baldwin writes:
>>
>>> -[8] In order to have a kernel that can run the 4.x binaries needed
>> to
>>> -do an installwo
On 1/2/19 1:31 PM, Robert Huff wrote:
>
> John Baldwin writes:
>
>> >> [8] In order to have a kernel that can run the 4.x binaries
>> >> needed to do an installworld, you must include the
>> >> COMPAT_FREEBSD4 option in your kernel. [...]
>
; No, COMPAT_FREEBSD4 is not needed. Maybe COMPAT_FREEBSD11 is needed.
Yes, that text needs to be made more generic to say that you will need
COMPAT_FREEBSD. Though we've also had so
ng (and llvm) with stripped down debug symbols by
default. If you don't put any DEBUG_* foo in src.conf you will get debug
symbols for all of the world including the limited ones for clang. (We
use -gline-tables-only or some such fo
n all of the devices.)
I have a fresh install of 12.0-RC3 here that still has the files in /boot
and doesn't have a /bootpool directory at all.
--
John Baldwin
___
freebsd-current
On 12/10/18 12:19 PM, Ian Lepore wrote:
> On Mon, 2018-12-10 at 14:42 -0500, Anthony Jenkins wrote:
>> On 12/10/18 1:26 PM, John Baldwin wrote:
>>>
>>> On 12/10/18 9:00 AM, Anthony Jenkins wrote:
>>>>
>>>> Hi all,
>>>>
>>>>
e
BAR. If you want to enforce exclusivity (once a device allocates part of
a BAR then other children shouldn't be permitted to do so), then you will
need a more complicated solution.
Hopefully that gives you a starting point?
--
John Baldwin
Konstantin Belousov wrote this message on Sat, Nov 24, 2018 at 12:40 +0200:
> On Sat, Nov 24, 2018 at 01:04:29AM -0800, John-Mark Gurney wrote:
> > I have an BeagleBoard Black. I'm running a recent snapshot:
> > FreeBSD generic 13.0-CURRENT FreeBSD 13.0-CURRENT r340239 GENERIC a
for the zones did not increase at ALL:
swpctrie:48, 62084, 0, 0, 0, 0, 0
swblk: 72, 62040, 0, 0, 0, 0, 0
Thoughts?
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has
ry
devices work? Maybe your battery devices don't have a _STA method and you
need the change in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191?
--
John Baldwin
___
freeb
On 10/30/18 1:22 AM, Rajesh Kumar wrote:
> Hi John,
>
> Thanks for your updates. I assume you are talking about having a unified
> intr_machdep.h compared to having seperate amd64 and i386 versions.
>
> Can you please update this thread once all changes are MFC
On 10/25/18 10:24 AM, Rajesh Kumar wrote:
> Hi John,
>
> Thanks a lot. It helps. I backported the changes to 11.2 and tried booting in
> my board with success without any need for the said tunables.
>
> I see those changes are marked for MFC after 2 Weeks. But I don't
to ask the following: is it expected for
> kernel panics to happen when there are errors in the file system?
Have you unmounted the file system, and tried to do a fsck on it? That
you're getting a bad file descriptor sounds like it might be a directory
entry pointing to a bad inode.
--
John-Mar
On 10/25/18 2:14 AM, Marcin Cieslak wrote:
> On Wed, 24 Oct 2018, John Baldwin wrote:
>
>> On 10/23/18 10:58 AM, Marcin Cieslak wrote:
>>> This GDB was configured as "amd64-marcel-freebsd"...BFD:
>>> /boot/kernel/kernel: invalid relocation type 37
&
h my observations about the issue on
> 11.1/11.2 in the following thread
> https://forums.freebsd.org/threads/freebsd-11-1-installation-fails-and-rebooting.65814/
>
> Let me know if you need any details.
I believe this was fixed by r338360.
--
John Baldwin
__
Is this something that matters at all?
It is not something that is likely to be fixed. If you pkg install gdb from
ports, is the kgdb it includes able to examine the crash dump?
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://l
zeof oexport_args... It zeros out the remaining of the buffer..
> > + memcpy(, bufp, len);
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
signature.asc
Description: PGP signature
Hi, if there's a better place to report this then please advise
It seems the web-mail-list software for FreeBSD has failed partially (mostly?)
For example, these work, to display the subjects of messages
https://lists.freebsd.org/pipermail/freebsd-ports/2018-September/thread.html
cm's in 3.01s
> Doing aes-256-gcm for 3s on 1024 size blocks: 587396 aes-256-gcm's in 3.01s
> Doing aes-256-gcm for 3s on 8192 size blocks: 75806 aes-256-gcm's in 3.03s
> ...
> aes-256-gcm 62590.75k 135047.68k 181245.26k 199977.06k 204866.89k
--
John-Mark Gurney
On 9/17/18 11:32 AM, Michael Butler wrote:
> On 9/10/18 1:20 PM, John Baldwin wrote:
>> On 9/8/18 1:44 PM, Michael Butler wrote:
>>> On 9/8/18 3:43 PM, Konstantin Belousov wrote:
>>>> On Sat, Sep 08, 2018 at 02:07:41PM -0400, Michael Butler wrote:
>>>>
error booting FreeBSD/riscv in qemu.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
it
doesn't I'd check for a BIOS option disabling it).
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubsc
2 users would have hassles getting kgdb to work?
No, this means that if you turn this option on in HEAD and leave it always
on (as I read your mail to say), then it would be a hassle for developers
on head. On stable branches it would be nice to keep the info if people
are building kernel
er/firewall with few actual applications running.
>>>
>>> As another data point, I manually reversed both SVN r338360 and r338415
>>> (a related change) and it is now stable running at SVN r338520,
>>
>&g
tree the extra info is useful to
have. For better or worse, kgdb also parses the path to try to find
kernel.full (used by e.g. 'kgdb -n last'), so if you remove the path it
won't be able to find the matching kernel using its current logic.
crashinfo uses
On Sun, Sep 02, 2018 at 07:58:16AM +1200, Jonathan Chen wrote:
> On 2 September 2018 at 05:25, Alex McKeever
> wrote:
> > After compiling PKG, when I go to ports to compile anything (my eMac can
> > run FreeBSD but not modern Linux due to the version of the Radeon GPU) it
> > fails to retrieve
interrupt_sorted),
Probably just needs #ifdef SMP around the mallocarray(). I'll test locallyon a
UP kernel config.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
h
Hi,
On Sun, 26 Aug 2018, at 13:02, Tomoaki AOKI wrote:
> Hi, John.
> It's broken again by r338318. (Previously broken by r338107.)
>
> If your previous src rev is older, you could be bitten by these.
> If so, update ports tree at latest rev and try the latest single patch
> be
Hello,
On Sun, 26 Aug 2018, at 12:12, Kubilay Kocak wrote:
> On 26/08/2018 9:07 pm, John wrote:
> > Hello lists,
> >
> > x11/nvidia-driver is broken again.
> >
> > Context: FreeBSD-12-ALPHA3 r338323 / ports 478102 / amd64.
> >
> > Tried to bui
Hello lists,
x11/nvidia-driver is broken again.
Context: FreeBSD-12-ALPHA3 r338323 / ports 478102 / amd64.
Tried to build with make distclean clean rmconfig && make MAKE_JOBS_UNSAFE=yes
It fails here:
=kernel -Wno-sign-compare -Wno-format-extra-args -UDEBUG -U_DEBUG -DNDEBUG
-Werror=undef
longer mimic the layout on the host,
such as syslog.d being "flattened".)
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
o that maybe Brett has a chance to upgrade
> to 12.0, unless this sounds familiar to someone and the cause is
> obvious. =)
I would start with bisecting the changes to libi386/biosdisk.c. Also,
comparing 'lsdev -v' output between old and new loaders might be a useful
step before starting on the bisecting.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
e/rescue
>> [...]
>>
>>
>> This problem occured during today's source updates since I was able to build
>> the NanoBSD
>> image I intend to build yesterday ~ r338060.
>>
>> What is going wrong?
>
> It seems the problem has been intr
loader,
>> or is this a change with the recent default switch?
>>
>> And to be clear, you expect the host's file to be used for this, not the VM
>> filesystem?
>>
>
> (CC'ing jhb@ and tychon@, who might have better insight)
>
> If
think of no sound reason that you should be
>>> forced to use modules.
>> I thought that ZFS was required to be a module because of the licensing
>> terms (they didn't want any CDDL code in the core kernel)?
>>
>
> It can't be in _GENERIC_ for that reason. Ther
On 8/17/18 9:54 AM, Michael Gmelin wrote:
>
>
>> On 17. Aug 2018, at 08:17, John Baldwin wrote:
>>
>>> On 8/16/18 1:58 PM, Michael Gmelin wrote:
>>>
>>>
>>>> On 15. Aug 2018, at 15:55, Konstantin Belousov >>> <mailto:kosti
t - so the previous fix just worked due to a bug it seems.
>
> Is there an easy way to output the content of physmap at that point
> (debug.late_console=0 doesn’t work) - like an existing buffer I could use, or
> would this be more elaborate (I did something complicated last time b
failed to set bus width
Instruction Set Attributes 1 = <>
Processor Features 0 =
Comments?
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
_
> Revision: Revision: 337343
The core dumps don't really do me any good unfortunately without a binary,
but if you can open fortune.core under gdb for example, just getting the
stack trace along with 'info reg' is probably sufficient.
> Erich
>
>
> On Wed, 8 Aug 2018 08:57:06 -
ically due to an exception occuring before
> IDT is set up and trap machinery operational. Double-check that
> there is no any early framebuffer access, as a drastic measure remove
> all framebuffer drivers from your kernel config.
>
> I
On 8/7/18 7:00 PM, Erich Dollansky wrote:
> Hi,
>
> On Tue, 7 Aug 2018 11:59:11 -0700
> John Baldwin wrote:
>
>> On 8/6/18 8:11 PM, Erich Dollansky wrote:
>>> On Mon, 6 Aug 2018 15:57:53 -0700
>>> John Baldwin wrote:
>>>
>>>> On
On 8/6/18 8:11 PM, Erich Dollansky wrote:
> Hi,
>
> On Mon, 6 Aug 2018 15:57:53 -0700
> John Baldwin wrote:
>
>> On 8/4/18 4:38 PM, Erich Dollansky wrote:
>>> Hi,
>>>
>>> I compiled me yesterday this system:
>>>
>>> 12.0-CURREN
t; Lars Schotte
> > > Mudro??ova 13
> > > 92101 Pieany
> > > ___
> > > freebsd-current@freebsd.org mailing list
> > > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > > To unsubscr
;
> Bad system call (core dumped)
>
> Trying to install ports results in the same effect.
>
> Erich
Did you upgrade from stable/11 with a world that is still stable/11?
If so, did you make sure your kernel config includes COMPAT_FREEBSD11?
I decided that it was better to fix our stdatomic.h, so I have a review
to do that at https://reviews.freebsd.org/D16585
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
ight be to fix sys/cdefs.h
and sys/stdatomic.h to actually work with modern GCC by having them not
use the struct for the _GCC_ATOMICS case, only for the _SYNC case.
I think that would fix all of the cases.
--
John Baldwin
___
freebsd-current@free
der for the
> directories for now.
I finally got the approval 2 days ago to remove float.h from amd64-gcc so
you shouldn't need this reverted anymore once the OFED thing is
straightened out.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On 7/26/18 10:55 AM, Mark Millard wrote:
>
>
> On 2018-Jul-26, at 10:21 AM, John Baldwin wrote:
>
>> On 7/25/18 6:52 PM, Mark Millard wrote:
>>>
>>>
>>> On 2018-Jul-25, at 2:10 PM, Mark Millard wrote:
>>>
>>>
>>>
>>
On 7/25/18 6:52 PM, Mark Millard wrote:
>
>
> On 2018-Jul-25, at 2:10 PM, Mark Millard wrote:
>
>
>
>> On 2018-Jul-25, at 10:09 AM, Mark Millard wrote:
>>
>>> On 2018-Jul-25, at 8:39 AM, John Baldwin wrote:
>>>
>>>> On 7/24/18 11:
201 - 300 of 4518 matches
Mail list logo
