Re: should aarch64 cross-build work at amd64?
On Tue, Sep 27, 2016 at 09:46:29PM -0600, Ross Alexander wrote: > On Fri, 23 Sep 2016 22:19:15 +, Glenn Barber wrote: > > >On Sat, Sep 24, 2016 at 12:54:05AM +0300, Boris Samorodov wrote: > >> 24.09.2016 00:44, Boris Samorodov ?: > >> > 24.09.2016 00:39, Glen Barber ?: > >> >> On Sat, Sep 24, 2016 at 12:35:30AM +0300, Boris Samorodov wrote: > >> >>> make[1]: /poudriere/jails/HEAD-aarch64/usr/src/Makefile.inc1 line 177: > >> >>> In-tree binutils does not support the aarch64 architecture. Install the > >> >>> aarch64-binutils port or package or set CROSS_BINUTILS_PREFIX. > >> >> > >> >> These lines are relevant. > >> > > >> > Ops. Thank you. > >> > >> The error when aarch64-binutils are installed: > >> - > >> % sudo poudriere jail -c -j HEAD-aarch64 -a arm.aarch64 -v head -m > >> svn+https -J 8 > > > >Try with 'arm64.aarch64'. > >Glen > > Glen, > > The more I read this, the less I understand. I've built and install'd > aarch64-binutils on my poud box, then created an "-x -a arm64.aarch64 -m svn" > jail - which worked fine - but that jail won't build anything. No > /usr/bin/ld, so toolchain is borked, so can't build ports-mgmt/pkg. > What utterly obvious thing have I missed? I've spent hours trying to > fake out the nxb-bin stuff, or to find some other point of entry, no > joy. > > FreeBSD aubey2.bogons 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r306286: > Fri Sep 23 21:32:37 MDT 2016 > toor@aubey2.bogons:/usr/obj/usr/src/sys/GENERIC amd64 > > poudriere-devel-3.1.99.20160624_2 > > qemu-user-static-2.6.90.g20160728 > > aarch64-binutils-2.25.1_3,1 > > # /usr/sbin/binmiscctl lookup aarch64 > name: aarch64 > interpreter: /usr/local/bin/qemu-aarch64-static > flags: ENABLED USE_MASK > magic size: 20 > magic offset: 0 > magic: 0x7f 0x45 0x4c 0x46 0x02 0x01 0x01 0x00 0x00 0x00 0x00 0x00 >0x00 0x00 0x00 0x00 0x02 0x00 0xb7 0x00 >mask: 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x00 0xff 0xff 0xff 0xff > 0xff 0xff 0xff 0xff 0xfe 0xff 0xff 0xff > > failing jail is "11-stab-arm64 11.0-PRERELEASE r306344 arm64.aarch64 svn > 2016-09-26 18:54:15 /usr/local/pd/jails/11-stab-arm64" > You should not need to use binmiscctl and QEMU. Try: # poudriere jail -c -j HEAD-aarch64 -a arm.aarch64 -v head -m \ svn+https Glen signature.asc Description: PGP signature
Re: Freeze during booting of ASUS F2A85-M motherboard with Coreboot
On Tuesday, September 27, 2016 10:31:24 PM Piotr Kubaj wrote: > No, I get only messages about allocating window. > > On 09/26/16 22:48, John Baldwin wrote: > > On Wednesday, September 21, 2016 11:19:05 AM Piotr Kubaj wrote: > >> I'm trying to boot the ASUS F2A85-M board with flashed Coreboot 4.4 and > >> SeaBIOS 1.9.1 as a payload. > >> > >> This board works nicely with stock UEFI, it can also boot Slackware 14.2 > >> from Coreboot with SeaBIOS without any issues. > >> > >> But it seems to have problems with FreeBSD (I've tried 11.0-RC3 and > >> later 12.0-CURRENT). That's why I'm posting it here, instead of Coreboot > >> mailing lists. > >> > >> Booting freezes after printing: > >> pcib1: failed to allocate initial I/O port window: 0x1000-0x1fff > > > > Do you get this message in a verbose dmesg with the stock UEFI? > > Are you able to capture a full verbose dmesg via a serial console or the like that would really help as it may be that we are seeing a resource conflict with the way Coreboot sets up the PCI bridge windows and then disabling an I/O window that happens to break something. A verbose dmesg from the stock UEFI would also be useful, though it is less important. -- John Baldwin ___ 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"
zpool (online|replace|labelclear) issues, -f option also failing
Hello, I am currently trying to replace a disk that was offlined and getting the following error: # zpool replace tank 14989197580381994958 gptid/31be0527-84f0-11e6-bbbc-fcaa14edc6a6 invalid vdev specification use '-f' to override the following errors: /dev/gptid/31be0527-84f0-11e6-bbbc-fcaa14edc6a6 is part of active pool 'tank' # zpool replace -f tank 14989197580381994958 gptid/31be0527-84f0-11e6-bbbc-fcaa14edc6a6 invalid vdev specification the following errors must be manually repaired: /dev/gptid/31be0527-84f0-11e6-bbbc-fcaa14edc6a6 is part of active pool 'tank' # zpool status tank pool: tank state: DEGRADED status: One or more devices has been taken offline by the administrator. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Online the device using 'zpool online' or replace the device with 'zpool replace'. scan: resilvered 1.10T in 9h4m with 0 errors on Tue Sep 20 00:33:32 2016 config: NAMESTATE READ WRITE CKSUM tankDEGRADED 0 0 0 raidz2-0 ONLINE 0 0 0 gptid/8bdbd180-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/8c4df91d-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/8ccf21a3-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/8d5521cb-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/8de13b47-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/8e842f92-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 raidz2-1 DEGRADED 0 0 0 gptid/8bba4a82-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/8c26d491-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/8ca3fea6-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 14989197580381994958OFFLINE 0 0 0 was /dev/diskid/DISK-p2 gptid/8db26351-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/8e4bfa70-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 raidz2-2 ONLINE 0 0 0 gptid/8b957b47-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/8c0340da-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/8c77ddcb-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/8cf6b7f1-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/8d84b31e-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/8e146dad-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 raidz2-3 ONLINE 0 0 0 gptid/8ebb39df-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/8ef49770-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/2f94035d-7e9f-11e6-abe9-fcaa14edc6a6 ONLINE 0 0 0 gptid/8f69cf08-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/8fa7c0a6-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 gptid/8fe7816d-f52a-11e5-90c5-fcaa14edc6a6 ONLINE 0 0 0 logs gptid/683dc146-f531-11e5-90c5-fcaa14edc6a6ONLINE 0 0 0 errors: No known data errors # glabel status | grep da14 gptid/24a57a9b-84f0-11e6-bbbc-fcaa14edc6a6 N/A da14p1 gptid/31be0527-84f0-11e6-bbbc-fcaa14edc6a6 N/A da14p2 diskid/DISK- N/A da14 # gpart show da13 da14 =>40 7814037088 da13 GPT (3.6T) 40 4194304 1 freebsd-swap (2.0G) 4194344 7809842784 2 freebsd-zfs (3.6T) =>40 7814037088 da14 GPT (3.6T) 40 4194304 1 freebsd-swap (2.0G) 4194344 7809842784 2 freebsd-zfs (3.6T) # uname -a FreeBSD S1 12.0-CURRENT FreeBSD 12.0-CURRENT #4 r306300: Sat Sep 24 14:24:23 EDT 2016 root@S1:/usr/src/head/obj/usr/src/head/src/sys/MYKERNEL-NODEBUG amd64 I recently offlined the device and after onlining it the label changed to geom. After a few reboots the pool started importing by diskid. After attempting to offline/online by gptid, would continue to fail with an error. I decided try to replace it and is also failing with the error above. I also wiped the first & last 2MB of the disk without success. Is they're a known issue or perhaps I'm missing something obvious? zpool labelclear is also providing a similar error. The -f options are not helping. Any ideas what my issue maybe? The error suggests it is currently active on the pool, however the offline should have changed that status correct? Ultima ___ 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: Freeze during booting of ASUS F2A85-M motherboard with Coreboot
No, I get only messages about allocating window. On 09/26/16 22:48, John Baldwin wrote: On Wednesday, September 21, 2016 11:19:05 AM Piotr Kubaj wrote: I'm trying to boot the ASUS F2A85-M board with flashed Coreboot 4.4 and SeaBIOS 1.9.1 as a payload. This board works nicely with stock UEFI, it can also boot Slackware 14.2 from Coreboot with SeaBIOS without any issues. But it seems to have problems with FreeBSD (I've tried 11.0-RC3 and later 12.0-CURRENT). That's why I'm posting it here, instead of Coreboot mailing lists. Booting freezes after printing: pcib1: failed to allocate initial I/O port window: 0x1000-0x1fff Do you get this message in a verbose dmesg with the stock UEFI? ___ 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: Differences between freebsd-base-graphics and regular current source trees?
On Tue, Sep 27, 2016 at 07:32:36AM +, Thomas Mueller wrote: > If I want to keep up with FreeBSD-current with new graphics drivers, is it > sufficient to keep only the freebsd-base-graphics source tree to avoid the > redundancy of keeping the regular src tree as well? I use the drm-next-4.7 branch at https://github.com/FreeBSDDesktop/freebsd-base-graphics >From what I understand, this is the repo where the current effort in syncing with Linux i915 & Radeon drivers happens. Upstream is merged from time to time, usual delay <= 2 week. I am also interested in changes to the iwm driver and maintain a branch with patches to this module that I rebase onto drm-next-4.7. Hope this helps, Christian ___ 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: Differences between freebsd-base-graphics and regular current source trees?
If I want to keep up with FreeBSD-current with new graphics drivers, is it sufficient to keep only the freebsd-base-graphics source tree to avoid the redundancy of keeping the regular src tree as well? I notice some things are not updated as frequently in the freebsd-base-graphics tree; "git pull" showed Already up-to-date, and I noticed GENERIC file not up-to-date in /freebsd-base-graphics/sys/i386/conf/GENERIC compared to /usr/src/sys/i386/conf/GENERIC. I switched regular src tree from head to stable/11 but could checkout the head source tree, in which case I have to move/rename /usr/src to /usr/src11 or use /usr/src12 for the head source tree. Tom ___ 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"
