On Fri, Aug 21, 2015 at 3:57 PM, Kevin Lo wrote:
> I hit this and poked bapt@ two weeks ago, he said he couldn't reproduce
> this problem...
>
> Kevin
>
Well seems three people just confirmed it exists might be a corner
case
>
> On Thu, Aug 20, 2015 at 08:29:32PM -0700, Adrian
I hit this and poked bapt@ two weeks ago, he said he couldn't reproduce
this problem...
Kevin
On Thu, Aug 20, 2015 at 08:29:32PM -0700, Adrian Chadd wrote:
>
> I just hit this; i'll hit up gjb@ about it.
>
>
> -a
>
>
> On 20 August 2015 at 19:04, Outback Dingo wrote:
> > On Fri, Aug
I just hit this; i'll hit up gjb@ about it.
-a
On 20 August 2015 at 19:04, Outback Dingo wrote:
> On Fri, Aug 21, 2015 at 11:30 AM, Allan Jude wrote:
>
>> On 2015-08-20 21:04, Keynes Augusto wrote:
>> >
>> >
>> >
>> > The ISO (r286893/r284969) does not create the folder / home or /usr/home
>>
On Fri, Aug 21, 2015 at 11:30 AM, Allan Jude wrote:
> On 2015-08-20 21:04, Keynes Augusto wrote:
> >
> >
> >
> > The ISO (r286893/r284969) does not create the folder / home or /usr/home
> and the user created during installation disappears.
> >
> > All files em skel disappears too.
> >
> > Sorry
On 2015-08-20 21:04, Keynes Augusto wrote:
>
>
>
> The ISO (r286893/r284969) does not create the folder / home or /usr/home and
> the user created during installation disappears.
>
> All files em skel disappears too.
>
> Sorry my english, i use Google for translate.
>
> Keynes Deus
>
>
The ISO (r286893/r284969) does not create the folder / home or /usr/home and
the user created during installation disappears.
All files em skel disappears too.
Sorry my english, i use Google for translate.
Keynes Deus
__
On Thu, Aug 20, 2015 at 03:26:10PM -0500, Mark Felder wrote:
>
>
> On Thu, Aug 20, 2015, at 06:50, Konstantin Belousov wrote:
> > On Wed, Aug 19, 2015 at 04:52:56PM -0500, Mark Felder wrote:
> > > panic: children list
> > > cpuid = 0
> > > KDB: stack backtrace:
> > > db_trace_self_wrapper() at db
Hi!
This has started happening on -HEAD recently. No, I don't have any
more details yet than "recently."
Whenever I get an NMI panic (and getting an NMI is a separate issue,
sigh) I get a slew of "failed to stop cpu" messages, and all CPUs
enter ddb. This is .. sub-optimal. Has anyone seen this?
[snip]
and if you're interested in doing some stuff with the scheduler and
interrupt handling then please poke jhb/i.
-adrian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send a
On Thu, Aug 20, 2015, at 15:26, Mark Felder wrote:
> >
> > diff --git a/sys/kern/kern_procctl.c b/sys/kern/kern_procctl.c
> > index d65ba5a..8ef72901 100644
> > --- a/sys/kern/kern_procctl.c
> > +++ b/sys/kern/kern_procctl.c
> > @@ -187,8 +187,6 @@ reap_status(struct thread *td, struct proc *p,
On Thu, Aug 20, 2015, at 06:50, Konstantin Belousov wrote:
> On Wed, Aug 19, 2015 at 04:52:56PM -0500, Mark Felder wrote:
> > panic: children list
> > cpuid = 0
> > KDB: stack backtrace:
> > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
> > 0xfe01228ea840
> > vpanic() at vpanic+
> On Aug 20, 2015, at 1:21 PM, Warner Losh wrote:
>
>
>> On Aug 20, 2015, at 10:32 AM, Dimitry Andric wrote:
>>
>> On 20 Aug 2015, at 18:24, Warner Losh wrote:
>>>
On Aug 20, 2015, at 9:38 AM, Oliver Pinter
wrote:
>> ...
>>>
>>> I think you are wrong about the cause. -mno-avx i
> On Aug 20, 2015, at 10:32 AM, Dimitry Andric wrote:
>
> On 20 Aug 2015, at 18:24, Warner Losh wrote:
>>
>>> On Aug 20, 2015, at 9:38 AM, Oliver Pinter
>>> wrote:
> ...
>>
>> I think you are wrong about the cause. -mno-avx is bogusly listed
>> unconditionally
>> in efi/Makefile.inc. I’m w
FreeBSD_HEAD-tests - Build #1303 - Fixed:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1303/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1303/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1303/console
Change summaries:
Andriy,
The problem can be reliably reproduced.
# If you can reproduce the problem reliably could you please test a patch
# from this review request https://reviews.freebsd.org/D3281 ?
# (https://reviews.freebsd.org/D3281?download=true)
# If I get a success report then I'll immediately commit the
On 08/20/2015 11:32, Dimitry Andric wrote:
> On 20 Aug 2015, at 18:24, Warner Losh wrote:
>>
>> I think you are wrong about the cause. -mno-avx is bogusly listed
>> unconditionally
>> in efi/Makefile.inc. I’m working on a patch now…
>
> Ah, this should be replaced with the recently introduced CF
On Thu, Aug 20, 2015 at 5:44 AM, Will Green wrote:
> Hello,
>
> I’ve been thinking about CPU performance and power management on FreeBSD
> recently. As a user it seems like there has been little activity in this area
> and I wanted to try and understand what the situation was.
>
> From the publi
On 20 Aug 2015, at 18:24, Warner Losh wrote:
>
>> On Aug 20, 2015, at 9:38 AM, Oliver Pinter
>> wrote:
...
>
> I think you are wrong about the cause. -mno-avx is bogusly listed
> unconditionally
> in efi/Makefile.inc. I’m working on a patch now…
Ah, this should be replaced with the recently
On 8/20/15, Warner Losh wrote:
>
>> On Aug 20, 2015, at 9:38 AM, Oliver Pinter
>> wrote:
>>
>> On 8/20/15, Dimitry Andric wrote:
>>> On 20 Aug 2015, at 00:56, Oliver Pinter
>>> wrote:
I got this error, when I try to build recent 11-CURRENT with gcc on
amd64
box:
--- del
> On Aug 20, 2015, at 9:38 AM, Oliver Pinter
> wrote:
>
> On 8/20/15, Dimitry Andric wrote:
>> On 20 Aug 2015, at 00:56, Oliver Pinter
>> wrote:
>>> I got this error, when I try to build recent 11-CURRENT with gcc on amd64
>>> box:
>>>
>>> --- delay.o ---
>>> cc -O2 -pipe -fPIC -mno-red-
On 8/20/15, Dimitry Andric wrote:
> On 20 Aug 2015, at 00:56, Oliver Pinter
> wrote:
>> I got this error, when I try to build recent 11-CURRENT with gcc on amd64
>> box:
>>
>> --- delay.o ---
>> cc -O2 -pipe -fPIC -mno-red-zone
>> -I/usr/data/source/git/opBSD/opBSD.git/sys/boot/efi/libefi/../
On 20 Aug 2015, at 00:56, Oliver Pinter wrote:
> I got this error, when I try to build recent 11-CURRENT with gcc on amd64 box:
>
> --- delay.o ---
> cc -O2 -pipe -fPIC -mno-red-zone
> -I/usr/data/source/git/opBSD/opBSD.git/sys/boot/efi/libefi/../include
> -I/usr/data/source/git/opBSD/opBSD.g
FreeBSD_HEAD-tests - Build #1302 - Still Unstable:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1302/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1302/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1302/console
Change su
Hello,
I’ve been thinking about CPU performance and power management on FreeBSD
recently. As a user it seems like there has been little activity in this area
and I wanted to try and understand what the situation was.
From the publicly available information on powerd [1], the wiki [2] and my
at
On Wed, Aug 19, 2015 at 04:52:56PM -0500, Mark Felder wrote:
> panic: children list
> cpuid = 0
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
> 0xfe01228ea840
> vpanic() at vpanic+0x189/frame 0xfe01228ea8c0
> kassert_panic() at kassert_panic+0x132/fra
Andriy Gapon wrote:
> On 20/08/2015 00:07, Jens Schweikhardt wrote:
> > Gang,
> >
> > for a few weeks now I can't get a CURRENT system to boot. I am using the
> > zfsloader and have root fs on ZFS. This has worked flawlessly for more
> > than a year.
> >
> > The last message printed is "Mountin
FreeBSD_HEAD-tests - Build #1301 - Still Unstable:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1301/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1301/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1301/console
Change su
On 20/08/2015 00:07, Jens Schweikhardt wrote:
> Gang,
>
> for a few weeks now I can't get a CURRENT system to boot. I am using the
> zfsloader and have root fs on ZFS. This has worked flawlessly for more
> than a year.
>
> The last message printed is "Mounting local file systems:" (from
> rc.d/mo
28 matches
Mail list logo