> Just suped and builded new kernel and discovered that it paniced when
> trying to initialise APM (VIA MVP3 based Tyan Trinity 100AT motherboard
> + k6-II/300 CPU). Any ideas or recommendations about what should I do to
> make a more informative report?
Just the usual ones; full text of the pani
In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes:
>David Scheidt <[EMAIL PROTECTED]> writes:
>> Six weeks, and no computer more sophisticated than the SCUBA one, are what
>> I remembered. Someone remind me what a vacation is again?
>
>des@flood ~% whatis vacation
>vacation(1) - return `
On Friday, 30 July 1999 at 9:31:15 +0200, Dag-Erling Smorgrav wrote:
> Jeroen Ruigrok/Asmodai <[EMAIL PROTECTED]> writes:
>> [note I already did chflags]
>> I'd love to hear some ideas about how to solve this.
>
> # chflags -R 0 /usr/obj/work
> # rm -rf /usr/obj/work
That doesn't seem to be the
Jeroen Ruigrok/Asmodai <[EMAIL PROTECTED]> writes:
> I'd love to hear some ideas about how to solve this.
# chflags -R 0 /usr/obj/work
# rm -rf /usr/obj/work
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the
"Marc Schneiders" <[EMAIL PROTECTED]> writes:
> > Are there any experiences at what time (UTC) the -current tree is most
> stable?
> I've had no problems so far some time after 0:00 h GMT, using the Dutch
> mirror. I suppose you use the German one. Perhaps that is updated more
> often.
Considerin
David Scheidt <[EMAIL PROTECTED]> writes:
> Six weeks, and no computer more sophisticated than the SCUBA one, are what
> I remembered. Someone remind me what a vacation is again?
des@flood ~% whatis vacation
vacation(1) - return ``I am not here'' indication
Apparently, it means he's not there.
>Look up a bit in the code. If bigenough is not true, cnp does not
>get initialized. This could lead to the bogus length -- or rather,
>it would be the cnp that is bogus, not the 'len'.
>
>The question is how to fix it. I think we can safely avoid doing the
>cache_enter so
On Friday, 30 July 1999 at 8:45:32 +0200, Jeroen Ruigrok/Asmodai wrote:
> Hi,
>
> I started a make world on my box last night and then proceeded to go to bed.
>
> When I looked at my console this morning it had sprung into DDB because
> of a panic: ffs_alloccg: map corrupted.
>
> This panic occur
Hi,
I was cleansing /usr/obj after a panic to see if I could reproduce it and
I have this slight oddity:
[root@daemon:/usr/obj] (32) # rm -rf work/
rm: work/FreeBSD/src/gnu/usr.bin/: Directory not empty
rm: work/FreeBSD/src/gnu: Directory not empty
rm: work/FreeBSD/src: Directory not empty
rm: w
Hi,
I started a make world on my box last night and then proceeded to go to bed.
When I looked at my console this morning it had sprung into DDB because
of a panic: ffs_alloccg: map corrupted.
This panic occured on a box running pretty stable (at least panic less for
the last past 4-8 weeks).
:Hm. Well, it cures the panic that I was experiencing quite nicely.
:I'm going to commit this latest patch for now since it fixes both
:the vnode locking problem and a crash condition, which are pretty
:serious problems. If you come up with something different, I'll be happy
:to try it out.
:
:No
:Is there any good documentation on the vnode system? I'd like to know, for
:instance, what the deal is with v{hold,drop}.
:
:Originally, I was most interested in doing things with networking. VFS
:seems so interesting now... Perhaps I should wait before experimenting
:with it until the rewrite o
Is there any good documentation on the vnode system? I'd like to know, for
instance, what the deal is with v{hold,drop}.
Originally, I was most interested in doing things with networking. VFS
seems so interesting now... Perhaps I should wait before experimenting
with it until the rewrite of lots
Of all the gin joints in all the towns in all the world, Matthew Dillon
had to walk into mine and say:
> Look up a bit in the code. If bigenough is not true, cnp does not
> get initialized. This could lead to the bogus length -- or rather,
> it would be the cnp that is bogus, not
:It's not hard. vput() VOP_UNLOCK()s a vnode and then vrele() (opposite of
:vref())'s it (decreases v_usecount, I believe.) So when a file system
:is mounted, with these bugs, the locked vnodes are never unlocked.
:The unmount call will end up sleeping with the state "vnlock" waiting for
:the ope
On Thu, 29 Jul 1999, Bill Paul wrote:
> > Ok, I was able to reproduce the above bug and fix it. The problem on
> > the FreeBSD client is in nfs_readdirplusrpc() in nfs/nfs_vnops.c. It
> > can obtain the vnode being used to populate the additional directory
> > info in one of t
:
:Close, but not quite. You didn't beat up on it hard enough. The secret
:is to think like a kid with a new toy, or more precisely, a sysadmin with
:a new toy (amounts to the same thing :). The first thing any sysadmin
:wants to do when you hand him a new gizmo is to push the buttons, turns
:the
:Crap, I just sent out an incomplete message. Let me pick up from where
:I left off. Here's a diff that shows the changes I made to nfs_vfsops.c:
:
:*** nfs_vnops.c.orig Thu Jul 29 22:46:28 1999
:--- nfs_vnops.cThu Jul 29 22:36:39 1999
:***
:*** 2342,2348
:
Crap, I just sent out an incomplete message. Let me pick up from where
I left off. Here's a diff that shows the changes I made to nfs_vfsops.c:
*** nfs_vnops.c.origThu Jul 29 22:46:28 1999
--- nfs_vnops.c Thu Jul 29 22:36:39 1999
***
*** 2342,2348
Of all the gin joints in all the towns in all the world, Matthew Dillon
had to walk into mine and say:
> :And here is something even scarier: readdirplus from the client side
> :doesn't appear to work correctly either. This time, you don't need an
> :IRIX machine to trigger the problem (though i
Malte Wedel <[EMAIL PROTECTED]> wrote on Thursday, July 29, 1999 3:59 PM
> I just wondered what time of the day is the best to do a cvsup, because it
> often happened to me, that I couldn't make world or compile the kernel
because
> of current work. Of course I know, that's why it's called -curren
:And here is something even scarier: readdirplus from the client side
:doesn't appear to work correctly either. This time, you don't need an
:IRIX machine to trigger the problem (though it helps :). Do the following
:
:client# mount -o nvsv3,tcp,rdirplus server:/somefs /mnt
:client# ls /mnt; du /m
Hello,
I just wondered what time of the day is the best to do a cvsup, because it
often happened to me, that I couldn't make world or compile the kernel because
of current work. Of course I know, that's why it's called -current, but there
should be a difference whether there are many people worki
Of all the gin joints in all the towns in all the world, Matthew Dillon
had to walk into mine and say:
> And here is something *really* scary. For the last month I've been
> running NFS over TCP without even realizing it. I had set up my
> machines to run NFS/TCP as a test instea
:
:Okay. I committed the fix to the length calculation to -current and
:-stable (I just love one-line patches that stop panics). I just got
:done patching my NFS server machines and they all seem to get along
:nicely with the SGI now. Now I can upgrade the other SGIs without
:worrying about them
Of all the gin joints in all the towns in all the world, Matthew Dillon
had to walk into mine and say:
> I think dirlen is supposed to be a calculation of the size of the
> struct dirent that the client will eventually synthesize from all
> of this, in order to ensure that the resu
:/*
: * If either the dircount or maxcount will be
: * exceeded, get out now. Both of these lengths
: * are calculated conservatively, including all
: * XDR overheads.
:
On Thu, 29 Jul 1999, Maxim Sobolev wrote:
> + k6-II/300 CPU). Any ideas or recommendations about what should I do to
> make a more informative report?
Maybe dmesg would be a good start...
Later,
--mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the b
Of all the gin joints in all the towns in all the world, Matthew Dillon
had to walk into mine and say:
> I counted it all up. It definitely needs to be 8 * NFSX_UNSIGNED.
Yes, I know that. :)
But what about the check for dirlen:
> :dirlen += (6 * NFSX_UNSIGNED + n
I counted it all up. It definitely needs to be 8 * NFSX_UNSIGNED.
See my count below.
-Matt
:In /sys/nfs/nfs_serv.c:nfsrv_readdirplus(), we have the following
:code:
:
:/*
: * If either the
Of all the gin joints in all the towns in all the world, Matthew Dillon
had to walk into mine and say:
> :Yes, we do. I've run into this problem elsewhere but a quick fix was needed
> :so it just got hacked. NT NFS clients tend to trigger it too.
> :
> :The problem is that the sanity check is
Just suped and builded new kernel and discovered that it paniced when
trying to initialise APM (VIA MVP3 based Tyan Trinity 100AT motherboard
+ k6-II/300 CPU). Any ideas or recommendations about what should I do to
make a more informative report?
Sincerely,
Maxim
To Unsubscribe: send mail to
On Thu, 29 Jul 1999, G. Adam Stanislav wrote:
> > Jordan, God, what's the difference?
> Jordan exists.
Enough childish neo-religious babble? May we return to our
regularly-scheduled, actually-FreeBSD-related discussions?
Thanks.
Later,
--mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
> Six weeks, and no computer more sophisticated than the SCUBA one, are what
> I remembered. Someone remind me what a vacation is again?
It's when you don't have to answer your own e-mail.
$ which vacation
/usr/bin/vacation
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
On Fri, 30 Jul 1999, Daniel C. Sobral wrote:
> Peter Holm wrote:
> >
> > Kirk seems to be out of touch :-), so I created PR kern/12869.
>
> I seem to recall a message from him last week saying he was going on
> a six weeks vacation. Well, he *did* said he was going on vacation,
> it's the "last
> I think, a guess, that make world without -DWANT_AOUT in conjunction with
Unless you are trying to support current development of a.out binaries,
there is little need to be useing "-DWANT_AOUT". All you want is suport
for existing 2.2.x a.out binaries (since that is what Netscape is).
Realize
* John Polstra ([EMAIL PROTECTED]) [990729 18:49]:
> Jeroen Ruigrok/Asmodai wrote:
> > Well, it seems to want libc.so.3.1 and that one is present in /usr/lib/aout
> > and is grepable from ldconfig -aout -r:
> >
> > [asmodai@daemon:/usr/home/asmodai] (3) $ ldconfig -aout -r | grep libc.so
> >
"G. Adam Stanislav" wrote:
>
> On Thu, Jul 29, 1999 at 11:25:44AM +0200, Dag-Erling Smorgrav wrote:
> > Jordan, God, what's the difference?
>
> Jordan exists.
Don't go there. This whole existance-of-perl-scripts thingy is
dangerous territory.
--
Daniel C. Sobral(8-DCS)
Peter Holm wrote:
>
> Kirk seems to be out of touch :-), so I created PR kern/12869.
I seem to recall a message from him last week saying he was going on
a six weeks vacation. Well, he *did* said he was going on vacation,
it's the "last week" and "six weeks" part I'm not 100% sure.
--
Daniel C.
On Thu, Jul 29, 1999 at 11:25:44AM +0200, Dag-Erling Smorgrav wrote:
> Jordan, God, what's the difference?
Jordan exists.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Kirk seems to be out of touch :-), so I created PR kern/12869.
--
Peter Holm | mailto:[EMAIL PROTECTED] | http://login.dknet.dk/~pho/
-[ Member of the BSD-Dk User Group / http://www.bsd-dk.dk/ ] -
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of
:Yes, we do. I've run into this problem elsewhere but a quick fix was needed
:so it just got hacked. NT NFS clients tend to trigger it too.
:
:The problem is that the sanity check is a fair way away from where the problem
:packet is generated. The bad reply is generated in the readdirplus routi
On Thu, Jul 29, 1999 at 08:46:52AM -0400, John W. DeBoskey wrote:
> Hi,
>
>The following seems to have slipped in over the last 24 hours. I'm
> probably the last to see it, and it may already be fixed, but I don't
> see any obvious commits:
>
> c++ -c -I/usr/obj/usr/src/tmp/usr/include/g++ -
Jeroen Ruigrok/Asmodai wrote:
> * Matthew Dillon ([EMAIL PROTECTED]) [990729 07:20]:
>> lib/libc.so.3: minor version -1 older
>> :> than expected 0, using it anyway
>> :> ld.so failed: bad magic number in "/usr/lib/libc.so.3"
Look, it's finding its library in "/usr/lib" and it shouldn't be doing
Hi,
The following seems to have slipped in over the last 24 hours. I'm
probably the last to see it, and it may already be fixed, but I don't
see any obvious commits:
c++ -c -I/usr/obj/usr/src/tmp/usr/include/g++ -O -pipe
-I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config
-I/usr/src/
Dag-Erling Smorgrav wrote:
>
> Jordan, God, what's the difference?
God does not belong to the -core.
--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
"Is it true that you're a millionaire's son who never worked a day
in your life?"
"Yeah, I
Try sending the command to [EMAIL PROTECTED]
Nick
On Thu, 29 Jul 1999, Joachim Kuebart wrote:
> unsubscribe
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
>
--
ISIS/STA, T.P.270, Joint Research Centre, 21020
"Daniel C. Sobral" <[EMAIL PROTECTED]> writes:
> Garrett Wollman wrote:
> > Jordan stopped including CVS directories in the /usr/ports tarball.
> I don't think a transfer rate can be affected by that, though the
> total transfer time certainly would.
The transfer rate measured by sysinstall inclu
unsubscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
"Jordan K. Hubbard" <[EMAIL PROTECTED]> writes:
> The CVS metadata was removed, reducing the inode count per port significantly.
> This results in faster extraction time and hence "faster" downloads, assuming
> that extraction time is the bottleneck (which it is for all but the 28K and
> below dow
Peter Jeremy <[EMAIL PROTECTED]> writes:
> You'll also need the a.out X11 libraries, and last time I tried,
> they built OK, but wouldn't work.
They build OK and work fine.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-
I don't think this is a new problem. I recall a similar error being
mentioned on the -stable mailing list last week.
If you can repeat the error, please write down the program counter
value. Knowing the instruction at which the fault occurs would
be most valuable.
Alan
To Unsubscribe: send
On Wed, 28 Jul 1999, Garrett Wollman wrote:
> < said:
>
> > Add support for SYS_RES_DENSE and SYS_RES_BWX resource types. These are
> > equivalent to SYS_RES_MEMORY for x86 but for alpha, the rman_get_virtual()
> > address of the resource is initialised to point into either dense-mapped
>
53 matches
Mail list logo
