I'm not subscribed to -stable.
This is in response to jkim@'s messages here:
https://lists.freebsd.org/pipermail/freebsd-stable/2018-December/090202.html
https://lists.freebsd.org/pipermail/freebsd-stable/2018-December/090202.html
Based on what I can tell, OpenSSL 1.1.1 or thereabouts removed
On Thu, Dec 06, 2018 at 04:48:35PM -0700, John Nielsen wrote:
> Is aesni(4) even required if all you want is userland acceleration?
>
No, it is not. Same for rdrand_rng(4), if an application uses hw random
source directly.
___
On 18. 12. 6., Jung-uk Kim wrote:
> On 18. 12. 6., John Nielsen wrote:
>>> On Dec 6, 2018, at 4:04 PM, Xin LI wrote:
>>>
>>> On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote:
I have upgraded two physical machines from 11-STABLE to 12-STABLE recently
(one is 12.0-PRERELEASE
On 18. 12. 6., John Nielsen wrote:
>> On Dec 6, 2018, at 4:04 PM, Xin LI wrote:
>>
>> On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote:
>>>
>>> I have upgraded two physical machines from 11-STABLE to 12-STABLE recently
>>> (one is 12.0-PRERELEASE r341380 and the other is 12.0-PRERELEASE
> On Dec 6, 2018, at 4:39 PM, John Baldwin wrote:
>
> On 12/6/18 3:24 PM, John Nielsen wrote:
>>> On Dec 6, 2018, at 4:04 PM, Xin LI wrote:
>>>
>>> On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote:
I have upgraded two physical machines from 11-STABLE to 12-STABLE recently
On Thu, Dec 6, 2018 at 3:24 PM John Nielsen wrote:
>
> > On Dec 6, 2018, at 4:04 PM, Xin LI wrote:
> >
> > On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote:
> >>
> >> I have upgraded two physical machines from 11-STABLE to 12-STABLE recently
> >> (one is 12.0-PRERELEASE r341380 and the other
On 12/6/18 3:24 PM, John Nielsen wrote:
>> On Dec 6, 2018, at 4:04 PM, Xin LI wrote:
>>
>> On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote:
>>>
>>> I have upgraded two physical machines from 11-STABLE to 12-STABLE recently
>>> (one is 12.0-PRERELEASE r341380 and the other is 12.0-PRERELEASE
> On Dec 6, 2018, at 4:04 PM, Xin LI wrote:
>
> On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote:
>>
>> I have upgraded two physical machines from 11-STABLE to 12-STABLE recently
>> (one is 12.0-PRERELEASE r341380 and the other is 12.0-PRERELEASE r341391). I
>> noticed today that neither
On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote:
>
> I have upgraded two physical machines from 11-STABLE to 12-STABLE recently
> (one is 12.0-PRERELEASE r341380 and the other is 12.0-PRERELEASE r341391). I
> noticed today that neither machine seems to be utilizing /dev/crypto.
> Typically
On Thu, 06 Dec 2018 20:19:44 +0100, John Nielsen wrote:
>
> I have upgraded two physical machines from 11-STABLE to 12-STABLE
> recently (one is 12.0-PRERELEASE r341380 and the other is
> 12.0-PRERELEASE r341391). I noticed today that neither machine seems
> to be utilizing /dev/crypto. Typically
I have upgraded two physical machines from 11-STABLE to 12-STABLE recently (one
is 12.0-PRERELEASE r341380 and the other is 12.0-PRERELEASE r341391). I noticed
today that neither machine seems to be utilizing /dev/crypto. Typically I see
at least ssh/sshd have the device open plus some programs
Can you please file a bug at https://bugs.freebsd.org/bugzilla/ and
assign it to me?
Regards,
Navdeep
On 12/6/18 4:02 AM, Trond Endrestøl wrote:
> After booting stable/12 r341604, running a custom kernel including
> cxgbe(4), cxgbev(4), and ccr(4), and running swapon -a in SU mode:
>
>
On 12/6/18 3:16 PM, David Wolfskill wrote:
On Thu, Dec 06, 2018 at 03:02:43PM +0100, Christian Stærk wrote:
I have a new laptop. It's running 11.2-RELEASE.
While sound on the speakers works fine, sound through the headphones
does not.
.
Some of us who had a problem of this nature (in the
In most cases it's just wrong info passed from UEFI firmware about FB.
try to hardcode FrameBuffer params into vt_efb driver, to know exatly.
>>>
>>> Forgot to add importand detail: it boots and works with vt(4) using FreeBSD
>>> 11.1.
>>>
>>
>> r322258 is known working stable/11
On 06.12.2018 23:01, Eugene Grosbein wrote:
>>> In most cases it's just wrong info passed from UEFI firmware about FB.
>>> try to hardcode FrameBuffer params into vt_efb driver, to know exatly.
>>
>> Forgot to add importand detail: it boots and works with vt(4) using FreeBSD
>> 11.1.
>>
>>
>
>
On 06.12.2018 22:52, Eugene Grosbein wrote:
> On 06.12.2018 20:57, Aleksandr Rybalko wrote:
>
>> In most cases it's just wrong info passed from UEFI firmware about FB.
>> try to hardcode FrameBuffer params into vt_efb driver, to know exatly.
>
> Forgot to add importand detail: it boots and works
On 06.12.2018 20:57, Aleksandr Rybalko wrote:
> In most cases it's just wrong info passed from UEFI firmware about FB.
> try to hardcode FrameBuffer params into vt_efb driver, to know exatly.
Forgot to add importand detail: it boots and works with vt(4) using FreeBSD
11.1.
On Thu, Dec 06, 2018 at 03:02:43PM +0100, Christian Stærk wrote:
> Hello,
>
> I have a new laptop. It's running 11.2-RELEASE.
>
> While sound on the speakers works fine, sound through the headphones
> does not.
> .
Some of us who had a problem of this nature (in the cases with which I
am
On 06.12.2018 20:57, Aleksandr Rybalko wrote:
> Hi, Eugene!
>
> In most cases it's just wrong info passed from UEFI firmware about FB.
> try to hardcode FrameBuffer params into vt_efb driver, to know exatly.
I'm not familiar with vt_efb code. Can you please elaborate what should I do to
debug
Hello,
I have a new laptop. It's running 11.2-RELEASE.
While sound on the speakers works fine, sound through the headphones
does not.
From dmesg:
hdac0: mem
0xa1318000-0xa131bfff,0xa100-0xa10f irq 16 at device 31.3 on pci0
hdacc0: at cad 0 on hdac0
hdaa0: at nid 1 on hdacc0
On 06.12.2018 20:52, Eugene Grosbein wrote:
> Hi!
>
> I ran across several systems based on AMI Aptio CRB CLBTM210 equiped with
> Intel J1900 processor
> that hang early at boot in the moment of kernel initialisation unless forced
> to use syscons(4) console driver
> instead of default vt(4).
Hi, Eugene!
In most cases it's just wrong info passed from UEFI firmware about FB.
try to hardcode FrameBuffer params into vt_efb driver, to know exatly.
Thanks.
чт, 6 груд. 2018 о 15:52 Eugene Grosbein пише:
> Hi!
>
> I ran across several systems based on AMI Aptio CRB CLBTM210 equiped with
On 06/12/2018 21:34, George Mitchell wrote:
so that I can installkernel and installworld on them in single user
mode (hard to use NFS when booting in single user).-- George
# cd /usr/src
# make installkernel KERNCONF=GENERIC (or whatever)
reboot then repeat with installworld:
# mount
Hi!
I ran across several systems based on AMI Aptio CRB CLBTM210 equiped with Intel
J1900 processor
that hang early at boot in the moment of kernel initialisation unless forced to
use syscons(4) console driver
instead of default vt(4). Here is screen photo of one of such systems in such
dead
On 12/5/18 9:31 AM, Miroslav Lachman wrote:
> George Mitchell wrote on 2018/12/05 14:24:
>> [...]
>> But what I really need to know is
>> whether to make buildworld under 10.4 or 11.2. Or do I do it twice?
>> And presumably I can't run mergemaster until after buildworld.
>
> I did upgrade from
After booting stable/12 r341604, running a custom kernel including
cxgbe(4), cxgbev(4), and ccr(4), and running swapon -a in SU mode:
GEOM_ELI: Device gpt/swap0.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI: Crypto: hardware
Fatal trap 12: page fault while in kernel mode
cpuid =
1. How I can build release media of FreeBSD-12 on FreeBSD-11 system?
Currenly process failed by 'Abort trap'.
585191 121 -rw---1 root wheel
8962048 Dec 5 18:58 ./ldconfig.core
585199 121 -rw---1 root
27 matches
Mail list logo