Your message dated Wed, 26 Feb 2020 23:10:45 +0000 with message-id <d34275ad9d4e0ff0ae8860f56323b0740cb07d34.camel@decadent.org.uk> and subject line Re: Bug#952452: initramfs-tools: prefers serial console over framebuffer console has caused the Debian Bug report #952452, regarding initramfs-tools: prefers serial console over framebuffer console to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 952452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952452 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: initramfs-tools: prefers serial console over framebuffer console
- From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
- Date: Mon, 24 Feb 2020 19:50:59 +0300
- Message-id: <[🔎] d3059269-a87e-23a2-a775-54e04993b517@gmail.com>
Package: initramfs-tools Version: 0.136 Severity: minor Dear kernel team,I'm using Debian on an arm64 chromebook, and not setting "console=tty1" in the kernel command line results in a number of weird behaviours related to the initramfs.During an ordinary boot, plymouth doesn't show the futureprototype boot splash. Instead, it shows the init log; but pressing ESC does switch to plymouth (but with what I'm assuming is the text theme instead).If I use "break" (even "break=init") in the kernel command line, I don't see an initramfs shell prompt and the keyboard does nothing. If plymouth is installed, I see the "Spawning shell within the initramfs" message but rest is the same (plymouth quits in it's panic hook).When I'm trying to boot from an encrypted root (different installation), I don't see the "Please unlock disk" cryptsetup prompt and can't type a passphrase; unless plymouth is installed.I'm able to boot the encrypted system as a QEMU virtual machine and I get similar behaviour there, no messages or prompts are printed to the graphical console and instead all go to the serial console. However having plymouth doesn't make the cryptsetup prompt ask in the graphical console in the virtual machine.All these are fixed by simply adding "console=tty1" to the command line, is that something a user is supposed to do manually (e.g. GRUB configs)? Should the initramfs (or maybe the kernel itself) be detecting when graphics are working and automatically switch outputs/prompts to that? I want to work on this, what would be the best way to proceed?-- Might be relevant: -- /proc/consoles: ttyS2 -W- (EC p a) 4:66 tty0 -WU (E p ) 4:7 -- Some dmesg lines that might be useful: [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 5.4.0-4-arm64 (...) [ 0.000000] Machine model: Google Kevin [ 0.001029] Console: colour dummy device 80x25 [ 0.001038] printk: console [tty0] enabled [ 0.044788] Serial: AMBA PL011 UART driver [ 1.853700] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled[ 1.855861] ff1a0000.serial: ttyS2 at MMIO 0xff1a0000 (irq = 39, base_baud = 1500000) is a 16550A[ 1.856046] printk: console [ttyS2] enabled [ 1.857318] Serial: AMBA driver [ 1.857898] msm_serial: driver initialized [ 2.103745] ttyS2 - failed to request DMA [ 2.159994] Run /init as init process[ 2.785121] rockchip-drm display-subsystem: bound ff8f0000.vop (ops rockchip_drm_fini [rockchipdrm]) [ 2.787381] rockchip-drm display-subsystem: bound ff900000.vop (ops rockchip_drm_fini [rockchipdrm]) [ 2.794270] rockchip-drm display-subsystem: bound ff970000.edp (ops rockchip_drm_fini [rockchipdrm]) [ 2.794439] rockchip-drm display-subsystem: bound fec00000.dp (ops rockchip_drm_fini [rockchipdrm])[ 2.794446] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 2.794449] [drm] No driver support for vblank timestamp query.[ 2.824898] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work [rockchipdrm]] Not connected. Disabling cdn[ 3.076232] Console: switching to colour frame buffer device 300x100[ 3.132091] rockchip-drm display-subsystem: fb0: rockchipdrmfb frame buffer device [ 3.144856] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0[ 4.972935] systemd[1]: systemd 244.3-1 running in system mode. (...) -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 12M Jan 19 11:20 /boot/initrd.img-5.4.0-2-arm64 -rw-r--r-- 1 root root 16M Feb 8 12:52 /boot/initrd.img-5.4.0-3-arm64 -rw-r--r-- 1 root root 16M Feb 19 14:25 /boot/initrd.img-5.4.0-4-arm64 -- /proc/cmdlinecros_secure kern_guid=7849fbba-1fb3-4f0b-9989-952567ef5a3c root=PARTUUID=3518689e-a82c-4448-9ec2-c79b13f88d8e rootwait quiet splash-- resume RESUME=UUID=490bfb86-ee41-4944-8bcf-4f4b2211026d -- /proc/filesystems ext3 ext2 ext4 fuseblk -- lsmod Module Size Used by vhost_net 32768 0 vhost 49152 1 vhost_net tap 32768 1 vhost_net uhid 24576 1 algif_hash 20480 1 algif_skcipher 16384 1 af_alg 28672 6 algif_hash,algif_skcipher rfcomm 81920 16 fuse 139264 5 xt_CHECKSUM 16384 1 xt_MASQUERADE 20480 3 xt_conntrack 16384 1 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT xt_tcpudp 20480 6 nft_compat 20480 13 nft_counter 16384 30 nft_chain_nat 16384 8 nf_nat 45056 2 nft_chain_nat,xt_MASQUERADE nf_conntrack 159744 3 xt_conntrack,nf_nat,xt_MASQUERADE nf_defrag_ipv6 24576 1 nf_conntrack nf_defrag_ipv4 16384 1 nf_conntrack libcrc32c 16384 2 nf_conntrack,nf_nat nf_tables 151552 102 nft_compat,nft_counter,nft_chain_nat nfnetlink 20480 2 nft_compat,nf_tables tun 61440 2 vhost_net bridge 212992 0 stp 16384 1 bridge llc 20480 2 bridge,stp bnep 32768 2 btusb 61440 0 btrtl 24576 1 btusb btbcm 20480 1 btusb btintel 28672 1 btusb bluetooth 606208 43 btrtl,btintel,btbcm,bnep,btusb,rfcomm drbg 32768 1 ansi_cprng 20480 0 ecdh_generic 16384 2 bluetooth ecc 32768 1 ecdh_generic sd_mod 57344 0 sg 53248 0 uas 32768 0 usb_storage 73728 1 uas scsi_mod 233472 4 sd_mod,usb_storage,uas,sg uvcvideo 114688 0 videobuf2_vmalloc 20480 1 uvcvideo videobuf2_memops 20480 1 videobuf2_vmalloc videobuf2_v4l2 28672 1 uvcvideo videobuf2_common 53248 2 videobuf2_v4l2,uvcvideo videodev 266240 3 videobuf2_v4l2,uvcvideo,videobuf2_commonmc 57344 4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_commonaes_ce_blk 32768 5 crypto_simd 20480 1 aes_ce_blk cryptd 20480 2 crypto_simd joydev 32768 0 hid_generic 16384 0 aes_ce_cipher 16384 1 aes_ce_blk xhci_plat_hcd 20480 0 xhci_hcd 253952 1 xhci_plat_hcd ghash_ce 20480 0 gf128mul 16384 1 ghash_ce dwc3 163840 0 mwifiex_pcie 45056 0 tpm_i2c_infineon 20480 0 udc_core 49152 1 dwc3 sha2_ce 16384 1 mwifiex 311296 1 mwifiex_pcie tpm 69632 1 tpm_i2c_infineon ulpi 20480 1 dwc3 i2c_hid 36864 0 rng_core 20480 2 tpm snd_soc_rt5514 53248 1 sha256_arm64 24576 1 sha2_ce atmel_mxt_ts 40960 0 hid 139264 3 i2c_hid,hid_generic,uhid cfg80211 696320 1 mwifiex snd_soc_rt5514_spi 16384 2 snd_soc_rt5514 sha1_ce 16384 0 sbs_battery 24576 0 snd_soc_rk3399_gru_sound 24576 1 snd_soc_rl6231 20480 1 snd_soc_rt5514 governor_simpleondemand 16384 0 snd_soc_da7219 69632 2 snd_soc_rk3399_gru_sound panfrost 65536 0 ntc_thermistor 20480 0 dwc3_of_simple 20480 0 snd_soc_rockchip_i2s 20480 4 snd_soc_hdmi_codec 20480 1 snd_soc_max98357a 20480 1 gpio_keys 24576 0 snd_soc_rockchip_pcm 16384 1 snd_soc_rockchip_i2s rfkill 36864 6 bluetooth,cfg80211 gpu_sched 36864 1 panfrost ohci_platform 16384 0snd_soc_core 204800 8 snd_soc_rk3399_gru_sound,snd_soc_rockchip_pcm,snd_soc_da7219,snd_soc_hdmi_codec,snd_soc_rockchip_i2s,snd_soc_rt5514,snd_soc_max98357a,snd_soc_rt5514_spiohci_hcd 57344 1 ohci_platform dw_wdt 20480 0 ehci_platform 16384 0 snd_pcm_dmaengine 20480 1 snd_soc_core ofpart 20480 0 sdhci_of_arasan 20480 1 watchdog 36864 1 dw_wdt nvmem_rockchip_efuse 16384 0 cros_ec_sensors 16384 0snd_pcm 122880 5 snd_soc_da7219,snd_soc_hdmi_codec,snd_soc_core,snd_soc_rt5514_spi,snd_pcm_dmaengineehci_hcd 94208 1 ehci_platform sdhci_pltfm 16384 1 sdhci_of_arasan rockchip_saradc 24576 0 cros_ec_sensors_core 16384 1 cros_ec_sensors spi_nor 61440 0 snd_timer 45056 1 snd_pcmusbcore 290816 10 ohci_platform,xhci_hcd,ohci_hcd,ehci_platform,usb_storage,uvcvideo,ehci_hcd,btusb,uas,xhci_plat_hcdcqhci 32768 1 sdhci_of_arasan industrialio_triggered_buffer 16384 1 cros_ec_sensors cros_usbpd_charger 20480 0 kfifo_buf 16384 1 industrialio_triggered_buffersnd 102400 7 snd_soc_rk3399_gru_sound,snd_soc_hdmi_codec,snd_timer,snd_soc_core,snd_pcmsdhci 65536 2 sdhci_pltfm,sdhci_of_arasan cros_usbpd_logger 20480 0 cros_ec_sysfs 16384 0 mtd 77824 3 spi_nor,ofpartindustrialio 77824 6 industrialio_triggered_buffer,cros_ec_sensors,ntc_thermistor,kfifo_buf,rockchip_saradc,cros_ec_sensors_corecros_ec_debugfs 16384 0 soundcore 20480 1 snd cros_ec_lightbar 16384 0 cros_ec_chardev 24576 0 i2c_rk3x 28672 0 coreboot_table 16384 0 rockchip_thermal 28672 0 cpufreq_dt 20480 0 i2c_cros_ec_tunnel 16384 0 binfmt_misc 24576 1 ip_tables 32768 0x_tables 45056 7 xt_conntrack,nft_compat,xt_tcpudp,xt_CHECKSUM,ipt_REJECT,ip_tables,xt_MASQUERADEautofs4 53248 2 ext4 700416 1 crc16 16384 2 bluetooth,ext4 mbcache 24576 1 ext4 jbd2 135168 1 ext4 crc32c_generic 16384 3 evdev 36864 14 rtc_cros_ec 16384 1 extcon_usbc_cros_ec 20480 0 cros_ec_keyb 20480 0 pwm_cros_ec 20480 1 matrix_keymap 16384 1 cros_ec_keyb cros_ec_dev 20480 0 cros_ec_spi 24576 0 cros_ec 20480 1 cros_ec_spi rockchipdrm 114688 2 analogix_dp 53248 1 rockchipdrm dw_hdmi 40960 1 rockchipdrm cec 53248 1 dw_hdmi dw_mipi_dsi 20480 1 rockchipdrm panel_simple 65536 0 drm_kms_helper 176128 4 dw_mipi_dsi,rockchipdrm,dw_hdmi,analogix_dp gpio_regulator 16384 2 pwm_regulator 16384 4 vctrl_regulator 16384 3 fixed 20480 34drm 503808 10 gpu_sched,drm_kms_helper,dw_mipi_dsi,panel_simple,rockchipdrm,dw_hdmi,panfrost,analogix_dpphy_rockchip_pcie 20480 4 phy_rockchip_inno_usb2 40960 12usb_common 16384 10 xhci_hcd,ohci_hcd,ehci_platform,phy_rockchip_inno_usb2,usbcore,uvcvideo,ehci_hcd,xhci_plat_hcd,dwc3,udc_corerockchip_io_domain 24576 0 phy_rockchip_emmc 20480 1 phy_rockchip_typec 20480 6 dw_mmc_rockchip 20480 0 pwm_rockchip 16384 4 dw_mmc_pltfm 16384 1 dw_mmc_rockchip spi_rockchip 24576 0 pl330 45056 10 dw_mmc 49152 2 dw_mmc_pltfm,dw_mmc_rockchip pwm_bl 20480 0 -- /etc/initramfs-tools/modules -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = yes -- /etc/initramfs-tools/initramfs.conf MODULES=dep BUSYBOX=auto KEYMAP=n COMPRESS=gzip DEVICE= NFSROOT=auto RUNSIZE=10% -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /sys/block mmcblk0 mmcblk1 mmcblk1boot0 mmcblk1boot1 sda -- mkinitramfs hooks /etc/initramfs-tools/hooks/: firmware remove-panfrost /usr/share/initramfs-tools/hooks: dmsetup fsck fuse keymap klibc-utils kmod lvm2 ntfs_3g plymouth resume thermal thin-provisioning-tools udev zz-busybox -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: arm64 (aarch64) Kernel: Linux 5.4.0-4-arm64 (SMP w/6 CPU cores)Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages initramfs-tools depends on: ii initramfs-tools-core 0.136 ii linux-base 4.6 initramfs-tools recommends no packages. Versions of packages initramfs-tools suggests: ii bash-completion 1:2.10-1 -- no debconf information
--- End Message ---
--- Begin Message ---
- To: 952452-done@bugs.debian.org
- Subject: Re: Bug#952452: initramfs-tools: prefers serial console over framebuffer console
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Wed, 26 Feb 2020 23:10:45 +0000
- Message-id: <d34275ad9d4e0ff0ae8860f56323b0740cb07d34.camel@decadent.org.uk>
- In-reply-to: <[🔎] 8ebe8b56-4477-441a-301a-1b20d367dfcb@gmail.com>
- References: <[🔎] d3059269-a87e-23a2-a775-54e04993b517@gmail.com> <[🔎] d3059269-a87e-23a2-a775-54e04993b517@gmail.com> <[🔎] 8ebe8b56-4477-441a-301a-1b20d367dfcb@gmail.com>
On Wed, 2020-02-26 at 17:10 +0300, Alper Nebi Yasak wrote: > On 24/02/2020 19:50, Alper Nebi Yasak wrote: > > I'm using Debian on an arm64 chromebook, and not setting "console=tty1" > > in the kernel command line results in a number of weird behaviours > > related to the initramfs. > > Turns out my device-tree has (for debugging purposes?): > > chosen { > stdout-path = "serial2:115200n8"; > }; > > Removing that makes everything work on the screen again, but that's a > worse way to solve it compared to adding a kernel cmdline arg. > > QEMU on aarch64 does a similar thing according to [0]: > > $ sudo dmesg | grep -i console > [ 0.000000] ACPI: SPCR: console: pl011,mmio,0x9000000,9600 > ... > > [0] https://bugzilla.redhat.com/show_bug.cgi?id=1661288#c35 > > Those seem to be the root cause. A device that is intended to be used with keyboard and video display should not have this in the device tree for production units. If we ship the device tree then we can correct that. If not, then the boot loader should be configured to override it, and the installer could do that by default. I don't think it makes sense for initramfs-tools to do this, as the wrong default console will still affect other software. Ben. -- Ben Hutchings Tomorrow will be cancelled due to lack of interest.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---