[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#887139: installation-reports: Debian Installer Bullseye RC 1 damages UEFI setup on Dell Latitude 5510

Package: installation-reports
Followup-For: Bug #887139

Dear Maintainer,

Paul Gevers has asked subscribers to debian-devel-announce to try out
the debian-installer, so I tried it.

-- Package-specific info:

Boot method: netinst.iso on a USB flash drive
Image version: https://cdimage.debian.org/cdimage/bullseye_di_rc1/amd64/iso-cd/debian-bullseye-DI-rc1-amd64-netinst.iso as downloaded 2021-05-06 14:00 UTC
Date: 2021-05-06 14:30 UTC

Machine: Dell Latitude 5510 laptop, Intel Comet Lake i7-10610U CPU with associated Intel chipset, Intel Wifi, Intel integrated graphics

Partitions: the command "df -Tl" reports the following while *buster* is
running.  Is this information useful, though?  I include it only because
installation-report specifically requests it.
Filesystem      Type      1K-blocks      Used Available Use% Mounted on
udev            devtmpfs   16223268         0  16223268   0% /dev
tmpfs           tmpfs       3247352      9972   3237380   1% /run
/dev/nvme0n1p9  ext4      263174212  17009396 232726660   7% /
tmpfs           tmpfs      16236752     69528  16167224   1% /dev/shm
tmpfs           tmpfs          5120         4      5116   1% /run/lock
tmpfs           tmpfs      16236752         0  16236752   0% /sys/fs/cgroup
/dev/nvme0n1p11 ext4     1254007444 451985672 738251968  38% /arc
/dev/nvme0n1p1  vfat         507904    110000    397904  22% /boot/efi
tmpfs           tmpfs       3247348     12756   3234592   1% /run/user/1000
/dev/sda1       iso9660      369664    369664         0 100% /media/thb/Debian bullseye-DI-rc1 amd64 n

Partitions: the command "fdisk -l" reports the following. This may be
more informative than the above.  Buster is installed on p9; bullseye,
on p12.
Disk /dev/nvme0n1: 1.9 TiB, 2048408248320 bytes, 4000797360 sectors
Disk model: INTEL SSDPEKNW020T9
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: E40D7C7A-2099-49F3-808B-FB583DFE4C6C
Device               Start        End    Sectors   Size Type
/dev/nvme0n1p1        2048    1026047    1024000   500M EFI System
/dev/nvme0n1p2     1026048    1288191     262144   128M Microsoft reserved
/dev/nvme0n1p3     1288192  774707199  773419008 368.8G Microsoft basic data
/dev/nvme0n1p4  3995934720 3997962239    2027520   990M Windows recovery environment
/dev/nvme0n1p5  3997962240 4000759807    2797568   1.3G Windows recovery environment
/dev/nvme0n1p6   774709245  774709245          1   512B Microsoft basic data
/dev/nvme0n1p7   774709246  774709246          1   512B Microsoft basic data
/dev/nvme0n1p8   774709247  774709247          1   512B Microsoft basic data
/dev/nvme0n1p9   774709248 1311580159  536870912   256G Linux filesystem
/dev/nvme0n1p10 1311580160 1378689023   67108864    32G Linux swap
/dev/nvme0n1p11 1378689024 3928825855 2550136832   1.2T Linux filesystem
/dev/nvme0n1p12 3928825856 3995934719   67108864    32G Linux filesystem

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [O]
Detect network card:    [ ]
Configure network:      [ ]
Detect CD:              [O]
Load installer modules: [O]
Clock/timezone setup:   [ ]
User/password setup:    [O]
Detect hard drives:     [O]
Partition hard drives:  [O]
Install base system:    [O]
Install tasks:          [O]
Install boot loader:    [E]
Overall install:        [O]


The installation went as expected.  Unfortunately, after installation,

    * bullseye testing (newly installed) booted normally but
    * buster stable (already installed) booted abnormally.

Installation of bullseye on one partition disrupts buster on another
partition.  Insofar as bullseye's installer was not asked by me to touch
buster's partition, I assume that the problem is a UEFI problem.
It may be that bullseye's installer damages UEFI.

Buster still boots, but takes two or three minutes instead of the
usual 20 seconds or so.  Buster's boot stalled so long, I had time to
write down the messages that appeared live on the screen during the
stall (though I cannot promise that I have precisely copied all the
hexidecimal numbers and such):
fsckd-cancel-msg:Press Ctrl-C to cancel all filesystem checks in progress
[35.999999] ioremap-errorr for 0x76980000-0x76981000, requested 0x2, got 0x0
[some messages about iwlwifi]
[some messages about Plymouth]
[37.999999] tpm tpm0: tpm_try_transmit send(): error -62
[37.999999] tpm tpm0: [Firmware bug]: TPM interrupt not working, polling instead
[   ***   ] A start job is running for /dev/disk/by-uuid/ef70f152-a70a-4d70-8402-a3e2a0c6db90 (59s / 1min 30s)

To emphasize, the above messages appear during a stall when *buster*
boots after *bullseye* is installed.  There is no stall when bullseye


The following were generated while buster was running, not bullseye.

Installer lsb-release:
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20210415"

Installer hardware-summary:
uname -a: Linux debian 5.10.0-6-amd64 #1 SMP Debian 5.10.28-1 (2021-04-09) x86_64 GNU/Linux
(The complete report is too long to include inline here.  Please find
it attached.)

Attachment: installer-hardware-summary.txt.gz
Description: application/gzip

Reply to: