Re: Crash loading dtraceall

2019-05-08 Thread Mark Johnston
On Wed, May 08, 2019 at 11:01:58PM -0500, Larry Rosenman wrote: > On 05/08/2019 10:32 pm, Mark Johnston wrote: > > On Wed, May 08, 2019 at 05:57:18PM -0500, Larry Rosenman wrote: > >> On 05/08/2019 5:55 pm, Mark Johnston wrote: > >> > On Wed, May 08, 2019 at 05:47:08PM -0500, Larry Rosenman wrote:

Re: Crash loading dtraceall

2019-05-08 Thread Larry Rosenman
On 05/08/2019 10:32 pm, Mark Johnston wrote: On Wed, May 08, 2019 at 05:57:18PM -0500, Larry Rosenman wrote: On 05/08/2019 5:55 pm, Mark Johnston wrote: > On Wed, May 08, 2019 at 05:47:08PM -0500, Larry Rosenman wrote: >> On 05/08/2019 5:29 pm, Mark Johnston wrote: >> > On Wed, May 08, 2019 at 0

Re: Crash loading dtraceall

2019-05-08 Thread Mark Johnston
On Wed, May 08, 2019 at 05:57:18PM -0500, Larry Rosenman wrote: > On 05/08/2019 5:55 pm, Mark Johnston wrote: > > On Wed, May 08, 2019 at 05:47:08PM -0500, Larry Rosenman wrote: > >> On 05/08/2019 5:29 pm, Mark Johnston wrote: > >> > On Wed, May 08, 2019 at 03:52:45PM -0500, Larry Rosenman wrote: >

Re: Crash loading dtraceall

2019-05-08 Thread Larry Rosenman
On 05/08/2019 5:55 pm, Mark Johnston wrote: On Wed, May 08, 2019 at 05:47:08PM -0500, Larry Rosenman wrote: On 05/08/2019 5:29 pm, Mark Johnston wrote: > On Wed, May 08, 2019 at 03:52:45PM -0500, Larry Rosenman wrote: >> Greetings, >> >> Somewhere between r346483 and r347241 loading dtraceal

Re: Crash loading dtraceall

2019-05-08 Thread Mark Johnston
On Wed, May 08, 2019 at 05:47:08PM -0500, Larry Rosenman wrote: > On 05/08/2019 5:29 pm, Mark Johnston wrote: > > On Wed, May 08, 2019 at 03:52:45PM -0500, Larry Rosenman wrote: > >> Greetings, > >> > >> Somewhere between r346483 and r347241 loading dtraceall causes a > >> crash. I have t

Re: Crash loading dtraceall

2019-05-08 Thread Larry Rosenman
On 05/08/2019 5:29 pm, Mark Johnston wrote: On Wed, May 08, 2019 at 03:52:45PM -0500, Larry Rosenman wrote: Greetings, Somewhere between r346483 and r347241 loading dtraceall causes a crash. I have the cores and kernels. It's hard for me to bisect more than this, as the box is rem

Re: Crash loading dtraceall

2019-05-08 Thread Mark Johnston
On Wed, May 08, 2019 at 03:52:45PM -0500, Larry Rosenman wrote: > Greetings, > > Somewhere between r346483 and r347241 loading dtraceall causes a > crash. I have the cores and kernels. > > It's hard for me to bisect more than this, as the box is remote. > > What more do you ne

Crash loading dtraceall

2019-05-08 Thread Larry Rosenman
Greetings, Somewhere between r346483 and r347241 loading dtraceall causes a crash. I have the cores and kernels. It's hard for me to bisect more than this, as the box is remote. What more do you need? (this dump is fropm r347355). [l...@oldtbh2.lerctr.org:/var/crash] $ mo

Re: Elantech touchpad (HID over I2C): any work planned?

2019-05-08 Thread Marek Zarychta
W dniu 08.05.2019 o 18:54, Nikola Lečić pisze: > Hi, > > After buying a new Asus Zenbook 14 UX410UFR, I was unpleasantly > surprised that its touchpad (Elantech over I2C) isn't supported under > FreeBSD. > > I see that this kind of problem was discussed several times in the past: > https://lists.fr

Elantech touchpad (HID over I2C): any work planned?

2019-05-08 Thread Nikola Lečić
Hi, After buying a new Asus Zenbook 14 UX410UFR, I was unpleasantly surprised that its touchpad (Elantech over I2C) isn't supported under FreeBSD. I see that this kind of problem was discussed several times in the past: https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069704.html htt

Re: random_sources_feed: rs_read for hardware device 'Intel Secure Key RNG' returned no entropy.

2019-05-08 Thread Michael Tuexen
> On 8. May 2019, at 18:13, Andrey V. Elsukov wrote: > > Hi, > > today I updated one of my test machines and discovered that message from > the subject periodically printed in the console. Fixed in https://svnweb.freebsd.org/changeset/base/347329 Best regards Michael > > FreeBSD 13.0-CURRENT

Re: random_sources_feed: rs_read for hardware device 'Intel Secure Key RNG' returned no entropy.

2019-05-08 Thread Conrad Meyer
Sorry about that. Please update to r347329. Thanks, Conrad On Wed, May 8, 2019 at 9:16 AM Andrey V. Elsukov wrote: > Hi, > > today I updated one of my test machines and discovered that message from > the subject periodically printed in the console. > > FreeBSD 13.0-CURRENT r347327=4f47587(svn_h

Re: random_sources_feed: rs_read for hardware device 'Intel Secure Key RNG' returned no entropy.

2019-05-08 Thread Ian Lepore
On Wed, 2019-05-08 at 19:13 +0300, Andrey V. Elsukov wrote: > Hi, > > today I updated one of my test machines and discovered that message > from > the subject periodically printed in the console. > > FreeBSD 13.0-CURRENT r347327=4f47587(svn_head) GENERIC-NODEBUG amd64 > FreeBSD clang version 8.0.

random_sources_feed: rs_read for hardware device 'Intel Secure Key RNG' returned no entropy.

2019-05-08 Thread Andrey V. Elsukov
Hi, today I updated one of my test machines and discovered that message from the subject periodically printed in the console. FreeBSD 13.0-CURRENT r347327=4f47587(svn_head) GENERIC-NODEBUG amd64 FreeBSD clang version 8.0.0 (tags/RELEASE_800/final 356365) (based on LLVM 8.0.0) VT(vga): resolution