DRM and Radeon

On 26/01/2021 07:02, Alexey Dokuchaev wrote: > Re: loading drm crashes system > … There are known issues with Radeon cards, they were quite well > supported a year ago, then something got broken. I've promised to > bisect this and find the cause, but there were several > syscall-related

Re: loading drm crashes system

W dniu 26.01.2021 o 08:02, Alexey Dokuchaev pisze: On Mon, Jan 25, 2021 at 10:21:16PM -0500, Robert Huff wrote: Niclas Zeising asks: When did it stop working? September ... I _think_. Yeah, that sounds about right. There are known issues with Radeon cards, they were quite well supported a

Re: loading drm crashes system

On Mon, Jan 25, 2021 at 10:21:16PM -0500, Robert Huff wrote: > Niclas Zeising asks: > > When did it stop working? > > September ... I _think_. Yeah, that sounds about right. There are known issues with Radeon cards, they were quite well supported a year ago, then something got broken. I've

problem building virtualbox-ose-kmod

having this issue building virtualbox-ose-kmod, its been like this for a while but I deinstalled and forgot, for quite a while now, maybe over a month. now that I've moved from 13-current to stable/13 I thought I would try to put it back, but it still wont build. I haven't seen anyone else

Re: pkg for 14-current

On 2021-01-26 11:14:53 (+0800), Mark Millard wrote: Philip Paeps philip at freebsd.org wrote on Mon Jan 25 21:40:03 UTC 2021 : The first package build for 14-CURRENT is visible on the mirrors now (as of a couple of minutes ago). It has been a bit so I tried and it failed for what I tried so

Re: loading drm crashes system

Niclas Zeising asks: > Which version of drm-current-kmod? 5.4.62.g20210118 > Can you try to remove it and build it directly from an updated ports > tree, without using PORTS_MODULES=, and see if that helps? It does not. > > The GPU is a Radeon HD 3300, and at one

Re: pkg for 14-current

Philip Paeps philip at freebsd.org wrote on Mon Jan 25 21:40:03 UTC 2021 : > The first package build for 14-CURRENT is visible on the mirrors now (as > of a couple of minutes ago). It has been a bit so I tried and it failed for what I tried so I looked at http://pkg.freebsd.org . It reported:

Re: fsck strange output

On Mon, 25 Jan 2021 20:51:50 + "Poul-Henning Kamp" wrote: > > Disk is 100% alive, got same on other HW. > > A disk can be alive and still have individually unreadable sectors, > that is, IMO, the most common failure mode. > > Try: > recoverdisk -v /dev/whatever > > That will

Re: fsck strange output

> From: Rozhuk Ivan > Date: Mon, 25 Jan 2021 23:29:33 +0300 > To: freebsd-current@freebsd.org > Cc: Rozhuk Ivan > Subject: fsck strange output > > Hi! > > I am on fresh 13 and on auto fsck got: > > Jan 25 23:14:13 3des kernel: Starting file system checks: > Jan 25 23:14:13 3des kernel:

Re: Getting /usr/src to match specific git hash?

On Mon, Jan 25, 2021 at 3:57 PM tech-lists wrote: > On Sun, Jan 24, 2021 at 01:08:05PM +0900, Yasuhiro Kimura wrote: > >From: Steve Kargl > >Subject: Getting /usr/src to match specific git hash? > >Date: Sat, 23 Jan 2021 19:58:52 -0800 > > > >> Suppose one has an empty /usr/src. > >> > >>

Re: Getting /usr/src to match specific git hash?

On Sun, Jan 24, 2021 at 01:08:05PM +0900, Yasuhiro Kimura wrote: From: Steve Kargl Subject: Getting /usr/src to match specific git hash? Date: Sat, 23 Jan 2021 19:58:52 -0800 Suppose one has an empty /usr/src. Suppose further that one had to re-install a 32-bit i386-*-freebsd with the 24 Dec

Re: ZFS feature compatibility?

> On 26. Jan 2021, at 00:23, John Kennedy wrote: > >> Thanks, I am new to the EFI world. Does the name now have to be >> BOOTx64.efi ? >> >> root@zoo2:/boot # ls -l /mnt/EFI/freebsd/ >> total 824 >> -rwxr-xr-x 1 root wheel 843776 Nov 21 10:50 loader.efi >> root@zoo2:/boot # > if there

Re: ZFS feature compatibility?

> Thanks, I am new to the EFI world.  Does the name now have to be > BOOTx64.efi ? > > root@zoo2:/boot # ls -l /mnt/EFI/freebsd/ > total 824 > -rwxr-xr-x  1 root  wheel  843776 Nov 21 10:50 loader.efi > root@zoo2:/boot # I don't know. This came out of an email thread I had a while ago:

Re: FreeBSD-provided .vhd with VirtualBox: gpart I/O errors after resizing the virtual hard disk

On 17/01/2021 18:22, Graham Perrin wrote: VirtualBox 5.2.44 r139111 on FreeBSD-CURRENT. 01. Add FreeBSD-12.2-RELEASE-amd64.vhd to a machine 02. use Virtual Disk Manager to resize it to 2.0 TB 03. apply, close 04. boot single user 05. gpart show /dev/ada0 07. observe reported corruption 08.

Re: ZFS feature compatibility?

> On 25. Jan 2021, at 23:08, Allan Jude wrote: > > On 2021-01-25 16:03, Toomas Soome via freebsd-current wrote: >> >> >>> On 25. Jan 2021, at 22:15, mike tancsa wrote: >>> >>> On 1/25/2021 2:37 PM, Toomas Soome via freebsd-current wrote: > On 25. Jan 2021, at 21:31, Michael

Re: ZFS feature compatibility?

On 1/25/2021 4:51 PM, John Kennedy wrote: > On Mon, Jan 25, 2021 at 04:17:18PM -0500, mike tancsa wrote: >> Is there a way to check from the bin if its the right version ? strings >> of the file doesnt seem to show anything useful.  I wonder if its the >> UEFI boot that got missed ?  Just >> >>

Re: ZFS feature compatibility?

On Mon, Jan 25, 2021 at 04:17:18PM -0500, mike tancsa wrote: > Is there a way to check from the bin if its the right version ? strings > of the file doesnt seem to show anything useful.  I wonder if its the > UEFI boot that got missed ?  Just > > gpart bootcode -p /boot/boot1.efifat -i 1ada8 >

Re: pkg for 14-current

On 2021-01-24 18:18:29 (+0800), Yasuhiro Kimura wrote: From: Masachika ISHIZUKA Subject: pkg for 14-current Date: Sun, 24 Jan 2021 19:11:28 +0900 (JST) Hi. I updated to 14-current from 13-current and reinstalled ports-mgmt/pkg. I cannot get meta files for 14-current. How can I use

Re: ZFS feature compatibility?

On 1/25/2021 4:03 PM, Toomas Soome wrote: > > >> On 25. Jan 2021, at 22:15, mike tancsa > > wrote: >> >> On 1/25/2021 2:37 PM, Toomas Soome via freebsd-current wrote: >>> On 25. Jan 2021, at 21:31, Michael Butler via freebsd-current

Re: ZFS feature compatibility?

On 2021-01-25 16:03, Toomas Soome via freebsd-current wrote: > > >> On 25. Jan 2021, at 22:15, mike tancsa wrote: >> >> On 1/25/2021 2:37 PM, Toomas Soome via freebsd-current wrote: >>> On 25. Jan 2021, at 21:31, Michael Butler via freebsd-current wrote: I have a few

Re: ZFS feature compatibility?

> On 25. Jan 2021, at 22:15, mike tancsa wrote: > > On 1/25/2021 2:37 PM, Toomas Soome via freebsd-current wrote: >> >>> On 25. Jan 2021, at 21:31, Michael Butler via freebsd-current >>> wrote: >>> >>> I have a few machines on which I've been hesitant to run 'zpool upgrade' as >>> I'm not

Re: fsck strange output

Rozhuk Ivan writes: > Disk is 100% alive, got same on other HW. A disk can be alive and still have individually unreadable sectors, that is, IMO, the most common failure mode. Try: recoverdisk -v /dev/whatever That will attempt to read all sectors on the disk. --

fsck strange output

Hi! I am on fresh 13 and on auto fsck got: Jan 25 23:14:13 3des kernel: Starting file system checks: Jan 25 23:14:13 3des kernel: /dev/gptid/81241708-8948-11e9-b1ae-049226c061d6: CANNOT READ BLK: 11072 Jan 25 23:14:13 3des kernel: /dev/gptid/81241708-8948-11e9-b1ae-049226c061d6: UNEXPECTED

Re: ZFS feature compatibility?

On 1/25/2021 2:37 PM, Toomas Soome via freebsd-current wrote: > >> On 25. Jan 2021, at 21:31, Michael Butler via freebsd-current >> wrote: >> >> I have a few machines on which I've been hesitant to run 'zpool upgrade' as >> I'm not sure of the (boot?) implications. They report like this .. >>

Re: ZFS feature compatibility?

I ran into an issue not being able to boot because of v2 bookmarks on the boot pool on RELENG_13 just last Friday.     ---Mike On 1/25/2021 2:31 PM, Michael Butler via freebsd-current wrote: > I have a few machines on which I've been hesitant to run 'zpool > upgrade' as I'm not sure of the

Re: Can In-Kernel TLS (kTLS) work with any OpenSSL Application?

On 1/20/21 12:21 PM, Neel Chauhan wrote: Hi freebsd-current@, I know that In-Kernel TLS was merged into the FreeBSD HEAD tree a while back. With 13.0-RELEASE around the corner, I'm thinking about upgrading my home server, well if I can accelerate any SSL application. I'm asking because I have

Re: 13-alpha2 libncurses removal breaks ports build

Builds OK from inside clean install. Which is all I needed this far. Thank you. With kindest regards, Kostya Berger On Sunday, 24 January 2021, 17:53:41 GMT+3, Kostya Berger wrote: OK, building ports against a clean installation of 13.0-ALPHA2 has no problem with ncurses. But

Re: using git to get a particular version of src

On Mon, Jan 25, 2021 at 12:35 PM Warner Losh wrote: > > > On Mon, Jan 25, 2021 at 11:55 AM Warner Losh wrote: > >> >> >> On Mon, Jan 25, 2021 at 11:11 AM Yasuhiro Kimura >> wrote: >> >>> From: Chris >>> Subject: Re: using git to get a particular version of src >>> Date: Mon, 25 Jan 2021

Re: ZFS feature compatibility?

> On 25. Jan 2021, at 21:31, Michael Butler via freebsd-current > wrote: > > I have a few machines on which I've been hesitant to run 'zpool upgrade' as > I'm not sure of the (boot?) implications. They report like this .. > > imb@toshi:/home/imb> uname -a > FreeBSD

Re: service -e doesn't really sort does it? the cool tip is slightly off

On 1/16/21 3:28 PM, Dennis Clarke wrote: root@rhea:/usr/src/freebsd-src # diff -u usr.bin/fortune/datfiles/freebsd-tips.orig usr.bin/fortune/datfiles/freebsd-tips --- usr.bin/fortune/datfiles/freebsd-tips.orig 2021-01-15 00:37:37.863506000 + +++ usr.bin/fortune/datfiles/freebsd-tips

Re: using git to get a particular version of src

On Mon, Jan 25, 2021 at 11:55 AM Warner Losh wrote: > > > On Mon, Jan 25, 2021 at 11:11 AM Yasuhiro Kimura wrote: > >> From: Chris >> Subject: Re: using git to get a particular version of src >> Date: Mon, 25 Jan 2021 09:21:44 -0800 >> >> >> Hi, >> >> I have this version installed: >> >>

ZFS feature compatibility?

I have a few machines on which I've been hesitant to run 'zpool upgrade' as I'm not sure of the (boot?) implications. They report like this .. imb@toshi:/home/imb> uname -a FreeBSD toshi.auburn.protected-networks.net 14.0-CURRENT FreeBSD 14.0-CURRENT #25 main-eb61de5b78: Fri Jan 22 10:03:02

Re: Re: Files in /usr/share/misc

Thank you all for the input. So, this directory is a little bit like the bottom drawer on my desk, where i put things, i don't know where to put else :) the hier man page states: misc/ miscellaneous system-wide ASCII text files About half of the files are ASCII text, according to the file

Re: using git to get a particular version of src

On Mon, Jan 25, 2021 at 11:11 AM Yasuhiro Kimura wrote: > From: Chris > Subject: Re: using git to get a particular version of src > Date: Mon, 25 Jan 2021 09:21:44 -0800 > > >> Hi, > >> I have this version installed: > >> 13.0-CURRENT #0 2ed50808d2b-c254384(main): Thu Nov 12 10:03:35 UTC > >>

Re: using git to get a particular version of src

From: Chris Subject: Re: using git to get a particular version of src Date: Mon, 25 Jan 2021 09:21:44 -0800 >> Hi, >> I have this version installed: >> 13.0-CURRENT #0 2ed50808d2b-c254384(main): Thu Nov 12 10:03:35 UTC >> 2020 >> I'd like to get the sources for this (want to make a no-debug

Re: using git to get a particular version of src

On 2021-01-25 08:31, tech-lists wrote: Hi, I have this version installed: 13.0-CURRENT #0 2ed50808d2b-c254384(main): Thu Nov 12 10:03:35 UTC 2020 I'd like to get the sources for this (want to make a no-debug kernel) as I know this version works on this hardware. But -current has gone to 14

Re: using git to get a particular version of src

On Mon, Jan 25, 2021 at 04:31:13PM +, tech-lists wrote: Hi, I have this version installed: 13.0-CURRENT #0 2ed50808d2b-c254384(main): Thu Nov 12 10:03:35 UTC 2020 I'd like to get the sources for this (want to make a no-debug kernel) as I know this version works on this hardware. But

using git to get a particular version of src

Hi, I have this version installed: 13.0-CURRENT #0 2ed50808d2b-c254384(main): Thu Nov 12 10:03:35 UTC 2020 I'd like to get the sources for this (want to make a no-debug kernel) as I know this version works on this hardware. But -current has gone to 14 and what was -current is now 13-stable.

Re: loading drm crashes system

On 2021-01-25 00:19, Robert Huff wrote: Hello: On a system now running: 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-d6327ae8c1: Sun Jan 24 14:16:54 EST 2021 amd64 (src+ports updated at midnight US EST) with PORTS_MODULES="drm-current-kmod gpu-firmware-kmod", starting the

Re: Can In-Kernel TLS (kTLS) work with any OpenSSL Application?

Benjamin Kaduk wrote: >On Sat, Jan 23, 2021 at 03:25:59PM +, Rick Macklem wrote: >> Ronald Klop wrote: >> >On Wed, 20 Jan 2021 21:21:15 +0100, Neel Chauhan wrote: >> >But I think for Tor to support KTLS it needs to implement some things >> >itself. More information about that could be asked

Re: Poudriere failed to build pkg in 13-stable jail under 12-stable

On Mon, Jan 25, 2021 at 12:46:43PM +0800, Thomas Legg wrote: > The build of a 13-stable source and kernel were a success under 12-stable > (though with some issues on freeze-ups and hard reboots that I suspect > might be related to the bufdaemon issue and my 0x15 gen AMD cpu). > > Created a

Poudriere failed to build pkg in 13-stable jail under 12-stable

The build of a 13-stable source and kernel were a success under 12-stable (though with some issues on freeze-ups and hard reboots that I suspect might be related to the bufdaemon issue and my 0x15 gen AMD cpu). Created a 13-stable poudriere jail with the knowledge that there may be issues with

13.0-CURRENT r368448 panic

Hi, Some time ago I was writting about this kernel panic. But due to the fact that there was very little information I haven't receive any reply (I hope that is was a reason). Luckily I have a host with a single interface (w/o lagg) and I was able to set up netdump. I observe this panic on all