It seems John S. Dyson wrote:
Søren Schmidt said:
It should work, but the promise support in the old system is, well,
hacky at best. I'm not sure if Promise supports more than one card
at a time, but from looking at the chip specs, it should work just
fine, and if the hardware works,
On Tue, Feb 23, 1999 at 02:41:14AM +0300, Dmitrij Tejblum wrote:
Jos Backus wrote:
This occurs almost immediately after copying a file to an msdos fs. I can
provide more info if that is deemed useful.
I suspect your kernel compiled with INVARIANTS,
Yes, and with INVARIANTS_SUPPORT as well
On Mon, 22 Feb 1999, Bruce Evans wrote:
I fixed this a while back to use sysctlbyname, as it should have been
done. Bruce subsequently backed it out (bad idea, IMO).
You only worked around the previous breakage of vfs sysctls for the
statically configured case. The dynamically configured
Jos Backus wrote:
On Tue, Feb 23, 1999 at 02:41:14AM +0300, Dmitrij Tejblum wrote:
Jos Backus wrote:
This occurs almost immediately after copying a file to an msdos fs. I can
provide more info if that is deemed useful.
I suspect your kernel compiled with INVARIANTS,
Yes, and with
Excerpt from po...@freebsd.org:
MVHO - lsof should be in contrib/ and _very_ thoroughly grovelled through.
If people feel this is desired, I can easily bmake and import it.
From working with Vic Abell, I know he is interested in any
problems/issues that we may find in LSOF if we find issues when
I fixed this a while back to use sysctlbyname, as it should have been
done. Bruce subsequently backed it out (bad idea, IMO).
You only worked around the previous breakage of vfs sysctls for the
statically configured case. The dynamically configured case was more
fundamentally broken
On Tue, Feb 23, 1999 at 12:09:03PM +0300, Dmitrij Tejblum wrote:
Inline functions in vm/vm_zone.h depend on INVARIANTS. These functions
used in msdosfs and in other parts of the kernel.
OK, I see.
How does one add INVARIANTS support to modules?
You could add -DINVARIANTS to CFLAGS in
Is it possible to load kernel modules that are supposed
to operate on pci devices?
... Does pci_rescan() need to be finished ?
What am I missing here?
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
On Tue, 23 Feb 1999 01:18:42 PST, David O'Brien wrote:
If people feel this is desired, I can easily bmake and import it.
From working with Vic Abell, I know he is interested in any
problems/issues that we may find in LSOF if we find issues when
scrutinizing it.
Hi David,
I think Vic's
David O'Brien wrote:
Excerpt from po...@freebsd.org:
MVHO - lsof should be in contrib/ and _very_ thoroughly grovelled through.
If people feel this is desired, I can easily bmake and import it.
From working with Vic Abell, I know he is interested in any
problems/issues that we may find in
On Mon, 22 Feb 1999, Alexander N. Kabaev wrote:
The following script reliably causes FreeBSD 4.0-CURRENT (and 3.1-STABLE
as of today) to lookup. Shortly after this script is started, all disk
activity
stops and any attempt to create new process causes system to freese. While
in
On Tue, 23 Feb 1999 02:04:46 -0800, David Holloway david...@wrs.com said:
Is it possible to load kernel modules that are supposed
to operate on pci devices?
Not yet. There are several of us who have worked on parts of this
problem in the past, but we're not there yet. Join
On Tue, Feb 23, 1999 at 10:59:39AM +0100, Jos Backus wrote:
On Tue, Feb 23, 1999 at 12:09:03PM +0300, Dmitrij Tejblum wrote:
Inline functions in vm/vm_zone.h depend on INVARIANTS. These functions
used in msdosfs and in other parts of the kernel.
OK, I see.
How does one add INVARIANTS
Alexander N. Kabaev wrote:
ANK The following script reliably causes FreeBSD 4.0-CURRENT (and 3.1-STABLE
ANK as of today) to lookup.
2.2.8 and 3.0-RELEASE are not vulnerable, by the way.
ANK Shortly after this script is started, all disk
ANK activity stops and any attempt to create new process
On Tue, Feb 23, 1999 at 04:16:26PM +0100, Eivind Eklund wrote:
Somehow this strikes me as a Bad Thing...
It _is_ a bad thing. I've been pondering what to do with the
intrusive invariant checks - make them dependent on
INTRUSIVE_INVARIANTS, perhaps?
Depends on how dangerous these invariant
Luoqi Chen said:
This seems to be the good old vnode deadlock during vm_fault() that has been
reported a couple of times, and there's still no satisfactory solution to
it:
fgrep does something like this: (don't ask me why)
addr = mmap(0, len, PROT_READ|PROT_WRITE,
Garrett feels happier about fstat as it is Original BSD Code. Any
chances of engineering the functional diffs between fstat(1) and
lsof(1) back into fstat?
I guess it is possible, but it would probably take someone like Peter,
bde, or Matt Dillon that understands well all of our layerd
On Tue, Feb 23, 1999 at 05:08:57PM +0100, Jos Backus wrote:
On Tue, Feb 23, 1999 at 04:16:26PM +0100, Eivind Eklund wrote:
Somehow this strikes me as a Bad Thing...
It _is_ a bad thing. I've been pondering what to do with the
intrusive invariant checks - make them dependent on
I think Vic's responsiveness and enthusiasm for team-work means that the
software gets excellent attention when it comes to FreeBSD issues.
We get very high attention by Vic. I've provided him access (or
obtained access) to FreeBSD-CURRENT many times when he requested so he
could test things.
In message 19990223191857.h10...@bitbox.follo.net, Eivind Eklund writes:
A couple of the invariants we have modify the
behaviour to make it possible to check for things, and this should be
separate from the ones that doesn't modify the behaviour beyond adding
checks.
That sounds more like
This reminds me; do we have a utility to reference wmesg strings back
to the code that sets them, a la TAGS? Would this be useful?
No, and yes respectively.
I have the scanner mostly written; there is one bug yet to fix (This
time for sure!). Presently, it creates a single file WTAGS which
Luoqi Chen said:
Do you still have that piece of code? Does it handle the case involves more
than one process? For example, process 1 mmaps file B and reads file A into
the mmapped region, while process 2 mmaps file A and reads file B, this could
also result in a deadlock.
It used to be
Søren Schmidt said:
It seems John S. Dyson wrote:
Søren Schmidt said:
It should work, but the promise support in the old system is, well,
hacky at best. I'm not sure if Promise supports more than one card
at a time, but from looking at the chip specs, it should work just
fine,
I have been seeing 5 hour delays from when the message was sent to the list
and when the message arrives in my mailbox. It seems to be a problem with
the following jump:
Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18])
by mail2.sol.net (8.8.8/8.8.8/SNNS-1.02) with ESMTP id
Hi folks,
Updating at Mar 23 fév 1999 22:52:33 CET,
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions
-ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK
-include
On Tue, Feb 16, 1999 at 10:16:05PM -0700, Warner Losh wrote:
In message 199902141331.faa27...@hub.freebsd.org Jonathan M. Bresler
writes:
: how much information about this should be included in
: /usr/src/UPDATING? the entry there talks about the change but does
: not provide enough
Hi,
I don't claim to know a great deal about cache code etc, but I'm
pretty sure that it's extremely unlikely that the file name has any
chance of affecting the buffer cache. While NFS has its fair
share of problems (with which Matt is dealing with admirably), I
would think that the code
According to David E . O'Brien:
If people feel this is desired, I can easily bmake and import it.
From working with Vic Abell, I know he is interested in any
problems/issues that we may find in LSOF if we find issues when
scrutinizing it.
Well, the way I see it, Vic is already maintaining
Jos Backus wrote:
That is, INVARIANTS in kernel incompatible with dynamic loading.
Somehow this strikes me as a Bad Thing...
Invariants is not for the production minded. It is for those who
work with things likely to get broken. Say, for instance, -current.
:-)
--
Daniel C. Sobral
On Tue, 23 Feb 1999, Thomas T. Veldhouse wrote:
Also, as a side note, how do I set up my box to use PostFix instead of
sendmail? I heard that it was (or was considered) included in the
3.1-RELEASE, it just wasn't enabled by default.
It was shouted down as unnecessary bloat in favour of a
:In message 19990223191857.h10...@bitbox.follo.net, Eivind Eklund writes:
:
:A couple of the invariants we have modify the
:behaviour to make it possible to check for things, and this should be
:separate from the ones that doesn't modify the behaviour beyond adding
:checks.
:
:That sounds more
Hi, brian,
Good idea - I will set up tests tomorrow following your advice.
I don't want to be right - I want to be problem-free:-)
I can't use my son's machine as he is behind a firewall I can't breach
so I will set it up with a couple of machines here on my LAN,
internally.
I might just swap
On Tue, 23 Feb 1999, Ollivier Robert wrote:
According to David E . O'Brien:
If people feel this is desired, I can easily bmake and import it.
From working with Vic Abell, I know he is interested in any
problems/issues that we may find in LSOF if we find issues when
scrutinizing it.
33 matches
Mail list logo
