text:
Incomplete card description in zhTW

The following is a reference in-game card image:

The following is the card image taken from hearthstonelabs.com:
http://hearthstonelabs.com/cards#lang=zhTW;cost=3;page=2;detail=EX1_083

Most words in the description are missing.
The same problem exists in almost all other cards that has multi-line description.

I see the problem - sunwell does automatic line breaks on spaces - normally. Because most asiatic languages operate without spaces, sunwell doesnt break the text and renders everything into one line, which is being cut off.
Thank you for the heads up, I will try and fix this, soon.

So, this is done in UberText.CanWrapBetween().
And uh... I just... don't know what to do with this.

	private bool CanWrapBetween(int lastChar, int wideChar, int nextChar)
	{
		if (Localization.GetLocale() == Locale.frFR || Localization.GetLocale() == Locale.deDE)
		{
			if (char.IsWhiteSpace(char.ConvertFromUtf32(wideChar), 0))
			{
				switch (nextChar)
				{
				case 58:
				case 59:
				case 63:
					return false;
				case 60:
				case 61:
				case 62:
					IL_4A:
					if (nextChar != 33 && nextChar != 46 && nextChar != 171 && nextChar != 187)
					{
						goto IL_77;
					}
					return false;
				}
				goto IL_4A;
			}
			IL_77:
			if (char.IsWhiteSpace(char.ConvertFromUtf32(wideChar), 0) && lastChar == 171)
			{
				return false;
			}
		}
		if (lastChar == 45)
		{
			return wideChar < 48 || wideChar > 57;
		}
		if (lastChar == 59)
		{
			return true;
		}
		if (wideChar == 124)
		{
			return true;
		}
		if (char.IsWhiteSpace(char.ConvertFromUtf32(lastChar), 0))
		{
			return false;
		}
		if (char.IsWhiteSpace(char.ConvertFromUtf32(wideChar), 0))
		{
			return true;
		}
		switch (lastChar)
		{
		case 12296:
		case 12298:
		case 12300:
		case 12302:
		case 12304:
			return false;
		case 12297:
		case 12299:
		case 12301:
		case 12303:
			IL_11D:
			switch (lastChar)
			{
			case 65505:
			case 65509:
			case 65510:
				return false;
			case 65506:
			case 65507:
			case 65508:
				IL_141:
				switch (lastChar)
				{
				case 65113:
				case 65115:
				case 65117:
					return false;
				case 65114:
				case 65116:
					IL_161:
					if (lastChar != 91 && lastChar != 92 && lastChar != 36 && lastChar != 40 && lastChar != 123 && lastChar != 8216 && lastChar != 8220 && lastChar != 8245 && lastChar != 12308 && lastChar != 12317 && lastChar != 65284 && lastChar != 65288 && lastChar != 65339 && lastChar != 65371)
					{
						switch (wideChar)
						{
						case 65104:
						case 65105:
						case 65106:
						case 65108:
						case 65109:
						case 65110:
						case 65111:
						case 65114:
						case 65116:
						case 65118:
							return false;
						case 65107:
						case 65112:
						case 65113:
						case 65115:
						case 65117:
							IL_23D:
							switch (wideChar)
							{
							case 12297:
							case 12299:
							case 12301:
							case 12303:
							case 12305:
								return false;
							case 12298:
							case 12300:
							case 12302:
							case 12304:
								IL_26D:
								switch (wideChar)
								{
								case 41:
								case 44:
								case 46:
									return false;
								case 42:
								case 43:
								case 45:
									IL_28E:
									switch (wideChar)
									{
									case 58:
									case 59:
									case 63:
										return false;
									case 60:
									case 61:
									case 62:
										IL_2AF:
										switch (wideChar)
										{
										case 8226:
										case 8230:
										case 8231:
											return false;
										case 8227:
										case 8228:
										case 8229:
											IL_2D3:
											switch (wideChar)
											{
											case 65289:
											case 65292:
											case 65294:
												return false;
											case 65290:
											case 65291:
											case 65293:
												IL_2F7:
												switch (wideChar)
												{
												case 65306:
												case 65307:
												case 65311:
													return false;
												case 65308:
												case 65309:
												case 65310:
													IL_31B:
													if (wideChar != 8211 && wideChar != 8212 && wideChar != 8242 && wideChar != 8243 && wideChar != 12289 && wideChar != 12290 && wideChar != 65438 && wideChar != 65439 && wideChar != 33 && wideChar != 37 && wideChar != 93 && wideChar != 125 && wideChar != 176 && wideChar != 183 && wideChar != 8217 && wideChar != 8221 && wideChar != 8451 && wideChar != 12309 && wideChar != 12318 && wideChar != 12540 && wideChar != 65072 && wideChar != 65281 && wideChar != 65285 && wideChar != 65341 && wideChar != 65373 && wideChar != 65392 && wideChar != 65504)
													{
														return lastChar == 12290 || lastChar == 65292 || ((Localization.GetLocale() != Locale.koKR || this.m_Alignment != UberText.AlignmentOptions.Center) && ((wideChar >= 4352 && wideChar <= 4607) || (wideChar >= 12288 && wideChar <= 55215) || (wideChar >= 63744 && wideChar <= 64255) || (wideChar >= 65280 && wideChar <= 65439) || (wideChar >= 65440 && wideChar <= 65500)));
													}
													return false;
												}
												goto IL_31B;
											}
											goto IL_2F7;
										}
										goto IL_2D3;
									}
									goto IL_2AF;
								}
								goto IL_28E;
							}
							goto IL_26D;
						}
						goto IL_23D;
					}
					return false;
				}
				goto IL_161;
			}
			goto IL_141;
		}
		goto IL_11D;
	}

authors: Paratron jleclanche mochunhei

repo: HearthSim/Sunwell


text:
Build documentation from doc comments

Is it supported to build documentation from doc comments?

Doesn't seem like zigs auto doc is not quite ready as it has not yet been merged into master:
https://github.com/ziglang/zig/wiki/How-to-contribute-to-Autodoc#where-is-autodoc=
I know there is some old system, but I don't think it's worth looking into that

source: gharchive/issue

authors: Hejsil notramo

repo: Hejsil/mecha

license: MIT

license_type: permissive

license_source: github-api


text:
graph execution error/libdevice not found

When running Careless on the thermolysin example data with (attached) settings, I encounter the following graph execution error (attached).
slurm_script.txt
myoutput_30592150_err.txt

i'm pretty sure this is a python config issue on your end. i have encountered this before. try making a new conda env and reinstalling.
conda create -n careless python=3.10
conda activate careless
pip install --upgrade pip
pip install careless

Based on my test, this was an issue with the TensorFlow 2.11 release candidate. I modified setup.py in #73 such that it should no longer install release candidates for TF. So, I did a new release to distribute this change. Let me know if this fixes your issue.

yes, it works now!

authors: DHekstra kmdalton

repo: Hekstra-Lab/careless


text:
Change to Social Spy event Priority REQUEST

https://img001.prntscr.com/file/img001/w4OIokX0QP6FAorpDYXhgg.png
As seen in the image above, if you /msg or /r to someone, it'll sometimes show the socialspy message last, rather than first. Social spy should always be the first one to send.

This can be easily changed by switching from using a Map here, to a LinkedHashMap so it keeps its order. We will be making this change after PR #116 will be merged to avoid unnecessary conflicts.
https://github.com/HelpChat/ChatChat/blob/4941d6083583674758d6c33c8c463fdd711ac5e0/plugin/src/main/java/at/helpch/chatchat/command/WhisperCommand.java#L92-L103

img001.prntscr.com/file/img001/w4OIokX0QP6FAorpDYXhgg.png
As seen in the image above, if you /msg or /r to someone, it'll sometimes show the socialspy message last, rather than first. Social spy should always be the first one to send.

I've somehow only now realized that you want the socialspy message to show first. Why would you want this? It makes no sense. If the message wasn't send yet what would you actually spy on. I'm not going to make it this way, and socialspy will stay last but I'm fixing it so it will be consistent and always last.

authors: BlitzOffline spookymgmt

repo: HelpChat/ChatChat


text:
User Verification

There should be a way to verify a user, probably through pictures of themselves and their passports. Also a way for peoples varification status to be displayed on their profile / the profile being invisible without verification / the app being unusable without verification

User verification is either done through the Google sign-in or E-mail verification

authors: Logophoman Plagiatus

repo: HelpingHandsProject/Application


text:
图片无法上传无任何提示信息

在部署完minio后，配置了bucket，设置为public，添加用户，赋权，生成accessKey和secretKey,API设置的默认的9000，但是不能上传图片，也没有任何信息提示，这该怎么处理啊？

端口放行了

2022-07-23 22:31:12 [PicGo WARN] {"code":"InvalidAccessKeyId","bucketname":"pic","resource":"/pic","requestid":"17047BCA4B563B0C","hostid":"6f8c7cbb-78cd-483d-b2ff-e101baa08085","amzRequestid":null,"amzId2":null,"amzBucketRegion":null}
2022-07-23 22:31:12 [PicGo SUCCESS]

看了日志发现原来users的key,而不是Service Accounts的key

repo: Herbertzz/picgo-plugin-minio


text:
G104 whitelisting

There are some functions that do return an error but are guaranteed to always return nil - so checking for errors is somewhere between pointless and a sign of risky program logic.
It'd be nice to be able to whitelist functions rather than having to annotate, e.g., every use of bytes.Buffer.Write() individually.

I would second this as a useful feature and suggest maybe drawing inspiration from brakeman.

Ok. Will look at adding this. For isolated instances you can always add the '// #nosec' annotation to ignore.

I've made some progress here in PR https://github.com/GoASTScanner/gas/pull/92.

Added the ability to add custom whitelists via config file.
Fixed rule so in addition to assignment to '_', errors that are implicitly ignored will also be reported.

The problem now becomes that this rule will be even more noisy. I'm considering switching from a whitelist to a blacklist of calls that you should check to avoid security issues, however coming up with that list could be difficult also.
@wttw @tam7t how would you prefer this works?

authors: gcmurphy tam7t wttw

repo: HewlettPackard/gas


text:
downloading firmware fails due to ignored redirect

Running rpi-update on my up to date raspberry pi zero fails at un-gzipping the downloaded firmware.
 *** Downloading specific firmware revision (this will take a few minutes)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   168    0   168    0     0    188      0 --:--:-- --:--:-- --:--:--   188

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

When investigationg I added set -o xtrace in '/usr/bin/rpi-update' and ran it with updates disabled.
The offending line seems to be eval curl -w "" -L https://github.com/Hexxeh/rpi-firmware/tarball/eefe4b161f5e9730183c8dc1605e14c85b15cf51.
After eval that line get executed as curl -w -L https://github.com/Hexxeh/rpi-firmware/tarball and the empty format string for -w gets left out. That makes -L the new format string and therefore gets ignored and curl does not follow the redirect
# curl -w -L https://github.com/Hexxeh/rpi-firmware/tarball/eefe4b161f5e9730183c8dc1605e14c85b15cf51
You are being redirected.-L

A solution to that problem could be to wrap the empty quotes with another pair of single quotes
eval curl -w '""' -L ${GITHUB_AUTH_PARAM} "${REPO_URI}/tarball/${FW_REV}" | tar xzf - -C "${FW_REPOLOCAL}" --strip-components=1

By doing that the update worked flawlessly

I've added the suggestion. Does it seem good now?

Wow, that was fast.
I am new to github but I think just sent a pull request doing that, which that won't be necessary now.

authors: BMicraft popcornmix

repo: Hexxeh/rpi-update

license: mit

license_source: bigquery


text:
auth, auth_sign, session_id是如何爬取的？

header有三个关键词auth, auth_sign, session_id是如何获取到的，用mitmdump软件吗

appium爬取太麻烦了，我是直接破解了这几个参数

请问你是咋破解的呢？因为我用过mitmproxy等这些软件抓取请求头，也没有看到这些信息

反编译小红书的微信小程序

反编译小红书的微信小程序

你好, 可以请教下sign的破解方法吗, 或是提供以下思路吗. 现在我已经把小程序的包解了, 对于寻找sign的算法位置还一头雾水, 希望可以教我一下, 非常感谢!

authors: Matchay huihui720 kbqncf


text:
Wrong serialization of strings containing commas in flow style list

Code
val list = listOf("foo", "bar, baz")
Yaml { listSerialization = YamlBuilder.ListSerialization.FLOW_SEQUENCE }.encodeToString(list)

Expected
[ foo, 'bar, baz' ]

Actual
[ foo, bar, baz ]

Workaround: Setting stringSerialization = YamlBuilder.StringSerialization.SINGLE_QUOTATION:
[ 'foo', 'bar, baz' ]

It probably has to be fixed in the getQuotationAvailability function.


text:
[Feature Request]: Send mail on contact form submission

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I would like to implement a feature where mail is sent to the owner when user submits the contact form. This will be implemented using emailjs. The mail will include the details of the user which where filled in contact form. This will improve user experience.
Use Case
Implementing email functionality for the contact form will enhance the project by ensuring timely communication, improving user engagement, and streamlining the handling of user queries and feedback.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Go Ahead @Ayesha-Siddiqua88 !


text:
Uninitialized constant error when reference module or class

I'm getting an "uninitialize constant" error when I reference a Flow module or class.
For example, I clone the Flow repo, build the gem with rake gem, and install it. I create an app with motion create --template=flow Hello. I then add one line to the application:didFinishLaunchingWithOptions: method in app/ios/app_delegate.rb:
Store['test'] = 123

When I try to build and run the app, though, it immediately terminates with an uninitialized constant error for AppDelegate::Store, so it seems it doesn't know about the Store class from Flow:
$ rake ios:simulator
       Build build/ios/iPhoneSimulator-9.2-Development
      Create build/ios/iPhoneSimulator-9.2-Development/Hello.app/Info.plist
    Simulate build/ios/iPhoneSimulator-9.2-Development/Hello.app
  *** Starting simulator
  2016-03-14 15:58:52.041 Hello[62268:27772307] app_delegate.rb:9:in `application:didFinishLaunchingWithOptions:': uninitialized constant AppDelegate::Store (NameError)

What am I doing wrong?
I'm using RubyMotion 4.9 on OS X El Capitan.
Thanks!

Do you have the latest version (0.2)?

Yes:
$ gem list | grep motion-flow
motion-flow (0.2)

OK, I got it working for an iOS project!  For an iOS project, the problem is that the docs assume I have the bundler gem installed since they say to add gem lines to Gemfile.
Going back to what I initially reported using the RubyMotion flow template, the created project actually has no targets:
$ motion create --template=flow Hello
    Create Hello
    Create Hello/app/android/main_activity.rb
    Create Hello/app/ios/app_delegate.rb
    Create Hello/config/android.rb
    Create Hello/config/ios.rb
    Create Hello/config/osx.rb
    Create Hello/Gemfile
    Create Hello/Rakefile
$ cd Hello
$ rake -T
$

So, maybe that's not ready yet, or maybe I have to change something to get targets.  I don't know how I had targets before; maybe I never did and really just made a mistake and got it mixed up with a RubyMotion ios template project.  So, scratch the claim that I'm using a flow template project.
I switched to just using an ios template project:
$ motion create Hello
    Create Hello
    Create Hello/.gitignore
    Create Hello/app/app_delegate.rb
    Create Hello/Gemfile
    Create Hello/Rakefile
    Create Hello/resources/Default-568h@2x.png
    Create Hello/resources/Default-667h@2x.png
    Create Hello/resources/Default-736h@3x.png
    Create Hello/spec/main_spec.rb
$ cd Hello

I add the following line to Gemfile:
gem 'motion-flow'

I add the following line to the application:didFinishLaunchingWithOptions: method in app/app_delegate.rb:
Store['test'] = 123

I build it with rake and get the "uninitialized constant AppDelegate::Store (NameError)" error.
I then tried removing gem 'motion-flow' from Gemfile and adding the following line after require 'motion/project/template/ios' in Rakefile:
require 'motion-flow'

I build and run it with rake and it works!
So, the problem is that the docs assume I have the bundler gem installed when I don't.  If I revert my change to Rakefile, install the bunder gem with gem install bundler, build and run with rake, then it works with gem 'motion-flow' in Gemfile.

Hmm.. I tried motion create --template=flow Hello and it worked for me. But glad you figured it out though!

It's a Bundler dependency issue again!  If I have the bundler gem installed before I run motion create --template=flow Hello, then rake -T reports lots of targets.  But if I do not have the bunder gem installed and run motion create --template=flow Hello, then rake -T reports no targets.

I think Flow needs to be clear on its prerequisites.  If it requires Bundler to work, then this needs to be documented (and probably asserted in code).  If it doesn't, then obviously it needs to be able to work when Bundler is not installed.

authors: hboon jlmuir

repo: HipByte/Flow


text:
Unroll recursion in list.h

As for now, the list operations are implemented naively. The task is to unroll them (see loop unrolling) to improve their performance (at least unroll the mostly used functions).

Metalang99 seems to perform well without it, so this will not be worked on.


text:
🛑 Kamero.in Website is down

In d6530b8, Kamero.in Website (https://kamero.in) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Kamero.in Website is back up in 3b4ce8c after 11 minutes.

repo: Hitesh-Kamero/kamero-upptime


text:
"Package 'wlroots' requires 'wayland-protocols >= 1.17' but version of wayland-protocols is 1.12" during building

I was trying to build the latest release on Debian11/KDE. For this I had to install meson and chmod /usr/bin/ccache /usr/bin/cc and /usr/bin/gcc. When I ran meson build it returned: meson.build:1:0: ERROR: Compiler ccache cc can not compile programs. installing gcc-multilib was not required, instead I only had to also chmod /usr/bin/as. Then I also installed libwlroots6 libwlroots-dev.
Now my problem is that meson build returns:
Run-time dependency wlroots found: NO (tried cmake)

meson.build:37:0: ERROR: Could not generate cargs for wlroots:
Package 'wlroots' requires 'wayland-protocols >= 1.17' but version of wayland-protocols is 1.12

Does this mean it's not yet supported on Debian11 (with Wayland) and one would need to wait to be able install it there?
Once it's available, it would be great if this could be added to the Debian repos.

Hi @mYnDstrEAm. This means that the version of wayland-protocols in Debian 11 is too old. There is not much I can do about that.

Once it's available, it would be great if this could be added to the Debian repos.

Looks like someone filed a request to package Cage for Debian already: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927899. It's not up to me to package Cage for different distributions :)

authors: Hjdskes mYnDstrEAm

repo: Hjdskes/cage


text:
Manh - add form DeTai, Form LyLichKhoaHoc

Manh - add form DeTai, Form LyLichKhoaHoc

#8 done


text:
🛑 Hodl10 AG Webseite is down

In 63fd31b, Hodl10 AG Webseite (https://hodl10.io/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Hodl10 AG Webseite is back up in 9c3d8e7.


text:
🛑 Hodl10 AG Webseite is down

In 062c223, Hodl10 AG Webseite (https://hodl10.io/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Hodl10 AG Webseite is back up in c6df52b.


text:
🛑 Apicore Service is down

In 5cad54e, Apicore Service (https://az-hxg.hexabase.com/apicore/health_check) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Apicore Service is back up in 3d578c9.

repo: Hokutosei/HexaUptime


text:
brew install wget resulted in updating 8 billion 300 thousand and 35 trillion packages on my system

brew config output
HOMEBREW_VERSION: 3.2.14
ORIGIN: https://github.com/Homebrew/brew
HEAD: 4e6919b73444e9f9e02ad81d8afc4bbd97533567
Last commit: 4 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 918badf7f68bbe68f03e2ae1f977aa71f9aeb801
Core tap last commit: 6 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 8
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: octa-core 64-bit icelake
Clang: 13.0.0 build 1300
Git: 2.29.2 => /usr/local/bin/git
Curl: 7.64.1 => /usr/bin/curl
macOS: 11.6-x86_64
CLT: 12.5.0.22.11
Xcode: 13.0

brew doctor output
brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: A newer Command Line Tools release is available.
Update them from Software Update in System Preferences or run:
  softwareupdate --all --install --force

If that doesn't show you any updates, run:
  sudo rm -rf /Library/Developer/CommandLineTools
  sudo xcode-select --install

Alternatively, manually download them from:
  https://developer.apple.com/download/more/.
You should download the Command Line Tools for Xcode 13.0.

Warning: Some installed formulae are deprecated or disabled.
You should find replacements for the following formulae:
  ilmbase

Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause formulae that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
  imath
  qt
  openexr

Warning: Homebrew's "sbin" was not found in your PATH but you have installed
formulae that put executables in /usr/local/sbin.
Consider setting your PATH for example like so:
  echo 'export PATH="/usr/local/sbin:$PATH"' >> ~/.zshrc

[X] I ran brew update and am still able to reproduce my issue.
[X] I have resolved all warnings from brew doctor and that did not fix my problem.

What were you trying to do (and why)?
install wget ... to download a file?
What happened (include all command output)?
home-brew updated literally everything.  mysql, ruby, python, sensible, like... everything on my system.  it's still going.
it's installed/updated so much stuff at this point the original list has scrolled off the buffer.
finally it ended - it must've updated everything.  it updated memcache, Postgres, map nginx imagemagick, etc etc etc -- all stuff I've previously installed but by no means wanted or needed updated.
I bet absolutely nothing works now.
What did you expect to happen?
just install wget and maybe, I dunno, 3 dependencies
Step-by-step reproduction instructions (by running brew commands)
1. don't brew install anything for a few months
2. `brew install wget`

brew install foo will also upgrade everything connected to foo via its dependency graph.
wget depends on openssl@1.1. Lots of packages are connected to openssl@1.1, so those are upgraded too.

@josh-m-sharpe Please reread our Code of Conduct and adjust your tone accordingly in future issues.

authors: MikeMcQuaid carlocab josh-m-sharpe

repo: Homebrew/brew


text:
OCI: Add sh.brew.tab to the image manifest

The tab is needed to install the package using the SHA-256 of the single-architecture image.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew style with your changes locally?
[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

See for example the SHA-256 of the single-architecture images advertised under the OS / Arch tab of the multi-architecture image at https://github.com/orgs/brewsci/packages/container/package/bio/seqkit-mediatype-docker

Review period will end on 2021-04-06 at 00:00:00 UTC.

Review period skipped due to critical label.

source: gharchive/pull-request

authors: BrewTestBot sjackman


text:
resource: allow on_os blocks

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Just wrote the test to showcase what we need to implement.

I applied suggestions made by @Bo98.

The patch stuff only makes sense for ExternalPatch, in which case we could simplify implementation by simply delegating on_* blocks to the resource via def_delegators.

The patch stuff only makes sense for ExternalPatch

You mean, it will not work for patch :DATA? I did not plan to implement this for that case as I am unsure if we can have tow DATA blocks at the end. In that case it is better to keep the patch in formula-patches anyway.

simply delegating on_* blocks to the resource via def_delegators.

Not sure what you mean by that

I did not plan to implement this for that case as I am unsure if we can have tow DATA blocks at the end.

Yeh, we cannot.

In that case it is better to keep the patch in formula-patches anyway.

Agreed.

Not sure what you mean by that

grep for def_delegator and you'll see the usage, hopefully that helps.

Yeah, the idea you have here is to have it inside the do block, and only ExternalPatch makes use of blocks.
ExternalPatch uses a resource internally. Notice how it doesn't reimplement stuff like url etc - it shares the implementation with Resource. def_delegator as Mike points out is what is responsible for this.


text:
brew install homebrew/binary/subgit doesn't work out of the box

Installing subgit doesn't seem to work out the box:
> brew install homebrew/binary/subgit
...
==> Caveats
    To use SubGit, you must agree to the SubGit licensing agreement:
      http://subgit.com/license.html
==> Summary
🍺  /usr/local/Cellar/subgit/3.0.0: 37 files, 12.8M, built in 1 second
>rehash
>subgit
Error: JAVA_HOME is not defined correctly.
  We cannot execute /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/bin/java
>/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/bin/java
zsh: no such file or directory: /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/bin/java

(I'm guessing a dependency on a JVM is missing somewhere.)

I could get things started with
> brew install java
> JAVACMD=/System/Library/Frameworks/JavaVM.framework/Versions/A/Commands/java subgit

Some readme's mention that doing a reboot or re-login might fix the latter part, but I haven't given it a shot yet.

Does this also happen if you download and install subgit outside of Homebrew?

Nope.

We'll accept PRs for this but we're not actively working on it at this time.

authors: MikeMcQuaid dunn msiebuhr

repo: Homebrew/homebrew-binary


text:
Bottles published but revision not merged

We have regularly cases where bottles are published but the corresponding revision is not merged to homebrew-core. The latest is opencv in https://github.com/Homebrew/homebrew-core/pull/124578
We're left in a state that the test-bot alone cannot recover from:
Error: docker://ghcr.io/homebrew/core/opencv:4.7.0_2 already exists!

Published 3 days ago. But the corresponding revision was not committed to homebrew-core, so any revision bump will now fail on bottles publishing.
How can we make the bottles publishing atomic? I.e., ensure that bottles are published if and only if the revision is committed?

How can we make the bottles publishing atomic? I.e., ensure that bottles are published if and only if the revision is committed?

I don't think we really can do this without changing our workflow (which we should probably do).
Eventually we really need to get to a "bottle commits are pushed to PRs and only actually published when they are merged into master".
The public beta for the new merge queue feature could help us here. You can have additional CI jobs which are only run when something is "queued for merge" which, in our case, could be the job that does the actual publishing and then merges it to master only when the publishing succeeds.

But the corresponding revision was not committed to homebrew-core, so any revision bump will now fail on bottles publishing.

Zero blame here but: any ideas why this happened?
CC @Homebrew/maintainers @Homebrew/core for input and thoughts here.

Zero blame here but: any ideas why this happened?

I'm guessing GitHub packages outage

I'm guessing GitHub packages outage

Can confirm this is what happened.

authors: MikeMcQuaid SMillerDev fxcoudert p-linnane

repo: Homebrew/homebrew-test-bot


text:
https://angi.com

https://www.angi.com/ is on url-lists.txt. Any reason this is on a  phishing block list?

https://github.com/HorusTeknoloji/TR-PhishingList/commit/33fdb187c2b6e619608c0f75a213053ca8b9f3d7

authors: MertcanGokgoz louisgtwo

repo: HorusTeknoloji/TR-PhishingList


text:
Capture Gas Meter readouts

We want to be able to capture the magnetic pulses of gas meters to process them with software..

We were able to use the exact same setup from the water meter to capture gas meter readouts.

repo: HouseOfTheFuture/TickTack


text:
$

Un

Un


text:
[CARBONDATA-118] Temp location clean up in compaction

Temp locations should get deleted after the compaction is completed in RDD.

LGTM

repo: HuaweiBigData/carbondata


text:
Can't login

I used to be able to login through http://robsdixon.github.io/blog/hubpress or http://robdblog.ml/hubpress but when I enter my credentials, it comes up with a green box saying:
Authentication
Welcome back Robert S Dixon
But stays on the login page and when I refresh the page, it clears my inputted credentials and asks me to login again :-(
Arrrggg! This is so annoying! I would hate to have to reset the blog because I have made posts.
Pleeeeaaaaassseee help me thanks

Hi @robsdixon!
You must upgrade your instance of hubpress with the version 0.3.0.
The Github authorization has changed and the 0.2.0 can't work anymore
You can find a blog post here https://blog.hubpress.io

Thanks, soz about slow reply, I've been away

@anthonny This Firefox warning message when trying to access the blog is expected?

That error is because blog.hubpress.io is actually hosted at GitHub Pages (http://hubpress.github.io/blog.hubpress.io/).
http://blog.hubpress.io should be fine.

authors: adityadalal924 anthonny robsdixon simevidas


text:
Static deps & provides

@also @gchomatas @jhaber

Do we need to include runtimeDeps or devDeps as well?

Oh yeah. I'll add post lunch.
On Mar 14, 2016 1:00 PM, "Jonathan Haber" notifications@github.com wrote:

Do we need to include runtimeDeps or devDeps as well?
—
Reply to this email directly or view it on GitHub
https://github.com/HubSpot/Blazar/pull/128#issuecomment-196411619.

@jhaber We good here?

cool lgtm

authors: jhaber jonathanwgoodwin

repo: HubSpot/Blazar


text:
Fix extra spaces in class names

The current way of switching class names for body and the div.pace creates extra spaces in front of some class names, for example:  pace-running and pace  pace-inactive.
This PR fixes this problem by using a slightly different way of replacing class names.

Sorry didn't realise that this is a coffee project. I've created a new PR #245. :sweat_smile:

repo: HubSpot/pace


text:
Reflecting the latest comments regarding control key

Based on the latest comments from @basepi

Perfect! I'll try to keep my OCD under control. :)

Oh, no!!! OCD is good in programming :)

repo: HubbleStack/Nova


text:
Add dev-mode features

Hi @Hugo-Dz,
I've included the Excel file download feature in Settings.
For detailed instructions, please check the link below.
https://youtu.be/VgOoC5Irh08

@Hugo-Dz
I figured out that the limit of Figma's client storage is 1 MB, and I've devised a new way to replace it.
I created a new page named 🔒 DevMode Image Storage (Do Not Delete), and stored images that were used for TensorFlow Image classification, and this change was a success.
This method not only allows us to support Developer Mode much faster and more reliably, but we can also replace the inconvenient Excel download feature.
Because instead of sending this design-research-data to design system administrators in Excel or Google Sheets, they can easily search this newly created page by themselves.

In addition, I have modified the card design for dev mode. I hope you love this change :)

https://youtu.be/ltMCaMXW3jA?si=BCk_E6D6jFzOA0eS
Updated. @Hugo-Dz

Hello @Hugo-Dz
I've put a lot of thought into this. Since I fundamentally agree that providing a base URL for the design system in the settings isn't a great user experience, I decided to completely REMOVE this part from the UI panel and explore an alternative way to support Dev mode.
Fortunately, I found a great alternative through the metadata JSON of custom TensorFlow models. With this approach, I've improved all the code.
You can test the model here:

Test Model
Metadata

The updated code's UI doesn't mention anything related to the design system in the settings. Just like before, users can put the model URL with Teachable Machine, and it will work as you already know it.
If only the metadata's JSON is specifically modified to include URLs, AutoName finally dev-resource information provides up to three URLs on the dev-move.
So.. role-play again:

Junior designers can use the plugin as usual, with no changes on their user interface.
If their design system manager intends to display info in the Dev mode and distribute their custom URLs
the task for junior designers remains simple: update the settings with the received URL.
But the AutoName plugin works and provides AI magic on the dev-mode.

Best regards,

@dusskapark I think we are good! I need build it locally to publish on the Figma community and we will be good!

Hi @Hugo-Dz
I've made the fixes you requested in your message.

type error

This should be resolved by updating the dependency libraries to the latest version of Figma. The API related to devResource is relatively new, having been added last year.

tmImage issues

Models created with the old Teachable machine seem to perform predictive modeling in a different way than the usual tfjs layer model. I don't know the exact internals, but as long as we distinguish between TM and TFJS models by the URL of the model, it should be fine.
Please check my latest update and review the merge again.

authors: Hugo-Dz dusskapark


text:
PageSpy使用过程中偶尔会出现websocket大量调用

Describe the bug

使用过程中偶尔会出现websocket大量调用的现象, 暂时未找到触发的原因
Steps to reproduce
No response
System Info
Chrome 120.0.6099.109（正式版本） (x86_64)

Logs
No response
Validations

[X] Read the docs.
[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible example of the bug.

请升级到最新版本 1.5.0。

请升级到最新版本 1.5.0。
如果已经是最新版本，麻烦提供一下复现步骤，感谢。

目前使用的版本是1.5.0, 复现步骤是打开项目网页, PageSpy进入对应的房间, 然后打开新的浏览器标签正常浏览其他网站, 大概半个小时后再返回项目页面刷新, 有一定概率会复现, 刷新页面也依然存在问题.

curl -H "Pragma: no-cache" -H "Origin: http://10.122.23.37:30080" -H "Host: 10.122.23.37:6752" -H "Accept-Language: zh-CN,zh;q=0.9" -H "Sec-WebSocket-Key: wBLS1BhTfu9Re6/uUdaafA==" -H "User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 16_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.6 Mobile/15E148 Safari/604.1" -H "Upgrade: websocket" -H "Cache-Control: no-cache" -H "Sec-WebSocket-Version: 13" -H "Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits" --compressed "ws://10.122.23.37:6752/api/v1/ws/room/join?address=df14dd5c-0953-4997-b8af-aaf9255dfb34.local&name=client%253Av93nmzojhu&userId=Client"

下个版本中我们会做些兜底策略，请保持关注

请升级到 1.5.1 版本

authors: LeafOfMango wqcstrong

repo: HuolalaTech/page-spy-web


text:
关于在docker镜像中增加网关模式的建议

建议在docker镜像中，增加一个启用网关模式的参数变量，若启用网关模式，则在启动脚本中增加几条iptables规则，引导流量至tun，实现旁路网关的功能

理论上确实是可行的, 但是需要 docker 容器以特权模式运行, 且如果 iptables 设置不当会造成服务器失联... 所以这种东西交给普通用户操作, 我个人是觉得比较危险的.

@tobyxdd @mritd
Could you consider using a mode like v2rayA (https://github.com/v2rayA/v2rayA) ? It would be very useful to the general linux version and it will not be limited to just docker.
Thanks,

authors: egg1234 hejaxian mritd

repo: HyNetwork/hysteria


text:
Mixins for structure modules

An important feature currently missing from the framework. Just posting this as a reminder to myself to implement eventually.

Implemented as of today. Check out the structure mixin under core/structures/_structure.scss

repo: HydroWeb/hydro-css


text:
Table with plot: Deleting rows not working correctly

Deziree and I both experienced issues with deleting rows. I was unable to delete any rows when I only had two rows. Is this by design? Maybe we require two rows? Everything else seems to work for me. Dez, had a situation where deleting the last row was actually deleting the first row.

This issue seemed to have occurred while also testing copying and pasting in the table. Attached is a video demonstrating the issue with deleting rows. I tried to delete the bottom row and it deleted the top row.
https://user-images.githubusercontent.com/47678178/161867697-f1222854-c05d-4753-9f98-a960e28476c3.mp4

you dont have a row selected - so it deletes the first row.

This is odd. I'm unable to reproduce that behavior on the current main. Unless someone snuck in and fixed this, It seems like there might be a version issue. Are you able to reliably reproduce this on your machine @dezidizon ?

I am unable to reproduce this. Based on the values in the table in the video, it looks like Dez was using pasted in values. Maybe there is something with copy and paste and delete. I tried pasting data in and then deleting rows, and it all behaved normal for me. Unless someone can reproduce it, lets call it non reproduceable and move on.

closing because I could not reproduce. We can open it up again if it pops up

authors: Brennan1994 HenryGeorgist codymccoy dezidizon

repo: HydrologicEngineeringCenter/HEC-FDA


text:
remove all double nan and is infinity checks.

in time trialing, these are killing us in our performance.

this is complete with #69


text:
Can't load HyperEnclaveDriver: hang on & need manual reboot machine

Hi, I try HyperEnclave in Ubuntu20, when type 'bash start_hyperenclave.sh’, it always hang on, and freeze the whole system, I need to manual reboot the machine.
when comment out the following line in file: https://github.com/HyperEnclave/hyperenclave-driver/blob/0af18c3ea3a3935fd9bd5d08b901ff6a288b161d/driver/main.c#L456C2-L456C2
	preempt_disable();

	header->online_cpus = num_online_cpus();
	atomic_set(&call_done, 0);
	on_each_cpu(enter_hypervisor, header, 0);
	while (atomic_read(&call_done) != num_online_cpus())
		cpu_relax();

	preempt_enable();

compile HyperEnclaveDriver and run again, it now does not hang on, but dmesg show error log: Initialize CMRM fail
Environment:
cat /proc/cmdline
	BOOT_IMAGE=/boot/vmlinuz-5.4.0-166-generic root=UUID=7eb35854-7835-49d7-8c68-b7eb7e8f296c ro memmap=32G$0x100000000 amd_iommu=off intremap=off no5lvl default_hugepagesz=1G hugepagesz=1G
uname -a
	Linux t017372-172-25-10-21 5.4.0-166-generic #183-Ubuntu SMP Mon Oct 2 11:28:33 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
lsb_release -a
	No LSB modules are available.
	Distributor ID:	Ubuntu
	Description:	Ubuntu 20.04.3 LTS
	Release:	20.04
	Codename:	focal

lscpu
	Architecture:                       x86_64
	CPU op-mode(s):                     32-bit, 64-bit
	Byte Order:                         Little Endian
	Address sizes:                      43 bits physical, 48 bits virtual
	CPU(s):                             128
	On-line CPU(s) list:                0-127
	Thread(s) per core:                 1
	Core(s) per socket:                 64
	Socket(s):                          2
	NUMA node(s):                       8
	Vendor ID:                          AuthenticAMD
	CPU family:                         25
	Model:                              1
	Model name:                         AMD EPYC 7T83 64-Core Processor
	Stepping:                           1
	Frequency boost:                    enabled
	CPU MHz:                            1794.019
	CPU max MHz:                        3500.0000
	CPU min MHz:                        1500.0000
	BogoMIPS:                           6986.98
	Virtualization:                     AMD-V
	L1d cache:                          4 MiB
	L1i cache:                          4 MiB
	L2 cache:                           64 MiB
	L3 cache:                           512 MiB
	NUMA node0 CPU(s):                  0-15
	NUMA node1 CPU(s):                  16-31
	NUMA node2 CPU(s):                  32-47
	NUMA node3 CPU(s):                  48-63
	NUMA node4 CPU(s):                  64-79
	NUMA node5 CPU(s):                  80-95
	NUMA node6 CPU(s):                  96-111
	NUMA node7 CPU(s):                  112-127
	Vulnerability Gather data sampling: Not affected
	Vulnerability Itlb multihit:        Not affected
	Vulnerability L1tf:                 Not affected
	Vulnerability Mds:                  Not affected
	Vulnerability Meltdown:             Not affected
	Vulnerability Mmio stale data:      Not affected
	Vulnerability Retbleed:             Not affected
	Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl and seccomp
	Vulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __user pointer sanitization
	Vulnerability Spectre v2:           Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected
	Vulnerability Srbds:                Not affected
	Vulnerability Tsx async abort:      Not affected
	Flags:                              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3
										 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat
										_l3 cdp_l3 invpcid_single hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local
										clzero irperf xsaveerptr wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold v_vmsave_vmload vgif umip pku ospke vaes vpclmulqdq rdpid overflow_recov succor smca sme sev sev_es

Hi @linguohua , thanks for your interest for HyperEnclave.
The code you have commented out:
	preempt_disable();

	header->online_cpus = num_online_cpus();
	atomic_set(&call_done, 0);
	on_each_cpu(enter_hypervisor, header, 0);
	while (atomic_read(&call_done) != num_online_cpus())
		cpu_relax();

	preempt_enable();

is the key operations to start HyperEnclave on the platform. So it is natural that you get
Initialize CMRM fail

in the log shown by dmesg.
It seems that the platform is a server. Could you please show the output of the Serial Port when you start HyperEnclave? (We usually get the output of Serial Port by typing the following command):
ipmitool -I lanplus -H [IP address] -U admin -P admin sol activate

Thanks for you reply.
My server is located in an IDC, far away from my work site, so it is not easy to get the log out from serial port, but I will try my best to get it later.
More information about the 'hang on' is, our enclave-driver hang on the following line:
https://github.com/HyperEnclave/hyperenclave-driver/blob/0af18c3ea3a3935fd9bd5d08b901ff6a288b161d/driver/main.c#L158C20-L158C20
		err = entry(cpu);

When this line been commented out,  enclave-driver can go ahead(with 'Initialize CMRM fail' finally). It seems that the entry of rust-monitor has some issue which stuck the progress.

Could you please show the complete dmesg log with the following line commented out:
                err = entry(cpu);

Maybe we can get more information about your platform from the log.

Hi, thanks for your reply and sorry for my delay.
The dmesg logs:
[90190.155078] HE: cpu_vendor_detect: 39. Vendor ID: AuthenticAMD
[90190.170580] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000000000000 -> 0x00000000000a0000], type: System RAM
[90190.170582] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000000a0000 -> 0x0000000000100000], type: Reserved
[90190.170583] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000000100000 -> 0x0000000030000000], type: System RAM
[90190.170584] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000030000000 -> 0x0000000030047000], type: ACPI Non-volatile Storage
[90190.170585] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000030047000 -> 0x0000000075cf0000], type: System RAM
[90190.170586] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000075cf0000 -> 0x0000000076000000], type: Reserved
[90190.170587] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000076000000 -> 0x00000000a60b6000], type: System RAM
[90190.170588] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000a60b6000 -> 0x00000000a820f000], type: Reserved
[90190.170588] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000a820f000 -> 0x00000000a83c9000], type: ACPI Tables
[90190.170589] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000a83c9000 -> 0x00000000a88d4000], type: ACPI Non-volatile Storage
[90190.170590] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000a88d4000 -> 0x00000000a97ff000], type: Reserved
[90190.170591] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000a97ff000 -> 0x00000000ac000000], type: System RAM
[90190.170592] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000ac000000 -> 0x00000000b0000000], type: Reserved
[90190.170593] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000b4280000 -> 0x00000000b4281000], type: Reserved
[90190.170593] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000b5180000 -> 0x00000000b5181000], type: Reserved
[90190.170594] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000be180000 -> 0x00000000be181000], type: Reserved
[90190.170595] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000bf200000 -> 0x00000000bf301000], type: Reserved
[90190.170596] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000c8180000 -> 0x00000000c8181000], type: Reserved
[90190.170596] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000c9100000 -> 0x00000000c9200000], type: Reserved
[90190.170597] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000c9300000 -> 0x00000000c9401000], type: Reserved
[90190.170598] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000c9500000 -> 0x00000000c9600000], type: Reserved
[90190.170599] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000f4180000 -> 0x00000000f4181000], type: Reserved
[90190.170599] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000f5180000 -> 0x00000000f5181000], type: Reserved
[90190.170600] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fea00000 -> 0x00000000feb00000], type: Reserved
[90190.170601] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fec00000 -> 0x00000000fec01000], type: Reserved
[90190.170602] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fec10000 -> 0x00000000fec11000], type: Reserved
[90190.170602] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fed00000 -> 0x00000000fed01000], type: Reserved
[90190.170603] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fed40000 -> 0x00000000fed45000], type: Reserved
[90190.170604] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fed80000 -> 0x00000000fed90000], type: Reserved
[90190.170605] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fedc0000 -> 0x00000000fedc1000], type: Reserved
[90190.170605] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fedc2000 -> 0x00000000fedc9000], type: Reserved
[90190.170606] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fee00000 -> 0x00000000fef00000], type: Reserved
[90190.170607] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000ff000000 -> 0x0000000100000000], type: Reserved
[90190.170608] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000100000000 -> 0x000000404fe00000], type: System RAM
[90190.170609] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000000404fe00000 -> 0x0000004050000000], type: Reserved
[90190.170609] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000004050000000 -> 0x000000804ff00000], type: System RAM
[90190.170610] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000000804ff00000 -> 0x0000008050000000], type: Reserved
[90190.170611] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000008050000000 -> 0x000000c04ff00000], type: System RAM
[90190.170612] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000000c04ff00000 -> 0x000000c050000000], type: Reserved
[90190.170613] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000000fd00000000 -> 0x0000010000000000], type: Reserved
[90190.170613] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000010000000000 -> 0x0000013fff300000], type: System RAM
[90190.170614] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000013fff300000 -> 0x0000014000000000], type: Reserved
[90190.170615] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000014000000000 -> 0x0000017ffff00000], type: System RAM
[90190.170616] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000017ffff00000 -> 0x0000018000000000], type: Reserved
[90190.170616] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000018000000000 -> 0x000001bffff00000], type: System RAM
[90190.170617] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000001bffff00000 -> 0x000001c000000000], type: Reserved
[90190.170618] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000001c000000000 -> 0x000001fffff00000], type: System RAM
[90190.170619] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000001fffff00000 -> 0x0000020000000000], type: Reserved
[90190.170619] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000020000000000 -> 0x0000023ffff00000], type: System RAM
[90190.170620] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000023ffff00000 -> 0x0000024010400000], type: Reserved
[90190.170621] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000034030000000 -> 0x0000034040400000], type: Reserved
[90190.170622] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000034060000000 -> 0x0000034070400000], type: Reserved
[90190.170623] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000004c090000000 -> 0x000004c0a0400000], type: Reserved
[90190.170623] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000004c0c0000000 -> 0x000004c0d0400000], type: Reserved
[90190.170624] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000005c0f0000000 -> 0x000005c100400000], type: Reserved
[90190.170625] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000005c120000000 -> 0x000005c130400000], type: Reserved
[90190.170626] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000006c150000000 -> 0x000006c160400000], type: Reserved
[90190.170626] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000007fc00000000 -> 0x000007fc04000000], type: Reserved
[90190.170630] HE: get_convertible_memory: 213. Convertible Memory[ 0]: 0x0000000000000000 -> 0x00000000000a0000
[90190.170631] HE: get_convertible_memory: 213. Convertible Memory[ 1]: 0x0000000000100000 -> 0x0000000030000000
[90190.170632] HE: get_convertible_memory: 213. Convertible Memory[ 2]: 0x0000000030047000 -> 0x0000000075cf0000
[90190.170632] HE: get_convertible_memory: 213. Convertible Memory[ 3]: 0x0000000076000000 -> 0x00000000a60b6000
[90190.170633] HE: get_convertible_memory: 213. Convertible Memory[ 4]: 0x00000000a97ff000 -> 0x00000000ac000000
[90190.170634] HE: get_convertible_memory: 213. Convertible Memory[ 5]: 0x0000000100000000 -> 0x000000404fe00000
[90190.170635] HE: get_convertible_memory: 213. Convertible Memory[ 6]: 0x0000004050000000 -> 0x000000804ff00000
[90190.170636] HE: get_convertible_memory: 213. Convertible Memory[ 7]: 0x0000008050000000 -> 0x000000c04ff00000
[90190.170637] HE: get_convertible_memory: 213. Convertible Memory[ 8]: 0x0000010000000000 -> 0x0000013fff300000
[90190.170637] HE: get_convertible_memory: 213. Convertible Memory[ 9]: 0x0000014000000000 -> 0x0000017ffff00000
[90190.170638] HE: get_convertible_memory: 213. Convertible Memory[10]: 0x0000018000000000 -> 0x000001bffff00000
[90190.170639] HE: get_convertible_memory: 213. Convertible Memory[11]: 0x000001c000000000 -> 0x000001fffff00000
[90190.170640] HE: get_convertible_memory: 213. Convertible Memory[12]: 0x0000020000000000 -> 0x0000023ffff00000
[90190.170641] HE: get_convertible_memory: 218. Convertible Memory size: 0x1fff7000000
[90190.170642] HE: get_valid_rsrv_mem: 285. Reserved Memory[ 0]: 0x100000000 -> 0x900000000
[90190.170643] HE: get_valid_rsrv_mem: 290. Reserved Memory size: 0x800000000
[90190.170644] HE: get_sme_mask: 68. SME mask: [0x8000000000000]
[90190.172636] HE: mem_test: 48. Memory[0x100000000 - 0x300000000] test begin
[90191.959802] HE: mem_test: 78. Memory[0x100000000 - 0x300000000] test pass
[90191.960733] HE: mem_test: 48. Memory[0x300000000 - 0x500000000] test begin
[90194.169362] HE: mem_test: 78. Memory[0x300000000 - 0x500000000] test pass
[90194.170423] HE: mem_test: 48. Memory[0x500000000 - 0x700000000] test begin
[90196.334480] HE: mem_test: 78. Memory[0x500000000 - 0x700000000] test pass
[90196.335283] HE: mem_test: 48. Memory[0x700000000 - 0x900000000] test begin
[90198.513603] HE: mem_test: 78. Memory[0x700000000 - 0x900000000] test pass
[90198.540042] HE: get_hypervisor_meminfo: 185. HE_WARN. get_hypervisor_meminfo 1 : 0x100000001, 0x800000000
[90198.540044] HE: get_hypervisor_meminfo: 198. HE_WARN. get_hypervisor_meminfo 1: 1
[90198.540045] HE: get_hv_heap_size: 375. Hypervisor heap size: 0x23f800000
[90198.540045] HE: get_hv_cmrm_size: 387. Hypervisor cmrm size: 0x35ffff000
[90198.540046] HE: get_hv_frame_size: 400. Hypervisor frame size: 0xffc00000
[90198.540046] HE: get_hypervisor_size: 413. Hv_core_and_percpu_size: 0x8914000, Hypervisor size: 0x6c0000000
[90198.540047] HE: get_hypervisor_meminfo: 206. HE_WARN. get_hypervisor_meminfo 2r : 0x100000001, 0x800000000
[90198.540048] HE: get_hypervisor_meminfo: 207. HE_WARN. get_hypervisor_meminfo 2h : 0x0, 0x6c0000000
[90198.540049] HE: he_cmd_enable: 302. hypervisor size: 0x6c0000000
[90198.540050] HE: get_sme_mask: 68. SME mask: [0x8000000000000]
[90199.827205] HE: he_cmd_enable: 352. config_size: 2916
[90199.881821] HE: add_epc_pages: 43. total_epc_pages: 0x140000, free_epc_pages: 0x140000
[90199.881824] HE: init_enclave_page: 317. epc ranges: [0x7c0000000-0x900000000], 0x140000000
[90199.881825] HE: init_enclave_page: 333. Initialized EPC ranges size: 0x140000000
[90199.881827] HE: he_cmd_enable: 383. config_header load_addr: 0xffffff0008914000
[90199.881923] HE: he_cmd_enable: 404. mem_region load_addr: 0xffffff0008914124
[90199.881924] HE: inspect_tpm: 206. using fake tpm
[90199.881925] HE: he_cmd_enable: 411. tpm mmio type=8,size=0 pa=ffffffff
[90199.921574] HE: he_cmd_enable: 468. HE_ERROR. error_code: -22

Hi, @linguohua ,
It seems that there is no problem on the dmesg log. So it is better to have a look on the output of Serial Port.

My server is located in an IDC, far away from my work site, so it is not easy to get the log out from serial port, but I will try my best to get it later.

Actually, the output of Serial Port can be shown remotely,  could you please ask the service provider of IDC for more information?
Another thing it needs to be checked is that: What is the type (virtual machine or a bare mental machine) of the platform on which you run HyperEnclave? Currently, we do not support starting HyperEnclave on virtual machine.
For more information for your platform, could you please provide the output of cpuid for us? By typing cpuid in your shell:
$ sudo apt install cpuid
$ cpuid

Hi, @Bonjourz , sorry for my delay.
The CPU is AMD 7T83, and platform is bare meta machine.

Actually, the output of Serial Port can be shown remotely, could you please ask the service provider of IDC for more information?
Yes, i could. I will ask IDC for help tomorrow, I will post it here, along with 'cpuid' informations.
Again, thanks for your help.

Hi, @Bonjourz
I have got the log from serial port via IPMI.
When use the origin HyperEnclave code, the log as following:

It says that: the index out of bounds, so I change 'buddy_system_allocator' version to '0.8', which I can change 'LockedHeap'  bound to 64 instead of 32, in src/memory/heap.rs:
#[cfg_attr(not(test), global_allocator)]
static HEAP_ALLOCATOR: LockedHeap<64> = LockedHeap::<64>::new();

then, it hang again but at different position, the logs:

ok, now it says that the 'bitmap_allocator' has some problem, and I continue to modify the following codes in src/memory/frame.rs:
// Support max 1M * 4096 = 64GB memory.
type FrameAlloc = bitmap_allocator::BitAlloc16M;

but, it hangs frustratingly, at a new position, the logs:

Maybe the main reason of the problem is, my CPU is amd 7t83, it has 8 numas and 128 cores, for 16 cores per numa, maybe HyperEnclave dose not yet support such many cores.
Another example is, when i use the cmdline that is recommended by 'ReadMe' file of HyperEnclave: memmap=4G\\\$0x100000000 , HyperEnclave will failed too. but when I modify it to memmap=32G\\\$0x100000000  , it can go ahead, and finally hang the whole machine, as mentioned above.

Hi @linguohua ,
Thanks for your input. The third picture is a bit blurry, and the information shown is incomplete...
could you please show a clearer version which contains more logs of the third picture?

Hi, @Bonjourz.
Sorry again for my delay.
Here is the third pic,  with some improvement of quality:

The content of lines with read color is:
[ERROR][96]
panicked at 'called `Result::unwrap()` on an `Err` value: [src/memory/paging.rs:46:18] Bad address: AlreadyMapped((0, 14076680675840, READ | WRITE | EXECUTE | USER, Size1G))', src/cell.rs:2
Current Cpu: PerCpu {

Hi @linguohua.
Thanks for providing more information for us.

The log you provide

[ERROR][96]
panicked at 'called `Result::unwrap()` on an `Err` value: [src/memory/paging.rs:46:18] Bad address: AlreadyMapped((0, 14076680675840, READ | WRITE | EXECUTE | USER, Size1G))', src/cell.rs:2
Current Cpu: PerCpu {

is still incomplete. The log can show the line of codes which triggers the error: src/cell.rs:2...., but it seems the log is truncated.
Could you please add some log to get which expression in src/cell.rs triggers the error?

From the log you provide, the memory size of your platform is 2TB. Currently, the open-sourced HyperEnclave cannot support it... Could you please change the memory size of your platform to 512 GB?

Another way to support 2TB platform, we need some modifications on the code. But I cannot get accessed to your environment, it is hard to develop it. So here I can only provide some advise. Maybe you can remove the code at https://github.com/HyperEnclave/hyperenclave/blob/master/src/cell.rs#L159C21-L165:

                hvm.insert(MemoryRegion::new_with_offset_mapper(
                    hv_virt_start,
                    region.phys_start as HostPhysAddr,
                    region.size as usize,
                    MemFlags::READ | MemFlags::WRITE,
                ))?;
                // Support hardware encrypt when swap out EPC page to guest RAM
-               #[cfg(feature = "sme")]
-               hvm.insert(MemoryRegion::new_with_offset_mapper(
-                  region.virt_start as HostVirtAddr,
-                  region.phys_start as HostPhysAddr,
-                  region.size as usize,
-                  MemFlags::READ | MemFlags::WRITE | MemFlags::ENCRYPTED,
-               ))?;
                normal_world_mem_region.insert(
                    (region.phys_start as usize)..(region.phys_start + region.size) as usize,
                )?;

and then have a try.

Since HyperEnclave is a low-level software running on the bare-metal machine, so there exist some corner cases we still have not considered yet that HyperEnclave cannot handle for a new platform. Support for TB-level memory is a new feature which is in our plan. And currently, HyperEnclave should inform developers that it cannot support TB-level memory.
Thanks for your information to help us discover that. We will get some environment similar to that you provide and have a test.

If you have any updates, feel free to contact us. Looking forward to your reply.

Hi, @Bonjourz .
Thanks for your reply and suggestion.

The log can show the line of codes which triggers the error: src/cell.rs:2...., but it seems the log is truncated.

Here did you mean backtrace? But ‘PanicInfo' have no backtrace. I try to use std::backtrace crate and std::panic:set_hook function, but compile failed for HyperEnclave 'no-std' cfg.

Could you please change the memory size of your platform to 512 GB?

Yes, I use boot cmdline with mem=512G to limit the linux to use 512GB mem only.
But,  HyperEnclave still hang the whole machine, the difference is, there are no error logs:

Hi, @linguohua
Thanks agin for your information.

Hi, @Bonjourz . Thanks for your reply and suggestion.

The log can show the line of codes which triggers the error: src/cell.rs:2...., but it seems the log is truncated.

Here did you mean backtrace? But ‘PanicInfo' have no backtrace. I try to use std::backtrace crate and std::panic:set_hook function, but compile failed for HyperEnclave 'no-std' cfg.

I mean the error log can show which line of code in src/cell.rs triggers the error, but the log you provided seem to be truncated. In the log you provided perviously show that the line at 2x or 2xx (I can only see the number of 2...).

Could you please change the memory size of your platform to 512 GB?

Yes, I use boot cmdline with mem=512G to limit the linux to use 512GB mem only. But, HyperEnclave still hang the whole machine, the difference is, there are no error logs:

Cool! Could you please show the dmesg log and the configuration of the kernel command line again?

Hi, @Bonjourz
Sorry for my delay again.
And so many thanks for patience.
First of all, as mentioned earlier, i have made some changes to HyperEnclave's rust code:
 // Support max 1M * 4096 = 4GB memory.
-type FrameAlloc = bitmap_allocator::BitAlloc1M;
+type FrameAlloc = bitmap_allocator::BitAlloc16M;

 #[cfg_attr(not(test), global_allocator)]
-static HEAP_ALLOCATOR: LockedHeap = LockedHeap::new();
+static HEAP_ALLOCATOR: LockedHeap<64> = LockedHeap::<64>::new();

Then, my kernel command line:
BOOT_IMAGE=/boot/vmlinuz-5.4.0-166-generic root=UUID=7eb35854-7835-49d7-8c68-b7eb7e8f296c ro mem=512G memmap=32G$0x100000000 amd_iommu=off intremap=off no5lvl
Which use mem=512G  to limit linux kernel to use only 512GB mem.
Now, type bash start_hyperenclave.sh,  dmesg:
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: cpu_vendor_detect: 39. Vendor ID: AuthenticAMD
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000000000000 -> 0x00000000000a0000], type: System RAM
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000000a0000 -> 0x0000000000100000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000000100000 -> 0x0000000030000000], type: System RAM
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000030000000 -> 0x0000000030047000], type: ACPI Non-volatile Storage
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000030047000 -> 0x0000000075cf0000], type: System RAM
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000075cf0000 -> 0x0000000076000000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000076000000 -> 0x00000000a60b6000], type: System RAM
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000a60b6000 -> 0x00000000a820f000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000a820f000 -> 0x00000000a83c9000], type: ACPI Tables
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000a83c9000 -> 0x00000000a88d4000], type: ACPI Non-volatile Storage
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000a88d4000 -> 0x00000000a97ff000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000a97ff000 -> 0x00000000ac000000], type: System RAM
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000ac000000 -> 0x00000000b0000000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000b4280000 -> 0x00000000b4281000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000b5180000 -> 0x00000000b5181000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000be180000 -> 0x00000000be181000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000bf200000 -> 0x00000000bf301000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000c8180000 -> 0x00000000c8181000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000c9100000 -> 0x00000000c9200000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000c9300000 -> 0x00000000c9401000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000c9500000 -> 0x00000000c9600000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000f4180000 -> 0x00000000f4181000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000f5180000 -> 0x00000000f5181000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fea00000 -> 0x00000000feb00000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fec00000 -> 0x00000000fec01000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fec10000 -> 0x00000000fec11000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fed00000 -> 0x00000000fed01000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fed40000 -> 0x00000000fed45000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fed80000 -> 0x00000000fed90000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fedc0000 -> 0x00000000fedc1000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fedc2000 -> 0x00000000fedc9000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fee00000 -> 0x00000000fef00000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000ff000000 -> 0x0000000100000000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000100000000 -> 0x000000404fe00000], type: System RAM
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000000404fe00000 -> 0x0000004050000000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000004050000000 -> 0x000000804ff00000], type: System RAM
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000000804ff00000 -> 0x0000008050000000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000008050000000 -> 0x000000c04ff00000], type: System RAM
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000000c04ff00000 -> 0x000000c050000000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000000fd00000000 -> 0x0000010000000000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000010000000000 -> 0x0000013fff300000], type: System RAM
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000013fff300000 -> 0x0000014000000000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000014000000000 -> 0x0000017ffff00000], type: System RAM
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000017ffff00000 -> 0x0000018000000000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000018000000000 -> 0x000001bffff00000], type: System RAM
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000001bffff00000 -> 0x000001c000000000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000001c000000000 -> 0x000001fffff00000], type: System RAM
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000001fffff00000 -> 0x0000020000000000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000020000000000 -> 0x0000023ffff00000], type: System RAM
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000023ffff00000 -> 0x0000024010400000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000034030000000 -> 0x0000034040400000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000034060000000 -> 0x0000034070400000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000004c090000000 -> 0x000004c0a0400000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000004c0c0000000 -> 0x000004c0d0400000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000005c0f0000000 -> 0x000005c100400000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000005c120000000 -> 0x000005c130400000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000006c150000000 -> 0x000006c160400000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000007fc00000000 -> 0x000007fc04000000], type: Reserved
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 213. Convertible Memory[ 0]: 0x0000000000000000 -> 0x00000000000a0000
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 213. Convertible Memory[ 1]: 0x0000000000100000 -> 0x0000000030000000
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 213. Convertible Memory[ 2]: 0x0000000030047000 -> 0x0000000075cf0000
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 213. Convertible Memory[ 3]: 0x0000000076000000 -> 0x00000000a60b6000
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 213. Convertible Memory[ 4]: 0x00000000a97ff000 -> 0x00000000ac000000
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 213. Convertible Memory[ 5]: 0x0000000100000000 -> 0x000000404fe00000
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 213. Convertible Memory[ 6]: 0x0000004050000000 -> 0x000000804ff00000
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 213. Convertible Memory[ 7]: 0x0000008050000000 -> 0x000000c04ff00000
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 213. Convertible Memory[ 8]: 0x0000010000000000 -> 0x0000013fff300000
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 213. Convertible Memory[ 9]: 0x0000014000000000 -> 0x0000017ffff00000
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 213. Convertible Memory[10]: 0x0000018000000000 -> 0x000001bffff00000
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 213. Convertible Memory[11]: 0x000001c000000000 -> 0x000001fffff00000
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 213. Convertible Memory[12]: 0x0000020000000000 -> 0x0000023ffff00000
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_convertible_memory: 218. Convertible Memory size: 0x1fff7000000
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_valid_rsrv_mem: 285. Reserved Memory[ 0]: 0x100000000 -> 0x900000000
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_valid_rsrv_mem: 290. Reserved Memory size: 0x800000000
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: get_sme_mask: 68. SME mask: [0x8000000000000]
kern  :info  : [Mon Nov 13 14:37:34 2023] HE: mem_test: 48. Memory[0x100000000 - 0x300000000] test begin
kern  :info  : [Mon Nov 13 14:37:35 2023] HE: mem_test: 78. Memory[0x100000000 - 0x300000000] test pass
kern  :info  : [Mon Nov 13 14:37:35 2023] HE: mem_test: 48. Memory[0x300000000 - 0x500000000] test begin
kern  :info  : [Mon Nov 13 14:37:37 2023] HE: mem_test: 78. Memory[0x300000000 - 0x500000000] test pass
kern  :info  : [Mon Nov 13 14:37:37 2023] HE: mem_test: 48. Memory[0x500000000 - 0x700000000] test begin
kern  :info  : [Mon Nov 13 14:37:40 2023] HE: mem_test: 78. Memory[0x500000000 - 0x700000000] test pass
kern  :info  : [Mon Nov 13 14:37:40 2023] HE: mem_test: 48. Memory[0x700000000 - 0x900000000] test begin
kern  :info  : [Mon Nov 13 14:37:42 2023] HE: mem_test: 78. Memory[0x700000000 - 0x900000000] test pass
kern  :warn  : [Mon Nov 13 14:37:42 2023] HE: get_hypervisor_meminfo: 185. HE_WARN. get_hypervisor_meminfo 1 : 0x100000001, 0x800000000
kern  :warn  : [Mon Nov 13 14:37:42 2023] HE: get_hypervisor_meminfo: 198. HE_WARN. get_hypervisor_meminfo 1: 1
kern  :info  : [Mon Nov 13 14:37:42 2023] HE: get_hv_heap_size: 375. Hypervisor heap size: 0x23f800000
kern  :info  : [Mon Nov 13 14:37:42 2023] HE: get_hv_cmrm_size: 387. Hypervisor cmrm size: 0x35ffff000
kern  :info  : [Mon Nov 13 14:37:42 2023] HE: get_hv_frame_size: 400. Hypervisor frame size: 0xffc00000
kern  :info  : [Mon Nov 13 14:37:42 2023] HE: get_hypervisor_size: 413. Hv_core_and_percpu_size: 0x8b10000, Hypervisor size: 0x6c0000000
kern  :warn  : [Mon Nov 13 14:37:42 2023] HE: get_hypervisor_meminfo: 206. HE_WARN. get_hypervisor_meminfo 2r : 0x100000001, 0x800000000
kern  :warn  : [Mon Nov 13 14:37:42 2023] HE: get_hypervisor_meminfo: 207. HE_WARN. get_hypervisor_meminfo 2h : 0x0, 0x6c0000000
kern  :info  : [Mon Nov 13 14:37:42 2023] HE: he_cmd_enable: 302. hypervisor size: 0x6c0000000
kern  :info  : [Mon Nov 13 14:37:42 2023] HE: get_sme_mask: 68. SME mask: [0x8000000000000]
kern  :info  : [Mon Nov 13 14:37:43 2023] HE: he_cmd_enable: 352. config_size: 2724
kern  :info  : [Mon Nov 13 14:37:43 2023] HE: add_epc_pages: 43. total_epc_pages: 0x140000, free_epc_pages: 0x140000
kern  :info  : [Mon Nov 13 14:37:43 2023] HE: init_enclave_page: 317. epc ranges: [0x7c0000000-0x900000000], 0x140000000
kern  :info  : [Mon Nov 13 14:37:43 2023] HE: init_enclave_page: 333. Initialized EPC ranges size: 0x140000000
kern  :info  : [Mon Nov 13 14:37:43 2023] HE: he_cmd_enable: 383. config_header load_addr: 0xffffff0008b10000
kern  :info  : [Mon Nov 13 14:37:43 2023] HE: he_cmd_enable: 404. mem_region load_addr: 0xffffff0008b10124
kern  :info  : [Mon Nov 13 14:37:43 2023] HE: inspect_tpm: 206. using fake tpm
kern  :info  : [Mon Nov 13 14:37:43 2023] HE: he_cmd_enable: 411. tpm mmio type=8,size=0 pa=ffffffff

IPMI Serial port logs:

The logs above are results when kernel runs with 512GB mem, and finally the system is hanged.
Following are results when kernel runs with 2TB mem.
Kernel cmdline:
BOOT_IMAGE=/boot/vmlinuz-5.4.0-166-generic root=UUID=7eb35854-7835-49d7-8c68-b7eb7e8f296c ro memmap=32G$0x100000000 amd_iommu=off intremap=off no5lvl
Dmesg:
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: cpu_vendor_detect: 39. Vendor ID: AuthenticAMD
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000000000000 -> 0x00000000000a0000], type: System RAM
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000000a0000 -> 0x0000000000100000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000000100000 -> 0x0000000030000000], type: System RAM
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000030000000 -> 0x0000000030047000], type: ACPI Non-volatile Storage
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000030047000 -> 0x0000000075cf0000], type: System RAM
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000075cf0000 -> 0x0000000076000000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000076000000 -> 0x00000000a60b6000], type: System RAM
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000a60b6000 -> 0x00000000a820f000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000a820f000 -> 0x00000000a83c9000], type: ACPI Tables
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000a83c9000 -> 0x00000000a88d4000], type: ACPI Non-volatile Storage
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000a88d4000 -> 0x00000000a97ff000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000a97ff000 -> 0x00000000ac000000], type: System RAM
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000ac000000 -> 0x00000000b0000000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000b4280000 -> 0x00000000b4281000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000b5180000 -> 0x00000000b5181000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000be180000 -> 0x00000000be181000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000bf200000 -> 0x00000000bf301000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000c8180000 -> 0x00000000c8181000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000c9100000 -> 0x00000000c9200000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000c9300000 -> 0x00000000c9401000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000c9500000 -> 0x00000000c9600000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000f4180000 -> 0x00000000f4181000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000f5180000 -> 0x00000000f5181000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fea00000 -> 0x00000000feb00000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fec00000 -> 0x00000000fec01000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fec10000 -> 0x00000000fec11000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fed00000 -> 0x00000000fed01000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fed40000 -> 0x00000000fed45000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fed80000 -> 0x00000000fed90000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fedc0000 -> 0x00000000fedc1000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fedc2000 -> 0x00000000fedc9000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000fee00000 -> 0x00000000fef00000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x00000000ff000000 -> 0x0000000100000000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000000100000000 -> 0x000000404fe00000], type: System RAM
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000000404fe00000 -> 0x0000004050000000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000004050000000 -> 0x000000804ff00000], type: System RAM
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000000804ff00000 -> 0x0000008050000000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000008050000000 -> 0x000000c04ff00000], type: System RAM
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000000c04ff00000 -> 0x000000c050000000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000000fd00000000 -> 0x0000010000000000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000010000000000 -> 0x0000013fff300000], type: System RAM
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000013fff300000 -> 0x0000014000000000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000014000000000 -> 0x0000017ffff00000], type: System RAM
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000017ffff00000 -> 0x0000018000000000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000018000000000 -> 0x000001bffff00000], type: System RAM
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000001bffff00000 -> 0x000001c000000000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000001c000000000 -> 0x000001fffff00000], type: System RAM
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000001fffff00000 -> 0x0000020000000000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000020000000000 -> 0x0000023ffff00000], type: System RAM
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000023ffff00000 -> 0x0000024010400000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000034030000000 -> 0x0000034040400000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x0000034060000000 -> 0x0000034070400000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000004c090000000 -> 0x000004c0a0400000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000004c0c0000000 -> 0x000004c0d0400000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000005c0f0000000 -> 0x000005c100400000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000005c120000000 -> 0x000005c130400000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000006c150000000 -> 0x000006c160400000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 136. BIOS E820 table from firmware: [0x000007fc00000000 -> 0x000007fc04000000], type: Reserved
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 213. Convertible Memory[ 0]: 0x0000000000000000 -> 0x00000000000a0000
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 213. Convertible Memory[ 1]: 0x0000000000100000 -> 0x0000000030000000
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 213. Convertible Memory[ 2]: 0x0000000030047000 -> 0x0000000075cf0000
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 213. Convertible Memory[ 3]: 0x0000000076000000 -> 0x00000000a60b6000
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 213. Convertible Memory[ 4]: 0x00000000a97ff000 -> 0x00000000ac000000
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 213. Convertible Memory[ 5]: 0x0000000100000000 -> 0x000000404fe00000
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 213. Convertible Memory[ 6]: 0x0000004050000000 -> 0x000000804ff00000
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 213. Convertible Memory[ 7]: 0x0000008050000000 -> 0x000000c04ff00000
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 213. Convertible Memory[ 8]: 0x0000010000000000 -> 0x0000013fff300000
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 213. Convertible Memory[ 9]: 0x0000014000000000 -> 0x0000017ffff00000
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 213. Convertible Memory[10]: 0x0000018000000000 -> 0x000001bffff00000
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 213. Convertible Memory[11]: 0x000001c000000000 -> 0x000001fffff00000
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 213. Convertible Memory[12]: 0x0000020000000000 -> 0x0000023ffff00000
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_convertible_memory: 218. Convertible Memory size: 0x1fff7000000
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_valid_rsrv_mem: 285. Reserved Memory[ 0]: 0x100000000 -> 0x900000000
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_valid_rsrv_mem: 290. Reserved Memory size: 0x800000000
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: get_sme_mask: 68. SME mask: [0x8000000000000]
kern  :info  : [Mon Nov 13 15:15:46 2023] HE: mem_test: 48. Memory[0x100000000 - 0x300000000] test begin
kern  :info  : [Mon Nov 13 15:15:47 2023] HE: mem_test: 78. Memory[0x100000000 - 0x300000000] test pass
kern  :info  : [Mon Nov 13 15:15:47 2023] HE: mem_test: 48. Memory[0x300000000 - 0x500000000] test begin
kern  :info  : [Mon Nov 13 15:15:50 2023] HE: mem_test: 78. Memory[0x300000000 - 0x500000000] test pass
kern  :info  : [Mon Nov 13 15:15:50 2023] HE: mem_test: 48. Memory[0x500000000 - 0x700000000] test begin
kern  :info  : [Mon Nov 13 15:15:53 2023] HE: mem_test: 78. Memory[0x500000000 - 0x700000000] test pass
kern  :info  : [Mon Nov 13 15:15:53 2023] HE: mem_test: 48. Memory[0x700000000 - 0x900000000] test begin
kern  :info  : [Mon Nov 13 15:15:56 2023] HE: mem_test: 78. Memory[0x700000000 - 0x900000000] test pass
kern  :warn  : [Mon Nov 13 15:15:56 2023] HE: get_hypervisor_meminfo: 185. HE_WARN. get_hypervisor_meminfo 1 : 0x100000001, 0x800000000
kern  :warn  : [Mon Nov 13 15:15:56 2023] HE: get_hypervisor_meminfo: 198. HE_WARN. get_hypervisor_meminfo 1: 1
kern  :info  : [Mon Nov 13 15:15:56 2023] HE: get_hv_heap_size: 375. Hypervisor heap size: 0x23f800000
kern  :info  : [Mon Nov 13 15:15:56 2023] HE: get_hv_cmrm_size: 387. Hypervisor cmrm size: 0x35ffff000
kern  :info  : [Mon Nov 13 15:15:56 2023] HE: get_hv_frame_size: 400. Hypervisor frame size: 0xffc00000
kern  :info  : [Mon Nov 13 15:15:56 2023] HE: get_hypervisor_size: 413. Hv_core_and_percpu_size: 0x8b10000, Hypervisor size: 0x6c0000000
kern  :warn  : [Mon Nov 13 15:15:56 2023] HE: get_hypervisor_meminfo: 206. HE_WARN. get_hypervisor_meminfo 2r : 0x100000001, 0x800000000
kern  :warn  : [Mon Nov 13 15:15:56 2023] HE: get_hypervisor_meminfo: 207. HE_WARN. get_hypervisor_meminfo 2h : 0x0, 0x6c0000000
kern  :info  : [Mon Nov 13 15:15:56 2023] HE: he_cmd_enable: 302. hypervisor size: 0x6c0000000
kern  :info  : [Mon Nov 13 15:15:56 2023] HE: get_sme_mask: 68. SME mask: [0x8000000000000]
kern  :info  : [Mon Nov 13 15:15:57 2023] HE: he_cmd_enable: 352. config_size: 2916
kern  :info  : [Mon Nov 13 15:15:57 2023] HE: add_epc_pages: 43. total_epc_pages: 0x140000, free_epc_pages: 0x140000
kern  :info  : [Mon Nov 13 15:15:57 2023] HE: init_enclave_page: 317. epc ranges: [0x7c0000000-0x900000000], 0x140000000
kern  :info  : [Mon Nov 13 15:15:57 2023] HE: init_enclave_page: 333. Initialized EPC ranges size: 0x140000000
kern  :info  : [Mon Nov 13 15:15:57 2023] HE: he_cmd_enable: 383. config_header load_addr: 0xffffff0008b10000
kern  :info  : [Mon Nov 13 15:15:57 2023] HE: he_cmd_enable: 404. mem_region load_addr: 0xffffff0008b10124
kern  :info  : [Mon Nov 13 15:15:57 2023] HE: inspect_tpm: 206. using fake tpm
kern  :info  : [Mon Nov 13 15:15:57 2023] HE: he_cmd_enable: 411. tpm mmio type=8,size=0 pa=ffffffff

Logs from serial port:

Hi @linguohua ,
Thanks for providing the information for us.
After have a try on my platform, I'm sorry to tell you that HyperEnclave does not support 2TB memory, even though we limit memory use by kernel in command line: mem=512G.
We are working to add TB-level memory support for HyperEnclave in the near future. So, we can only start HyperEnclave on the platform with memory size less than 1TB currently. Could you please have a try on another platform with 512GB memory. Sorry for that 🙏
Thank you again for help us discover that HyperEnclave could not throw warnings if the configuration of the platform that HyperEnclave cannot adapt to. And we are working to fixing such issue now.
For this issue, we look forward to having a deeper communication and conversation with you 😊. Could you please provide your email for us or contact me: bojun.zhu@foxmail.com?
Looking forward to your reply!

Hi, @Bonjourz
So many thanks for your patience and help.
I will try HyperEnclave on a server with physical 512GB mem, then write a report and mail it to you.
Now I close this issue, and I hope that we can keep going on via emails.

Hi @linguohua , can you successfully try HyperEnclave on machine with 512 GB physical memory now?
If you find that it is difficult to get a new machine with 512GB physical memory, you can also try our workaround patch (It can address the issue that virtual address beyond 1TB will cause address space collision):
$git diff src/cell.rs
diff --git a/src/cell.rs b/src/cell.rs
index 928e1e1..f618087 100644
--- a/src/cell.rs
+++ b/src/cell.rs
@@ -140,29 +140,12 @@ impl Cell {
         for region in sys_config.mem_regions() {
             if region.flags.contains(MemFlags::DMA) {
                 let hv_virt_start = phys_to_virt(region.virt_start as GuestPhysAddr);
-                if hv_virt_start < region.virt_start as GuestPhysAddr {
-                    return hv_result_err!(
-                        EINVAL,
-                        format!(
-                            "Guest physical address {:#x} is too large",
-                            region.virt_start
-                        )
-                    );
-                }
                 hvm.insert(MemoryRegion::new_with_offset_mapper(
                     hv_virt_start,
                     region.phys_start as HostPhysAddr,
                     region.size as usize,
                     MemFlags::READ | MemFlags::WRITE,
                 ))?;
-                // Support hardware encrypt when swap out EPC page to guest RAM
-                #[cfg(feature = "sme")]
-                hvm.insert(MemoryRegion::new_with_offset_mapper(
-                    region.virt_start as HostVirtAddr,
-                    region.phys_start as HostPhysAddr,
-                    region.size as usize,
-                    MemFlags::READ | MemFlags::WRITE | MemFlags::ENCRYPTED,
-                ))?;
                 normal_world_mem_region.insert(
                     (region.phys_start as usize)..(region.phys_start + region.size) as usize,
                 )?;

Here, you only need to apply modifications above on src/cell.rs, and then recompile and install  HyperEnclave by:
$ make VENDOR=amd SME=on LOG=warn
$ make VENDOR=amd SME=on LOG=warn install

Then, start HyperEnclave:
$ cd hyperenclave/scripts
$ bash start_hyperenclave.sh

authors: Bonjourz linguohua

repo: HyperEnclave/hyperenclave