[regression] login screen frozen after kernel update 4.13.0-38-generic (but 4.13.0-37-generic works)

Bug #1765110 reported by Joe Liau
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Committed
Medium
Unassigned

Bug Description

Ubuntu 17.10
4.13.0-38-generic
Asus UX305FA

When using the 4.13.0-38-generic kernel, the login screen is completely frozen and unresponsive.
Using a different kernel works fine.
---
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: obsidian 1922 F.... pulseaudio
 /dev/snd/controlC1: obsidian 1922 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 17.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-04-14 (371 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
 Bus 001 Device 002: ID 8087:0a2a Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX305FA
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=930dc116-4058-44a2-89bf-a754585181ff ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-38-generic N/A
 linux-backports-modules-4.13.0-38-generic N/A
 linux-firmware 1.169.3
Tags: artful
Uname: Linux 4.13.0-38-generic x86_64
UpgradeStatus: Upgraded to artful on 2017-10-20 (181 days ago)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/26/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX305FA.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX305FA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305FA.208:bd03/26/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX305FA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please try to find the closest two kernel versions where one works and the other doesn't.

tags: added: artful
affects: gdm3 (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joe Liau (joe) wrote :

Oops, I made a mistake. Here is the case:

4.13.0-38-generic (DOESN'T WORK)
4.13.0-37-generic (WORKS)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sounds like that contradicts the bug description: "When using the 4.13.0-37-generic kernel, the login screen is completely frozen and unresponsive."

If the description is wrong then please change it.

Revision history for this message
Joe Liau (joe) wrote :

Updated description.

description: updated
description: updated
summary: - login screen frozen after kernel update
+ [regression] login screen frozen after kernel update
tags: added: regression-update
Changed in linux (Ubuntu):
status: Incomplete → New
importance: Undecided → Medium
summary: - [regression] login screen frozen after kernel update
+ [regression] login screen frozen after kernel update 4.13.0-38-generic
+ (but 4.13.0-37-generic works)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1765110

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

Thank you in advance!

tags: added: kernel-da-key
Revision history for this message
Joe Liau (joe) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Joe Liau (joe) wrote : CRDA.txt

apport information

Revision history for this message
Joe Liau (joe) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Joe Liau (joe) wrote : IwConfig.txt

apport information

Revision history for this message
Joe Liau (joe) wrote : Lspci.txt

apport information

Revision history for this message
Joe Liau (joe) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Joe Liau (joe) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Joe Liau (joe) wrote : ProcEnviron.txt

apport information

Revision history for this message
Joe Liau (joe) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Joe Liau (joe) wrote : ProcModules.txt

apport information

Revision history for this message
Joe Liau (joe) wrote : PulseList.txt

apport information

Revision history for this message
Joe Liau (joe) wrote : RfKill.txt

apport information

Revision history for this message
Joe Liau (joe) wrote : UdevDb.txt

apport information

Revision history for this message
Joe Liau (joe) wrote : WifiSyslog.txt

apport information

Revision history for this message
Joe Liau (joe) wrote :

Somehow I was able to boot to the problem kernel just now without a freeze. But it took multiple booting tries. Then I ran apport.

I will try to see if it persists and also try the proposed kernel.

Revision history for this message
Joe Liau (joe) wrote :

The proposed kernel 4.13.0-39-generic is working.

Changed in linux (Ubuntu):
status: Incomplete → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.