[FreeBSD Bugzilla] Commit Needs MFC
Hi, You have a bug in the Needs MFC state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by ead...@freebsd.org. (11 bugs) Bug 155028: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=155028 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: init(8): init q in single user causes segfault Bug 156481: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=156481 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [kernel] [patch] kernel incorrectly reports PPS jitter with accurate measurements Bug 165630: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165630 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [ndis][panic][patch] IRQL_NOT_GREATER_THAN Bug 167133: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167133 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: stale files in /usr/share/examples Bug 169471: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169471 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [patch] pw(8) deletes group username on userdel even if group username is not assoc. w/user username Bug 171779: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=171779 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [patch] passwd(1): make option NO_FSCHG incomplete Bug 181155: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181155 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [libc] [patch] *access*(2) does not handle invalid amodes properly Bug 184681: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184681 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: A bug of bsdconfig(8) in 10.0 RC1 Bug 190186: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190186 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [patch] i915 driver: enable opregion handling Bug 192730: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192730 Severity: Affects Some People Priority: --- Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [build] make checkdpadd failures with LD* variables being added to LDADD Bug 192760: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192760 Severity: Affects Some People Priority: --- Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [build] sbin/ifconfig: missing DPADD for LIBM ___ 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 194180] New: [panic] [zfs] Bio not on queue
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194180 Bug ID: 194180 Summary: [panic] [zfs] Bio not on queue Product: Base System Version: 10.1-BETA3 Hardware: amd64 OS: Any Status: Needs Triage Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: d...@vlsi.se Created attachment 148026 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=148026action=edit Kernel dump summary Occurs intermittent related to destroying zfs pool, adding zfs spares and adding zfs caches. panic: Bio not on queue bp=0xf800098a66c8 target 0x814c0518 Unread portion of the kernel message buffer: panic: Bio not on queue bp=0xf800098a66c8 target 0x814c0518 cpuid = 0 KDB: stack backtrace: #0 0x8090c770 at kdb_backtrace+0x60 #1 0x808d3b96 at vpanic+0x126 #2 0x808d3a69 at kassert_panic+0x139 #3 0x80839ac0 at g_bioq_first+0x80 #4 0x80839c48 at g_io_schedule_up+0x88 #5 0x8083a24d at g_up_procbody+0x7d #6 0x808a2c04 at fork_exit+0x84 #7 0x80cbc9ce at fork_trampoline+0xe -- 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 186293] tar(1): Problems with tar on FreeBSD 10.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186293 --- Comment #6 from jnaug...@ee.ryerson.ca --- Hi All, I can confirm Martin's NFS traces. I installed a brand new Solaris 11.2 server. I didn't configure anything except networking. Exported /var/mnt from the Solaris 11.2 server to a Freebsd 10.0 client and got the following traces: Freebsd 10.0 Client NFSv3 Request: NFS: - Sun NFS - NFS: NFS: Proc = 2 (Set file attributes) NFS: File handle = [FBA3] NFS: 1E59EFB108C388D40A002000F8B80 5000A00040052E40100 NFS:Mode = 0644 NFS: Setuid = 0, Setgid = 0, Sticky = 0 NFS: Owner's permissions = rw- NFS: Group's permissions = r-- NFS: Other's permissions = r-- NFS: User ID = (not set) NFS: Group ID = (not set) NFS: Size = (not set) NFS: Access time = 02-Oct-14 14:47:23.00 GMT (set to client time) NFS: Modification time = 02-Oct-14 14:47:23.00 GMT (set to client time) Solaris 11.2 NFS Server Response NFS: - Sun NFS - NFS: NFS: Proc = 2 (Set file attributes) NFS: Status = 0 (OK) NFS: Pre-operation attributes: NFS:Size = 0 bytes NFS:Modification time = 10-Oct-78 12:33:23.1364841573 GMT NFS:Attribute change time = 02-Oct-14 10:47:57.031549787 GMT NFS: NFS: Post-operation attributes: NFS:File type = 1 (Regular File) NFS:Mode = 00 NFS: Setuid = 0, Setgid = 0, Sticky = 0 NFS: Owner's permissions = --- NFS: Group's permissions = --- NFS: Other's permissions = --- NFS:Link count = 1, User ID = 0, Group ID = 0 NFS:File size = 0, Used = 512 NFS:Special: Major = 4294967295, Minor = 4294967295 NFS:File system id = 1198295941134, File id = 32 NFS:Last access time = 02-Oct-14 14:47:23.0 GMT NFS:Modification time = 02-Oct-14 14:47:23.0 GMT NFS:Attribute change time = 02-Oct-14 10:47:57.038686069 GMT Freebsd 8.0 Client NFS: - Sun NFS - NFS: NFS: Proc = 2 (Set file attributes) NFS: File handle = [27D9] NFS: 1E59EFB108C388D40A00210025C205000A00040052E40100 NFS:Mode = 0644 NFS: Setuid = 0, Setgid = 0, Sticky = 0 NFS: Owner's permissions = rw- NFS: Group's permissions = r-- NFS: Other's permissions = r-- NFS: User ID = (not set) NFS: Group ID = (not set) NFS: Size = (not set) NFS: Access time = (set to server time) NFS: Modification time = (set to server time) Solaris 11.2 NFS Server response NFS: - Sun NFS - NFS: NFS: Proc = 2 (Set file attributes) NFS: Status = 0 (OK) NFS: Pre-operation attributes: NFS:Size = 0 bytes NFS:Modification time = 13-Nov-87 14:32:33.2130706433 GMT NFS:Attribute change time = 02-Oct-14 14:03:35.971683411 GMT NFS: NFS: Post-operation attributes: NFS:File type = 1 (Regular File) NFS:Mode = 0644 NFS: Setuid = 0, Setgid = 0, Sticky = 0 NFS: Owner's permissions = rw- NFS: Group's permissions = r-- NFS: Other's permissions = r-- NFS:Link count = 1, User ID = 0, Group ID = 0 NFS:File size = 0, Used = 512 NFS:Special: Major = 4294967295, Minor = 4294967295 NFS:File system id = 1198295941134, File id = 33 NFS:Last access time = 02-Oct-14 14:03:35.979188718 GMT NFS:Modification time = 02-Oct-14 14:03:35.979188834 GMT NFS:Attribute change time = 02-Oct-14 14:03:35.979237259 GMT So it looks like (to me) that with FreeBSD 8.0 it would send set file attributes in one request and set access time/modification time in a follow up request. As of FreeBSD 9.0 and onwards the FreeBSD client sends a file mode request and access time request in one packet. Solaris is responding OK in with respect to the access time and modification time change but ignoring the file mode additional change. You can see in the FreeBSD 8.0 the Access time/Modification time is not set in the mode change. Any way we can go back to doing this again? Right now NFSv3 is broken until this gets resolved. I own a Oracle Contract support right now so I've also filed a ticket with them. Yet this issue seems to be not prevalent with linux or Solaris Clients. For example a Scientfic Linux Client 6.3 and Solaris 11.2 response was the following: Scientfic Linux NFS Client 6.3 NFS: - Sun NFS - NFS: NFS: Proc = 2 (Set file attributes) NFS: File handle = [07A3] NFS: 1E59EFB108C388D40A001F003BB805000A00040052E40100 NFS:Mode = 0644 NFS: Setuid = 0, Setgid = 0, Sticky = 0 NFS: Owner's permissions = rw- NFS: Group's permissions = r-- NFS: Other's permissions = r-- NFS: User ID = (not set) NFS: Group ID = (not set) NFS: Size = (not set) NFS: Access time = (do not set) NFS: Modification time = (do not set) Solaris 11.2 NFS Server Response NFS: - Sun NFS - NFS: NFS: Proc = 2 (Set file attributes) NFS: Status = 0 (OK) NFS: Pre-operation attributes: NFS:Size = 0 bytes NFS:Modification time = 05-Sep-14 21:14:33.0 GMT NFS:
[Bug 181448] [mlxen] [patch] Using sysctl for mlxen stats might crash the kernel.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181448 John Baldwin j...@freebsd.org changed: What|Removed |Added CC||j...@freebsd.org Assignee|freebsd-bugs@FreeBSD.org|hsela...@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 193873] [PATCH] Unify dumpsys() under generic kern_dump.c.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193873 --- Comment #7 from Ed Maste ema...@freebsd.org --- https://reviews.freebsd.org/D904 -- 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 193660] [PATCH] Fix build of IA-32 but not i686 systems (e.g. alix)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193660 John Baldwin j...@freebsd.org changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|j...@freebsd.org --- Comment #1 from John Baldwin j...@freebsd.org --- We can actually use a simpler test as I686_CPU is never defined on amd64 (so can just check for that and ignore amd64 entirely). Thanks for the report, sorry about the breakage. -- 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 194173] Timezones (zoneinfo) starting from October 2014 wrong for Russia, etc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194173
--- Comment #3 from l...@sai.msu.ru ---
Also, this problem may cause application errors. For example:
[XXX@YYY ~]# freebsd-upgrade fetch
...
[XXX@YYY ~]# freebsd-upgrade install
...
[XXX@YYY ~]# pkg upgrade
...
[XXX@YYY ~]# date +'%d.%m.%Y %H:%M:%S %Z'
27.10.2014 12:30:00 MSK
[XXX@YYY ~]# TZ=Europe/Moscow date +'%d.%m.%Y %H:%M:%S %Z'
27.10.2014 12:30:06 MSK
[XXX@YYY ~]# php -r '
date_default_timezone_set(Europe/Moscow);
echo date(r e\n);'
Mon, 27 Oct 2014 11:30:21 +0300 Europe/Moscow
[XXX@YYY ~]# ruby -e require 'tzinfo' ;
puts TZInfo::Timezone.get('Europe/Moscow').strftime('%d.%m.%Y %H:%M:%S %Z')
27.10.2014 11:30:33 MSK
libc localtime may differ from localtime ruby, php and others with
unpredictable consequences
--
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 194197] New: IGB cards need a kernel option to enable legacy mode (to support ALTQ)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194197 Bug ID: 194197 Summary: IGB cards need a kernel option to enable legacy mode (to support ALTQ) Product: Base System Version: 10.1-BETA3 Hardware: Any OS: Any Status: Needs Triage Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: dan_...@yahoo.com Created attachment 148039 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=148039action=edit Adds IGB_LEGACY_TX and IXGBE_LEGACY_TX to kernel options IGB cards still do not support ALTQ, except in legacy mode, since FreeBSD 7/8. To enable legacy mode, patching of the kernel source is required. There is no official documentation on how to patch source, although reading between the lines on various forums would point you in the right direction. I created the attached patch to enable legacy mode in IGB driver through a kernel option, rather than a patch. A similar patch needs to be created for IXGBE. Because of bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193053, IXGBE will not compile with the kernel option set, but IGB will. Still, there should be a way to enable this option for IXGBE, even if it does not currently compile. -- 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 194025] [PATCH] nscd set query timeout properly
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194025 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: jhb Date: Mon Oct 6 18:16:46 UTC 2014 New revision: 272668 URL: https://svnweb.freebsd.org/changeset/base/272668 Log: Properly set the timeout in a query_state. The global query_timeout configuration value is an integer count of seconds, it is not a timeval. Using memcpy() to copy a timeval from it put garbage into the tv_usec field. PR:194025 Submitted by:David Shane Holden dpej...@yahoo.com MFC after:1 week Changes: head/usr.sbin/nscd/query.c -- 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 194025] [PATCH] nscd set query timeout properly
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194025 John Baldwin j...@freebsd.org changed: What|Removed |Added Status|Needs Triage|Needs MFC CC||j...@freebsd.org Assignee|freebsd-bugs@FreeBSD.org|j...@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 194063] [uefi] installer fails to boot / kernel panic on HP Probook 430 G1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194063 --- Comment #19 from Oliver Pinter o...@freebsd.org --- Created attachment 148041 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=148041action=edit fbsd10rc1 uefi hybrid mode with csm -- 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 194063] [uefi] installer fails to boot / kernel panic on HP Probook 430 G1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194063 --- Comment #20 from Oliver Pinter o...@freebsd.org --- Created attachment 148042 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=148042action=edit fbsd10rc1 uefi native mode without csm -- 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 194204] New: getentropy(2): sys call from openbsd
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194204 Bug ID: 194204 Summary: getentropy(2): sys call from openbsd 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: david.carl...@hardenedbsd.org Created attachment 148045 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=148045action=edit Proposed patch it is a proposed simple FreeBSD version of the OpenBSD's -- 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 194209] New: ahciems should be optional
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194209
Bug ID: 194209
Summary: ahciems should be optional
Product: Base System
Version: 11.0-CURRENT
Hardware: Any
OS: Any
Status: Needs Triage
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: freebsd-bugs@FreeBSD.org
Reporter: n...@freebsd.org
The code in sys/dev/ahci.c automatically detects whether or not a device has
AHCI_CAP_EMS support, then automatically loads the ahciem device. The ahciem
device should instead be loaded in the default kernel as a dependency of ahci.
310 if (ctlr-caps AHCI_CAP_EMS) {
311 child = device_add_child(dev, ahciem, -1);
312 if (child == NULL)
313 device_printf(dev, failed to add enclosure device\n);
314 else
315 device_set_ivars(child, (void *)(intptr_t)-1);
316 }
--
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
