Julian Elischer wrote:
can you announce when the fixes are in place?
I'll do better; I am about to back it all out.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
On Fri, 22 Jan 1999, Archie Cobbs wrote:
Unrelated question: SYSINIT() doesn't work from KLD modules.
Is this problem being addressed?
you mean sysctl
-Archie
___
Archie Cobbs * Whistle Communications, Inc. *
:It's definately happening still, sorry. :-( I recompiled a 100% static
:kernel and have had three more explosions, usually after starting exmh.
:(exmh takes 10 to 15MB of ram on this system due to my mailbox folder
:sizes).
:
:However, a clue.. The SMP box that is doing fine is a P6, an NFS
Poul-Henning Kamp writes:
... to make up our mind about it.
[ clear arguments for DEVFS and why persistence is complicated ]
This email was a few weeks ago, and there was a lively debate, then
Julian sent an email listing some issues/requirements, and then
the thread kindof died and now we're
Julian Elischer writes:
On Fri, 22 Jan 1999, Archie Cobbs wrote:
Unrelated question: SYSINIT() doesn't work from KLD modules.
Is this problem being addressed?
you mean sysctl
Oops, thanks.. SYSCTL() doesn't work from KLD modules but SYSINIT() does.
-Archie
Matthew Dillon wrote:
:It's definately happening still, sorry. :-( I recompiled a 100% static
:kernel and have had three more explosions, usually after starting exmh.
:(exmh takes 10 to 15MB of ram on this system due to my mailbox folder
:sizes).
:
:However, a clue.. The SMP box that
Archie Cobbs wrote:
Julian Elischer writes:
On Fri, 22 Jan 1999, Archie Cobbs wrote:
Unrelated question: SYSINIT() doesn't work from KLD modules.
Is this problem being addressed?
you mean sysctl
Oops, thanks.. SYSCTL() doesn't work from KLD modules but SYSINIT() does.
-Archie
A very interesting error during last nights buildworld.
In think the fix is obvious.
=== usr.bin/xlint/xlint
cc -O2 -m486 -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK
-I/ust/src/usr.bin/xlint/xlint/../lint1 -I/usr/obj/ust/src/tmp/usr/include -c
/ust/src/usr.bin/xlint/xlint/xlint.c
cc -O2 -m486
On Thu, Jan 21, 1999 at 12:55:38AM -0800, Matthew Dillon wrote:
One thing I haven't been able to test, because I forgot: Interleaved
swap ( more then one swap device ). I'll try to test that ASAP.
I've tried, with sources cvsupped at 0600 22/11/1999 UTC. On a 128MB
machine, and a
On 22 Jan, Bruce Evans wrote:
/cdrom:
.(type: unknown)
.. (type: unknown)
autorun.inf (type: unknown)
This is because the cd9660 file system doesn't implement d_type.
man dirent or man
Hi
I het a lot of this in my PLIP connection:
Jan 23 14:44:00 gratis /kernel: X
Jan 23 14:44:00 gratis /kernel: X
Jan 23 14:44:01 gratis /kernel: RR
Jan 23 14:44:01 gratis /kernel: RR
Jan 23 14:44:02 gratis /kernel: X^X^R
Jan 23 14:44:02 gratis /kernel: X^X^R
Seems that in
On Sat, Jan 23, 1999 at 01:34:40AM -0500, Mikhail Teterin wrote:
I tried both cam and bio -- no difference. It is not that it's
slow -- I was prepared for that, it is that it totally hangs --
forever.
I narrowed it down to softupdates. If I disable the softupdates on
the cartridge's filesystem
On Sat, Jan 23, 1999 at 02:59:22PM +0200, Mark Murray wrote:
Hi
I het a lot of this in my PLIP connection:
Jan 23 14:44:00 gratis /kernel: X
Jan 23 14:44:00 gratis /kernel: X
Jan 23 14:44:01 gratis /kernel: RR
Jan 23 14:44:01 gratis /kernel: RR
Jan 23 14:44:02 gratis /kernel: X^X^R
Jan 23
=I tried both cam and bio -- no difference. It is not that it's
=slow -- I was prepared for that, it is that it totally hangs --
=forever.
=
=I narrowed it down to softupdates. If I disable the softupdates on
=the cartridge's filesystem copying finishes successfully. Somehow
=the `cp' process
Has this been done yet? It has been over 7 hours since the post and I
have only seen two source changes, and they are in sys/pci by roger.
Tom Veldhouse
ve...@visi.com
Mark Murray wrote:
Julian Elischer wrote:
can you announce when the fixes are in place?
I'll do better; I am about to
Never mind, I was using the RELENG_3 tag during CVSup. Sorry.
Thomas T. Veldhouse wrote:
Has this been done yet? It has been over 7 hours since the post and I
have only seen two source changes, and they are in sys/pci by roger.
Tom Veldhouse
ve...@visi.com
Mark Murray wrote:
Julian
I've just posted a brief overview of the new device system in FreeBSD at
http://www.freebsd.org/~dfr/devices.html. The information content is
fairly small but it might help someone who is trying to understand the
source code.
--
Doug Rabson Mail: d...@nlsystems.com
Thomas T. Veldhouse wrote:
Has this been done yet? It has been over 7 hours since the post and I
have only seen two source changes, and they are in sys/pci by roger.
Hours ago :-).
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to
Hi
This isn't exactly topic here, but it might be useful as a little hint
or warning...
Even most recent versions of libtool (1.2e imho) fail to check for
freebsd4* (as expected). As a result, they set can_build_shared to no
which disables building of shared libraries.
This affects most major
On Thu, Jan 21, 1999 at 07:41:20AM -0400, Victor Salaman wrote:
I just csvup'ed the sources...(I had the sources from January 12's
snapshot). While trying to do a make world, eventually I get this message.
c++ -pg -I/usr/obj/usr/src/tmp/usr/include/g++ -nostdinc -O -pipe
-I/usr/src/gnu
I ran into an interesting problem in the process of modifying
netstat to understand the PF_NETGRAPH protocol family. netstat
uses kvm_read(), etc. to read kernel symbols. However, this doesn't
work when the symbols you're looking for are in an KLD module (eg,
ng_socket.ko) -- the symbol will
Julian Elischer writes:
On Fri, 22 Jan 1999, Archie Cobbs wrote:
Unrelated question: SYSINIT() doesn't work from KLD modules.
Is this problem being addressed?
you mean sysctl
Oops, thanks.. SYSCTL() doesn't work from KLD modules but SYSINIT() does.
What I get for being too fast.
On Sat, 23 Jan 1999, Peter Wemm wrote:
Matthew Dillon wrote:
:It's definately happening still, sorry. :-( I recompiled a 100% static
:kernel and have had three more explosions, usually after starting exmh.
:(exmh takes 10 to 15MB of ram on this system due to my mailbox folder
On Sat, 23 Jan 1999, Doug Rabson wrote:
I just had one of these on one of my alphas. The machine is UP
(obviously), no MFS, no dynamically loaded stuff. It was doing an
installworld with NFSv3 mounted source, local obj. All filesystems were
using softupdates.
I made it happen again by
-current as of early this morning
% make aout-to-elf-bbuild
...
cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 pccard/*.h
/usr/obj/aout/usr/src/tmp/usr/include/pccard
cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 posix4/*.h
Mike Smith writes:
Yes, there's a desire to see this fixed; it requires a significant
rewrite of the sysctl stuff unfortunately. Mark Murray was working on
this but probably as a 4.x feature; if you have something simpler you
feel up to contributing in the short term you'd be very popular.
:I made it happen again by doing the same installworld but this time I
:caught it in the debugger. I'll leave the machine up for a while in case
:someone has some idea of how to debug it. The stacktrace looks like this:
:
:#0 Debugger () at ../../alpha/alpha/db_interface.c:260
:#1
In article m1047wh-0008...@rip.psg.com, Randy Bush ra...@psg.com wrote:
-current as of early this morning
% make aout-to-elf-bbuild
...
cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 ufs/ffs/*.h
/usr/obj/aout/usr/src/tmp/usr/include/ufs/ffs
install:
On Sat, 23 Jan 1999, Matthew Dillon wrote:
:I made it happen again by doing the same installworld but this time I
:caught it in the debugger. I'll leave the machine up for a while in case
:someone has some idea of how to debug it. The stacktrace looks like this:
:
:#0 Debugger () at
Mike Smith writes:
My question is, should kvm_read() and friends be enhanced with
this ability to find a symbol by searching through the loaded
KLD modules? Seems a bit hackish, but then again so is the whole
kvm() idea.
No; you should be using sysctl to get at the information.
Yes in
For everybody who has been waiting for me finish the aic driver I thought
I should give a status report. My move is mostly complete and I am trying
to get back to working in the aic driver. Unfortunately I have run into
hardware problems. Having just bought a house I can not afford to run out
Doug Rabson wrote:
On Sat, 23 Jan 1999, Matthew Dillon wrote:
:I made it happen again by doing the same installworld but this time I
:caught it in the debugger. I'll leave the machine up for a while in case
:someone has some idea of how to debug it. The stacktrace looks like this:
At 05:47 PM 1/23/99 +0100, Alexander Sanda wrote:
Even most recent versions of libtool (1.2e imho) fail to check for
freebsd4* (as expected). As a result, they set can_build_shared to no
which disables building of shared libraries.
Here is a simple patch (which I'll forward this to the libtool
Peter Wemm wrote:
Matthew Dillon wrote:
[..]
Try changing the panic in vm/vm_page.c to a printf() (
I'll do that.
BTW; what are the dangers of this? lost disk writes or corruption? Can
we (as a workaround) push the page that we found back onto a dirty queue
and try again after some
On Sun, 24 Jan 1999, Peter Wemm wrote:
Doug Rabson wrote:
On Sat, 23 Jan 1999, Matthew Dillon wrote:
:I made it happen again by doing the same installworld but this time I
:caught it in the debugger. I'll leave the machine up for a while in case
:someone has some idea of how
It seems to be the same problem we have been having with current.
Should it be crypt stuff be backed out of here as well?
=== libpam/modules/pam_radius
=== libpam/modules/pam_skey
=== libpam/modules/pam_tacplus
=== libpam/modules/pam_unix
=== libpam/libpam
ld -o pam_static_modules.o -r
:[..]
: Try changing the panic in vm/vm_page.c to a printf() (
:
: I'll do that.
:
:BTW; what are the dangers of this? lost disk writes or corruption? Can
:we (as a workaround) push the page that we found back onto a dirty queue
:and try again after some diagnostics?
That's ok,
I'm sorry if this was already discussed -- I just re-subscribed
to current.
In many places in config scripts, host_os is checked against
freebsd2 | freebsd3
Absence of freebsd4 breaks stuff, like, for example, kdelibs11
port, which refuses to build shared libraries on an unknown platform
such as
Matthew Dillon wrote:
[..]
:Oh, one other thing that occurred to me.. Under 4.0-current, I regularly
:(ie: within 30 seconds of boot) get if_de tranmitter underflows. My
:console corruption was happening at the instant that de0 was being
:configured with ifconfig. exmh is running to a
On Sun, 24 Jan 1999, Peter Wemm wrote:
Oh, one other thing that occurred to me.. Under 4.0-current, I regularly
(ie: within 30 seconds of boot) get if_de tranmitter underflows. My
console corruption was happening at the instant that de0 was being
configured with ifconfig. exmh is
As of Today's 4.0-CURRENT My system Halts on boot-up after the BTX Driver
showing my BIOS-drives, with the following message:
FreeBSD/i386 bootstrap loader, Revision 0.2
(dae...@shadowmere. etc...)
ficlExecFD: Error at line 1
then it shows a lot of Register-information with the message
an hour further on
/usr/obj/aout/usr/src/tmp/usr/libexec/elf/ld: warning: libcrypt.so.2, needed by
/usr/obj/elf/usr/src/kerberosIV/libexec/kauthd/../../lib/libkrb/libkrb.so, not
found (try using --rpath)
/usr/obj/elf/usr/src/kerberosIV/libexec/kauthd/../../lib/libkrb/libkrb.so:
undefined
Thomas T. Veldhouse wrote:
It seems to be the same problem we have been having with current.
Should it be crypt stuff be backed out of here as well?
_Completely_ Different issue. :-(
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to
I have noticed this behaviour on at least one machine.
If I shutdown the machine with apm power off, the filesystem is dirty and
has to been checked on the next reboot. It seems, the power is cut too fast.
I don't have any problems with reboots.
It seems the drive doesn't have the time to write
probably the drive needs write-caching turned off...
On Sat, 23 Jan 1999, D. Rock wrote:
I have noticed this behaviour on at least one machine.
If I shutdown the machine with apm power off, the filesystem is dirty and
has to been checked on the next reboot. It seems, the power is cut too
On Sat, 23 Jan 1999, Kurt D. Zeilenga wrote:
At 05:47 PM 1/23/99 +0100, Alexander Sanda wrote:
Even most recent versions of libtool (1.2e imho) fail to check for
freebsd4* (as expected). As a result, they set can_build_shared to no
which disables building of shared libraries.
Here is a
I build a current-4 kernel on gina and installed it on arnold.
Then I added 32MB ram.
nfs'mounted gina's /usr/src and /usr/obj on arnold, and tried an
installworld. But I got random reboots, I guess it was signal 11,
segmentation fault.
Could it be because I had a current-4 kernel, but a stable-3
This is what I also thought. But how do I turn off write caching on IDE
disks. I know how to do on SCSI bit (mode page 8 byte 2 bit 2 clear), but
I have absolutely no clue how this can be achieved on IDE disks.
I normally turn off write caching on all drives I install. The drive shouldn't
shuffle
D. Rock wrote:
This is what I also thought. But how do I turn off write caching on IDE
disks. I know how to do on SCSI bit (mode page 8 byte 2 bit 2 clear), but
I have absolutely no clue how this can be achieved on IDE disks.
I normally turn off write caching on all drives I install. The
Do any of the LaTeX ports work anymore, or do I have something
grubby in my ${LOCALBASE}?
I tried latex, teTeX, and teTeX-beta... each had one problem
or another. latex can't be fetched, teTeX-beta can't build,
and teTeX doesn't work after being installed.
Jacques Vidrine / n...@nectar.com /
We are sorry if you received this email in error. To be removed
from this list please send an email to the address below.
mailto:getl...@tfz.net;
$ ENTREPRENEURS $
*Tired of working for someone else and getting paid what
they feel you're worth?
*Tired of the get-rich-quick $5 fantasy
On Sat, Jan 23, 1999 at 10:46:30AM +, Adrian Wontroba wrote:
I've tried, with sources cvsupped at 0600 22/11/1999 UTC. On a 128MB
!
0 (sigh, up too late)
--
Adrian Wontroba
To Unsubscribe: send
Is this the first page of a 20 page document giving examples and pointers?
:-)
On Sat, 23 Jan 1999, Doug Rabson wrote:
I've just posted a brief overview of the new device system in FreeBSD at
http://www.freebsd.org/~dfr/devices.html. The information content is
fairly small but it might help
On Sat, 23 Jan 1999, Julian Elischer wrote:
Is this the first page of a 20 page document giving examples and pointers?
:-)
No.. Its just an overview at the moment (it started off as some email
explaining roughly how the thing fits together). Maybe I'll find the time
to write some more
:swapinfo output looks a little odd:
:
:
:Device 1K-blocks UsedAvail Capacity Type
:/dev/da0s2b19660819372 17710810%Interleaved
:/dev/da3b 19670419140 17743610%Interleaved
:Total 393056 3930560 100%
:
:The totals don't appear
On Sun, 24 Jan 1999, Peter Wemm wrote:
[..]
Oh, one other thing that occurred to me.. Under 4.0-current, I regularly
(ie: within 30 seconds of boot) get if_de tranmitter underflows. My
console corruption was happening at the instant that de0 was being
configured with ifconfig. exmh is
Yes, we're working on it in a sub-group.
Since the panic message is a new one -- it's one I added that never existed
in -3.x, it is possible that the bug is not related to my VM stuff but
related to something else going on.
I've found a number of other bugs in the greater VM
Hey guys:
I thought I'd put this up for discussion here.
Does anyone have objections to changing the default behavior for how the
long password for fetch is chosen?
Most FTP servers which do check the password given for an anonymous login,
expect either 'username@' or 'usern...@valid.fqdn'.
:Here too... pretty quickly after boot on a SMP machine (current as of Jan
:12) that pushes quite a bit of traffic, the following messages appear:
:
:de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256)
:de0: abnormal interrupt: transmit underflow (raising TX threshold to
Here too... pretty quickly after boot on a SMP machine (current as of Jan
12) that pushes quite a bit of traffic, the following messages appear:
de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256)
[..]
Three people getting these panics, three people with DEC
:But that was a week ago, and it's a *busy* news server (that's not hitting
:swap), I was just curious about the error messages from the de driver.
:
: -- Niels.
The transmit underflow messages:
de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256)
de0: abnormal
On Sat, 23 Jan 1999, Matthew Dillon wrote:
Yes, we're working on it in a sub-group.
Since the panic message is a new one -- it's one I added that never
existed
in -3.x, it is possible that the bug is not related to my VM stuff but
related to something else going on.
:
: I am also comitting some very strict KASSERT checking to try to catch
: the problem earlier. Everyone running 4.x kernels should add the
following
:
:Ahem, would you kindly define 'everyone'?
Anyone, everyone, everybody, all ... any individual using the -4.x
kernels needs
Matthew Dillon wrote:
:But that was a week ago, and it's a *busy* news server (that's not hitting
:swap), I was just curious about the error messages from the de driver.
:
: -- Niels.
The transmit underflow messages:
de0: abnormal interrupt: transmit underflow (raising TX
On Sat, 23 Jan 1999, Matthew Dillon wrote:
i have 'ed' driver and mine blows up as well.
:Here too... pretty quickly after boot on a SMP machine (current as of Jan
:12) that pushes quite a bit of traffic, the following messages appear:
:
:de0: abnormal interrupt: transmit underflow (raising
Hi,
I tried latex, teTeX, and teTeX-beta... each had one problem or
another. latex can't be fetched, teTeX-beta can't build, and teTeX
doesn't work after being installed.
How is teTeX not working? I'm using a month or so old version of -current
(back in the 3.0 days) on my home machine and
:
:i have 'ed' driver and mine blows up as well.
:
:panic: found dirty cache page 0xf047ae60
:Debugger(panic)
Ok, so much for if_de being the cause.
BTW, for anybody who doesn't want to wait for us to find the
bug, you can comment out the MADV_FREE code and that should
put a
What if we declare death to LKM screen savers and remove them from
the source tree? After all KLD screen savers are working well.
Kazu
As of a few minutes ago, I committed some changes that:
1: make the LKM code use the common VFS and syscall registration routines
2: make an 'options LKM'
:On my system I can understand it, it's a 2xP5 with a shared L2 cache on a
:Neptune chipset - something that isn't known for speed. Once you get two
:processors hammering the system bus, *plus* mix in an EISA scsi
:controller, I could well imagine the memory bus getting thrashed.
When we
On Sat, 23 Jan 1999, Matthew Dillon wrote:
:
:i have 'ed' driver and mine blows up as well.
:
:panic: found dirty cache page 0xf047ae60
:Debugger(panic)
Ok, so much for if_de being the cause.
BTW, for anybody who doesn't want to wait for us to find the
bug, you can
Kazutaka YOKOTA yok...@zodiac.mech.utsunomiya-u.ac.jp writes:
What if we declare death to LKM screen savers and remove them from
the source tree? After all KLD screen savers are working well.
Sure. I don't see any reason to keep them. I'll do the deed.
DES
--
Dag-Erling Smorgrav -
In article 36aa271c.1bcfa...@visi.com,
Thomas T. Veldhouse ve...@visi.com wrote:
It seems to be the same problem we have been having with current.
Should it be crypt stuff be backed out of here as well?
=== libpam/modules/pam_radius
=== libpam/modules/pam_skey
=== libpam/modules/pam_tacplus
Dag-Erling Smorgrav d...@flood.ping.uio.no writes:
Kazutaka YOKOTA yok...@zodiac.mech.utsunomiya-u.ac.jp writes:
What if we declare death to LKM screen savers and remove them from
the source tree? After all KLD screen savers are working well.
Sure. I don't see any reason to keep them. I'll
Pascal Hofstee wrote:
As of Today's 4.0-CURRENT My system Halts on boot-up after the BTX Driver
showing my BIOS-drives, with the following message:
FreeBSD/i386 bootstrap loader, Revision 0.2
(dae...@shadowmere. etc...)
ficlExecFD: Error at line 1
then it shows a lot of
In article xzpyamtnwl0@flood.ping.uio.no,
Dag-Erling Smorgrav d...@flood.ping.uio.no wrote:
Doh, they were already axed by sos in late December. 'cvs co src/lkm'
still creates directories for them though. I'm sure someone with more
CVS experience than me will be able to explain why :)
On Sat, 23 Jan 1999, John Polstra wrote:
In article xzpyamtnwl0@flood.ping.uio.no,
Dag-Erling Smorgrav d...@flood.ping.uio.no wrote:
Doh, they were already axed by sos in late December. 'cvs co src/lkm'
still creates directories for them though. I'm sure someone with more
CVS
On Sat, 23 Jan 1999, Matthew Dillon wrote:
:
:i have 'ed' driver and mine blows up as well.
:
:panic: found dirty cache page 0xf047ae60
:Debugger(panic)
Ok, so much for if_de being the cause.
BTW, for anybody who doesn't want to wait for us to find the
bug, you can
On Sat, 23 Jan 1999, John Polstra wrote:
In article xzpyamtnwl0@flood.ping.uio.no,
Dag-Erling Smorgrav d...@flood.ping.uio.no wrote:
Doh, they were already axed by sos in late December. 'cvs co src/lkm'
still creates directories for them though. I'm sure someone with more
On Sat, Jan 23, 1999 at 06:51:54PM -0800, Matthew Dillon wrote:
:
:btw, i'm hardly 'stressing' this machine it's a k6-233+96ram and
:i'm running X and doing a 'make release'
:
:Is it safe to enable crashdumps on IDE disks yet?
:
:-Alfred
I don't know.
I wasn't aware that there
I have noticed this behaviour on at least one machine.
If I shutdown the machine with apm power off, the filesystem is dirty and
has to been checked on the next reboot. It seems, the power is cut too fast.
I don't have any problems with reboots.
It seems the drive doesn't have the time to
I've committed one bug fix to the 'found dirty cache page' bug --
turns out vm_map_split() was the culprit, renaming pages
without removing them from PQ_CACHE. The bug was introduced
in -3.0, and hit the KASSERT() I put in -4.x.
I've committed a general inlining of 'changing
On Sat, 23 Jan 1999, Mike Smith wrote:
Always use -P when you check out sources: cvs co -P src/lkm.
And when you update sources already checked out, use cvs upd -Pd.
cvs up (not cvsup) takes me a LONG time to execute, i've been using '-z3'
for comppression because i'm on dialup,
On Sun, 24 Jan 1999, Brian Feldman wrote:
:btw, i'm hardly 'stressing' this machine it's a k6-233+96ram and
:i'm running X and doing a 'make release'
:
:Is it safe to enable crashdumps on IDE disks yet?
:
:-Alfred
I don't know.
I wasn't aware that there was a problem
.(02:36:11)(r...@bright.reserved)
ipfw add pipe 1 ip from server to cvsup.freebsd.org
(long pause i assume DNS)
0 pipe 1 ip from 192.168.2.20 to 198.104.92.71
.(02:36:26)(r...@bright.reserved)
~perlsta # ipfw pipe 1 config bw 18Kbit/s delay 20ms
.(02:36:45)(r...@bright.reserved)
~perlsta #
84 matches
Mail list logo
