In message: [EMAIL PROTECTED]
Wesley Morgan [EMAIL PROTECTED] writes:
: And of course the answer to that is to create a /lib. Something that I
: would *never ever* want to see. Sure, a few people might throw around the
: idea of an extremely light-weight set of libraries to go into
On Fri, Nov 01, 2002 at 07:23:04AM +, Daniel Flickinger wrote:
from cvsup *default date=2002.11.01.06.00.00:
rm -rf /usr/obj/usr
make -j 4 -k -s buildworld ...
crashed in libc. v1.19 is in /usr/include; v1.20 is in
the /usr/obj/ tree where it should be read
--
Rebuilding the temporary build tree
--
stage 1: bootstrap tools
--
stage 2: cleaning up the object tree
Hi,
I've enabled sound using device pcm. Now at boot and each time I'm trying to
play a sound I got a lot of messages like:
pcm0: VIA VT82C686A port 0x1430-0x1433,0x1434-0x1437,0x1000-0x10ff irq 9 at de
vice 7.5 on pci0
../../../vm/uma_core.c:1311: could sleep with pcm0 locked from
On 2002-10-31 18:39, Conrad Sabatier [EMAIL PROTECTED] wrote:
I just upgraded a 4.7-STABLE box to current over the weekend. Went off
very well, thanks to the great documentation in UPDATING.
[...]
And finally, is there a simple way to ensure that none of the debugging
code (including
John Baldwin wrote:
Sectors more than 63 are not allowed for IDE drives at all.
What happens when you use the LBA geometry? Does the drive
not boot properly after being installed?
Well, I did try LBA as well, but couldn't boot at all. boot2 did
let me look at the root directory, but any
On 01-Nov-2002 stephan mantler wrote:
John Baldwin wrote:
Sectors more than 63 are not allowed for IDE drives at all.
What happens when you use the LBA geometry? Does the drive
not boot properly after being installed?
Well, I did try LBA as well, but couldn't boot at all. boot2 did
let
I'm getting panics on SMP -CURRENT while running apachebench (binary ab
from apache distribution, not the Perl one) against httpd on the machine.
The panics don't occur when I have WITNESS and INVARIANTS turned on.
I'm running apache server from ports with no special configuration. I'm
running
In message [EMAIL PROTECTED], Poul-Henning Kamp
writes:
phk 2002/11/01 07:32:12 PST
Modified files:
sys/fs/specfsspec_vnops.c
Log:
Put a KASSERT in specfs::strategy() to check that the incoming buffer
has a valid b_iocmd. Valid is any one of BIO_{READ,WRITE,DELETE}.
On Sun, 27 Oct 2002, Sean Kelly wrote:
On Sun, Oct 27, 2002 at 05:17:44PM -0500, Robert Watson wrote:
Are you using UFS1 extended attributes on that box?
Yes.
(290) smkelly@edgemaster:~$ grep UFS /usr/src/sys/i386/conf/EDGEMASTER
options UFS_DIRHASH
options UFS_EXTATTR
[...]
Anyone knows why / what to do ?
-- Aurélien
It does the same thing on my machine, but sound still works :)
I don't know how to fix it...I look forward to somebody hopefully
enlightening us :)
Bon FreeBSD,
Mike
Yep, sound still works but the box takes heavy loads
I installed two machines with fresh current snapshots last night
and this morning. One was an i386 box the other a sparc64 box.
Both machines are NIS clients from the same server. I do have
other 5.x and 4.x boxes on the same LAN at home that also are NIS
clients of the same server (the server
I updated to 5.0-current using the . tag because I wanted SMP
support for our development AlphaServer 1200 that was otherwise
gathering dust.
I added some new disks and wanted to do a sysinstall to label and
newfs them. So running /usr/sbin/sysinstall built from the sources of
today
In message [EMAIL PROTECTED], Michael Richards writes
:
--Boundary-00=_R7WWAEEZ5BZNTT4D7TH0
Content-Type: Text/Plain
Content-Transfer-Encoding: 7bit
I updated to 5.0-current using the . tag because I wanted SMP
support for our development AlphaServer 1200 that was otherwise
Ok, first make sure that your machine is running a -current
kernel.
FreeBSD 5.0-CURRENT #0: Thu Oct 31 01:54:22 EST 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/BOATANCHOR
Preloaded elf kernel /boot/kernel/kernel at 0xfc69a000.
AlphaServer 4100
AlphaServer 1200 5/533 4MB, 531MHz
8192
In message [EMAIL PROTECTED], Michael Richards writes
:
--Boundary-00=_GTXW0ZNZ5BZNTT4D7TH0
Content-Type: Text/Plain
Content-Transfer-Encoding: 7bit
Ok, first make sure that your machine is running a -current
kernel.
1st thing:
Make sure you have removed the NO_GEOM option
Per our discussion out-of-band, and just for the reference of others who
might have the same question, forced dependencies for rpcbind from ypserv
and ypbind aren't present right now, you can work around by explicitly
enabling rpcbind in rc.conf. You might actually see rpcbind running later
in
On Fri, Nov 01, 2002 at 07:23:04AM +, Daniel Flickinger wrote:
This is another instance where the build is not reading
from the /usr/obj tree, reading from /usr/include first.
I don't think so. You cannot do cross-builds if you're messing
up the include searches. I would suggest
Hi there.
I tried installing the 5.0-CURRENT-20021028-JPSNAP ISO today, on my 120G
harddrive, which is the second one on the system. Sysinstall failed to get
the right geometry of the disk, even though the BIOS was in LBA mode.
My 50G FreeBSD partition (ad1s3) as two partitions, 1000MB and a
On Fri, Nov 01, 2002 at 12:50:38PM -0800, Marcel Moolenaar wrote:
On Fri, Nov 01, 2002 at 07:23:04AM +, Daniel Flickinger wrote:
This is another instance where the build is not reading
from the /usr/obj tree, reading from /usr/include first.
I don't think so. You cannot do
Michal Mertl wrote:
I'm getting panics on SMP -CURRENT while running apachebench (binary ab
from apache distribution, not the Perl one) against httpd on the machine.
The panics don't occur when I have WITNESS and INVARIANTS turned on.
[ ... ]
#10 0xc01bd46f in panic (fmt=0x0) at
On Fri, Nov 01, 2002 at 12:59:33PM -0800, Steve Kargl wrote:
On Fri, Nov 01, 2002 at 12:50:38PM -0800, Marcel Moolenaar wrote:
On Fri, Nov 01, 2002 at 07:23:04AM +, Daniel Flickinger wrote:
This is another instance where the build is not reading
from the /usr/obj tree,
On Fri, Nov 01, 2002 at 08:56:44PM +, Hiten Pandya wrote the words in effect of:
Hi there.
I tried installing the 5.0-CURRENT-20021028-JPSNAP ISO today, on my 120G
harddrive, which is the second one on the system. Sysinstall failed to get
the right geometry of the disk, even though
On Thu, Oct 31, 2002 at 06:39:00PM -0600, Conrad Sabatier wrote:
I just upgraded a 4.7-STABLE box to current over the weekend. Went off
very well, thanks to the great documentation in UPDATING.
It's odd, though, that after upgrading again just a few days later,
suddenly X (or perhaps just
SO ok, we need a good marketting name for 5.0..
Off the top of my head FreeBSD 5.0 banana :-)
slug, monkey, heffalump, peach, blender... :-)
blackjack (It's a gamble)
tahoe, reno amd vegas are gone, but silver city is up for grabs :-)
p.s. while the names suggested are humourous I am very
sonewconn() hands sofree() a self-inconsistent socket -- so-so_head is
set, so so must be on a queue, but sonewconn() hasn't put it on a queue yet.
Please try this patch.
Bill
Index: uipc_socket2.c
===
RCS file:
This is fixed in my WIP on rc.d . I'm more or less ready for wider
review; I especially need review of the atm and diskless changes.
Bill
http://people.freebsd.org/~fenner/rc.d.diff
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Rebuilding the temporary build tree
--
stage 1: bootstrap tools
--
stage 2: cleaning up the object tree
BTW, /etc/rc.network never tried to save you from
rpcbind_enable=NO
nis_client_enable=YES
so it may be a mistake for /etc/rc.d/* to try to.
Bill
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Fri, Nov 01, 2002 at 04:23:02PM -0800, Bill Fenner wrote:
BTW, /etc/rc.network never tried to save you from
rpcbind_enable=NO
nis_client_enable=YES
so it may be a mistake for /etc/rc.d/* to try to.
/etc/rc does though:
chkdepend amd amd_enablerpcbind rpcbind_enable
chkdepend
Oops, you're right, I was looking too closely =)
Bill
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Bill Fenner wrote:
sonewconn() hands sofree() a self-inconsistent socket -- so-so_head is
set, so so must be on a queue, but sonewconn() hasn't put it on a queue yet.
Please try this patch.
I think this can still crash (just like my patch); the problem is in
what happens when it fails to
I think this can still crash (just like my patch); the problem is in
what happens when it fails to allocate memory. Unless you set one of
the flags, it's still going to panic in the same place, I think, when
you run out of memory.
No. The flags are only checked when so_head is not NULL.
For all you weekend install warriors out there...
There is a new 5.0 snap iso available via
anonymous ftp at:
usw2.FreeBSD.Org
/pub/FreeBSD/snapshots/i386/5.0-20021101-CURRENT
and the iso:
/pub/FreeBSD/snapshots/i386/5.0-20021101-CURRENT.iso
I have verified that this iso boots and can
Bill Fenner wrote:
I think this can still crash (just like my patch); the problem is in
what happens when it fails to allocate memory. Unless you set one of
the flags, it's still going to panic in the same place, I think, when
you run out of memory.
No. The flags are only checked when
Hiten Pandya wrote:
Hi there.
I tried installing the 5.0-CURRENT-20021028-JPSNAP ISO today, on my 120G
harddrive, which is the second one on the system. Sysinstall failed to get
the right geometry of the disk, even though the BIOS was in LBA mode.
My 50G FreeBSD partition (ad1s3) as two
1st thing:
Make sure you have removed the NO_GEOM option from your
kernel config, sysinstall/libdisk only works with GEOM
kernels.
This was the problem. I think sysinstall should have a graceful way
to detect this and return a complaint to the user rather than return
a
OK, I've installed 20021102-JPSNAP to fresh 80GB disk on my P-III x 2
box from floppy and ftp and finishes fine.
But I cannot boot it.
I used BootMgr in sysinstall. When I booted after install, it
stopped at:
-
F1 FreeBSD
Default: F1
-
At this, pushing [F1] or [Enter] causes
I'm getting the following panic on one of the bento cluster machines.
The machine has a single drive:
ad0: 29314MB IBM-DTLA-307030 [59560/16/63] at ata0-master UDMA66
and I have it set up to zero the disk at boot-time (the machine boots
diskless via NFS):
dd if=/dev/zero of=/dev/ad0 bs=64k
At Sat, 2 Nov 2002 02:03:48 + (UTC),
kuriyama wrote:
I used BootMgr in sysinstall. When I booted after install, it
stopped at:
-
F1 FreeBSD
Default: F1
-
Oops, I set LBA in BIOS explicitly, it booted fine.
Hmm, it's my bad to believe BISO Auto setting...
--
Jun
On 01-Nov-2002 Conrad Sabatier wrote:
I just upgraded a 4.7-STABLE box to current over the weekend. Went off
very well, thanks to the great documentation in UPDATING.
It's odd, though, that after upgrading again just a few days later,
suddenly X (or perhaps just xdm) failed to start due to
I recently came across a dual MP 2000 and installed a snapshot of
10/29, then did a few buildworlds to check out the speed. I then
upgraded to -current as of day and various times of today and started
getting this. Does anyone have any clues. It usually happens during
periods of high cpu
2050949120 bytes transferred in 198.151980 secs (10350384 bytes/sec)
ad0: WRITE command timeout tag=0 serv=0 - resetting
ata0: resetting devices ..
ad0: removed from configuration
While I don't remember if my panic was the same, the above message is
what I have been seeing recently as well
Now that uucp is no longer in the base system, is there any reason to
keep user uucp in /usr/src/etc/master.passwd?
Greg
--
See complete headers for address and phone numbers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On 01-Nov-2002 Kris Kennaway wrote:
On Thu, Oct 31, 2002 at 06:39:00PM -0600, Conrad Sabatier wrote:
I just upgraded a 4.7-STABLE box to current over the weekend. Went off
very well, thanks to the great documentation in UPDATING.
It's odd, though, that after upgrading again just a few days
On 01-Nov-2002 Giorgos Keramidas wrote:
On 2002-10-31 18:39, Conrad Sabatier [EMAIL PROTECTED] wrote:
[...]
And finally, is there a simple way to ensure that none of the debugging
code (including INVARIANTS stuff) is included during a buildworld?
INVARIANTS and WITNESS are kernel-only
46 matches
Mail list logo
