| Age | Commit message (Collapse) | Author |
|---|
|
|
|
The return value from the interrupt handling was bogus. Now we return 1
if we have handled the interrupt.
When resuming from suspend wrong values were restored to the mixer
which sometimes caused a high-pitched sound to be emitted. (how fast
can you type "mixerctl -w outputs.master.mute=on"?)
|
|
|
|
Previously it was possible to remove multiple entries on a single pass thru
the pv deletion code in pmap_page_protect. Also when it did this, it
was not properly tracking of decrementing pm->pm_stats.resident_count.
By storing an additional piece of information in the pv structure,
the pmap pointer it is possible to call pmap_remove on the
entries rather than duplicating the pte removal code (again).
This fixes a problem seen where the system panics or hangs in
pmap_remove_pv due to the item not being on the list. Now
it is not possible for mix entries.
Because the pv entry only contained the pteidx, it was possible
to remove an incorrect entry due to ambiguity. multiple pmaps
having mappings at the same va of the same pa. Multipe pmap containing similar
entries will occur frequenty with shared libaries. Because of the hash
entries that have the same result of (sr & ptab_mask) will alias in the pv
list..
Since the pv_idx is now recomputable, should it be removed?
|
|
if you reconfigure inet6 too much, the reference count can go
into negative by mistake. KAME in6.c 1.98 -> 1.99.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
on diff from "Pete Kazmier" <pete@kazmier.com>
|
|
|
|
|
|
|
|
|
|
not sure if there is a real threat or not, but it seems that there's
possibility for overrun/underrun (like non-NOP option with optlen > cnt).
|
|
|
|
|
|
|
|
|
|
retrieved, do not walk the (uninitialized?) stack until a value is found.
|
|
|
|
calculation. Now it's better.
|
|
Match Promise Ultra/100 controller
(Ultra/100 drives will be used as Ultra/66 fow now)
Work-around for a bug in revision D2 AMD controllers
(They do not work correctly with Multiword-DMA mode, workaround is to
disable MW DMA, but this bug does not affect all drives so there is an
option PCIIDE_AMD756_ENABLEDMA to stop this behavior. You know you have
this bug when your system hangs completely with this option.)
|
|
|
|
|
|
|
|
|
|
|
|
Add a new flag to fork1 - FORK_VMNOSTACK that shares all of the vmspace
except the stack and use it for rfork.
|
|
|
|
|
|
poll had the same timeout problem as select.
|
|
the mac esp driver was not yet ported, when that is done, this will
be readded appropriately.
|
|
Use the interrupt line as configured by pci, now that
the bridge will walk the openfirmware device tree and properly
initialize that field.
|
|
use the same code for read and write for easier maintance.
code to walk the openfirmware device tree when a bridge is configured
to copy the interrupt line information into the pci register so
that the device driver can use it. Apple Openfirmware doesn't do
this automatically.
|
|
the timeout.
|
|
in the config cycle, and pci devices as well as mac onboard devices
do not use interrupts to probe. It is possible to record that the
interrupt is to be configured, but not configure it with the interrupt
controller until the interrupt controller configures itself.
This is lazy binding of interrupts. If there is a conflicting interrupt
or other problem it will be noticed when the interrupt controller configures
and collects the data rather than when the device configures.
Currently on the openpic interrupt controller supports these pre-configured
interrupts.
|
|
due to busdma issues on powerpc.
|
|
Return 1 from zshard more often to reduce (not fix) the stray interrupt
problem.
|
|
|
|
|
|
Add these syscalls to linux_dummy.c where they return ENOSYS and display
a friendler message which tells you what unimplemented syscall has been
called.
|
|
Noticed by: Chris Cappuccio <chris@dqc.org>
|
|
|
|
from dugsong@
|
|
its brains in order.
|
|
|
