Re: Is there any machine RISC-V implemented ?

2020-12-24 Thread Mehmet Erol Sanliturk
On Fri, Dec 25, 2020 at 3:43 AM KIRIYAMA Kazuhiko wrote: > Hi, all > > I've found RISC-V images in snapshots/ISO-IMAGES. Is there > any machine RISC-V implemented so far ? > ___ > > Please , search the following phrase in Google : Is there any

Re: Boot panic on Lenovo P50s since r367998

2020-12-24 Thread Marc Veldman
> On 25 Dec 2020, at 01:02, Tomoaki AOKI wrote: > > On Thu, 24 Dec 2020 10:34:49 +0100 > Marc Veldman wrote: > >> Hello, >> >> since r367998 my Lenovo P50s panics on boot: >> >> mmc0: detached >> panic: Bad link elm 0xf80003a73300 next->prep != elm >> cupid=3 >> time=2 >> KDB: stack

Re: Boot panic on Lenovo P50s since r367998

2020-12-24 Thread Marc Veldman
> On 25 Dec 2020, at 00:04, Yuri Pankov wrote: > > Marc Veldman wrote: >> Hello, >> since r367998 my Lenovo P50s panics on boot: >> mmc0: detached >> panic: Bad link elm 0xf80003a73300 next->prep != elm >> cupid=3 >> time=2 >> KDB: stack backtrace: >> db_trace_self_wrapper() at

Is there any machine RISC-V implemented ?

2020-12-24 Thread KIRIYAMA Kazuhiko
Hi, all I've found RISC-V images in snapshots/ISO-IMAGES. Is there any machine RISC-V implemented so far ? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: Boot panic on Lenovo P50s since r367998

2020-12-24 Thread Yuri Pankov
Yuri Pankov wrote: Tomoaki AOKI wrote: On Thu, 24 Dec 2020 10:34:49 +0100 Marc Veldman wrote: Hello, since r367998 my Lenovo P50s panics on boot: mmc0: detached panic: Bad link elm 0xf80003a73300 next->prep != elm cupid=3 time=2 KDB: stack backtrace: db_trace_self_wrapper() at

Re: Boot panic on Lenovo P50s since r367998

2020-12-24 Thread Yuri Pankov
Tomoaki AOKI wrote: On Thu, 24 Dec 2020 10:34:49 +0100 Marc Veldman wrote: Hello, since r367998 my Lenovo P50s panics on boot: mmc0: detached panic: Bad link elm 0xf80003a73300 next->prep != elm cupid=3 time=2 KDB: stack backtrace: db_trace_self_wrapper() at

Re: git and the loss of revision numbers

2020-12-24 Thread Thomas Mueller
> Disclaimer: I just started to learn git, never used it before. > If I do understand it correctly, the switch from svn to git comes with a loss > of continuously increasing revision numbers. Correct? If so I wonder how > future security advisories and errata notices will be composed. Will

Re: Boot panic on Lenovo P50s since r367998

2020-12-24 Thread Tomoaki AOKI
On Thu, 24 Dec 2020 10:34:49 +0100 Marc Veldman wrote: > Hello, > > since r367998 my Lenovo P50s panics on boot: > > mmc0: detached > panic: Bad link elm 0xf80003a73300 next->prep != elm > cupid=3 > time=2 > KDB: stack backtrace: > db_trace_self_wrapper() at

Re: Boot panic on Lenovo P50s since r367998

2020-12-24 Thread Yuri Pankov
Marc Veldman wrote: Hello, since r367998 my Lenovo P50s panics on boot: mmc0: detached panic: Bad link elm 0xf80003a73300 next->prep != elm cupid=3 time=2 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0x8299a9c0 vpanic() at vpanic+0x181/frame

[LAST OFFICIAL REMINDER] Call for 2020Q4 quarterly status reports

2020-12-24 Thread Daniel Ebdrup Jensen
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is December, 31st 2021 for work done since the last round of Quarterly Reports: October 2020 - December 2020. I would like to remind you that reports are collected during the last month of every quarter. Status

Re: referencing one commit in another for git

2020-12-24 Thread Yuri Pankov
Warner Losh wrote: On Wed, Dec 23, 2020 at 6:22 PM Jan Beich wrote: Warner Losh writes: On Wed, Dec 23, 2020, 3:21 PM Alan Somers wrote: On Wed, Dec 23, 2020 at 3:16 PM Rick Macklem wrote: Hi, So I just did my first git commit. Pretty scary, but it looks ok. Now, how do I

Re: git and the loss of revision numbers

2020-12-24 Thread Christian Weisgerber
Michael Grimm: > If I do understand it correctly, the switch from svn to git comes with a loss > of continuously increasing revision numbers. Correct. > Correct? If so I wonder how future security advisories and errata notices > will be composed. Will there be a date of the commit besides its

Git and uname(1)

2020-12-24 Thread Graham Perrin
On 24/12/2020 14:15, Michael Grimm wrote: … In the past I could easily judge if there was a need to buildworld or buildkernel: If uname shows a smaller revision number than those in advisories or notices. … I see Rainer Hurling's response to John Kennedy at

Git commits/revisions: sequential numbering: git-rev-list(1) --count

2020-12-24 Thread Graham Perrin
On 24/12/2020 14:11, Michael Grimm wrote: … Disclaimer: I just started to learn git, never used it before. If I do understand it correctly, the switch from svn to git comes with a loss of continuously increasing revision numbers. Correct? … Yes and no.

Re: git and the loss of revision numbers

2020-12-24 Thread grarpamp
> loss of continuously increasing revision numbers git rev-list --count HEAD git describe --tags / parent Plus a bunch of similar ways to do it, from different points, in different formats, search internet for them all... git revision version numbering... Some deploy structured metadata in tag

Re: git and the loss of revision numbers

2020-12-24 Thread Michael Grimm
Correction: > On 24. Dec 2020, at 15:11, Michael Grimm wrote: > > In the past I could easily judge if there was a need to buildworld or > buildkernel: If uname shows a larger revision number than those in advisories > or notices. In the past I could easily judge if there was a need to

git and the loss of revision numbers

2020-12-24 Thread Michael Grimm
Hi Disclaimer: I just started to learn git, never used it before. If I do understand it correctly, the switch from svn to git comes with a loss of continuously increasing revision numbers. Correct? If so I wonder how future security advisories and errata notices will be composed. Will there be

Boot panic on Lenovo P50s since r367998

2020-12-24 Thread Marc Veldman
Hello, since r367998 my Lenovo P50s panics on boot: mmc0: detached panic: Bad link elm 0xf80003a73300 next->prep != elm cupid=3 time=2 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0x8299a9c0 vpanic() at vpanic+0x181/frame 0x8299aa10