building world via ccache broken?

2017-10-02 Thread Pete Wright 

hey there,
i've been unable to buildworld using ccache for a while.  initially i 
assumed it was due to some incompatibilities on the drm-next branch 
which i was running, but i've since cut over to CURRENT and am still 
having issues.  running "make buildworld" i am running into this exception:


/usr/home/pwright/git/freebsd/lib/libufs/cgroup.c:217:11: error: no 
member named 'fs_metackhash' in 'struct fs'

if ((fs->fs_metackhash & CK_CYLGRP) != 0) {
 ~~  ^


full exception here:
https://gist.github.com/nomadlogic/30771aacd05d6dbb1c0cbebfb2ef6b61

I am going to re-run this w/o ccache - to verify that this is a ccache 
related issue.  I guess my first question - is anyone else using ccache 
successfully?


thanks in advance!
-pete

--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
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 world via ccache broken?

2017-10-02 Thread Pete Wright 



On 10/02/2017 13:07, Pete Wright wrote:

hey there,
i've been unable to buildworld using ccache for a while. initially i 
assumed it was due to some incompatibilities on the drm-next branch 
which i was running, but i've since cut over to CURRENT and am still 
having issues.  running "make buildworld" i am running into this 
exception:


/usr/home/pwright/git/freebsd/lib/libufs/cgroup.c:217:11: error: no 
member named 'fs_metackhash' in 'struct fs'

    if ((fs->fs_metackhash & CK_CYLGRP) != 0) {
 ~~  ^


full exception here:
https://gist.github.com/nomadlogic/30771aacd05d6dbb1c0cbebfb2ef6b61

I am going to re-run this w/o ccache - to verify that this is a ccache 
related issue.  I guess my first question - is anyone else using 
ccache successfully?




fwiw building the world without ccache works as expected.  perhaps my 
make.conf is not correctly configured?


$ cat /etc/make.conf
.if !defined(NO_CCACHE)
  CC= /usr/local/libexec/ccache/world/cc
  CXX= /usr/local/libexec/ccache/world/c++
.endif

cheers,
-pete

--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA

___
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 world via ccache broken?

2017-10-02 Thread Pete Wright 



On 10/02/2017 16:33, Matt Joras wrote:

On 10/02/2017 15:23, Pete Wright wrote:


On 10/02/2017 13:07, Pete Wright wrote:

hey there,
i've been unable to buildworld using ccache for a while. initially i
assumed it was due to some incompatibilities on the drm-next branch
which i was running, but i've since cut over to CURRENT and am still
having issues.  running "make buildworld" i am running into this
exception:

/usr/home/pwright/git/freebsd/lib/libufs/cgroup.c:217:11: error: no
member named 'fs_metackhash' in 'struct fs'
     if ((fs->fs_metackhash & CK_CYLGRP) != 0) {
  ~~  ^


full exception here:
https://gist.github.com/nomadlogic/30771aacd05d6dbb1c0cbebfb2ef6b61

I am going to re-run this w/o ccache - to verify that this is a
ccache related issue.  I guess my first question - is anyone else
using ccache successfully?


fwiw building the world without ccache works as expected.  perhaps my
make.conf is not correctly configured?

$ cat /etc/make.conf
.if !defined(NO_CCACHE)
   CC= /usr/local/libexec/ccache/world/cc
   CXX= /usr/local/libexec/ccache/world/c++
.endif

cheers,
-pete


Someone can correct me if I'm wrong but I believe the current "correct"
way to get ccache builds is WITH_CCACHE_BUILD set in src.conf.
src.conf(5) seems to indicate as much as well. To answer your question,
yes, I am I'm sure many others are building world on HEAD with ccache
without issue.


thanks, i had another person point me in this direction - and after 
reading the man page it does indeed clearly state as much :)


what had tripped me up is that the ccache portfile installs:
/usr/local/share/doc/ccache/ccache-howto-freebsd.txt

which does not mention src.conf, but states:


To use ccache for base add the following to /etc/make.conf.
You can replace cc and c++ with the compilers of your choice.
(remember that only GCC and Clang can build world and kernel)

.if (!empty(.CURDIR:M/usr/src*) || !empty(.CURDIR:M/usr/obj*))
.if !defined(NOCCACHE) && exists(/usr/local/libexec/ccache/world/cc)
CC:=${CC:C,^cc,/usr/local/libexec/ccache/world/cc,1}
CXX:=${CXX:C,^c\+\+,/usr/local/libexec/ccache/world/c++,1}
.endif
.endif


if i'm able to successfully build my world and kernel via src.conf i'll 
file a PR against the ccache port.


cheers!
-pete

--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA

___
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 world via ccache broken?

2017-10-02 Thread Pete Wright 



On 10/02/2017 16:35, Pete Wright wrote:



On 10/02/2017 16:33, Matt Joras wrote:

On 10/02/2017 15:23, Pete Wright wrote:


On 10/02/2017 13:07, Pete Wright wrote:

hey there,
i've been unable to buildworld using ccache for a while. initially i
assumed it was due to some incompatibilities on the drm-next branch
which i was running, but i've since cut over to CURRENT and am still
having issues.  running "make buildworld" i am running into this
exception:

/usr/home/pwright/git/freebsd/lib/libufs/cgroup.c:217:11: error: no
member named 'fs_metackhash' in 'struct fs'
 if ((fs->fs_metackhash & CK_CYLGRP) != 0) {
  ~~  ^


full exception here:
https://gist.github.com/nomadlogic/30771aacd05d6dbb1c0cbebfb2ef6b61

I am going to re-run this w/o ccache - to verify that this is a
ccache related issue.  I guess my first question - is anyone else
using ccache successfully?


fwiw building the world without ccache works as expected. perhaps my
make.conf is not correctly configured?

$ cat /etc/make.conf
.if !defined(NO_CCACHE)
   CC= /usr/local/libexec/ccache/world/cc
   CXX= /usr/local/libexec/ccache/world/c++
.endif

cheers,
-pete


Someone can correct me if I'm wrong but I believe the current "correct"
way to get ccache builds is WITH_CCACHE_BUILD set in src.conf.
src.conf(5) seems to indicate as much as well. To answer your question,
yes, I am I'm sure many others are building world on HEAD with ccache
without issue.


thanks, i had another person point me in this direction - and after 
reading the man page it does indeed clearly state as much :)


what had tripped me up is that the ccache portfile installs:
/usr/local/share/doc/ccache/ccache-howto-freebsd.txt

which does not mention src.conf, but states:


To use ccache for base add the following to /etc/make.conf.
You can replace cc and c++ with the compilers of your choice.
(remember that only GCC and Clang can build world and kernel)

.if (!empty(.CURDIR:M/usr/src*) || !empty(.CURDIR:M/usr/obj*))
.if !defined(NOCCACHE) && exists(/usr/local/libexec/ccache/world/cc)
CC:=${CC:C,^cc,/usr/local/libexec/ccache/world/cc,1}
CXX:=${CXX:C,^c\+\+,/usr/local/libexec/ccache/world/c++,1}
.endif
.endif


if i'm able to successfully build my world and kernel via src.conf 
i'll file a PR against the ccache port.


cheers!
-pete



I can verify that this works on my system, firing off a PR now to the 
ports team to update documentation shortly :)


thanks for the input everyone.

-pete

--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA

___
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 world via ccache broken?

2017-10-02 Thread Matt Joras 
On 10/02/2017 15:23, Pete Wright wrote:
>
>
> On 10/02/2017 13:07, Pete Wright wrote:
>> hey there,
>> i've been unable to buildworld using ccache for a while. initially i
>> assumed it was due to some incompatibilities on the drm-next branch
>> which i was running, but i've since cut over to CURRENT and am still
>> having issues.  running "make buildworld" i am running into this
>> exception:
>>
>> /usr/home/pwright/git/freebsd/lib/libufs/cgroup.c:217:11: error: no
>> member named 'fs_metackhash' in 'struct fs'
>>     if ((fs->fs_metackhash & CK_CYLGRP) != 0) {
>>  ~~  ^
>>
>>
>> full exception here:
>> https://gist.github.com/nomadlogic/30771aacd05d6dbb1c0cbebfb2ef6b61
>>
>> I am going to re-run this w/o ccache - to verify that this is a
>> ccache related issue.  I guess my first question - is anyone else
>> using ccache successfully?
>>
>
> fwiw building the world without ccache works as expected.  perhaps my
> make.conf is not correctly configured?
>
> $ cat /etc/make.conf
> .if !defined(NO_CCACHE)
>   CC= /usr/local/libexec/ccache/world/cc
>   CXX= /usr/local/libexec/ccache/world/c++
> .endif
>
> cheers,
> -pete
>
Someone can correct me if I'm wrong but I believe the current "correct"
way to get ccache builds is WITH_CCACHE_BUILD set in src.conf.
src.conf(5) seems to indicate as much as well. To answer your question,
yes, I am I'm sure many others are building world on HEAD with ccache
without issue.

___
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: Build error: 'isa/rtc.h' file not found

2017-10-02 Thread O. Hartmann 
Am Mon, 2 Oct 2017 11:35:22 +0700
"Alex V. Petrov"  schrieb:

> revision 324186
> In file included from /usr/obj/usr/src/tmp/usr/include/sys/efi.h:33:
> /usr/obj/usr/src/tmp/usr/include/machine/efi.h:35:10: fatal error:
> 'isa/rtc.h' file not found

Me, too here.

-- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).


pgp_EamkvmUYq.pgp
Description: OpenPGP digital signature

Re: Build error: 'isa/rtc.h' file not found

2017-10-02 Thread Konstantin Belousov 
On Mon, Oct 02, 2017 at 09:44:36AM +0200, O. Hartmann wrote:
> Am Mon, 2 Oct 2017 11:35:22 +0700
> "Alex V. Petrov"  schrieb:
> 
> > revision 324186
> > In file included from /usr/obj/usr/src/tmp/usr/include/sys/efi.h:33:
> > /usr/obj/usr/src/tmp/usr/include/machine/efi.h:35:10: fatal error:
> > 'isa/rtc.h' file not found
> 
> Me, too here.
> 

I am only starting the build, but I believe that the following patch should
give the fix.


diff --git a/sys/amd64/include/efi.h b/sys/amd64/include/efi.h
index 75d39592e28..eaea8d03276 100644
--- a/sys/amd64/include/efi.h
+++ b/sys/amd64/include/efi.h
@@ -32,8 +32,6 @@
 #ifndef __AMD64_INCLUDE_EFI_H_
 #define __AMD64_INCLUDE_EFI_H_
 
-#include 
-
 /*
  * XXX: from gcc 6.2 manual:
  * Note, the ms_abi attribute for Microsoft Windows 64-bit targets
@@ -47,8 +45,12 @@
 #defineEFIABI_ATTR __attribute__((ms_abi))
 #endif
 
+#ifdef _KERNEL
+#include 
+
 #defineEFI_TIME_LOCK() mtx_lock(_time_lock);
 #defineEFI_TIME_UNLOCK()   mtx_unlock(_time_lock);
 #defineEFI_TIME_OWNED()mtx_assert(_time_lock, MA_OWNED);
+#endif
 
 #endif /* __AMD64_INCLUDE_EFI_H_ */
___
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"

ATAPI_IDENTIFY error while trying to install FreeBSD on Acer Veriton M421G

2017-10-02 Thread Elena Mihailescu 
Hello!

I am trying to install FreeBSD 12.0-CURRENT / FreeBSD 11.1-RELEASE on an
Acer Veriton M421G with AMD Athlon II X2 250 processor and M2N rev 1.02g
motherboard.

While booting from USB, it does not recognize the harddisk (a SATA HDD) and
I cannot continue the process of installation. I get the following error
periodically :


ahcich1: is 0002 cs  ss  rs 1000 tfd 50 serr
 cmd 00046c17
(aprobe0:ahcich1:0:0:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 00
00 00
(aprobe0:ahcich1:0:0:0): CAM status: Command timeout
(aprobe0:ahcich1:0:0:0): Error 5, Retries exhausted


A proper image with error showed on screen is here [1] and a dmesg output
obtained using  an USB device with FreeBSD installed on it can be found
here [2].

I mention that on this HDD I have successfully installed Linux Mint
Cinnamon 17.3 64 bit.

What I already did/checked:
- I checked SATA cables (DVD-ROM is connected as well on SATA and works
fine - I can boot from a CD and I tried to switch HDD and DVD-ROM cables).
- I tried another SATA HDD
- I tried different versions of FreeBSD (bootable USB and ISO CDs)
- Modify in BIOS the SATA mode: Native, Legacy and AHCI.
- I managed to install FreeBSD 11.1-Release on another USB device -
unfortunately this is not a solution - it runs very very slow. Also, this
way, I managed to get a dmesg output [2].
- I updated the BIOS.
- I tried what is described here [3]
- The only way this error is not displayed is when I disconnect both HDD
and DVD-ROM.
- BIOS system info is here [4]


Does anyone knows how I can solve this issue?

Thanks,
Elena

[1] https://drive.google.com/open?id=0B8qXIRloK7xeZk0zZFhlWFJWU3M
and https://drive.google.com/open?id=0B8qXIRloK7xeUlJwSTZUaXIxYlE
[2] https://drive.google.com/open?id=0B8qXIRloK7xeWGR3WXZFSXVkaFk
[3]
https://lists.freebsd.org/pipermail/freebsd-questions/2003-August/015096.html
[4] https://drive.google.com/open?id=0B8qXIRloK7xedVpYb0NuWVB6ODg
___
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: panic in AcpiOsGetTimer during boot.

2017-10-02 Thread Rick Macklem 
Conrad Meyer wrote:
> Are you running into the same issue reported on this svn-src thread?
> https://lists.freebsd.org/pipermail/svn-src-all/2017-September/151775.html
Yep, same panic().

> I believe jkim has reverted the change in a subsequent revision (r324136).
I'll try a post-r324136 kernel. If it still panics, I'll post again.

Thanks, rick
> Best,
> Conrad

On Sun, Oct 1, 2017 at 3:12 PM, Rick Macklem  wrote:
> Hi,
>
> I get the KASSERT panic in AcpiOsGetTimer() while booting a recent (2 day old)
> kernel. When I delete the KASSERT(), the kernel boots and seems to work ok.
> (This is the AcpiOsGetTimer() in sys/dev/acpica/Osd/OsdSchedule.c. There also
>  seems to be one of these functions under contrib.)
>
> Here is my dmesg after boot, if it helps indicate why this is called when 
> "cold"
> is still set. (I've marked where the dmesg ends when it Panics if the 
> KASSERT()
> is enabled.)
>
> dmesg after booting:
> Copyright (c) 1992-2017 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 12.0-CURRENT #1: Sun Oct  1 09:48:42 EDT 2017
> r...@nfsv4-newerlap.rick.home:/sub1/sys.headsep30/amd64/compile/GENERIC 
> amd64
> FreeBSD clang version 3.7.0 (tags/RELEASE_370/final 246257) 20150906
> WARNING: WITNESS option enabled, expect reduced performance.
> VT(vga): resolution 640x480
> CPU: Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz (2294.84-MHz K8-class CPU)
>   Origin="GenuineIntel"  Id=0x306a9  Family=0x6  Model=0x3a  Stepping=9
>   
> Features=0xbfebfbff
>   
> Features2=0x7fbae3bf
>   AMD Features=0x28100800
>   AMD Features2=0x1
>   Structured Extended Features=0x281
>   XSAVE Features=0x1
>   VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
>   TSC: P-state invariant, performance statistics
> real memory  = 17179869184 (16384 MB)
> avail memory = 16518905856 (15753 MB)
> Event timer "LAPIC" quality 600
> ACPI APIC Table: <_ASUS_ Notebook>
> FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
> FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 hardware threads
> random: unblocking device.
> arc4random: no preloaded entropy cache
> ioapic0  irqs 0-23 on motherboard
> SMP: AP CPU #1 Launched!
> SMP: AP CPU #3 Launched!
> SMP: AP CPU #7 Launched!
> SMP: AP CPU #6 Launched!
> SMP: AP CPU #4 Launched!
>  dmesg ends here when in KASSERT() panics.
> SMP: AP CPU #5 Launched!
> SMP: AP CPU #2 Launched!
> Timecounter "TSC-low" frequency 1147419696 Hz quality 1000
> random: entropy device external interface
> netmap: loaded module
> [ath_hal] loaded
> module_register_init: MOD_LOAD (vesa, 0x80f779d0, 0) error 19
> random: registering fast source Intel Secure Key RNG
> random: fast provider: "Intel Secure Key RNG"
> kbd1 at kbdmux0
> nexus0
> vtvga0:  on motherboard
> cryptosoft0:  on motherboard
> acpi0: <_ASUS_ Notebook> on motherboard
> acpi_ec0:  port 0x62,0x66 on acpi0
> acpi0: Power Button (fixed)
> cpu0:  on acpi0
> cpu1:  on acpi0
> cpu2:  on acpi0
> cpu3:  on acpi0
> cpu4:  on acpi0
> cpu5:  on acpi0
> cpu6:  on acpi0
> cpu7:  on acpi0
> hpet0:  iomem 0xfed0-0xfed003ff on acpi0
> Timecounter "HPET" frequency 14318180 Hz quality 950
> Event timer "HPET" frequency 14318180 Hz quality 550
> atrtc0:  port 0x70-0x77 irq 8 on acpi0
> atrtc0: Warning: Couldn't map I/O.
> atrtc0: registered as a time-of-day clock, resolution 1.00s
> Event timer "RTC" frequency 32768 Hz quality 0
> attimer0:  port 0x40-0x43,0x50-0x53 irq 0 on acpi0
> Timecounter "i8254" frequency 1193182 Hz quality 0
> Event timer "i8254" frequency 1193182 Hz quality 100
> Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
> pcib0:  port 0xcf8-0xcff on acpi0
> pci0:  on pcib0
> pcib1:  irq 16 at device 1.0 on pci0
> pci1:  on pcib1
> vgapci0:  port 0xe000-0xe07f mem 
> 0xf600-0xf6ff,0xf000-0xf3ff,0xf400-0xf5ff irq 16 at 
> device 0.0 on pci1
> vgapci0: Boot video device
> hdac0:  mem 0xf708-0xf7083fff irq 17 at 
> device 0.1 on pci1
> xhci0:  mem 0xf730-0xf730 irq 
> 16 at device 20.0 on pci0
> xhci0: 32 bytes context size, 64-bit DMA
> usbus0: waiting for BIOS to give up control
> xhci0: Port routing mask set to 0x
> usbus0 on xhci0
> usbus0: 5.0Gbps Super Speed USB v3.0
> pci0:  at device 22.0 (no driver attached)
> ehci0:  mem 0xf7318000-0xf73183ff irq 
> 16 at device 26.0 on pci0
> usbus1: EHCI version 1.0
> usbus1 on ehci0
> usbus1: 480Mbps High Speed USB v2.0
> hdac1:  mem 0xf731-0xf7313fff irq 22 
> at