Re: in -current is svn still canonical?

[tech-lists]

On Tue, Nov 17, 2020 at 10:57:51AM -0700, Warner Losh wrote:

For now, though, you might want to look at
https://github.com/bsdimp/freebsd-git-docs/ for the docs we do have,
especially
https://github.com/bsdimp/freebsd-git-docs/blob/main/mini-primer.md which
should answer most of your questions.


Thanks for posting this. May I suggest that it is linked somewhere off the 
section of the website that deals with updating? Particularly following -current.

Like here: 
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading.html
or here: 
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html

where someone considering following -current would see immediately that 
changes were afoot. As well as say a link off the main site, so a casual reader 
could see, too.

--
J.


signature.asc
Description: PGP signature

Re: in -current is svn still canonical?

[tech-lists]

On Tue, Nov 17, 2020 at 03:04:26AM -0800, Jeffrey Bouquet wrote:

..
Can this be put up in a wiki page as well as in each UPDATING, referencing the 
wiki page?
something like

src - current   dec 2020   now  svn up /usr/src... git 
svn cleanup  git ... [ other svn-git...
src - stable may 2021  dec 2020  svn up /usr/ports
src -releasejuly 2021
ports   dec 2021
doc dec 2021


Yeah this is what I was looking for before posting here, was surprised not to find it. 
Thought something as important as this would be linked off the main page. 
--

J.


signature.asc
Description: PGP signature

Re: /etc/os-release isn't created

[Warner Losh]

On Wed, Nov 18, 2020 at 4:16 AM Yasuhiro KIMURA  wrote:

> Dear Committers,
>
> From: Yasuhiro KIMURA 
> Subject: Re: /etc/os-release isn't created
> Date: Wed, 22 Jan 2020 15:56:54 +0900 (JST)
>
> > I created patch adding logic that handles symbolik link to mergemaster
> > and submitted it to following bug report.
> >
> > Bug 242212 usr.sbin/mergemaster/mergemaster.sh: There is no logic to
> handle symbolic
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242212
> >
> > So please review and/or test it.
>
> Would someone please commit it? As is explained currently mergemaster
> doesn't handle symbolic links. And it causes that /etc/os-release
> symbolink link isn't created when it doesn't exit before upgrade and
> you upgrade base system with steps described in /usr/src/Makefile.
> It happens such cases as following.
>
> * 13-CURRENT before r354922 -> 13-CURRENT r354922 or later
> * 12.1-RELEASE -> 12.2-RELEASE
> * 11.4-RELEASE -> 12.2-RELEASE
>

I did some light testing and it seemed to work for me, so I've gone ahead
and committed it as r367810.

Thanks for the reminder.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: in -current is svn still canonical?

[Warner Losh]

On Wed, Nov 18, 2020 at 1:47 AM Matthias Apitz  wrote:

> El día martes, noviembre 17, 2020 a las 11:05:13a. m. -0700, Warner Losh
> escribió:
>
> > > Warner, please forgive me my nearly off-topic question: When we move to
> > > git, will this conserve all the FreeBSD svn history of ci's somehow?
> Can
> > > you please point me to a document about FreeBSD's transition from svn
> to
> > > git?
> > >
> >
> > Yes. The history is preserved. As an aside, we've been exporting a git
> tree
> > for a while now, but it has so many issues in it that we decided to redo
> > the export to fix them. They weren't apparent in day-to-day grabbing of
> the
> > sources. However, when you went to do vendor-branch stuff or anything at
> > all complicated, the issues were so bad that we decided to fix them.
> >
> > For docs, I'd start here:
> > https://github.com/bsdimp/freebsd-git-docs/blob/main/mini-primer.md
> but in
> > general https://github.com/bsdimp/freebsd-git-docs/blob/main/ has
> > interesting docs that I'm working on. These are rough drafts for handbook
> > chapters. Since docs is migrating from DocBook to AsciiDoc, I did them in
> > markdown.
>
> Warner, thanks for the pointers to your docs in Git. The 2nd one does
> not work, but I can glance through the docs below
> https://github.com/bsdimp/freebsd-git-docs


Yea, that's the right one to look at... sorry for the wrong link.


> Is there also a document about how the export and setup of git was done
> for FreeBSD? I'm asking with the background that the organization I'm
> working for also is thinking in moving from svn to git. At the moment
> we're studying the pros and conts for such a step.
>

So you can get the code that FreeBSD used at
https://github.com/freebsd/git_conv/ which goes through things. This code
does a number of things that your organization likely wouldn't need to do.
It uses the latest different versions of the svn->git conversion tools.
Each has their pros and cons and part of the issue with this process was
evaluating which ones to use for the conversion. Not least because the
conversions can take quite a while with some of the less efficient tools

We don't have a paper or write-up on the nuts and bolts of this conversion,
though.

Warner

> Please let me know if there's bits that are missing that would be helpful
> > to add, or drop a pull request if you think you can improve the wording
> of
> > sections...
>
> I will do so. Thanks
>
> matthias
>
> > ___
> > freebsd-current@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "
> freebsd-current-unsubscr...@freebsd.org"
>
> --
> Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/
> +49-176-38902045
> Public GnuPG key: http://www.unixarea.de/key.pub
> Без книги нет знания, без знания нет коммунизма (Влaдимир Ильич Ленин)
> Without books no knowledge - without knowledge no communism (Vladimir
> Ilyich Lenin)
> Sin libros no hay saber - sin saber no hay comunismo. (Vladimir Ilich
> Lenin)
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: /etc/os-release isn't created

[Yasuhiro KIMURA]

Dear Committers,

From: Yasuhiro KIMURA 
Subject: Re: /etc/os-release isn't created
Date: Wed, 22 Jan 2020 15:56:54 +0900 (JST)

> I created patch adding logic that handles symbolik link to mergemaster
> and submitted it to following bug report.
> 
> Bug 242212 usr.sbin/mergemaster/mergemaster.sh: There is no logic to handle 
> symbolic
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242212
> 
> So please review and/or test it.

Would someone please commit it? As is explained currently mergemaster
doesn't handle symbolic links. And it causes that /etc/os-release
symbolink link isn't created when it doesn't exit before upgrade and
you upgrade base system with steps described in /usr/src/Makefile.
It happens such cases as following.

* 13-CURRENT before r354922 -> 13-CURRENT r354922 or later
* 12.1-RELEASE -> 12.2-RELEASE
* 11.4-RELEASE -> 12.2-RELEASE

Best Regards.

---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Samba kernel panics.

[Johan Hendriks]

On 18/11/2020 05:53, Kyle Evans wrote:

On Tue, Nov 17, 2020 at 10:01 PM Mark Johnston  wrote:

On Tue, Nov 17, 2020 at 08:19:12PM +0200, Konstantin Belousov wrote:

On Tue, Nov 17, 2020 at 06:20:31PM +0100, Johan Hendriks wrote:

Hello all after updating FreeBSD13 from r367724 to r367755 my samba server
craches the server.
I did rebuild samba 4.11 but that does not help.

The output on the console is the following.

Fatal trap 12: page fault while in kernel mode
cpuid =3; apic id = 06
fault virtual address= 0x803a122b8
fault code   = supervisor read instruction, protection
violation
instruction pointer  = 0x20:0x803a122b8
stack pointer   = 0x28:0xfe0127733a50
frame pointer  = 0x28:0x803a122b0
code segment = base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags  = 17340 (smbd)
trap number= 12
panic: page fault
cpuid =3
time = 1605632521
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_setf_wrapper+0x2b/frame
0xfe0127733700
vpanic() at vpanic+0x182/frame 0xfe0127733750
panic() at panic+0x43/frame 0xfe01277337b0
trap_fatal() at trap_fatal+0x387/frame 0xfe0127733810
trap_pfault() at trap_pfault+0x4f/frame 0xfe0127733870
trap() at trap+0x27d/frame 0xfe0127733980
calltrap() at caltrap+0x8/frame 0xfe0127733980
--- trap 0xc, rip = 0x803a122b8, rsp = 0xfe0127733a50, rbp = 0x803a122b0
---
KDB: enter: panic
[ thread pid 17340 tid 101772 ]
stopped atkdb_enter+0x37: movq $0,0x1fa9446(%rip)
db>

This looks like SMEP catching an issue, but it is not clear why.

Probably fixed by r367783?  The bug would have partially overwritten the
stack frame, resulting in a jump to a user address after a return.


Ah, yes, sorry that I missed this -- smbd was in-fact the exact
program that the reporter noted observed it with, and what the fix was
confirmed with. Sorry for the breakage~

Kyle Evans


I can confirm all is working fine again after i svnupped to r367785
Thank you all for your time.

regards
Johan

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: dma-resv.c: make does not know, how to compile

[Mateusz Piotrowski]

On 11/18/20 11:32 AM, M - Krasznai András wrote:

Hi

in the last two days I was not able to compile FreeBSD-CURRENT, make stopped 
with error:

does not know, how to compile dma-resv.c

I did not find the above file in a freshly synchromized source tree (dma-resv.h 
file does exist).


You are probably using drm-kmod and missing the following patch:

https://docs.freebsd.org/cgi/getmsg.cgi?fetch=2979410+0+/usr/local/www/mailindex/archive/2020/svn-ports-head/20201115.svn-ports-head

Basically, you probably want to update the graphics/drm-current-kmod port and install it so that all 
the required driver sources are present at /usr/local/sys/modules/drm-current-kmod.


Cheers,

Mateusz

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

dma-resv.c: make does not know, how to compile

[M - Krasznai András]

Hi

in the last two days I was not able to compile FreeBSD-CURRENT, make stopped 
with error:

does not know, how to compile dma-resv.c

I did not find the above file in a freshly synchromized source tree (dma-resv.h 
file does exist).



Üdvözlettel / with regards

Krasznai András
rendszermérnök

[M_logo]
1136 Budapest, Pannónia utca 11.
Tel:  +36 1 703 2923
Mobil: +36 30 703 2923
Központ:  +36 1 703 2920
Fax:  +36 1 703 2949
email: krasznai.and...@mands.hu

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

sdhci timeout on wakeup

[Frederic Chardon]

Hello

Any time I wake my laptop from sleep, I get these errors a dozen times
on the console.

sdhci_pci0-slot0: Controller timeout
sdhci_pci0-slot0: == REGISTER DUMP ==
sdhci_pci0-slot0: Sys addr: 0x | Version:  0xc001
sdhci_pci0-slot0: Blk size: 0x | Blk cnt:  0x
sdhci_pci0-slot0: Argument: 0x | Trn mode: 0x
sdhci_pci0-slot0: Present:  0x01f7 | Host ctl: 0x0001
sdhci_pci0-slot0: Power:0x000f | Blk gap:  0x
sdhci_pci0-slot0: Wake-up:  0x | Clock:0x4007
sdhci_pci0-slot0: Timeout:  0x | Int stat: 0x0001
sdhci_pci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb
sdhci_pci0-slot0: AC12 err: 0x | Host ctl2:0x
sdhci_pci0-slot0: Caps: 0x21fe32b2 | Caps2:0x0077
sdhci_pci0-slot0: Max curr: 0x0064 | ADMA err: 0x
sdhci_pci0-slot0: ADMA addr:0x | Slot int: 0x0001
sdhci_pci0-slot0: ===

Eventually it stops and then everything is working without issues, the
annoying part is that it takes a few minutes to wake.

This is running current at r367762, however this issue lasts since
sleeping with drm started working for me a few months ago. The laptop
is a Latitude E5430 booting through UEFI. The sd slot is empty.

Anything I could do to prevent this from happening?

Thanks
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Shutdown errors and timeout

[Mateusz Piotrowski]

On 11/16/20 7:16 PM, Johan Hendriks wrote:


On 14/11/2020 13:03, Mateusz Piotrowski wrote:

On 11/14/20 1:19 AM, Tomoaki AOKI wrote:

On Fri, 13 Nov 2020 20:04:59 +0900 (JST)
Yasuhiro KIMURA  wrote:


From: Johan Hendriks 


Hello all, i have two FreeBSD 13 machines, one is a bare metal and one
is virtualbox machine which i both update about once a week.

The vritual machine seems to fail stopping something and gives a
timeout after 90 sec.

The console ends with

Writing entropy file: .
Writing early boot entropy file: .

90 second watchdog timeout expired. Shutdown terminated.
Fri Nov13 11:20:40 CEST 2020
Nov 13 11:20:40 test-head init[1]: /etc/rc.shutdown terminated
abnormally, going to single user mode
...

On the bare metal machine i see the following.
Writing entropy file: .
Writing early boot entropy file: .
cannot unmount '/var/run': umount failed
cannot unmount '/var/log': umount failed
cannot unmount '/var': umount failed
cannot unmount '/usr/home': umount failed
cannot unmount '/usr': umount failed
cannot unmount '/': umount failed


(snip)

The pools have not been upgraded after the latest openzfs import,
maybe that is related?

FreeBSD test-freebsd-head 13.0-CURRENT FreeBSD 13.0-CURRENT #2
r367585:

First thing i noticed is about a week ago.

I'm facing same problem with 13.0-CURRENT amd64 r367487 and
virtualbox. In my case I use autofs to mount remote file system of
12.2-RELEASE amd64 server with NFSv4. When there is still filesystem
mounted by autofs, then watchdog timeout happens while shutdown. The
watchdog timeout can be worked around by executing `automount -fu`
before shutting down. But 'cannot unmount ...' error messages are
still displayed.

I added 'rc_debug="YES"' to /etc/rc.conf and checked which rc script
causes this message. Then it is displayed when following `zfs_stop`
function of /etc/rc.d/zfs is executed.

--
zfs_stop_main()
{
zfs unshare -a
zfs unmount -a
}
--

At this point syslog process still running and it opens some files
under /var/log. So it make sence that `zfs unmount -a` results in the
message.

Probably order of executing each rc script in shutdown time should be
changed so `/etc/rc.d/zfs faststop` is executed after all processes
other than `init' are exited.

This happens on stable/12, too.
As a workaround, reverting r367291 on head (r367546 on stable/12)
would stop the issue until this is really fixed.

If you have shared dataset or jail(s) mounting dataset, the workaround
would be discouraged. Read commit message for detail.


I've committed r367291 and r367546.

I am not sure if I can think of a proper fix for the described issues, so I guess the best idea 
would be to revert those changes for now until we figure out how to do it properly.



I can tell that reverting the mentioned commit i do not have the symptoms when 
i reboot my servers.
Thank you all for your time, and no sorry needed ;-)


I'll revert the commit then. I'm just waiting for an approval from a src 
committer.

Best,

Mateusz

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: in -current is svn still canonical?

[Matthias Apitz]

El día martes, noviembre 17, 2020 a las 11:05:13a. m. -0700, Warner Losh 
escribió:

> > Warner, please forgive me my nearly off-topic question: When we move to
> > git, will this conserve all the FreeBSD svn history of ci's somehow? Can
> > you please point me to a document about FreeBSD's transition from svn to
> > git?
> >
> 
> Yes. The history is preserved. As an aside, we've been exporting a git tree
> for a while now, but it has so many issues in it that we decided to redo
> the export to fix them. They weren't apparent in day-to-day grabbing of the
> sources. However, when you went to do vendor-branch stuff or anything at
> all complicated, the issues were so bad that we decided to fix them.
> 
> For docs, I'd start here:
> https://github.com/bsdimp/freebsd-git-docs/blob/main/mini-primer.md  but in
> general https://github.com/bsdimp/freebsd-git-docs/blob/main/ has
> interesting docs that I'm working on. These are rough drafts for handbook
> chapters. Since docs is migrating from DocBook to AsciiDoc, I did them in
> markdown.

Warner, thanks for the pointers to your docs in Git. The 2nd one does
not work, but I can glance through the docs below
https://github.com/bsdimp/freebsd-git-docs

Is there also a document about how the export and setup of git was done
for FreeBSD? I'm asking with the background that the organization I'm
working for also is thinking in moving from svn to git. At the moment
we're studying the pros and conts for such a step.

> 
> Please let me know if there's bits that are missing that would be helpful
> to add, or drop a pull request if you think you can improve the wording of
> sections...

I will do so. Thanks

matthias

> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
Без книги нет знания, без знания нет коммунизма (Влaдимир Ильич Ленин)
Without books no knowledge - without knowledge no communism (Vladimir Ilyich 
Lenin)
Sin libros no hay saber - sin saber no hay comunismo. (Vladimir Ilich Lenin)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"