On Fri, 8 Feb 2002, Julian Elischer wrote:
John, (peter? others?)
How is it that getting a ucred reference is guarded by PROC_LOCK(p)
but freeing it is guarded by mtx_lock(Giant);
?
Call me naive, but shouldn't they be guarded by the same thing?
In fact, if we had good atomic
This is a note for someone upgrading from 4.4 stable to current 5.0
comes right out of my experience in doing so the file
/usr/src/UPGRADE doesnt detail the following step
I didnt see ne 1 post this before may be it will help
some newbie like myself and perhaps somebody will add
it to the
On Fri, 8 Feb 2002, Julian Elischer wrote:
Bruce, for the low-level impared such as myself, can you give a quick
precis on teh difference between fast interrupt handlers in -current
and 'normal' interrupt handlers.
Fast interrupt handlers are harder to program and should rarely be used.
On Fri, 8 Feb 2002, Julian Elischer wrote:
I'd like to commit the code to keep the ucred across userland,
with the code to clear it to NULL kept under DEBUG ifdefs.
i.e.
in trap(), ast() and syscall()
if (td-td_ucred != p-p_ucred) {
PROC_LOCK(p);
On 09-Feb-02 Julian Elischer wrote:
I'm a little worried about invariants because the behaviour when
INVARIANTS is set wil be different to teh behaviour when it is off, which
is 'strange' to say the least. Normally the behaviour si the same but you
just check for invariant conditions.
In
On 09-Feb-02 Julian Elischer wrote:
John, (peter? others?)
How is it that getting a ucred reference is guarded by PROC_LOCK(p)
but freeing it is guarded by mtx_lock(Giant);
?
Call me naive, but shouldn't they be guarded by the same thing?
Naive, maybe. :-P The actual refcount for a
On 09-Feb-02 Julian Elischer wrote:
On Fri, 8 Feb 2002, Julian Elischer wrote:
John, (peter? others?)
How is it that getting a ucred reference is guarded by PROC_LOCK(p)
but freeing it is guarded by mtx_lock(Giant);
?
Call me naive, but shouldn't they be guarded by the same
Re: "Re: /dev/rtc not configured message when starting VMWare2 on -current"
In article [EMAIL PROTECTED],
Munehiro Matsuda [EMAIL PROTECTED] wrote:
I have a hack^Wpatch that should fix your problem.
I think you need to prevent returning the value of uninitialized
variable (``error'') when
I am trying to install one of the -current snapshots, but
current.freebsd.org doesn't seem to want to let me log in as anonymous
(some problem saying it cannot set guest access). Has the procedure
changed to get -current?
thanks
-j
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
Thanks
On Sun, 10 Feb 2002, Bruce Evans wrote:
Yes, anything that reaches doreti checks for ASTs and runs userret() if
necessary and possible (only for returns to user mode).
Hmm, this check seems to be inadequate for fast interrupts. There is
no check for rescheduling if the return is
On Thu, Feb 07, 2002 at 12:38 +0100, Søren Schmidt wrote:
[ snipped ATAPI - SCSI conversion ]
Doesn't burncd work for you on -current ?
Well, since you asked about it ... :)
Back in June I told you about the progress meter bogus
values in burncd and provided a patch in a private message
On Sun, 10 Feb 2002, Bruce Evans wrote:
On Fri, 8 Feb 2002, Julian Elischer wrote:
I'd like to commit the code to keep the ucred across userland,
with the code to clear it to NULL kept under DEBUG ifdefs.
i.e.
in trap(), ast() and syscall()
if (td-td_ucred !=
On Sat, 09 Feb 2002 10:54:06 -0800
Jason Nordwick [EMAIL PROTECTED] wrote:
I am trying to install one of the -current snapshots, but
current.freebsd.org doesn't seem to want to let me log in as anonymous
(some problem saying it cannot set guest access). Has the procedure
changed to get
No, the NFS server it depends on is down. Still working on getting it
back up.
I am trying to install one of the -current snapshots, but
current.freebsd.org doesn't seem to want to let me log in as anonymous
(some problem saying it cannot set guest access). Has the procedure
changed to
++ 09/02/02 10:54 -0800 - Jason Nordwick:
| I am trying to install one of the -current snapshots, but
| current.freebsd.org doesn't seem to want to let me log in as anonymous
| (some problem saying it cannot set guest access). Has the procedure
| changed to get -current?
There have been some
It seems Gerhard Sittig wrote:
On Thu, Feb 07, 2002 at 12:38 +0100, Søren Schmidt wrote:
[ snipped ATAPI - SCSI conversion ]
Doesn't burncd work for you on -current ?
Well, since you asked about it ... :)
I asked for *problems* not cosmetic issues :)
The bug (talking about a few
While attempting to ``fdisk fd0.1440''. Or ``fdisk fd0''. Or
``newfs_msdos fd0.1440'' with or without the floppy inside :-\
With todays or Jan 3rd kernel (my previous upgrade).
IdlePTD at phsyical address 0x004ed000
initial pcb at physical address 0x00411560
panicstr: bdwrite: buffer is not busy
On 09-Feb-02 Mikhail Teterin wrote:
While attempting to ``fdisk fd0.1440''. Or ``fdisk fd0''. Or
``newfs_msdos fd0.1440'' with or without the floppy inside :-\
With todays or Jan 3rd kernel (my previous upgrade).
Only use fdisk on hard disks. Still it shouldn't panic. The bdwrite is just
On Sat, 9 Feb 2002, Julian Elischer wrote:
On Sun, 10 Feb 2002, Bruce Evans wrote:
Yes, anything that reaches doreti checks for ASTs and runs userret() if
necessary and possible (only for returns to user mode).
Hmm, this check seems to be inadequate for fast interrupts. There is
no
On Sat, 9 Feb 2002, Julian Elischer wrote:
On Sun, 10 Feb 2002, Bruce Evans wrote:
On Fri, 8 Feb 2002, Julian Elischer wrote:
...
and in userret() and ast()
#ifdef DEBUG /*your choice of variable here*/
if (td-td_ucred != NULL) {
On Sat, 9 Feb 2002, John Baldwin wrote:
On 09-Feb-02 Mikhail Teterin wrote:
While attempting to ``fdisk fd0.1440''. Or ``fdisk fd0''. Or
``newfs_msdos fd0.1440'' with or without the floppy inside :-\
With todays or Jan 3rd kernel (my previous upgrade).
Only use fdisk on hard disks.
On Sun, 10 Feb 2002, Bruce Evans wrote:
On Sat, 9 Feb 2002, Julian Elischer wrote:
AST is not always called
and userret is always called, but unfortunatly sometimes multiple times
userret() isn't always called either in my version :-). When I'm
finished, it will never be called
On Sun, 10 Feb 2002, Bruce Evans wrote:
This is a well known bug in the device layer. I reported it on 2001/12/26
and fixed it locally a little later. See the thread in -current about
panic during fdisk'ing a md(4) device for patches.
Can you commit the fix?
To Unsubscribe: send
On Sat, 9 Feb 2002, Julian Elischer wrote:
On Sun, 10 Feb 2002, Bruce Evans wrote:
This is a well known bug in the device layer. I reported it on 2001/12/26
and fixed it locally a little later. See the thread in -current about
panic during fdisk'ing a md(4) device for patches.
Can
On Sat, 9 Feb 2002, Julian Elischer wrote:
On Sun, 10 Feb 2002, Bruce Evans wrote:
On Sat, 9 Feb 2002, Julian Elischer wrote:
AST is not always called
and userret is always called, but unfortunatly sometimes multiple times
userret() isn't always called either in my version :-).
In message [EMAIL PROTECTED], Bruce Evans writes:
On Sat, 9 Feb 2002, Julian Elischer wrote:
On Sun, 10 Feb 2002, Bruce Evans wrote:
This is a well known bug in the device layer. I reported it on 2001/12/26
and fixed it locally a little later. See the thread in -current about
panic
After comments by jhb and bde
--
++ __ _ __
| __--_|\ Julian Elischer | \ U \/ / hard at work in
| / \ [EMAIL PROTECTED] +--x USA\ a very strange
| ( OZ)\___ ___ |
On Sun, 10 Feb 2002, Bruce Evans wrote:
On Sat, 9 Feb 2002, Julian Elischer wrote:
On Sun, 10 Feb 2002, Bruce Evans wrote:
On Sat, 9 Feb 2002, Julian Elischer wrote:
AST is not always called
and userret is always called, but unfortunatly sometimes multiple times
I'm the maintainer for ports/editors/joe, and just tried compiling it under
-CURRENT.
signal.h includes sys/signal.h which includes ucontext.h
cc -O -pipe -c umath.c
In file included from b.h:6,
from bw.h:23,
from umath.c:5:
rc.h:41: conflicting types
29 matches
Mail list logo
