Thanks,
--
Jos Backus [EMAIL PROTECTED]
WebTV Networks, Inc., Mountain View, CA
I can confirm that on my system with world built from sources cvsuped on
Sunday and a kernel just built from sources cvsuped today, I see these
messages with an mfs mounted /tmp.
Hmm. They went away for me-
A little context
CROSSENV= MAKEOBJDIRPREFIX=${OBJTREE} \
COMPILER_PATH=${WORLDTMP}/usr/libexec:${WORLDTMP}/usr/bin \
LIBRARY_PATH=${WORLDTMP}${SHLIBDIR}:${WORLDTMP}/usr/lib \
OBJFORMAT_PATH=${WORLDTMP}/usr/libexec \
Warning:
Do not use IBM Microdrives in any USB based CF II readers, like the
SmartMedia ImageMate until further notice. I've had reports of 2 drives
breaking in a SmartMedia ImageMedia. They are PHYSICALLY broken and will
no longer work.
Nick
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Hi Brian,
Does this have anything to do with your recent change to if_tun.c?
Ciao,
Sheldon.
Script started on Wed Jul 26 12:28:35 2000
# pwd
/root
# date
Wed Jul 26 12:28:39 SAST 2000
# uname -a
FreeBSD axl.ops.uunet.co.za 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Jul 26 12:01:00
SAST 2000
On Wed, 26 Jul 2000 12:33:07 +0200, Sheldon Hearn wrote:
Does this have anything to do with your recent change to if_tun.c?
Nope. I've reverted rev 1.75 of if_tun.c and the behaviour persists.
Someone locally insists that the ifconfig line
ifconfig tun0 inet 10.0.0.1
should work.
[This email is an update of Hong Kong government's Workplace English Campaign,
and of Wall Street Institute English specials for July. If you wish to be removed,
or are not in Hong Kong, please click on [EMAIL PROTECTED]].
The Workplace English Campaign of the Hong Kong government is now in
Hi Kirk,
On Tue, 25 Jul 2000 11:28:47 MST, Kirk McKusick wrote:
Modified files:
sys/kern vfs_bio.c
Log:
Now that buffer locks can be recursive, we need to delete the panics
that complain about them.
This looks related. I get it pretty consistently on shutdown,
I've already introduced before (last Auguest), but here it is again;
we have updated our service host and add some services.
current.jp.freebsd.org (CAUTION: not 'current.freebsd.org') is a yet
another daily SNAPSHOTs service host. Service contents are almost the
same of current.freebsd.org
Mahtew Jacob wrote:
Hmm. They went away for me- I thought, but no, you're right. They're
still
there. This is what I actually use to get rid of them:
Index: mfs_vnops.c
===
RCS file: /home/ncvs/src/sys/ufs/mfs/mfs_vnops.c,v
Sheldon Hearn wrote:
On Wed, 26 Jul 2000 12:33:07 +0200, Sheldon Hearn wrote:
Does this have anything to do with your recent change to if_tun.c?
Nope. I've reverted rev 1.75 of if_tun.c and the behaviour persists.
Someone locally insists that the ifconfig line
ifconfig tun0
Bill Fumerola wrote:
STRICTTMPPATH= ${WORLDTMP}/usr/sbin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games
INSTALLTMP= ${TMPDIR}/install.${TMPPID}
IMAKEENV= ${CROSSENV} \
PATH=${STRICTTMPPATH}:${INSTALLTMP}
installkernel:
cd ${KRNLOBJDIR}/${INSTALLKERNEL}; \
On Wed, Jul 26, 2000 at 08:56:03AM -0700, Marcel Moolenaar wrote:
Now, why are we looking in ${WORLDTMP}/usr/sbin when what we should be
looking in is ${WORLDTMP}/usr.sbin? Same with /usr/bin != /usr.bin...
WORLDTMP is a place to *install* binaries we made during the build. We
don't
Bill Fumerola wrote:
WORLDTMP is a place to *install* binaries we made during the build. We
don't install in /usr.bin or /usr.sbin; we install in /usr/bin and
/usr/sbin resp.
And then we try and install the kernel using those utilties that are in
directories that don't exist:
On Wed, Jul 26, 2000 at 10:02:40AM -0700, Marcel Moolenaar wrote:
Make sure you have /usr/src/Makefile.inc1 rev 1.162 or up. The
installkernel was using the wrong buildcontext (ie IMAKEENV). IMAKEENV
was changed to have the very restricted path that broke the
installkernel target as you
Somebody send it to Kirk
On Wed, 26 Jul 2000, George W. Dinolt wrote:
Mahtew Jacob wrote:
Hmm. They went away for me- I thought, but no, you're right. They're
still
there. This is what I actually use to get rid of them:
Index: mfs_vnops.c
On Wed, 26 Jul 2000, Sheldon Hearn wrote:
Hi Kirk,
On Tue, 25 Jul 2000 11:28:47 MST, Kirk McKusick wrote:
Modified files:
sys/kern vfs_bio.c
Log:
Now that buffer locks can be recursive, we need to delete the panics
that complain about them.
This
How does OpenBSD handle this issue? Anyone know?
--
Ben
220 go.ahead.make.my.day ESMTP Postfix
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Because there is no write-only hardware page protection on ia32,
a write-only page fault is handled just like a read/write one.
But the mi vm layer distinguishes between the write-only and the
read/write protections, so if the fault takes place in a write-only
region, the vm layer would think
On Wed, 26 Jul 2000, void wrote:
How does OpenBSD handle this issue? Anyone know?
It looks like they have four different kernel-exported random-number
generators:
#define RND_RND 0 /* real randomness like nuclear chips */
#define RND_SRND1 /* strong random source
[This is with yesterdays' -current and today's kernel, and Xfree86 4.0.1 using
the ati driver module.]
Something I noticed today: switch to text console from X using C-A-F1; upon
return, the mouse cursor is frozen. moused appears to still work because I
can cut/paste text in the text console.
On Wed, Jul 26, 2000 at 03:53:15PM -0700, Jos Backus wrote:
[This is with yesterdays' -current and today's kernel, and Xfree86 4.0.1 using
the ati driver module.]
Something I noticed today: switch to text console from X using C-A-F1; upon
return, the mouse cursor is frozen. moused appears
On Thu, 27 Jul 2000, Benedikt Schmidt wrote:
On Wed, Jul 26, 2000 at 03:53:15PM -0700, Jos Backus wrote:
[This is with yesterdays' -current and today's kernel, and Xfree86 4.0.1 using
the ati driver module.]
Something I noticed today: switch to text console from X using C-A-F1; upon
There was a patch floating around which fixed these mouse problems for me.
XFree86-patch
This is at current -current, softupdates. Panic happens at reboot, from
sync() kernel function:
panic: lockmgr: pid 1, not exlusive lock holder 0 unlocking
--
Andrey A. Chernov
[EMAIL PROTECTED]
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
I already mentioned it
On Thu, 27 Jul 2000, Andrey A. Chernov wrote:
This is at current -current, softupdates. Panic happens at reboot, from
sync() kernel function:
panic: lockmgr: pid 1, not exlusive lock holder 0 unlocking
--
Andrey A. Chernov
[EMAIL PROTECTED]
I saw the exact same error today (just happened to be scanning this mailing list) with
4.1-STABLE after a panic.
Original message from: Matthew Jacob
panic: lockmgr: pid 1, not exlusive lock holder 0 unlocking
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current"
26 matches
Mail list logo
