| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
have per-CPU data and gdb on the i386 at least needs access to it.
- Clean up includes in kern_idle.c and subr_smp.c.
Reviewed by: jake
|
|
|
|
|
|
|
| |
a LinkSys card here in the office where reading the station address
fails the first time, but works find afterwards. Without this, the
probe fails. I don't think this will negatively impact any existing
cards, but I want to confirm this before MFC'ing.
|
|
|
|
|
|
|
| |
safe from preemption and concurrent access to the LDT.
- Move the prototype for i386_extend_pcb() to <machine/pcb_ext.h>.
Reviewed by: silence on -hackers
|
|
|
|
|
| |
*that* whilst we ponder the best way to decide how to register dwlpx interrupts
with TLSB.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
we need to delete the info from the list as well as zero out the res
pointer we saved in the code.
Also made a few style(9) changes while I was at it. Don't use if
(ptr) or if (!ptr), but compare against NULL. Compare against NULL
rather than 0. Don't have useless blocks.
There are likely other problems as well, but at least the wi based
wireless card with memory listed in its cis doesn't panic the system
when the card is inserted.
|
| |
|
|
|
|
| |
without an i8254 timer/counter. This really needs to be cleaned up.
|
|
|
|
| |
Spotted by: Peter Jeremy <peter.jeremy@alcatel.com.au>
|
|
|
|
| |
include.
|
|
|
|
|
|
|
| |
documented. They cannot be turned on by default due to conflicting
symbols at link time between OLDCARD and NEWCARD.
Approved by: imp
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
use TAILQ macros. The sk_attach_xmac() routine calls sk_init_xmac()
before doing the transceiver probe, but *before* ether_ifattach()
is called. This causes sk_init_xmac() to call sk_setmulti(), which
tries to do a TAILQ_FOREACH(), which it can't do because ether_ifattach()
hasn't done a TAILQ_INIT() yet. This causes a NULL pointer dereference
and panic in sk_setmulti() at driver load/initialization time.
Fixed by calling ether_ifattach() before the MII probe.
The code in RELENG_4 still uses the old way of enumerating the
multicast list and doesn't have this problem. Yet.
|
| |
|
| |
|
|
|
|
|
|
|
| |
PR 27213.
BTW the CDIOCREADAUDIO ioctl is deprecated, its not longer needed
and was an ugly hack from start on.
|
|
|
|
|
| |
PR: 27215
Submitted by: Jim Pirzyk <Jim.Pirzyk@disney.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Reduce the verbose memory map setup reports and work with pccardd to
set the common memory map up.
Use enumeration values for CARD_SET_RES_FLAGS.
Use DELAY when spinning waiting for the card to come free instead of a loop.
MFC: after 1 week
|
|
|
|
|
|
|
| |
Remove panic on out of range io window and return ENXIO. Add a similar
check for memory windows.
Approved by: imp
|
|
|
|
| |
Approved by: imp
|
|
|
|
|
| |
Approved by: imp
MFC: after 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
machdep.pccard.pcic_mem_start
machdep.pccard.pcic_mem_end
and default the range to IOM_BEGIN/IOM_END.
This may prove useful to if_ray users (and others) on more modern
hardware that maps BIOS stuff into 0xd000-0xdffff.
MFC: after 1 week
Approved by: imp
|
|
|
|
|
|
| |
- Finish transmitting data to mpu when a buffer gets empty.
Submitted by: KUROSAWA Takahiro <fwkg7679@mb.infoweb.ne.jp>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The pipe code could not handle running out of kva, it would panic
if that happened. Instead return ENFILE to the application which
is an acceptable error return from pipe(2).
There was some slightly tricky things that needed to be worked on,
namely that the pipe code can 'realloc' the size of the buffer if
it detects that the pipe could use a bit more room. However if it
failed the reallocation it could not cope and would panic. Fix
this by attempting to grow the pipe while holding onto our old
resources. If all goes well free the old resources and use the
new ones, otherwise continue to use the smaller buffer already
allocated.
While I'm here add a few blank lines for style(9) and remove
'register'.
|
|
|
|
|
|
|
|
| |
handling a bit.
Dogmatic lingupurists can celebrate that a number of gotos got removed.
Reviewed by: mjacob, ken
|
|
|
|
| |
that the drivers don't have to do it umpteen times.
|
|
|
|
|
|
| |
Tidy up includes, credit Slawa Olhovchenkov, John Prince and Eric Hernes
for their efforts and add a couple of missing parenthesis around return
expressions.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that are committed to being freed and reflect these blocks in the
counts returned by statfs (and thus also by the `df' command). This
change allows programs such as those that do news expiration to
know when to stop if they are trying to create a certain percentage
of free space. Note that this change does not solve the much harder
problem of making this to-be-freed space available to applications
that want it (thus on a nearly full filesystem, you may still
encounter out-of-space conditions even though the free space will
show up eventually). Hopefully this harder problem will be the
subject of a future enhancement.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Do not assume that the superblock will be of size fs->fs_bsize.
This fixes a panic when taking a snapshot on a filesystem with
a block size bigger than 8K.
2) Properly calculate the number of fragments that follow the
superblock summary information. This fixes a bug with inconsistent
snapshots.
3) When cleaning up a snapshot that is about to be removed, properly
calculate the number of blocks that need to be checked. This fixes
a bug that created partially allocated inodes.
4) When moving blocks from a snapshot that is about to be removed
to another snapshot, properly account for the reduced number of
blocks in the snapshot from which they are taken. This fixes a
bug in which the number of blocks released from a snapshot did not
match the number that it claimed to have.
|
|
|
|
|
| |
buffer locking so as to avoid locking against ourselves if we need to
write filesystem metadata.
|
|
|
|
|
|
| |
RL5C47x cards do not. Only set them for that set of bridges.
Submitted by: shiba (Takeshi Shibagaki-san)
|
| |
|
|
|
|
| |
Re-spotted by: phk
|
|
|
|
|
|
|
|
| |
chip to the one that the Japanese use. Now we get insert/remove
events on my PC-9821Ne. More work in bus space is needed to make
drivers work.
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
- Rework of twe_report_request to use the command status value rather
than the flags register. (Joel Jacobson @ 3ware)
- Update to match some changes in -current vs. stable.
MFC in: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
process on fork(2).
It is the supposed behavior stated in the manpage of sigaction(2), and
Solaris, NetBSD and FreeBSD 3-STABLE correctly do so.
The previous fix against libc_r/uthread/uthread_fork.c fixed the
problem only for the programs linked with libc_r, so back it out and
fix fork(2) itself to help those not linked with libc_r as well.
PR: kern/26705
Submitted by: KUROSAWA Takahiro <fwkg7679@mb.infoweb.ne.jp>
Tested by: knu, GOTOU Yuuzou <gotoyuzo@notwork.org>,
and some other people
Not objected by: hackers
MFC in: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
layer. This fixes an ordering problem that would cause the ISR for
the device to run with now power applied to the device. Most cards
failed to deal with this gracefully, and thus would hang on card
eject.
The power down event, for those keeping score, is what causes the
interrupt for the card.
Many folks in the Japanese nomads list have reported this, so I'll be
MFCing quickly for their benefit.
Submitted by: Masayuki FUKUI
MFC after: 2 days
|
|
|
|
|
| |
Setup attribute memory resource in ray_probe so that it is added to
the print out of the resource list on card insertion.
|
|
|
|
| |
SMP being defined.
|
|
|
|
| |
instead of the underlying drivers.
|
|
|
|
| |
Spotted by: phk
|
|
|
|
|
|
| |
than the bioerror().
Most of this patch is generated by scripts.
|
| |
|
|
|
|
| |
Noticed by: rwatson
|
|
|
|
| |
Noticed by: rwatson
|
|
|
|
|
|
|
| |
XXX: the real bug is that devstat isn't part of the disk minilayer.
PR: 27158
Submitted by: Anders Nordby <anders@fix.no>
|