summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* sysctl(9) cleanup checkpoint: amd64 GENERIC builds cleanly.mdf2011-01-1213-22/+22
| | | | Commit the kernel changes.
* sysctl(9) cleanup checkpoint: amd64 GENERIC builds cleanly.mdf2011-01-122-2/+2
| | | | Commit the security directory.
* sysctl(9) cleanup checkpoint: amd64 GENERIC builds cleanly.mdf2011-01-122-12/+12
| | | | Commit the geom piece.
* sysctl(9) cleanup checkpoint: amd64 GENERIC builds cleanly.mdf2011-01-1221-100/+102
| | | | Commit the rest of the devices.
* sysctl(9) cleanup checkpoint: amd64 GENERIC builds cleanly.mdf2011-01-1211-40/+40
| | | | Commit the net* piece.
* sysctl(9) cleanup checkpoint: amd64 GENERIC builds cleanly.mdf2011-01-123-24/+24
| | | | Commit the cxgb driver piece.
* sysctl(9) cleanup checkpoint: amd64 GENERIC builds cleanly.mdf2011-01-127-23/+23
| | | | Commit the netgraph piece.
* sysctl(9) cleanup checkpoint: amd64 GENERIC builds cleanly.mdf2011-01-123-27/+27
| | | | Commit the zfs piece.
* sysctl(9) cleanup checkpoint: amd64 GENERIC builds cleanly.mdf2011-01-124-239/+239
| | | | Commit the Intel drivers.
* Fix wrapping of 20110103 entry.brucec2011-01-121-3/+4
|
* Fix cross-reference to gvinum(8).brucec2011-01-121-1/+1
|
* Fix several bugs in the ARP code related to improperly formattedgnn2011-01-121-1/+16
| | | | | | | | | | | | | | | packets. *) Reject requests with a protocol length not equal to 4. This is IPv4 and there is no reason to accept anything else. *) Reject packets that have a multicast source hardware address. *) Drop requests where the hardware address length is not equal to the hardware address length of the interface. Pointed out by: Rozhuk Ivan MFC after: 1 week
* Fix up the grammar.ae2011-01-121-3/+3
| | | | | PR: docs/153933 MFC after: 3 days
* Add type checking for static and dynamic sysctls using scalar types.mdf2011-01-122-50/+147
| | | | | | | | | | | | The code is turned off until the tree is fixed up so it compiles. __FreeBSD_version was already bumped once today, so skip the bump, but add an entry to UPDATING. Note that __DESCR() is used in the SYSCTL_OID() macro and so is not needed in macros that invoke it. This use was inconsistent in the file and I have made it consistent any lines already being changed. Reviewed by: bde (previous version), -arch (previous version)
* execve(2), not fork(2) resets signal handler to the default value (if it isn'tpjd2011-01-121-3/+3
| | | | | | | ignored). Correct comment talking about that. Pointed out by: kib MFC after: 3 days
* Update dialog to version 20100428. This changes the license under whichnwhitehorn2011-01-12363-1541/+61311
| | | | | | | | | | | | | dialog is distributed from GPLv2 to LGPLv2 and introduces a number of new features and a new and better libdialog API. The existing libdialog will be kept temporarily as libodialog for compatibility purposes until sade, sysinstall and tzsetup have been either updated or replaced. __FreeBSD_version is now 900030. Discussed on: -current Approved by: core Obtained from: http://invisible-island.net/dialog
* Add a note that when custom signal handler is installed for a signal,pjd2011-01-121-0/+5
| | | | | | | | | signal action is restored to default in child after fork(2). In this case there is no need to do anything with dummy SIGCHLD handler, because after fork(2) it will be automatically reverted to SIG_IGN. Obtained from: Wheel Systems Sp. z o.o. http://www.wheelsystems.com MFC after: 3 days
* Install default signal handlers before masking signals we want to handle.pjd2011-01-121-0/+8
| | | | | | | | | | | | | It is possible that the parent process ignores some of them and sigtimedwait() will never see them, eventhough they are masked. The most common situation for this to happen is boot process where init(8) ignores SIGHUP before starting to execute /etc/rc. This in turn caused hastd(8) to ignore SIGHUP. Reported by: trasz Obtained from: Wheel Systems Sp. z o.o. http://www.wheelsystems.com MFC after: 3 days
* Sector size can not be greater than MAXPHYS. Since GRAID3 calculatesae2011-01-122-0/+9
| | | | | | | | sector size from user-specified block size, report to user about big blocksize. PR: kern/147851 MFC after: 1 week
* The message ring interrupt needs to be enabled for all cpus, not justjchandra2011-01-121-65/+52
| | | | | | | | | | | | | the ones which run the message ring handler. Some bits of the interrupt mask are part of the status register which is saved with the process context, and these bits are initialized from the cpu on which the process is created. This means that all the processes should have the same value for these interrupt mask bits, so that the interrupt mask remains the same regardless of what thread is scheduled on the cpu. Submitted by: Sriram Gorti (srgorti at netlogicmicro dot com)
* Sector size can not be greater than MAXPHYS.ae2011-01-121-0/+4
| | | | MFC after: 1 week
* Provide up-to-date estimates that are pessimal today...imp2011-01-121-1/+2
|
* For re(4) controllers that uses new jumbo frame scheme(RTL8168C/D/E),yongari2011-01-121-2/+7
| | | | | | | | | | | | | | | | | | | limit maximum RX buffer size to RE_RX_DESC_BUFLEN instead of blindly configuring it to 16KB. Due to lack of documentation, re(4) didn't allow jumbo frame on these controllers. However it seems controller is confused with jumbo frame such that it can DMA the received frame to wrong address instead of splitting it into multiple RX buffers. Of course, this caused panic. Since re(4) does not support jumbo frames on these controllers, make controller drop frame that is longer than RE_RX_DESC_BUFLEN sized frame. Fortunately RTL810x controllers, which do not support jumbo frame, have no such issues but this change also limited maximum RX buffer size allowed to RTL810x controllers. Allowing 16KB RX buffer for controllers that have no such capability is meaningless. MFC after: 3 days
* A couple problems discovered by Andrew Boyer:jfv2011-01-121-3/+11
| | | | | | | | | - failure code in em_xmit got mangled along the way and was not properly handling errors. - local timer code had a leftover UNLOCK call that should be removed. MFC after 3 days
* Proving once again, I can't typo: fix a type.imp2011-01-111-1/+1
|
* - Retire some unused ithread priorities: PI_TTYHIGH, PI_TAPE, andjhb2011-01-112-22/+11
| | | | | | PI_DISKLOW. While here, rename PI_TTYLOW to PI_TTY. - Add a macro PI_SWI() that takes a SWI_* constant as an argument and returns the suitable thread priority.
* Always use PRI_BASE() when checking the base type of a thread's priorityjhb2011-01-111-2/+2
| | | | | | class. MFC after: 2 weeks
* Don't re-use MODINFOMD_BOOTINFO as MODINFOMD_DTBP. It breaksmarcel2011-01-111-1/+2
| | | | | compatibility without any means for the kernel to work with an older loader.
* Add manpage for runfw, the Ralink RT2700U, RT2800U and RT3000U firmwarethompsa2011-01-113-6/+65
| | | | | | module. Also fix a few nits in run.4. Submitted by: Akinori Furukoshi
* Allow runfw(4) to be compiled in to the kernel.thompsa2011-01-111-0/+14
| | | | Submitted by: Akinori Furukoshi
* Add new functions, fcu_fan_set_pwm and fcu_fan_get_pwm, to set and getandreast2011-01-111-58/+172
| | | | | | | | | | | | | the pwm values. We can now set the fan's speed of a PWM controlled fan with % numbers between 30 and 100 % instead of trying to model a % number based on rpm. The fcu chip offers both, the dutycycle and the rpm value of the PWM controlled fans. I added the rpm value to the list of information available via sysctl(8). Tested by: Paul Mather <paul at gromit dlib vt edu> Approved by: nwhitehorn (mentor)
* Work around a witness(4) panic introduced in r217238.jkim2011-01-111-8/+26
| | | | Reported by: jh
* Fix a witness(4) warning introduced in r217238.jkim2011-01-111-13/+18
|
* Update the uplcom(4) man page to reflect the devices currently supported bygavin2011-01-111-10/+78
| | | | | | uplcom(4). MFC after: 1 week
* Improve or fix some comments. No functional change.gavin2011-01-111-10/+10
| | | | MFC after: 1 week
* Minor improvements in the wording of a comment. Document tinderbox target.imp2011-01-111-1/+3
|
* Remove unneeded includes of <sys/linker_set.h>. Other headers that usejhb2011-01-11109-109/+0
| | | | | | it internally contain nested includes. Reviewed by: bde
* Remove a bullet point that appears to have been accidentally inserted twice.gavin2011-01-111-1/+0
| | | | | | | It has also been included within the feature lists to which it is relevant. Submitted by: tobez MFC after: 1 week
* Remove redundant check.ae2011-01-111-2/+1
| | | | MFC after: 1 week
* Round GNOP provider's mediasize to its sectorsize. This prevents KASSERTae2011-01-111-0/+2
| | | | | | | in g_io_request when geom classes doing tasting. PR: kern/147852 MFC after: 1 week
* Initialize PCIe buses and add preliminary support for 64-bit BARs.jmallett2011-01-111-215/+321
|
* Fix a typo.davidxu2011-01-111-1/+1
| | | | Submitted by: avg
* Fixe some whitespace nits that were introduced in r216758.lstewart2011-01-111-7/+7
| | | | | | | Sponsored by: FreeBSD Foundation Submitted by: pjd MFC after: 10 weeks X-MFC with: r216758
* Fix hhook_head_is_virtualised() so that "ret" can't be used uninitialised.lstewart2011-01-111-4/+5
| | | | | | | Sponsored by: FreeBSD Foundation Submitted by: pjd MFC after: 9 weeks X-MFC with: r216615
* Fix some minor style/readability nits in hhook.lstewart2011-01-111-6/+3
| | | | | | | Sponsored by: FreeBSD Foundation Submitted by: pjd MFC after: 9 weeks X-MFC with: r216615
* When driver is not running, do not send DUMP command to controlleryongari2011-01-101-0/+5
| | | | | | and just show old (cached) values. Controller will not respond to the command unless MAC is enabled so DUMP request for down interface caused request timeout.
* Implement TSO on RealTek RTL8168/8111 C or later controllers.yongari2011-01-102-21/+21
| | | | | | | | | | | | RealTek changed TX descriptor format for later controllers so these controllers require MSS configuration in different location of TX descriptor. TSO is enabled by default for controllers that use new descriptor format. For old controllers, TSO is still disabled by default due to broken frames under certain conditions but users can enable it. Special thanks to Hayes Wang at RealTek. MFC after: 2 weeks
* Add IDs for HighPoint RocketRAID 64x controllers.mav2011-01-101-0/+2
| | | | | | | | | | | | These controllers consist of two Marvell 88SE9128 6Gbps SATA chips and PLX PCIe bridge. As result, they seem to be agree to work with ahci(4) as usual HBAs. The only noticed issue is that RAID BIOS disables all drive caches during boot, though `camcontrol cmd ...` is able to fix that. Those who wants RAID functionality can still use closed proprietary driver from HighPoint site. MFC after: 1 week
* Count output bytes and packets.jmallett2011-01-102-2/+8
|
* Shorten device name so it fits into vmstat -i.jmallett2011-01-101-3/+3
|
OpenPOWER on IntegriCloud