Bug 1367 - [anolis7][aarch64]rhck镜像加载后,dmesg下有异常error和warn信息
Summary: [anolis7][aarch64]rhck镜像加载后,dmesg下有异常error和warn信息
Status: CONFIRMED
Alias: None
Product: Anolis OS 7
Classification: Anolis OS
Component: Images&Installations (show other bugs) Images&Installations
Version: 7.9
Hardware: aarch64 Linux
: P3-Medium S3-normal
Target Milestone: ---
Assignee: xunlei
QA Contact: shuming
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-30 19:28 UTC by liuyaqing
Modified: 2022-11-07 13:49 UTC (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description liuyaqing alibaba_cloud_group 2022-05-30 19:28:47 UTC
Description of problem:
ecs.g6r.large加载anck镜像,启动后dmesg有异常warn和err信息
镜像:anolisos_7_9_arm64_20G_rhck_alibase_20220518.vhd
# dmesg -l err -T
[Mon May 30 19:03:56 2022] pcieport 0000:00:03.1: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:03.0: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:02.7: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:02.6: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:02.5: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:02.4: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:02.3: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:02.2: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:02.1: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:02.0: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:08.6: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:08.5: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:08.4: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:08.3: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:08.2: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:08.1: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:08.0: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:07.7: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:07.6: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:07.5: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:07.4: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:07.3: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:07.2: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:07.1: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:07.0: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:06.7: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:06.6: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:06.5: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:06.4: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:06.3: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:06.2: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:06.1: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:06.0: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:05.7: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:05.6: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:05.5: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:05.4: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:05.3: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:05.2: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:05.1: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:05.0: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:04.7: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:04.6: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:04.5: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:04.4: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:04.3: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:04.2: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:04.1: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:04.0: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:03.7: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:03.6: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:03.5: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:03.4: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:03.3: Failed to check link status
[Mon May 30 19:03:56 2022] pcieport 0000:00:03.2: Failed to check link status

# dmesg -l warn -T
[Mon May 30 19:03:52 2022] ACPI PPTT: No PPTT table found, CPU and cache topology may be inaccurate
[Mon May 30 19:03:53 2022] cacheinfo: Unable to detect cache hierarchy for CPU 0
[Mon May 30 19:03:54 2022] printk: systemd: 15 output lines suppressed due to ratelimiting
[Mon May 30 19:03:55 2022] FAT-fs (vda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Version-Release number of selected component (if applicable):
# cat /etc/image-id
image_name="Anolis OS 7.9 RHCK 64 bit ARM Edition"
image_id="anolisos_7_9_arm64_20G_rhck_alibase_20220518.vhd"
release_date="20220518121027"


# uname -a
Linux iZbp14924q5i68ekb4cqlzZ 4.18.0-193.28.1.an7.aarch64 #1 SMP Wed Dec 22 16:43:38 CST 2021 aarch64 aarch64 aarch64 GNU/Linux


How reproducible:


Steps to Reproduce:
1.镜像测试,启动后查看dmesg有异常err和warn
dmesg -l err -T
dmesg -l warn -T
2.
3.

Actual results:
dmesg有异常err和warn信息

Expected results:
dmesg没有异常err和warn信息

Additional info:
Comment 2 cherryliyumei alibaba_cloud_group 2022-06-01 18:15:36 UTC
不影响发布,