FreeBSD's commit message (r232411) explains it: Fix a problem that was causing the mpt(4) driver to attach to MegaRAID cards that should be handled by the mfi(4) driver. The root of the problem is that the mpt(4) driver was masking off the bottom bit of the PCI device ID when deciding which cards to attach to. It appears that a number of the mpt(4) Fibre Channel cards had a LAN variant whose PCI device ID was just one bit off from the FC card's device ID. The FC cards were even and the LAN cards were odd. The problem was that this pattern wasn't carried over on the SAS and parallel SCSI mpt(4) cards. Luckily the SAS and parallel SCSI PCI device IDs were either even numbers, or they would get masked to a supported adjacent PCI device ID, and everything worked well. Now LSI is using some of the odd-numbered PCI device IDs between the 3Gb SAS device IDs for their new MegaRAID cards. This is causing the mpt(4) driver to attach to the RAID cards instead of the mfi(4) driver. The solution is to stop masking off the bottom bit of the device ID, and explicitly list the PCI device IDs of all supported cards. This change should be a no-op for mpt(4) hardware. The only intended functional change is that for the 929X, the is_fc variable gets set. It wasn't being set previously, but needs to be because the 929X is a Fibre Channel card.
…achine I/O APIC causes too much trouble on virtual machines; simply disable I/O APIC for virtual machines by default. You could always explicitly enable I/O APIC on virtual machines by setting tunable hw.ioapic_enable to 1 Thank swildner@ for hint on virtual machine detection method. Reported-by: many
This follows up on a previous (pthread specific) commit by alexh (e7322b0) that used a per-proto macro. Revert this commit, too. In principle, we do it like NetBSD now. See http://gcc.gnu.org/wiki/Visibility in the GCC wiki for details on the issue. This solution was suggested by Martin Husemann in a thread about xulrunner building issues: http://mail-index.netbsd.org/tech-pkg/2012/03/11/msg008680.html Reported-and-tested-by: marino and others
was resulting in cherry-pick conflicts in MFC branch
Move holds outside of the pagecopy loop to reduce locking overhead. Suggested-by: dillon
Add missing holds/drops to vm_fault_copy_entry that were triggering assertions in vm_page_alloc/vm_page_lookup when when a process holding locked memory is forked. Fixes: https://bugs.dragonflybsd.org/issues/2320 Reviewed-by: vsrinavas X-Nahmean-Status: word
inform() expects a printf-like format string as the second argument, so you should always supply one instead of a random string by itself. DragonFly-bug: <http://bugs.dragonflybsd.org/issues/1596>
It was introduced in c4c23d9.
This caused compiling with -pg to fail for C++: zoot# c++ -pg -o t t.c /usr/libexec/binutils222/elf/ld.bfd: cannot find -lm_p Our libraries for profiling don't have different names than the normal ones. They just are in a different directory (/usr/lib/profile), which is cared for. Reported-by: Pierre Abbat <firstname.lastname@example.org> Dragonfly-bug: <http://bugs.dragonflybsd.org/issues/2325>
northamerica: 8.52 -> 8.53 * northamerica: Summer time in Cuba has been delayed 3 weeks (now starts April 1 rather than March 11). Since Mar 11 (the old start date, as listed in 2012a) is just a little over a week away, this change is urgent. Also bump zone.tab's version for a fix that was not in 2012a but which I already added.
antarctica: 8.9 -> 8.10 asia: 8.69 -> 8.70 australasia: 8.29 -> 8.30 europe: 8.40 -> 8.41 leapseconds: 8.11 -> 8.13 northamerica: 8.51 -> 8.52 README: 8.3 -> 8.4 southamerica: 8.52 -> 8.53 zone.tab: 8.52 -> 8.54 * antarctica: Current best known timezone info for various Antarctic bases for the winter of 2012. * asia: Armenia has abolished summer time. * australasia: Tokelau copied Samoa and swapped sides of the International Date Line last December (affects current timestams). * europe: Updated URL for UK timezone history. * leapseconds: Bulletin C43 incorporated (a leap Second will occur 2012-06-30 at 23:59:60 UTC). Bulletin C42 was also incorporated (but never released) - it said nothing very interesting (no leap second 2011-12-31). * northamerica: New zone America/Creston created for an area in British Columbia that was previously (and apparently incorrectly) considered identical to Dawson Creek. Also, some corrections to 1918 summer time end dates in several Canadian zones. * README: Updated to reflect the current home of the mailing list and files. * southamerica: Chile has extended Summer time in the 2011/2 summer. Future years (2013->) are assumed revert to "normal" for now. The Falkland Islands now have it permanently (continuing the 2011 experiment). This "permanently" is a guess, it apparently is certain for 2012 (as certain as these things ever are) and considered likely into the future. * zone.tab: New America/Creston zone added, and a typo in the entry for Europe/Samara corrected.
Before referencing *sem->... in the check, do not just test if sem is NULL but also if *sem is NULL. Reported-by: Max Herrgard <email@example.com>
Reported-by: Max Herrgard <firstname.lastname@example.org>
When binutils 2.20 was brought in, the x86_64 kernel built with it loaded at 0x200000 instead of 0x100000 as it was previously. The getmemsize() function was never updated with the new address so the physical memory between 0x100000 and 0x200000 has been lost since then. The hardcoded value has been updated. In the future, it may be a good idea to replace with a variable as FreeBSD has done.
* Nullfs are a clever hack, they forget their mp after mount and let the non-nullfs underlying mount point do all the work * Nevertheless, we need to get the real struct mount associated to a mount point to count the space used by PFSes. We cache it in the vnode. * But since the vnode we use really belongs to the lowest underlying mount point, the upper-level mp may already have been freed. * We need to first check if it still valid; a new function, mountlist_exists() now exists for that purpose. * Should fix issue #2266
mfs_start() is active for the life of an MFS mount, handling copyin/out requests. It is directed to exit when an MFS filesystem is unmounted. The VFS accounting code and VFS MPLOCK code assumed that the mountpoint structure was stable on return of mfs_start, which was not the case. To work around that, don't call acinit if the vfs_start vfsop returns EMOUNTEXIT, a kernel-specific pseudo-errno. Also allow marking vfs_start MPSAFE and mark mfs vfs_start MPSAFE, to avoid accessing a per-mount token field. A future commit will rework MFS's locking so that critical sections are not used to protect the MFS bioq. This is a hack for MFS; future work should either rework the filesystem or replace it outright with tmpfs. Closes: Bug 2276
* Fix buildworld on DragonFly hosts built before Dec 18, 2010 (2.9). * NELEM() macro was added to sys/param.h on Dec 18, 2010 and objformat was made to use it on May 20, 2011. This broke upgrades for machines running a DragonFly version built prior to Dec 18, 2010 since objformat is built with the hosts headers as part of the cross tools stage.