I had exactly the same thing happen to /var on an SMP test box using
-current as of 16 May. It happened once out of about a half dozen panics.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, 17 May 2001, David Wolfskill wrote:
:(I see it does want the file system clean when soft updates is enabled,
:but doesn't check for that for a disable request.)
:
Right. fsck(8) can make assumptions about the state of the filesystem if it
knows that softupdates were in use. (There's a
>Date: Thu, 17 May 2001 22:30:03 -0500 (CDT)
>From: David Scheidt <[EMAIL PROTECTED]>
>Does tunefs update the alternate superblocks when it enables soft updates?
>It doesn't look it does, but I might be missing something.
I could easily have overlooked something myself, but it doesn't appear
to
In message <[EMAIL PROTECTED]> John Polstra writes:
: When booting GENERIC, the kernel probes most (all?) of the devices and
: gets to the point where it says, "Waiting 15 seconds for SCSI devices
: to settle." At that point it hangs solid. Keystrokes aren't echoed;
: scroll-lock doesn't work; C
On Thu, 17 May 2001, David Wolfskill wrote:
:>From: John Baldwin <[EMAIL PROTECTED]>
:
:>Hmm, that's odd, I did have soft updates on on /usr and /var before the crash.
:>It seems to be off now. :(
:
:That also happened to me. I thought it odd at the time, but forgot to
:mention it At least
In message <[EMAIL PROTECTED]> Szilveszter Adam writes:
: I think that cross-platform means compilation between i386 and alpha (and
: possibly others) not different OS's:-) (Although admittedly you can build
: Debian CDs on FreeBSD with linux emulation way better than you can build
: say a -STABLE
The GENERIC kernel in -current hangs on my ASUS P2B-S system, but my
custom kernel is OK. By trial and error I determined that removing
the "uhci" device from the GENERIC kernel makes it work. I don't know
how long this has been broken, because I don't normally use GENERIC.
I do know it was brok
In article <[EMAIL PROTECTED]>,
Brad Huntting <[EMAIL PROTECTED]> wrote:
>
> Suppose I'm a (root) process: I have an appointment in exactly
> one hour. I call select() and specify a timeout of 3600 seconds,
> trusting that the system will wake me up just in time. But
> unbeknownst to me someo
Looks OK to me.
In message <[EMAIL PROTECTED]>, "Sergey A. Osokin" writes:
>
>--9amGYk9869ThD9tj
>Content-Type: text/plain; charset=us-ascii
>Content-Disposition: inline
>
>On Fri, May 11, 2001 at 07:35:50PM +0200, Poul-Henning Kamp wrote:
>> In message <[EMAIL PROTECTED]>, "Sergey A. Osokin" wr
> The usual platform-independent way to do this is to have a thread
> that monitors the system clock. It wakes up every, say, 2 seconds
> and makes sure the clock is where it expects it. If the clock isn't
> what it expects, it does whatever you need to do in that case.
> I fear, however, that t
>Date: Thu, 17 May 2001 14:31:55 -0700 (PDT)
>From: John Baldwin <[EMAIL PROTECTED]>
>Has anyone else been trying out the background fsck?
A little; despite my desire to help debug things, getting to a point
where doing this is appropriate isn't something I am all too eager to do.
Thus, it wasn'
cvsup 17-5-2001
buildworld worked fine
make install failed with the following:
/usr/share/man/man1/tcsh.1.gz -> /usr/share/man/man1/csh.1.gz
===> bin/csh/nls
===> bin/csh/nls/finnish
install -c -o root -g wheel -m 444 tcsh.cat
/usr/share/nls/fi_FI.ISO_8859-1/tcsh.cat
ln -fs ../fi_FI.ISO_8859-1
Has anyone else been trying out the background fsck? Last night I was working
on the ithread code some and managed to panic my laptop while ejecting a pccard.
Anyways, the kernel ate itself while trying to flush its buffers and I ended up
with a dirty filesystem. I rebooted and let fsck -p do i
Robert Watson wrote:
> The last package build on current.FreeBSD.org seems to be from March 26th.
> Is there any chance we could get an updated package build for -CURRENT?
AFAIK there are some problems with bento's hardware. Contact Satoshi for more
details.
-Maxim
To Unsubscribe: send mail t
On Thu, May 17, 2001 at 05:37:54PM +0100, Brian Somers wrote:
> [cc'd to -arch and not to cvs-committers]
>
> For anyone that's reading -arch and hasn't seen this on -current, the
> thread is discussing userland sources that have -I../../sys in their
> Makefile and then #include .
>
> I think
The last package build on current.FreeBSD.org seems to be from March 26th.
Is there any chance we could get an updated package build for -CURRENT?
Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED] NAI Labs, Safeport Network Services
To Unsubscribe: se
[cc'd to -arch and not to cvs-committers]
For anyone that's reading -arch and hasn't seen this on -current, the
thread is discussing userland sources that have -I../../sys in their
Makefile and then #include .
I think everyone agrees that these headers should be made public, the
question is `
In message <[EMAIL PROTECTED]> Brian
Somers writes:
: Solaris calls it's ioctl files /usr/include/sys/_io.h so I'd
: spell digiio.h /usr/include/sys/digi_io.h.
Actually, the more I think about it, the more I like putting it in
/usr/include/sys/fooio.h. We have lots of other files there now. Th
In message <[EMAIL PROTECTED]> Brian Somers writes:
: Solaris calls it's ioctl files /usr/include/sys/_io.h so I'd
: spell digiio.h /usr/include/sys/digi_io.h.
We're not solaris :-). BSD traditionally spells things fooio.h for
driver foo. FreeBSD changed the traditional place for devices, so o
On Thu, 17 May 2001 07:11:16 -0500, Will Andrews <[EMAIL PROTECTED]> said:
> On Thu, May 17, 2001 at 06:36:01AM -0500, Michael Harnois wrote:
>> Are you telling me this error had something to do with
>> optimizations?
> No.
My point is that I knew that.
> However, in this
> > Most headers that define ioctls are in . I think there should
> > be at most one directory for ioctl headers and it shouldn't be a subdir
> > of /usr/include/sys (/usr/include/sys/dev doesn't even reflect the
> > kernel tree).
> >
> Might I guess it should probably be called /usr/include/sys
On Thu, May 17, 2001 at 08:14:10PM +1000, Bruce Evans wrote:
> On Wed, 16 May 2001, Warner Losh wrote:
>
> > In message <[EMAIL PROTECTED]> Brian Somers writes:
> > : How should this be done - and where should I install digiio.h if
> > : that's what's required ?
> >
> > I think that ppi device
On Thu, May 17, 2001 at 06:36:01AM -0500, Michael Harnois wrote:
> Are you telling me this error had something to do with optimizations?
No. But they can affect compiles in bizarre ways (believe me, in the
four years that I've compiled world, I've seen several).
If you compile with optimization
On Thu, May 17, 2001 at 01:21:38 -0700, Peter Wemm wrote:
> Import in progress. This will take a little while to complete, so any
> cvsups right at the wrong time (ie: in the next hour or so) will not
> survive a make world. I need to make some changes to the Makefiles.
> Once that is done, it s
> On Wed, 16 May 2001, Warner Losh wrote:
>
> > In message <[EMAIL PROTECTED]> Brian Somers writes:
> > : How should this be done - and where should I install digiio.h if
> > : that's what's required ?
> >
> > I think that ppi device sets the standard here. It installs into
> > /usr/include/de
On Thu, 17 May 2001 11:17:10 +0200, Sheldon Hearn <[EMAIL PROTECTED]> said:
> You're not supposed to report errors with world and kernel if
> you're using non-standard optimizations.
Are you telling me this error had something to do with optimizations?
--
Michael D. Harnois
It seems [EMAIL PROTECTED] wrote:
>Which ports break?
There are no other consumers (AFAIK) than atacontrol (yet)
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Which ports break?
Nick
On Thu, 17 May 2001, Søren Schmidt wrote:
>
> The ioctl to the ata driver has changed a bit, please
> make sure your kernel and userland are in sync.
>
> -Søren
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the me
The ioctl to the ata driver has changed a bit, please
make sure your kernel and userland are in sync.
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Wed, 16 May 2001, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Brian Somers writes:
> : How should this be done - and where should I install digiio.h if
> : that's what's required ?
>
> I think that ppi device sets the standard here. It installs into
> /usr/include/dev/ppi/ppi*.h. d
On 16 May 2001 20:47:05 EST, Michael Harnois wrote:
> cc -O2 -fno-strength-reduce -pipe -march=pentiumpro -DHAS_CGETENT -DENCRYPTION
>-DDES_ENCRYPTION -DAUTHENTICATION -DSRA
>-I/usr/src/secure/lib/libtelnet/../../../crypto/telnet
>-I/usr/obj/usr/src/i386/usr/include -c
>/usr/src/secure/lib
Peter Wemm wrote:
> Import in progress. This will take a little while to complete, so any
> cvsups right at the wrong time (ie: in the next hour or so) will not
> survive a make world. I need to make some changes to the Makefiles.
> Once that is done, it should be ok.
Unless I have missed somet
Import in progress. This will take a little while to complete, so any
cvsups right at the wrong time (ie: in the next hour or so) will not
survive a make world. I need to make some changes to the Makefiles.
Once that is done, it should be ok.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [E
Suppose I'm a (root) process: I have an appointment in exactly
one hour. I call select() and specify a timeout of 3600 seconds,
trusting that the system will wake me up just in time. But
unbeknownst to me someone sets the clock back 10 minutes while I'm
asleep (using settimeofday(), not adjtim
34 matches
Mail list logo
