Re: Lockdown adaX numbers to allow booting ?

> On 21 Sep 2019, at 02:36, Garrett Wollman > wrote: > > In article <20190920155304.gn3...@zxy.spb.ru>, s...@zxy.spb.ru writes: > >> Location of device in multi-chassis storage system is different story. >> I am don't know how to field engineer insert disks in chassis. >> For me simple is

Re: Lockdown adaX numbers to allow booting ?

> On 14 Oct 2019, at 03:17, Kurt Jaeger wrote: >>> You're probably looking for this: >>> https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html >> >> Would glabel solve it? > > The disks are not gpart-formatted, they are used raw. What file system are they formatted with? UFS

Re: SVN r353480 now mandates kernel option VIMAGE

> On 13. Oct 2019, at 21:26, Michael Butler wrote: > > sys/net/route.c will no longer compile when VIMAGE is removed from the > kernel, That wasn't intended. Fixed in r353482. Sorry for the breakage and thank you very much for reporting! Best regards Michael > > imb

Re: SVN r353480 now mandates kernel option VIMAGE

> On 13. Oct 2019, at 21:26, Michael Butler wrote: > > sys/net/route.c will no longer compile when VIMAGE is removed from the > kernel, Let me look at it... Best regards Michael > > imb ___ freebsd-current@freebsd.org mailing list

SVN r353480 now mandates kernel option VIMAGE

sys/net/route.c will no longer compile when VIMAGE is removed from the kernel, imb ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: Lockdown adaX numbers to allow booting ?

Hi! > > You're probably looking for this: > > https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html > > Thanks, that looks like a very useful approach. > > Will test that when I'm in the housing facility, and report back. I tested it, no change 8-( -- p...@opsec.eu

Re: Lockdown adaX numbers to allow booting ?

Hi! > > You're probably looking for this: > > https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html > > Would glabel solve it? The disks are not gpart-formatted, they are used raw. -- p...@opsec.eu+49 171 3101372One year to go !

Re: svn commit: r351858 - in head: bin/uuidgen ...

Building a jail from pkgbase packages after base r351858 shows this cap_mkdb message: to create the jail this command is used: pkg --rootdir /jails/test01 -o 'ASSUME_ALWAYS_YES=true' -o 'ABI=FreeBSD:13:amd64' install --repository FreeBSD-base FreeBSD-utilities FreeBSD-rc (note: FreeBSD-base

Re: Lockdown adaX numbers to allow booting ?

On Thu, September 19, 2019 17:10, Daniel Engberg wrote: > Hi Kurt! > > You're probably looking for this: > https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html Would glabel solve it? I have almost as much disks and some zpools and it runs fine. matheus

New driver for Asus Xonar DG/DGX soundcards now available

Good day everyone! Driver for Asus Xonar DG/DGX soundcards is now available on my home page. Features are playback, recording (up to 192 kHz both directions), playback up to 6 channels, spdif, volume controls, ACPI. If someone is interested - download it, test, and share results. Again, I

Re: hang up with r352239 and r352386 with i5-7500

On Mon, Sep 16, 2019 at 01:24:12PM +0200, Niclas Zeising wrote: > On 2019-09-16 13:09, Masachika ISHIZUKA wrote: > >Hi. > > > >My machine (with core i5-7500) is hangup when loading i915kms.ko > > on r352239 and r352386 (1300047). > >This machine was working good with r351728

assertion error in ZFS

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: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zrlock.c, line: 115 cpuid = 16 time = 26

Enable wasm LLVM backend

Hi list, I’m trying the Freebsd 12.1 prerelease which comes with llvm 8.0. The webassembly (wasm) backend is no longer experimental and enabled by default in llvm 8.0 and also the coming 9.0 with riscv backend. But I failed to use the wasm backend in the prerelease: clang90 -Wall

Re: Kernel-Crash when working with ubt0

On Friday, 30 August 2019 21:50:28 CEST Maksim Yevmenkin wrote: > [trimming the list of recipients] > good like this, so many mails gonna unsubscribe the list - many problems and bugs as far as eye reaches... > On Fri, Aug 30, 2019 at 12:08 PM Miranda Maria Sophie Van den > > Breukelingen

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

On Tue, 27 Aug 2019 08:43:53 +0300 Toomas Soome wrote: > > On 27 Aug 2019, at 08:08, Warner Losh wrote: > > > > On Mon, Aug 26, 2019, 5:32 PM Rebecca Cran > > wrote: > >> On 8/26/19 5:22 AM, O. Hartmann wrote: > >> > >>> > >>> the other thing is the weird Lenovo

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Wed, 21 Aug 2019 22:34:21 +0300 Toomas Soome schrieb: > > On 21 Aug 2019, at 22:30, O. Hartmann wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > Am Wed, 21 Aug 2019 22:14:46 +0300 > > Toomas Soome

Re: Kernel-Crash when working with ubt0

On Monday, 26 August 2019 23:35:25 CEST maksim yevmenkin wrote: > > On Aug 26, 2019, at 9:14 AM, Warner Losh wrote: > > > > Is it from read_connection_list? If so I have a 'patch' that I'm using but > > haven't committed because it's just too gross: drop the lock before the > > copyout and pick

Re: HEADSUP: drm-current-kmod now installs sources

Is it then possible to introduce another option - install only drm-kmod sources and don't build a module, so that a user that builds a new kernel often can build when he chooses to? signature.asc Description: PGP signature

Re: Lockdown adaX numbers to allow booting ?

In article <20190920155304.gn3...@zxy.spb.ru>, s...@zxy.spb.ru writes: >Location of device in multi-chassis storage system is different story. >I am don't know how to field engineer insert disks in chassis. >For me simple is find in /var/run/dmesg.boot S/N <=> daXY mapping and >turn ON led by

Re: ntpd segfaults on start

Cy, On 9/6/2019 4:56 PM, Cy Schubert wrote: > ... > > For those who enable ASLR, a better workaround is, to add this to your > ntp.conf: > > rlimit memlock 64 > > Until a more precise default is determined. Should I change the default value for FreeBSD-12 to be 64 for now? I can get this

current 350855 build error / intel hd 5500 / intel wifi 7265 / sierra em7305

Hello world :-) I have switched to a Panasonic Toughbook CF-MX4 (i5-5300U based), which has problematic: 1. Intel HD 5500 GPU. Cannot see screen (DRM issue?). 2. Intel WiFi 7265. Load format error. 3. Sierra Wireless EM7305. Not recognised by U3G. None of them seem to work out of the box in

Re: current 350855 build error / intel hd 5500 / intel wifi 7265 / sierra em7305

On Sun, Aug 11, 2019 at 4:03 PM Tomasz CEDRO wrote: > I have switched to a Panasonic Toughbook CF-MX4 (i5-5300U based), > which has problematic: > 1. Intel HD 5500 GPU. Cannot see screen (DRM issue?). > 2. Intel WiFi 7265. Load format error. > 3. Sierra Wireless EM7305. Not recognised by U3G. > >

Re: panic... r350849M panic: ng_snd_item: 42 != 1414

Larry: I am clueless when it comes to net graph :o.. I will be committing the fix/patch for rack shortly :) R > On Aug 20, 2019, at 9:26 AM, Larry Rosenman wrote: > > the M is a patch from rrs@ for the previous crash on m_pullup. > > Ideas? I have a core. > > > Unread portion of the

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Wed, 21 Aug 2019 22:29:29 + greg@unrelenting.technology schrieb: > August 22, 2019 12:23 AM, "O. Hartmann" wrote: > > > Am Wed, 21 Aug 2019 15:58:24 -0500 > > Karl Denninger schrieb: > > > >> I would see if you can get REFIND loaded

Re: CURRENT: supeblock hash failure - CURRENT wrecking disks

> Date: Wed, 7 Aug 2019 10:37:29 +0200 > From: "O. Hartmann" > To: freebsd-current > Subject: CURRENT: supeblock hash failure - CURRENT wrecking disks > > Hello, > > Today I ran into a ctastrophy with r350671. After installing a fresh > compiled system and rebooted the box, UEFI loader dropped

Re: Kernel-Crash when working with ubt0

On Monday, 26 August 2019 09:21:53 CEST Hans Petter Selasky wrote: > Do you have a backtrace? > > --HPS Yup! Have a look at this sniplet: https://pastebin.com/bkNkThAd MvB ___ freebsd-current@freebsd.org mailing list

Re: kernel module code coverage

The whole point of adding gcov support was for integrating with the ZoL CI framework which does coverage. So it very much does work with modules. Not sure where that comes from. -M On Thu, Aug 8, 2019 at 6:52 AM Alan Somers wrote: > > On Thu, Aug 8, 2019 at 7:42 AM Michael Tuexen wrote: > > > >

Re: CURRENT: supeblock hash failure - CURRENT wrecking disks

> To: Enji Cooper > cc: "O. Hartmann" , > freebsd-current , mckus...@mckusick.com > Subject: Re: CURRENT: supeblock hash failure - CURRENT wrecking disks > From: "Poul-Henning Kamp" > > In message <39fb31e6-a8ec-484c-b297-39c19a787...@gmail.com>, Enji Cooper > writes > : > >

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

On 10/13/19, Evilham wrote: > Hello, > > I somehow had managed to mess up my build system and only > yesterday got it back to compiling properly. > So to be clear, there is an unrelated bug where it seems the module can decide to abort loading and then it crashes in pseudofs. This can happen if

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

Hello, I somehow had managed to mess up my build system and only yesterday got it back to compiling properly. On ds., oct. 12 2019, Mateusz Guzik wrote: Try this: https://people.freebsd.org/~mjg/pmap-fict-invl.diff I tested this patch on top of r353449 and a panic is still ocurring