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

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

Bug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot

Started byJulian Calaby <julian.calaby@gmail.com>
First post2018-07-24 13:40 +0200
Last post2018-08-09 17:50 +0200
Articles 12 — 9 participants

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

Contents

  Bug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot Julian Calaby <julian.calaby@gmail.com> - 2018-07-24 13:40 +0200
    Bug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot Ben Hutchings <ben@decadent.org.uk> - 2018-07-24 18:30 +0200
      Bug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot Julian Calaby <julian.calaby@gmail.com> - 2018-07-27 13:40 +0200
        Bug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot Tomas Janousek <tomi@nomi.cz> - 2018-07-29 12:10 +0200
          Bug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot Tomas Janousek <tomi@nomi.cz> - 2018-07-30 17:10 +0200
          Bug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot Julian Calaby <julian.calaby@gmail.com> - 2018-07-31 12:40 +0200
    Processed: Re: Bug#904441: linux-image-4.17.0-1-amd64: system  disk stopped during boot "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-07-24 18:30 +0200
    Bug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot "Felix C. Stegerman" <flx@obfusk.net> - 2018-07-29 01:40 +0200
    Bug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot YOSHINO Yoshihito <yy.y.ja.jp@gmail.com> - 2018-07-30 18:50 +0200
      Bug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot Olivier Berger <olivier.berger@telecom-sudparis.eu> - 2018-08-01 15:30 +0200
    Bug#904441: Same problem with Asus Zenbook Antoine Amarilli <a3nm@a3nm.net> - 2018-08-07 12:40 +0200
    Bug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot Felipe Sologuren <sologuren@estudiohum.cl> - 2018-08-09 17:50 +0200

#61543 — Bug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot

FromJulian Calaby <julian.calaby@gmail.com>
Date2018-07-24 13:40 +0200
SubjectBug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot
Message-ID<wf3PA-5uT-7@gated-at.bofh.it>
Package: src:linux
Version: 4.17.8-1
Severity: important

Dear Maintainer,

Linux 4.17.0-1-amd64 (4.17.8-1) causes my laptop (Thinkpad X200) to fail to
boot.

During a boot with Systemd the disk gets stopped erroneously approximately
after udev "coldplugs" anything that hasn't been autodetected already.

This causes the kernel to stop the system disk causing the machine to hang
with all SATA requests eventually timing out and all startup processes
eventually failing.

FROM MEMORY, the last disk related messages are:

sda: Synchronising SCSI cache
sda: Stopping disk

Please note that as I cannot boot that kernel, this bug report was compiled on
4.16.0-2-amd64 (4.16.16-2) instead.

Severity is relatively low as this laptop is the only computer I maintain that
has shown this behaviour (so far) which makes me think it's related to the
specific drivers I'm using, not something "generic" to this kernel version.

Please let me know if there's any further details you need about my hardware
or system configuration.

Thanks,

Julian Calaby


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

** Model information
sys_vendor: LENOVO
product_name: 7454CTO
product_version: ThinkPad X200
chassis_vendor: LENOVO
chassis_version: Not Available
bios_vendor: LENOVO
bios_version: 7XET72WW (3.22 )
board_vendor: LENOVO
board_name: 7454CTO
board_version: Not Available

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07)
	Subsystem: Lenovo Mobile 4 Series Chipset Memory Controller Hub [17aa:20e0]
	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>

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])
	Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4]
	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 16
	Region 0: Memory at f2000000 (64-bit, non-prefetchable) [size=4M]
	Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at 1800 [size=8]
	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: i915
	Kernel modules: i915

00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07)
	Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4]
	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
	Region 0: Memory at f2400000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: <access denied>

00:03.0 Communication controller [0780]: Intel Corporation Mobile 4 Series Chipset MEI Controller [8086:2a44] (rev 07)
	Subsystem: Lenovo Mobile 4 Series Chipset MEI Controller [17aa:20e6]
	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 29
	Region 0: Memory at f2825800 (64-bit, non-prefetchable) [size=16]
	Capabilities: <access denied>
	Kernel driver in use: mei_me
	Kernel modules: mei_me

00:19.0 Ethernet controller [0200]: Intel Corporation 82567LF Gigabit Network Connection [8086:10bf] (rev 03)
	Subsystem: Lenovo 82567LF Gigabit Network Connection [17aa:20ee]
	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 27
	Region 0: Memory at f2600000 (32-bit, non-prefetchable) [disabled] [size=128K]
	Region 1: Memory at f2624000 (32-bit, non-prefetchable) [disabled] [size=4K]
	Region 2: I/O ports at 1820 [disabled] [size=32]
	Capabilities: <access denied>
	Kernel driver in use: e1000e
	Kernel modules: e1000e

00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 03) (prog-if 00 [UHCI])
	Subsystem: Lenovo 82801I (ICH9 Family) USB UHCI Controller [17aa:20f0]
	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 20
	Region 4: I/O ports at 1840 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd

00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 03) (prog-if 00 [UHCI])
	Subsystem: Lenovo 82801I (ICH9 Family) USB UHCI Controller [17aa:20f0]
	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 B routed to IRQ 21
	Region 4: I/O ports at 1860 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd

00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 03) (prog-if 00 [UHCI])
	Subsystem: Lenovo 82801I (ICH9 Family) USB UHCI Controller [17aa:20f0]
	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 C routed to IRQ 22
	Region 4: I/O ports at 1880 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd

00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 03) (prog-if 20 [EHCI])
	Subsystem: Lenovo 82801I (ICH9 Family) USB2 EHCI Controller [17aa:20f1]
	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 D routed to IRQ 23
	Region 0: Memory at f2825c00 (32-bit, non-prefetchable) [size=1K]
	Capabilities: <access denied>
	Kernel driver in use: ehci-pci
	Kernel modules: ehci_pci

00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 03)
	Subsystem: Lenovo 82801I (ICH9 Family) HD Audio Controller [17aa:20f2]
	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 30
	Region 0: Memory at f2620000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 03) (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 24
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 00003000-00003fff
	Memory behind bridge: c0000000-c01fffff
	Prefetchable memory behind bridge: 00000000c0200000-00000000c03fffff
	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
	Kernel modules: shpchp

00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 03) (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 B routed to IRQ 25
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: 00004000-00004fff
	Memory behind bridge: f2500000-f25fffff
	Prefetchable memory behind bridge: 00000000c0400000-00000000c05fffff
	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
	Kernel modules: shpchp

00:1c.3 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 [8086:2946] (rev 03) (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 D routed to IRQ 26
	Bus: primary=00, secondary=05, subordinate=0c, sec-latency=0
	I/O behind bridge: 00002000-00002fff
	Memory behind bridge: f0000000-f1ffffff
	Prefetchable memory behind bridge: 00000000f2900000-00000000f29fffff
	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
	Kernel modules: shpchp

00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 03) (prog-if 00 [UHCI])
	Subsystem: Lenovo 82801I (ICH9 Family) USB UHCI Controller [17aa:20f0]
	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 16
	Region 4: I/O ports at 18a0 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd

00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 03) (prog-if 00 [UHCI])
	Subsystem: Lenovo 82801I (ICH9 Family) USB UHCI Controller [17aa:20f0]
	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 B routed to IRQ 17
	Region 4: I/O ports at 18c0 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd

00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 03) (prog-if 00 [UHCI])
	Subsystem: Lenovo 82801I (ICH9 Family) USB UHCI Controller [17aa:20f0]
	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 C routed to IRQ 18
	Region 4: I/O ports at 18e0 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd

00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 03) (prog-if 20 [EHCI])
	Subsystem: Lenovo 82801I (ICH9 Family) USB2 EHCI Controller [17aa:20f1]
	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 D routed to IRQ 19
	Region 0: Memory at f2826000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: <access denied>
	Kernel driver in use: ehci-pci
	Kernel modules: ehci_pci

00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 93) (prog-if 01 [Subtractive 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
	Bus: primary=00, secondary=0d, subordinate=0d, sec-latency=0
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>

00:1f.0 ISA bridge [0601]: Intel Corporation ICH9M LPC Interface Controller [8086:2919] (rev 03)
	Subsystem: Lenovo ICH9M LPC Interface Controller [17aa:20f6]
	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
	Capabilities: <access denied>
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich

00:1f.2 SATA controller [0106]: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] [8086:2929] (rev 03) (prog-if 01 [AHCI 1.0])
	Subsystem: Lenovo 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] [17aa:20f8]
	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 B routed to IRQ 28
	Region 0: I/O ports at 1818 [size=8]
	Region 1: I/O ports at 180c [size=4]
	Region 2: I/O ports at 1810 [size=8]
	Region 3: I/O ports at 1808 [size=4]
	Region 4: I/O ports at 1c00 [size=32]
	Region 5: Memory at f2825000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: <access denied>
	Kernel driver in use: ahci
	Kernel modules: ahci

00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 03)
	Subsystem: Lenovo 82801I (ICH9 Family) SMBus Controller [17aa:20f9]
	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 23
	Region 0: Memory at f2826400 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at 1c20 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801

03:00.0 Network controller [0280]: Intel Corporation Ultimate N WiFi Link 5300 [8086:4236]
	Subsystem: Intel Corporation Ultimate N WiFi Link 5300 [8086:1011]
	Physical Slot: 1
	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 31
	Region 0: Memory at f2500000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: <access denied>
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi


** USB devices:
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 17ef:480c Lenovo Integrated Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 0a5c:2145 Broadcom Corp. BCM2045B (BDC-2.1) [Bluetooth Controller]
Bus 003 Device 002: ID 08ff:2810 AuthenTec, Inc. AES2810
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en_AU: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.17.0-1-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.130
ii  kmod                                    25-1
ii  linux-base                              4.5

Versions of packages linux-image-4.17.0-1-amd64 recommends:
ii  apparmor             2.12-5
ii  firmware-linux-free  3.4
ii  irqbalance           1.3.0-0.1+b1

Versions of packages linux-image-4.17.0-1-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  grub-pc                 2.02+dfsg1-4
pn  linux-doc-4.17          <none>

Versions of packages linux-image-4.17.0-1-amd64 is related to:
ii  firmware-amd-graphics     20170823-1
ii  firmware-atheros          20170823-1
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          20170823-1
pn  firmware-libertas         <none>
ii  firmware-linux-nonfree    20170823-1
ii  firmware-misc-nonfree     20170823-1
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]

#61547

FromBen Hutchings <ben@decadent.org.uk>
Date2018-07-24 18:30 +0200
Message-ID<wf8md-nW-7@gated-at.bofh.it>
In reply to#61543

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

Control: tag -1 moreinfo

On Tue, 2018-07-24 at 21:25 +1000, Julian Calaby wrote:
> Package: src:linux
> Version: 4.17.8-1
> Severity: important
> 
> Dear Maintainer,
> 
> Linux 4.17.0-1-amd64 (4.17.8-1) causes my laptop (Thinkpad X200) to fail to
> boot.
> 
> During a boot with Systemd the disk gets stopped erroneously approximately
> after udev "coldplugs" anything that hasn't been autodetected already.
> 
> This causes the kernel to stop the system disk causing the machine to hang
> with all SATA requests eventually timing out and all startup processes
> eventually failing.
> 
> FROM MEMORY, the last disk related messages are:
> 
> sda: Synchronising SCSI cache
> sda: Stopping disk
> 
> Please note that as I cannot boot that kernel, this bug report was compiled on
> 4.16.0-2-amd64 (4.16.16-2) instead.
> 
> Severity is relatively low as this laptop is the only computer I maintain that
> has shown this behaviour (so far) which makes me think it's related to the
> specific drivers I'm using, not something "generic" to this kernel version.
> 
> Please let me know if there's any further details you need about my hardware
> or system configuration.
[...]

Does adding the kernel parameter "ahci.mobile_lpm_policy=1" avoid this?

Can you also run these commands to get the model and revision strings
for the HD, so this can be done automatically if necessary:

cat /sys/bus/scsi/devices/1:0:0:0/model
cat /sys/bus/scsi/devices/1:0:0:0/rev

Ben.

-- 
Ben Hutchings
[W]e found...that it wasn't as easy to get programs right as we had
thought. I realized that a large part of my life from then on was going
to be spent in finding mistakes in my own programs.
                                                 - Maurice Wilkes, 1949

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

#61646

FromJulian Calaby <julian.calaby@gmail.com>
Date2018-07-27 13:40 +0200
Message-ID<wg9gd-7yi-1@gated-at.bofh.it>
In reply to#61547
Hi Ben,

On Wed, Jul 25, 2018 at 2:23 AM Ben Hutchings <ben@decadent.org.uk> wrote:
>
> Control: tag -1 moreinfo
>
> On Tue, 2018-07-24 at 21:25 +1000, Julian Calaby wrote:
> > Package: src:linux
> > Version: 4.17.8-1
> > Severity: important
> >
> > Dear Maintainer,
> >
> > Linux 4.17.0-1-amd64 (4.17.8-1) causes my laptop (Thinkpad X200) to fail to
> > boot.
> >
> > During a boot with Systemd the disk gets stopped erroneously approximately
> > after udev "coldplugs" anything that hasn't been autodetected already.
> >
> > This causes the kernel to stop the system disk causing the machine to hang
> > with all SATA requests eventually timing out and all startup processes
> > eventually failing.
> >
> > FROM MEMORY, the last disk related messages are:
> >
> > sda: Synchronising SCSI cache
> > sda: Stopping disk
> >
> > Please note that as I cannot boot that kernel, this bug report was compiled on
> > 4.16.0-2-amd64 (4.16.16-2) instead.
> >
> > Severity is relatively low as this laptop is the only computer I maintain that
> > has shown this behaviour (so far) which makes me think it's related to the
> > specific drivers I'm using, not something "generic" to this kernel version.
> >
> > Please let me know if there's any further details you need about my hardware
> > or system configuration.
> [...]
>
> Does adding the kernel parameter "ahci.mobile_lpm_policy=1" avoid this?

No, booting with that parameter makes no difference.

> Can you also run these commands to get the model and revision strings
> for the HD, so this can be done automatically if necessary:
>
> cat /sys/bus/scsi/devices/1:0:0:0/model
> cat /sys/bus/scsi/devices/1:0:0:0/rev

For reference:

root@kbitbucket:/home/jcalaby# cat /sys/bus/scsi/devices/0\:0\:0\:0/model
ST9250315AS
root@kbitbucket:/home/jcalaby# cat /sys/bus/scsi/devices/0\:0\:0\:0/rev
LVM1

I'll try to acquire more information over the weekend.

Thanks,

-- 
Julian Calaby

Email: julian.calaby@gmail.com
Profile: http://www.google.com/profiles/julian.calaby/

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

#61668

FromTomas Janousek <tomi@nomi.cz>
Date2018-07-29 12:10 +0200
Message-ID<wgQOe-Qd-17@gated-at.bofh.it>
In reply to#61646
Hi Julian,

On Fri, Jul 27, 2018 at 09:31:42PM +1000, Julian Calaby wrote:
> > Does adding the kernel parameter "ahci.mobile_lpm_policy=1" avoid this?
> 
> No, booting with that parameter makes no difference.

Can you try "dm_mod.use_blk_mq=0 scsi_mod.use_blk_mq=0" as well?

Block multiqueue was enabled in debian's 4.17
(https://salsa.debian.org/kernel-team/linux/commit/049487d8822c141bef503b024e73db55e2a695ff)
but there's no support for runtime power management yet:
https://github.com/torvalds/linux/blob/a26fb01c2879ed7026e6cbd78bb701912d249eef/block/blk-core.c#L3765

Unfortunately, the above code doesn't prevent laptop-mode-tools, tlp nor
custom udev rules from enabling runtime-pm for devices so if you use any of
that, you might be having runtime-pm enabled on devices that don't support it,
and therefore get hangs.

See https://github.com/rickysarraf/laptop-mode-tools/issues/123 for more
details.

-- 
Tomáš Janoušek, a.k.a. Pivník, a.k.a. Liskni_si, http://work.lisk.in/

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

#61676

FromTomas Janousek <tomi@nomi.cz>
Date2018-07-30 17:10 +0200
Message-ID<whhY5-MI-3@gated-at.bofh.it>
In reply to#61668
Hi again,

On Sun, Jul 29, 2018 at 11:52:10AM +0200, Tomas Janousek wrote:
> Unfortunately, the above code doesn't prevent laptop-mode-tools, tlp nor
> custom udev rules from enabling runtime-pm for devices so if you use any of
> that, you might be having runtime-pm enabled on devices that don't support it,
> and therefore get hangs.

LKML doesn't disappoint, I reported the above yesterday and there's a patch
today: https://patchwork.kernel.org/patch/10548975/ :-)

-- 
Tomáš Janoušek, a.k.a. Pivník, a.k.a. Liskni_si, http://work.lisk.in/

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

#61682

FromJulian Calaby <julian.calaby@gmail.com>
Date2018-07-31 12:40 +0200
Message-ID<whAen-3we-29@gated-at.bofh.it>
In reply to#61668
Hi Tomas,

On Sun, Jul 29, 2018 at 7:52 PM Tomas Janousek <tomi@nomi.cz> wrote:
>
> Hi Julian,
>
> On Fri, Jul 27, 2018 at 09:31:42PM +1000, Julian Calaby wrote:
> > > Does adding the kernel parameter "ahci.mobile_lpm_policy=1" avoid this?
> >
> > No, booting with that parameter makes no difference.
>
> Can you try "dm_mod.use_blk_mq=0 scsi_mod.use_blk_mq=0" as well?

Disabling multi-queue fixes it and allows it to boot.

I have not tested this in combination with the AHCI LPM policy change
Ben suggested as just disabling multi-queue Works Fine For Me.

> Block multiqueue was enabled in debian's 4.17
> (https://salsa.debian.org/kernel-team/linux/commit/049487d8822c141bef503b024e73db55e2a695ff)
> but there's no support for runtime power management yet:
> https://github.com/torvalds/linux/blob/a26fb01c2879ed7026e6cbd78bb701912d249eef/block/blk-core.c#L3765

This seems unwize. I saw the patches implementing runtime PM for MQ go
by and am firmly in the camp of not enabling the new way to do stuff
until it's (mostly) feature-complete with the old way.

> Unfortunately, the above code doesn't prevent laptop-mode-tools, tlp nor
> custom udev rules from enabling runtime-pm for devices so if you use any of
> that, you might be having runtime-pm enabled on devices that don't support it,
> and therefore get hangs.
>
> See https://github.com/rickysarraf/laptop-mode-tools/issues/123 for more
> details.

Ah! I have laptop-mode-tools installed.

Thanks,

-- 
Julian Calaby

Email: julian.calaby@gmail.com
Profile: http://www.google.com/profiles/julian.calaby/

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

#61548 — Processed: Re: Bug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2018-07-24 18:30 +0200
SubjectProcessed: Re: Bug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot
Message-ID<wf8md-nW-5@gated-at.bofh.it>
In reply to#61543
Processing control commands:

> tag -1 moreinfo
Bug #904441 [src:linux] linux-image-4.17.0-1-amd64: system disk stopped during boot
Added tag(s) moreinfo.

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

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

#61667

From"Felix C. Stegerman" <flx@obfusk.net>
Date2018-07-29 01:40 +0200
Message-ID<wgGYx-2W9-1@gated-at.bofh.it>
In reply to#61543
Package: src:linux
Version: 4.17.8-1
Followup-For: Bug #904441

Dear Maintainer,

Same issue here; 4.16.0-2-amd64 works fine; ahci.mobile_lpm_policy=1
does not help.

$ cat /sys/bus/scsi/devices/0\:0\:0\:0/model
ST9500325ASG
$ cat /sys/bus/scsi/devices/0\:0\:0\:0/rev
APM1

Happy to help debug this.  Not sure where to start though.

Thanks.

- Felix

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

** Model information
sys_vendor: Apple Inc.
product_name: MacBookPro8,1
product_version: 1.0

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE= (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.17.0-1-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.132
ii  kmod                                    25-1
ii  linux-base                              4.5

Versions of packages linux-image-4.17.0-1-amd64 recommends:
ii  apparmor             2.13-4
ii  firmware-linux-free  3.4
ii  irqbalance           1.3.0-0.1+b1

Versions of packages linux-image-4.17.0-1-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  extlinux                3:6.03+dfsg1-2
ii  grub-efi-amd64          2.02+dfsg1-4
pn  linux-doc-4.17          <none>

Versions of packages linux-image-4.17.0-1-amd64 is related to:
pn  firmware-amd-graphics     <none>
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>
pn  firmware-iwlwifi          <none>
pn  firmware-libertas         <none>
pn  firmware-linux-nonfree    <none>
pn  firmware-misc-nonfree     <none>
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] | [prev] | [next] | [standalone]

#61677

FromYOSHINO Yoshihito <yy.y.ja.jp@gmail.com>
Date2018-07-30 18:50 +0200
Message-ID<whjwS-1Bh-9@gated-at.bofh.it>
In reply to#61543
Package: src:linux
Followup-For: Bug #904441

Dear Maintainer,

I have the same problem.
Setting "dm_mod.use_blk_mq=0 scsi_mod.use_blk_mq=0" works well.

$ cat /sys/bus/scsi/devices/0\:0\:0\:0/model
APPLE SSD TS0128
$ cat /sys/bus/scsi/devices/0\:0\:0\:0/rev
0219

Regards,

--
YOSHINO Yoshihito <yy.y.ja.jp@gmail.com>

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8),
LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

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

#61686

FromOlivier Berger <olivier.berger@telecom-sudparis.eu>
Date2018-08-01 15:30 +0200
Message-ID<whZmp-28V-5@gated-at.bofh.it>
In reply to#61677
On Tue, Jul 31, 2018 at 01:40:45AM +0900, YOSHINO Yoshihito wrote:
> I have the same problem.
> Setting "dm_mod.use_blk_mq=0 scsi_mod.use_blk_mq=0" works well.
> 
FWIW, same here on Dell Latitude 5580.

# cat /sys/bus/scsi/devices/2\:0\:0\:0/model
SAMSUNG SSD PM87
# cat /sys/bus/scsi/devices/2\:0\:0\:0/rev
2D0Q

# uname -a
Linux newlatitude 4.17.0-1-amd64 #1 SMP Debian 4.17.8-1 (2018-07-20) x86_64 GNU/Linux

Also, laptop-mode-tools 1.72-2 installed, FWIW.

Now seems fine after I added dm_mod.use_blk_mq=0 scsi_mod.use_blk_mq=0

Best regards,

-- 
Olivier BERGER 
http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)

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

#61758 — Bug#904441: Same problem with Asus Zenbook

FromAntoine Amarilli <a3nm@a3nm.net>
Date2018-08-07 12:40 +0200
SubjectBug#904441: Same problem with Asus Zenbook
Message-ID<wk7zb-7Th-3@gated-at.bofh.it>
In reply to#61543

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

Hi all,

I am having the same problem with my Asus Zenbook: it booted fine with
linux-image-4.16.0-2-amd64 but wasn't booting with
linux-image-4.17.0-1-amd64. The specific problem was that the boot
sequence hung and near the end the following was displayed (copying from
a screen capture):

  sd 0:0:0:0: [sda] Synchronizing SCSI cache
  sd 0:0:0:0: [sda] Stopping disk

The laptop model is "ASUSTeK COMPUTER INC. UX330UAK" as reported during
boot:

Aug  7 12:18:15 zeta kernel: [    9.374427] asus_nb_wmi: Identified laptop model 'ASUSTeK COMPUTER INC. UX330UAK'
Aug  7 12:18:15 zeta kernel: [    9.374495] asus_wmi: Initialization: 0x1
Aug  7 12:18:15 zeta kernel: [    9.374538] asus_wmi: BIOS WMI version: 9.0
Aug  7 12:18:15 zeta kernel: [    9.374576] asus_wmi: SFUN value: 0x2021
Aug  7 12:18:15 zeta kernel: [    9.375536] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input11
Aug  7 12:18:15 zeta kernel: [    9.375646] asus_wmi: Number of fans: 0

And to give some info about the SSD:

$ cat /sys/bus/scsi/devices/0:0:0:0/model 
Micron_1100_MTFD
$ cat /sys/bus/scsi/devices/0:0:0:0/rev  
A020

Adding "dm_mod.use_blk_mq=0 scsi_mod.use_blk_mq=0" to the boot
parameters in grub works around the problem for now, thanks for
suggesting this!

Best,

-- 
Antoine Amarilli

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

#61770

FromFelipe Sologuren <sologuren@estudiohum.cl>
Date2018-08-09 17:50 +0200
Message-ID<wkVmh-5gs-5@gated-at.bofh.it>
In reply to#61543

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

On Sun, 29 Jul 2018 11:52:10 +0200 Tomas Janousek <tomi@nomi.cz> wrote:
> Hi Julian,
>
> On Fri, Jul 27, 2018 at 09:31:42PM +1000, Julian Calaby wrote:
> > > Does adding the kernel parameter "ahci.mobile_lpm_policy=1" avoid
this?
> >
> > No, booting with that parameter makes no difference.
>
> Can you try "dm_mod.use_blk_mq=0 scsi_mod.use_blk_mq=0" as well?
Setting "dm_mod.use_blk_mq=0 scsi_mod.use_blk_mq=0" allows to boot.

$ cat /sys/bus/scsi/devices/0\:0\:0\:0/model
Crucial_CT1050MX
$ cat /sys/bus/scsi/devices/0\:0\:0\:0/rev
R040

I have laptop-mode-tools installed too.

Thank you.

[toc] | [prev] | [standalone]

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

csiph-web