Please forgive the crosspost, I don't know where the problem actually
belongs.
For the last several months I've had a problem where doing a buildworld
on FreeBSD CURRENT running as a virtualbox guest is crashing a the
FreeBSD current host.
This doesn't always happen, but there is a pattern. The
On 2019-09-24 15:09, Ian Lepore wrote:
>
> On my system, a whole lotta stuff happens between ntpd and syscons (the
> thing that configures blanktime). Try setting rc_debug=YES in rc.conf,
> that should write more info to syslog about what's happening between
> ntpd and the lockup point.
>
Ian:
I
On Sat, Sep 21, 2019 at 08:43:58PM -0400, Ryan Stone wrote:
> I have written a short test program that runs unlinkat(2) in
> capability mode and fails due to not having the write capabilities:
>
> https://people.freebsd.org/~rstone/src/unlink.c
>
> If I run the binary under ktrace and look at the
On 9/25/19 8:00 AM, c...@riseup.net wrote:
> On Wed, Sep 25, 2019 at 09:28:49AM -0500, Valeri Galtsev wrote:
>>
>> On 2019-09-25 01:04, Kevin Oberman wrote:
>>> On Tue, Sep 24, 2019 at 8:56 PM wrote:
>>>
developed
Reply-To:
X-Priority: 1
Importance: high
Disposition-Noti
From: Yasuhiro KIMURA
Subject: Re: panic: sched_pickcpu: Failed to find a cpu.
Date: Thu, 26 Sep 2019 00:12:48 +0900 (JST)
>> Yes; mav@ fixed it with r352677.
>
> Thanks. I'll update source tree and rebuild kernel.
I updated kernel to r352685 and now system boots successfully.
---
Yasuhiro KIM
Had verbose on and got the following kernel error on 290:
taskqgroup_adjust_if_config_tqg: panic: sched_pickcpu: failed to find a cpu
Looked for device tqg, isn't available in a slightly changing GENERIC custom.
I know what this personally means to me, incompatibility and a lack of social
i
From: David Wolfskill
Subject: Re: panic: sched_pickcpu: Failed to find a cpu.
Date: Wed, 25 Sep 2019 08:08:15 -0700
> Yes; mav@ fixed it with r352677.
Thanks. I'll update source tree and rebuild kernel.
Regards.
---
Yasuhiro KIMURA
___
freebsd-curre
On Wed, Sep 25, 2019 at 11:44:51PM +0900, Yasuhiro KIMURA wrote:
> yasu@rolling-vm-freebsd1[2001]% uname -a
> ~
> FreeBSD rolling-vm-freebsd1.home.utahime.org 13.0-CURRENT FreeBSD
> 13.0-CURRENT r352351 GENERIC amd
On Wed, Sep 25, 2019 at 09:28:49AM -0500, Valeri Galtsev wrote:
>
>
> On 2019-09-25 01:04, Kevin Oberman wrote:
> > On Tue, Sep 24, 2019 at 8:56 PM wrote:
> >
> > > developed
> > > Reply-To:
> > > X-Priority: 1
> > > Importance: high
> > > Disposition-Notification-To:
> > > X-Confirm-Reading-T
yasu@rolling-vm-freebsd1[2001]% uname -a
~
FreeBSD rolling-vm-freebsd1.home.utahime.org 13.0-CURRENT FreeBSD 13.0-CURRENT
r352351 GENERIC amd64
After update to r352669, boot fails as following.
https://www.utahim
On Wed, Sep 25, 2019 at 08:02:12AM -0400, Alexander Motin wrote:
> Thanks for the notice, it was a wrong assertion. Fixed. I'm sorry.
>
After applying r352677 (via "svn patch --strip 1"), the machine boots
successfully:
FreeBSD freebeast.catwhisker.org 13.0-CURRENT FreeBSD 13.0-CURRENT #68
Thanks for the notice, it was a wrong assertion. Fixed. I'm sorry.
On 25.09.2019 06:54, David Wolfskill wrote:
> ...
> SMP: AP CPU #3 Launched!
> cpu3 AP:
> ID: 0x0003 VER: 0x01060015 LDR: 0x0008 DFR: 0x x2APIC:
> 1
> lint0: 0x00010700 lint1: 0x0400 TPR: 0x
...
SMP: AP CPU #3 Launched!
cpu3 AP:
ID: 0x0003 VER: 0x01060015 LDR: 0x0008 DFR: 0x x2APIC: 1
lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x11ff
timer: 0x000100ef therm: 0x0001 err: 0x00f0 pmc: 0x00010400
cmci: 0x000100f2
SMP: AP CPU #6 Launch
13 matches
Mail list logo
