peter [Thu, 13 Feb 2003 02:42:06 +0000 (02:42 +0000)]
Oops. I mis-remembered about the P4 problems. It was 5.0-DP2 that
was shipped with DISABLE_PG_G and DISABLE_PSE, not 5.0-REL. *blush*
Disable the code - but still leave it there in case its still lurking.
peter [Thu, 13 Feb 2003 01:00:26 +0000 (01:00 +0000)]
Show the paritition types that we recognize in human readable format. eg:
pluto2# gpt show da0
start end size contents
0 0 1 PMBR
1 1 1 Pri GPT header
2 33 32 Pri GPT table
34 401595 401562 GPT part - EFI System partition
401596 925883 524288 GPT part - FreeBSD ufs partition
925884 93144918388608 GPT part - FreeBSD swap partition
...
It'll print a plain uuid string for unrecognized types.
des [Wed, 12 Feb 2003 21:06:19 +0000 (21:06 +0000)]
Simplify the log accumulation code. It turns out that the trick of
looking for ^===> can give quite annoying false positives, especially
when building kernels, so drop it; the context can be inferred from
make's "Stop in /foo/bar/baz" messages anyway.
Also add a case that I'd missed the first time around (which happens
to be the common case, not the exception...)
mike [Wed, 12 Feb 2003 20:03:41 +0000 (20:03 +0000)]
o Implement C99 classification macros isfinite(), isinf(), isnan(),
isnormal(). The current isinf() and isnan() are perserved for
binary compatibility with 5.0, but new programs will use the macros.
o Implement C99 comparison macros isgreater(), isgreaterequal(),
isless(), islessequal(), islessgreater(), isunordered().
Submitted by: David Schultz <dschultz@uclink.Berkeley.EDU>
peter [Wed, 12 Feb 2003 19:34:34 +0000 (19:34 +0000)]
Do not do an assignment in a truth test (previous commit) or gcc gives a
warning which breaks builds.
cc1: warnings being treated as errors
src/sys/net/bridge.c: In function `bdg_forward':
sys/net/bridge.c:931: warning: suggest parentheses around assignment used as truth value
*** Error code 1
phk [Wed, 12 Feb 2003 09:48:27 +0000 (09:48 +0000)]
Implement a handle for efficient implementation of perforations in
lower extremities.
Setting bit 4 in debugflags (sysctl kern.geom.debugflags=16) will
allow any open to succeed on rank#1 providers. This will generally
correspond to the physical disk devices: ad0, da0, md0 etc.
This fundamentally violates the mechanics of GEOMs autoconfiguration,
and is only provided as a debugging facility, so obviously error
reports on GEOM where this bit is or has been set will not be
accepted.
imp [Wed, 12 Feb 2003 06:11:47 +0000 (06:11 +0000)]
MF-p4:
Kill the slightly bogus #define for DECODE_PROTOTYPE
Be less verbose. Hide most (all I hope) of the CIS
parsing behind cardbus_debug_cis (which is set with
hw.cardbus.debug_cis=1).
This doesn't fix problems with parsing, but should make cardbus
less chatty. There appears to be some issues still with the
parsing of the CIS, but this won't fix them.
imp [Wed, 12 Feb 2003 05:57:02 +0000 (05:57 +0000)]
MFp4:
Second part of the kldload patches for cardbus. This makes
kldload of a driver for a device that's inserted now appears
to work. To make it work, we only do a power cycle of the card
if there's no children drivers attached.
This likely is papering over bogosities in the power system. The
power sequence needs to be re-written, so I'll not worry about
the papering over until the re-write.
imp [Wed, 12 Feb 2003 04:26:10 +0000 (04:26 +0000)]
Back out 1.143 and 1.144. They are no longer needed now that we start
devd later in the boot process. This should fix all the problems
people have had with those commits. Diskless should be working again,
and those that mount /usr with nfs should be able to do that again too.
imp [Wed, 12 Feb 2003 04:22:40 +0000 (04:22 +0000)]
Start devd after the networking stuff, but before we mount the
critical remote systems. This lets us run commands from devd that
aren't on the / partition. This also means we can remove some kludges
from the networking startup that I added a while ago that caused other
problems.
There's still a race in starting devd that needs to be fixed in devd
so that things present at boot will be configured by the time devd
does daemon(). That race will be fixed later.
imp [Wed, 12 Feb 2003 04:12:23 +0000 (04:12 +0000)]
Now that we don't have the NODEVFS case, we can just check to see if a
device node exists directly to see if OLDCARD is compiled into the
kernel. This eliminates the scary warning that people using NEWCARD
are seeing when they have pccard_enable=YES in their /etc/rc.conf
files.
phk [Tue, 11 Feb 2003 22:30:26 +0000 (22:30 +0000)]
Implement a bio-taskqueue to reduce number of context switches in
disk I/O processing.
The intent is that the disk driver in its hardware interrupt
routine will simply schedule the bio on the task queue with
a routine to finish off whatever needs done.
The g_up thread will then schedule this routine, the likely
outcome of which is a biodone() which queues the bio on
g_up's regular queue where it will be picked up and processed.
Compared to the using the regular taskqueue, this saves one
contextswitch.
Change our scheduling of the g_up and g_down queues to be water-tight,
at the cost of breaking the userland regression test-shims.
imp [Tue, 11 Feb 2003 17:36:38 +0000 (17:36 +0000)]
Commit a nearly real man page describing the current state of devctl.
More work likely needs to happen. This describes things better than
the old "this man page intentionally left blank" style man page that
I'd committed previously.
phk [Tue, 11 Feb 2003 11:01:26 +0000 (11:01 +0000)]
Turn the "updating" flag (back) into two sequence number fields at
either ends of the structure so we have a way to determine if a
snapshot is consistent.
alfred [Tue, 11 Feb 2003 07:20:52 +0000 (07:20 +0000)]
Don't lock FILEDESC under PROC.
The locking here needs to be revisited, but this ought to get rid of the
LOR messages that people are complaining about for now. I imagine either
I or someone else interested with smp will eventually clear this up.
imp [Tue, 11 Feb 2003 05:31:35 +0000 (05:31 +0000)]
Don't turn off the power of cards when new drivers are added
unconditionally. kldloading a cardbus driver was shooting down other
attached devices because most drivers assume that one cannot
power-cycle cards w/o the driver knowning about it.
jmallett [Tue, 11 Feb 2003 03:06:45 +0000 (03:06 +0000)]
Convert newfs to libufs (really). Solves one real issue with previous
version of such. Differences in filesystems generated were found to be
from 1) sbwrite with the "all" parameter 2) removal of writecache. The
sbwrite call was made to perform as the original version, and otherwise
this was checked against a version of newfs with the write cache removed.