Bug#834386: linux-image-4.6.0-1-amd64: Locks hard on boot.

2016-12-17 Thread Nathan Paul Simons
Just tried  rebooting with 4.7.0-1-amd64 and it didn't work.

On Wed, Dec 07, 2016 at 02:24:57AM +, Ben Hutchings wrote:
> Nathan, I'm sorry we didn't answer this report much sooner.
> 
> Have you tried upgrading to a newer kernel version, and did that
> resolve the problem?  The latest version in testing is now 4.8.7-1.
> 
> If the latest version has the same problem, does adding the kernel
> parameter 'nomodeset' allow the system to boot all the way to a text-
> mode login prompt?
> 
> Ben.
> 
> -- 
> Ben Hutchings
> When in doubt, use brute force. - Ken Thompson
> 



-- 
Sent from my Universal Turing Machine
My phone (please leave a voicemail or SMS): +17607933893



Bug#834386: linux-image-4.6.0-1-amd64: Locks hard on boot.

2016-12-06 Thread Ben Hutchings
Nathan, I'm sorry we didn't answer this report much sooner.

Have you tried upgrading to a newer kernel version, and did that
resolve the problem?  The latest version in testing is now 4.8.7-1.

If the latest version has the same problem, does adding the kernel
parameter 'nomodeset' allow the system to boot all the way to a text-
mode login prompt?

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson



signature.asc
Description: This is a digitally signed message part


Bug#834386: linux-image-4.6.0-1-amd64: Locks hard on boot.

2016-08-14 Thread Nathan Paul Simons
Package: src:linux
Version: 4.6.4-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?
 - I accidentally unplugged the system, and the system was powered
   off after I came back from an errand. I powered the system on,
   and it locked after the usual (and expected) complaints about
   missing Intel Bluetooth firmware.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
  - I hard booted (as system was unresponsive to ctrl-alt-del and
magic SysRq keys) and chose a different kernel to boot.
   * What was the outcome of this action?
  - Kernels 4.4.0 and 4.5.0 seem to boot fine.
   * What outcome did you expect instead?
  - I expected version 4.6.4 to boot.

It's been a long time since I've done kernel debugging, and
unfortunately that's not what the day job pays me to do, but the first
thing I would do is try pawing through a source diff between
versions. My best guess is a change introduced an incompatibility with
EFI on this system. Unfortunately, since it does not boot with the
offending kernel, I can't provide more information, and I am fairly
certain the messages are identical with newer kernels, right up until
the point it becomes unresponsive.

One last thing that might help: I tried switching off TPM, and that at
least had the effect of locking up after the font cnahged (indicating a
switching of video modes).

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

** Model information
sys_vendor: System76, Inc.
product_name: Oryx Pro
product_version: orxp1
chassis_vendor: System76, Inc.
chassis_version: N/A 
bios_vendor: American Megatrends Inc.
bios_version: 1.05.09RS76
board_vendor: System76, Inc.
board_name: Oryx Pro
board_version: orxp1

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM 
Registers [8086:1910] (rev 07)
Subsystem: CLEVO/KAPOK Computer Skylake Host Bridge/DRAM Registers 
[1558:6540]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation Sky Lake 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- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller [8086:a12f] (rev 31) (prog-if 30 [XHCI])
Subsystem: CLEVO/KAPOK Computer Sunrise Point-H USB 3.0 xHCI Controller 
[1558:6540]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H 
Thermal subsystem [8086:a131] (rev 31)
Subsystem: CLEVO/KAPOK Computer Sunrise Point-H Thermal subsystem 
[1558:6540]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME 
HECI #1 [8086:a13a] (rev 31)
Subsystem: CLEVO/KAPOK Computer Sunrise Point-H CSME HECI [1558:6540]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA 
Controller [AHCI mode] [8086:a103] (rev 31) (prog-if 01 [AHCI 1.0])
Subsystem: CLEVO/KAPOK Computer Sunrise Point-H SATA Controller [AHCI 
mode] [1558:6540]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ahci
Kernel modules: ahci

00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root 
Port #5 [8086:a114] (rev f1) (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- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-