Re: assertion error in ZFS

2019-10-10 Thread Andriy Gapon
On 10/10/2019 20:28, Piotr Kubaj via freebsd-fs wrote: > Hi, > > I use ZFS compiled-in to the kernel in order to boot without loader. > > After upgrade to LLVM9, it fails to mount with: > panic: solaris assert: (int32_t)n >= 0 (0x >= 0x0), file: >

Re: DRM-current-kmod is still a problem at r353339

2019-10-10 Thread Jung-uk Kim
On 19. 10. 10., Mateusz Guzik wrote: > Probably whitespace issues from copypasting. I used dpaste since > people.freebsd.org was down. > > It's up, so: > https://people.freebsd.org/~mjg/pmap-fict3.diff This patch fixed a similar problem for me. FYI, I am using drm-devel-kmod for "AMD Ryzen 5

Re: DRM-current-kmod is still a problem at r353339

2019-10-10 Thread Mateusz Guzik
Probably whitespace issues from copypasting. I used dpaste since people.freebsd.org was down. It's up, so: https://people.freebsd.org/~mjg/pmap-fict3.diff On 10/10/19, Thomas Laus wrote: > On 2019-10-10 12:21, Mateusz Guzik wrote: >> Try this: >> >> http://dpaste.com/0P2MXF6 >> >> if it still

Re: DRM-current-kmod is still a problem at r353339

2019-10-10 Thread Thomas Laus
On 2019-10-10 12:21, Mateusz Guzik wrote: > Try this: > > http://dpaste.com/0P2MXF6 > > if it still fails, provide the panic info + the first debug line(the > one with "pv_table"). > This patch did not apply cleanly to my source tree checked out today. My pmap.c version is r353311. I saved the

Re: DRM-current-kmod is still a problem at r353339

2019-10-10 Thread Mateusz Guzik
Try this: http://dpaste.com/0P2MXF6 if it still fails, provide the panic info + the first debug line(the one with "pv_table"). On 10/10/19, Thomas Laus wrote: > List: > > I am still getting kernel panics on my laptop after the recent changes > made to /sys/amd64/amd64/pmap.c. > > The updated

DRM-current-kmod is still a problem at r353339

2019-10-10 Thread Thomas Laus
List: I am still getting kernel panics on my laptop after the recent changes made to /sys/amd64/amd64/pmap.c. The updated pmap.c works on my Skylake build machine but panics on my laptop. I always build on the faster computer and perform a installkernel and installworld from a nfs share. The

Re: freebsd-current Digest, Vol 832, Issue 4

2019-10-10 Thread Miranda van den Breukelingen
newly buildworld for 7 hours, couldn't be installed in headers/test from single mode on and on a normal reboot ELF doesn't work when installing. So reverted, revision is 353388 now kernel with VERBOSE_DEBUG=2 on. Plasma comes to the point where the 'kstart5 plasmashell' should begin to a "sudden

Re: 2 things; a cool crash log of my grandmother-laptop, that's plasma's now bricked; vmn0 not X -configuring

2019-10-10 Thread mms.vanbreukelin...@gmail.com
No,  there's no LED flashing of SDD when entering to boot the initial modules.  On Thu, 10 Oct 2019 at 7:34, Theron wrote: On 2019-10-09 19:46, Miranda van den Breukelingen wrote: > 2. Radeon R7 240 firmware error: > > did hw.syscons.disable=1 in /boot/loader.conf --- nothing, no boot >

Re: 2 things; a cool crash log of my grandmother-laptop, that's plasma's now bricked; vmn0 not X -configuring

2019-10-10 Thread Miranda van den Breukelingen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Gotta tailed dmesg.log and imported on linux via zfs-current-git-dkms: https://pastebin.com/LqQrdf2y this is when using kmod-stable... concerning updating from source, grandmother's laptop is sniffing with -j4 for 4 hours now and is still at

Re: 2 things; a cool crash log of my grandmother-laptop, that's plasma's now bricked; vmn0 not X -configuring

2019-10-10 Thread Theron
On 2019-10-09 19:46, Miranda van den Breukelingen wrote: 2. Radeon R7 240 firmware error: did hw.syscons.disable=1 in /boot/loader.conf --- nothing, no boot with none of the kernels. Really no boot with that line in loader.conf, whereas it could boot previously?  Possibly it is booting,