Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SQL error during submission #42

Open
johntron opened this issue Feb 7, 2024 · 2 comments
Open

SQL error during submission #42

johntron opened this issue Feb 7, 2024 · 2 comments
Assignees

Comments

@johntron
Copy link

johntron commented Feb 7, 2024

My results aren't appearing on the site. I debugged and looks like $Submit holds some unexpected HTML. I saved this and opened in my browser:
image

@stevefalco
Copy link

I'm getting the same error, for what it is worth.

@stevefalco
Copy link

stevefalco commented Mar 9, 2024

I've poked around a bit more, and added a set -x at the top of the script. One thing that looks peculiar is the nvme show-regs probe:

++ nvme show-regs /dev/nvme0n1p2 -H
++ sed 's/;/!/g'
++ sed 's/\x0//g'
+ Test_nvme+='get-property: No such file or directory
��<cÿ���<cÿ�er Ready With Media Support (CRWMS): Not Supported
	Controller Ready Independent of Media Support (CRIMS): Not Supported

There are a bunch of gibberish characters, which may be causing the problem. Also, if I run the command manually, I get an abort:

# nvme show-regs /dev/nvme0n1p2 -H
...
double free or corruption (!prev)
Aborted

If I comment out the probe at around line 401 in the script, then it runs to completion and tells me that my submission was processed correctly.

This is the line that I removed:

Test_nvme+=$(nvme show-regs "$BootDrive" -H 2>&1 | sed 's/;/!/g' | sed 's/\x0//g')

I looked at the source code for the nvme tool, and I see:

ENTRY("show-regs", "Shows the controller registers or properties. Requires character device", show_registers)

Notice that the above indicates that a character device is needed for the show-regs command. The nvme show-regs call is operating on "$BootDrive", which in my case is /dev/nvme0n1p2. But /dev/nvme0n1p2 is a block device, not a character device.

Looking at the help for that command via nvme help show-regs says in part:

       The <device> parameter is mandatory and must be the nvme admin
       character device (ex: /dev/nvme0).

I don't know how the pibenchmarks.com web site uses the information, so I'm not sure what the correct fix would be, but it seems illegal to use $BootDrive with nvme show-regs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants