Got this on an April 14 -CURRENT, while rebuilding a kernel:
panic: vm_page_alloc: free/cache page 0xc092fab8 was dirty
Debugger("panic")
Stopped at Debugger+0x44 pushl %ebx
db> trace
Debugger(c0412b7b) at Debugger+0x44
panic(c0432160,c092fab8,0,c8a98ca0,c7b1bce0) at panic+0x70
vm_page_a
I have a Dell Latitude CPi notebook, and recently ran into some nastiness
involving the boot process. The machine is using an April 24th world, and
up until now had been using an April 24th kernel. Leaving aside problems
with pcm hanging the kernel at boot, things seemed to work largely fine.
Note that you have to be careful to avoid the value of VNOVAL (-1) for a
uid or a gid, or you'll run into trouble with the VFS layer; this is
arguably due to poor design of VFS. NFSv2 also had problems with reserved
values (as the NFSv2 interface greatly resembles the VFS interface, for
the obvi
On Tue, 1 May 2001, Jordan Hubbard wrote:
> > Say, FreeBSD is usually pretty safe, even in CURRENT.
> > Has something near this magnitude of Really Bad Stuffage snuck into the
> > codebase before?
>
> No, it's not common, and it generally takes a Dane swinging something
> sharp to inflict quite
On Fri, 4 May 2001, J Wunsch wrote:
> Terry Lambert <[EMAIL PROTECTED]> wrote:
>
> > Isn't anyone but me and Walnut Creek cum BSDI cum Windriver
> > Systems using "make release"?!?
>
> We are, but why would we use anything else than GENERIC for it,
> seriously? I'd never roll a `release' for
On Fri, 4 May 2001, John Polstra wrote:
> In article <[EMAIL PROTECTED]>,
> Robert Watson <[EMAIL PROTECTED]> wrote:
> >
> > I think we can all take lessons from phk here -- he achieves a level of
> > destructiveness that makes even the pro's marvel
I just updated a box to a recent -CURRENT (first Thursday, then today),
and have been having the following problem for its serial console login:
FreeBSD/i386 (dev.TrustedBSD.org) (ttyd0)
gin: MK²aB"ÙÉÕÍÑ MzÉëËKaþ
FreeBSD/i386 (dev.TrustedBSD.org) (ttyd0)
gin: MJ²aB"ÙÉÕÍÑ MzÉëËKa
On Tue, 8 May 2001, John Baldwin wrote:
> That's easy enough. Well, it used to be at least. You can use 'ps' to
> find the address of the struct proc (first pointer in the display) and
> then do 'call psignal(addr, 9)' to send SIGKILL to the process. Then
> hit 'c' to continue and voila, the
On Wed, 9 May 2001, John Baldwin wrote:
> I am more worried about the fact that you can deadlock the debugger.
> What does the debugger do if another process hold the proc lock on the
> process you want to kill? Cute, eh? The debugger is an extra special
> environment. Most of the time you've
On Wed, 9 May 2001, Garrett Wollman wrote:
> < said:
>
> > I followed everything here fine until you asserted that the debugger
> > shouldn't need any locks.
>
> When the debugger is running, everything else should have been
> forcibly halted.
The process and signal-related structures may be
On Fri, 11 May 2001, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Bruce Evan
> s writes:
>
> >> Blame the poor design of mount(2) (and ask Adrian when he fixes
> >> it :-)
> >
> >It must be the excellent design of mount(2) that makes it so easy to
> >do things with it where it can
On Mon, 14 May 2001, Garrett Wollman wrote:
> < said:
>
> > The process and signal-related structures may be inconsistent if the
> > debugger disregards existing locks held over those structures. It does
> > not matter if code is currently still executing, it matters that
> > preemption can occ
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
I sent a similar crash trace to Kirk recently, and he claimed to have
fixed it (look for a commit crediting me as a source of information
sometime in the last few days). However, given the currently VM problems,
you'll want to pull in those FFS patches carefully :-). Since I'm 500
miles from th
I haven't made any mutex commits -- my commits were credential-related.
At least two bugs have popped up and been resolved since the pcred removal
commits, including:
1) Bug in execve() such that saved uids/gids were not being done in some
situations.
2) Bug in crfree() such that there was a
On Sun, 10 Jun 2001, Joerg Wunsch wrote:
> Joerg Wunsch <[EMAIL PROTECTED]> wrote:
>
> > It /only/ happens after a "mount -a", not after just mounting /tmp
> > only. No idea why, the only `obscure' filesystems i've got are procfs
> > and portalfs.
>
> portalfs indeed seems to be the culprit f
The only BSD-related NFSv4 work I know about is at:
http://www.citi.umich.edu/projects/nfsv4/download/
The amount of BSD-related information on the CITI NFSv4 page has gradually
diminished over time (that is, originally they proudly stated ports to
Linux and OpenBSD, and now they proudly sta
On Tue, 26 Jun 2001, Ruslan Ermilov wrote:
> Could someone please take a look at it before I commit this?
I won't get a chance to properly review this until I'm at USENIX tomorrow.
If you're willing to hold off for about a week, I'd be happy to give it a
fairly detailed review: I had some thoug
I reported this problem on the linprocfs and procfs modules a while back
while playing with a complete Linux environment under jail(). So clearly
we have a general problem among our synthetic file systems with regards to
the linux emulator (and possibly other emulators?)
Robert N M Watson
My only real observation is that with Protocol using (2) by default, my
logins to RELENG_4 boxes using RSA key authentication are broken. If I
stick a Protocol 1 in, it works fine, but it took me a bit to figure out
what was going on, and given that scp doesn't support -1, was a bit of a
pain. I
Yeah, I've been seeing that also with recent -CURRENT. /etc is in sync
with /usr/src/etc. Doesn't seem to prevent normal functioning, but isn't
encouraging. Looks like rootok needs to not whine when not running as
root?
Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAI
On Wed, 15 Aug 2001, Julian Elischer wrote:
> I ported the code to allow gcc to report functions that use too much
> of our 3.4KB kernel stacks.
Julian,
This is way cool stuff. I assume these are done based on i386 stack frame
layouts? Running on other platforms will result in different alig
On Mon, 27 Aug 2001, Bruce Evans wrote:
> How much faster (or slower) will it be for threaded programs (for
> various numbers of CPUs)? I don't see how it can be faster for a single
> CPU (interrupt threads in the kernel show that using threads tends to
> pessimize both efficiency and latency f
On Mon, 27 Aug 2001, Poul-Henning Kamp wrote:
> (phk-isms)
I found Poul-Henning's comments struck a chord with me. I agree with his
comments that a commit at this point would be premature, and that more
review is required. In particular, it seems like his observation that we
need additional e
On Mon, 27 Aug 2001, Matt Dillon wrote:
>Sheesh. Everyone is so negative! Well, I'm going to be too.
>
>I think compared to some of the other things that have been thrown into
>-current, the KSE stuff will be the LEAST disruptive. Don't go bashing
>Julian for coming up with a
On Wed, 29 Aug 2001, Garrett Wollman wrote:
> < said:
>
> > - I pushed the power button, and my system shut down cleanly!
>
> > Yes. ACPI brings some useful new features. 8)
>
> FSVO ``useful''. It's a real PITA to have to physically unplug the
> machine when the kernel is wedged rather th
As of this afternoon, I seem to be having problems with machines hanging
on incoming TCP connections. As soon as some process attempts to do
useful TCP stuff (incoming telnet, ssh, et al), all process hang. If I
break to ddb, a ps shows that telnetd has no wmesg. If I begin tapping on
various
On Tue, 5 Sep 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Wes Peters writes:
> : Ejecting an interface configured up will do that. ifconfig the interface
> : `down' and then `delete' before ejecting it.
>
> At best this is an unsatisfactory workaround. if_detach should cause
> t
On Fri, 28 Jul 2000, Brian Fundakowski Feldman wrote:
> On Fri, 28 Jul 2000, Robert Watson wrote:
>
> > Nope, it didn't appear to help. When I move the mouse around, it
> > intermitently pauses, perhaps once a second, for a short period of time.
>
> Robert, how
On Fri, 8 Sep 2000, John Baldwin wrote:
> Ok, an update on the dirty buffers on reboot:
>
> If you use the reboot command, you will get dirty buffers. If you use
> 'shutdown -r now' instead, you won't get dirty buffers. Thus, as a
> workaround for now, use the shutdown command to reboot your
On Sat, 9 Sep 2000, Brian Somers wrote:
> > Seigo Tanimura wrote:
> > >
> > > I have been suffering from this problem for almost 2 months. When I
> > > remove a pcmcia ethernet card from my laptop PC, routed(8) announces
> > > updated routing information by multicast, leading to a kernel
> > >
On Thu, 5 Oct 2000, Wesley Morgan wrote:
> I'm getting a panic in ufs_extattr_uepm_destroy() because in ffs_vfsops.c
> it is being called (line 788) with ump NULL:
>
> ufs_extattr_uepm_destroy(&ump->um_extattr);
>
> Of course disabling FFS_EXTATTR gets rid of this:)
Hmm. I added these change
On Fri, 6 Oct 2000, David O'Brien wrote:
> This has a KNF style problem. The line you remove should stay and
> "ump = VFSTOUFS(mp);" added.
Well, either way, it has to be moved further up in the function or you
dereference the NULL pointer. Bruce also pointed out the style problem,
and I'll
On Mon, 9 Oct 2000, Marc G. Fournier wrote:
> Well, I swear I have to be missing something here that is going to
> make me slap my forehead, but I can't get into single user mode :(
>
> I hit the space bar, type in 'boot -s' and it goes through all the
> normal start up procedures, s
On Sun, 29 Oct 2000, Manfred Antar wrote:
> From latest sources:
> cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
>-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
>-g -nostdinc -I- -I. -I../.. -I../../../include
>-I../../contrib/d
On Thu, 14 Sep 2000, Julian Elischer wrote:
> I've never thought of a use for fdescfs...
I used /dev/fd/1 just yesterday for a third-party precompiled binary
that insists on outputting to a file specified on the command line.
Slapping in /dev/fd/1 lets me stuff the command in a pipe chain. Same
Sending this to freebsd-stable or freebsd-current was somewhat of a
toss-up, but since I expect more committers hang out on -current than
-stable, here it is.
For the last few days (not sure when it started) I've been unable to build
-STABLE on a -CURRENT machine. This has proven a problem for
Driver developers!
As you probably know by now, Poul-Henning has enabled DEVFS in the GENERIC
kernel on FreeBSD 5.0-CURRENT. This is a strong feature and it's great to
see it getting brought back to life. However! Many of consumers of
make_dev() have chosen their default permissions somewhat
Updated to a recent -CURRENT yesterday on one of my boxes, and noticed a
slightly unusual shutdown message:
syncing disks... 8 8 5 5 1 1
done
Reclaim 8 0 Killed
Uptime: 10h23m28s
Rebooting...
Don't know what it means, or if it's harmful, but it's certainly different
:-).
Robert N M
Recently, I updated a box with an ISA Advansys controller card + HP CD
Burner to -CURRENT. On doing so, I discovered that my machine crashed at
boot due to a NULL pointer passed to free(). John Baldwin provided me
with a set of patches that appears to correct bugs in the Advansys (adv)
driver t
On 7 Feb 2001, Dag-Erling Smorgrav wrote:
> Brian Somers <[EMAIL PROTECTED]> writes:
> > Indeed. I've been doing a ``make build'' on an OpenBSD-current vm
> > for three days (probably about 36 hours excluding suspends) on a
> > 366MHz laptop with a ATA33 disk.
>
> Would it be possible for so
On 12 Feb 2001, Dag-Erling Smorgrav wrote:
> Jake Burkholder <[EMAIL PROTECTED]> writes:
> > As I mentioned in the commit message, this changes the size and layout
> > of struct kinfo_proc, so you'll have to recompile libkvm-using programs.
>
> I thought the whole point with kinfo_proc was to a
On Wed, 14 Feb 2001, Adrian Chadd wrote:
> *sigh* now, if we had per-file open vnode[1] support, I could quite
> happily solve this by fixing procfs, but people view procfs as bad for
> some reason.
>
> [1] Ignore my vagueness in terms here - the general request is to have
> some form of s
As has been pointed out, this is simply incorrect due to an attempt to use
kernel string operators on a string in the kernel address space. Generally
speaking, it's a bad idea to explicitly perform string activities on
userland strings, instead, to rely on the bounds checking in copyinstr()
and r
On Fri, 16 Feb 2001, Bruce Evans wrote:
> > What is it you're trying to accomplish here, exactly? Is it prevent paths
> > >MNAMELEN to be used as targets of mounting operations? Or is it to
> > truncate strings reported via statfs to some arbitrary bound? If it's the
>
> It is to not permit
On Thu, 25 Feb 2010, Giovanni Trematerra wrote:
Try to boot with GENERIC kernel.
I think this is no problem because SMP is already turned on in GENERIC
kernel.
yes, my fault, I copied the kernel config file from my other UP box. All is
well now.
In fact, my fault. I had a bug in three a
On Mon, 1 Mar 2010, FreeBSD Tinderbox wrote:
===> usr.bin/systat (all)
cc -O -pipe -DINET6 -std=gnu99 -Wno-pointer-sign -c /src/usr.bin/systat/cmds.c
cc -O -pipe -DINET6 -std=gnu99 -Wno-pointer-sign -c
/src/usr.bin/systat/cmdtab.c
In file included from /src/usr.bin/systat/extern.h:39,
On Thu, 4 Mar 2010, Xin LI wrote:
One good thing (in my opinion) that NetBSD and Darwin have is that they have
a "common" tree which holds the common files that shared between kernel and
userland libc. Currently we have 2 or more copies of certain files in the
tree but I'm not sure if it's a
On Thu, 4 Mar 2010, paradox wrote:
so, I really do not understand why it is so difficult to move a few folders
in the shared folder is a big problem as is done in openbsd and netbsd
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/?only_with_tag=MAIN
http://www.openbsd.org/cgi-bin/cvsweb/src/
On Fri, 5 Mar 2010, Poul-Henning Kamp wrote:
In message , Robert
Watso n writes:
Doing that kind of rearrangement [...] would be a nightmare for anyone with
large [...] patches, so I'd say we could pretty much rule that out
outright.
I would say that we should do it occasionally, to encou
On Fri, 5 Mar 2010, Alex Keda wrote:
On 05.03.2010 12:17, Robert Watson wrote:
consumers like Isilon, NetApp, Juniper, and many others
thus, it is not 'Free', this managed by 'consumers like Isilon, NetApp,
Juniper, and many others'?
These and other companies contrib
On Fri, 5 Mar 2010, Poul-Henning Kamp wrote:
In message , Robert
Watso n writes:
[...] it's that changes in layout come with a less visible but much larger
cost than "svn mv".
Really stupid question: Doesn't svn support symlinks ?
Yes, but does that help? The issue is not user applicati
On Fri, 5 Mar 2010, Alex Keda wrote:
thus, it is not 'Free', this managed by 'consumers like Isilon, NetApp,
Juniper, and many others'?
It might be helpful to think of them as 'customers' who are using our
'product' and paying for it by feeding back patches and employing FreeBSD
developers.
Dear all:
I'm embarking on some new network stack locking work, which requires me to
address a number of loose ends in the current model. A few years ago, my
attention was drawn to a largly theoretical race, which had existed in the BSD
code since inception. It is detected and handled in pr
On Sat, 6 Mar 2010, David O'Brien wrote:
No, not it isn't. Provide a script to convert path's in the diff. This is
what $LARGE_FREEBSD_USER did when it rearranged it source tree.
It was done by creating a copy of the CVS repo and moved files around. Old
releases stayed in the old repo, and
On Sun, 7 Mar 2010, Robert Watson wrote:
If your system shows a non-zero value, please send me a *private e-mail*
with the output of that command, plus also the output of "sysctl kern.smp",
"uptime", and a brief description of the workload and network interface
configu
On Mon, 8 Mar 2010, Doug Hardie wrote:
I run a number of 4 core systems with em interfaces. These are production
systems that are unmanned and located a long way from me. Under unusual
conditions it can take up to 6 hours to get there. I have been waiting to
switch to 8.0 because of the di
On Mon, 22 Mar 2010, Xin LI wrote:
A MFC of this update is planned, but we will have to make some rather
aggressive changes against the library and more testing.
Please make sure that you have at least libxml2-2.7.6_2 in your ports tree
before even thinking about updating your ports tree. Ol
On Fri, 2 Apr 2010, Alexander Leidinger wrote:
from r206082 on: $Subject
Make sure to read UPDATING (short: make sure there is no WITH_CTF in
src.conf or make.conf).
Once any fallout from this has sorted itself out, assuming no serious
objections, and pending appropriate make universe foo,
On Fri, 2 Apr 2010, Poul-Henning Kamp wrote:
The result of the RFC was that bind is not a mandatory component to make "a
usable system", so you argument suffers from bad logic.
With an eye on the date of Doug's suggestive e-mail, I actually am concerned
that we maintain support for DNSSEC va
On Mon, 5 Apr 2010, FreeBSD Tinderbox wrote:
cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
-Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc
-I. -I/src/sys -I/src
On Mon, 5 Apr 2010, Robert Watson wrote:
In file included from /src/sys/fs/coda/coda_fbsd.c:49:
/src/sys/fs/coda/cnode.h:97: error: expected specifier-qualifier-list
before 'CodaFid' /src/sys/fs/coda/cnode.h:199: error: expected ')' before
'*' token
Sorry all
On Mon, 26 Apr 2010, M. Warner Losh wrote:
I've read most of this thread. I think this is cool technology. However,
before we move forward with this, we need to have a plan for the various
issues that have come up. The plan needs to be specific, have owners for
key items, warnings about own
On Wed, 20 Jan 1999, Mike Smith wrote:
> > I was just pointing out that having things in subdirectories
> > is better than having a zillion files piled into a single directory.
>
> I'm torn between agreeing that it's tidier and disagreeing on the
> grounds that it's much more of a pain to admini
On Tue, 26 Jan 1999, RT wrote:
> I highly doubt that I'll ever use FORTRAN directly or indirectly. If it's
> not used by a vast majority, it should be optional...
So the problem seems to be that 'included in the system' is a problem
because the system gets unwieldy in terms of junk a lot of peo
I was wondering what the naming scheme for files in /usr/src/sys/kern was
:). There seem to be several sorts of files there--
bus_if.mdevice_.m imgact_*.c
inflate.c init_*.ckern_*.c
link_*.cmake*.{pl,sh} md5c.c
On Wed, 27 Jan 1999, Garrett Wollman wrote:
> < said:
>
> > It's not clear to me, when thinking of introducing a new file (say, for
> > auditing support :), what I should name it. Would it be kern_audit.c or
> > sys_audit.c?
>
> Depends on what it is auditing. If it only auditing the basic I/
. My kernel code is a few days old on the 4.0-CURRENT branch.
Source: auditd.c (just disable auditing stuff to make it compile). Invoke
as auditd /dev/mem.
/*-
* Copyright (c) 1999 Robert Watson
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
On Mon, 1 Feb 1999, Matthew Dillon wrote:
> Uh. Mm.. Hmm :-)
>
> i = read(fd, &size, sizeof(size));
> ... malloc(bufsize * sizeof(char))
> i = read(fd, buf, bufsize);
>
> When you are reading /dev/mem, 'size' can turn out to be anything.
> You are t
On Mon, 1 Feb 1999, Matthew Dillon wrote:
> :So this probably works for non-root users on files like /dev/zero that can
> :produce as much data as you might be interested in, suggesting a fun
> :denial of service attack for the bored and/or insane.
>
> Presumably the datasize limit can be use
I've been unable to buildworld for a day or so now, much to my
frustration. I've tried recvsuping my /home/ncvs, as well as rechecking
out, etc. I get the following:
cd /usr/src/lib/libskey; /usr/obj/usr/src/tmp/usr/bin/make all;
/usr/obj/usr/src
/tmp/usr/bin/make -B install
cc -pipe -DPERMIT_C
kernel code cvsup'd this morning, I believe.
FreeBSD sleipnir.watson.org 4.0-CURRENT FreeBSD 4.0-CURRENT #20: Mon Feb
22 11:53:53 EST 1999
rob...@sleipnir.watson.org:/usr/src/sys/compile/SLEIPNIR_AUDIT i386
panic(f01f13a7) at Debugger+0x37
worklist_remove(f0bd56a0) at worklist_remove+0x2a
free_di
Looks like it may actually have been triggered by a bug in my kernel
auditing code, which turned out to be doing stuff when I didn't think it
should have. Sorry about that :-).
On Mon, 22 Feb 1999, Robert Watson wrote:
> kernel code cvsup'd this morning, I belie
On Wed, 3 Mar 1999, SXren Schmidt wrote:
> It seems Daniel O'Connor wrote:
> >
> > On 02-Mar-99 SXren Schmidt wrote:
> > > Its in the works, together with the tagged queuing some of the
> > > newer drives supports.
> > Wow! :)
> >
> > Is there any chance od adding the ability to 'wire' devices
I get the following message from the zp0 driver on boot:
zp0 XXX: driver didn't set ifq_maxlen
lo0 XXX: driver didn't set ifq_maxlen
I assume they should be setting it? :-)
Robert N Watson
rob...@fledge.watson.org http://www.watson.org/~robert/
PGP key fingerprint: 03 01 DD 8E
So actually, I have a question about this. How is the syscall glue
generated, and when. Pretty much all the userland libraries call syscalls
using symbols of the same name rather than the syscall() wrapper,
presumably for performance and feasiability reasons (especially with
pipe()). When is th
So this is actually just a general response to the whole thing--one of the
things I actually dislike about rc.conf is its flexibility: the user can
put anything script-wise they like into it. My temptation would be to
reduce the flexibility: to have a simple name:value configuration file
(with app
On Wed, 10 Mar 1999 sth...@nethelp.no wrote:
> > Uh, no. Invariants are for developers who want to make sure their code
> > is correct. There is no reason why an end user would want to build a
> > kernel with invariants enabled. Invariants will *not* increase data
> > safety. If they have any effe
On Fri, 19 Mar 1999, Andrew McNaughton wrote:
> > Dmitry Valdov wrote:
> > > I think that there is only one way to fix it - it's to disable making
> > > *hard*links to directory with mode 1777.
>
> I don't use quotas, and don't know a great deal about how they operate,
> but I think there's anoth
On Tue, 24 Dec 2002, Poul-Henning Kamp wrote:
> Isn't there a pretty obvious race between the revoke() and the open() ?
>
> Wouldn't it in fact make much more sense if revoke(2) was defined as
>
> int revoke(int fd); /* kick everybody else off */
>
> and the code above would look like:
On Sat, 28 Dec 2002, Bruce Evans wrote:
> > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:932: (near initialization for
>`devfs_specop_entries[14]')
> > *** Error code 1
>
> This was broken by removing a unsed definition in:
>
> % RCS file: /home/ncvs/src/sys/kern/vnode_if.src,v
> % Worki
On Mon, 30 Dec 2002, Marc Butler wrote:
> I'm currently trying to build CURRENT (DEC 29 2002) within a chroot
> environment under CURRENT (DEC 17 2002). Presently I am stuck on an
> error which appears to be related to /dev/stdout in a chroot environment
> (devfs?).
Could you provide a bit mor
Juli Mallett pointed me at the following reproduceable problem on my
-current notebook with userland/kernel dated Dec 29:
paprika:~/freebsd/test/pthread> ./test
1
2
1
2
1
2
load: 0.02 cmd: test 910 [running] 0.00u 0.01s 0% 824k
1
Bus error (core dumped)
paprika:~/freebsd/test/pthread> ./test
1
2
On Sat, 4 Jan 2003, Juli Mallett wrote:
> * De: Robert Watson <[EMAIL PROTECTED]> [ Data: 2003-01-04 ]
> [ Subjecte: pthread ^T problem on recent -CURRENT: death in libc_r mutex ]
> >
> > Juli Mallett pointed me at the following reproduceable problem on my
&g
On Sat, 4 Jan 2003, Juli Mallett wrote:
> * De: Robert Watson <[EMAIL PROTECTED]> [ Data: 2003-01-04 ]
> [ Subjecte: pthread ^T problem on recent -CURRENT: death in libc_r mutex ]
> >
> > Juli Mallett pointed me at the following reproduceable problem on my
&g
While debugging the recent pthreads problem, I've started running into
this:
pid 663 (test), uid 1000: exited on signal 10 (core dumped)
failed to set signal flags properly for ast()
failed to set signal flags properly for ast()
failed to set signal flags properly for ast()
failed to set signal f
On Sun, 5 Jan 2003, Julian Elischer wrote:
> On Sun, 5 Jan 2003, Robert Watson wrote:
>
> >
> > Updating to Jan 4 kernel generates the same failure mode for me: following
>
> What makes you think it's the kernel?
Well, to be more precise, I upgraded the entire s
On Mon, 6 Jan 2003, Mike Barcroft wrote:
> These new truncated lines only make problems harder to solve.
>
> Anyway, the problem is the 5th argument to vn_extattr_get() should be an
> int *, but it's passing a size_t *. It looks like most consumers of
> vn_extattr_get() would prefer a size_t *
Sorry for a lack of details here, but -- sometime in the last few ACPI
imports (perhaps in the last three months), one of my test boxes began to
spew the attached message:
ACPI-1287: *** Error: Method execution failed, AE_AML_BUFFER_LIMIT
ACPI-1287: *** Error: Method execution failed, AE_
On Sat, 18 Jan 2003, Andy Farkas wrote:
> Some of observations of 5.0-RELEASE:
>
> 1/ Everytime I ssh to the box there are 4 connection attempts to UDP
> port 53 from itself. ie:
>
> Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53
>from 172.22.2.12:49205
> Jan 18 12:4
On Fri, 17 Jan 2003, Russell L. Carter wrote:
> rl0: discard oversize frame (ether type fbf7 flags 3 len 2992 > max 1514)
> rl0: discard oversize frame (ether type fbf7 flags 3 len 2992 > max 1514)
> rl0: discard oversize frame (ether type 2e3d flags 3 len 55442 > max 1514)
> rl0: discard oversiz
Next time you run fsck -y in this scenario, log the output to an md
partition and stick it somewhere for analysis. At least, that was the
moral of the story last time I hosed a box in this form (incidentally, I
think it ended up being a failing hard disk).
Robert N M Watson FreeBSD Co
On Tue, 28 Jan 2003, Enache Adrian wrote:
> On Mon, Jan 27, 2003 at 01:36:35PM -0800, Steve Kargl wrote:
> > Portions of the ext2fs source are covered by the GPL. You
> > need to rebuild the kernel with "option EXT2FS". The
> > FreeBSD cannot create a ext2fs.ko and comply with the GPL.
>
> Thi
On Tue, 28 Jan 2003, Andre Guibert de Bruet wrote:
> > I don't see it listed in 5.0-RELEASE ERRATA. Several people have now
> > reported problems with background fsck and in the case Kirk as
> > original author is loaded with other work I see no justification to
> > not mention the brokenness of
On Tue, 28 Jan 2003, Gerrit Kühn wrote:
> On Tue, Jan 28, 2003 at 12:34:25PM -0500, Robert Watson wrote:
>
> > Following reports of problems with bgfsck during the 5.0-RC series, and
> > prior to the release, I spent some time adding hard disks to machines,
> > resetting
On Thu, 30 Jan 2003, Craig Dooley wrote:
> Last cvsup/world/kernel is from around midnight last night, but noticed
> the problem yesterday. For a csi class I have to sort and uniq a file
> in c, and as a test case, I wrote a simple hex dump that respects
> newlines. No matter what I give it as
twork Associates Laboratories
-- Forwarded message --
Date: Thu, 30 Jan 2003 16:19:32 -0500
From: Craig Dooley <[EMAIL PROTECTED]>
To: Robert Watson <[EMAIL PROTECTED]>
Subject: Re: Recent current dies hard with simple program
That did it. When I took -pg out of CFLAGS the
On Thu, 30 Jan 2003, Julian Elischer wrote:
> On Thu, 30 Jan 2003, Julian Elischer wrote:
>
> > On Thu, 30 Jan 2003, Julian Elischer wrote:
> >
> > > hmm first I've heard of it but I'll check..
> > > (david's offline for a week)
&g
On Thu, 30 Jan 2003, David Vidal Rodríguez wrote:
> After some investigation, I come to the conclusion that there is no
> means to copy the extended attributes of a file by using standard
> commands like cp (even with the -p option) or mv. At least it works with
> mv if the rename(2) syscall is u
On Sat, 1 Feb 2003, Matthew Dillon wrote:
> sys/acl.h -- looks like the authors tried to use the underscore technique
> but forgot a couple.
Actually, the pattern is that the function prototypes exposed to userspace
are prefixed with '_' to prevent interfering with the appli
101 - 200 of 682 matches
Mail list logo
