Logging boot messages from the loader

2019-11-21 Thread Eugene Grosbein
Hi! How do I get boot messages generated by loader itself written to some log after successfull boot? This is generic BIOS-based 11.3-STABLE/amd64 system with syscons console driver. /var/run/dmesg.boot starts with kernel messages without previous lines from the loader. Specifically, I need mes

Re: Logging boot messages from the loader

2019-11-21 Thread Bjoern A. Zeeb
On 21 Nov 2019, at 9:51, Eugene Grosbein wrote: Hi! How do I get boot messages generated by loader itself written to some log after successfull boot? This is generic BIOS-based 11.3-STABLE/amd64 system with syscons console driver. /var/run/dmesg.boot starts with kernel messages without prev

Re: Logging boot messages from the loader

2019-11-21 Thread Eugene Grosbein
21.11.2019 17:22, Bjoern A. Zeeb wrote: > On 21 Nov 2019, at 9:51, Eugene Grosbein wrote: > >> Hi! >> >> How do I get boot messages generated by loader itself written to some log >> after successfull boot? >> This is generic BIOS-based 11.3-STABLE/amd64 system with syscons console >> driver. >>

Re: Logging boot messages from the loader

2019-11-21 Thread David Wolfskill
On Thu, Nov 21, 2019 at 04:51:13PM +0700, Eugene Grosbein wrote: > Hi! > > How do I get boot messages generated by loader itself written to some log > after successfull boot? > This is generic BIOS-based 11.3-STABLE/amd64 system with syscons console > driver. > > /var/run/dmesg.boot starts with

device_attach: ixv0 attach returned 5

2019-11-21 Thread Michal Vančo via freebsd-stable
Hi, I’m trying to get SR-IOV working with my two port Intel 10G NIC: ix0@pci0:3:0:0: class=0x02 card=0x15ad15d9 chip=0x15ad8086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Ethernet Connection X552/X557-AT 10GBASE-T' class = network subclass = ethern

[NTP] "Unexpected origin timestamp 0xe180e455.d15bf3fb does not match aorg 0000000000.00000000 from server" (kernel reports TIME_ERROR: 0x41: Clock Unsynchronized)

2019-11-21 Thread Vinícius Zavam via freebsd-stable
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242137 -- Vinícius Zavam keybase.io/egypcio ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr

Re: Logging boot messages from the loader

2019-11-21 Thread Eugene Grosbein
21.11.2019 18:35, David Wolfskill wrote: >> How do I get boot messages generated by loader itself written to some log >> after successfull boot? >> This is generic BIOS-based 11.3-STABLE/amd64 system with syscons console >> driver. >> >> /var/run/dmesg.boot starts with kernel messages without pr

Re: Logging boot messages from the loader

2019-11-21 Thread Kyle Evans
On Thu, Nov 21, 2019 at 4:48 AM Eugene Grosbein wrote: > > 21.11.2019 17:22, Bjoern A. Zeeb wrote: > > > On 21 Nov 2019, at 9:51, Eugene Grosbein wrote: > > > >> Hi! > >> > >> How do I get boot messages generated by loader itself written to some log > >> after successfull boot? > >> This is gener

Re: device_attach: ixv0 attach returned 5

2019-11-21 Thread Michal Vančo via freebsd-stable
Well then this is really annoying. I can image few other applications besides virtualization. Jails using vnet bound to VF instead of epair being one of examples. Any hope that someone will port the SR-IOV from Intel’s code into the base driver on foreseeable future? regards Michal > On 21 Nov 2