Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: request" leads to panic [now fixed]

On Wed, Feb 14, 2024 at 06:19:04PM -0800, Mark Millard wrote: > Your changes have the RPi4B that previously got the > panic to boot all the way instead. Details: > > I have updated my pkg base environment to have the > downloaded kernels (and kernel source) with your > changes and have booted

Re: ZFS problems since recently ?

On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote: > Please see/test: https://github.com/openzfs/zfs/pull/15732 . Looks like that has landed in current: commit f552d7adebb13e24f65276a6c4822bffeeac3993 Merge: 13720136fbf a382e21194c Author: Martin Matuska

Re: ZFS problems since recently ?

On Tue, Jan 02, 2024 at 08:02:04PM -0800, John Kennedy wrote: > On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote: > > On 01.01.2024 08:59, John Kennedy wrote: > > > ... > > >My poudriere build did eventually fail as well: > > > ... > &g

Re: ZFS problems since recently ?

On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote: > On 01.01.2024 08:59, John Kennedy wrote: > > ... > >My poudriere build did eventually fail as well: > > ... > > [05:40:24] [01] [00:17:20] Finished devel/gdb@py39 | gdb-13.2_1: Success &g

Re: ZFS problems since recently ?

On Mon, Jan 01, 2024 at 02:27:17PM +0100, Kurt Jaeger wrote: > > On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote: > > > markj@ pointed me in > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 > > > to > > > https://github.com/openzfs/zfs/pull/15719 > > > > > > So it will

Re: ZFS problems since recently ?

On Mon, Jan 01, 2024 at 08:42:26AM -0800, John Kennedy wrote: > Applying the two ZFS kernel patches fixes that issue: commit 09af4bf2c987f6f57804162cef8aeee05575ad1d (zfs: Fix SPA sysctl handlers) landed too. root@bsd15:~ # sysctl -a | grep vfs.zfs.

Re: ZFS problems since recently ?

On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote: > > > I can crash mine with "sysctl -a" as well. > > markj@ pointed me in > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 > to > https://github.com/openzfs/zfs/pull/15719 > > So it will probably be fixed sooner or later.

Re: ZFS problems since recently ?

On Mon, Jan 01, 2024 at 02:27:17PM +0100, Kurt Jaeger wrote: > Do you have >vfs.zfs.dmu_offset_next_sync=0 I didn't initially, I do now. Like I said, I haven't been following that one 100%. I know it isn't block-clone per say, so much as some underlying problem it pokes with a pointy

Re: ZFS problems since recently ?

On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote: > markj@ pointed me in > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 > to > https://github.com/openzfs/zfs/pull/15719 > > So it will probably be fixed sooner or later. > > The other ZFS crashes I've seen are still an

Re: ZFS problems since recently ?

> I can crash mine with "sysctl -a" as well. Smaller test, this is sufficient to crash things: root@bsd15:~ # sysctl vfs.zfs.zio vfs.zfs.zio.deadman_log_all: 0 vfs.zfs.zio.dva_throttle_enabled: 1 vfs.zfs.ziopanic: sbuf_clear makes no sense on sbuf

Re: ZFS problems since recently ?

On Sun, Dec 31, 2023 at 07:34:45PM +0100, Kurt Jaeger wrote: > Hi! > > Short overview: > - Had CURRENT system from around September > - Upgrade on the 23th of December > - crashes in ZFS, see > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261538 > for details > - Reinstalled from scratch

Re: Accessibility in the FreeBSD installer and console

On Thu, Jul 07, 2022 at 10:11:52PM +0200, Klaus Küchemann wrote: > > Am 07.07.2022 um 19:32 schrieb Hans Petter Selasky : > > The only argument I've heard from some non-sighted friends about not using > > FreeBSD natively is that ooh, MacOSX is so cool. It starts speaking from > > the start if I

Re: Accessibility in the FreeBSD installer and console

On Thu, Jul 07, 2022 at 10:11:52PM +0200, Klaus Küchemann wrote: > > Am 07.07.2022 um 19:32 schrieb Hans Petter Selasky : > > The only argument I've heard from some non-sighted friends about not using > > FreeBSD natively is that ooh, MacOSX is so cool. It starts speaking from > > the start if I

Re: Problems with getting a crash dump

On Mon, Nov 08, 2021 at 07:08:31PM +, Alexander wrote: > Hello, I am currently using FreeBSD 14.0-CURRENT and I found a bug that > triggers a kernel panic. I wanted to make a kernel crash dump to further > investigate the issue, but after a few tries I still did not manage to do it. > I

Re: URL for stable/13

On Tue, Mar 02, 2021 at 08:18:23AM -0800, bob prohaska wrote: > A while back I obtained a buildable source tree for stable/13 > but it hasn't been updated in the last few days. Running > git remote show origin > reports in part > . > Local branch configured for 'git pull': > stable/13

Re: HEADS-UP: PIE enabled by default on main

On Sun, Feb 28, 2021 at 09:40:54AM -0500, Shawn Webb wrote: > ... The point of ASLR is to combine it with W^X. Without W^X, ASLR makes > no sense. FreeBSD recently gained a W^X implementation that requires > opt-in. ... I'm not plugged into the right places to catch some of these things up

Re: HEADS-UP: PIE enabled by default on main

On Fri, Feb 26, 2021 at 10:10:28AM +1100, Greg 'groggy' Lehey wrote: > On Thursday, 25 February 2021 at 15:58:07 -0500, Ed Maste wrote: > > As of 9a227a2fd642 (main-n245052) base system binaries are now built > > as position-independent executable (PIE) by default, for 64-bit > > architectures.

Re: zpool upgrade can't enable new features

On Thu, Feb 25, 2021 at 11:09:17AM -0300, Renato Botelho wrote: > I recently upgraded a CURRENT system to main-n244932-248a47a4c2f and > zpool status shows: > >pool: zroot > state: ONLINE > status: Some supported and requested features are not enabled on the pool. > The pool can

Re: gib/em driver problems?

On Wed, Feb 03, 2021 at 08:23:49PM -0800, John Kennedy wrote: > On Wed, Feb 03, 2021 at 06:40:50PM -0800, joe mcguckin wrote: > > I went out and purchased a PCIe ethernet card - it uses the em driver. The > > system > > boots and it is em0. > > > > It works f

Re: gib/em driver problems?

On Wed, Feb 03, 2021 at 06:40:50PM -0800, joe mcguckin wrote: > I went out and purchased a PCIe ethernet card - it uses the em driver. The > system > boots and it is em0. > > It works fine in 100Mb mode, but in gigabit mode, it does not pass any > traffic although ifconfig reports > the card

Re: ZFS feature compatibility?

ead I had a while ago: Date: Thu, 9 Jul 2020 14:18:54 -0700 From: John Kennedy To: Kyle Evans Cc: FreeBSD-STABLE Mailing List Subject: Re: 12.1p7 no longer boots after doing zpool upgrade -a The "new" documentation was here: https://wiki.free

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: 13-alpha2 libncurses removal breaks ports build

On Sun, Jan 24, 2021 at 02:53:41PM +, Kostya Berger wrote: > OK, building ports against a clean installation of 13.0-ALPHA2 has no problem > with ncurses. > But devel/glib20 fails for no obvious reason closer to the end of building > process... I just wonder: do I need to report this to

Re: Which branch in git is 13.0-current?

On Sat, Jan 23, 2021 at 06:34:58PM -0700, Russell L. Carter wrote: > So has anyone tracking stable/12 and ports successfully completed the > git checkout stable/13; make buildworld; make installworld; mergemaster > drill? I see I can checkout stable/13. > > Do make.conf | src.conf | GENERIC have

Re: 13-alpha2 libncurses removal breaks ports build

On Sat, Jan 23, 2021 at 10:40:57PM +, Kostya Berger wrote: > Hi everyone,I don't seem to find any mentioning in the /usr/ports/UPDATING > about how one should handle the removal of libncurses.so.9 from base. > Source UPDATING only says:ncurses installation has been modified to only keep >

Re: boot loader blank screen

On Fri, Jan 15, 2021 at 03:51:38PM +0200, Toomas Soome wrote: > Could you please check latest current now?:) Success! With main-c255999-g0bc776f3da70, I've been able to comment out the screen.textmode=0 (so, back to the default like I originally was).

Re: boot loader blank screen

On Wed, Jan 06, 2021 at 02:19:12PM -0800, John Kennedy wrote: > I saw your commit of 99870c70bac7 (loader: rewrite vidc_install_font), > 31c2bcad7e44 (loader: remove left over call to unsetenv()), and belatedly > babda0952f8355a89b3241d5e8943c7da0fa4f6b (hw.vga.textmode -> scr

Re: boot loader blank screen

On Wed, Jan 06, 2021 at 02:40:32PM -0800, Mark Millard wrote: > ... screen.textmode="0" works, including with screen.font="8x16" . There > is a difference, in that it displays some material at the very beginning > that it was not displaying since the recent problems started (until now > or so).

Re: boot loader blank screen

On Tue, Jan 05, 2021 at 07:09:22PM -0800, John Kennedy wrote: > On Wed, Jan 06, 2021 at 12:46:08AM +0200, Toomas Soome wrote: > > I think, I got it fixed (at least idwer did confirm for his system, > > thanks). If you can test this patch: > > http://148-52-235-80.sta.

Re: boot loader blank screen

On Wed, Jan 06, 2021 at 12:46:08AM +0200, Toomas Soome wrote: > I think, I got it fixed (at least idwer did confirm for his system, thanks). > If you can test this patch: > http://148-52-235-80.sta.estpak.ee/0001-loader-rewrite-font-install.patch >

Re: boot loader blank screen

Op ma 4 jan. 2021 om 23:59 schreef Toomas Soome : > the 58661b3ba9eb should hopefully fix the loader text mode issue, it would be > cool if you can verify:) No, sorry... On Tue, Jan 05, 2021 at 02:58:02AM +0100, Idwer Vollering wrote: > I had more success with this patch, applied on top of

Re: git non-time-sequential logs

On Mon, Jan 04, 2021 at 07:59:12PM +0100, Franco Fichtner wrote: > The author date stays the same, the committer date is sequential except > that it indicates the local time of the committer doing the cherry-pick > instead of the central server as opposed to svn: > > # git log --format=fuller

Re: boot loader blank screen

On Mon, Jan 04, 2021 at 11:39:08AM -0700, Warner Losh wrote: > Yea, this is a feature that needs to be fixed since black on black text is > a show stopper :( Ah, this is part of the "Terminal colours in current" thread? I saw that, but didn't correlate it with default black-on-black text. It

Re: boot loader blank screen

On Mon, Jan 04, 2021 at 06:30:38PM +0200, Toomas Soome wrote: > Yes, it is known defect, and I???m searching for cause; the issue is with > /boot/loader and BIOS text mode (unfortunately I have the usual ???but it is > working for me??? case). For workaround, you can try to either: 1 (blind) >

git non-time-sequential logs

On Mon, Jan 04, 2021 at 08:22:56AM -0800, John Kennedy wrote: > The git logs in /usr/src aren't time-sequential, so maybe I shouldn't trust > those dates above (I pulled it ~Jan 3rd and let it compile overnight), but > I'm going to repull all the sources and recompile, just in case.

boot loader blank screen

This is a little weird. Somewhere between 13.0-g2ff66a915526 (Dec 30th) and -gd03fd8ede2c4 (Dec 29th), I've lost the screen in the boot loader. This is really weird because I didn't update the boot loader (in quite a while, actually), but I suppose it might drag some stuff off of the disk and

Re: # Fssh_packet_write_wait: Connection to 77.183.250.3 port 22: Broken pipe

On Wed, Dec 30, 2020 at 08:04:03AM +0100, Hartmann, O. wrote: > On recent 12-STABLE, 12.1-RELENG and 12.2-RELENG I face a very nasty problem > which > occured a while ago after it seemed to have vanished for a while: running ssh > in a xterm > on FreeBSD boxes as mentioned at the beginning ends

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

On Mon, Dec 21, 2020 at 12:47:38PM -0800, John Kennedy wrote: > On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote: > > The FreeBSD project will be moving it's source repo from subversion to git > > starting this this weekend. The docs repo was moved 2 weeks ago. The

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

Attributions are really confusing at this point... On 2020-Dec-22, at 13:06, bob prohaska wrote: > bob@www:/usr % git clone cgit.freebsd.org -b stable/12 freebsd-src On 2020-Dec-22, at 13:31, Mark Millard wrote: > I cloned FreeBSD's src.git via: > git clone -o freebsd --config >

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote: > The FreeBSD project will be moving it's source repo from subversion to git > starting this this weekend. The docs repo was moved 2 weeks ago. The ports > repo will move at the end of March, 2021 due to timing issues. ... I filed Bug

Re: (239489) buildkernel fails if PORTS_MODULES= includes openzfs-kmod

On Sun, Dec 13, 2020 at 06:49:07PM +, Graham Perrin wrote: > Not entirely moot; for > the description for > the most recent commit refers to building on 13-CURRENT Well, it's a port, so they'll want it to compile if nothing else. It just

Re: (239489) buildkernel fails if PORTS_MODULES= includes openzfs-kmod

On Sun, Dec 13, 2020 at 08:19:30AM +, Graham Perrin wrote: > Please: is there some way to include openzfs-kmod at buildkernel time? > > To work around > I habitually > remove openzfs-kmod from /etc/src.conf _and_ modify

Re: AMNESIA:33 and FreeBSD TCP/IP stack involvement

On Wed, Dec 09, 2020 at 06:58:49AM +0100, Hartmann, O. wrote: > Hello, > I've got a question about recently discovered serious vulnerabilities > in certain TCP stack implementations, designated as AMNESIA:33 (as far > as I could follow the recently made announcements and statements, > please see,

Re: KLD zfs.ko: depends on kernel - not available or version mismatch

On Tue, Dec 08, 2020 at 07:10:26PM +0100, Alban Hertroys wrote: > > You didn't say that you've installed the new kernel, which at least starts > > you down the road towards a driver/kernel mismatch. You presumably have a > > non-ZFS boot+root. > > I???m fairly sure I did, actually. > > Last

Re: KLD zfs.ko: depends on kernel - not available or version mismatch

On Tue, Dec 08, 2020 at 08:56:25AM +0100, Alban Hertroys wrote: > This seems to have gotten lost in the moderate queue, but after a week I am > no closer to a solution, so here???s a resend: > > I???ve been trying to get a fresh world running (for the eventual purpose of > running amdgpu

Re: immediate panic after nvidia load

On Tue, Nov 10, 2020 at 05:58:15AM -0800, David Wolfskill wrote: > What I do on my laptop is build FreeBSD from source, with he directive > in /etc/src.conf so the x11/nvidia0driver kmod is rebuilt during "make > buildkernel" (and installed during "make installkernel"). > > That's simple and

Re: r367415: can't load linuxulator, link_elf_obj: symbol sdt_provider_linuxulator undefined

On Fri, Nov 06, 2020 at 08:35:41AM -0800, John Kennedy wrote: > Trying a run against r367420 with the LIN_SDT_PROVIDER_DECLARE() commented > out. Not the solution. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/m

Re: r367415: can't load linuxulator, link_elf_obj: symbol sdt_provider_linuxulator undefined

On Fri, Nov 06, 2020 at 08:35:41AM -0800, John Kennedy wrote: > I had this crop up this morning r367410, while yesterdays build against > r367379 seemed fine. I think this is an issue because of r367395: > > linux(4): Deduplicate unimpl/dummy syscall handlers > > If

r367415: can't load linuxulator, link_elf_obj: symbol sdt_provider_linuxulator undefined

I had this crop up this morning r367410, while yesterdays build against r367379 seemed fine. I think this is an issue because of r367395: linux(4): Deduplicate unimpl/dummy syscall handlers If I tracked it down correctly, the LIN_SDT_PROVIDER_DECLARE(LINUX_DTRACE) in

Re: Failing to retrieve source tarballs for anything.

On Sun, Sep 02, 2018 at 07:58:16AM +1200, Jonathan Chen wrote: > On 2 September 2018 at 05:25, Alex McKeever > wrote: > > After compiling PKG, when I go to ports to compile anything (my eMac can > > run FreeBSD but not modern Linux due to the version of the Radeon GPU) it > > fails to retrieve

Re: IDE DVD playback on 5.1-CURRENT

On Tue, Aug 26, 2003 at 09:31:45PM -0400, Adam K Kirchhoff wrote: I've asked this same question on freebsd-questions an on #freebsd (freenode), but haven't gotten any answer, so I thought I'd ask on here. ... Is DVD playback just not supported on IDE drives on FreeBSD -CURRENT? This is