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

Graham Perrin grahamperrin at gmail.com wrote on Mon Jan 25 22:08:53 UTC 2021 : . . . omitted material, including steps 01..13 . . . Your steps 01..13 make no mention of involving growfs as indicated in "man 8 growfs". I'd guess that the growfs step would be after step 8 (recover) and before 10

Re: Can't fetch https://www.freebsd.org/releng/index.html

On 27.01.2021 3:40, KIRIYAMA Kazuhiko wrote: I've been used https://www.freebsd.org/releng/index.html to know about latest FreeBSD updateing status for my many applications. I found that index.html can't fetch yesterday. Is there anyone to tell me how to get latest FreeBSD updateing status

Can't fetch https://www.freebsd.org/releng/index.html

Hi all, I've been used https://www.freebsd.org/releng/index.html to know about latest FreeBSD updateing status for my many applications. I found that index.html can't fetch yesterday. Is there anyone to tell me how to get latest FreeBSD updateing status information with source file ? ---

Re: FYI: Why META_MODE rebuilds so much for building again after installworld (no source changes)

On 2021-Jan-23, at 21:37, Mark Millard wrote: > On 2021-Jan-22, at 01:45, Mark Millard wrote: > >> Given an already built, installed and booted system version, I've >> noted a big difference for META_MODE in 2 rebuild contexts (no >> source updates involved): >> >> *) Prior buildworld

Re: fsck strange output

> From: Rozhuk Ivan > Date: Tue, 26 Jan 2021 17:08:41 +0300 > To: Kirk McKusick > Cc: freebsd-current@freebsd.org > Subject: Re: fsck strange output > > On Mon, 25 Jan 2021 15:40:12 -0800 > Kirk McKusick wrote: > > >> Please try this patch to fsck_ffs and see if it fixes your problem. >> >>

Re: loading drm crashes system

Me: > Try September 26 as a reference date. s/September 26/September 6/ ; src = r365372 Respectfully, Robert "Gotcha, ya little bugger!" Huff ___ freebsd-current@freebsd.org

Re: loading drm crashes system

On Mon, 25 Jan 2021 22:21:16 -0500 Robert Huff wrote: > 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?

Re: loading drm crashes system

On Tue, 26 Jan 2021 13:42:45 +0100 Emmanuel Vadot wrote: > On Tue, 26 Jan 2021 07:02:11 + > Alexey Dokuchaev wrote: >> 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,

Re: problem building virtualbox-ose-kmod

On 26/01/21 13:29, Dima Panov wrote: Moin! Stefan, please add check for __FreeBSD_version and fill PR or commit it directly with ports-secteam approval. There's a bug report for this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252675 And another one which is marked as a duplicate

Re: fsck strange output

On Mon, 25 Jan 2021 15:40:12 -0800 Kirk McKusick wrote: > Please try this patch to fsck_ffs and see if it fixes your problem. > > Kirk McKusick > > =-=-= > > *** sbin/fsck_ffs/inode.c.orig2021-01-07 15:04:04.969086284 > -0800 --- sbin/fsck_ffs/inode.c 2021-01-25

Re: svnlite behaviour changed?

Thanks! I did not make it very clear but the whole thing started when I used FreeBSD-CURRENT - that is sometime in December I observed that although the revision number is increased, there are no updates listed; the fact that the revision number is the revision of the whole repository and not

Re: loading drm crashes system

Hello: > > 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 promised to >

Re: DRM and Radeon

W dniu 26.01.2021 o 10:15, Toomas Soome pisze: On 26. Jan 2021, at 10:18, Marek Zarychta > wrote: W dniu 26.01.2021 o 08:58, Graham Perrin pisze: On 26/01/2021 07:02, Alexey Dokuchaev wrote: > Re: loading drm crashes system > … There are known issues

Re: loading drm crashes system

On Tue, 26 Jan 2021 07:02:11 + Alexey Dokuchaev wrote: > 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,

Re: problem building virtualbox-ose-kmod

Moin! Stefan, please add check for __FreeBSD_version and fill PR or commit it directly with ports-secteam approval. -- Dima. (desktop, kde, x11, office, ports-secteam)@FreeBSD team (flu...@freebsd.org, https://t.me/dima_panov) > On Tuesday, Jan 26, 2021 at 8:37 PM, Stefan Esser

Re: svnlite behaviour changed?

On Tue, Jan 26, 2021 at 09:52:15AM +, M - Krasznai András wrote: > Good morning! > > I regularly sync my FreeBSD source tree with the central repository using svn > update. I use a one-lis script to synchonize, which sends the output of svn > to a file, and also copies to the console. This

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

Re: svnlite behaviour changed?

Good morning! > I regularly sync my FreeBSD source tree with the central repository using svn > update. I use a one-lis script to synchonize, which sends the output of svn > to a file, and also copies to the console. This list contained - according to > the 'svn help update' - one

Re: problem building virtualbox-ose-kmod

Am 26.01.21 um 07:34 schrieb monochrome: 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

svnlite behaviour changed?

Good morning! I regularly sync my FreeBSD source tree with the central repository using svn update. I use a one-lis script to synchonize, which sends the output of svn to a file, and also copies to the console. This list contained - according to the 'svn help update' - one line for any item

tools/toos/{zfsboottest|bootparttest} build broken

Hi, root@hostname:/usr/src/tools/tools/bootparttest # make [Creating objdir /usr/obj/usr/src/amd64.amd64/tools/tools/bootparttest...] make: don't know how to make crc32.c. Stop make: stopped in /usr/src/tools/tools/bootparttest root@hostname:/usr/src/tools/tools/zfsboottest # make ln -sf

Re: DRM and Radeon

> On 26. Jan 2021, at 10:18, Marek Zarychta > wrote: > > W dniu 26.01.2021 o 08:58, Graham Perrin pisze: >> 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

Re: fsck strange output

Rozhuk Ivan rozhuk.im at gmail.com wrote on Tue Jan 26 00:58:07 UTC 2021 : > This happen on 4 different systems, that: > - based on Ryzen zen/zen+ > - FreeBSD 13 > > 2 systems have ECC that works and show no errors. This is just a example-contexts note: I've seen what appears to be the same

Re: problem building virtualbox-ose-kmod

On 1/26/21 9:13 AM, Mark Millard via freebsd-current wrote: monochrome monochrome at twcny.rr.com wrote on Tue Jan 26 06:34:23 UTC 2021 : . . . for quite a while now, maybe over a month . . . --- memobj-r0drv-freebsd.o ---

Re: DRM and Radeon

W dniu 26.01.2021 o 08:58, Graham Perrin pisze: 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

Re: problem building virtualbox-ose-kmod

monochrome monochrome at twcny.rr.com wrote on Tue Jan 26 06:34:23 UTC 2021 : > . . . for quite a while now, maybe over a month . . . > --- memobj-r0drv-freebsd.o --- >