Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #68582 > unrolled thread

Bug#974939: machine does not boot

Started byToni <toni@debian.org>
First post2020-11-16 21:00 +0100
Last post2020-11-23 15:40 +0100
Articles 9 — 5 participants

Back to article view | Back to linux.debian.kernel

Contents

  Bug#974939: machine does not boot Toni <toni@debian.org> - 2020-11-16 21:00 +0100
    Bug#974939: machine does not boot Ben Hutchings <ben@decadent.org.uk> - 2020-11-17 13:00 +0100
    Bug#974939: machine does not boot Bastian Blank <bblank@thinkmo.de> - 2020-11-17 13:10 +0100
      Bug#974939: machine does not boot Toni Mueller <toni@debian.org> - 2020-11-22 18:20 +0100
    Processed: Re: Bug#974939: machine does not boot "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-11-17 13:10 +0100
    Bug#974939: machine does not boot Ben Hutchings <ben@decadent.org.uk> - 2020-11-23 11:20 +0100
      Bug#974939: machine does not boot Toni Mueller <toni@debian.org> - 2020-11-23 11:30 +0100
    Bug#974939: marked as done (machine does not boot) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-11-23 11:50 +0100
    Bug#974939: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Bug#974939: machine does not boot) Toni Mueller <toni@debian.org> - 2020-11-23 15:40 +0100

#68582 — Bug#974939: machine does not boot

FromToni <toni@debian.org>
Date2020-11-16 21:00 +0100
SubjectBug#974939: machine does not boot
Message-ID<BbSPn-7kK-1@gated-at.bofh.it>
Package: src:linux
Version: 4.19.152-1
Severity: critical


Hi,

with the two latest kernels, linux-image-4.19.0-12-amd64 and
linux-image-4.19.0-11-amd64, my machine does not boot, the reason being
that something with cryptsetup is amiss. I used to be asked for a
passphrase, but using these two kernels, I'm not, and the machine just
cycles trying to find the root partition. I am now running the -10
kernel again, which I would like to get off of. I've tried recovery mode
without any success.

On the console, after dmesg, these three lines repeat ad nauseum:

mdadm: No arrays found in config file or automatically
  Volume group "ev0" not found
  Cannot process volume group ev0
mdadm: No arrays found in config file or automatically
  Volume group "ev0" not found
  Cannot process volume group ev0


I think this bug is critical, since I can't get to anything with this
state of the machine.


The disk configuration is pretty straightforward:

git:(master*)$ lsblk 
NAME                MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
nvme0n1             259:0    0 953.9G  0 disk  
├─nvme0n1p1         259:1    0 238.4M  0 part  
├─nvme0n1p2         259:2    0   3.5G  0 part  
├─nvme0n1p3         259:3    0   953M  0 part  /boot
└─nvme0n1p4         259:4    0 949.2G  0 part  
  └─nvme0n1p4_crypt 253:0    0 949.2G  0 crypt 
    ├─ev0-swap      253:1    0  29.8G  0 lvm   [SWAP]
    ├─ev0-root      253:2    0 789.4G  0 lvm   /


There is one other (data) partition, but that's it for what the system
has.


Cheers,
Toni




-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Dell Inc.
product_name: Precision 5530
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: 1.13.0
board_vendor: Dell Inc.
board_name: 0X78C1
board_version: A02

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers [8086:3ec4] (rev 07)
	Subsystem: Dell 8th Gen Core Processor Host Bridge/DRAM Registers [1028:087d]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: <access denied>
	Kernel driver in use: skl_uncore

00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 122
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 00003000-00003fff
	Memory behind bridge: ec000000-ed0fffff
	Prefetchable memory behind bridge: 00000000c0000000-00000000d1ffffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller])
	Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 154
	Region 0: Memory at eb000000 (64-bit, non-prefetchable) [size=16M]
	Region 2: Memory at 80000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at 4000 [size=64]
	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: i915
	Kernel modules: i915

00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 07)
	Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [1028:087d]
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at ed510000 (64-bit, non-prefetchable) [size=32K]
	Capabilities: <access denied>
	Kernel driver in use: proc_thermal
	Kernel modules: processor_thermal_device

00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture Model [8086:1911]
	Subsystem: Dell Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [1028:087d]
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 255
	Region 0: Memory at ed528000 (64-bit, non-prefetchable) [disabled] [size=4K]
	Capabilities: <access denied>

00:12.0 Signal processing controller [1180]: Intel Corporation Cannon Lake PCH Thermal Controller [8086:a379] (rev 10)
	Subsystem: Dell Cannon Lake PCH Thermal Controller [1028:087d]
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at ed527000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: intel_pch_thermal
	Kernel modules: intel_pch_thermal

00:14.0 USB controller [0c03]: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller [8086:a36d] (rev 10) (prog-if 30 [XHCI])
	Subsystem: Dell Cannon Lake PCH USB 3.1 xHCI Host Controller [1028:087d]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 130
	Region 0: Memory at ed500000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

00:14.2 RAM memory [0500]: Intel Corporation Cannon Lake PCH Shared SRAM [8086:a36f] (rev 10)
	Subsystem: Dell Cannon Lake PCH Shared SRAM [1028:087d]
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at ed51e000 (64-bit, non-prefetchable) [disabled] [size=8K]
	Region 2: Memory at ed526000 (64-bit, non-prefetchable) [disabled] [size=4K]
	Capabilities: <access denied>

00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller [8086:a368] (rev 10)
	Subsystem: Dell Cannon Lake PCH Serial IO I2C Controller [1028:087d]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at 7f800000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller [8086:a369] (rev 10)
	Subsystem: Dell Cannon Lake PCH Serial IO I2C Controller [1028:087d]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 17
	Region 0: Memory at 7f801000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:16.0 Communication controller [0780]: Intel Corporation Cannon Lake PCH HECI Controller [8086:a360] (rev 10)
	Subsystem: Dell Cannon Lake PCH HECI Controller [1028:087d]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 139
	Region 0: Memory at ed523000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: mei_me
	Kernel modules: mei_me

00:17.0 SATA controller [0106]: Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller [8086:a353] (rev 10) (prog-if 01 [AHCI 1.0])
	Subsystem: Dell Cannon Lake Mobile PCH SATA AHCI Controller [1028:087d]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 129
	Region 0: Memory at ed51c000 (32-bit, non-prefetchable) [size=8K]
	Region 1: Memory at ed522000 (32-bit, non-prefetchable) [size=256]
	Region 2: I/O ports at 4090 [size=8]
	Region 3: I/O ports at 4080 [size=4]
	Region 4: I/O ports at 4060 [size=32]
	Region 5: Memory at ed521000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: <access denied>
	Kernel driver in use: ahci
	Kernel modules: ahci

00:1b.0 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port [8086:a340] (rev f0) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 123
	Bus: primary=00, secondary=02, subordinate=3a, sec-latency=0
	I/O behind bridge: 00005000-00005fff
	Memory behind bridge: d4000000-ea0fffff
	Prefetchable memory behind bridge: 0000000090000000-00000000b1ffffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:1c.0 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port [8086:a338] (rev f0) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 124
	Bus: primary=00, secondary=3b, subordinate=3b, sec-latency=0
	Memory behind bridge: ed400000-ed4fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:1c.4 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port [8086:a33c] (rev f0) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 125
	Bus: primary=00, secondary=3c, subordinate=3c, sec-latency=0
	Memory behind bridge: ed300000-ed3fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:1d.0 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port [8086:a330] (rev f0) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 126
	Bus: primary=00, secondary=3d, subordinate=3d, sec-latency=0
	Memory behind bridge: ed200000-ed2fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:a30e] (rev 10)
	Subsystem: Dell Device [1028:087d]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0

00:1f.3 Audio device [0403]: Intel Corporation Cannon Lake PCH cAVS [8086:a348] (rev 10) (prog-if 80)
	Subsystem: Dell Cannon Lake PCH cAVS [1028:087d]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 155
	Region 0: Memory at ed518000 (64-bit, non-prefetchable) [size=16K]
	Region 4: Memory at ed100000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

00:1f.4 SMBus [0c05]: Intel Corporation Cannon Lake PCH SMBus Controller [8086:a323] (rev 10)
	Subsystem: Dell Cannon Lake PCH SMBus Controller [1028:087d]
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at ed520000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at efa0 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801

00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller [8086:a324] (rev 10)
	Subsystem: Dell Cannon Lake PCH SPI Controller [1028:087d]
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at fe010000 (32-bit, non-prefetchable) [size=4K]

01:00.0 3D controller [0302]: NVIDIA Corporation GP107GLM [Quadro P2000 Mobile] [10de:1cba] (rev ff) (prog-if ff)
	!!! Unknown header type 7f
	Kernel modules: nvidia

3b:00.0 Network controller [0280]: Intel Corporation Wireless-AC 9260 [8086:2526] (rev 29)
	Subsystem: Intel Corporation Wireless-AC 9260 [8086:4010]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at ed400000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01)
	Subsystem: Dell RTS525A PCI Express Card Reader [1028:087d]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 127
	Region 1: Memory at ed300000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: rtsx_pci
	Kernel modules: rtsx_pci

3d:00.0 Non-Volatile memory controller [0108]: Toshiba America Info Systems Device [1179:0116] (prog-if 02 [NVM Express])
	Subsystem: Toshiba America Info Systems Device [1179:0001]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	NUMA node: 0
	Region 0: Memory at ed200000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: nvme
	Kernel modules: nvme


** USB devices:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c08b Logitech, Inc. 
Bus 001 Device 003: ID 0c45:671d Microdia 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


-- System Information:
Debian Release: 10.6
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'proposed-updates'), (90, 'testing'), (70, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-10-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-4.19.0-12-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.133+deb10u1
ii  kmod                                    26-1
ii  linux-base                              4.6

Versions of packages linux-image-4.19.0-12-amd64 recommends:
ii  apparmor             2.13.2-10
ii  firmware-linux-free  3.4

Versions of packages linux-image-4.19.0-12-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  extlinux                3:6.04~git20190206.bf6db5b4+dfsg1-1
ii  grub-efi-amd64          2.02+dfsg1-20+deb10u2
pn  linux-doc-4.19          <none>

Versions of packages linux-image-4.19.0-12-amd64 is related to:
ii  firmware-amd-graphics     20190114-2
pn  firmware-atheros          <none>
pn  firmware-bnx2             <none>
pn  firmware-bnx2x            <none>
pn  firmware-brcm80211        <none>
pn  firmware-cavium           <none>
pn  firmware-intel-sound      <none>
pn  firmware-intelwimax       <none>
pn  firmware-ipw2x00          <none>
pn  firmware-ivtv             <none>
ii  firmware-iwlwifi          20190114-2
pn  firmware-libertas         <none>
ii  firmware-linux-nonfree    20190114-2
ii  firmware-misc-nonfree     20190114-2
pn  firmware-myricom          <none>
pn  firmware-netxen           <none>
pn  firmware-qlogic           <none>
pn  firmware-realtek          <none>
pn  firmware-samsung          <none>
pn  firmware-siano            <none>
pn  firmware-ti-connectivity  <none>
pn  xen-hypervisor            <none>

-- no debconf information

[toc] | [next] | [standalone]

#68585

FromBen Hutchings <ben@decadent.org.uk>
Date2020-11-17 13:00 +0100
Message-ID<Bc7Op-84U-3@gated-at.bofh.it>
In reply to#68582

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 moreinfo
Control: severity -1 important

On Mon, 2020-11-16 at 19:41 +0000, Toni wrote:
> Package: src:linux
> Version: 4.19.152-1
> Severity: critical
> 
> 
> Hi,
> 
> with the two latest kernels, linux-image-4.19.0-12-amd64 and
> linux-image-4.19.0-11-amd64, my machine does not boot, the reason being
> that something with cryptsetup is amiss. I used to be asked for a
> passphrase, but using these two kernels, I'm not, and the machine just
> cycles trying to find the root partition. I am now running the -10
> kernel again, which I would like to get off of. I've tried recovery mode
> without any success.

This is probably an issue with the initramfs built for this kernel, and
not with the kernel itself.  Please send the output of the command:

    lsinitramfs /boot/initrd.img-4.19.0-12-amd64

> On the console, after dmesg, these three lines repeat ad nauseum:
> 
> mdadm: No arrays found in config file or automatically
>   Volume group "ev0" not found
>   Cannot process volume group ev0
> mdadm: No arrays found in config file or automatically
>   Volume group "ev0" not found
>   Cannot process volume group ev0
[...]

If you wait for about 30 seconds you should get a shell with the prompt
"(initramfs)".  At the shell prompt, run:

    ls -l /dev/nvme*

Are the expected partitions listed?

Ben.

-- 
Ben Hutchings
Usenet is essentially a HUGE group of people passing notes in class.
                 - Rachel Kadel, `A Quick Guide to Newsgroup Etiquette'

[toc] | [prev] | [next] | [standalone]

#68586

FromBastian Blank <bblank@thinkmo.de>
Date2020-11-17 13:10 +0100
Message-ID<Bc7Y5-8nz-1@gated-at.bofh.it>
In reply to#68582
Control: severity -1 important

On Mon, Nov 16, 2020 at 07:41:05PM +0000, Toni wrote:
> Severity: critical

Sorry, no.  This problem does not break the package for everyone.

> On the console, after dmesg, these three lines repeat ad nauseum:
> mdadm: No arrays found in config file or automatically
>   Volume group "ev0" not found
>   Cannot process volume group ev0
> mdadm: No arrays found in config file or automatically
>   Volume group "ev0" not found
>   Cannot process volume group ev0

So it actually boots, but the boot process is not able to find your root
filesystem?

> The disk configuration is pretty straightforward:
> 
> git:(master*)$ lsblk 
> NAME                MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
> nvme0n1             259:0    0 953.9G  0 disk  
> ├─nvme0n1p1         259:1    0 238.4M  0 part  
> ├─nvme0n1p2         259:2    0   3.5G  0 part  
> ├─nvme0n1p3         259:3    0   953M  0 part  /boot
> └─nvme0n1p4         259:4    0 949.2G  0 part  
>   └─nvme0n1p4_crypt 253:0    0 949.2G  0 crypt 
>     ├─ev0-swap      253:1    0  29.8G  0 lvm   [SWAP]
>     ├─ev0-root      253:2    0 789.4G  0 lvm   /

Yes, that look pretty normal and like something the Debian installer
would create.

What is the content of /etc/crypttab? /etc/fstab? /boot/grub/grub.conf?
What do you have mdadm for?

Regards,
Bastian

-- 
You can't evaluate a man by logic alone.
		-- McCoy, "I, Mudd", stardate 4513.3

[toc] | [prev] | [next] | [standalone]

#68637

FromToni Mueller <toni@debian.org>
Date2020-11-22 18:20 +0100
Message-ID<Be1bP-3tF-1@gated-at.bofh.it>
In reply to#68586

Hi,

On Tue, Nov 17, 2020 at 12:50:19PM +0100, Bastian Blank wrote:
> On Mon, Nov 16, 2020 at 07:41:05PM +0000, Toni wrote:
> > Severity: critical
> 
> Sorry, no.  This problem does not break the package for everyone.
> 
> > On the console, after dmesg, these three lines repeat ad nauseum:
> > mdadm: No arrays found in config file or automatically
> >   Volume group "ev0" not found
> >   Cannot process volume group ev0
> > mdadm: No arrays found in config file or automatically
> >   Volume group "ev0" not found
> >   Cannot process volume group ev0
> 
> So it actually boots, but the boot process is not able to find your root
> filesystem?

It loads the kernel, I can see the dmesg, and then I see an endless loop
of these messages. So yes, there's something broken with encrypted
partitions, that wasn't broken until the -10 kernel.

> Yes, that look pretty normal and like something the Debian installer
> would create.

It did.

> What is the content of /etc/crypttab? /etc/fstab? /boot/grub/grub.conf?
> What do you have mdadm for?

I don't have mdadm devices in this machine (it's a laptop with only one
SSD, anyway). I don't know why mdadm is present on this machine, but it
has "always" been, with no detrimental effects until possibly recently.



Thanks,
Toni

[toc] | [prev] | [next] | [standalone]

#68587 — Processed: Re: Bug#974939: machine does not boot

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2020-11-17 13:10 +0100
SubjectProcessed: Re: Bug#974939: machine does not boot
Message-ID<Bc7Y6-8nz-7@gated-at.bofh.it>
In reply to#68582
Processing control commands:

> severity -1 important
Bug #974939 [src:linux] machine does not boot
Bug #971535 [src:linux] this package makes my laptop almost unbootable
Ignoring request to change severity of Bug 974939 to the same value.
Ignoring request to change severity of Bug 971535 to the same value.

-- 
971535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971535
974939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974939
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#68652

FromBen Hutchings <ben@decadent.org.uk>
Date2020-11-23 11:20 +0100
Message-ID<Beh6V-4KO-7@gated-at.bofh.it>
In reply to#68582

[Multipart message — attachments visible in raw view] — view raw

On Mon, 2020-11-23 at 10:04 +0000, Toni Mueller wrote:
> 
> Hi Ben!
> 
> On Tue, Nov 17, 2020 at 11:26:53AM +0000, Ben Hutchings wrote:
> > On Mon, 2020-11-16 at 19:41 +0000, Toni wrote:
> > > Package: src:linux
> > > Version: 4.19.152-1
> > > Severity: critical
> > > passphrase, but using these two kernels, I'm not, and the machine just
> > > cycles trying to find the root partition. I am now running the -10
> > > kernel again, which I would like to get off of. I've tried recovery mode
> > > without any success.
> > 
> > This is probably an issue with the initramfs built for this kernel, and
> > not with the kernel itself.  Please send the output of the command:
> > 
> >     lsinitramfs /boot/initrd.img-4.19.0-12-amd64
> 
> I agree, but I can only file a bug report against the kernel package.
> Please find the output of this command attached.
[...]

cryptsetup support is not included in the newer initramfs images.  Did
you remove cryptsetup-initramfs by accident?

Ben.

-- 
Ben Hutchings
For every complex problem
there is a solution that is simple, neat, and wrong.

[toc] | [prev] | [next] | [standalone]

#68653

FromToni Mueller <toni@debian.org>
Date2020-11-23 11:30 +0100
Message-ID<BehgC-4O0-9@gated-at.bofh.it>
In reply to#68652
Hi Ben,

On Mon, Nov 23, 2020 at 10:12:01AM +0000, Ben Hutchings wrote:
> On Mon, 2020-11-23 at 10:04 +0000, Toni Mueller wrote:
> > I agree, but I can only file a bug report against the kernel package.
> > Please find the output of this command attached.
> cryptsetup support is not included in the newer initramfs images.

I saw that, but was not aware of this package:

> Did you remove cryptsetup-initramfs by accident?

Not that I am aware of, and definitely not intentionally. Until now, I
had no idea that it even existed. But I can now see that it was removed
in a dist-upgrade run on the 9th of May last year (huh?!?). But there
seems to be a problem to re-install it:


# apt install cryptsetup-initramfs -y 

...

The following packages will be REMOVED:
  libgcc-s1
The following NEW packages will be installed:
  cryptsetup-initramfs
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
  libgcc-s1
0 upgraded, 1 newly installed, 1 to remove and 2 not upgraded.
E: Essential packages were removed and -y was used without --allow-remove-essential.



Since libgcc-s1 is being provided by libgcc1, I am inclined to run with
--allow-remove-essential. But this is still quite scary!

(I wasn't aware of libgcc-s1, either. :(   )



Thanks,
Toni

[toc] | [prev] | [next] | [standalone]

#68654 — Bug#974939: marked as done (machine does not boot)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2020-11-23 11:50 +0100
SubjectBug#974939: marked as done (machine does not boot)
Message-ID<BehzX-4UM-3@gated-at.bofh.it>
In reply to#68582

[Multipart message — attachments visible in raw view] — view raw

Your message dated Mon, 23 Nov 2020 10:41:25 +0000
with message-id <0b90a840471d86834671e45cc6294e4d5f1bf953.camel@decadent.org.uk>
and subject line Re: Bug#974939: machine does not boot
has caused the Debian Bug report #974939,
regarding machine does not boot
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.)


-- 
974939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974939
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#68657 — Bug#974939: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Bug#974939: machine does not boot)

FromToni Mueller <toni@debian.org>
Date2020-11-23 15:40 +0100
SubjectBug#974939: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Bug#974939: machine does not boot)
Message-ID<Belax-776-1@gated-at.bofh.it>
In reply to#68582
Hi Ben,

On Mon, Nov 23, 2020 at 10:45:09AM +0000, Debian Bug Tracking System wrote:
> I recommend that you always check the list of packages to be removed in
> a dist-upgrade, if you have some packages installed from
> testing/unstable.

yes. :/

> It doesn't exist in stable.  Perhaps you installed something from
> testing/unstable that required it?  libgcc-s1 breaks the stable version
> of cryptsetup-initramfs.

I checked. My apt and libc6 are both from stable, and should thus only
have stable dependencies, right?

However, removing libgcc-s1 broke apt ("could not load shared
library...").


Thanks for the heads-ups,
Toni

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web