Re: beadm vs bectl

On 8/27/18 3:22 PM, Allan Jude wrote: On 2018-08-27 14:50, Pete Wright wrote: hi there - i have a zfs based system where /boot is on its own pool. beadm seems happy enough with this setup but bectl errors out like so: $ sudo bectl list / and /boot not on same device, quitting $ $ beadm list

Re: intr_machdep.c:176:2: error: use of undeclared identifier 'interrupt_sorted'

I moved the #ifdef down one line and its compiling. Ian -- Ian Freislich On 08/29/2018 07: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

Re: intr_machdep.c:176:2: error: use of undeclared identifier 'interrupt_sorted'

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 undeclared > identifier 'interrupt_sorted';

intr_machdep.c:176:2: error: use of undeclared identifier 'interrupt_sorted'

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 undeclared identifier 'interrupt_sorted'; did you mean 'interrupt_sources'?    

Re: r336921 broke booting on MBP 2017, EFIRT related

I met similar panic on my ASUS ROG GL553VE: module_register_init: MOD_LOAD (vesa, 0x80a9dd30, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" nexus0 Fatal trap 12: page fault while in kernel mode cpuid = 7; apic id = 07 fault

Re: old top and new -current: missing arcstat sysctl

On 2018-08-29 11:18, Mark Johnston wrote: > On Wed, Aug 29, 2018 at 07:44:31AM +0200, Alexander Leidinger wrote: >> >> Quoting Mark Johnston (from Tue, 28 Aug 2018 >> 10:48:42 -0400): >> >>> On Tue, Aug 28, 2018 at 10:25:39AM -0400, Allan Jude wrote: On 2018-08-28 02:40, Alexander

Re: r336921 broke booting on MBP 2017, EFIRT related

On Wed, Aug 29, 2018 at 07:17:07PM +0300, Yuri Pankov wrote: > Konstantin Belousov wrote: > > On Wed, Aug 29, 2018 at 09:12:37AM -0500, Kyle Evans wrote: > >> I guess this patch might do it: > >> https://people.freebsd.org/~kevans/efi-bootmap.diff > >> > >> Linux commit messages depict a tale in

Re: r336921 broke booting on MBP 2017, EFIRT related

Konstantin Belousov wrote: On Wed, Aug 29, 2018 at 09:12:37AM -0500, Kyle Evans wrote: I guess this patch might do it: https://people.freebsd.org/~kevans/efi-bootmap.diff Linux commit messages depict a tale in which they used to also only map RUNTIME entries, but they were effectively forced

Re: old top and new -current: missing arcstat sysctl

On Wed, Aug 29, 2018 at 07:44:31AM +0200, Alexander Leidinger wrote: > > Quoting Mark Johnston (from Tue, 28 Aug 2018 > 10:48:42 -0400): > > > On Tue, Aug 28, 2018 at 10:25:39AM -0400, Allan Jude wrote: > >> On 2018-08-28 02:40, Alexander Leidinger wrote: > >> > Hi, > >> > > >> > top reports

Re: r336921 broke booting on MBP 2017, EFIRT related

On Wed, Aug 29, 2018 at 09:12:37AM -0500, Kyle Evans wrote: > I guess this patch might do it: > https://people.freebsd.org/~kevans/efi-bootmap.diff > > Linux commit messages depict a tale in which they used to also only > map RUNTIME entries, but they were effectively forced to back down on >

Re: r336921 broke booting on MBP 2017, EFIRT related

On Wed, Aug 29, 2018 at 6:53 AM Yuri Pankov wrote: > > Yuri Pankov wrote: > > Konstantin Belousov wrote: > >> On Wed, Aug 29, 2018 at 12:37:52PM +0300, Yuri Pankov wrote: > >>> Hi, > >>> > >>> I've noticed that all recent snapshots (ALPHA3, ALPHA2, ALPHA1, > >>> 20180802) fail to boot on MBP

Re: r336921 broke booting on MBP 2017, EFIRT related

Am 29.08.18 um 15:25 schrieb Kyle Evans: > On Wed, Aug 29, 2018 at 8:20 AM Rainer Hurling wrote: >> >> Am 29.08.18 um 11:37 schrieb Yuri Pankov: >>> Hi, >>> >>> I've noticed that all recent snapshots (ALPHA3, ALPHA2, ALPHA1, >>> 20180802) fail to boot on MBP 2017: >>> >>> kbd0 at kbdmux0 >>>

Re: r336921 broke booting on MBP 2017, EFIRT related

On Wed, Aug 29, 2018 at 8:20 AM Rainer Hurling wrote: > > Am 29.08.18 um 11:37 schrieb Yuri Pankov: > > Hi, > > > > I've noticed that all recent snapshots (ALPHA3, ALPHA2, ALPHA1, > > 20180802) fail to boot on MBP 2017: > > > > kbd0 at kbdmux0 > > netmap: loaded module > > nexus0 > > > > Fatal

Re: r336921 broke booting on MBP 2017, EFIRT related

Am 29.08.18 um 11:37 schrieb Yuri Pankov: > Hi, > > I've noticed that all recent snapshots (ALPHA3, ALPHA2, ALPHA1, > 20180802) fail to boot on MBP 2017: > > kbd0 at kbdmux0 > netmap: loaded module > nexus0 > > Fatal trap 12: page fault while in kernel mode > cpuid = 2: apic id = 02 > fault

Re: r336921 broke booting on MBP 2017, EFIRT related

> On 29 Aug 2018, at 14:53, Yuri Pankov wrote: > > Yuri Pankov wrote: >> Konstantin Belousov wrote: >>> On Wed, Aug 29, 2018 at 12:37:52PM +0300, Yuri Pankov wrote: Hi, I've noticed that all recent snapshots (ALPHA3, ALPHA2, ALPHA1, 20180802) fail to boot on MBP 2017:

Re: r336921 broke booting on MBP 2017, EFIRT related

> On 29 Aug 2018, at 15:05, Toomas Soome wrote: > > > >> On 29 Aug 2018, at 14:53, Yuri Pankov > > wrote: >> >> Yuri Pankov wrote: >>> Konstantin Belousov wrote: On Wed, Aug 29, 2018 at 12:37:52PM +0300, Yuri Pankov wrote: > Hi, > > I've noticed

Re: r336921 broke booting on MBP 2017, EFIRT related

Yuri Pankov wrote: Konstantin Belousov wrote: On Wed, Aug 29, 2018 at 12:37:52PM +0300, Yuri Pankov wrote: Hi, I've noticed that all recent snapshots (ALPHA3, ALPHA2, ALPHA1, 20180802) fail to boot on MBP 2017: kbd0 at kbdmux0 netmap: loaded module nexus0 Fatal trap 12: page fault while in

Re: r336921 broke booting on MBP 2017, EFIRT related

Konstantin Belousov wrote: On Wed, Aug 29, 2018 at 12:37:52PM +0300, Yuri Pankov wrote: Hi, I've noticed that all recent snapshots (ALPHA3, ALPHA2, ALPHA1, 20180802) fail to boot on MBP 2017: kbd0 at kbdmux0 netmap: loaded module nexus0 Fatal trap 12: page fault while in kernel mode cpuid =

Re: Current and nvidia-driver again

For me it did not solve the problem. 29.08.2018 1:03, tech-lists пишет: > On 28/08/2018 10:14, Alex V. Petrov wrote: >> /usr/src Revision: 338342 >> >> >> ===>  Building for nvidia-driver-390.77 > > Hi, > > Have you tried applying the patch at >

Re: r336921 broke booting on MBP 2017, EFIRT related

On Wed, Aug 29, 2018 at 12:37:52PM +0300, Yuri Pankov wrote: > Hi, > > I've noticed that all recent snapshots (ALPHA3, ALPHA2, ALPHA1, > 20180802) fail to boot on MBP 2017: > > kbd0 at kbdmux0 > netmap: loaded module > nexus0 > > Fatal trap 12: page fault while in kernel mode > cpuid = 2: apic

r336921 broke booting on MBP 2017, EFIRT related

Hi, I've noticed that all recent snapshots (ALPHA3, ALPHA2, ALPHA1, 20180802) fail to boot on MBP 2017: kbd0 at kbdmux0 netmap: loaded module nexus0 Fatal trap 12: page fault while in kernel mode cpuid = 2: apic id = 02 fault virtual address = 0x74c64a50 fault code = supervisor

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

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 boots. > > > > > > Before

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

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 (machdep.c), physmap looks

Re: old top and new -current: missing arcstat sysctl

Quoting Eitan Adler (from Tue, 28 Aug 2018 22:54:04 -0700): On Tue, 28 Aug 2018 at 22:46, Alexander Leidinger wrote: > > IIRC that would have been the inverted case of running a newer top(1) > with an older kernel lacking the v_laundry_pages sysctl. In general I'd > expect us to support

Re: r336876 breaks sysutils/acpi_call

On 8/25/18 11:51 PM, Theron wrote: A recent change in CURRENT has sysutils/acpi_call reliably cause a kernel panic The problem is with the port itself, not with CURRENT.  A bug is filed accordingly. ___ freebsd-current@freebsd.org mailing list