diff --git a/README.md b/README.md index 42aea63e085bc3acfe1a54ee88360113c4f05613..0c51de0c488e40d07a9aaca278f3a23595b8e4c5 100644 --- a/README.md +++ b/README.md @@ -143,35 +143,29 @@ Please follow the following general instructions for collecting SystemReady ES o #### `./fw/uefi-shell-cmds-logs/` - Run the UEFI Shell commands below and attach the logs. +- Check ACS media device's result partition's \acs_results\uefi_dump folder. If no log in the folder, please manually load debug_dump.nsh in ACS media device's boot partition's Boot\EFI\BOOT\debug folder to run few more UEFI Shell commands and attach the logs. - The UEFI Shell can be run from the ACS test suite by interrupting the automated run, and pressing a key at the UEFI timeout prompt before the tests begin to execute. ``` Shell> connect -r - Shell> map -r - Shell> ver - Shell> dmem - Shell> pci - Shell> drivers - Shell> devices - Shell> devtree - Shell> dh -d -v - Shell> dmpstore - Shell> memmap - Shell> smbiosview - Shell> acpiview -l - Shell> acpiview - Shell> acpiview -r 2 + Shell> dh -d -v > dh_d_v.log Shell> acpiview -s DSDT -d (if DSDT table is present) - Shell> acpiview -s SSDT -d (if SSDT table is present) - Shell> bcfg boot dump -v + Shell> acpiview -s SSDT -d (if SSDT table is present) + Shell> bcfg boot dump -v > bcfg_boot_dump_v.log Shell> ifconfig -l - Shell> ifconfig -s eth0 dhcp (If eth0 doesn't display an updated IP address, run "connect -r" again) - Shell> ifconfig -l eth0 + (If "ifconfig -l" output message shows a network port having IP address, skip other ifconfig commands below and directly run ping command.) + Shell> ifconfig -s eth dhcp (The is shown in ) + Shell> connect -r + Shell> ifconfig -l eth Shell> ping xxx.xxx.xxx.xxx (If don’t know any other system’s IP address, you can get DNS Server's IP address from ifconfig output and ping it) ``` ### `./os-logs/` - Please check ./os_logs/OS_image_download_links.txt to get the latest publicly available AARCH64 OS images for testing. - +- The boot and install logs are required and can be collected by serial console. Both logs must begin when the platform is released from reset and must include: + - All firmware output + - Output from the Linux installer + - Output of reboot to the installed OS. + #### `./os-logs/[distroname] [distroversion]/` - Please rename the subfolders to indicate the OS name and version. For example, rename 'linux-distro1-version' to 'Fedora Server 37'. - It is recommended to choose one OS per group below, an OS based on an old kernel, and an OS based on an kernel version close to the latest kernel for certification testing to cover as many kernel versions as possible. @@ -181,44 +175,22 @@ Please follow the following general instructions for collecting SystemReady ES o - For SystemReady ES, you can choose Fedora, openSUSE, Ubuntu, and CentOS 7 for your testing. - For each OS being tested - Install the OS from some media (eg. USB drive) to a disk (e.g. SATA, NVMe, USB), and boot it. - - Note that a network controller (PCIe or USB) may be needed during installation. - - The install log must begin when the platform is released from reset and must include: - - All firmware output - - Output from the Linux installer - - Output of reboot to the installed OS. - - Run the following commands and attach the logs: (For example, save dmesg messages to dmesg.txt). Note that some commands may not exist on some OS distros, and you may need to install additional packages or run alternative commands. + - A network controller (PCIe or USB) may be needed during installation. + - The OS commands output and files are required. For collecting them, run the commands below to download and run the script linux-distro-cmds.sh. Then, copy all the files that are collected in ~/CertTestLogs folder to the template's ./os-logs/[distroname] [distroversion]/ folder. + - If network port doesn't get IP address, giving "dhclient" or "ip a add /255.255.255.0 dev eth" and "ip link set dev eth up" a try might be helpful. + - If the network doesn't work, please manually run the commands in ./os-logs/linux-distro-cmds.sh. + - For manually running the ping commnad, if the system is connected to intranet, please ping the IP address of another system within the intranet instead. ``` sudo -s (Prevent from running into "Permission denied" error) - dmesg - lspci - lspci -vvv - cat /proc/interrupts - cat /proc/cpuinfo - cat /proc/meminfo - lscpu - lsblk - lsusb - dmidecode - uname -a - cat /etc/os-release - efibootmgr (Check the output message to know the ) - efibootmgr -t 20 - efibootmgr -t - efibootmgr -c - ifconfig (If ifconfig is not supported, use "ip addr show" and "ip link show" instead.) - (If network port doesn't get IP address, run "dhclient" or "ip a add /255.255.255.0 dev eth" and "ip link set dev eth up") - ping -c 5 www.arm.com (If the system is connected to intranet, please ping another system's IP address) - Go to /sys/firmware and use "ls -lR" (Or use tree /sys/firmware/) - + wget https://gitlab.arm.com/systemready/systemready-es-sr-template/-/raw/main/os-logs/linux-distro-cmds.sh + chmod +x linux-distro-cmds.sh + ./linux-distro-cmds.sh ``` -- Copy the entire content of /sys/firmware and attach zipped/archive file. - - Note that running "tar -cvzf //sys_firmware.tgz /sys/firmware/" may result in corruption. In this case, you can run "cp -r sys/firmware " and then separately compress the files. #### `./os-logs/vmware [version]/` -- Please rename the subfolders. For example, rename 'vmware-version' to 'VMware ESXi 1.11' -- Install VMWare ESXi to a disk, and boot it. Note that a network controller (PCIe or USB) is required to complete the installation. -- Collect the installation and OS boot logs and save in a text file. If there is no serial output log, attach screenshots or a video instead. +- Please rename the subfolders. For example, rename 'vmware-version' to 'VMware ESXi 1.12' +- Install VMware ESXi to a disk, and boot it. Note that a network controller (PCIe or USB) is required to complete the installation. - Connect to vSphere web console over network (from a remote client) and capture some screenshots. - Follow the instruction in https://kb.vmware.com/s/article/2004746 to enable ESXi Shell and SSH. - Connect ESXi shell through the SSH and Run the following commands and attach the logs: @@ -252,16 +224,15 @@ Please follow the following general instructions for collecting SystemReady ES o ch (run this command after the message "EVENT: A new channel has been created".) Esc + Tab (Switch channel to command channel (like Cmd0001) for running WinPE commands) ver - Systeminfo (This may not be supported) pnputil/enum-devices pnputil/enum-drivers diskpart list disk - list partition + list volume exit c: dir/w - ipconfig + ipconfig /all date time Esc + Tab (Switch channel to SAC> for running SAC commands) diff --git a/SystemReady-[band]-[SystemName]-[DateYYYYMMDD].zip b/SystemReady-[band]-[SystemName]-[DateYYYYMMDD].zip index 2cfbab5fe0e151f8db660a8e4d96fb4bdd1d2575..613ca6d2e3f7e73d80f657970b10283a901be437 100644 Binary files a/SystemReady-[band]-[SystemName]-[DateYYYYMMDD].zip and b/SystemReady-[band]-[SystemName]-[DateYYYYMMDD].zip differ diff --git a/os-logs/linux-distro-cmds.sh b/os-logs/linux-distro-cmds.sh new file mode 100644 index 0000000000000000000000000000000000000000..4975d1396cc3634f6290c57f7e169dc753c90e19 --- /dev/null +++ b/os-logs/linux-distro-cmds.sh @@ -0,0 +1,41 @@ +#!/bin/sh +set -x +mkdir ~/CertTestLogs +cd ~/CertTestLogs +dmesg 2>&1 |tee dmesg.txt +lspci 2>&1 |tee lspci.txt +cat /proc/interrupts 2>&1 |tee cat-proc-interrupts.txt +cat /proc/cpuinfo 2>&1 |tee cat-proc-cpuinfo.txt +cat /proc/meminfo 2>&1 |tee cat-proc-meminfo.txt +lscpu 2>&1 |tee lscpu.txt +lsblk 2>&1 |tee lsblk.txt +lsusb 2>&1 |tee lsusb.txt +dmidecode 2>&1 |tee dmidecode.txt +dmidecode --dump-bin dmidecode.bin +uname -a 2>&1 |tee uname-a.txt +cat /etc/os-release 2>&1 |tee cat-etc-os-release.txt +date 2>&1 |tee date.txt +timedatectl 2>&1 |tee timedatectl.txt +hwclock 2>&1 |tee hwclock.txt +efibootmgr 2>&1 |tee efibootmgr.txt +efibootmgr -t 20 2>&1 |tee efibootmgr-t-20.txt +efibootmgr -t 5 2>&1 |tee efibootmgr-t-5.txt +efibootmgr -c 2>&1 |tee efibootmgr-c.txt +ifconfig 2>&1 |tee ifconfig.txt +ip addr show 2>&1 |tee ip-addr-show.txt +ping -c 5 www.arm.com +ping -c 5 www.arm.com > ping-c-5-www-arm-com.txt +echo date --set="20221215 05:30" +date --set="20221215 05:30" +date +hwclock --set --date "2023-01-01 09:10:15" +hwclock +cd /sys/firmware +ls -lR +cp -r /sys/firmware ~/CertTestLogs/ +cd ~/CertTestLogs +apt-get install -y acpica-tools +acpidump > acpi.log +acpixtract acpi.log +iasl -d *.dat +cd /mnt/usb/OS_sys_firmware \ No newline at end of file