**** BEGIN LOGGING AT Thu Dec 19 03:00:12 2019
Dec 19 09:07:52 <Herrie> Morning!
Dec 19 10:25:49 <Tofe> JaMa: for linux 5.4, I get "scripts/Kconfig.include:39:  gold linker 'aarch64-webos-linux-ld' not supported"... you know something about that one?
Dec 19 10:30:23 <Tofe> oh... https://gitlab.com/pine64-org/linux/commit/75959d44f9dc8e44410667009724e4e238515502
Dec 19 10:38:01 <JaMa> Tofe: we have gold as default ld (ld-is-gold DISTRO_FEATURE) but you should be able to easily disable that with -fuse-ld=bfd, but the check for ld itself might be an issue
Dec 19 10:38:22 <Tofe> I'll commit a revert of that commit
Dec 19 10:38:32 <Tofe> (as a patch)
Dec 19 10:38:42 <JaMa> kernel-arch.bbclass:KERNEL_CC = "${CCACHE}${HOST_PREFIX}gcc ${HOST_CC_KERNEL_ARCH} -fuse-ld=bfd ${DEBUG_PREFIX_MAP} -fdebug-prefix-map=${STAGING_KERNEL_DIR}=${KERNEL_SRC_PATH}"
Dec 19 10:39:01 <JaMa> yes, probably best to just revert it, you should already get -fuse-ld=bfd in KERNEL_CC
Dec 19 10:39:01 <Tofe> done, let's try again
Dec 19 13:30:46 <JaMa> novaldex: Hi, there seems to be some issue with bonaire, first the fs went read-only http://jenkins.nas-admin.org/job/LuneOS/view/unstable/job/luneos-unstable_qemux86-64/82/console and when I try to ssh in to see what's going on I cannot
Dec 19 13:30:57 <JaMa> jenkins@kaylee:~$ ssh 10.20.1.198
Dec 19 13:30:57 <JaMa> ssh_exchange_identification: read: Connection reset by peer
Dec 19 14:32:06 <novaldex> JaMa: thanks, i'll take a look
Dec 19 15:29:14 <novaldex> JaMa: disk error with bonaire, will get it back up soon as we can, need to do some more investigating as to 'why' first
Dec 19 16:30:08 <JaMa> novaldex: ok, thanks
Dec 19 19:14:06 <JaMa> bonaire seems to be back online about 40 minutes ago, is it safe to queue new builds on it?
Dec 19 20:27:50 <JaMa> well it isn't usable yet, root is read-only again now
Dec 19 20:27:52 <JaMa> [Thu Dec 19 19:48:36 2019] Buffer I/O error on device xvda2, logical block 4051970
Dec 19 20:27:56 <JaMa> [Thu Dec 19 19:48:36 2019] print_req_error: I/O error, dev xvda, sector 36612144
Dec 19 20:27:59 <JaMa> [Thu Dec 19 19:48:36 2019] EXT4-fs warning (device xvda2): ext4_end_bio:323: I/O error 10 writing to inode 614414 (offset 0 size 0 starting block 4576519)
Dec 19 20:28:02 <JaMa> [Thu Dec 19 19:48:36 2019] Buffer I/O error on device xvda2, logical block 4051974
Dec 19 20:28:05 <JaMa> [Thu Dec 19 19:49:35 2019] EXT4-fs error (device xvda2): ext4_journal_check_start:61: Detected aborted journal
Dec 19 20:28:08 <JaMa> [Thu Dec 19 19:49:35 2019] EXT4-fs (xvda2): Remounting filesystem read-only
Dec 19 20:28:10 <JaMa> [Thu Dec 19 19:49:35 2019] EXT4-fs error (device xvda2): ext4_journal_check_start:61: Detected aborted journal
Dec 19 20:28:13 <JaMa> [Thu Dec 19 19:49:35 2019] EXT4-fs error (device xvda2): ext4_journal_check_start:61: Detected aborted journal
Dec 19 20:28:16 <JaMa> [Thu Dec 19 19:49:35 2019] EXT4-fs (xvda2): ext4_writepages: jbd2_start: 1024 pages, ino 1081345; err -30
Dec 19 20:28:19 <JaMa> [Thu Dec 19 19:49:35 2019] EXT4-fs error (device xvda2): ext4_journal_check_start:61: Detected aborted journal
Dec 19 20:28:22 <JaMa> [Thu Dec 19 20:20:01 2019] systemd-journald[353]: Failed to write entry (21 items, 602 bytes), ignoring: Read-only file system
Dec 19 20:28:25 <JaMa> [Thu Dec 19 20:20:01 2019] systemd-journald[353]: Failed to write entry (21 items, 693 bytes), ignoring: Read-only file system
**** ENDING LOGGING AT Thu Dec 19 21:08:38 2019

**** BEGIN LOGGING AT Thu Dec 19 23:03:53 2019
**** ENDING LOGGING AT Fri Dec 20 03:00:11 2019