TB --- 2003-11-15 06:02:11 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-15 06:02:11 - starting CURRENT tinderbox run for amd64/amd64
TB --- 2003-11-15 06:02:11 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64
TB --- /usr/bin/cvs -f -R -q
On Sat, Nov 15, 2003 at 04:52:14PM +1000, Andy Farkas wrote:
The dc(4) driver is still reporting collisions on 100 Mbit full-duplex
links:
[snip]
netstat -i
NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll
dc01500 Link#1 00:00:e8:89:b9:6626463
Jos Backus wrote:
Fwiw, I'm seeing the same with tx(4):
Looks like a different problem.
lizzy:~% ifconfig tx0
tx0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 10.0.0.2 netmask 0xff00 broadcast 10.0.0.255
inet 10.0.0.10 netmask 0x broadcast
Andy Farkas replies to himself:
The dc(4) driver currently has an almost 1:1 ratio of packets:collisions.
Your tx0 is quite low.
Ack! I can't count. Or my numerical recognition system is failing
NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll
dc01500
TB --- 2003-11-15 06:57:46 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-15 06:57:46 - starting CURRENT tinderbox run for i386/i386
TB --- 2003-11-15 06:57:46 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/i386
TB --- /usr/bin/cvs -f -R -q
FWIW: I don't know exactly why/what is happening, but
I've seen it once. In my case, the process (script
foo.log make install clean exit) failed abruptly
and the process entry was not correctly cleared. You
see that your second process with pid 0 (xbattbar) is
a zombie (Z), swapped out (W). I
In message [EMAIL PROTECTED], Josef Karthauser writes:
What's the best way to prepare for this? Should I leave some
unallocated space at the beginning of the disk so that any magic geom
bits can be inserted later?
Rather: leave a bit free at the end.
--
Poul-Henning Kamp | UNIX since
TB --- 2003-11-15 07:52:03 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-15 07:52:03 - starting CURRENT tinderbox run for i386/pc98
TB --- 2003-11-15 07:52:03 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/pc98
TB --- /usr/bin/cvs -f -R -q
It seems Andy Farkas wrote:
When messages are sent to console rapidly, console becomes unavailable :(
That is an oold problem, at least its been do for months...
My previous email complains of messages being spewed to the console. These
messages stop after a few minutes and the console is
TB --- 2003-11-15 08:50:05 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-15 08:50:05 - starting CURRENT tinderbox run for ia64/ia64
TB --- 2003-11-15 08:50:05 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64
TB --- /usr/bin/cvs -f -R -q
Hi,
On Sun, 02 Nov 2003 15:49:35 +0200
Kostyuk Oleg [EMAIL PROTECTED] said:
cubProblem is in order of starting /etc/rc.d/ipsec.
cubIt must start BEFORE any network interaction,
cubmay be even before configuring interfaces.
cubBut I not sure in case with diskless mashines.
cub
Selon long [EMAIL PROTECTED]:
reboot
make world
single user mode, make installworld
reboot
and it's up and running... no more sig12 or anything like that...
Yes, but no !
I don't have any sig12 error...
I have: /libexec/ld-elf.so.1: Shared object libedit.so.4 not found
And I can't even
TB --- 2003-11-15 10:30:12 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-15 10:30:12 - starting CURRENT tinderbox run for sparc64/sparc64
TB --- 2003-11-15 10:30:12 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64
TB --- /usr/bin/cvs -f -R -q
On Fri, 14 Nov 2003 22:51:27 +
Josef Karthauser [EMAIL PROTECTED] wrote:
I've been a bit out of touch with developments recently. I was
wondering whether it's possible to mirror root partitions across two
drives yet? I seem to remember that this was something that geom could
help with,
Richard Coleman wrote:
Andy Farkas wrote:
Richard Coleman wrote:
1. make buildworld
2. make buildkernel KERNCONF=NAME_OF_KERNEL_FILE
3. make installkernel KERNCONF=NAME_OF_KERNEL_FILE
4. shutdown -r now
5. boot into single user mode
6. fsck -p
7. mount -u /
8. mount -a -t ufs
9. swapon -a
Adding a rule to devfs on current seems broken or at least not in touch with
the man page.
# devfs rule add path acpi mode 660
devfs rule: ioctl DEVFSIO_RADD: Input/output error
Sven Esbjerg
--
http://www.usenet.dk/netikette - på forhånd tak.
___
Mathew Kanner has developed the new version of the midi framework,
based on kobj(9) and buildable as a module. As the first step to
replace the midi driver, the conventional one is removed from the
kernel in a minute.
Mathew will soon be starting a work to merge his driver.
--
Seigo Tanimura
On Sat, Nov 15, 2003 at 10:42:44PM +0900, Seigo Tanimura wrote:
Mathew Kanner has developed the new version of the midi framework,
based on kobj(9) and buildable as a module. As the first step to
replace the midi driver, the conventional one is removed from the
kernel in a minute.
Mathew
On Sat, 15 Nov 2003, Andy Farkas wrote:
These messages spew onto my console and into syslogd once every second:
Heh. Sounds like your box is having a really bad day, we'll see if we
can't get it fixed up over the next couple of weeks as things settle out
:-).
I think John has this one in his
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2
anyone else seeing this:
checking stopevent 2 with the following non-sleepable locks held:
exclusive sleep mutex sigacts r = 0 (0xc6b51aa8) locked @ kern/subr_trap.c:260
checking stopevent 2 with the following non-sleepable locks held:
exclusive sleep mutex sigacts r = 0 (0xc6b51aa8) locked @
Selon Dylan Wylie [EMAIL PROTECTED]:
The idea is that you need to build a new kernel with the new sources before
you install
world.
You built your kernel before building the sources, so your kernel is based on
old source.
Quoting from another message:
make buildworld
make buildkernel
On Sat, Nov 15, 2003 at 09:38:37AM -0500, Robert Watson wrote:
On Sat, 15 Nov 2003, Andy Farkas wrote:
would probably be useful if you could drop to DDB and generate a trace for
the event.
I've done that, in this email message:
Lör 2003-11-15 klockan 16.30 skrev Antoine Jacoutot:
Selon Dylan Wylie [EMAIL PROTECTED]:
The idea is that you need to build a new kernel with the new sources
before you install
world.
You built your kernel before building the sources, so your kernel is based
on old source.
masta [EMAIL PROTECTED] writes:
I found that if I put /rescue in my PATH before all the normal stuff,
things tend to work (like ls). For me I got caught doing the:
make buildworld
make buildkernel KERNCONF=FOO
make installkernel
mergemaster
make installworld
BAM! installworld fails, and
Hi.
I'm getting a bit desperate here. I recently moved our
web-servers from Linux, php4 4.1 and apache 1.3.20 to
FreeBSD 5.1 (mostly frozen branch), php 4.3.4 and
apache 1.3.29.
My problem is that the web-servers keep rebooting for
no apperant reason. They are up for about 20-24 hours
and then
Selon Aron Håkanson [EMAIL PROTECTED]:
If you are looking for a fast and temporary solution, just to finish the
installworld process, you can export the following value to the
LD_LIBRARY_PATH variable: $LD_LIBRARY_PATH:/lib:/usr/lib
Hey :)
Thanks a lot... I'll try that.
Antoine
On Sat, Nov 15, 2003 at 09:38:37AM -0500, Robert Watson wrote:
On Sat, 15 Nov 2003, Andy Farkas wrote:
These messages spew onto my console and into syslogd once every second:
I'm seeing the same on a recently upgraded dual cpu machine.
Also when I run the reboot command the errors get mixed
Date: Sat, 15 Nov 2003 09:51:40 +1000 (EST)
From: Andy Farkas [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Richard Coleman wrote:
0. mergemaster -p
1. make buildworld
2. make buildkernel KERNCONF=NAME_OF_KERNEL_FILE
3. make installkernel KERNCONF=NAME_OF_KERNEL_FILE
2 and 3 may be
TB --- 2003-11-15 17:00:01 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-15 17:00:01 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2003-11-15 17:00:01 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha
TB --- /usr/bin/cvs -f -R -q
Hi,
this panic just happened on an i386 SMP box that was idle except for
generating tons of checking stopevent 2 with the following
non-sleepable locks held messages. Its sources are are just a few
hours old.
%%
checking stopevent 2 with the following non-sleepable locks held:
This looks slightly different if I use SCHED_ULE, but the effect is
the same.
Off the top of my head, I have not been able to find any places
where softclock would call schedcpu directly.
Suspect locking foobar.
Suggest more people us DIAGNOSTIC
Poul-Henning
ata2-slave: FAILURE -
On Fri, Nov 14, 2003 at 05:32:31PM -0800, Alfred Perlstein wrote:
The Citi project over at the University of Michegan has been nice
enough to provide us with an initial implementation of a NFSv4
client. We still need locking, delegations and cypto.
If anyone who's crypto friendly wants to
Yes I tried.
Still No reboot
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag
von Lowell Gilbert
Gesendet: Samstag, 15. November 2003 18:49
An: Hutterer Robert
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Betreff: Re: AW: 5.1. does not boot afte
In the last episode (Nov 15), Andy Farkas said:
The dc(4) driver is still reporting collisions on 100 Mbit full-duplex
links:
ifconfig -a
dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 172.22.2.12 netmask 0xfff0 broadcast 172.22.2.15
ether
Hello All,
I'm sorry to be a pain, but I think it's important this PR be
commited before any branch.
http://www.freebsd.org/cgi/query-pr.cgi?pr=59233
It's vital to build current midi software and it has been in
other OSes for a while.
Thanks,
--Mat
Hello.
If I boot my box with a cd disc already inserted, it mounts ok. But if
I eject the tray on a booted system, insert a disc and then try to mount it,
there occurs a system panic.
% uname -a
FreeBSD becho.home 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Mon Nov 10
20:39:27 NOVT 2003 [EMAIL
Andrzej Tobola wrote:
Just cvsuped.
kldload nfsclient is now not working:
link_elf: symbol nfs4_writebp undefined
Did you tested it with nfsclient dynamically loaded ?
Same here. Is there a way to fall back to the old code?
Lars
--
Lars Eggert [EMAIL PROTECTED] USC Information
Damn, I've forgotten to include `dmesg` output. Attached.
--
be9
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.1-CURRENT #0: Mon Nov 10
On Sat, 15 Nov 2003, Sven Esbjerg wrote:
On Sat, Nov 15, 2003 at 09:38:37AM -0500, Robert Watson wrote:
On Sat, 15 Nov 2003, Andy Farkas wrote:
These messages spew onto my console and into syslogd once every second:
I'm seeing the same on a recently upgraded dual cpu machine.
Also
This morning's cvsup.
checking stopevent 2 with the following non-sleepable locks held:
exclusive sleep mutex sigacts r = 0 (0xc6b8baa8) locked @
/space1s1/freebsd/FreeBSD/branches/-current/src/sys/kern/subr_trap.c:260
Eric
___
[EMAIL PROTECTED]
Hi,
shouldn't this work?
# ifconfig em0 inet 128.9.168.58 netmask 255.255.240.0 \
ether 00:07:e9:0a:26:52
ifconfig: ether: bad value
This is with today's -current, but this may have been around longer - I
hadn't tried it before today. Using two commands to set MAC and IP
addresses
On 15 Nov, Robert Watson wrote:
On Sat, 15 Nov 2003, Andy Farkas wrote:
These messages spew onto my console and into syslogd once every second:
Heh. Sounds like your box is having a really bad day, we'll see if we
can't get it fixed up over the next couple of weeks as things settle out
In message: [EMAIL PROTECTED]
Andrzej Tobola [EMAIL PROTECTED] writes:
: Did you tested it with nfsclient dynamically loaded ?
I can't load nfs4client.ko either. If you put all the files/paths in
nfsclient, it will load and work.
I load nfsclient.ko in my boot loader, so I couldn't
In message: [EMAIL PROTECTED]
Don Lewis [EMAIL PROTECTED] writes:
: I hope the fix isn't too extensive, since I'll probably be typing it in
: by hand in single user mode ...
You could do what I did: remove the two lines that jhb added. You'll
get no more warnings. Sure, the problems
On Sat, Nov 15, 2003 at 11:54:20AM -0800, Lars Eggert wrote:
shouldn't this work?
# ifconfig em0 inet 128.9.168.58 netmask 255.255.240.0 \
ether 00:07:e9:0a:26:52
ifconfig: ether: bad value
This is with today's -current, but this may have been around longer - I
hadn't tried it
On Sat, 15 Nov 2003, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Don Lewis [EMAIL PROTECTED] writes:
: I hope the fix isn't too extensive, since I'll probably be typing it in
: by hand in single user mode ...
You could do what I did: remove the two lines that jhb
Bruce M Simpson wrote:
On Sat, Nov 15, 2003 at 11:54:20AM -0800, Lars Eggert wrote:
shouldn't this work?
# ifconfig em0 inet 128.9.168.58 netmask 255.255.240.0 \
ether 00:07:e9:0a:26:52
ifconfig: ether: bad value
This is with today's -current, but this may have been around longer - I
Hello,
I looking to extend the smartmontools support
(/usr/ports/sysutils/smartmontools) to include support for drives behind
a TWE device.
I looked at the source for the TWE driver, and it seems to support what
I neednot sure yet, as the linux version use the ATA Passthru
IOCTL. At any
The default value of this driver is to use C1 (HLT), which is equivalent
to previous behavior. To use lower idle states, set hw.acpi.cpu.cx_lowest
to the index of the desired state. See sysctl hw.acpi.cpu output to get
an idea of the values. Here is the result on my IBM T23:
On Fri, Nov 14, 2003 at 11:14:36PM -0800, Jos Backus wrote:
On Sat, Nov 15, 2003 at 04:52:14PM +1000, Andy Farkas wrote:
The dc(4) driver is still reporting collisions on 100 Mbit full-duplex
links:
[snip]
netstat -i
NameMtu Network Address Ipkts IerrsOpkts
On Sat, Nov 15, 2003 at 05:23:08PM +1000, Andy Farkas wrote:
Jos Backus wrote:
Fwiw, I'm seeing the same with tx(4):
Looks like a different problem.
Probably. I was commenting on the (relatively) high collision count I'm
seeing. This is a hub (DSL router) with 2 PC's on it. I have never
TB --- 2003-11-15 19:25:16 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-15 19:25:16 - starting CURRENT tinderbox run for i386/i386
TB --- 2003-11-15 19:25:16 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/i386
TB --- /usr/bin/cvs -f -R -q
List,
Running -CURRENT now gives the following problem on a Compaq Pressario 1600-
XL144 laptop:
[...]
cbb0: TI1211 PCI-CardBus Bridge at device 10.0 on pci0
cardbus0: CardBus bus on cbb0
pccard0: 16-bit PCCard bus on cbb0
pcib0: _PRS resource entry has unsupported type 0
cbb: Unable to map
Robert Watson wrote:
On Sat, 15 Nov 2003, Andy Farkas wrote:
These messages spew onto my console and into syslogd once every second:
Heh. Sounds like your box is having a really bad day, we'll see if we
can't get it fixed up over the next couple of weeks as things settle out
:-).
As
Matt Smith wrote:
Marco Wertejuk wrote:
Just for a short note: cfsd (ports/security/cfs) should be
recompiled as well after those statfs changes.
And mail/postfix and devel/gnomevfs2 (ones's i've found so far)
postfix did this every time it received a mail until I recompiled it:
pid
:Expect to have to recompile the entire fricking world for a change
:this fundamental.
:
:Really, what should have appened is that the system call interface
:for stat should have been retired as ostat, a new system call
:interface introduced, and the libc version number bumped, given a
:change
Peter Edwards wrote:
On Wed, Nov 12, 2003 at 06:04:00PM -0800, Kris Kennaway wrote:
...my sparc machine reports that my i386 nfs server has 15 exabytes of
free space!
[ ... ]
The NFS protocols have unsigned fields where statfs has signed
equivalents: NFS can't represent negative available
TB --- 2003-11-15 20:55:11 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-15 20:55:11 - starting CURRENT tinderbox run for i386/pc98
TB --- 2003-11-15 20:55:11 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/pc98
TB --- /usr/bin/cvs -f -R -q
Hi,
On a system without kernel modules moused fails to start with the
following message :
moused: unable to load USB mouse driver: No such file or directory
The hardware is a Via C3 mini-itx PC with an USB mouse.
The system was compiled today; it worked on the 13th.
Even though the
Hello,
I have a Compaq armada 7800 with a noname pccard ethernet adapter
which used to be detected as:
rl0: RealTek 8139 10/100BaseTX port 0x1100-0x11ff mem 0x8800-0x880001ff irq 11
at device 0.0 on cardbus0
rl0: Ethernet address: 00:10:60:58:60:b8
miibus0: MII bus on rl0
rlphy0: RealTek
Gang,
I don't know if this is a known issue or not, but:
lock order reversal
1st 0xe0002843d7a0 vnode interlock (vnode interlock) @
/q/src/sys/ufs/ufs/ufs_ihash.c:128
2nd 0xe4685300 ufs ihash (ufs ihash) @ /q/src/sys/ufs/ufs/ufs_ihash.c:124
Stack backtrace:
recursed on
(CC's trimmed, I'm sure I'm boring people at this stage.)
Peter Edwards wrote:
On Wed, Nov 12, 2003 at 06:04:00PM -0800, Kris Kennaway wrote:
...my sparc machine reports that my i386 nfs server has 15 exabytes
of
free space!
[ ... ]
The NFS protocols have unsigned fields where statfs has
Bruce Evans wrote:
I just got around to testing the patch in that reply:
[ ... ]
This seems to work. On a 2TB-epsilon ffs1 file system (*) on an md malloc
disk (**):
Try it again. This time, take the remote FS below its free reserve
as the root user, and see what the client machine reports.
Daniel Eischen wrote:
On Fri, 14 Nov 2003, Andrew Gallatin wrote:
Can't we bump the libc version so that dynamically linked, non-system
binaries can continue to work? Having things like postfix and gnome
dumping core seems excessivly bumpy. Upgrading all ports is a pain.
I don't think
Eugene M. Kim wrote:
Validating a root password is possible with other means in many cases,
if not always. OpenSSH sshd is a good example. Even with
PermitRootLogin set to no, the attacker can differentiate whether the
password has been accepted or not.
That's because the software in
Robert Watson wrote:
What's going on is the following: while we have a compatibility system
call in place, it only affects applications linked against non-current
libc. As soon as you recompile libc, applications expecting the old
statfs() ABI get the new statfs(), and depending on where
On Sat, 15 Nov 2003, Jos Backus wrote:
On Sat, Nov 15, 2003 at 05:23:08PM +1000, Andy Farkas wrote:
Jos Backus wrote:
Fwiw, I'm seeing the same with tx(4):
Looks like a different problem.
Probably. I was commenting on the (relatively) high collision count I'm
seeing. This is a hub
On Sat, 15 Nov 2003, [iso-8859-1] Claus Guttesen wrote:
After a draft to this mail was written I was lucky
to get some output to the screen (which is the first
time since we migrated):
panic: kmem_malloc(4096): kmem_map too small:
275251200 total allocated cpuid = 0; lapic.id =
On Sat, Nov 15, 2003 at 02:45:57PM -0800, Terry Lambert wrote:
For 6.0, can we start off libc at libc.so.MMDD and move it
back to libc.so.6 for the first release? That way we can bump
it whenever we want to avoid the bumpy rides for -current
folk.
This is a great idea!
Provided
Hajimu UMEMOTO wrote:
Kostyuk Oleg [EMAIL PROTECTED] said:
cubProblem is in order of starting /etc/rc.d/ipsec.
cubIt must start BEFORE any network interaction,
cubmay be even before configuring interfaces.
cubBut I not sure in case with diskless mashines.
cub-#
M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Andrzej Tobola [EMAIL PROTECTED] writes:
: Did you tested it with nfsclient dynamically loaded ?
I can't load nfs4client.ko either. If you put all the files/paths in
nfsclient, it will load and work.
I load nfsclient.ko in my boot
Hi.
panic: kmem_malloc(4096): kmem_map too small:
275251200 total allocated cpuid = 0; lapic.id =
man tuning
You probably need to reset maxusers to 128 or so
manually since the
auto-tuning is doing the wrong thing. Although this
is usually a problem
on 4GB systems.
Matthew Dillon wrote:
I recommend that instead of rolling these sorts of system calls over
and over again (how many versions of stat do we have now? A lot!),
that instead you make a system call which returns a capability buffer
and then have libc load the capabilities it
TB --- 2003-11-15 22:21:03 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-15 22:21:03 - starting CURRENT tinderbox run for ia64/ia64
TB --- 2003-11-15 22:21:03 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64
TB --- /usr/bin/cvs -f -R -q
On Sat, Nov 15, 2003 at 03:09:27PM -0800, Doug White wrote:
On Sat, 15 Nov 2003, Jos Backus wrote:
On Sat, Nov 15, 2003 at 05:23:08PM +1000, Andy Farkas wrote:
Jos Backus wrote:
Fwiw, I'm seeing the same with tx(4):
Looks like a different problem.
Probably. I was
[EMAIL PROTECTED] wrote:
I disagree.
The intent of the negative number from df is to subtract the amount
used from the total amount available, in order to get the amount
remaining.
I just don't see how you can possibly infer from the NFS spec that
abytes is anything other than an
In message: [EMAIL PROTECTED]
Dylan Wylie [EMAIL PROTECTED] writes:
: List,
:
: Running -CURRENT now gives the following problem on a Compaq Pressario 1600-
: XL144 laptop:
:
: [...]
: cbb0: TI1211 PCI-CardBus Bridge at device 10.0 on pci0
: cardbus0: CardBus bus on cbb0
: pccard0:
: sense to do it.
:
:How do you propose to achieve POSIX compliance? At the library
:level? Or not at all?
:
:-- Terry
I don't understand the question. All that happens is that functions like
fstat() and statfs() become libc functions rather then direct syscalls.
The userland
On 11 Nov, Lukas Ertl wrote:
On Tue, 11 Nov 2003, Lukas Ertl wrote:
Unfortunately, we are still seeing a problem here: we are running uvscan
(virus scanner), and while running it we are still seeing increasing unpcb
usage and orphaned unix domain sockets.
We added some debug printfs to the
TB --- 2003-11-16 00:01:57 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-16 00:01:57 - starting CURRENT tinderbox run for sparc64/sparc64
TB --- 2003-11-16 00:01:57 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64
TB --- /usr/bin/cvs -f -R -q
On Sat, 15 Nov 2003, Terry Lambert wrote:
Bruce Evans wrote:
I just got around to testing the patch in that reply:
[ ... ]
This seems to work. On a 2TB-epsilon ffs1 file system (*) on an md malloc
disk (**):
Try it again. This time, take the remote FS below its free reserve
as the
On Fri, 14 Nov 2003 [EMAIL PROTECTED] wrote:
Bruce Evans wrote:
...
I just got around to testing the patch in that reply:
...
Your patch to nfs_vfsops won't apply to my Solaris kernel :-)
The protocol says abytes is unsigned, so the server shouldn't be lying
by sending a huge
On Sat, 15 Nov 2003, Poul-Henning Kamp wrote:
This looks slightly different if I use SCHED_ULE, but the effect is
the same.
Off the top of my head, I have not been able to find any places
where softclock would call schedcpu directly.
schedcpu() is a timeout routine, so it is always called
On Sat, Nov 15, 2003 at 03:16:03PM -0800, Marcel Moolenaar wrote:
Provided that we
2. replace the date with a convenient sequence number, which we can
call the minor version number, and
..
E.g.: libc.so.6.0, libc.so.6.1, and (first release) libc.so.6.2...
Please no -- it wouldn't be easy
On Sat, Nov 15, 2003 at 08:27:44PM +, Ceri Davies wrote: These
probably are actual collisions though. The OP's point is that
collisions are supposed to be impossible on a full duplex link,
whereas in your situation they aren't.
The collision mechanism is used for flow control on full-duplex
On Sat, Nov 15, 2003 at 11:54:20AM -0800, Lars Eggert wrote:
shouldn't this work?
# ifconfig em0 inet 128.9.168.58 netmask 255.255.240.0 \
ether 00:07:e9:0a:26:52
ifconfig: ether: bad value
This is with today's -current, but this may have been around longer - I
hadn't tried it
At 6:20 PM -0800 11/15/03, David O'Brien wrote:
On Sat, Nov 15, 2003 at 03:16:03PM -0800, Marcel Moolenaar wrote:
Provided that we
2. replace the date with a convenient sequence number,
which we can call the minor version number, and
..
E.g.: libc.so.6.0, libc.so.6.1, and (first release)
Hi,
I saw that something has changed on ULE and wanted to give it a try but with
sources from ~ So 16 Nov 2003 04:00 UTC I get the following kernel panic just
before disk/geom and after Timecounter TSC frequency 1095341787 Hz quality
800:
Fatal trap 12 :page fault while in kernel mode
fault
On Sun, 16 Nov 2003, Harald Schmalzbauer wrote:
Fatal trap 12 :page fault while in kernel mode
fault virtual address =0x24
fault code =supervisor read, page not present
instruction pointer =0x8:0xc056c706
stack pointer =0x10:0xcdca4ca4
frame pointer
On Sunday 16 November 2003 05:34, Robert Watson wrote:
On Sun, 16 Nov 2003, Harald Schmalzbauer wrote:
Fatal trap 12 :page fault while in kernel mode
fault virtual address =0x24
fault code =supervisor read, page not present
instruction pointer =0x8:0xc056c706
stack
On Sunday 16 November 2003 05:40, Craig Rodrigues wrote:
On Sun, Nov 16, 2003 at 05:32:03AM +0100, Harald Schmalzbauer wrote:
instruction pointer =0x8:0xc056c706
stack pointer =0x10:0xcdca4ca4
frame pointer =0x10:0xcdca4ca4
Do you have a file:
On Sunday 16 November 2003 05:49, Harald Schmalzbauer wrote:
On Sunday 16 November 2003 05:34, Robert Watson wrote:
On Sun, 16 Nov 2003, Harald Schmalzbauer wrote:
Fatal trap 12 :page fault while in kernel mode
fault virtual address =0x24
fault code =supervisor read,
I just committed a patch to change /bin and /sbin from statically to
dynamically linked. If you don't like the idea of using a dynamically
linked /bin and /sbin, now is the time to define NO_DYNAMICROOT in your
make.conf.
The reasons for doing so have been hashed over lots of times. But the
short
On Sat, Nov 15, 2003 at 11:05:51PM -0500, Garance A Drosihn wrote:
Or maybe the real problem is that we claim that there will
be no API/ABI changes after X.0-RELEASE, and we've really
missed that mark with 5.0-RELEASE, for a variety of reasons.
Where do we claim that?
All I'm aware of is the
On Sat, Nov 15, 2003 at 06:36:17PM -0800, Kris Kennaway wrote:
hammer02 died after a few minutes of idling with:
panic: Assertion TD_IS_RUNNING(td) failed at
/a/asami/portbuild/amd64/src-client/sys/kern/subr_turnstile.c:687
Debugger(panic)
Stopped at Debugger+0x4b: xchgl
On Sat, 15 Nov 2003, Marcel Moolenaar wrote:
On Sat, Nov 15, 2003 at 02:45:57PM -0800, Terry Lambert wrote:
For 6.0, can we start off libc at libc.so.MMDD and move it
back to libc.so.6 for the first release? That way we can bump
it whenever we want to avoid the bumpy rides for
In message: [EMAIL PROTECTED]
David O'Brien [EMAIL PROTECTED] writes:
: On Sat, Nov 15, 2003 at 03:16:03PM -0800, Marcel Moolenaar wrote:
: Provided that we
: 2. replace the date with a convenient sequence number, which we can
: call the minor version number, and
: ..
: E.g.:
TB --- 2003-11-16 05:00:02 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-16 05:00:02 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2003-11-16 05:00:02 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha
TB --- /usr/bin/cvs -f -R -q
In message: [EMAIL PROTECTED]
Garance A Drosihn [EMAIL PROTECTED] writes:
: At 6:20 PM -0800 11/15/03, David O'Brien wrote:
: On Sat, Nov 15, 2003 at 03:16:03PM -0800, Marcel Moolenaar wrote:
: Provided that we
:2. replace the date with a convenient sequence number,
: which
1 - 100 of 104 matches
Mail list logo
