On 9/4/18 21:39, Conrad Meyer wrote:
> With current libc, I instead see:
>
> load: 0.10 cmd: blocked_random_poc 1668 [randseed] 1.27r 0.00u 0.00s
> 0% 2328k (SIGINFO)
>
> $ procstat -kk 1668
> PIDTID COMMTDNAME KSTACK
> 1668 100609 blocked_random_poc -
With current libc, I instead see:
load: 0.10 cmd: blocked_random_poc 1668 [randseed] 1.27r 0.00u 0.00s
0% 2328k (SIGINFO)
$ procstat -kk 1668
PIDTID COMMTDNAME KSTACK
1668 100609 blocked_random_poc - mi_switch+0xd3
sleepq_catch_signals+0x386
Hi Lev,
I took a first attempt at reproducing this problem on a fast
desktop-class system. First steps, give us a way to revert back to
unseeded status:
--- a/sys/dev/random/fortuna.c
+++ b/sys/dev/random/fortuna.c
@@ -39,6 +39,7 @@ __FBSDID("$FreeBSD$");
#ifdef _KERNEL
#include
+#include
Powers s/b powers (autocorrect).
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.
Cy Schubert
or
The need of the many outweighs the greed of the few.
---
-Original Message-
From: Cy Schubert
Sent: 04/
Are you running powers?
Do you use c-states?
What happens if you boot in (instead of switch to) turbo mode?
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.
Cy Schubert
or
The need of the many outweighs the
On Tue, Sep 4, 2018 at 2:10 PM, Lev Serebryakov wrote:
> Wednesday, September 5, 2018, 12:05:43 AM, you wrote:
>> I think it is tripping on raise/abort() in one of these routines, but
>> nothing is printing that information. See below.
>
> Maybe, it should be fixed?
Yes, it should.
> One secon
On Wed, 2018-09-05 at 00:07 +0300, Lev Serebryakov wrote:
> Hello FreeBSD,
>
> When I use serial console (configured as console + "getty std.115200
> xterm"), csh works perfectly Ok, but "sh" and "more" lockss forever.
> If I hit
> ^T system shows that locked process is in "[ttydcd]" state. ^C ki
Hello Conrad,
Wednesday, September 5, 2018, 12:05:43 AM, you wrote:
> On Tue, Sep 4, 2018 at 1:55 PM, Lev Serebryakov wrote:
>> Tuesday, September 4, 2018, 11:37:59 PM, you wrote:
>>> Is newfs tripping on a raise()/abort() in arc4random(3) /
>>> getentropy(3)?
>> Nope, it is silently does noth
Hello FreeBSD,
When I use serial console (configured as console + "getty std.115200
xterm"), csh works perfectly Ok, but "sh" and "more" lockss forever. If I hit
^T system shows that locked process is in "[ttydcd]" state. ^C kills locked
process.
What do I have misconfigured?
--
Best regards,
Hi Lev,
On Tue, Sep 4, 2018 at 1:55 PM, Lev Serebryakov wrote:
> Tuesday, September 4, 2018, 11:37:59 PM, you wrote:
>> Is newfs tripping on a raise()/abort() in arc4random(3) /
>> getentropy(3)?
> Nope, it is silently does nothing
I think it is tripping on raise/abort() in one of these routin
Hello Conrad,
Tuesday, September 4, 2018, 11:37:59 PM, you wrote:
> Newfs just uses arc4random(3) to generate its FSID and generation
> numbers. arc4random(3) is seeded from getentropy(3) -> getrandom(2)
->> read_random_uio(9), which is what produces the "random:
> read_random_uio unblock wait"
Hi Lev,
Newfs just uses arc4random(3) to generate its FSID and generation
numbers. arc4random(3) is seeded from getentropy(3) -> getrandom(2)
-> read_random_uio(9), which is what produces the "random:
read_random_uio unblock wait" messages.
Is newfs tripping on a raise()/abort() in arc4random(3)
Hello FreeBSD,
I'm installing latest 12-ALPHA4 on new MiniPC with Celeron J3160 CPU. It
is 1.6GHz CPU with Turbo up to 2.somethingGHz.
If I enable Turbo mode, after booting to FreeBSD it locks at 480MHz
according to dev.cpu.0.freq, and simple "openssl" test confirms it.
If I disable Turb
Hello FreeBSD,
I have problems with diskless install when kernel doesn't have tmpfs and
random device takes long time to unlock.
Looks like newfs used to create in-memory /etc (on /dev/md0) silently fail
to create FS.
I've added '-XL' options to mdmfs and it looks like this:
da0: quirks=0x2
On Tue, Sep 04, 2018 at 09:49:32PM +0530, Rajesh Kumar wrote:
> Hi Jake,
>
> Please try setting hw.pci.mcfg=0 from the boot loader and see if it helps.
>
> On Tue, Sep 4, 2018 at 2:34 AM Jake Champlin wrote:
>
> > Testing out various BSD's with a Huawei Matebook D, and FreeBSD -CURRENT is
> > f
Hi Jake,
Please try setting hw.pci.mcfg=0 from the boot loader and see if it helps.
On Tue, Sep 4, 2018 at 2:34 AM Jake Champlin wrote:
> Testing out various BSD's with a Huawei Matebook D, and FreeBSD -CURRENT is
> failing to boot from an installer image. No serial console, so unable to
> grab
On Tue, Sep 4, 2018 at 3:32 AM, tech-lists wrote:
> Hello list,
>
> What's the difference between github freebsd and svn freebsd, other than one
> is on github and the other is on svn?
The github repository is read-only mirror -- new additions all come
through SVN.
> How does one transcode or t
Hi!
> What's the difference between github freebsd and svn freebsd, other than
> one is on github and the other is on svn?
The github repo isn't official, because there are still some
consistency issues. The consistency problem is: If an repo-copy
from svn to git is done, how can that repo-copy
Hello list,
What's the difference between github freebsd and svn freebsd, other than
one is on github and the other is on svn?
How does one transcode or translate a git commit reference into a svn
reference number?
thanks,
--
J.
___
freebsd-curren
Running CURRENT (FreeBSD 12.0-ALPHA4 #19 r338446: Mon Sep 3 21:07:45
CEST 2018 amd64) on a PCengine APU2C4 (NIC is 3x Intel i210:
[...]
igb0@pci0:2:0:0:class=0x02 card=0x8086 chip=0x157b8086
rev=0x03 hdr=0x00 vendor = 'Intel Corporation'
device = 'I210 Gigabit Network C
20 matches
Mail list logo
