atomic in i386 Current after CLANG 6 upgrade

Hy all, I've already received a couple of messages from pkg-fallout about build failure on head-i386-default [1] [2] both pointing to the same errors, about missing intrinsic symbols related to __atomic_* The clang documentation about C11 atomic builtins [3] stats that __atomic_* are GCC

[SOLVED] Re: pcie Realtek 8168G issues (re driver)(minnowboard)

for all your tips. Best regards, Luca Pizzamiglio On Wed, Feb 25, 2015 at 3:59 PM, Luca Pizzamiglio luca.pizzamig...@gmail.com wrote: Hi, thanks you all for the replies. Unfortunately, the network chip is still not working and I updated the PR (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id

Re: pcie Realtek 8168G issues (re driver)

another board with the same chip :O Best regards, Luca On Tue, Feb 17, 2015 at 7:31 PM, O. Hartmann ohart...@zedat.fu-berlin.de wrote: Am Tue, 17 Feb 2015 18:32:22 +0100 Luca Pizzamiglio luca.pizzamig...@gmail.com schrieb: Hi Ben, thanks for the tip! tso was already disabled. I tried anyway

Re: pcie Realtek 8168G issues (re driver)

re0 up ). This also seems to stop the panics under current. I'm not sure it will work for you - but it has on everyone of those interfaces I've dealt with. Good luck, -bp On Feb 13, 2015, at 8:06 AM, Luca Pizzamiglio luca.pizzamig...@gmail.com wrote: Hi, I'm Luca, I've some issues

pcie Realtek 8168G issues (re driver)

Hi, I'm Luca, I've some issues using a PCIe Realtek Ethernet board: re0@pci0:3:0:0: class=0x02 card=0x012310ec chip=0x816810ec rev=0x0c hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' class = network

Memory modified after free Kernel panic with current (r278031)

Hallo, I'm still fighting with MinnowBoard... When I set the network interface I get a bunch of Memory modified after free messages. If I wait long enough (a couple of minutes) I get a kernel panic. Here an example with the dmesg (https://pastebin.mozilla.org/8657938) I've tested it using

Re: UEFI boot fail on higher resolutions (Re: Acer E3-112 and UEFI)

On a Minnowboard I've the same behavior, 800x600 it boots, at 1024x768 it crash, using a DVI display. best regards, pizzamig On Wed, Feb 4, 2015 at 2:04 PM, Jakob Alvermark ja...@alvermark.net wrote: On 31 dec 2014, at 16:24, Jakob Alvermark wrote: On Tue, December 30, 2014 17:00, Nathan

Re: UEFI boot hangs with MINNOWBOARD

30, 2015 at 6:35 PM, Ed Maste ema...@freebsd.org wrote: On 30 January 2015 at 10:57, Luca Pizzamiglio luca.pizzamig...@gmail.com wrote: Hi, I'm testing CURRENT on a MINNOWBOARD (http://www.elinux.org/Minnowboard:MinnowMax): Dual-core atom E3825 CPU EFI Version: 2.4.0 EFI: EDK II boot1.efi

Re: UEFI boot hangs with MINNOWBOARD

Hi Ed, thanks for the reply I tested the last available memstick (r277486) of CURRENT to install FreeBSD, but it didn't finish the boot process. The boot process hangs after showing the framebuffer information ( bi_load_efi_data() in bootinfo.c). I'm using a DVI monitor with a mini-HDMI-DVI

UEFI boot hangs with MINNOWBOARD

(only one) and they call also a FreePoll(). Do you have any tips, suggestions or something that could help to get FreeBSD boot on this apparently standard board? Best regards, Luca Pizzamiglio PS: should we implement the ExitBootServices() retry

Re: [CFT] Xorg Upgrade 7.5.2

Running on: * Intel Sandybridge (+ optimus, disabled) on FreeBSD 9.0 * NVidia GTS 450 on FreeBSD 8.2 Not unkwonw problem. Usual problem on Intel Sandybridge (tty switch, KMS patch issues on FreeBSD 9 and optimus incompatibility (/dev/dri/card1)). Tested with KDE 4.7.4 and desktop effect