Tachyum Prodigy processors
Hi everybody, does anyone have any information regarding the new Tachyum Prodigy processors? They have announced FreeBSD support as well as a porting kit of their instruction set architecture for FreeBSD: https://www.tachyum.com/en-eu/media/press-releases/2022/04/05/tachyum-successfully-runs-freebsd-in-prodigy-ecosystem-expands-open-source-os-support/ They are also offering pre-orders for their evaluation platform: https://www.tachyum.com/media/press-releases/2022/06/01/tachyum-begins-pre-orders-for-prodigy-evaluation-platform/ If their proclamations and statements about Prodigy's performance and features are right this might be the next game-changer in the server industry. Cheers, mm
Re: Tachyum Prodigy processors
Hi! > does anyone have any information regarding the new Tachyum Prodigy > processors? golem had an article 3 days ago (written in german), which was detailled enough to trigger my interest. https://www.golem.de/news/tachyum-prodigy-t16128-der-wunderkind-prozessor-2206-165307.html -- p...@opsec.eu+49 171 3101372Now what ?
review: kernel GDB: do not reboot the target
I would like to call attention to this change to prevent accidentally rebooting the target of remote kernel GDB. The code is mundane, but the default could be controversial. https://reviews.freebsd.org/D35473 Please comment on the review, not on this thread. If you need an account on Phabricator, see: https://wiki.freebsd.org/Phabricator Cheers, Eric
Re: dmesg: ACPI Warning: Firmware issue warning spaming
> What do you think opening a review about this fix/tweak to stop this > spamming that blinds dmesg? > >> > I'm running CURRENT 8d95f500521 and I'm receiving loads of dmesg >> warnings: >> > --- >> > ACPI Warning: Firmware issue: Excessive sleep time (0x0010 >> ms > >> > 10 ms) in ACPI Control Method (20220331/exsystem-347) >> > --- >> > Is there a way to silence it? I think this spam message is from linux. So, I think we should discuss on linux forum but I don't familier to linux. -- Masachika ISHIZUKA
How to supress prompt on bc 5.3.1
I updated to master-n256084-5dd1f6f1441 (1400061) and this leads to bc to 5.3.1. Previosly, 'BC-ENV-APRG=-P' or 'bc -P' were working but it doesn't work on 5.3.1. Is there any way to supress prompt ? -- Masachika ISHIZUKA
Re: dmesg: ACPI Warning: Firmware issue warning spaming
On 22. 6. 13., Masachika ISHIZUKA wrote: What do you think opening a review about this fix/tweak to stop this spamming that blinds dmesg? I'm running CURRENT 8d95f500521 and I'm receiving loads of dmesg warnings: --- ACPI Warning: Firmware issue: Excessive sleep time (0x0010 ms > 10 ms) in ACPI Control Method (20220331/exsystem-347) --- Is there a way to silence it? I think this spam message is from linux. So, I think we should discuss on linux forum but I don't familier to linux. FYI, both FreeBSD and Linux use ACPICA to implement ACPI. https://acpica.org This message was added by this commit: https://github.com/acpica/acpica/commit/2a0d1d475e7ea1c815bee1e0692d81db9a7c909c You can file your complaints here if it is really bothering you. https://github.com/acpica/acpica/issues Jung-uk Kim
Re: dmesg: ACPI Warning: Firmware issue warning spaming
On 22. 6. 13., Jung-uk Kim wrote: On 22. 6. 13., Masachika ISHIZUKA wrote: What do you think opening a review about this fix/tweak to stop this spamming that blinds dmesg? I'm running CURRENT 8d95f500521 and I'm receiving loads of dmesg warnings: --- ACPI Warning: Firmware issue: Excessive sleep time (0x0010 ms > 10 ms) in ACPI Control Method (20220331/exsystem-347) --- Is there a way to silence it? I think this spam message is from linux. So, I think we should discuss on linux forum but I don't familier to linux. FYI, both FreeBSD and Linux use ACPICA to implement ACPI. https://acpica.org This message was added by this commit: https://github.com/acpica/acpica/commit/2a0d1d475e7ea1c815bee1e0692d81db9a7c909c You can file your complaints here if it is really bothering you. https://github.com/acpica/acpica/issues BTW, it seems it was discussed on Linux ML. https://lore.kernel.org/lkml/cajz5v0gwyz_bsonhlgt7l4wpqvxlvyobppte1nx6ponsgn4...@mail.gmail.com/T/#mae6a816bbcebb01dea9e5c19c81e9be872cad521 I am not sure what happened after that. Jung-uk Kim OpenPGP_signature Description: OpenPGP digital signature
Re: dmesg: ACPI Warning: Firmware issue warning spaming
On 22. 6. 13., Jung-uk Kim wrote: On 22. 6. 13., Jung-uk Kim wrote: On 22. 6. 13., Masachika ISHIZUKA wrote: What do you think opening a review about this fix/tweak to stop this spamming that blinds dmesg? I'm running CURRENT 8d95f500521 and I'm receiving loads of dmesg warnings: --- ACPI Warning: Firmware issue: Excessive sleep time (0x0010 ms > 10 ms) in ACPI Control Method (20220331/exsystem-347) --- Is there a way to silence it? I think this spam message is from linux. So, I think we should discuss on linux forum but I don't familier to linux. FYI, both FreeBSD and Linux use ACPICA to implement ACPI. https://acpica.org This message was added by this commit: https://github.com/acpica/acpica/commit/2a0d1d475e7ea1c815bee1e0692d81db9a7c909c You can file your complaints here if it is really bothering you. https://github.com/acpica/acpica/issues BTW, it seems it was discussed on Linux ML. https://lore.kernel.org/lkml/cajz5v0gwyz_bsonhlgt7l4wpqvxlvyobppte1nx6ponsgn4...@mail.gmail.com/T/#mae6a816bbcebb01dea9e5c19c81e9be872cad521 I am not sure what happened after that. I found the author actually filed a pull request to revert the commit. https://github.com/acpica/acpica/pull/780 Jung-uk Kim OpenPGP_signature Description: OpenPGP digital signature
Re: dmesg: ACPI Warning: Firmware issue warning spaming
On 22. 6. 13., Jung-uk Kim wrote: On 22. 6. 13., Jung-uk Kim wrote: On 22. 6. 13., Jung-uk Kim wrote: On 22. 6. 13., Masachika ISHIZUKA wrote: What do you think opening a review about this fix/tweak to stop this spamming that blinds dmesg? I'm running CURRENT 8d95f500521 and I'm receiving loads of dmesg warnings: --- ACPI Warning: Firmware issue: Excessive sleep time (0x0010 ms > 10 ms) in ACPI Control Method (20220331/exsystem-347) --- Is there a way to silence it? I think this spam message is from linux. So, I think we should discuss on linux forum but I don't familier to linux. FYI, both FreeBSD and Linux use ACPICA to implement ACPI. https://acpica.org This message was added by this commit: https://github.com/acpica/acpica/commit/2a0d1d475e7ea1c815bee1e0692d81db9a7c909c You can file your complaints here if it is really bothering you. https://github.com/acpica/acpica/issues BTW, it seems it was discussed on Linux ML. https://lore.kernel.org/lkml/cajz5v0gwyz_bsonhlgt7l4wpqvxlvyobppte1nx6ponsgn4...@mail.gmail.com/T/#mae6a816bbcebb01dea9e5c19c81e9be872cad521 I am not sure what happened after that. I found the author actually filed a pull request to revert the commit. https://github.com/acpica/acpica/pull/780 FYI, I removed the message. https://cgit.freebsd.org/src/commit/?id=c7f14adfda21dfacab1895015b4c78bf7c2febb6 Jung-uk Kim
Re: dmesg: ACPI Warning: Firmware issue warning spaming
>> What do you think opening a review about this fix/tweak to stop this >> spamming that blinds dmesg? [snip] FYI, both FreeBSD and Linux use ACPICA to implement ACPI. https://acpica.org This message was added by this commit: https://github.com/acpica/acpica/commit/2a0d1d475e7ea1c815bee1e0692d81db9a7c909c You can file your complaints here if it is really bothering you. https://github.com/acpica/acpica/issues >>> >>> BTW, it seems it was discussed on Linux ML. >>> >>> https://lore.kernel.org/lkml/cajz5v0gwyz_bsonhlgt7l4wpqvxlvyobppte1nx6ponsgn4...@mail.gmail.com/T/#mae6a816bbcebb01dea9e5c19c81e9be872cad521 >>> I am not sure what happened after that. >> I found the author actually filed a pull request to revert the commit. >> https://github.com/acpica/acpica/pull/780 > > FYI, I removed the message. > > https://cgit.freebsd.org/src/commit/?id=c7f14adfda21dfacab1895015b4c78bf7c2febb6 Thank you very much. -- Masachika ISHIZUKA
freebsd-current@freebsd.org
On 2022-06-13 00:16:55 (+0800), Mark Millard wrote: ampere3's activity is not showing up on the page: https://pkg-status.freebsd.org/?all=1&type=package but: http://ampere3.nyi.freebsd.org/#latest_builds and: http://ampere3.nyi.freebsd.org/build.html?mastername=130arm64-default&build=b44e82e7d313 shows a currently active build (but with only 2 ports remaining). pkg-status.freebsd.org is maintained on GitHub, outside the clusteradm automation. I sent in this patch a couple of months ago, when I set up ampere3: https://github.com/bdrewery/pkg-status.freebsd.org/pull/12/files This was merged last week but it doesn't look like there's any automation to keep the running infrastructure in sync with that repository. There were some reassuring screams in a logfile after I chanted some incantations in a the jail running pkg-status.freebsd.org. Let me know if that fixed it. Philip -- Philip Paeps Senior Reality Engineer Alternative Enterprises
Re: dmesg: ACPI Warning: Firmware issue warning spaming
Am 14.06.22 um 04:00 schrieb Jung-uk Kim: On 22. 6. 13., Jung-uk Kim wrote: On 22. 6. 13., Jung-uk Kim wrote: On 22. 6. 13., Jung-uk Kim wrote: On 22. 6. 13., Masachika ISHIZUKA wrote: What do you think opening a review about this fix/tweak to stop this spamming that blinds dmesg? I'm running CURRENT 8d95f500521 and I'm receiving loads of dmesg warnings: --- ACPI Warning: Firmware issue: Excessive sleep time (0x0010 ms > 10 ms) in ACPI Control Method (20220331/exsystem-347) --- Is there a way to silence it? I think this spam message is from linux. So, I think we should discuss on linux forum but I don't familier to linux. FYI, both FreeBSD and Linux use ACPICA to implement ACPI. https://acpica.org This message was added by this commit: https://github.com/acpica/acpica/commit/2a0d1d475e7ea1c815bee1e0692d81db9a7c909c You can file your complaints here if it is really bothering you. https://github.com/acpica/acpica/issues BTW, it seems it was discussed on Linux ML. https://lore.kernel.org/lkml/cajz5v0gwyz_bsonhlgt7l4wpqvxlvyobppte1nx6ponsgn4...@mail.gmail.com/T/#mae6a816bbcebb01dea9e5c19c81e9be872cad521 I am not sure what happened after that. I found the author actually filed a pull request to revert the commit. https://github.com/acpica/acpica/pull/780 FYI, I removed the message. https://cgit.freebsd.org/src/commit/?id=c7f14adfda21dfacab1895015b4c78bf7c2febb6 Thank you! This message bothered me a lot on two notebooks, Dell Latitude 6520 and Dell Latitude 5521. Greetings, Rainer Jung-uk Kim
freebsd-current@freebsd.org
On 2022-Jun-13, at 22:14, Philip Paeps wrote: > On 2022-06-13 00:16:55 (+0800), Mark Millard wrote: >> ampere3's activity is not showing up on the page: >> https://pkg-status.freebsd.org/?all=1&type=package >> >> but: >> >> http://ampere3.nyi.freebsd.org/#latest_builds >> and: >> http://ampere3.nyi.freebsd.org/build.html?mastername=130arm64-default&build=b44e82e7d313 >> >> shows a currently active build (but with only 2 ports remaining). > > pkg-status.freebsd.org is maintained on GitHub, outside the clusteradm > automation. I sent in this patch a couple of months ago, when I set up > ampere3: > > https://github.com/bdrewery/pkg-status.freebsd.org/pull/12/files > > This was merged last week but it doesn't look like there's any automation to > keep the running infrastructure in sync with that repository. There were > some reassuring screams in a logfile after I chanted some incantations in a > the jail running pkg-status.freebsd.org. > > Let me know if that fixed it. > Well, I now see 34 builds that were via ampere3. This was via use of: https://pkg-status.freebsd.org/?all=1&type=package They go back to 2022-Feb-26, with the most recent still in progress (371 remaining). Thanks. === Mark Millard marklmi at yahoo.com
