Panic testing ZFS raidz expansion feature.

I want to test the ZFS raidz expansion feature. I have create a VM with vm-bhyve: # vm iso https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/15.0/FreeBSD-15.0-CURRENT-amd64-20240718-a4469a0d19b6-271237-bootonly.iso # vm create fbsd15-bis I have increased the VM memory to 2G: # cat fbsd1

Re: no hw.acpi.video.lcd0 with graphics/drm-510-kmod

Il giorno dom 22 mag 2022 alle ore 18:08 Pete Wright ha scritto: > hello, > i have a lenovo P43s laptop running current. i've noticed that since > graphics/drm-510-kmod became available hw.acpi.video.lcd0 ceases to > exist (which makes it impossible to adjust screen brightness). i've > installe

Lenovo ThinkPad T450 panic in vm_page_alloc_check

Hello, second panic today. The laptop is running: > uname -a FreeBSD NomadBSD 14.0-CURRENT FreeBSD 14.0-CURRENT #0 e9016c0be: Sun Jan 2 04:27:33 CET 2022 root@NomadBSD:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 The backtrace command shows: (kgdb) backtrace #0 __curthread () at /usr/src/s

Lenovo ThinkPad T450 panic in vm_freelist_rem()

Hello and happy new year. The laptop is running: > uname -a FreeBSD NomadBSD 14.0-CURRENT FreeBSD 14.0-CURRENT #0 e9016c0be: Sun Jan 2 04:27:33 CET 2022 root@NomadBSD:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 The backtrace command shows: #0 __curthread () at /usr/src/sys/amd64/include

Kernel panic on Lenovo Thinkpad T450

On this laptop I've been using FreeBSD 14 for a few months now and sometimes it panics, but after upgrading to: uname -a FreeBSD NomadBSD 14.0-CURRENT FreeBSD 14.0-CURRENT #0 e2157cd00: Sat Nov 6 03:21:26 CET 2021 root@NomadBSD:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 It always panics

Re: OpenZFS port updated

Il giorno ven 17 apr 2020 alle ore 20:36 Ryan Moeller ha scritto: > FreeBSD support has been merged into the master branch of the openzfs/zfs > repository, and the FreeBSD ports have been switched to this branch. > > OpenZFS brings many exciting features to FreeBSD, including: > * native encrypt

Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted

2018-05-30 17:50 GMT+02:00 Glen Barber : > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images ar

Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted

2018-05-30 17:50 GMT+02:00 Glen Barber : > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images ar

net/isboot-kmod works with net/istgt but not with ctld(8)

I am successfully running a diskless TrueOS, a FreeBSD 12-CURRENT derivate, desktop with the net/istgt port installed in a FreeBSD 11-RELEASE server. I am using this setup without any error, but it is a bit slow. I want to test ctld on my server, but when the diskless PC loads the isboot driver it

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

2018-02-04 14:40 GMT+01:00 Andriy Gapon : > On 04/02/2018 11:50, Maurizio Vairani wrote: > > I have added a socket in the ifioctl() call as in the > > /usr/src/sys/nfs/bootp_subr.c source. > > Please let me know if you prefer a patch. > > A patch here https://review

Re: Testing requested: Hybrid ISO/USB boot

2018-03-22 19:06 GMT+01:00 Benno Rice : > Hello all! > > I’ve been working on the ability to create hybrid ISO/HDD boot images for > x86, a la what Linux systems do with ISOHYBRID. The general theory seems to > be that ISO images have a 32KB hunk of zeroes at the front that they > generally ignore

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

2018-02-07 19:29 GMT+01:00 John Nielsen : > > On Feb 7, 2018, at 6:07 AM, Maurizio Vairani > wrote: > > > > 2018-02-06 23:02 GMT+01:00 John Nielsen : > > > On Feb 6, 2018, at 11:50 AM, Ian Lepore wrote: > > > > > > On Tue, 2018-02-06 at 11:33 -07

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

2018-02-06 23:02 GMT+01:00 John Nielsen : > > On Feb 6, 2018, at 11:50 AM, Ian Lepore wrote: > > > > On Tue, 2018-02-06 at 11:33 -0700, John Nielsen wrote: > >> > >> Apparently sending a NULL socket pointer to ifioctl hasn't worked > >> since this commit in 2011: > >> https://svnweb.freebsd.org/b

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

2018-01-29 18:38 GMT+01:00 John Nielsen : > [ resending from correct email address ] > > On Jan 29, 2018, at 6:05 AM, Maurizio Vairani > wrote: > > I am running > # uname > -a > > FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 04:48:

Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

I am running # uname -a FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 04:48:52 UTC 2018 r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 After compiling the kernel module as discussed in this thread : https://lists.freebsd.org/pipermail/freebsd-

Re: Error compiling isboot-kmod

2018-01-27 17:20 GMT+01:00 Ian Lepore : > On Fri, 2018-01-26 at 23:20 -0700, John Nielsen wrote: > > > > > > On Jan 26, 2018, at 9:42 PM, John Nielsen wrote: > > > > > > > > > > > [...] > > > --- iscsi.o --- > > > iscsi.c:1146:3: error: incompatible pointer types passing 'void > (struct mbuf *, v

Re: Error compiling isboot-kmod

2018-01-24 17:19 GMT+01:00 Warner Losh : > > > On Wed, Jan 24, 2018 at 3:12 AM, Maurizio Vairani > wrote: > >> On this CURRENT snapshot >> # uname -a >> FreeBSD freebsd12 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r327788: Wed Jan 10 >> 22:55:40 UTC 2018 >&

Error compiling isboot-kmod

On this CURRENT snapshot # uname -a FreeBSD freebsd12 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r327788: Wed Jan 10 22:55:40 UTC 2018 r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 I can't compile the kernel module isboot-kmod: # cd /usr/ports/net/isboot-kmod && make ===>

Re: Programmatically cache line

2018-01-02 2:27 GMT+01:00 blubee blubeeme : > On Tue, Jan 2, 2018 at 12:26 AM, Ian Lepore wrote: > > > On Mon, 2018-01-01 at 12:36 +0200, Konstantin Belousov wrote: > > > On Mon, Jan 01, 2018 at 06:52:37AM +, David Chisnall wrote: > > > > > > > > On 1 Jan 2018, at 05:09, Adrian Chadd > wrote

Re: i915kms breakage

2017-04-29 0:52 GMT+02:00 Andrey Fesenko : > On Fri, Apr 28, 2017 at 10:10 PM, Maurizio Vairani > wrote: > > 2017-04-22 14:47 GMT+02:00 Domagoj Stolfa : > > > >> Hello, > >> > >> ever since I've merged yesterday, it would seem that the

Re: i915kms breakage

2017-04-22 14:47 GMT+02:00 Domagoj Stolfa : > Hello, > > ever since I've merged yesterday, it would seem that the i915kms driver > panics every time it is loaded. Unfortunately, I am not able to provide > a dump of the panic, as I am unable to see what the panic is, or what is > even going on as a

Re: New rc.d scripts on current

2016-04-24 21:26 GMT+02:00 Lars Engels : > On Sun, Apr 24, 2016 at 08:33:11AM -0700, Manfred Antar wrote: > > Updated /etc yesterday via mergemaster. > > Now I’m getting this on reboot. Everything seems to be working alright. > > > > eval: disk: not found > > eval: disk: not found > > eval: ${GELI