r352368 can't boot

2019-09-16 Thread KIRIYAMA Kazuhiko 
Hi,all

Yesterday I've updated latest head (r352368) and rebuild
13.0-CURRENT. All went fine, but when I boot, it's stopped
at boot stage. Then I typed `boot', booted normally and put
login prompt and login go ahead. But `shutdown -r now',
stopped at loader prompt same as login case. What happened?
All I've done is whithin bhyve VM.

root@vm:~ # vm start tbedfc
Starting tbedfc
  * found guest in /vm/tbedfc
  * booting...
root@vm:~ # vm console tbedfc
Connected

OK boot
/boot/kernel/kernel text=0x16d7bdc data=0x1c8af8+0x64e118 
syms=[0x8+0x182778+0x8+0x19fc7a]
/boot/entropy size=0x1000
Booting...
GDB: no debug ports present
KDB: debugger backends: ddb
KDB: current backend: ddb
---<>---
Copyright (c) 1992-2019 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 FreeBSD Foundation.
FreeBSD 13.0-CURRENT #0 r352368: Mon Sep 16 13:37:27 JST 2019
root@tbedfc:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 
8.0.1)
WARNING: WITNESS option enabled, expect reduced performance.
VT: init without driver.
CPU: Intel(R) Xeon(R) CPU E3-1230 v6 @ 3.50GHz (3503.56-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x906e9  Family=0x6  Model=0x9e  Stepping=9
  
Features=0x9f83fbff
  
Features2=0xfeda7a17
  AMD Features=0x24100800
  AMD Features2=0x121
  Structured Extended 
Features=0xf39
  XSAVE Features=0x1
  TSC: P-state invariant
Hypervisor: Origin = "bhyve bhyve "
real memory  = 5368709120 (5120 MB)
avail memory = 4090740736 (3901 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: 
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
random: unblocking device.
ioapic0  irqs 0-31
Timecounter "TSC-low" frequency 1751779076 Hz quality 1000
random: entropy device external interface
kbd1 at kbdmux0
000.42 [4335] netmap_init   netmap: loaded module
module_register_init: MOD_LOAD (vesa, 0x811bcfa0, 0) error 19
[ath_hal] loaded
nexus0
cryptosoft0: 
acpi0: 
acpi0: Power Button (fixed)
atrtc0:  port 0x70-0x71 irq 8 on acpi0
atrtc0: registered as a time-of-day clock, resolution 1.00s
Event timer "RTC" frequency 32768 Hz quality 0
attimer0:  port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
hpet0:  iomem 0xfed0-0xfed003ff on acpi0
Timecounter "HPET" frequency 16777216 Hz quality 950
Event timer "HPET" frequency 16777216 Hz quality 550
Event timer "HPET1" frequency 16777216 Hz quality 450
Event timer "HPET2" frequency 16777216 Hz quality 450
Event timer "HPET3" frequency 16777216 Hz quality 450
Event timer "HPET4" frequency 16777216 Hz quality 450
Event timer "HPET5" frequency 16777216 Hz quality 450
Event timer "HPET6" frequency 16777216 Hz quality 450
Event timer "HPET7" frequency 16777216 Hz quality 450
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
virtio_pci0:  port 0x2000-0x203f mem 
0xc000-0xc0001fff irq 16 at device 4.0 on pci0
vtblk0:  on virtio_pci0
vtblk0: 8192MB (16777216 512 byte sectors)
virtio_pci1:  port 0x2040-0x205f mem 
0xc0002000-0xc0003fff irq 17 at device 5.0 on pci0
vtnet0:  on virtio_pci1
vtnet0: Ethernet address: 58:9c:fc:0c:10:58
vtnet0: netmap queues/slots: TX 1/1024, RX 1/512
000.000150 [ 503] vtnet_netmap_attach   vtnet attached txq=1, txd=1024 
rxq=1, rxd=512
isab0:  at device 31.0 on pci0
isa0:  on isab0
atkbdc0:  port 0x60,0x64 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
driver bug: Unable to set devclass (class: atkbdc devname: (unknown))
psm0:  irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model Generic PS/2 mouse, device ID 0
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: console (9600,n,8,1)
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
vga0:  at port 0x3b0-0x3bb iomem 0xb-0xb7fff pnpid PNP0900 
on isa0
Timecounters tick every 10.000 msec
usb_needs_explore_all: no devclass
WARNING: WITNESS option enabled, expect reduced performance.
Trying to mount root from ufs:/dev/vtbd0p2 [rw]...
Setting hostuuid: fd03833b-4ce8-11e8-a966-589cfc0c1058.
Setting hostid: 0x13d7974a.
Starting file system checks:
/dev/vtbd0p2: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/vtbd0p2: clean, 376431 free (7015 frags, 46177 blocks, 0.6% fragmentation)
Mounting local filesystems:.
ELF ldconfig path: /lib /usr/lib /usr/lib/compat
32-bit compatibility ldconfig path: /usr/lib32
Setting hostname: tbedfc.
Setting up harvesting: 
PURE_RDRAND,[UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,[NET_ETHER],NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED
Feeding entropy: .
lo0: link state changed to UP
vtnet0: link state changed to UP
Starting Network: lo0 vtn

Re: r352368 can't boot

2019-09-16 Thread Toomas Soome 



> On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko  wrote:
> 
> Hi,all
> 
> Yesterday I've updated latest head (r352368) and rebuild
> 13.0-CURRENT. All went fine, but when I boot, it's stopped
> at boot stage. Then I typed `boot', booted normally and put
> login prompt and login go ahead. But `shutdown -r now',
> stopped at loader prompt same as login case. What happened?
> All I've done is whithin bhyve VM.
> 
> 


> Consoles: userboot  
> 
> FreeBSD/amd64 User boot, Revision 1.1
> (Mon Jun 18 16:11:55 UTC 2018 r...@releng3.nyi.freebsd.org)
> Loading /boot/defaults/loader.conf
> xemit not found
> Error while including /boot/frames.4th, in the line:
>h_el @ xemit
> 
> can't load 'kernel'
> 
> Type '?' for a list of commands, 'help' for more detailed help.
> OK 
> 

This is unfortunate case where the guest image has more recent boot scripts 
than hosts /boot/userboot.so has. I did push the fix for that issue to 
stable/11 and stable/12. The patch does introduce xemit word.

Such situation is unfortunate, but accident waiting to happen with this method 
where we are attempting to use bootloader (userboot.so) from older system to 
load  guest vm. 

rgds,
toomas

___
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: r352368 can't boot

2019-09-17 Thread Warner Losh 
On Tue, Sep 17, 2019, 6:47 AM Toomas Soome  wrote:

>
>
> > On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko  wrote:
> >
> > Hi,all
> >
> > Yesterday I've updated latest head (r352368) and rebuild
> > 13.0-CURRENT. All went fine, but when I boot, it's stopped
> > at boot stage. Then I typed `boot', booted normally and put
> > login prompt and login go ahead. But `shutdown -r now',
> > stopped at loader prompt same as login case. What happened?
> > All I've done is whithin bhyve VM.
> >
> >
>
>
> > Consoles: userboot
> >
> > FreeBSD/amd64 User boot, Revision 1.1
> > (Mon Jun 18 16:11:55 UTC 2018 r...@releng3.nyi.freebsd.org)
> > Loading /boot/defaults/loader.conf
> > xemit not found
> > Error while including /boot/frames.4th, in the line:
> >h_el @ xemit
> >
> > can't load 'kernel'
> >
> > Type '?' for a list of commands, 'help' for more detailed help.
> > OK
> >
>
> This is unfortunate case where the guest image has more recent boot
> scripts than hosts /boot/userboot.so has. I did push the fix for that issue
> to stable/11 and stable/12. The patch does introduce xemit word.
>
> Such situation is unfortunate, but accident waiting to happen with this
> method where we are attempting to use bootloader (userboot.so) from older
> system to load  guest vm.
>

Can we provide a fallback to xemit builtin for old systems without it? I
believe we did this for other things as a transition. Forth has a way to do
this, though we need to make sure we properly constrain what we pass to
emit...

Warner

P.s. I'm at legoland this week, so I can't look at it for a bit.


rgds,
> toomas
>
> ___
> 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"
>
___
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: r352368 can't boot

2019-09-17 Thread Toomas Soome 



> On 17 Sep 2019, at 13:09, Warner Losh  wrote:
> 
> 
> 
> On Tue, Sep 17, 2019, 6:47 AM Toomas Soome  > wrote:
> 
> 
> > On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko  > > wrote:
> > 
> > Hi,all
> > 
> > Yesterday I've updated latest head (r352368) and rebuild
> > 13.0-CURRENT. All went fine, but when I boot, it's stopped
> > at boot stage. Then I typed `boot', booted normally and put
> > login prompt and login go ahead. But `shutdown -r now',
> > stopped at loader prompt same as login case. What happened?
> > All I've done is whithin bhyve VM.
> > 
> > 
> 
> 
> > Consoles: userboot  
> > 
> > FreeBSD/amd64 User boot, Revision 1.1
> > (Mon Jun 18 16:11:55 UTC 2018 r...@releng3.nyi.freebsd.org 
> > )
> > Loading /boot/defaults/loader.conf
> > xemit not found
> > Error while including /boot/frames.4th, in the line:
> >h_el @ xemit
> > 
> > can't load 'kernel'
> > 
> > Type '?' for a list of commands, 'help' for more detailed help.
> > OK 
> > 
> 
> This is unfortunate case where the guest image has more recent boot scripts 
> than hosts /boot/userboot.so has. I did push the fix for that issue to 
> stable/11 and stable/12. The patch does introduce xemit word.
> 
> Such situation is unfortunate, but accident waiting to happen with this 
> method where we are attempting to use bootloader (userboot.so) from older 
> system to load  guest vm. 
> 
> Can we provide a fallback to xemit builtin for old systems without it? I 
> believe we did this for other things as a transition. Forth has a way to do 
> this, though we need to make sure we properly constrain what we pass to 
> emit...
> 
> Warner
> 
> P.s. I'm at legoland this week, so I can't look at it for a bit.
> 

Well, the only way to avoid such issue is to make sure the guest environment is 
providing all the needed bits, but since we do have interpreter inside the 
userboot.so and userboot.so is in host, this does set rather unfortunate limits 
what we can do.

rgds,
toomas
___
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: r352368 can't boot

2019-09-17 Thread Warner Losh 
On Tue, Sep 17, 2019, 11:24 AM Toomas Soome  wrote:

>
>
> On 17 Sep 2019, at 13:09, Warner Losh  wrote:
>
>
>
> On Tue, Sep 17, 2019, 6:47 AM Toomas Soome  wrote:
>
>>
>>
>> > On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko  wrote:
>> >
>> > Hi,all
>> >
>> > Yesterday I've updated latest head (r352368) and rebuild
>> > 13.0-CURRENT. All went fine, but when I boot, it's stopped
>> > at boot stage. Then I typed `boot', booted normally and put
>> > login prompt and login go ahead. But `shutdown -r now',
>> > stopped at loader prompt same as login case. What happened?
>> > All I've done is whithin bhyve VM.
>> >
>> >
>>
>>
>> > Consoles: userboot
>> >
>> > FreeBSD/amd64 User boot, Revision 1.1
>> > (Mon Jun 18 16:11:55 UTC 2018 r...@releng3.nyi.freebsd.org)
>> > Loading /boot/defaults/loader.conf
>> > xemit not found
>> > Error while including /boot/frames.4th, in the line:
>> >h_el @ xemit
>> >
>> > can't load 'kernel'
>> >
>> > Type '?' for a list of commands, 'help' for more detailed help.
>> > OK
>> >
>>
>> This is unfortunate case where the guest image has more recent boot
>> scripts than hosts /boot/userboot.so has. I did push the fix for that issue
>> to stable/11 and stable/12. The patch does introduce xemit word.
>>
>> Such situation is unfortunate, but accident waiting to happen with this
>> method where we are attempting to use bootloader (userboot.so) from older
>> system to load  guest vm.
>>
>
> Can we provide a fallback to xemit builtin for old systems without it? I
> believe we did this for other things as a transition. Forth has a way to do
> this, though we need to make sure we properly constrain what we pass to
> emit...
>
> Warner
>
> P.s. I'm at legoland this week, so I can't look at it for a bit.
>
>
> Well, the only way to avoid such issue is to make sure the guest
> environment is providing all the needed bits, but since we do have
> interpreter inside the userboot.so and userboot.so is in host, this does
> set rather unfortunate limits what we can do.
>

Yes. I understand that we are limited in our scripts to somehow testing if
xemit is a forth word and if not providing a fallback implementation of it
in forth using emit.

Warner

rgds,
> toomas
>
___
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: r352368 can't boot

2019-09-17 Thread Toomas Soome 



> On 17 Sep 2019, at 14:21, Warner Losh  wrote:
> 
> 
> 
> On Tue, Sep 17, 2019, 11:24 AM Toomas Soome  > wrote:
> 
> 
>> On 17 Sep 2019, at 13:09, Warner Losh > > wrote:
>> 
>> 
>> 
>> On Tue, Sep 17, 2019, 6:47 AM Toomas Soome > > wrote:
>> 
>> 
>> > On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko > > > wrote:
>> > 
>> > Hi,all
>> > 
>> > Yesterday I've updated latest head (r352368) and rebuild
>> > 13.0-CURRENT. All went fine, but when I boot, it's stopped
>> > at boot stage. Then I typed `boot', booted normally and put
>> > login prompt and login go ahead. But `shutdown -r now',
>> > stopped at loader prompt same as login case. What happened?
>> > All I've done is whithin bhyve VM.
>> > 
>> > 
>> 
>> 
>> > Consoles: userboot  
>> > 
>> > FreeBSD/amd64 User boot, Revision 1.1
>> > (Mon Jun 18 16:11:55 UTC 2018 r...@releng3.nyi.freebsd.org 
>> > )
>> > Loading /boot/defaults/loader.conf
>> > xemit not found
>> > Error while including /boot/frames.4th, in the line:
>> >h_el @ xemit
>> > 
>> > can't load 'kernel'
>> > 
>> > Type '?' for a list of commands, 'help' for more detailed help.
>> > OK 
>> > 
>> 
>> This is unfortunate case where the guest image has more recent boot scripts 
>> than hosts /boot/userboot.so has. I did push the fix for that issue to 
>> stable/11 and stable/12. The patch does introduce xemit word.
>> 
>> Such situation is unfortunate, but accident waiting to happen with this 
>> method where we are attempting to use bootloader (userboot.so) from older 
>> system to load  guest vm. 
>> 
>> Can we provide a fallback to xemit builtin for old systems without it? I 
>> believe we did this for other things as a transition. Forth has a way to do 
>> this, though we need to make sure we properly constrain what we pass to 
>> emit...
>> 
>> Warner
>> 
>> P.s. I'm at legoland this week, so I can't look at it for a bit.
>> 
> 
> Well, the only way to avoid such issue is to make sure the guest environment 
> is providing all the needed bits, but since we do have interpreter inside the 
> userboot.so and userboot.so is in host, this does set rather unfortunate 
> limits what we can do.
> 
> Yes. I understand that we are limited in our scripts to somehow testing if 
> xemit is a forth word and if not providing a fallback implementation of it in 
> forth using emit.
> 
> 

done:)

rgds,
toomas


___
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: r352368 can't boot

2019-09-18 Thread Warner Losh 
On Wed, Sep 18, 2019, 7:37 AM Toomas Soome  wrote:

>
>
> On 17 Sep 2019, at 14:21, Warner Losh  wrote:
>
>
>
> On Tue, Sep 17, 2019, 11:24 AM Toomas Soome  wrote:
>
>>
>>
>> On 17 Sep 2019, at 13:09, Warner Losh  wrote:
>>
>>
>>
>> On Tue, Sep 17, 2019, 6:47 AM Toomas Soome  wrote:
>>
>>>
>>>
>>> > On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko  wrote:
>>> >
>>> > Hi,all
>>> >
>>> > Yesterday I've updated latest head (r352368) and rebuild
>>> > 13.0-CURRENT. All went fine, but when I boot, it's stopped
>>> > at boot stage. Then I typed `boot', booted normally and put
>>> > login prompt and login go ahead. But `shutdown -r now',
>>> > stopped at loader prompt same as login case. What happened?
>>> > All I've done is whithin bhyve VM.
>>> >
>>> >
>>>
>>>
>>> > Consoles: userboot
>>> >
>>> > FreeBSD/amd64 User boot, Revision 1.1
>>> > (Mon Jun 18 16:11:55 UTC 2018 r...@releng3.nyi.freebsd.org)
>>> > Loading /boot/defaults/loader.conf
>>> > xemit not found
>>> > Error while including /boot/frames.4th, in the line:
>>> >h_el @ xemit
>>> >
>>> > can't load 'kernel'
>>> >
>>> > Type '?' for a list of commands, 'help' for more detailed help.
>>> > OK
>>> >
>>>
>>> This is unfortunate case where the guest image has more recent boot
>>> scripts than hosts /boot/userboot.so has. I did push the fix for that issue
>>> to stable/11 and stable/12. The patch does introduce xemit word.
>>>
>>> Such situation is unfortunate, but accident waiting to happen with this
>>> method where we are attempting to use bootloader (userboot.so) from older
>>> system to load  guest vm.
>>>
>>
>> Can we provide a fallback to xemit builtin for old systems without it? I
>> believe we did this for other things as a transition. Forth has a way to do
>> this, though we need to make sure we properly constrain what we pass to
>> emit...
>>
>> Warner
>>
>> P.s. I'm at legoland this week, so I can't look at it for a bit.
>>
>>
>> Well, the only way to avoid such issue is to make sure the guest
>> environment is providing all the needed bits, but since we do have
>> interpreter inside the userboot.so and userboot.so is in host, this does
>> set rather unfortunate limits what we can do.
>>
>
> Yes. I understand that we are limited in our scripts to somehow testing if
> xemit is a forth word and if not providing a fallback implementation of it
> in forth using emit.
>
>
>
> done:)
>

Thanks

Warner

rgds,
> toomas
>
>
>
>
___
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"