Re: Building modules gives error: "invalid output constraint '=@cce' in asm"
HI Andriy Gapon, Thanks. It works. On Wed, Jun 17, 2020 at 11:53 AM Andriy Gapon wrote: > On 17/06/2020 04:53, Rajesh Kumar wrote: > > Then, I am trying to compile the driver modules and hit the > > compilation error. I haven't done "install world" as I don't want the > base > > 12.0 to be disturbed. > > You should do `make buildenv` and then do the module build in the subshell. > This way you will be using a compiler (toolchain, in general) form the > buildworld, not the currently installed compiler. > > -- > Andriy Gapon > ___ 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"
Re: Building modules gives error: "invalid output constraint '=@cce' in asm"
Hi,
Has anyone faced a similar issue?
I had a 12.0-RELEASE kernel earlier. I cloned the master branch and built
world, built kernel and installed kernel with a different kernel name
(INSTKERNNAME) and rebooted the machine and see it booting to 13.0-CURRENT
as expected. Then, I am trying to compile the driver modules and hit the
compilation error. I haven't done "install world" as I don't want the base
12.0 to be disturbed.
When I compared the /usr/include/machine/atomic.h and the atomic.h from the
OBJ directory, I see the below highlighted change. Looks like, building
module is trying to use the headers in OBJ directory as expected, but
hitting the compilation issue.
*12.0 base installation atomic.h*
static __inline int \
atomic_fcmpset_##TYPE(volatile u_##TYPE *dst, u_##TYPE *expect, u_##TYPE
src) \
{ \
u_char res; \
\
__asm __volatile( \
" " MPLOCKED "" \
" cmpxchg %3,%1 ; " \
" sete%0 ;" \
"# atomic_fcmpset_" #TYPE " " \
*: "=q" (res), /* 0 */ \ *
"+m" (*dst), /* 1 */ \
"+a" (*expect)/* 2 */ \
: "r" (src) /* 3 */ \
: "memory", "cc"); \
return (res); \
}
*13.0- CURRENT atomic.h in OBJ dir*
static __inline int \
atomic_fcmpset_##TYPE(volatile u_##TYPE *dst, u_##TYPE *expect, u_##TYPE
src) \
{ \
u_char res; \
\
__asm __volatile( \
" " MPLOCKED "" \
"# atomic_fcmpset_" #TYPE " " \
*: "=@cce" (res),/* 0 */ \*
"+m" (*dst), /* 1 */ \
"+a" (*expect)/* 2 */ \
: "r" (src) /* 3 */ \
: "memory", "cc"); \
return (res); \
}
Any clue would be really helpful?
Thanks,
Rajesh
On Tue, Jun 16, 2020 at 12:29 PM Rajesh Kumar wrote:
> Hi,
>
> I am trying to build my module with freebsd current branch. But I am
> facing compilation issue with header files as below. I have built and
> installed the freebsd current branch and booted to that kernel before
> building my module. So, not sure what is going wrong.
>
>
>
>
>
>
> *In file included from
> /root//freebsd_current/sys/sys/systm.h:44:./machine/atomic.h:230:1: error:
> invalid output constraint '=@cce' in
> asmATOMIC_CMPSET(char);^./machine/atomic.h:205:4: note: expanded from macro
> 'ATOMIC_CMPSET': "=@cce" (res),/* 0 */ \*
>
> Am I missing something?
>
> Thanks,
> Rajesh.
>
___
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"
Building modules gives error: "invalid output constraint '=@cce' in asm"
Hi, I am trying to build my module with freebsd current branch. But I am facing compilation issue with header files as below. I have built and installed the freebsd current branch and booted to that kernel before building my module. So, not sure what is going wrong. *In file included from /root//freebsd_current/sys/sys/systm.h:44:./machine/atomic.h:230:1: error: invalid output constraint '=@cce' in asmATOMIC_CMPSET(char);^./machine/atomic.h:205:4: note: expanded from macro 'ATOMIC_CMPSET': "=@cce" (res),/* 0 */ \* Am I missing something? Thanks, Rajesh. ___ 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"
Re: Has anything changed from 11.2 to 12.0 in PCI MSI/MSIX path?
Thanks John. I tried building a kernel with these changes and things are working good. I could able to boot without any tunables. Thanks again. On Fri, Nov 2, 2018 at 12:05 AM John Baldwin wrote: > 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 complete or > tag me in necessary place? So that I can give a try in my board once it's > ready. > > I just committed r340016 which merges r338360 along with followup fixes to > stable/11. > > > On Mon, Oct 29, 2018 at 11:08 PM John Baldwin j...@freebsd.org>> wrote: > > > > 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 > see them still in stable/11 branch. So, will it be taken into stable/11 > branch by any chance? If not, can the backported changes be submitted for > review to take into stable/11 branch? > > > > I'm working on the MFC. The current patch I've tested an MFC of is > the one to > > unify sys/x86/include/intr_machdep.h as a precursor to MFC'ing this > change. > > > > > On Thu, Oct 25, 2018 at 1:17 AM John Baldwin <mailto:j...@freebsd.org> <mailto:j...@freebsd.org <mailto:j...@freebsd.org>>> > wrote: > > > > > > On 10/24/18 3:40 AM, Rajesh Kumar wrote: > > > > Hi, > > > > > > > > I have a amd64 based board. When I tried to boot 11.1 (or) > 11.2 in that, I > > > > needed the following tunables to be set from loader prompt > to get it booted > > > > (otherwise machine reboots continuously). > > > > > > > > hw.usb.xhci.msi=0 > > > > hw.usb.xhci.msix=0 > > > > hw.pci.enable_msi=0 > > > > hw.pci.enable_msix=0 > > > > > > > > But, when I tried with 12.0 - ALPHA4, I could able to get it > booted without > > > > any tunables. So, has anything changed significantly on PCI > MSI/MSI-X > > > > path? > > > > > > > > Note: I have a forum topic with 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 > > > > > > > > > -- > > John Baldwin > > > > > -- > 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"
Re: Has anything changed from 11.2 to 12.0 in PCI MSI/MSIX path?
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 complete or tag me in necessary place? So that I can give a try in my board once it's ready. On Mon, Oct 29, 2018 at 11:08 PM John Baldwin wrote: > 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 see > them still in stable/11 branch. So, will it be taken into stable/11 branch > by any chance? If not, can the backported changes be submitted for review > to take into stable/11 branch? > > I'm working on the MFC. The current patch I've tested an MFC of is the > one to > unify sys/x86/include/intr_machdep.h as a precursor to MFC'ing this change. > > > On Thu, Oct 25, 2018 at 1:17 AM John Baldwin j...@freebsd.org>> wrote: > > > > On 10/24/18 3:40 AM, Rajesh Kumar wrote: > > > Hi, > > > > > > I have a amd64 based board. When I tried to boot 11.1 (or) 11.2 in > that, I > > > needed the following tunables to be set from loader prompt to get > it booted > > > (otherwise machine reboots continuously). > > > > > > hw.usb.xhci.msi=0 > > > hw.usb.xhci.msix=0 > > > hw.pci.enable_msi=0 > > > hw.pci.enable_msix=0 > > > > > > But, when I tried with 12.0 - ALPHA4, I could able to get it > booted without > > > any tunables. So, has anything changed significantly on PCI > MSI/MSI-X > > > path? > > > > > > Note: I have a forum topic with 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 > > > > > -- > 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"
Re: Facing kernel panic during early boot from 12.0 ALPHA9
Thanks Mark. On Sat, Oct 27, 2018 at 12:29 AM Mark Johnston wrote: > On Fri, Oct 26, 2018 at 07:35:14PM +0530, Rajesh Kumar wrote: > > Hi Mark, > > > > Thanks for the inputs. With the two patches you pointed out, I could able > > to compile from current, install and boot properly without any panic. > > > > Will these changes be taken into stable/12 and be part of upcoming 12.0 > > releases? > > Yes, I will attempt to get them into 12.0. > > > On Thu, Oct 25, 2018 at 11:01 PM Mark Johnston > wrote: > > > > > On Tue, Oct 23, 2018 at 07:10:02PM +0530, Rajesh Kumar wrote: > > > > Hi Mark, > > > > > > > > > From the db> prompt, could you please run "show page" and "show > pageq", > > > > > and post the output? > > > > > > > > The system gets hung when it runs to db prompt. I only have the > option to > > > > force shutdown at that point. Is there any other way, I can collect > what > > > > you need? > > > > > > Just a followup for the list: the issue should be fixed by the > > > following two patches: > > > https://reviews.freebsd.org/D17418 > > > https://reviews.freebsd.org/D17704 > > > > ___ 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"
Re: Facing kernel panic during early boot from 12.0 ALPHA9
Hi Mark, Thanks for the inputs. With the two patches you pointed out, I could able to compile from current, install and boot properly without any panic. Will these changes be taken into stable/12 and be part of upcoming 12.0 releases? On Thu, Oct 25, 2018 at 11:01 PM Mark Johnston wrote: > On Tue, Oct 23, 2018 at 07:10:02PM +0530, Rajesh Kumar wrote: > > Hi Mark, > > > > > From the db> prompt, could you please run "show page" and "show pageq", > > > and post the output? > > > > The system gets hung when it runs to db prompt. I only have the option to > > force shutdown at that point. Is there any other way, I can collect what > > you need? > > Just a followup for the list: the issue should be fixed by the > following two patches: > https://reviews.freebsd.org/D17418 > https://reviews.freebsd.org/D17704 > ___ 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"
Re: Has anything changed from 11.2 to 12.0 in PCI MSI/MSIX path?
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 see them still in stable/11 branch. So, will it be taken into stable/11 branch by any chance? If not, can the backported changes be submitted for review to take into stable/11 branch? On Thu, Oct 25, 2018 at 1:17 AM John Baldwin wrote: > On 10/24/18 3:40 AM, Rajesh Kumar wrote: > > Hi, > > > > I have a amd64 based board. When I tried to boot 11.1 (or) 11.2 in that, > I > > needed the following tunables to be set from loader prompt to get it > booted > > (otherwise machine reboots continuously). > > > > hw.usb.xhci.msi=0 > > hw.usb.xhci.msix=0 > > hw.pci.enable_msi=0 > > hw.pci.enable_msix=0 > > > > But, when I tried with 12.0 - ALPHA4, I could able to get it booted > without > > any tunables. So, has anything changed significantly on PCI MSI/MSI-X > > path? > > > > Note: I have a forum topic with 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 > ___ 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"
Has anything changed from 11.2 to 12.0 in PCI MSI/MSIX path?
Hi, I have a amd64 based board. When I tried to boot 11.1 (or) 11.2 in that, I needed the following tunables to be set from loader prompt to get it booted (otherwise machine reboots continuously). hw.usb.xhci.msi=0 hw.usb.xhci.msix=0 hw.pci.enable_msi=0 hw.pci.enable_msix=0 But, when I tried with 12.0 - ALPHA4, I could able to get it booted without any tunables. So, has anything changed significantly on PCI MSI/MSI-X path? Note: I have a forum topic with 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. ___ 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"
Re: Facing kernel panic during early boot from 12.0 ALPHA9
Hi Mark,
Please find attached the "sysctl vm" output with ALPHA8.
On Tue, Oct 23, 2018 at 7:21 PM Mark Johnston wrote:
> On Tue, Oct 23, 2018 at 07:10:02PM +0530, Rajesh Kumar wrote:
> > Hi Mark,
> >
> > > From the db> prompt, could you please run "show page" and "show pageq",
> > > and post the output?
> >
> > The system gets hung when it runs to db prompt. I only have the option to
> > force shutdown at that point. Is there any other way, I can collect what
> > you need?
>
> Could you instead provide output from "sysctl vm" while the system has
> booted ALPHA8?
>
> > On Tue, Oct 23, 2018 at 7:05 PM Mark Johnston wrote:
> >
> > > On Tue, Oct 23, 2018 at 05:43:15PM +0530, Rajesh Kumar wrote:
> > > > Hi,
> > > >
> > > > I have a amd64 based board, where I could able to install upto
> FreeBSD
> > > 12.0
> > > > ALPHA8 without issues. But starting ALPHA9, I start to see the below
> > > panic
> > > > during early boot. Looks like some sleep at unwanted place. I am
> using
> > > > the memstick image from dowload page.
> > > >
> > > > Please let me know if you need any details.
> > >
> > > I'm having trouble seeing what might have changed between ALPHA8 and 9
> > > to cause this. At this point we've initialized the vm_phys page
> > > allocator, so we're not constrained by vm.boot_pages.
> > >
> > > From the db> prompt, could you please run "show page" and "show pageq",
> > > and post the output?
> > >
>
vm.vmtotal:
System wide totals computed every five seconds: (values in kilobytes)
===
Processes: (RUNQ: 1 Disk Wait: 0 Page Wait: 0 Sleep: 24)
Virtual Memory: (Total: 538514992K Active: 538502056K)
Real Memory:(Total: 48344K Active: 47656K)
Shared Virtual Memory: (Total: 23912K Active: 11004K)
Shared Real Memory: (Total: 9888K Active: 9224K)
Free Memory:64594236K
vm.loadavg: { 0.14 0.06 0.02 }
vm.v_free_min: 102837
vm.v_free_target: 347448
vm.v_free_reserved: 21300
vm.v_inactive_target: 521172
vm.v_pageout_free_min: 34
vm.swap_enabled: 1
vm.overcommit: 0
vm.domain.0.pidctrl.kdd: 8
vm.domain.0.pidctrl.kid: 4
vm.domain.0.pidctrl.kpd: 3
vm.domain.0.pidctrl.bound: 5559168
vm.domain.0.pidctrl.interval: 100
vm.domain.0.pidctrl.setpoint: 347448
vm.domain.0.pidctrl.ticks: 2146949887
vm.domain.0.pidctrl.output: 0
vm.domain.0.pidctrl.input: 16148569
vm.domain.0.pidctrl.derivative: 34
vm.domain.0.pidctrl.integral: 0
vm.domain.0.pidctrl.olderror: -15801155
vm.domain.0.pidctrl.error: -15801121
vm.domain.0.stats.free_severe: 62068
vm.domain.0.stats.free_min: 102837
vm.domain.0.stats.free_reserved: 21300
vm.domain.0.stats.free_target: 347448
vm.domain.0.stats.inactive_target: 521172
vm.domain.0.stats.unswppdpgs: 0
vm.domain.0.stats.unswappable: 0
vm.domain.0.stats.laundpdpgs: 0
vm.domain.0.stats.laundry: 0
vm.domain.0.stats.inactpdpgs: 0
vm.domain.0.stats.inactive: 525
vm.domain.0.stats.actpdpgs: 273
vm.domain.0.stats.active: 4886
vm.domain.0.stats.free_count: 16148553
vm.kvm_free: 2195460190208
vm.kvm_size: 2199023251456
vm.pmap.ad_emulation_superpage_promotions: 0
vm.pmap.num_superpage_accessed_emulations: 0
vm.pmap.num_accessed_emulations: 0
vm.pmap.num_dirty_emulations: 0
vm.pmap.pdpe.demotions: 3
vm.pmap.pde.promotions: 797
vm.pmap.pde.p_failures: 0
vm.pmap.pde.mappings: 0
vm.pmap.pde.demotions: 390
vm.pmap.pcid_save_cnt: 0
vm.pmap.pti: 0
vm.pmap.invpcid_works: 0
vm.pmap.pcid_enabled: 0
vm.pmap.pg_ps_enabled: 1
vm.pmap.pat_works: 1
vm.swap_idle_threshold2: 10
vm.swap_idle_threshold1: 2
vm.swap_idle_enabled: 0
vm.reserv.reclaimed: 0
vm.reserv.partpopq:
DOMAINLEVEL SIZE NUMBER
0, -1, 251088K,128
vm.reserv.fullpop: 121
vm.reserv.freed: 7952
vm.reserv.broken: 0
vm.ndomains: 1
vm.phys_locality:
0: -1
vm.phys_segs:
SEGMENT 0:
start: 0x1
end: 0x9f000
domain:0
free list: 0x8204fe30
SEGMENT 1:
start: 0x10
end: 0x100
domain:0
free list: 0x8204fe30
SEGMENT 2:
start: 0x100
end: 0x270f000
domain:0
free list: 0x8204fbc0
SEGMENT 3:
start: 0x2717000
end: 0x274c000
domain:0
free list: 0x8204fbc0
SEGMENT 4:
start: 0x280
end: 0x728e
domain:0
free list: 0x8204fbc0
SEGMENT 5:
start: 0x7290a000
end: 0x7877d000
domain:0
free list: 0x8204fbc0
SEGMENT 6:
start: 0x79e78000
end: 0x79eac000
domain:0
free list: 0x8204fbc0
SEGMENT 7:
start: 0x7a681000
end: 0x7c00
domain:0
free list: 0x8204fbc0
SEGMENT 8:
start: 0x1
end: 0x1015cb3000
domain:
Re: Facing kernel panic during early boot from 12.0 ALPHA9
Hi Mark, > From the db> prompt, could you please run "show page" and "show pageq", > and post the output? The system gets hung when it runs to db prompt. I only have the option to force shutdown at that point. Is there any other way, I can collect what you need? On Tue, Oct 23, 2018 at 7:05 PM Mark Johnston wrote: > On Tue, Oct 23, 2018 at 05:43:15PM +0530, Rajesh Kumar wrote: > > Hi, > > > > I have a amd64 based board, where I could able to install upto FreeBSD > 12.0 > > ALPHA8 without issues. But starting ALPHA9, I start to see the below > panic > > during early boot. Looks like some sleep at unwanted place. I am using > > the memstick image from dowload page. > > > > Please let me know if you need any details. > > I'm having trouble seeing what might have changed between ALPHA8 and 9 > to cause this. At this point we've initialized the vm_phys page > allocator, so we're not constrained by vm.boot_pages. > > From the db> prompt, could you please run "show page" and "show pageq", > and post the output? > ___ 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"
Facing kernel panic during early boot from 12.0 ALPHA9
Hi, I have a amd64 based board, where I could able to install upto FreeBSD 12.0 ALPHA8 without issues. But starting ALPHA9, I start to see the below panic during early boot. Looks like some sleep at unwanted place. I am using the memstick image from dowload page. Please let me know if you need any details. *Panic logs :* GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb ---<>--- Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of the The FreeBSD Foundation. FreeBSD 12.0-ALPHA9 r339271 GENERIC amd64 FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1) WARNING: WITNESS option enabled, expect reduced performance. panic: vm_wait in early boot cpuid = 0 time = 1 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0x827098d0 vpanic() at vpanic+0x1a3/frame 0x82709930 panic() at panic+0x43/frame 0x82709990 vm_wait_domain() at vm_wait_domain+0xf9/frame 0x827099c0 vm_domain_alloc_fail() at vm_domain_alloc_fail+0x94/frame 0x827099f0 vm_page_alloc_domain_after() at vm_page_alloc_domain_after+0x274/frame 0x82709a60 uma_small_alloc() at uma_small_alloc+0x6e/frame 0x82709a90 keg_alloc_slab() at keg_alloc_slab+0xf0/frame 0x82709af0 uma_prealloc() at uma_prealloc+0x92/frame 0x82709b30 vm_map_startup() at vm_map_startup+0x5f/frame 0x82709b40 vm_mem_init() at vm_mem_init+0x32/frame 0x82709b50 mi_startup() at mi_startup+0x118/frame 0x82709b70 btext() at btext+0x2c KDB: enter: panic [ thread pid 0 tid 0 ] Stopped at kdb_enter+0x3b: movq $0,kdb_why db> ___ 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"
Is there a standard way to check patch before submitting for review or upstreaming?
Hi, Do we have any standard tools/process in FreeBSD to check/validate the patch for basic issues before we submit them for review or upstreaming? Basically, something like checkpatch.pl in Linux. Thanks, Rajesh. ___ 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"
Re: FreeBSD -CURRENT on AMD Ryzen5
Hi Jake, Please try setting hw.pci.mcfg=0 from the boot loader and see if it helps. On Tue, Sep 4, 2018 at 2:34 AM Jake Champlin wrote: > Testing out various BSD's with a Huawei Matebook D, and FreeBSD -CURRENT is > failing to boot from an installer image. No serial console, so unable to > grab full boot output, any other info or boot flags that would help would > be awesome. > https://i.imgur.com/WAqwbza.jpg, shows where boot process hangs, and fails > to move past. > > Thanks > ___ > freebsd-hack...@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > ___ 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"
