Hi
My P100 testbox running a fairly recent current just said:
May 27 23:39:23 p100 /kernel: vnode_pager: *** WARNING *** stale FS getpages
May 27 23:39:23 p100 /kernel: No strategy for buffer at 0xc13637e0
May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4,
writecount 0,
refcoun
As Wilko Bulte wrote ...
> As Doug Rabson wrote ...
> > On Sat, 15 May 1999, Wilko Bulte wrote:
> >
> > > As Doug Rabson wrote ...
> > > > On Mon, 10 May 1999, Wilko Bulte wrote:
> > > After a buildworld of yesterday's -current and a new kernel
As Doug Rabson wrote ...
> On Sat, 15 May 1999, Wilko Bulte wrote:
>
> > As Doug Rabson wrote ...
> > > On Mon, 10 May 1999, Wilko Bulte wrote:
> > >
> > > > >
> > > > > Yeah. That must be why my 164lx won't netboot.
> >
As Doug Rabson wrote ...
> On Mon, 10 May 1999, Wilko Bulte wrote:
>
> > >
> > > Yeah. That must be why my 164lx won't netboot.
> >
> > Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit
> > only) worked just dandy.
>
&g
As Mark Murray wrote ...
> Wilko Bulte wrote:
> > PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl
> > Writing Makefile for DynaLoader
> > ==> Your Makefile has been rebuilt. <==
> > ==> Please rerun the make command. <==
> > false
> > false: not
As Rodney W. Grimes wrote ...
> > Wilko Bulte wrote:
> > > PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl
> > > Writing Makefile for DynaLoader
> > > ==> Your Makefile has been rebuilt. <==
> > > ==> Please rerun the make command. <==
>
As Gianmarco Giovannelli wrote ...
>
> In 4.0-current sometimes the box will froze again after the :
> "Waiting 3 seconds for SCSI devices to settle"
> then nothing happens.
> It was a thing happened also in early 1999, before the branch in
> 4.0-current and 3.1 stable, if I remember well.
>
> An
As e...@habatech.no wrote ...
>
> On 12-May-99 Ustimenko Semen wrote:
> >
> > Are we going to get this license? I am interested in NTFS
> > source code a lot...
> >
> > P.S. What's happening with MS?
> >
> They have got a virus. I think they're calling it Open Source...
Na... it's called US
As Wilko Bulte wrote ...
> As Doug Rabson wrote ...
> > On Mon, 10 May 1999, Wilko Bulte wrote:
> >
> > > >
> > > > Yeah. That must be why my 164lx won't netboot.
> > >
> > > Could well be. My Aspen Alpine refused to with a DE500
As Doug Rabson wrote ...
> On Mon, 10 May 1999, Wilko Bulte wrote:
>
> > >
> > > Yeah. That must be why my 164lx won't netboot.
> >
> > Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit
> > only) worked just dandy.
>
&g
As Doug Rabson wrote ...
> On Sun, 9 May 1999, Wilko Bulte wrote:
>
> > As Doug Rabson wrote ...
> > > On Sun, 9 May 1999, Khaled Daham wrote:
> > >
> > > > Hello folks
> > > >
> > > > I cvsupped,made world, built a kernel to
As Kenneth D. Merry wrote ...
> Eric Hodel wrote...
> > "Kenneth D. Merry" wrote:
> > > So I'm a little confused here. Does camcontrol work? Try this:
> > >
> > > camcontrol devlist
> >
> > camcontrol: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for
> > device
> >
> > > camcontrol tu
As Chuck Robey wrote ...
> I was thinking about Peter Wemm's recent change to the kernel Makefile,
> making a way to install multiple kernels without fragging your last
> known good kernel, and it got me to thinking, scragging kernel.old, now
> that we have good kld's, isn't the only way to find yo
As Doug Rabson wrote ...
> On Sun, 9 May 1999, Khaled Daham wrote:
>
> > Hello folks
> >
> > I cvsupped,made world, built a kernel today and from now on the de
> > interfaces only comes up in 100BaseTX, what causes it not to negotiate ?
> > My Apr_29 kernel doesnt behave like this.
> >
> > The l
[ should we keep this on -current ?? ]
As Bob Willcox wrote ...
> On Fri, Apr 30, 1999 at 12:36:25AM +0200, Wilko Bulte wrote:
> > As Bob Willcox wrote ...
> > > On Thu, Apr 29, 1999 at 10:26:36PM +0200, Wilko Bulte wrote:
> > > > As Bob Willcox wrote ...
> >
As Bob Willcox wrote ...
> On Thu, Apr 29, 1999 at 10:26:36PM +0200, Wilko Bulte wrote:
> > As Bob Willcox wrote ...
> > > On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote:
> >
> > > shipping 8200's (this was right at their end-of-life) was
As Christopher T. Johnson wrote ...
> > On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote:
> > >
> > > Exabyte is not particularly famous for stable firmware.
> >
> > I have quite a number of 8200's here (though I don't really use them
>
As Bob Willcox wrote ...
> On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote:
> >
> > Exabyte is not particularly famous for stable firmware.
>
> I have quite a number of 8200's here (though I don't really use them
> much anymore since I now have a
As Christopher T. Johnson wrote ...
> > As Christopher T. Johnson wrote ...
> >
> > > REGARDLESS!
> > > The drive is reporting an error condition and that error is NOT
> > > getting back to user land. I've verified the problem with amdump
> >
> > Oh? Where/what is the error, does the console
As Christopher T. Johnson wrote ...
> REGARDLESS!
> The drive is reporting an error condition and that error is NOT
> getting back to user land. I've verified the problem with amdump
Oh? Where/what is the error, does the console tell you?
> amflush and dd. In ALL cases once
As Matthew Dillon wrote ...
> The amber LED on exabytes typically means 'drive needs cleaning'. Exabyte
> drives should be cleaned once or twice a week depending on how heavily
> you use them. If an exabyte drive is not cleaned on a regular basis, the
> transfer rate will drop st
As Christopher T. Johnson wrote ...
> Some extra information on tape problems:
>
> FreeBSD neunacht.netgsi.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Apr 22
> 16:50:33 EDT 1999 root@:/m/src/sys/compile/NEUNACHT i386
>
> This is SMP machine with scsi only.
>
> The tape drive is an EXABYTE-8200.
As Rick Whitesel wrote ...
> Hi:
> Just wanted to say that I think the lack of a free-for-all CVS is
> exactly what is required to consistently move FreeBSD forward. If someone
Free-for-all as in 'everybody can do commits' ?
This is a joke I hope. There already exists such a thing. It is call
As Warner Losh wrote ...
> In message <199904181923.naa25...@mt.sri.com> Nate Williams writes:
> : This is wonderful, but has this ever happened in our mailing lists? I
> : guess I don't remember anyone *ever* ridiculing or harassing someone for
> : not being fluent in the language.
>
> I have se
As Bob Bishop wrote ...
> I'm getting the 'blocks of NULLs in NFS-mounted files' problem repeatably
> with last night's -current (cvsup'd at Wed Apr 14 04:02:34 BST 1999)
> running both on server and client (except that the client's kernel is 24hrs
> older than that).
>
> It happens during a kern
As Luoqi Chen wrote ...
> > The kernel-configfile and dmesg-output is available from:
> > http://www.attic.ch/fuchur_kernel.html
> >
> > panic at: generic_bcopy+0x1arepe movsl (%esi), %es:(%edi)
> >
> > db> trace
> > generic_bcopy(c02cc380,c7bb9b1f,0,a,0) at generic_bcopy+0x1a
> > sccnputc(c
As Andreas Dobloug wrote ...
> * Kenneth D. Merry
> | > Has the worm driver been taken out of current?
> | Yes. You have to use cdrecord now for SCSI CD burners.
>
> cdrecord lacks support for a whole lot of CD-burners...
? Having just a while ago downloaded the latest cdrecord source
I'd say th
As David O'Brien wrote ...
> > Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o from
> > the EGCS source rather than our home-grown ones.
> ..snip..
> > I've made the same fix to lib/csu as I did libgcc, but now am getting
> > the same weird "install" problem Poul-Henning was ge
As Open Systems Inc. wrote...
> On Thu, 4 Feb 1999, Jaroslaw Bazydlo wrote:
>
> > After yesterdays 'make world' I am having such warnings:
>
> > ep0 XXX: driver didn't set ifq_maxlen
> > lo0 XXX: driver didn't set ifq_maxlen
> > ^
> > The system itself seems to
As Jordan K. Hubbard wrote...
> > Unfortunately the AXP is still hosed :(
>
> Hmmm. Let me look at this - I may have failed to adjust one of the
> constants for the AXP case.
Sidestepping a bit: will there be AXP specific CDROMs in the WC
CDROM distribution?
Wilko
_ ___
As David Wolfskill wrote...
> >From: Wilko Bulte
> >Date: Wed, 27 Jan 1999 23:12:18 +0100 (CET)
>
> >Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
> >just a matter of taste or is there more to it? I for one don't see any
> >adv
As Jordan K. Hubbard wrote...
> > How Mr. ignoromous Nate could construe this to mean that I was trying
> > to brush something under the rug is beyond me. As I said to Julian,
> > I probably shouldn't have made the committ, but the fact is that I
> > not only left the module on my
As Daniel O'Connor wrote...
> On 27-Jan-99 Wilko Bulte wrote:
> > > I agree.. and same thing goes for Ethernet drivers. I actually
> > > like the way Linux always has "eth0", "eth1", ... (which we could
> > Yeagh... what is wrong with ed0, de
As sth...@nethelp.no wrote...
> > > I agree.. and same thing goes for Ethernet drivers. I actually
> > > like the way Linux always has "eth0", "eth1", ... (which we could
> >
> > Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
> > just a matter of taste or is there more
As Archie Cobbs wrote...
> Doug Rabson writes:
> > And another thing. Why can't we use a non-driver-specific name for the
> > disk? Most users simply don't care whether the driver was fd, wfd, wd or
> > anything. They just want to get to their files without any fuss.
>
> I agree.. and same thin
As Alfred Perlstein wrote...
> 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:
As Matthew Dillon wrote...
> 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 comm
As Joao Carlos Mendes Luis wrote...
> #define quoting(Jordan K. Hubbard)
> // All: Sorry the boot.flp has been broken for this long, but I've had
> // other distractions lately. I will make it work once more, somehow
> // or other, and just keep your eyes on current.freebsd.org over
> // the next
As p...@originative.co.uk wrote...
> > -Original Message-
> > From: Peter Jeremy [mailto:peter.jer...@auss2.alcatel.com.au]
> > Sent: Wednesday, January 20, 1999 6:21 AM
> > To: freebsd-current@FreeBSD.ORG
> > Subject: Re: Directory structure on current.freebsd.org
> >
> >
> > Oliver From
As Andrey A. Chernov wrote ...
> What this means? What actions required?
> It was a problem recently which cause my kernel paniced
> after boot, but now I got this diagnostic instead of panic:
>
> /kernel: Waiting 2 seconds for SCSI devices to settle
> /kernel: Creating DISK da0
> /kernel: Creati
301 - 340 of 340 matches
Mail list logo
