System freezes when logging into gnome-shell

Bug #1685864 reported by Richard Eames on 2017-04-24
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Unassigned
Zesty
High
Unassigned

Bug Description

I upgraded to ubuntu 17.04 this morning, and can no longer login with gnome/gnome(classic)/gnome on wayland. When I try, the UI completely freezes, and keyboard and mouse no longer respond.
However, I am able to ssh into the machine, and see that there is a kernel bug in the logs:

10:48:51 kernel: error: failed to run Kubelet: invalid kubeconfig: stat /etc/kubernetes/kubelet.conf: no such file or directory
10:48:51 kernel: I0424 10:48:50.979914 4641 feature_gate.go:144] feature gates: map[]
10:48:51 kernel: ---[ end trace 41c77bd8e97d35e7 ]---
10:48:51 kernel: CR2: 0000000000000000
10:48:51 kernel: RIP: (null) RSP: ffffc17a44fdfa30
10:48:51 kernel: Code: Bad RIP value.
10:48:51 kernel: R13: 000055f4bf9307b0 R14: 000000000000000a R15: 000055f4bf8f06e0
10:48:51 kernel: R10: 000055f4bf5c0c50 R11: 0000000000003246 R12: 0000000000000130
10:48:51 kernel: RBP: 0000000000001c80 R08: 0000000000000040 R09: 0000000000000780
10:48:51 kernel: RDX: 00007f96d5f0a360 RSI: 00000000c01c64a3 RDI: 000000000000000e
10:48:51 kernel: RAX: ffffffffffffffda RBX: 00007f96e30dcc20 RCX: 00007f96e0afa987
10:48:51 kernel: RSP: 002b:00007f96d5f0a328 EFLAGS: 00003246 ORIG_RAX: 0000000000000010
10:48:51 kernel: RIP: 0033:0x7f96e0afa987
10:48:51 kernel: entry_SYSCALL_64_fastpath+0x1e/0xad
10:48:51 kernel: SyS_ioctl+0x79/0x90
10:48:51 kernel: ? vfs_read+0x96/0x130
10:48:51 kernel: ? __vfs_read+0x18/0x40
10:48:51 kernel: do_vfs_ioctl+0xa3/0x610
10:48:51 kernel: nouveau_drm_ioctl+0x74/0xc0 [nouveau]
10:48:51 kernel: ? _copy_to_user+0x54/0x60
10:48:51 kernel: ? drm_mode_setplane+0x1a0/0x1a0 [drm]
10:48:51 kernel: drm_ioctl+0x21b/0x4c0 [drm]
10:48:51 kernel: drm_mode_cursor_ioctl+0x50/0x70 [drm]
10:48:51 kernel: ? ep_poll_callback+0xef/0x1f0
10:48:51 kernel: drm_mode_cursor_common+0x86/0x180 [drm]
10:48:51 kernel: drm_mode_cursor_universal+0x126/0x210 [drm]
10:48:51 kernel: ? __ww_mutex_lock_slowpath+0x29a/0x3d0
10:48:51 kernel: __setplane_internal+0x1b4/0x280 [drm]
10:48:51 kernel: drm_atomic_helper_update_plane+0xec/0x150 [drm_kms_helper]
10:48:51 kernel: drm_atomic_commit+0x4b/0x50 [drm]
10:48:51 kernel: nv50_disp_atomic_commit+0x19c/0x2a0 [nouveau]
10:48:51 kernel: drm_atomic_helper_wait_for_fences+0x48/0x120 [drm_kms_helper]
10:48:51 kernel: ? dma_fence_wait_timeout+0x39/0xf0
10:48:51 kernel: Call Trace:
10:48:51 kernel: CR2: 0000000000000000 CR3: 00000007ed6df000 CR4: 00000000000406e0
10:48:51 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
10:48:51 kernel: FS: 00007f96d5f0c700(0000) GS:ffff9aeefed00000(0000) knlGS:0000000000000000
10:48:51 kernel: R13: 0000000000000001 R14: 7fffffffffffffff R15: 0000000000000001
10:48:51 kernel: R10: ffff9aeed329b780 R11: ffff9aeed1157c08 R12: ffff9aeed08c6480
10:48:51 kernel: RBP: ffffc17a44fdfa58 R08: 0000000000000000 R09: ffff9aeed272a000
10:48:51 kernel: RDX: 7fffffffffffffff RSI: 0000000000000001 RDI: ffff9aeed08c6480
10:48:51 kernel: RAX: ffff9aeed3402000 RBX: ffff9aee6883b000 RCX: ffffffffc047afa0
10:48:51 kernel: RSP: 0018:ffffc17a44fdfa30 EFLAGS: 00010206
10:48:51 kernel: RIP: 0010: (null)
10:48:51 kernel: task: ffff9aeeafb02d00 task.stack: ffffc17a44fdc000
10:48:51 kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./GA-990FX-GAMING, BIOS F1 11/05/2015
10:48:51 kernel: CPU: 4 PID: 2212 Comm: InputThread Tainted: G OE 4.10.0-20-generic #22-Ubuntu
10:48:51 kernel: k10temp fam15h_power parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic hid_microsoft usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops alx drm nvme mdio ahci nvme_core libahci fjes wmi
10:48:51 kernel: Modules linked in: xt_nat xt_tcpudp veth ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge stp llc aufs pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc snd_hda_codec_hdmi dm_crypt btrfs xor nls_iso8859_1 raid6_pq edac_mce_amd edac_core kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc input_leds joydev aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hda_core snd_rawmidi snd_hwdep snd_seq snd_pcm snd_seq_device snd_timer tpm_infineon mac_hid snd soundcore shpchp i2c_piix4
10:48:51 kernel: Oops: 0010 [#1] SMP
10:48:51 kernel:
10:48:50 kernel: PGD 0
10:48:50 kernel: IP: (null)
10:48:50 kernel: BUG: unable to handle kernel NULL pointer dereference at (null)

Let me know what other information I can provide.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-generic 4.10.0.20.22
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: redbrick 6500 F.... pulseaudio
 /dev/snd/controlC0: redbrick 6500 F.... pulseaudio
CurrentDesktop: Unity:Unity7
Date: Mon Apr 24 11:16:20 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=0c92ceaa-f94b-4a93-8df4-d3a8d65397f6
InstallationDate: Installed on 2016-04-22 (367 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=68cd6df4-a88f-4604-a099-ae7be33de08a ro iommu=soft quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-20-generic N/A
 linux-backports-modules-4.10.0-20-generic N/A
 linux-firmware 1.164
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-04-24 (0 days ago)
dmi.bios.date: 11/05/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F1
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: GA-990FX-GAMING
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd11/05/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FX-GAMING:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Richard Eames (naddiseo) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Richard Eames (naddiseo) wrote :

Might also be related to https://bugs.launchpad.net/ubuntu/zesty/+source/unity8-desktop-session/+bug/1632772 since removing unity8-desktop-session also allowed me to log in using gnome shell. However, I still think it shouldn't have caused a null pointer dereference.

Changed in linux (Ubuntu):
importance: Undecided → High
Changed in linux (Ubuntu Zesty):
importance: Undecided → High
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Are you able to login if you boot with the prior kernel version?

tags: added: kernel-da-keyu
tags: added: kernel-da-key
removed: kernel-da-keyu
Richard Eames (naddiseo) wrote :

Yes, if I boot using the 4.8 kernel I am able to login.

Joseph Salisbury (jsalisbury) wrote :

I'd like to perform a kernel bisect to figure out which commit caused this regression. We need to identify the earliest kernel that did not exhibit the bug and the first kernel that did exhibit the bug.

Can you test the following kernels and post back?

v4.9 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/
v4.10-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc1/
v4.10-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc4/

You don't have to test every kernel, just up until the kernel that first has this bug.

tags: added: performing-bisect
Richard Eames (naddiseo) wrote :

I couldn't boot into 4.10-rc1 (it got stuck at loading the initram), and the other two allowed me to login, however, there were errors printed:

4.9:
10:02:44 kernel: nouveau 0000:01:00.0: priv: GPC1: 419df4 00000000 (1f40820e)
10:02:44 kernel: nouveau 0000:01:00.0: priv: GPC0: 419df4 00000000 (1f40820e)
10:02:44 kernel: nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid
10:02:44 kernel: [Firmware Bug]: CPU7: Using firmware package id 1 instead of 0
10:02:44 kernel: [Firmware Bug]: CPU7: APIC id mismatch. Firmware: 17 CPUID: 7
10:02:44 kernel: [Firmware Bug]: CPU6: Using firmware package id 1 instead of 0
10:02:44 kernel: [Firmware Bug]: CPU6: APIC id mismatch. Firmware: 16 CPUID: 6
10:02:44 kernel: [Firmware Bug]: CPU5: Using firmware package id 1 instead of 0
10:02:44 kernel: [Firmware Bug]: CPU5: APIC id mismatch. Firmware: 15 CPUID: 5
10:02:44 kernel: [Firmware Bug]: CPU4: Using firmware package id 1 instead of 0
10:02:44 kernel: [Firmware Bug]: CPU4: APIC id mismatch. Firmware: 14 CPUID: 4
10:02:44 kernel: [Firmware Bug]: CPU3: Using firmware package id 1 instead of 0
10:02:44 kernel: [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
10:02:44 kernel: [Firmware Bug]: CPU2: Using firmware package id 1 instead of 0
10:02:44 kernel: [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
10:02:44 kernel: [Firmware Bug]: CPU1: Using firmware package id 1 instead of 0
10:02:44 kernel: [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
10:02:44 kernel: [Firmware Bug]: CPU0: Using firmware package id 1 instead of 0
10:02:44 kernel: [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0

4.10-rc3:
10:14:38 kernel: nouveau 0000:01:00.0: priv: GPC1: 419df4 00000000 (1e40820e)
10:14:38 kernel: nouveau 0000:01:00.0: priv: GPC0: 419df4 00000000 (1e40820e)
10:14:38 kernel: nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid
10:14:38 kernel: nouveau 0000:01:00.0: bus: MMIO write of 800000be FAULT at 10eb14 [ IBUS ]

Richard Eames (naddiseo) wrote :
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers