summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Mention the upper hard limit for -n option. Patch slightly modifiedwblock2012-05-231-3/+6
| | | | | | | | | from PR version. PR: 168255 Submitted by: Andy Kosela Approved by: gjb MFC after: 3 days
* Note that the new jail(8) will be appearing in 9.1.jamie2012-05-232-4/+4
|
* mdoc: move two sentences from synopsis to description (where they reallyjoel2012-05-232-20/+16
| | | | belong). With this change, mandoc now formats these manpages properly.
* Rework the previous change to honor MADT processor IDs when probingjhb2012-05-232-60/+59
| | | | | | | | | | | processor objects. Instead of forcing the new-bus CPU objects to use a unit number equal to pc_cpuid, adjust acpi_pcpu_get_id() to honor the MADT IDs by default. As with the previous change, setting debug.acpi.cpu_unordered to 1 in the loader will revert to the old behavior. Tested by: jimharris MFC after: 1 month
* Only check to see if a memory resource is a PCI ROM BAR when activatingjhb2012-05-231-2/+2
| | | | | | | | | and deactivating PCI resources. Previously, if a device had more than 48 MSI interrupts, then activating message 48 (which has a rid == PCIR_BIOS) would incorrectly try to enable the PCI ROM BAR. Tested by: Olivier Cinquin ocinquin uci edu MFC after: 3 days
* Soft PMC support for ARM.fabient2012-05-233-11/+26
| | | | | | Callgraph is not captured, only current location. Sample system wide profiling: "pmcstat -Sclock.hard -T"
* vm_pager_object_lookup: small performance optimizationavg2012-05-231-6/+7
| | | | | | | do not needlessly lock an object if its handle doesn't match Reviewed by: kib, alc MFC after: 1 week
* Use consistent text at the begining of the files.tuexen2012-05-2340-181/+147
| | | | MFC after: 3 days
* Update copyright date.tuexen2012-05-231-2/+3
| | | | MFC after: 3 days
* Fix build:delphij2012-05-234-12/+12
| | | | | | | - Use %ll instead of %q for explicit long long casts; - Use %j instead of %q in XFS and cast to intmax_t. Tested with: make universe
* Don't force max payload size to 128. Root complex and Endpoint willyongari2012-05-231-2/+0
| | | | | | | | | negotiate with each other on the TLP payload size so blindly forcing the size to 128 can cause a completion error which in turn will stop device. Reported by: Geans Pin < geanspin <> broadcom dot com > MFC after: 5 days
* Make IPMI work in the bce driver even when the interface isyongari2012-05-231-1/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | configured down. Formerly, IPMI communication was lost whenever the interface was not up. The reason was that the BCE_EMAC_MODE register was not configured with the correct media settings. There are two parts to the fix. First, resetting the chip in bce_reset() causes the BCE_EMAC_MODE register to be initialized to a default value that does not necessarily correspond to the actual media settings. The fix implemented here is a bit of a hack. Ideally, at the end of bce_reset() we would poll the PHY to determine the negotiated media, and then we would set the BCE_EMAC_MODE register accordingly. That is difficult, since the PHY is abstracted behind the MII layer and is not supposed to be queried directly from the MAC driver. Instead, we read the BCE_EMAC_MODE register at the beginning of bce_reset() and then restore its media bits to their original values before returning. If IPMI is up and running, then the link is already established and the BCE_EMAC_MODE register is already set appropriately when bce_reset() is called. If IPMI is not running, no harm is done by preserving the BCE_EMAC_MODE settings. The driver will set the register properly once the interface is configured up and link is established. Second, bce_miibus_statchg() is sometimes called when the link is down. In that case, the reported media settings are invalid. Formerly, the driver used them anyway to setup the BCE_EMAC_MODE register. We now avoid changing any MAC registers unless link is active and the reported media settings are valid. Submitted by: jdp Tested by: jdp MFC after: 5 days
* Re-up the TX ath_buf limit from 128 to 512.adrian2012-05-221-1/+1
| | | | | | | | | I'll have to leave this high for now, until I've done some significant surgery with how ath_bufs (and descriptors) are handled. This should significantly cut down on the opportunities for a full TX queue hanging traffic. I'll continue making things work though; I'm mostly doing this for users. :)
* Fix use-after-free in kern_jail_set() triggered e.g. by attemptstrasz2012-05-221-6/+10
| | | | | | | | | | to clear "persist" flag from empty persistent jail, like this: jail -c persist=1 jail -n 1 -m persist=0 Submitted by: Mateusz Guzik <mjguzik at gmail dot com> MFC after: 2 weeks
* commandline -> command linedelphij2012-05-221-2/+2
| | | | MFC after: 1 week
* Fix some corner cases in the ieee80211_send_bar() handling.adrian2012-05-221-1/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * If the first call succeeded but failed to transmit, a timer would reschedule it via bar_timeout(). Unfortunately bar_timeout() didn't check the return value from the ieee80211_send_bar() reattempt and if that failed (eg the driver ic_raw_xmit() failed), it would never re-arm the timer. * If BARPEND is cleared (which ieee80211_send_bar() will do if it can't TX), then re-arming the timer isn't enough - once bar_timeout() occurs, it'll see BARPEND is 0 and not run through the rest of the routine. So when rearming the timer, also set that flag. * If the TX wasn't occuring, bar_tx_complete() wouldn't be called and the driver callback wouldn't be called either. So the driver had no idea that the BAR TX attempt had failed. In the ath(4) case, TX would stay paused. (There's no callback to indicate that BAR TX had failed or not; only a "BAR TX was attempted". That's a separate, later problem.) So call the driver callback (ic_bar_response()) before the ADDBA session is torn down, so it has a chance of being notified that things didn't quite go to plan. I've verified that yes, this does suspend traffic for ath(4), retry BAR TX even if the driver is failing ic_raw_xmit(), and then eventually giving up and sending a DELBA. I'll address the "out of ath_buf" issue in ath(4) in a subsequent commit - this commit just fixes the edge case where any driver is (way) out of internal buffers/descriptors and fails frame TX. PR: kern/168170 Reviewed by: bschmidt MFC after: 1 month
* The fix in r235291 re-broke the "allow.nomount" case. Re-fix itjamie2012-05-221-12/+14
| | | | by testing for the right parameter name.
* Do not incorrectly warn when printing a quad_t using "%qd" on 64-bit platforms.obrien2012-05-221-0/+4
|
* Don't leak locks in prison_racct_modify().trasz2012-05-221-1/+4
| | | | | Submitted by: Mateusz Guzik <mjguzik at gmail dot com> MFC after: 2 weeks
* Fix world after byacc import:bapt2012-05-2216-303/+302
| | | | | | | | - old yacc(1) use to magicially append stdlib.h, while new one don't - new yacc(1) do declare yyparse by itself, fix redundant declaration of 'yyparse' Approved by: des (mentor)
* Bump __FreeBSD_version for the byacc import, and update _bootstrap_tools.des2012-05-222-2/+5
|
* Fix panic with RACCT that could occur in low memory (or out of swap)trasz2012-05-222-1/+4
| | | | | | | | situations, due to fork1() calling racct_proc_exit() without calling racct_proc_fork() first. Submitted by: Mateusz Guzik <mjguzik at gmail dot com> (earlier version) Reviewed by: Mateusz Guzik <mjguzik at gmail dot com>
* Add the code for new Intel GPU driver, which supports GEM, KMS andkib2012-05-2281-0/+72060
| | | | | | | | | | works with new generations of GPUs (IronLake, SandyBridge and supposedly IvyBridge). The driver is not connected to the build yet. Sponsored by: The FreeBSD Foundation MFC after: 1 week
* A rewrite of the i810 bits of the agp(4) driver. New driver supportskib2012-05-229-638/+2273
| | | | | | | | operations required by GEMified i915.ko. It also attaches to SandyBridge and IvyBridge CPU northbridges now. Sponsored by: The FreeBSD Foundation MFC after: 1 month
* Fix enforcement of file size limit with O_APPEND on ZFS.trasz2012-05-221-3/+6
| | | | | | | | | | | | | | | vn_rlimit_fsize takes uio->uio_offset and uio->uio_resid into account when determining whether given write would exceed RLIMIT_FSIZE. When APPEND flag is specified, ZFS updates uio->uio_offset to point to the end of file. But this happens after a call to vn_rlimit_fsize, so vn_rlimit_fsize check can be rendered ineffective by thread that opens some file with O_APPEND and lseeks below RLIMIT_FSIZE before calling write. Submitted by: Mateusz Guzik <mjguzik at gmail dot com> MFC after: 2 weeks
* Fix a compilation error with some compilers: __attribute__harti2012-05-221-6/+4
| | | | | | requires two parenthesis for its argument, but instead of using __attribute__ directly, use the appropriate __nonnull macro from cdefs.h.
* Divide nand flash for DB6281 into two partitions. One for u-bootgber2012-05-221-0/+9
| | | | | | | and second one for general use. Obtained from: Semihalf Supported by: FreeBSD Foundation, Juniper Networks
* Add a new geom class which allows to divide NAND Flash chipgber2012-05-226-0/+433
| | | | | | | | | | into partitions. Partitions are created based on data in dts file which are extracted and interpreted by slicer. Obtained from: Semihalf Supported by: FreeBSD Foundation, Juniper Networks
* Make dumptid non-static. It is used by libkvm to detect whetherharti2012-05-221-1/+1
| | | | | | this is a VNET-kernel or not. gcc used to put the static symbol into the symbol table, clang does not. This fixes the 'netstat: no namelist' error seen on clang+VNET systems.
* Fix booting on ARM.andrew2012-05-221-1/+1
| | | | | | | | | In PHYS_TO_VM_PAGE() when VM_PHYSSEG_DENSE is set the check if we are past the end of vm_page_array was incorrect causing it to return NULL. This value is then used in vm_phys_add_page causing a data abort. Reviewed by: alc, kib, imp Tested by: stas
* Fix make depend.uqs2012-05-221-1/+1
|
* Fix up some corner cases with aggregation handling.adrian2012-05-222-5/+19
| | | | | | | | | | | | | | | | | | I've come across a weird scenario in net80211 where two TX streams will happily attempt to setup an aggregation session together. If we're very lucky, it happens concurrently on separate CPUs and the total lack of locking in the net80211 aggregation code causes this stuff to race. Badly. So >1 call would occur to the ath(4) addba start, but only one call would complete to addba complete or timeout. The TID would thus stay paused. The real fix is to implement some proper per-node (or maybe per-TID) locking in net80211, which then could be leveraged by the ath(4) TX aggregation code. Whilst I'm at it, shuffle around the debugging messages a bit. I like to keep people on their toes.
* Correct use_screen() and use_window() prototypes in curs_threads(3x).dim2012-05-221-2/+2
| | | | | Submitted by: Yanhui Shen <shen.elf@gmail.com> MFC after: 3 days
* Ignore the power button press event for resuming rather than startingiwasaki2012-05-221-5/+5
| | | | | | shutdown. MFC after: 2 days
* Remove redundant declaration of yyparsekevlo2012-05-221-1/+0
| | | | Reported by: tinderbox
* Add missing header needed by free()kevlo2012-05-221-0/+1
| | | | Reported by: tinderbox
* Wait until completion context unwinds before retrying CCBs that have beenjimharris2012-05-215-15/+147
| | | | | | | | | | | | | | | | | | | queued internally. This works around issue in the isci HAL where it cannot accept new I/O to a device after a resetting->ready state transition until the completion context has unwound. This issue was found by submitting non-tagged CCBs through pass(4) interface to a SATA disk with an extremely small timeout value (5ms). This would trigger internal resets with I/O in the isci(4) internal queues. The small timeout value had not been intentional (and original reporter has since changed his test to use 5sec instead), but it did uncover this corner case that would result in a hung disk. Sponsored by: Intel Reported and tested by: Ravi Pokala <rpokala at panasas dot com> Reviewed by: scottl (earlier version) MFC after: 1 week
* For now, add a quick debugging patch to log when the hw TXQ != the TID/AC.adrian2012-05-211-0/+12
|
* Rename ath_tx_cleanup() -> ath_tx_tid_cleanup() in order to not clashadrian2012-05-211-3/+3
| | | | with a symbol in if_ath.c
* Make most BPF ioctls() SMP-safe.melifaro2012-05-211-6/+47
| | | | | Approved by: kib(mentor) MFC in: 4 weeks
* Call bpf_jitter() before acquiring BPF global lock due to malloc() being ↵melifaro2012-05-213-29/+43
| | | | | | | | | | used inside bpf_jitter. Eliminate bpf_buffer_alloc() and allocate BPF buffers on descriptor creation and BIOCSBLEN ioctl. This permits us not to allocate buffers inside bpf_attachd() which is protected by global lock. Approved by: kib(mentor) MFC in: 4 weeks
* Fix old panic when BPF consumer attaches to destroying interface.melifaro2012-05-216-100/+138
| | | | | | | | | | | | | | | | | 'flags' field is added to the end of bpf_if structure. Currently the only flag is BPFIF_FLAG_DYING which is set on bpf detach and checked by bpf_attachd() Problem can be easily triggered on SMP stable/[89] by the following command (sort of): 'while true; do ifconfig vlan222 create vlan 222 vlandev em0 up ; tcpdump -pi vlan222 & ; ifconfig vlan222 destroy ; done' Fix possible use-after-free when BPF detaches itself from interface, freeing bpf_bif memory, while interface is still UP and there can be routes via this interface. Freeing is now delayed till ifnet_departure_event is received via eventhandler(9) api. Convert bpfd rwlock back to mutex due lack of performance gain (currently checking if packet matches filter is done without holding bpfd lock and we have to acquire write lock if packet matches) Approved by: kib(mentor) MFC in: 4 weeks
* Fix panic on attaching to non-existent interface (introduced by r233937, ↵melifaro2012-05-213-45/+163
| | | | | | | | | | | | | | | | pointed by hrs@) Fix panic on tcpdump being attached to interface being removed (introduced by r233937, pointed by hrs@ and adrian@) Protect most of bpf_setf() by BPF global lock Add several forgotten assertions (thanks to adrian@) Document current locking model inside bpf.c Document EVENTHANDLER(9) usage inside BPF. Approved by: kib(mentor) Tested by: gnn MFC in: 4 weeks
* Add checks for memory allocation failures in appropriate places, andghelmer2012-05-211-12/+27
| | | | | | | | avoid creating bad entries in the grp list as a result of memory allocation failures while building new entries. PR: bin/83340 Reviewed by: delphij (prior version of patch)
* Apply style(9) to return and switch/case statements.ghelmer2012-05-211-19/+22
| | | | Reviewed by: delphij (prior version of the patch)
* Re-add 'ic' and properly wrap it in the SUPERG macro.adrian2012-05-211-0/+3
|
* Don't recurse into libssp when MK_SSP is set to no.marcel2012-05-211-1/+5
|
* Add missing \n when generating pkg.confbapt2012-05-211-1/+1
| | | | | | Reported by: beat Approved by: des (mentor) MFC after: 1 day
* Regenerate usb.confhselasky2012-05-211-5/+13
| | | | MFC after: 3 days
* Import byacc from invisible island, it brings us lots of compatibilities withbapt2012-05-21175-5995/+60981
|\ | | | | | | | | | | | | | | | | | | | | | | | | bison, keeping full compatibility with our previous yacc implementation. Also bring the ability to create reentrant parser This fix bin/140309 [1] PR: bin/140309 [1] Submitted by: Philippe Pepiot <ksh@philpep.org> [1] Approved by: des (mentor) MFC after: 1 month
OpenPOWER on IntegriCloud