[Bug 188911] [libc] sysctl(KERN_PROC_VMMAP) takes too long
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188911 David Chisnall changed: What|Removed |Added CC||thera...@freebsd.org --- Comment #3 from David Chisnall --- To provide some context, this is currently a blocker in getting the clang sanitizers working on FreeBSD. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 190939] Panic when trying to boot FreeBSD-10.0-STABLE-amd64-20140608-r267232-bootonly.iso via USB-CDRW drive
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190939 Sean Bruno changed: What|Removed |Added CC||sbr...@freebsd.org Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 191533] New: Wrong holiday listed in calendar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191533 Bug ID: 191533 Summary: Wrong holiday listed in calendar Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: d...@freebsd.org Created attachment 144320 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=144320&action=edit changes Dominion Day in Canada to Canada Day From http://www.pch.gc.ca/eng/1359137387574/1359137429809 October 27, 1982: July 1, “Dominion Day” officially becomes Canada Day. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 190669] 'emmintrin.h' file not found - in /usr/src/lib/clang/libclangbasic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190669 John Baldwin changed: What|Removed |Added CC||j...@freebsd.org --- Comment #17 from John Baldwin --- Did you run 'make delete-old' after doing an 'svn up' but before doing a 'make buildworld'? It's odd that /usr/include/clang is empty. That should not be empty normally. However, if you ran 'make delete-old' after the clang 3.4 -> 3.4.1 upgrade before doing a buildworld/installworld, delete-old would delete /usr/include/clang/3.4 but you wouldn't have the new /usr/include/clang/3.4.1 yet. You can try coping the headers you put in /usr/include/clang/3.4.1 to /usr/include/clang/3.4 for now to get your buildworld re-bootstrapped if so. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 191540] New: the FAT32 implementation bugs out on Unicode file names
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191540 Bug ID: 191540 Summary: the FAT32 implementation bugs out on Unicode file names Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: d...@gmx.com Attempting to read or write (also, getting the inode of, shell-autocompleting, and so on) files with non-ASCII Unicode names fails on FAT32 partitions. Such a name can exist, for example, due to Windows. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 191540] the FAT32 implementation bugs out on Unicode file names
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191540 --- Comment #1 from d...@gmx.com --- Created attachment 144326 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=144326&action=edit an archive containing files with fancy names Contains 2 empty files: 1’.txt 2–.txt -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 191540] the FAT32 implementation bugs out on Unicode file names
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191540 --- Comment #2 from d...@gmx.com --- To reproduce: Create and mount a FAT32 partition: # dd if=/dev/zero of=space bs=1m count=4 # mdconfig -a -u 7 -t vnode -f space # newfs_msdos -F 32 /dev/md7 # mkdir fat # mount -t msdosfs /dev/md7 fat Attempt to create files with fancy names on the partition: # cd fat # tar -vxf ../files.zip The output is: x 1’.txt: Can't create '1’.txt' x 2–.txt: Can't create '2–.txt' Other file access can also be attempted, eg.: (The "–" is a Unicode "en dash".) # stat – The output is: stat: –: stat: Invalid argument Clean up (optional): # cd .. # umount fat # rmdir fat # mdconfig -d -u 7 # rm space -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 191022] [tests] sed:multi_test testcase # 75 fails
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191022 yaneurab...@gmail.com changed: What|Removed |Added Summary|sed:multi_test testcase # |[tests] sed:multi_test |75 fails|testcase # 75 fails -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 191545] New: tools/regression/acltools failures
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191545 Bug ID: 191545 Summary: tools/regression/acltools failures Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: yaneurab...@gmail.com The acltools testcases fail on ZFS, but not on UFS as shown below. I haven't investigated why the testcases fail. Script started on Tue Jul 1 19:45:13 2014 command: sh -c uname -a; sysctl vfs.zfs; prove -rv . FreeBSD freebsd-11-x64.localdomain 11.0-CURRENT FreeBSD 11.0-CURRENT #2 r267801+8b3cf1c(more-tools-regression-integration): Tue Jun 24 21:17:31 PDT 2014 root@freebsd-11-x64.localdomain:/usr/obj/usr/src/sys/GENERIC-DEBUG amd64^M vfs.zfs.arc_max: 3056087040^M vfs.zfs.arc_min: 382010880^M vfs.zfs.arc_meta_used: 0^M vfs.zfs.arc_meta_limit: 764021760^M vfs.zfs.l2arc_write_max: 8388608^M vfs.zfs.l2arc_write_boost: 8388608^M vfs.zfs.l2arc_headroom: 2^M vfs.zfs.l2arc_feed_secs: 1^M vfs.zfs.l2arc_feed_min_ms: 200^M vfs.zfs.l2arc_noprefetch: 1^M vfs.zfs.l2arc_feed_again: 1^M vfs.zfs.l2arc_norw: 1^M vfs.zfs.anon_size: 0^M vfs.zfs.anon_metadata_lsize: 0^M vfs.zfs.anon_data_lsize: 0^M vfs.zfs.mru_size: 0^M vfs.zfs.mru_metadata_lsize: 0^M vfs.zfs.mru_data_lsize: 0^M vfs.zfs.mru_ghost_size: 0^M vfs.zfs.mru_ghost_metadata_lsize: 0^M vfs.zfs.mru_ghost_data_lsize: 0^M vfs.zfs.mfu_size: 0^M vfs.zfs.mfu_metadata_lsize: 0^M vfs.zfs.mfu_data_lsize: 0^M vfs.zfs.mfu_ghost_size: 0^M vfs.zfs.mfu_ghost_metadata_lsize: 0^M vfs.zfs.mfu_ghost_data_lsize: 0^M vfs.zfs.l2c_only_size: 0^M vfs.zfs.dedup.prefetch: 1^M vfs.zfs.nopwrite_enabled: 1^M vfs.zfs.mdcomp_disable: 0^M vfs.zfs.dirty_data_max: 426699571^M vfs.zfs.dirty_data_max_max: 4294967296^M vfs.zfs.dirty_data_max_percent: 10^M vfs.zfs.dirty_data_sync: 67108864^M vfs.zfs.delay_min_dirty_percent: 60^M vfs.zfs.delay_scale: 50^M vfs.zfs.prefetch_disable: 1^M vfs.zfs.zfetch.max_streams: 8^M vfs.zfs.zfetch.min_sec_reap: 2^M vfs.zfs.zfetch.block_cap: 256^M vfs.zfs.zfetch.array_rd_sz: 1048576^M vfs.zfs.top_maxinflight: 32^M vfs.zfs.resilver_delay: 2^M vfs.zfs.scrub_delay: 4^M vfs.zfs.scan_idle: 50^M vfs.zfs.scan_min_time_ms: 1000^M vfs.zfs.free_min_time_ms: 1000^M vfs.zfs.resilver_min_time_ms: 3000^M vfs.zfs.no_scrub_io: 0^M vfs.zfs.no_scrub_prefetch: 0^M vfs.zfs.metaslab.gang_bang: 131073^M vfs.zfs.metaslab.debug_load: 0^M vfs.zfs.metaslab.debug_unload: 0^M vfs.zfs.metaslab.df_alloc_threshold: 131072^M vfs.zfs.metaslab.df_free_pct: 4^M vfs.zfs.metaslab.min_alloc_size: 10485760^M vfs.zfs.metaslab.load_pct: 50^M vfs.zfs.metaslab.unload_delay: 8^M vfs.zfs.metaslab.preload_limit: 3^M vfs.zfs.metaslab.preload_enabled: 1^M vfs.zfs.metaslab.weight_factor_enable: 0^M vfs.zfs.condense_pct: 200^M vfs.zfs.mg_noalloc_threshold: 0^M vfs.zfs.write_to_degraded: 0^M vfs.zfs.check_hostid: 1^M vfs.zfs.recover: 0^M vfs.zfs.deadman_synctime_ms: 100^M vfs.zfs.deadman_checktime_ms: 5000^M vfs.zfs.deadman_enabled: 0^M vfs.zfs.spa_asize_inflation: 24^M vfs.zfs.txg.timeout: 5^M vfs.zfs.vdev.cache.max: 16384^M vfs.zfs.vdev.cache.size: 0^M vfs.zfs.vdev.cache.bshift: 16^M vfs.zfs.vdev.trim_on_init: 1^M vfs.zfs.vdev.mirror.rotating_inc: 0^M vfs.zfs.vdev.mirror.rotating_seek_inc: 5^M vfs.zfs.vdev.mirror.rotating_seek_offset: 1048576^M vfs.zfs.vdev.mirror.non_rotating_inc: 0^M vfs.zfs.vdev.mirror.non_rotating_seek_inc: 1^M vfs.zfs.vdev.max_active: 1000^M vfs.zfs.vdev.sync_read_min_active: 10^M vfs.zfs.vdev.sync_read_max_active: 10^M vfs.zfs.vdev.sync_write_min_active: 10^M vfs.zfs.vdev.sync_write_max_active: 10^M vfs.zfs.vdev.async_read_min_active: 1^M vfs.zfs.vdev.async_read_max_active: 3^M vfs.zfs.vdev.async_write_min_active: 1^M vfs.zfs.vdev.async_write_max_active: 10^M vfs.zfs.vdev.scrub_min_active: 1^M vfs.zfs.vdev.scrub_max_active: 2^M vfs.zfs.vdev.trim_min_active: 1^M vfs.zfs.vdev.trim_max_active: 64^M vfs.zfs.vdev.aggregation_limit: 131072^M vfs.zfs.vdev.read_gap_limit: 32768^M vfs.zfs.vdev.write_gap_limit: 4096^M vfs.zfs.vdev.bio_flush_disable: 0^M vfs.zfs.vdev.bio_delete_disable: 0^M vfs.zfs.vdev.trim_max_bytes: 2147483648^M vfs.zfs.vdev.trim_max_pending: 64^M vfs.zfs.max_auto_ashift: 13^M vfs.zfs.min_auto_ashift: 9^M vfs.zfs.zil_replay_disable: 0^M vfs.zfs.cache_flush_disable: 0^M vfs.zfs.zio.use_uma: 1^M vfs.zfs.zio.exclude_metadata: 0^M vfs.zfs.sync_pass_deferred_free: 2^M vfs.zfs.sync_pass_dont_compress: 5^M vfs.zfs.sync_pass_rewrite: 2^M vfs.zfs.snapshot_list_prefetch: 0^M vfs.zfs.super_owner: 0^M vfs.zfs.debug: 0^M vfs.zfs.version.ioctl: 3^M vfs.zfs.version.acl: 1^M vfs.zfs.version.spa: 5000^M vfs.zfs.version.zpl: 5^M vfs.zfs.vol.mode: 1^M vfs.zfs.trim.enabled: 1^M vfs.zfs.trim.txg_delay: 32^M vfs.zfs.trim.timeout: 30^M vfs.zfs.trim.max_interval: 1^M ./00.t .. ^M 1..4^[[0m^M ok 1^[[0m^M ok 2^[[0m^M ok 3^[[0m^M ok 4^[[0m^M ok^M ./01.t
[Bug 191545] [tests] tools/regression/acltools failures on ZFS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191545 yaneurab...@gmail.com changed: What|Removed |Added Summary|tools/regression/acltools |[tests] |failures|tools/regression/acltools ||failures on ZFS -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 191512] /bin/date -j -v-sun returns a Saturday instead of Sunday
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191512 Eitan Adler changed: What|Removed |Added Status|Needs Triage|Open --- Comment #2 from Eitan Adler --- [10020 root@gravity (100%) /home/eitan !1!]#date -j -v-sun Sun Mar 9 22:30:07 PDT 2014 [10021 root@gravity (100%) /home/eitan ]#date "201403142230.00" Fri Mar 14 22:30:00 PDT 2014 [10022 root@gravity (100%) /home/eitan !2!]#date -j -v-sun Sun Mar 9 22:30:01 PDT 2014 [10023 root@gravity (100%) /home/eitan ]#date "201403150030.00" Sat Mar 15 00:30:00 PDT 2014 [10024 root@gravity (100%) /home/eitan !2!]#date -j -v-sun Sat Mar 8 23:30:01 PST 2014 [10025 root@gravity (100%) /home/eitan ]#date "201403150130.00" Sat Mar 15 01:30:00 PDT 2014 [10026 root@gravity (100%) /home/eitan !2!]#date -j -v-sun Sun Mar 9 00:30:01 PST 2014 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 191540] the FAT32 implementation bugs out on Unicode file names
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191540 Jamie Landeg-Jones changed: What|Removed |Added CC||ja...@dyslexicfish.net --- Comment #3 from Jamie Landeg-Jones --- With unix filesystems, slap out any 'binary' characters in a filename and they will be recorded 'as is'. So, when you do an 'ls', the filename data is preserved so that if it was originally a UTF-8 encoded name originally, it will still be a UTF-8 name, and displayed correctly on a UTF-8 terminal. msdos file systems don't work this way, and translate the filenames before storing. If the msdos filesystem doesn't know what the original character set is, it won't be coded correctly, and subsequently won't be displayed correctly. You therefore need to tell it on mount what character set you are using, with the -L option: -L locale Specify locale name used for file name conversions for DOS and Win'95 names. By default ISO 8859-1 assumed as local character set. Your test filenames are in UTF-8 fornat, so if you repeat your exercise, but instead mount the partition with: mount_msdosfs -L en_GB.UTF-8 /dev/md7 fat , then everything will work as expected. You are attempting to -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
