summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* So here I am, also born in USSR.danfe2004-08-231-0/+1
| | | | Approved by: fjoe (mentor)
* Don't try to translate the control message unless we're certain it'sdes2004-08-231-1/+2
| | | | | | | | valid; otherwise a caller could trick us into changing any 32-bit word in kernel memory to LINUX_SOL_SOCKET (0x00000001) if its previous value is SOL_SOCKET (0x0000ffff). MFC after: 3 days
* Update documentation to match reality: glob() sorts its result accordingtjr2004-08-231-4/+4
| | | | | | | to the current LC_COLLATE setting, not in "ASCII order". PR: 54391 MFC after: 1 week
* Restore FD_DEBUG for pc98.nyan2004-08-231-0/+4
|
* s/the on/on the/blackend2004-08-231-1/+1
| | | | | PR: misc/70842 Submitted by: Sean C. Farley <sean-freebsd@farley.org>
* o Fix whitespace bug introduced in the previous commit.sobomax2004-08-232-24/+8
| | | | | | | | Submitted by: ru o Simplify p4tcc_power_profile(). Submitted by: maxim
* o Extend boot output: print out mimimum/maximum performance value and numbersobomax2004-08-232-2/+38
| | | | | | | of performance steps available; o similarly to Enhanced SpeedStep driver, export list of all available steps via hw.p4tcc.cpuperf_levels sysctl.
* Add missing GEOM classes, which are aware of geom(8).pjd2004-08-231-0/+6
| | | | Submitted by: kuriyama
* Make this compile again in the standalone and the MODULES_WITH_WORLDimp2004-08-231-1/+5
| | | | | | environments. Chances are good that this doesn't produce a good module, but I leave the proper defaults to the dummy opt_* files to the author.
* Remove in6_prefix.[ch] and the contained router renumbering capability.rwatson2004-08-238-1328/+0
| | | | | | | | | | | | The prefix management code currently resides in nd6, leaving only the unused router renumbering capability in the in6_prefix files. Removing it will make it easier for us to provide locking for the remainder of IPv6 by reducing the number of objects requiring synchronized access. This functionality has also been removed from NetBSD and OpenBSD. Submitted by: George Neville-Neil <gnn at neville-neil.com> Discussed with/approved by: suz, keiichi at kame.net, core at kame.net
* Temporarily back out r1.74 as it seems to cause a number of regressionskan2004-08-231-12/+5
| | | | | accordimg to numerous reports. It might get reintroduced some time later when an exact failure mode is understood better.
* Pass a correct lowaddr to bus_dma_tag_create(), lnc(4) cards can onlymux2004-08-221-1/+1
| | | | | | | | | | | | | deal with 24-bit addresses. While the two other attachments, namely isa and cbus, do it properly, the PCI attachment was passing BUS_SPACE_MAXADDR instead of BUS_SPACE_MAXADDR_24BIT. This bug became apparent with the new contigmalloc() code. This fixes the problem reported with lnc(4) interfaces inside VMWare, and should theoritically also fix any user of a PCI lnc(4) card. It is a RELENG_5 MFC candidate. Tested by: Florian Le Goff <madflo@beertech.org>
* Style update: use newer style function prototypes in if_sl.c inrwatson2004-08-221-38/+15
| | | | prep for merging locking.
* Move the cow field between wire_count and hold_count. This is themarcel2004-08-221-1/+1
| | | | | | | | position that is 64-bit aligned and makes sure that the valid and dirty fields are also 64-bit aligned. This means that if PAGE_SIZE is 32K, the size of the vm_page structure is only increased by 8 bytes instead of 16 bytes. More importantly, the vm_page structure is either 120 or 128 bytes on ia64. These are "interesting" sizes.
* When creating a new md, wait for geom's event queue to become emptycperciva2004-08-221-0/+1
| | | | | | | | | | before returning. Device nodes are created via the "taste" mechanism, so this is necessary in order to make sure that devfs entries are created before mdconfig(8) returns. This may be a MFC candidate for 5.3. Suggested by: phk
* The new contigmalloc code is exposing a lot of misuses of busdma memorygreen2004-08-221-21/+15
| | | | | | | | | | | | | | | | | | allocation. Notably, in this case, the driver tries to allocate several pieces of memory and then fails if the pieces allocated after the first do not come after it physically, and within a specific range (8MB I believe). Of course, this could just as easily fail for any number of reasons, but it almost always fails now that contiguous allocations start at the end of possible specified memory locations rather than the beginning. Allocate all the possibly-needed memory up front, even though it's a waste, to get around this. The least bogus solution would be to take the physical address from the first allocation and create a new tag that specified that further allocations must follow it within that 8MB window, then use that when allocating new channels, but that's left for anyone else that really feels like doing it. Tested by: Erwin Lansing <erwin@lansing.dk>
* Implement the possibility to remove drives.le2004-08-221-0/+90
|
* Loopback a fix from Cedric Berger:mlaier2004-08-221-1/+8
| | | | | | | | Fix table add/replace commands with securelevel=2. Reported by James J. Lippard. Discussed with: yongari MFC after: 5 days
* Allow early drop for non-ALTQ enabled queues in an ALTQ-enabled kernel.mlaier2004-08-221-13/+14
| | | | | | | | | | Previously the early drop was disabled unconditionally for ALTQ-enabled kernels. This should give some benefit for the normal gateway + LAN-server case with a busy LAN leg and an ALTQ managed uplink. Reviewed and style help from: cperciva, pjd
* Regression tests for 'verify reading' algorithm.pjd2004-08-222-0/+69
|
* Fix sysctl name.pjd2004-08-221-1/+1
|
* Implementation of 'verify reading' algorithm, which uses parity data forpjd2004-08-225-24/+202
| | | | | | | | verification of regular data when device is in complete state. On verification error, EIO error is returned for the bio and sysctl kern.geom.raid3.stat.parity_mismatch is increased. Suggested by: phk
* Workaround devices that responds with registers as *both* master & slave,sos2004-08-221-2/+10
| | | | but fail utterly when we try to talk to the "fake" device.
* Use securelevel_gt instead of reading global securelevel unprotected.mlaier2004-08-221-0/+5
| | | | | Submitted by: yongari MFC after: 3 days
* opt_agp.h is not required anymore.nyan2004-08-221-1/+1
|
* MFi386: revision 1.215.nyan2004-08-221-3/+0
|
* Merged from sys/dev/fdc/fdc.c revision 1.283.nyan2004-08-222-8/+0
|
* Make debug.kdb.stop_cpus also a TUNABLE() so it can be set prior to bootrwatson2004-08-221-0/+1
| | | | to help debug early nasty hangs.
* Don't need to assert Giant in fw_output(), only in the firewire startrwatson2004-08-221-2/+0
| | | | routine.
* In the PCI error interrupt handler, specify the width of the PCI configurationgibbs2004-08-221-6/+7
| | | | | | cycle using the correct argument. The location and width were reversed. MFC in: 2 days
* Set AHD_BUSFREEREV_BUG in the bug field for Rev B chips, not thegibbs2004-08-221-3/+3
| | | | | | | feature field. Reported by: Ken Westerback <krw@openbsd.org> MFC in: 2 days
* Add forgotten format specifier in a KASSERT and shut up the compiler.le2004-08-221-1/+2
| | | | Submitted by: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk>
* Only compile fbsd-thread.c on amd64 and i386, other architecturesdavidxu2004-08-221-1/+5
| | | | have not been tested yet.
* Unbreak the build. Translators, please let me knowhrs2004-08-225-0/+90
| | | | if I break something in your localized docs.
* Fix comments, most are style fix.davidxu2004-08-221-21/+11
|
* Trim EOL white spaces.maxim2004-08-221-5/+4
|
* Check a return code from read(2) correctly.maxim2004-08-221-1/+1
| | | | | PR: kern/70815 Submitted by: info [at] haakh.de
* Fix some text messages.davidxu2004-08-221-2/+2
|
* Part 2 of fixing the boot code: gcc 3.4 fixes.marcel2004-08-222-2/+2
| | | | | | | | | The whole problem seems to be size. Which is odd, because it is said that size doesn't matter. Anyway... Add -Os to strategic places in the makefile to have the final loader be as mall as possible. This seems to be enough to make it work. For now... I think something is more fundamentally wrong; or something more fundamental is wrong. Potato, potaato.
* Add code to support statically linked binary and .core file of threadeddavidxu2004-08-221-177/+367
| | | | program.
* Found another one. Why does mdconfig hate me? Add a "sleep 5" tokensmith2004-08-221-0/+2
| | | | | | | | | | | this script, without it sparc64 ISO building was consistently failing because the /dev/md0 device name was not present when the commands following mdconfig ran. Apparently there is the possibility of a delay between when mdconfig finishes and the names become visible in /dev. Yes, we could code this better than an unconditional call to "sleep 5" but IMHO we should fix the underlying problem instead. MFC after: 3 days
* diff reduction for upcoming patch. Use a macro that masksjulian2004-08-221-8/+9
| | | | | some of the odd goings on with sub-structures, because they will go away anyhow.
* Add support for Intel E7205 AGP.anholt2004-08-222-0/+12
| | | | | PR: kern/69858 Submitted by: Jacobo Arvelo <unix4all at gulic dot org>
* Currently, if the secure level is low enough, system flags cancsjp2004-08-221-1/+1
| | | | | | | | | | | | | | | | | | | be manipulated by prison root. In 4.x prison root can not manipulate system flags, regardless of the security level. This behavior should remain consistent to avoid any surprises which could lead to security problems for system administrators which give out privileged access to jails. This commit changes suser_cred's flag argument from SUSER_ALLOWJAIL to 0. This will prevent prison root from being able to manipulate system flags on files. This may be a MFC candidate for RELENG_5. Discussed with: cperciva Reviewed by: rwatson Approved by: bmilekic (mentor) PR: kern/70298
* When sliding the m_data pointer forward, update m_pktrhdr.len as wellrwatson2004-08-221-1/+3
| | | | | | | | | as m_len, or the pkthdr length will be inconsistent with the actual length of data in the mbuf chain. The symptom of this occuring was "out of data" warnings from in_cksum_skip() on large UDP packets sent via the loopback interface. Foot shot: green
* Part 1 of fixing the boot code: binutils 2.15 fixes.marcel2004-08-222-1/+202
| | | | | | | | | | | | The binutils 2.15 assembler now automaticly and non-optionally adds the .eh_frame section for unwind information. This section appears to wreck havoc to the final boot code. Fix this by using a special linker script that discards the .eh_frame sections, but is otherwise identical to the linker internal script used for -N. Compiler used: gcc 3.3.5 Verified with: binutils 2.14 & binutils 2.15 (stock and in-tree) Tested with: /boot/loader & /boot/netboot
* In the previous revision, I failed to condition an early release of Giantalc2004-08-221-1/+2
| | | | | | | in vm_fault() on debug_mpsafevm. If debug_mpsafevm was not set, the result was an assertion failure early in the boot process. Reported by: green@
* If a tunable for the routing socket netisr queue max is defined, allow itrwatson2004-08-211-1/+3
| | | | | to override the default value, rather than the default value overriding the tunable.
* Allow the size of the routing socket netisr queue to be configured usingrwatson2004-08-211-1/+6
| | | | | | | | | | the tunable or sysctl 'net.route.netisr_maxqlen'. Default the maximum depth to 256 rather than IFQ_MAXLEN due to the downsides of dropping routing messages. MT5 candidate. Discussed with: mdodd, mlaier, Vincent Jardin <jardin at 6wind.com>
* Add version history.pjd2004-08-211-0/+5
|
OpenPOWER on IntegriCloud