On 11/2/19 5:15 PM, Toomas Soome wrote:
> Should be fixed by r354265.
The problem has moved .. now the kernel won't build ..
Building /usr/obj/usr/src/amd64.amd64/sys/VM01/avl.o
Building /usr/obj/usr/src/amd64.amd64/sys/VM01/lz4.o
--- lz4.o ---
cc: error: no such file or directory:
Something missing from SVN r354253?
Building /usr/obj/usr/src/amd64.amd64/rescue/rescue/rescue
ld: error: undefined symbol: lz4_init
>>> referenced by spa_misc.c:2066
(/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa_misc.c:2066)
>>> spa_misc.o:(spa_init) in archive
On 10/24/19 1:56 PM, Gleb Smirnoff wrote:
> On Thu, Oct 24, 2019 at 11:12:10AM -0400, Michael Butler wrote:
> M> The removal of these KPIs yields:
> M>
> M> link_elf_obj: symbol if_multiaddr_array undefined
> M> linker_load_file: /boot/modules/if_em_updated.ko - unsupp
The removal of these KPIs yields:
link_elf_obj: symbol if_multiaddr_array undefined
linker_load_file: /boot/modules/if_em_updated.ko - unsupported file type
imb
___
freebsd-current@freebsd.org mailing list
> On 13. Oct 2019, at 21:26, Michael Butler wrote:
>
> sys/net/route.c will no longer compile when VIMAGE is removed from the
> kernel,
That wasn't intended. Fixed in r353482.
Sorry for the breakage and thank you very much for reporting!
Best regards
Michael
&g
> On 13. Oct 2019, at 21:26, Michael Butler wrote:
>
> sys/net/route.c will no longer compile when VIMAGE is removed from the
> kernel,
Let me look at it...
Best regards
Michael
>
> imb
___
freebsd-current@freebsd.org
sys/net/route.c will no longer compile when VIMAGE is removed from the
kernel,
imb
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
In rc.d/sysvipc we see ..
name="sysvipc"
desc="Load SysV IPC modules"
rcvar="sysvipc_enable"
start_cmd="${name}_start"
.. so it won't try to run without explicitly setting sysvipc_enable in
/etc/rc.conf.
However in rc.d/linux, we have only ..
name="linux"
desc="Enable Linux ABI"
I also leave a bit of space at the
beginning and end of the drive (allows adding in a boot partition later or more
flexibility when replacing the drive).
Anyway, I’m curious what the exact problem will turn out to be.
Cheers,
Michael
>
>
> On 19. Sep 2019, at 17:57, Kurt Jaeger wrote:
>
> Hi!
>
>>> We have a system with 10 SATA disks. 2 disks are for the system,
>>> 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes:
>>>
>>> bck72.8T 38.7T 34.1T- - 1%53% 1.00x ONLINE
t;
> In (the most likely) case it's not helpful enough, I'm now running with dump
> device configured, and will update if/when the panic reproduces.
This panic should be fixed by:
https://svnweb.freebsd.org/changeset/base/352072
Please dr
On 9/8/19 7:09 PM, Alan Somers wrote:
> On Sun, Sep 8, 2019 at 5:00 PM Clay Daniels Jr.
> wrote:
>
>> I want to view my Windows C: drive on ata0p4.
>> This is what I have:
>> FreeBSD bsd13 13.0-CURRENT FreeBSD 13.0-CURRENT r351901 GENERIC amd64
>> clay@bsd13:~ % pkg info -r fusefs-libs
>>
On 2019-08-27 19:41, Michael Butler wrote:
> On 2019-08-27 19:15, Niclas Zeising wrote:
>> On 2019-08-28 00:38, Alexander Motin wrote:
>>> Hi.
>>>
>>> On 27.08.2019 18:03, Niclas Zeising wrote:
>>>> I have an issue where the ses driver no longer att
On 2019-08-27 19:15, Niclas Zeising wrote:
> On 2019-08-28 00:38, Alexander Motin wrote:
>> Hi.
>>
>> On 27.08.2019 18:03, Niclas Zeising wrote:
>>> I have an issue where the ses driver no longer attaches. Last known
>>> good version was r351188, r351544 is broken. In that interval,
>>>
Hi,
I have no tried (but it's in progress) this article:
http://zero-knowledge.org/post/126/
Hope it will help (for me too).
Thanks!
On Tue, Aug 27, 2019 at 11:25 AM O. Hartmann wrote:
> Hello list,
>
> trying to setup a poudriere jail on recent CURRENT and have some severe
> trouble.
>
> We
On 2019-08-24 19:09, Michael Butler wrote:
> On 2019-08-24 14:04, Konstantin Belousov wrote:
>> On Sat, Aug 24, 2019 at 11:02:20AM -0600, Warner Losh wrote:
>>> forward declaring struct pcpu; in md_var.h "fixes" this, but I'm not sure
>>> that's the
64__)
#include
+ #include
#include
#endif
#include
Locally, I've put this patch into graphics/drm-current-kmod/files so I
don't trip over it on subsequent builds,
Michael
___
freebsd-current@freebsd.org mailing list
https://lists.free
As follows ..
Building
/usr/obj/usr/src/amd64.amd64/sys/TOSHI/modules/usr/local/sys/modules/drm-current-kmod/linuxkpi/linux_compat.o
--- linux_compat.o ---
In file included from
/usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/src/linux_compat.c:5:
./machine/md_var.h:61:34: error:
> On 8. Aug 2019, at 15:52, Alan Somers wrote:
>
> On Thu, Aug 8, 2019 at 7:42 AM Michael Tuexen wrote:
>>
>>
>>
>>> On 8. Aug 2019, at 14:24, Slava Shwartsman wrote:
>>>
>>> Apparently, Bullseye are dropping support for FreeBSD.
>&g
> On 8. Aug 2019, at 16:16, Slava Shwartsman wrote:
>
>
>
> On 08-Aug-19 16:52, Alan Somers wrote:
>> On Thu, Aug 8, 2019 at 7:42 AM Michael Tuexen wrote:
>>>
>>>
>>>
>>>> On 8. Aug 2019, at 14:24, Slava Shwartsman wrote:
>
for you?
Have you looked into /dev/kcov. This is used by SYZKALLER for getting
coverage information from the kernel.
Best regards
Michael
>
>
> Slava
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman
As follows ..
--- kern_sysctl.o ---
/usr/src/sys/kern/kern_sysctl.c:1623:19: error: use of undeclared
identifier 'kdb_active'
if (arg2 == 0 || kdb_active) {
^
1 error generated.
*** [kern_sysctl.o] Error code 1
imb
> On 18. Jun 2019, at 12:56, Kubilay Kocak wrote:
>
> On 18/06/2019 5:42 pm, Michael Tuexen wrote:
>> Dear all,
>> I'm trying to run
>> sudo make buildworld
>> in a directory with r349168.
>> The result is:
>> cc -O2 -pipe -I/usr/home/tuexen/head
.
Any idea what is going wrong?
Best regards
Michael
___
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 2019-05-19 23:21, Johannes Lundberg wrote:
>
> On 5/19/19 7:36 PM, Steve Kargl wrote:
>> On Sun, May 19, 2019 at 02:50:54PM -0700, Johannes Lundberg wrote:
>>> LinuxKPI in base have received a lot of updates recently for Linux 5.0,
>>> a couple of them will break drm-current-kmod. So, as of
On 2019-05-09 14:38, Gleb Smirnoff wrote:
> On Thu, May 09, 2019 at 02:32:44PM -0400, Michael Butler wrote:
> M> (kgdb) frame 8
> M> #8 0x80a15377 in ip_output (m=, opt= M> optimized out>, ro=0x0, flags=0, imo=0xfe0072b14780, inp=0x0) at
> M> /usr/src/sys/
On 2019-05-09 14:22, Gleb Smirnoff wrote:
> Michael,
>
> On Thu, May 09, 2019 at 10:25:37AM -0500, Kyle Evans wrote:
> K> > #0 doadump () at src/sys/amd64/include/pcpu.h:241
> K> > #1 0x808393c8 in kern_reboot (howto=260) at
> K> > /usr/src/sy
On 2019-05-09 14:03, ossobser...@redchan.it wrote:
> Background: Apparently a FreeBSD developer, a viking looking fellow,
Further miscellaneous dribble elided ..
This has no place on this mailing list. Take your hate someplace else,
imb
___
On 2019-05-09 09:07, Kyle Evans wrote:
> On Thu, May 9, 2019 at 7:24 AM Michael Butler
> wrote:
>>
>> Seems there's a lock or tuntap issue after recent changes. Restarting
>> openvpn (configured to use /dev/tap) yields a panic as follows:
>>
>
> Ah, I knew
Seems there's a lock or tuntap issue after recent changes. Restarting
openvpn (configured to use /dev/tap) yields a panic as follows:
(kgdb) bt
#0 doadump () at src/sys/amd64/include/pcpu.h:241
#1 0x808393c8 in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:470
#2
> On 8. May 2019, at 18:13, Andrey V. Elsukov wrote:
>
> Hi,
>
> today I updated one of my test machines and discovered that message from
> the subject periodically printed in the console.
Fixed in https://svnweb.freebsd.org/changeset/base/347329
Best regards
Michael
>
&
='. /usr/src/lib/libbe'
1 error
Michael
___
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"
The removal of dma_mask (around line 105) in
/usr/src/sys/compat/linuxkpi/common/include/linux/device.h breaks the
DRM loadable modules :-(
As follows ..
--- amdgpu_amdkfd.o ---
/usr/ports/graphics/drm-current-kmod/work/kms-drm-068d6be/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:284:37:
error: no
On 2019-04-17 20:45, Ed Maste wrote:
> On Wed, 17 Apr 2019 at 17:31, Michael Butler
> wrote:
>>
>> There seems to be a missing include here?
>>
>> ===> usr.bin/strings (obj,all,install)
>> Building
>> /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/
There seems to be a missing include here?
===> usr.bin/strings (obj,all,install)
Building
/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/usr.bin/strings/strings.o
/usr/src/contrib/elftoolchain/strings/strings.c:198:55: error: use of
undeclared identifier 'FA_OPEN'
fa = fileargs_init(argc,
On 2019-04-09 09:30, O. Hartmann wrote:
> On Tue, 9 Apr 2019 10:42:47 +0200 (CEST)
> Trond Endrestøl wrote:
>
>> On Tue, 9 Apr 2019 10:06+0200, Trond Endrestøl wrote:
>>
>>> On Mon, 8 Apr 2019 19:58+0200, O. Hartmann wrote:
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Something changed in libxo that causes 'netstat -i' to segfault as below:
imb@toshi:/usr/src/usr.bin/netstat> lldb
/usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat
(lldb) target create "/usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat"
Current executable set to
As below .. an unused variable when KASSERT is not enabled ..
Building /usr/obj/usr/src/amd64.amd64/sys/TOSHI/fuse_ipc.o
--- fuse_ipc.o ---
/usr/src/sys/fs/fuse/fuse_ipc.c:223:22: error: unused variable 'ftick'
[-Werror,-Wunused-variable]
struct fuse_ticket *ftick = mem;
buildworld fails with ..
--- cddl/lib__L ---
Building
/usr/obj/usr/src/amd64.amd64/obj-lib32/cddl/lib/libzpool/vdev_initialize.o
--- lib__L ---
Building /usr/obj/usr/src/amd64.amd64/obj-lib32/lib/libsm/fscanf.o
Building /usr/obj/usr/src/amd64.amd64/obj-lib32/lib/libsm/fseek.o
---
As below ..
--- drm_atomic_helper.o ---
In file included from
/usr/ports/graphics/drm-current-kmod/work/kms-drm-78e51d0/drivers/gpu/drm/drm_atomic_helper.c:28:
In file included from
/usr/ports/graphics/drm-current-kmod/work/kms-drm-78e51d0/include/drm/drmP.h:139:
> On 18. Feb 2019, at 23:54, Mark Linimon wrote:
>
>> On Mon, Feb 18, 2019 at 08:50:27AM -0800, Rodney W. Grimes wrote:
>> I think one serious problem here is the summary dismissal of things
>> simply on the "5 year old" basis.
>
> IIUC the graphics changes are being forced upon FreeBSD by
On 1/12/19 5:12 AM, O. Hartmann wrote:
> Am Thu, 10 Jan 2019 22:22:05 +0100
> "O. Hartmann" schrieb:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>
>> Am Thu, 10 Jan 2019 12:02:15 -0800
>> Cy Schubert schrieb:
>
>>> I'm not able to reproduce this at the moment.
I can confirm that
As below:
Building /usr/obj/usr/src/i386.i386/sys/SARAH/kern_thr.o
Building /usr/obj/usr/src/i386.i386/sys/SARAH/kern_thread.o
--- kern_thread.o ---
/usr/src/sys/kern/kern_thread.c:105:1: error: static_assert failed
"struct thread KBI td_frame"
_Static_assert(offsetof(struct thread, td_frame) ==
I'm not lucky to reproduce it even if i use iwn and "sysctl
net.wlan.0.rate_stats"
Problem is related to 802.11n, but all my networks are 11g.
BR
On Thu, Jan 10, 2019 at 6:53 PM Michael Zhilin wrote:
> Hi,
>
> Is it possible to print out any local variables of frame #8?
Hi,
Is it possible to print out any local variables of frame #8?
Thx!
On Thu, Jan 10, 2019 at 6:31 PM Michael Butler
wrote:
> With 'device iwn' and all the related wireless bits compiled into a
> custom kernel for a laptop, executing 'sysctl -a' yields a kernel panic
> of
With 'device iwn' and all the related wireless bits compiled into a
custom kernel for a laptop, executing 'sysctl -a' yields a kernel panic
of the form ..
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x8
fault code = supervisor read
On 11/17/18 5:35 PM, Michael Butler wrote:
> Any clues as to what's broken here? I'm trying to build a CD and/or DVD
> image.
>
> My tree is at SVN r340525.
>
> --
>>>> Kernel build for GENERIC completed o
Any clues as to what's broken here? I'm trying to build a CD and/or DVD
image.
My tree is at SVN r340525.
--
>>> Kernel build for GENERIC completed on Sat Nov 17 22:19:48 UTC 2018
/sbin/unbound: Undefined symbol "sldns_key_EVP_load_gost_id"
The voices in my head mutter it's something about OpenSSL. But they're
usually wrong.
Here's my unbound.conf, just in case:
---
root-hints: "named.cache"
access-control: 0.0.0.0/0 allow
---
Thanks,
==ml
--
Michael W
Confirmed to be fixed by SVN r340134 - thanks!
On 11/4/18 1:50 PM, Michael Butler wrote:
> ===> libexec/dma/dma-mbox-create (all)
> Building
> /usr/obj/usr/src/amd64.amd64/libexec/dma/dma-mbox-create/dma-mbox-create.o
> In file included from /usr/src/contrib/dma/dma-mbox-create.c
===> libexec/dma/dma-mbox-create (all)
Building
/usr/obj/usr/src/amd64.amd64/libexec/dma/dma-mbox-create/dma-mbox-create.o
In file included from /usr/src/contrib/dma/dma-mbox-create.c:51:
/usr/obj/usr/src/amd64.amd64/tmp/usr/include/capsicum_helpers.h:161:1:
error: all paths through this function
When we try to enable the SR-IOV function of Network-Adapter in the
properties of the virtual machine, we get
f12rw kernel: hn0: got notify, nvs type 128
f12rw kernel: pcib0: on vmbus0
f12rw kernel: pcib0: failed to get resource for cfg window
f12rw kernel: device_attach: pcib0 attach returned 6
Hi Ernie,
On Thu, Oct 18, 2018 at 9:36 PM Ernie Luzar wrote:
> Wanting to get a head start on using 12.0 and vnet jails with in jail
> firewall.
>
> 1. Will Vimage be compiled as a module in the 12.0 kernel and be
> included in the base system release?
>
I suppose it's part of GENERIC kernel
On 10/9/18 11:14 PM, Michael Butler wrote:
> On 10/9/18 5:34 PM, Glen Barber wrote:
>> OpenSSL has been updated to version 1.1.1 as of r339270.
>>
>> It is important to rebuild third-party packages before running:
>>
>> # make -C /usr/src delete-old && mak
On 10/9/18 5:34 PM, Glen Barber wrote:
> OpenSSL has been updated to version 1.1.1 as of r339270.
>
> It is important to rebuild third-party packages before running:
>
> # make -C /usr/src delete-old && make -C /usr/src delete-old-libs
>
> Thank you for your patience while this work was in
On 10/9/18 3:18 PM, Dag-Erling Smørgrav wrote:
> Michael Butler writes:
>> Marek Zarychta writes:
>>> I have connected serial console to affected box and upgraded system
>>> from patched sources. I am sorry to say that this patch doesn't
>>> solve the iss
On 10/9/18 1:43 PM, Marek Zarychta wrote:
> W dniu 09.10.2018 o 01:28, Dag-Erling Smørgrav pisze:
>> Please try the attached patch. I expect it to fix i386. If it also
>> fixes arm32, all the better, although I don't quite see why it would.
>
> I have connected serial console to affected box
With an i386 system, ssh sessions to the updated sshd fail with:
sshd[28771]: fatal: mm_getpwnamallow: receive get struct passwd failed
[preauth]
This is reproducible on both real hardware and in a VM running an i386
build,
imb
___
,
Michael
___
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"
hink the preferred way to load i915kms is to use kld_list (might be
unrelated, but still).
pkg install drm-next-kmod
sysrc kld_list="/boot/modules/i915kms.ko"
Yours,
Michael
>
> --
> Andriy Gapon
> ___
> freebsd-current@free
> On 24. Sep 2018, at 12:42, Matthias Apitz wrote:
>
>> El día Monday, September 24, 2018 a las 10:31:38AM +0200, Matthias Apitz
>> escribió:
>>
>>
>> Hello,
>>
>> I've booted a fresh r338641 from an USB key on my Acer C720, and have
>> the required modules loaded at boot (cyapa and ig4)
eading bytes.
>
> What could be wrong?
Do you by any chance use vt(4) in vga textmode (hw.vga.textmode=1)?
vt doesn’t support hardware mouse cursors, so no cursor in text mode (see
https://wiki.freebsd.org/Newcons)
Best,
Michael
>
>matthias
> --
> Matthias Api
d64/i386 kernel
requires linker ifunc support
This is r338893.
amd64 works without any problem. So this is i386 specific. Any idea how to fix
it?
Best regards
Michael
>
> # All library objects contain FreeBSD revision strings by default; they
> may be
> # excluded as a space-
and see if the problem
is related to it...
Yes, if time and point in time permits, because that's a production server
and I can only mess around with it late night.
Michael
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman
> On 20. Sep 2018, at 19:11, Michael Schmiedgen wrote:
>
> Hi Michael,
>
> many thanks for your help.
>
>
> On 20.09.2018 18:15, Michael Tuexen wrote:
>>> On 20. Sep 2018, at 17:12, Michael Schmiedgen wrote:
>>>
>>>
>>>>
Hi Michael,
many thanks for your help.
On 20.09.2018 18:15, Michael Tuexen wrote:
On 20. Sep 2018, at 17:12, Michael Schmiedgen wrote:
Can you elaborate which port was triggering the fault and which platform you
are using?
I would like to reproduce the issue and fix it.
Port is devel
> On 20. Sep 2018, at 17:12, Michael Schmiedgen wrote:
>
>
>> Can you elaborate which port was triggering the fault and which platform you
>> are using?
>> I would like to reproduce the issue and fix it.
>
> Port is devel/apr1 and platform is amd64.
Works fin
compiling ports. But I
observed a crash two times exactly in the same place: configure script SCTP test
in devel/apr1.
Thanks,
Michael
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
> On 20. Sep 2018, at 14:18, Michael Schmiedgen wrote:
>
> Hi List,
>
> if compiling ports and configure script checks for SCTP with
>
> 'checking whether SCTP is supported...'
>
> 12.0-ALPHA6 dumps core with message:
>
> Fatal double fault
> rip 0xfff
I removed SCTP from kernel and updated from r338797 to r338827
and the problem seems to be gone.
Michael
On 20.09.2018 14:18, Michael Schmiedgen wrote:
Hi List,
if compiling ports and configure script checks for SCTP with
'checking whether SCTP is supported...'
12.0-ALPHA6 dumps core
panic: double fault
cpuid = 0
I can provide crash dumps if desired, but without debug information.
Thanks,
Michael
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
On 9/17/18 4:17 AM, Andrey V. Elsukov wrote:
> On 16.09.2018 03:04, Larry Rosenman wrote:
>> vpanic() at vpanic+0x1a3/frame 0xfe00ca17c150
>> panic() at panic+0x43/frame 0xfe00ca17c1b0
>> trap_fatal() at trap_fatal+0x35f/frame 0xfe00ca17c200
>> trap_pfault() at trap_pfault+0x49/frame
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:
>>>> On 8/31/18 1:28 AM, Konstantin Belousov wrote:
>>>>
On 9/15/18 8:04 PM, Larry Rosenman wrote:
> I've got 2 of these:
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 4; apic id = 04
> fault virtual address = 0x7c
> fault code = supervisor read data, page not present
> instruction pointer = 0x20:0x80631428
>
On Tue, Sep 11, 2018 at 06:55:56PM -0400, Shawn Webb wrote:
> On Tue, Sep 11, 2018 at 03:58:02PM -0400, Michael W. Lucas wrote:
> >
> > Hi,
> >
> > storm~;uname -a
> > FreeBSD storm 12.0-ALPHA4 FreeBSD 12.0-ALPHA4 #10 r338496: Thu Sep 6
> > 12:29:00 E
Path
9 loghost /jail/loghost
storm~;jexec 9 env | grep -i ssh
SSH_CLIENT=203.0.113.70 59076 22
SSH_CONNECTION=203.0.113.70 59076 203.0.113.50 22
SSH_TTY=/dev/pts/2
SSH_AUTH_SOCK=/tmp/ssh-ZfvZOatcsu/agent.60492
storm~;
Any ideas?
Tha
On 9/8/18 3:43 PM, Konstantin Belousov wrote:
> On Sat, Sep 08, 2018 at 02:07:41PM -0400, Michael Butler wrote:
>> On 8/31/18 1:28 AM, Konstantin Belousov wrote:
>>> On Fri, Aug 31, 2018 at 12:21:02AM -0400, Michael Butler wrote:
>>
>> [ .. snip .. ]
>>
&g
On 8/31/18 1:28 AM, Konstantin Belousov wrote:
> On Fri, Aug 31, 2018 at 12:21:02AM -0400, Michael Butler wrote:
[ .. snip .. ]
>> I see another problem after using Ian's workaround of moving the #ifdef
>> SMP; it seems I now run out of kernel stack on an i386 (Pentium-III)
>&
On 8/29/18 7:40 PM, John Baldwin wrote:
> On 8/29/18 4:20 PM, Ian FREISLICH wrote:
>> Hi
>>
>> I see the definition of interrupt_sorted is #ifdefed out by #ifdef SMP
>> at line 84. My system is UP so I'm not compiling an SMP kernel.
>>
>> /usr/src/sys/x86/x86/intr_machdep.c:176:2: error: use of
On Wed, 29 Aug 2018 11:21:05 +0200
Michael Gmelin wrote:
> On Sun, 26 Aug 2018 16:04:35 +0300
> Konstantin Belousov wrote:
>
> > On Sat, Aug 25, 2018 at 07:21:28PM +0200, Michael Gmelin wrote:
> > > Now, with the patch applied correctly, the machine actually bo
On Sun, 26 Aug 2018 16:04:35 +0300
Konstantin Belousov wrote:
> On Sat, Aug 25, 2018 at 07:21:28PM +0200, Michael Gmelin wrote:
> > Now, with the patch applied correctly, the machine actually boots.
> >
> > Before calling init_ops.mp_bootaddress in
> > getmemsize
>> On 24. Aug 2018, at 22:39, Konstantin Belousov wrote:
>>
>> On Fri, Aug 24, 2018 at 10:32:06PM +0200, Michael Gmelin wrote:
>>
>>
>>> On 24. Aug 2018, at 21:59, Konstantin Belousov wrote:
>>> Please apply the following debugging
> On 24. Aug 2018, at 21:59, Konstantin Belousov wrote:
>
>> On Thu, Aug 23, 2018 at 12:10:34AM +0200, Michael Gmelin wrote:
>>
>>
>>>> On 22. Aug 2018, at 23:15, Konstantin Belousov wrote:
>>>>
>>>> On Wed, Aug 22, 2018 at 10:0
m the boot prompt and reboot.
> After that, I rebooted without the fuse module in /boot/loader.conf and
> things work fine.
>
> I have tried to boot again with fuse in /boot/loader.conf, and the first
> boot I get to a mountroot
> prompt which I am now reading up on.
>
> Maybe t
> On 22. Aug 2018, at 23:15, Konstantin Belousov wrote:
>
>> On Wed, Aug 22, 2018 at 10:03:54PM +0200, Michael Gmelin wrote:
>>
>>
>>>> On 22. Aug 2018, at 17:46, Konstantin Belousov wrote:
>>>>
>>>> On Tue, Aug 21, 2018 at 12:1
> On 22. Aug 2018, at 17:46, Konstantin Belousov wrote:
>
>> On Tue, Aug 21, 2018 at 12:14:35AM +0200, Michael Gmelin wrote:
>>
>>
>>>> On 20. Aug 2018, at 17:09, Konstantin Belousov wrote:
>>>>
>>>> On Mon, Aug 20, 2018 at
> On 20. Aug 2018, at 17:09, Konstantin Belousov wrote:
>
>> On Mon, Aug 20, 2018 at 12:45:12AM +0200, Michael Gmelin wrote:
>>
>> See here for a screenshot (also including the output of "show pte
>> 0xf8000100"):
>>
>> https://gis
On Sun, 19 Aug 2018 19:16:42 +0300
Konstantin Belousov wrote:
> On Sun, Aug 19, 2018 at 04:59:51PM +0200, Michael Gmelin wrote:
> >
> >
> > On Fri, 17 Aug 2018 10:02:08 +0100
> > John Baldwin wrote:
> >
> > >
On Fri, 17 Aug 2018 10:02:08 +0100
John Baldwin wrote:
> 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 17. Aug 2018, at 12:13, Konstantin Belousov wrote:
>
>> On Fri, Aug 17, 2018 at 10:02:08AM +0100, John Baldwin wrote:
>>> On 8/17/18 9:54 AM, Michael Gmelin wrote:
>>>
>>>
>>>>> On 17. Aug 2018, at 08:17, John Baldwin 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:kostik...@gmail.com>> wrote:
>>>
>>>> On Wed, Aug 15, 201
> On 15. Aug 2018, at 15:55, Konstantin Belousov wrote:
>
>> On Wed, Aug 15, 2018 at 03:52:37PM +0200, Michael Gmelin wrote:
>>
>>
>>>> On 15. Aug 2018, at 15:04, Konstantin Belousov wrote:
>>>>
>>>> On Wed, Aug 15, 2018 at 12
> On 15. Aug 2018, at 15:04, Konstantin Belousov wrote:
>
>> On Wed, Aug 15, 2018 at 12:51:06AM +0200, Michael Gmelin wrote:
>> Reviving this old thread, since I just updated to r337818 and a similar
>> problem is happening again. Since the fix in
On Wed, 6 Jun 2018 01:06:25 +0200
Michael Gmelin wrote:
> On Tue, 5 Jun 2018 16:11:35 +0300
> Konstantin Belousov wrote:
>
> > On Mon, Jun 04, 2018 at 11:17:56PM +0200, Michael Gmelin wrote:
> > >
> > >
> > > On Mon, 4 Jun 2018 14:06
> On 14. Aug 2018, at 17:09, Kyle Evans wrote:
>
> On Tue, Aug 14, 2018 at 11:04 AM, Michael Tuexen wrote:
>> Dear all,
>>
>> r337761 panics on boot with a GENERIC kernel on a EPYC system:
>
> Oy. =(
>
>> [...]
>> panic: mutex pmap not o
d pid 0 tid 10 ]
Stopped at kdb_enter+0x3b: movq$0,kdb_why
db>
Any idea what is wrong?
Best regards
Michael
___
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"
non-SMP builds apparently don't define some required structures ..
--- kernel ---
linking kernel
ld: error: undefined symbol: cpu_info
>>> referenced by ucode.c
>>> ucode.o:(ucode_load_ap)
ld: error: undefined symbol: cpu_apic_ids
>>> referenced by ucode.c
>>>
Dear all,
the up-to-date indent translates a line like
bla._blub = 1;
into a line like
bla._ blub = 1;
(insert whitespace after _) which breaks C code... Older versions didn't do that
Is this change intended? If yes, is there a command line option to turn it off?
Best regards
Michael
Is anyone else seeing this when building a new kernel with ZFS compiled in?
Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vers.o
Building /usr/obj/usr/src/amd64.amd64/sys/VM01/kernel
--- kernel ---
linking kernel
ld: error: undefined symbol: dbuf_stats_init
>>> referenced by dbuf.c
>>>
make installworld results in ..
(cd /usr/src/etc; make MK_MAKE_CHECK_USE_SANDBOX=yes etc-examples)
cd /usr/src/etc; install -o root -g wheel -m 444 crontab devd.conf
devfs.conf ddb.conf dhclient.conf disktab fbtab gettytab group
hosts hosts.allow hosts.equiv libalias.conf libmap.conf
301 - 400 of 1690 matches
Mail list logo
