[Bug 236565] [PATCH] Mk/bsd.port.mk: /etc/make.conf included twice by FreeBSD make

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236565 --- Comment #8 from rozhuk...@gmail.com --- maintainer timeout -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.fr

[Bug 236565] [PATCH] Mk/bsd.port.mk: /etc/make.conf included twice by FreeBSD make

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236565 rozhuk...@gmail.com changed: What|Removed |Added Flags||maintainer-feedback- -- You

[Bug 237290] [PATCH] build(7): PORTS_MODULES does not build in parallel

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237290 --- Comment #7 from rozhuk...@gmail.com --- maintainer timeout -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.fr

[Bug 237290] [PATCH] build(7): PORTS_MODULES does not build in parallel

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237290 rozhuk...@gmail.com changed: What|Removed |Added Flags||maintainer-feedback- -- You

[Bug 245649] [zfs] [panic] panic booting after removing zil

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245649 --- Comment #2 from w...@worrbase.com --- At first, I tried booting with the disk still attached, since I was going to repurpose it as a cache device. However, now the disk is entirely removed. Note that I also have 2 USB disks (mfsbsd itse

[Bug 245654] ig4(4): Intel Bay Trail I2C not recognized

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245654 --- Comment #3 from Vladimir Kondratyev --- Created attachment 213457 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=213457&action=edit BayTrail_PCI_IDs.patch Please: 1. Upgrade sources to latest STABLE 2. Apply attached patch

[Bug 229745] ahcich: CAM status: Command timeout

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745 --- Comment #51 from Wayne Willcox --- Ok have some new information in my case. I commented out from /boot/loader.conf #vfs.zfs.cache_flush_disable="1" I commented out from /boot/device.hints #hint.ahcich.0.sata_rev=2 so that I was back t

[Bug 229745] ahcich: CAM status: Command timeout

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745 --- Comment #52 from Wayne Willcox --- well this is interesting could these Western Digital drives also be using SMR? Might that explain the problem? Seems Western Digital is trying to include SMR without telling us? https://www.tomshardw

[Bug 229745] ahcich: CAM status: Command timeout

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745 --- Comment #53 from sec --- (In reply to Wayne Willcox from comment #52) At the moment my drives are: WDC WD1005FBYZ-01YCBB2 RR07 (WD Gold 1TB) WDC WD1005FBYZ-01YCBB1 RR04 (WD Gold 1TB) I had two with RR07, but I RMA'd one of the drives b

[Bug 245649] [zfs] [panic] panic booting after removing zil

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245649 --- Comment #3 from Andriy Gapon --- I am wondering if DISK-VAHDA7WL could be a problem. It has a 7+ TB partition mirrored with a 3+ TB partition in the pool. If there's any garbage that looks like a valid ZFS label in the unused portion of

[Bug 245654] ig4(4): Intel Bay Trail I2C not recognized

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245654 Mark Linimon changed: What|Removed |Added Keywords|needs-patch |patch -- You are receiving this ma

[Bug 245649] [zfs] [panic] panic booting after removing zil

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245649 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|f...@freebsd.org Keywords

[Bug 245673] avoid any ambiguity when using jail -e

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245673 Bug ID: 245673 Summary: avoid any ambiguity when using jail -e Product: Base System Version: 12.1-RELEASE Hardware: Any OS: Any Status: New Severity

[Bug 245189] Building world WITH_BEARSSL=1 and WITH_PIE=1 is currently broken

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245189 --- Comment #8 from Gordon Bergling --- It would be nice, if r359601 could also be MFC'ed for consistency. I just did a full build world on 12-STABLE and it succeed with WITH_PIE=1 and WITH_RETPOLINE=1 within the /etc/src.conf, but you neve

[Bug 237290] [PATCH] build(7): PORTS_MODULES does not build in parallel

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237290 --- Comment #8 from Bryan Drewery --- (In reply to rozhuk.im from comment #3) What's a terrible idea is making a change you don't understand. The -j flag has 0 impact on the ports build except to BREAK it. -j is not how ports are allowed t

[Bug 237290] [PATCH] build(7): PORTS_MODULES does not build in parallel

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237290 --- Comment #9 from Bryan Drewery --- Passing -j1 instead of -B seems to work when using a proof of concept test. Can you try that please? -- You are receiving this mail because: You are the assignee for the bug. _

[Bug 245677] ldd fails to work on some binaries ("No space available for static Thread Local Storage")

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245677 Bug ID: 245677 Summary: ldd fails to work on some binaries ("No space available for static Thread Local Storage") Product: Base System Version: Unspecified Hardware:

[Bug 245677] ldd fails to work on some binaries ("No space available for static Thread Local Storage")

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245677 Mark Linimon changed: What|Removed |Added Flags||maintainer-feedback?(toolch

[Bug 245673] avoid any ambiguity when using jail -e

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245673 Mark Linimon changed: What|Removed |Added Flags||maintainer-feedback?(jail@F

[Bug 245654] ig4(4): Intel Bay Trail I2C not recognized

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245654 Vladimir Kondratyev changed: What|Removed |Added Attachment #213457|0 |1 is obsolete|

[Bug 245630] sysutils/bastille: Update to 0.6.20200414

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245630 Christer Edwards changed: What|Removed |Added Attachment #213402|0 |1 is obsolete|

[Bug 245679] daily_status_ntpd typo in periodic.conf.5

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245679 Bug ID: 245679 Summary: daily_status_ntpd typo in periodic.conf.5 Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity:

[Bug 245683] panic: solaris assert: HDR_EMPTY(hdr), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c, line: 6271

2020-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245683 Bug ID: 245683 Summary: panic: solaris assert: HDR_EMPTY(hdr), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zf s/arc.c, line: 6271 Product: Base System