| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
those options that is frequently misunderstood, and ends up on -questions.
PR: 21852
|
|
|
|
|
|
|
|
|
|
| |
to reinstall boot1 after a 'make world'.
Unfortunately this means that people who have already installed a new
boot1 from a 'make world' after 2000/09/18 *must* reinstall it after
their next build using something like:
# disklabel -B /dev/da0c
|
| |
|
|
|
|
|
|
| |
Remove #if DO_BSD_COMPRESS
They are the wrong way to enable/disable features and undocumented to boot.
|
|
|
|
| |
The i386 UP case was messily different.
|
|
|
|
|
|
|
|
| |
of IP datagram. This fixes the problem when firewall denied fragmented
packets whose last fragment was less than minimum protocol header size.
Found by: Harti Brandt <brandt@fokus.gmd.de>
PR: kern/22309
|
| |
|
|
|
|
|
|
|
| |
it for now with an option.
This option is already deprecated, and will be removed when the
entropy-harvesting code is fast enough to warrant it.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
it can function before malloc(9) is up and running.
- Add two new options WITNESS_DDB and WITNESS_SKIPSPIN. If WITNESS_SKIPSPIN
is enabled, then spin mutexes are ignored by the WITNESS code. If
WITNESS_DDB is turned on and DDB is compiled into the kernel, then the
kernel will drop into DDB when either a lock hierarchy violation occurs
or mutexes are held when going to sleep.
- Add some new sysctls:
debug.witness_ddb is a read-write sysctl that corresponds to WITNESS_DDB.
The kernel option merely changes the default value to on at boot.
debug.witness_skipspin is a read-only sysctl that one can use to determine
if the kernel was compiled with WITNESS_SKIPSPIN.
- Wipe out the BSD/OS-specific lock order lists. We get to build our own
lists now as we add mutexes to the kernel.
|
|
|
|
|
|
|
|
|
| |
the PCI latency timer value to 0x80. Davicom's Linux driver does this,
and it drastically reduces the number of TX underruns in my tests. (Note:
this is done only for the Davicom chips. I'm not sure it's a good idea to
do it for all of them.)
Again, still waiting on confirmation before merging to stable.
|
| |
|
|
|
|
|
| |
unstaticize chn_start()
add reset/resetdone functions to channels
|
| |
|
| |
|
|
|
|
|
| |
Also add a comment about a bogus assumption in the current code found at
bsdcon by jhb.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
change_ruid() in kern_prot.c. This fixes an incorrect use
of chgproccnt().
Update both osf1_setuid() and osf1_setgid() to use setsugid() instead
of just frobbing the flag.
(mostly) submitted by: truckman
|
| |
|
|
|
|
|
|
|
|
| |
in the code enforces this. So, do not check for and attempt a
false reassembly if only IP_RF is set.
Also, removed the dead code, since we no longer use dtom() on
return from ip_reass().
|
| |
|
|
|
|
|
|
| |
This was first fixed in rev 1.82 but then broken in rev 1.125.
PR: 6177
|
| |
|
|
|
|
| |
Increment isdn4bsd step.
|
|
|
|
| |
Submitted by: Hans Petter Selasky <hselasky@c2i.net>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
DM9100/DM9102 chips. Do not set DC_TX_ONE. The DC_TX_USE_TX_INTR flag
causes dc_encap() to set the 'interrupt on TX completion' bit only
once every 64 packets. This is an attempt to reduce the number
of interrupts generated by the chip. You're supposed to get a 'no more
TX buffers left' interrupt once you hit the last packet whether you
ask for one or not, however it seems the Davicom chip doesn't generate
this interrupt, or at least it doesn't generate it under the same
circumstances. The result is that if you transmit n packets, where
n is less than 64, and then wait 5 seconds, you'll get a watchdog
timeout whether you want one or not. The DC_TX_INTR_ALWAYS causes
dc_encap() to request an interrupt for every frame.
I'm still waiting on confirmation from a couple of users to see if this
fixes their problems with the Davicom DM9102 before I merge this into
-stable, but this fixed the problem for me in my own testing so I'm
willing to make the change to -current right away.
|
| |
|
|
|
|
|
|
| |
expands beyond the limit we will extend the address space before trying
to zero the BSS. This should give us plenty of headroom for modest
expansion of the loader.
|
| |
|
| |
|
| |
|
|
|
|
| |
Submitted by: R Bradford Jones <brad@kazrak.com>
|
|
|
|
|
|
| |
zeroes for the time being).
Prompted by: Nathan Boeger <nathan@khmere.com>
|
|
|
|
| |
- Add in atomic operations for 8-bit, 16-bit, and 32-bit integers
|
|
|
|
| |
schedule a non-existant handler to run.
|
|
|
|
| |
Noticed by: phk
|
|
|
|
|
|
| |
- Add a missing curly brace.
Noticed by: phk
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Change the softintr() macro to do nothing on FreeBSD. Previously,
this macro would set a bit in spending and schedule the softinterrupt
thread to run. However, the bs driver never actually registers a
a software interrupt handler, so all this work achieved nothing. From
the code it is not clear what exactly the softintr() macro is actually
supposed to be doing. It looks like it is supposed to be possibly
running the hardware interrupt handler maybe? This handler is only
present in the #ifdef __NetBSD__ code however. I have no idea how this
driver handles interrupts at all, but at least it compiles now.
|
|
|
|
| |
Noticed by: phk
|
|
|
|
|
|
|
| |
time, so there is no need to make the distinction between
ip_output() and ip_input() cases.
Reviewed by: silence on freebsd-net
|
|
|
|
| |
and schedule it. This fixes booting machines with broken MP tables.
|
| |
|
| |
|