summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Get in sync with reality: TurboLaser was never really well supported towilko2004-11-092-6/+0
| | | | | start with, so let it die in peace. While there, remove Multia-class as 486-like performance will not buy us much when 6.x arrives.
* Detect root mount attempts on the flag, not on the NULL path.phk2004-11-094-4/+4
|
* Refuse attempts to mount root filesystemphk2004-11-097-6/+11
|
* Refuse attemps to mount root filesystemphk2004-11-094-2/+6
|
* Revert the noexec,nosuid,nodev options for md /tmp file systems, sincekeramida2004-11-092-4/+3
| | | | | | the change in the default behavior may break existing, working setups. Requested by: brooks
* Remove the #if 0 wrapping around !ALTQ stuff that can't be used due to ABImlaier2004-11-091-34/+0
| | | | stability anyway.
* Attempt to fix a number of race conditions in the handling ofiedowse2004-11-094-49/+125
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | transfer timeouts that typically cause a transfer to be completed twice, resulting in panics and page faults: o A transfer completion interrupt could arrive while an abort_task event was set up, so the transfer would be aborted after it had completed. This is very easy to reproduce. Fix this by setting the transfer status to USBD_TIMEOUT before scheduling the abort_task so that the transfer completion code will ignore it. o The transfer completion code could execute concurrently with the timeout callout, leaving the callout blocked (e.g. waiting for Giant) while the transfer completion code runs. In this case, callout_stop() does not prevent the callout from running, so again the timeout code would run after the transfer was complete. Handle this case by checking the return value from callout_stop(), and ignoring the transfer if the callout could not be removed. o Finally, protect against a timeout callout occurring while a transfer is being aborted by another process. Here we arrange for the timeout processing to ignore the transfer, and use callout_drain() to ensure that the callout has really gone before completing the transfer. This was tested by repeatedly performing USB transfers with a timeout set to approximately the same as the normal transfer completion time. In the PR below, apparently this occurred by accident with a particular printer and the default timeout. PR: kern/71491
* When a port cannot be set up, report the error code in the `disablingiedowse2004-11-091-2/+2
| | | | port X' message.
* Since sb_timeo type was increased to int, use INT_MAX instead of SHRT_MAX.glebius2004-11-091-3/+3
| | | | | | | | This also gives us ability to close PR. PR: kern/42352 Approved by: julian (mentor) MFC after: 1 week
* Update the manpage for acpi_panasonic for new models supported.njl2004-11-091-16/+16
| | | | | Submitted by: OGAWA Takaya MFC after: 1 day
* The correct name of the long option is --line-buffered,keramida2004-11-091-2/+3
| | | | | | | | not --line-bufferring. PR: docs/72985 Submitted by: John Engelhart <johne@zang.com> MFC after: 1 week
* Use the RET macro.cognet2004-11-0917-52/+52
| | | | | For setjmp() and longjmp(), put the signal mask where it's supposed to be, instead of in the space reserved for fp regs.
* Use the RET macro.cognet2004-11-0927-302/+301
|
* Import a RET macro, that will use bx if the arch supports it.cognet2004-11-091-0/+36
| | | | Obtained from: NetBSD
* Add a week alias __siglongjmp => siglongjmp.cognet2004-11-091-0/+1
|
* Zero the tag when it's allocated. Also fix a printf format problem. Thisscottl2004-11-091-2/+3
| | | | should fix the problems introduced several hours ago.
* Fixed fd related tools on pc98.nyan2004-11-092-0/+63
| | | | Submitted by: Watanabe Kazuhiro <CQG00620@nifty.ne.jp>
* Add FL_MFM flag to the fd_native_types structure.nyan2004-11-092-4/+4
| | | | Submitted by: Watanabe Kazuhiro <CQG00620@nifty.ne.jp>
* Improve readability with a bunch of typedefs for the pager ops.phk2004-11-091-7/+15
| | | | These can also be used for prototypes in the pagers.
* Add -c option that calculates the overhead of read I/O ops.sos2004-11-092-2/+48
|
* Bump document datebrueffer2004-11-091-1/+1
| | | | Reminded by: ru
* Bump MAC Framework version to 2 in preparation for the upcoming API/ABIrwatson2004-11-095-5/+5
| | | | | | changes associated with adding System V IPC support. This will prevent old modules from being used with the new kernel, and new modules from being used with the old kernel.
* Bump document date for the {tmp,var}mfs_flags change.keramida2004-11-091-1/+1
|
* Add two new rc.conf options: tmpmfs_flags and varmfs_flags.keramida2004-11-095-7/+41
| | | | | | | | | | | | | | These can be used to pass extra options to the mdmfs(8) utility, to customize the finer details of the md file system creation (i.e. to turn on/off softupdates, to specify a default owner for md filesystem, etc). Use these two new flags to mount tmpmfs and varmfs without softupdates, since it doesn't make much sense to use SU on malloc-backed file systems. Reviewed by: mtm Inspired by: J. D. Bronson, jbronson at wixb dot com
* Fix a double-free in the 'hlen > m->m_len' sanity check.andre2004-11-091-1/+1
| | | | | Bug report by: <james@towardex.com> MFC after: 2 weeks
* Merge the following from the English version:hrs2004-11-091-240/+12
| | | | 1.256 -> 1.261 ja_JP.eucJP/hardware/common/dev.sgml
* First pass at replacing the single global bounce pool with sub-pools that arescottl2004-11-091-36/+140
| | | | | | | | | | | | | | appropriate for different tag requirements. With the former global pool, bounce pages might get allocated that are appropriate for one tag, but not appropriate for another, but the system had no way to distinguish between them. Now zones with distinct attributes are created to hold pages, and each tag that requires bouncing is associated with a zone. New zones are created as needed if no existing zones can meet the requirements of the tag. Stats for each zone are tracked via the hw.busdma sysctl node. This should help drivers that are failing with mysterious data corruption. MFC After: 1 week
* unsigned long -> u_longnjl2004-11-091-1/+1
|
* MFen 1.259 -> 1.261den2004-11-091-3/+4
|
* clean up some tunables that should of been removed a while ago...jmg2004-11-091-4/+0
|
* Whitespace fix.marcel2004-11-091-1/+1
|
* Prepare for a subsequent import: If the first letter of the filenamemarcel2004-11-091-35/+43
| | | | | | | | | | | changes, start on a new line. Insertion of a filename will keep the diff limited to the block of filenames that have the same first letter instead of creating a huge diff. While here, move remote.c after the remote-*.c files and move tui.c after the tui-*.c files. This matches the order of ls(1) and makes it easier to compare object files created by a stock gdb(1) build with the list of files we have here. This is a non-functional change only.
* Add info about some systems that refuse to switch via sysctl.njl2004-11-091-2/+8
| | | | MFC after: 1 day
* Tell the BIOS we want to handle brightness switching as well as outputnjl2004-11-091-24/+33
| | | | | | | switching. Don't initialize variables in their declaration. Reduce stack usage for device names. Minor style cleanups. MFC after: 1 week
* Bump document date.kensmith2004-11-091-1/+1
| | | | | | Noticed by: trhodes Pointy hat: kensmith MFC after: 1 week
* Add newsyslog(8) to the "See Also" section.kensmith2004-11-091-1/+2
| | | | MFC after: 1 week
* Fix signedness idiocy in previous commit. Pass the pointy hat...des2004-11-091-1/+1
|
* Back out previous commit; INT64_MAX (defined in <stdint.h>) is not alwaysdes2004-11-091-1/+1
| | | | visible when <sys/resource.h> is included.
* Drop Giant lock before grabbing the topology lock.pjd2004-11-092-0/+4
|
* Remove a pre-tier-1 kernel compatability helper. This means a 6.x loaderpeter2004-11-081-2/+0
| | | | won't boot a pre-5.1 development amd64 kernel. That's no big loss though.
* Remove __P, as well as other non-FreeBSD relevant code.imp2004-11-081-50/+2
|
* D-Link DFE-580TX is supportedbrueffer2004-11-081-0/+2
| | | | MFC after: 3 days
* Removed the remnants of gx(4).ru2004-11-082-2/+2
|
* If device is marked as beeing destroyed, deny all access requests.pjd2004-11-082-2/+4
|
* Remove if_gx.4 MLINK, also add one for if_cnw.4brueffer2004-11-081-1/+1
|
* gx(4) is gone, remove any referencesbrueffer2004-11-081-1/+0
|
* gx(4) is gone, reference em(4) insteadbrueffer2004-11-081-1/+1
|
* gx(4) is gone, remove any referencesbrueffer2004-11-085-9/+0
|
* Save a pointless FILE_LOCK_ASSERT() call in fhold.phk2004-11-081-1/+1
|
* The gx driver is gone, kill the manpage as well.brueffer2004-11-082-192/+0
|
OpenPOWER on IntegriCloud