After reviewing the man page, if you use 'screen -ln' you will NOT see
the error.
It's a utmp log issue.
Also, the reason why this happened to me is because chflags were set to:
# chflags sappnd /var/log
# chflags sappnd /var/log/*
(Safe to keep this permission drwxr-x--- log 'which i have min
Am 10/07/12 17:20, schrieb Konstantin Belousov:
> Please find below the patch to add the unwind annotations for the libc
> and libthr assembler routines on amd64. The change shall have no impact
> on the execution of the changed code, because no functions there ever
> generate C++ exception or call
David and Michael,
can you please build a kernel with attached patch and options KDB,
and report what's the trace is.
Unfortunately my iwn(4) is running on amd64, so I can reproduce
exactly your case.
--
Totus tuus, Glebius.
Index: i386/i386/in_cksum.c
On 10/7/12 8:02 AM, Luigi Rizzo wrote:
Coming to 802.11 (and I am using it just as an example):
configuration of the various parameters is not too different from,
say, manipulating the various features that are available in modern
NICs: interrupt mitigation, queue parameters, multiqueue support,
On Sun, Oct 07, 2012 at 01:51:20PM -0400, Michael Butler wrote:
M> On 10/07/12 13:03, Garrett Cooper wrote:
M> > Maybe these revisions had something to do with it... (r241245 is
M> > more likely)?
M>
M> I reverted r241245 and the messages went away,
I'll handle that. Sorry for breakage.
--
On Sun, Oct 7, 2012 at 10:51 AM, Michael Butler
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 10/07/12 13:03, Garrett Cooper wrote:
>> Maybe these revisions had something to do with it... (r241245 is
>> more likely)?
>
> I reverted r241245 and the messages went away,
>
>>
On Sun, Oct 7, 2012 at 10:43 AM, David Wolfskill wrote:
> On Sun, Oct 07, 2012 at 10:03:04AM -0700, Garrett Cooper wrote:
>> ...
>> Maybe these revisions had something to do with it... (r241245 is
>> more likely)?
>>
>>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/07/12 13:03, Garrett Cooper wrote:
> Maybe these revisions had something to do with it... (r241245 is
> more likely)?
I reverted r241245 and the messages went away,
> Did you rebuild all of your modules, and (for David) are you
> runnin
On Sun, Oct 07, 2012 at 01:05:21PM -0400, Justin Hibbits wrote:
> On Sun, 07 Oct 2012 10:16:40 -0600
> Ian Lepore wrote:
>
> > On Sun, 2012-10-07 at 17:53 +0200, Luigi Rizzo wrote:
> > > Access through sysctl is incredibly easy from both userspace and
> > > from a C application, because all the w
warning: total configured swap (2621440 pages) exceeds maximum
recommended amount (1852656 pages).
...
This is because kernel needs some memory to manage swap too.
Currently for amd64 this roughly reduces to the following rule
(My apologies in advance for the extra simplification):
100MB RAM
On Sun, Oct 07, 2012 at 10:03:04AM -0700, Garrett Cooper wrote:
> ...
> Maybe these revisions had something to do with it... (r241245 is
> more likely)?
>
>
> r241245 | glebius | 2012-10-06 03:02:11 -0700 (Sat, 06 Oct 201
On Sun, 07 Oct 2012 10:16:40 -0600
Ian Lepore wrote:
> On Sun, 2012-10-07 at 17:53 +0200, Luigi Rizzo wrote:
> > Access through sysctl is incredibly easy from both userspace and
> > from a C application, because all the work is done in the kernel
> > side, whereas other mechanisms (ioctl, i'd rat
On Sun, Oct 7, 2012 at 9:16 AM, Michael Butler
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 10/07/12 11:11, David Wolfskill wrote:
>> I started seeing these messages spewed (to both console &
>> /var/log/messages) following an update from:
>>
>> FreeBSD g1-227.catwhisker.org 10.
On Sun, 2012-10-07 at 17:53 +0200, Luigi Rizzo wrote:
> Access through sysctl is incredibly easy from both userspace and
> from a C application, because all the work is done in the kernel
> side, whereas other mechanisms (ioctl, i'd rather leave kvm apart
> as we really don't want that!) require th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/07/12 11:11, David Wolfskill wrote:
> I started seeing these messages spewed (to both console &
> /var/log/messages) following an update from:
>
> FreeBSD g1-227.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #697 241222M:
> Fri Oct 5 05:32:
On Sun, Oct 07, 2012 at 08:23:23AM -0700, Garrett Cooper wrote:
> On Sun, Oct 7, 2012 at 8:02 AM, Luigi Rizzo wrote:
...
> FWIW, I don't think that the problem is necessarily the fact that one
> should do it either via ioctl, kvm, sysctl, etc: having a library/set
> of interfaces as Adrian suggest
On Sun, Oct 7, 2012 at 8:02 AM, Luigi Rizzo wrote:
> [subject changed due to the shift of topic]
>
> On Sun, Oct 07, 2012 at 07:08:54AM -0700, Adrian Chadd wrote:
>> On 7 October 2012 03:43, Luigi Rizzo wrote:
>> >
>> > Good point, thanks for mentioning this:
>>
>> ew. ifconfig :-)
>>
>> >
>> >
Please find below the patch to add the unwind annotations for the libc
and libthr assembler routines on amd64. The change shall have no impact
on the execution of the changed code, because no functions there ever
generate C++ exception or call a function that could generate exception.
The addition
> > Seconded; but compare to Linux which has mutiple different commands to
> > do networking, as well as 'net'. :-)
>
> we do too -- we have arp, route, ifconfig, sysctl and possibly
> more that i am not aware of.
Note that at least arp, route and ifconfig have been there since very
early BSD rel
I started seeing these messages spewed (to both console &
/var/log/messages) following an update from:
FreeBSD g1-227.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #697 241222M:
Fri Oct 5 05:32:19 PDT 2012
r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386
to
FreeBSD g1-227.c
[subject changed due to the shift of topic]
On Sun, Oct 07, 2012 at 07:08:54AM -0700, Adrian Chadd wrote:
> On 7 October 2012 03:43, Luigi Rizzo wrote:
> >
> > Good point, thanks for mentioning this:
>
> ew. ifconfig :-)
>
> >
> > Could be done, but I consider the ifconfig one of the ugliest
>
On 7 October 2012 03:43, Luigi Rizzo wrote:
>
> Good point, thanks for mentioning this:
ew. ifconfig :-)
>
> Could be done, but I consider the ifconfig one of the ugliest
> configuration mechanisms we have in FreeBSD so I'd rather not
> contribute to that.
Seconded; but compare to Linux which
On Sunday 07 October 2012 12:42:11 Hans Petter Selasky wrote:
> On Sunday 07 October 2012 01:42:33 Jin Guojun wrote:
> > 1) moused stops functioning on 9.1-RC2. Neither PS2 nor USB mouse can
> > work.
> >
> > 9.1-RC1 has no such problem.
> >
> > 2) All i386 / amd64 of 9.1-RC1/RC2 have USB rea
On Sunday 07 October 2012 01:42:33 Jin Guojun wrote:
> 1) moused stops functioning on 9.1-RC2. Neither PS2 nor USB mouse can work.
> 9.1-RC1 has no such problem.
>
> 2) All i386 / amd64 of 9.1-RC1/RC2 have USB read failure -- see dmesg
> output at end of this email.
> ada0 is internal SATA dri
On Sun, Oct 07, 2012 at 12:57:42PM +1300, Andrew Thompson wrote:
> On 7 October 2012 06:28, Luigi Rizzo wrote:
> > Hi,
> > in order to control some netmap feature (namely, which interfaces
> > are attached to VALE switches), i would considering the use of
> > a sysctl interface triggering a sysctl
25 matches
Mail list logo
