Re: Problem with Industry Scenario on a NUC7i7DNH


Wu, Xiangyang
 

Hi Steve,

Please check my comments below, thanks!

-----Original Message-----
From: acrn-users@... <acrn-users@...>
On Behalf Of Yin, Fengwei
Sent: Friday, April 3, 2020 5:21 PM
To: acrn-users@...
Subject: Re: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH

Hi Steve,

On 2020/4/3 下午5:16, Steve Osselton wrote:
Have attached dmesg log. Actually looks like ttyS0 is using 0x3f8:

#  dmesg | grep tty
[    0.000000] Command line:
initrd=\EFI\org.clearlinux\freestanding-00-intel-ucode.cpio
initrd=\EFI\org.clearlinux\freestanding-i915-firmware.cpio.xz
root=PARTUUID=94a40b85-bbce-41ee-8fe7-4c85e8a89068 quiet
console=tty0
console=ttyS0,115200n8 consoleblank=0 cryptomgr.notests
hvlog=2M@0x1FE00000 i915.avail_planes_per_pipe=0x01010F
i915.domain_plane_owners=0x011111110000 i915.enable_guc=0
i915.enable_gvt=1 i915.nuclear_pageflip=1 ignore_loglevel
init=/usr/lib/systemd/systemd-bootchart intel_iommu=igfx_off
memmap=2M$0x1FE00000 no_timer_check no_timer_check noreplace-
smp
rcu_nocbs=0-64 rcupdate.rcu_expedited=1 rootfstype=ext4,btrfs,xfs
rootwait tsc=reliable rw
[    0.123693] Kernel command line:
initrd=\EFI\org.clearlinux\freestanding-00-intel-ucode.cpio
initrd=\EFI\org.clearlinux\freestanding-i915-firmware.cpio.xz
root=PARTUUID=94a40b85-bbce-41ee-8fe7-4c85e8a89068 quiet
console=tty0
console=ttyS0,115200n8 consoleblank=0 cryptomgr.notests
hvlog=2M@0x1FE00000 i915.avail_planes_per_pipe=0x01010F
i915.domain_plane_owners=0x011111110000 i915.enable_guc=0
i915.enable_gvt=1 i915.nuclear_pageflip=1 ignore_loglevel
init=/usr/lib/systemd/systemd-bootchart intel_iommu=igfx_off
memmap=2M$0x1FE00000 no_timer_check no_timer_check noreplace-
smp
rcu_nocbs=0-64 rcupdate.rcu_expedited=1 rootfstype=ext4,btrfs,xfs
rootwait tsc=reliable rw
[    0.202532] console [tty0] enabled
[    0.275084] console [ttyS0] enabled
[    0.711180] 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200)
is a 16550A
[    0.966636] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud =
115200) is a 16550A
[    0.988793] 0000:00:16.3: ttyS2 at I/O 0xf0a0 (irq = 19, base_baud =
115200) is a 16550A
[    1.666800] systemd[1]: system-getty.slice: unit configures an IP
firewall, but the local system does not support BPF/cgroup firewalling.
[    1.669839] systemd[1]: Created slice system-getty.slice.
[    1.670160] systemd[1]: Created slice system-serial\x2dgetty.slice.
From the kernel, the SOS serial console is using ttyS0:
console=ttyS0,115200n8
And it looks like everything is fine from the dmesg output.

So which serial port is broken? ACRN? SOS kernel?
Can you double check your serial cable connecting with KBL NUC following guidelines (https://projectacrn.github.io/latest/getting-started/rt_industry.html#use-serial-port-on-kbl-nuc)? Thanks!

BRs,
Xiangyang Wu.

Join acrn-users@lists.projectacrn.org to automatically receive all group messages.