drn0 - crash dump not in /var/crash

2020-08-19 Thread Vanbreukelingen Ltd.
On Thursday, August 20, 2020 8:12:58 AM CEST Vanbreukelingen Ltd. wrote: > On Wednesday, August 19, 2020 9:43:21 AM CEST you wrote: > > On Wed, Aug 19, 2020 at 3:22 AM Lizbeth Mutterhunt, Ph.D < > > > > lizbethmutterh...@gmail.com> wrote: > > > After having had some near-death-experiences in Greec

Re: PRINTF_BUFR_SIZE dangerous?

2020-08-19 Thread Gary Jennejohn
On Thu, 20 Aug 2020 08:33:32 +0200 Gary Jennejohn wrote: > It seems like PRINTF_BUFR_SIZE is a kernel fault waiting to happen. > > Only /usr/src/sys/cam/cam_xpt.c asserts that it's <= a maximum value of > 512 bytes. > > /usr/src/sys/kern/tty.c uses it to malloc space without checking its size.

PRINTF_BUFR_SIZE dangerous?

2020-08-19 Thread Gary Jennejohn
It seems like PRINTF_BUFR_SIZE is a kernel fault waiting to happen. Only /usr/src/sys/cam/cam_xpt.c asserts that it's <= a maximum value of 512 bytes. /usr/src/sys/kern/tty.c uses it to malloc space without checking its size. /usr/src/sys/dev/xen/console/xen_console.c and /usr/src/sys/kern/subr_

Re: CFT for vendor openzfs - week 5 reminder + memdisk images

2020-08-19 Thread Matthew Macy
> # kldload zfs > can't handle raw ops yet!!! > can't handle raw ops yet!!! > can't handle raw ops yet!!! > ZFS filesystem version: 5 > ZFS storage pool version: features support 5000 > can't handle raw ops yet!!! I'm working on it - Ryan reminded me of it today. It will probably get fixed before

Re: CFT for vendor openzfs - week 5 reminder + memdisk images

2020-08-19 Thread Johan Hendriks
Op 04-08-2020 om 02:24 schreef Matthew Macy: On Wednesday, July 8th I issued the initial call for testing for the update to HEAD to vendored openzfs. We'd like to give users roughly a month to test before merging. The tentative merge date is August 17th. Again, I hope it's not terribly contro

Re: kldref: too many segments on kernel build

2020-08-19 Thread Ed Maste
On Wed, 19 Aug 2020 at 00:19, Dustin Marquess wrote: > > On Tue, Aug 18, 2020 at 3:19 PM Michael Butler > wrote: > > > > Any thoughts as to why this is happening when I build a (custom) kernel? > > > > kldxref: /boot/kernel/kernel: too many segments > > I'm seeing this too. I haven't tried actua

Re: CFT: major update to if_ure

2020-08-19 Thread Ganbold Tsagaankhuu
On Tue, Jul 28, 2020 at 2:35 AM John-Mark Gurney wrote: > Ganbold Tsagaankhuu wrote this message on Mon, Jul 27, 2020 at 18:29 +0800: > > On Mon, Jul 27, 2020 at 5:14 AM John-Mark Gurney > wrote: > > > > > Ganbold Tsagaankhuu wrote this message on Sun, Jul 26, 2020 at 11:05 > +0800: > > > > On S

Re: funny thing with the drm0

2020-08-19 Thread Andreas Nilsson
On Wed, Aug 19, 2020 at 3:22 AM Lizbeth Mutterhunt, Ph.D < lizbethmutterh...@gmail.com> wrote: > After having had some near-death-experiences in Greece I'm back to my > screens. As horizon arises, BSD gets up --- and if it is 3 a.m.! :-) > > > But this is the experience with my Dell Vostro on 13 c

Re: kldref: too many segments on kernel build

2020-08-19 Thread Michael Tuexen
> On 19. Aug 2020, at 06:19, Dustin Marquess wrote: > > On Tue, Aug 18, 2020 at 3:19 PM Michael Butler > wrote: >> >> Any thoughts as to why this is happening when I build a (custom) kernel? >> >> kldxref: /boot/kernel/kernel: too many segments > > I'm seeing this too. I haven't tried actual

Re: kldref: too many segments on kernel build

2020-08-19 Thread Gary Jennejohn
On Tue, 18 Aug 2020 23:19:08 -0500 Dustin Marquess wrote: > On Tue, Aug 18, 2020 at 3:19 PM Michael Butler > wrote: > > > > Any thoughts as to why this is happening when I build a (custom) kernel? > > > > kldxref: /boot/kernel/kernel: too many segments > > I'm seeing this too. I haven't trie