[Bug 231810] [build] release always fails with "mkimg: partition 2: No space left on device"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231810 --- Comment #4 from Matthias Apitz --- (In reply to leeb from comment #3) My file system produced by mkfs(8) is around 24 GByte by intention because I added '-M 50331648b -m 50331648b' in the script to the parms of mkfs(8). The idea is to

[Bug 231795] 12-ALPHA8 top SIGSEGV

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231795 --- Comment #1 from Jeremy Faulkner --- Top when run on the host has a chance to core dump when an new app loads in a jail. It has core dumped just logging in to a jail via ssh. -- You are receiving this mail because: You are the assignee

[Bug 231810] [build] release always fails with "mkimg: partition 2: No space left on device"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231810 --- Comment #3 from l...@ratnaling.org --- My /tmp is 12G tmpfs. Using the patch I supplied, it doesn't really go over 100M, just checking with frequent df -h in another console during the mkimg process. This happens with a GENERIC kernel

[Bug 221777] merge the latest changes to the ig4 module from DragonFly BSD and add Kaby Lake / Intel 100 series platform support

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221777 --- Comment #25 from commit-h...@freebsd.org --- A commit references this bug: Author: gonzo Date: Sun Sep 30 23:17:33 UTC 2018 New revision: 339031 URL: https://svnweb.freebsd.org/changeset/base/339031 Log: MFC r338654, r338701 r3386

[Bug 221777] merge the latest changes to the ig4 module from DragonFly BSD and add Kaby Lake / Intel 100 series platform support

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221777 --- Comment #24 from commit-h...@freebsd.org --- A commit references this bug: Author: gonzo Date: Sun Sep 30 23:14:08 UTC 2018 New revision: 339029 URL: https://svnweb.freebsd.org/changeset/base/339029 Log: MFC r336050-r336051, r336142,

Problem reports for b...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 231828] em(4) is unusable after suspend/resume

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231828 Bug ID: 231828 Summary: em(4) is unusable after suspend/resume Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: A

[Bug 231810] [build] release always fails with "mkimg: partition 2: No space left on device"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231810 --- Comment #2 from Matthias Apitz --- (In reply to leeb from comment #0) I think, in your case it will help to set an env var to some file system with more space than one normally has below /tmp, for example: # mkdir /usr/tmp # TMPDIR=/u

[Bug 231827] unzip sync with NetBSD upstream

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231827 Alex Kozlov changed: What|Removed |Added Assignee|b...@freebsd.org|d...@freebsd.org -- You are receivi

[Bug 231827] unzip sync with NetBSD upstream

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231827 Bug ID: 231827 Summary: unzip sync with NetBSD upstream Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Ma

[Bug 231080] callout structure corruption and panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080 --- Comment #22 from Sean Bruno --- The machine did crash last night, finally. However it did *not* hit the code we were hoping and died somewhere else. I've dumped the kernel and assorted crash files to freefall.freebsd.org:~sbruno/servi

[Bug 231810] [build] release always fails with "mkimg: partition 2: No space left on device"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231810 Kubilay Kocak changed: What|Removed |Added CC||r...@freebsd.org Severit