[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 produce a file system in which I can install packages (a complete KDE4) for testing before I do move to the new CURRENT and my own packages produced with poudriere. I applied your patch to my script make-memstick.sh and it now produced fine the memestick.img without any memory problems. It seems that the problems is caused by chaining the mkimg(1) calls, which your patch exactly addresses. I will copy over the memstick.img to an USB key and test further. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[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 for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[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 on a stock installation. Nothing added. cd /usr/src make -j16 buildworld make -j16 buildkernel cd release make release I don't know why your mkfs is 24G, mine is more like 350M. sh /usr/src/release/amd64/make-memstick.sh bootonly mini-memstick.img Calculated size of `mini-memstick.img.part': 361332736 bytes, 11416 inodes Extent size set to 32768 mini-memstick.img.part: 344.6MB (705728 sectors) block size 32768, fragment size 4096 using 1 cylinder groups of 344.59MB, 11027 blks, 12672 inodes. super-block backups (for fsck -b #) at: 192, Populating `mini-memstick.img.part' Image `mini-memstick.img.part' complete -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[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 r338654: [ig4] Add PCI IDs for I2C controller on Intel Kaby Lake systems PR: 221777 Approved by: re (kib) Submitted by: marc.priggeme...@gmail.com r338701: [ig4] Fix device description for Kaby Lake systems Kaby Lake I2C controller is Intel Sunrise Point-H not Intel Sunrise Point-LP. Submitted by: Dmitry Luhtionov Approved by: re (kib) Changes: _U stable/11/ stable/11/sys/dev/ichiic/ig4_pci.c -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[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, r336326, r337719 r336050: ig4(4): add support for Apollo Lake I2C controllers Add PCI ids for I2C controllers on Apollo Lake platform. Also convert switch/case probe logic into a table. Reviewed by: avg Differential Revision:https://reviews.freebsd.org/D16120 r336051: ig4(4): Fix Apollo lake entries platform identifier Identify Apollo Lake controllers as IG4_APL and not as a IG4_SKYLAKE Reported by: rpokala@ r336142: ig4(4): add devmatch(8) PNP info Now that we have all devices ids in a table add MODULE_PNP_INFO macro to let devmatch autoload module r336326: Remove MODULE_PNP_INFO for ig4(4) driver ig4(4) does not support suspend/resume but present on the hardware where such functionality is critical, like laptops. Remove PNP info to avoid breaking suspend/resume on the systems where ig4(4) load is not explicitly requested by the user. PR: 229791 Reported by:Ali Abdallah r337719: [ig4] Fix initialization sequence for newer ig4 chips Newer chips may require assert/deassert after power down for proper startup. Check respective flag in DEVIDLE_CTRL and perform operation if neccesssary. PR: 221777 Submitted by: marc.priggeme...@gmail.com Obtained from:DragonFly BSD Tested on:Thinkpad T470 Changes: _U stable/11/ stable/11/sys/dev/ichiic/ig4_iic.c stable/11/sys/dev/ichiic/ig4_pci.c stable/11/sys/dev/ichiic/ig4_reg.h stable/11/sys/dev/ichiic/ig4_var.h -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
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 obsolete releases. Status |Bug Id | Description +---+--- In Progress |155163 | [patch] Add Recursive Functionality to setfacl(1) In Progress |210415 | vidcontrol -h does not work with v In Progress |230491 | stat(1): Improve performance with getpwuid() and New |197876 | [devfs] an error in devfs leads to data loss and New |198797 | [PATCH] Added an option to install BSDstats to bs New |202290 | /usr/bin/vi conversion error on valid character New |202362 | ntp: restore refclocks selection (10.2-RELEASE re New |202740 | vi/ex string substitution problem when there is m New |204097 | witness_initialize() does not perform bound check New |204115 | freebsd-update: Add support for better user messa New |204545 | Adding quirk entry for some (Acer C720P Chromeboo New |207940 | [patch] sys/boot/efi/boot1 select boot partition New |209213 | UEFI Loader shows only black screen with Nvidia G New |210804 | installerconfig - using ZFS create in custom scri New |212561 | stucking kyua test (/usr/tests/sys/acl/01) with e New |214705 | Kernel panic trying to playback encrypted DVD, "F New |221906 | sys/cddl: Allow to modify the ZFS deadman sysctls New |221973 | cam iosched: BIO_ZONE commands probably shouldn't New |221974 | cam iosched: The iops limiter should enforce limi New |224436 | vt: CONS_CLRHIST (vidcontrol -C) not implemented New |231354 | Potential null pointer deference in drm/r128 Open| 71667 | [patch] cleanup of the usr.sbin/bootparamd code Open|155873 | calendar(1) recurring date not working Open|157718 | input data trigers a core dump from calendar(1) [ Open|182466 | [headers] [patch] make self-contained Open|183618 | [panic] Dell PowerEdge R620 -- PERC H710 Mini (mf Open|189914 | i2c(8) utility does not work on Raspberry Pi Open|194925 | [pf] [ifconfig] interface group keywords do not w Open|196973 | sh(1) broken UTF-8 input Open|206528 | Emulex LPe 16002 FC HBA Not Recognized by oce(4) Open|206585 | hpt_set_info possible buffer overflow Open|206754 | Out of bounds negative array index in iicrdwr Open|207109 | makefs includes a timestamp that prevents reprodu Open|207248 | [patch] daemon(8): Add option to redirect stdout Open|211713 | NVME controller failure: resetting (Samsung SM961 Open|212418 | kernel panic in _taskqgroup_adjust - uninitialize Open|217505 | [asmc] [patch] Add Support for Macbook Pro 8,1 Open|220246 | syslogd does not send RFC3164-conformant messages Open|221305 | Mouse cursor loss when moving cursor while loadin Open|221350 | Unable to boot/install on HPE Proliant MicroServe Open|221854 | makefs: Reject UFS labels that are too long to fi Open|222632 | connect(2) not available in capability mode New |230725 | [patch] kerberos5 files missing in tools/build/mk New |230727 | [patch] NIS file missing in tools/build/mk/Option New |230955 | [patch] Some speedup mergemaster Open|191348 | [mps] LSI2308 with WD3000FYYZ drives disappears a Open|206754 | Out of bounds negative array index in iicrdwr 47 problems total for which you should take action. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[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: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: p...@nomadlogic.org There are several reports that when using an em(4) device on 12-CURRENT the NIC is unusable until after a reboot or kld_unload/kld_load of the if_em kernel module. upon resume there are messages like this in the dmesg buffer: in6_purgeaddr: err=65, destination address delete failed lo0: link state changed to DOWN lo0: link state changed to UP Link state changed to down em0: link state changed to DOWN em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 there is a mailing list thread about the issue here: https://lists.freebsd.org/pipermail/freebsd-current/2018-September/071408.html my device info via pciconf: em0@pci0:0:31:6:class=0x02 card=0x30d017aa chip=0x15b78086 rev=0x31 hdr=0x00 vendor = 'Intel Corporation' device = 'Ethernet Connection (2) I219-LM' class = network subclass = ethernet -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[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=/usr/tmp export TMPDIR AT least, this helped me for a tiny root file system to make an image off. But if you specify in the command mkfs(8) that your file system should have plenty space for additional thinks, it will create there in TMPDIR some swap file with giga o even terra bytes. There is something broken with mkimg(1). Some time ago, in March 2017 on r314251, this was all working fine and w/o any TMPDIR. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[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 receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[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 Many People
Priority: ---
Component: bin
Assignee: b...@freebsd.org
Reporter: a...@freebsd.org
Created attachment 197636
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=197636&action=edit
sync with NetBSD upstream
Sync unzip in the base with upstream from NetBSD (rev1.24):
- Ignore malformed directory entries as created by Dropbox ("/")
- Use getline() instead of getdelim()
- Always overwrite symlinks on extraction, ever if they're newer than entries
in the archive
- Use libarchive 3.x interface: check result for archive_read_free() and don't
call archive_read_close() manually
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[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/service1_softclock.rbsd.tar -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[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 Severity|Affects Only Me |Affects Some People Flags||mfc-stable11? Status|New |Open -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
