Complete computer freeze (screen, mouse, keyboard) after 17.04 upgrade

Bug #1687383 reported by Pascal Gicquel
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
High
Unassigned
Zesty
Invalid
High
Unassigned

Bug Description

Extract of system log (Oops part)
Apr 30 12:01:25 salon kernel: [ 8273.281441] Oops: 0000 [#1] SMP
Apr 30 12:01:25 salon kernel: [ 8273.281447] Modules linked in: ccm gpio_ich snd_hda_codec_hdmi joydev input_leds arc4 ath9k ath9k_common coretemp kvm_intel ath9k_hw ath kvm irqbypass mac80211 snd_hda_codec_realtek snd_hda_codec_generic serio_raw snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep lpc_ich cfg80211 snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq tpm_infineon snd_seq_device snd_timer mac_hid shpchp snd soundcore parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech ff_memless psmouse uas nouveau firewire_ohci pata_acpi firewire_core crc_itu_t usb_storage mxm_wmi wmi video pata_jmicron i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm fjes usbhid hid
Apr 30 12:01:25 salon kernel: [ 8273.281524] CPU: 1 PID: 1210 Comm: InputThread Not tainted 4.10.0-20-generic #22-Ubuntu
Apr 30 12:01:25 salon kernel: [ 8273.281531] Hardware name: Gigabyte Technology Co., Ltd. EP45-DS3R/EP45-DS3R, BIOS F4 05/28/2008
Apr 30 12:01:25 salon kernel: [ 8273.281538] task: ffff955c5bad6a40 task.stack: ffffac66c1758000
Apr 30 12:01:25 salon kernel: [ 8273.281545] RIP: 0010:dma_fence_wait_timeout+0x36/0xf0
Apr 30 12:01:25 salon kernel: [ 8273.281550] RSP: 0018:ffffac66c175ba38 EFLAGS: 00010206
Apr 30 12:01:25 salon kernel: [ 8273.281556] RAX: 0000000000000001 RBX: ffff955bc39ca680 RCX: ffffffffc0351fa0
Apr 30 12:01:25 salon kernel: [ 8273.281563] RDX: 7fffffffffffffff RSI: 0000000000000001 RDI: ffff955c5b82f300
Apr 30 12:01:25 salon kernel: [ 8273.281569] RBP: ffffac66c175ba58 R08: 0000000000000000 R09: ffff955c71c98000
Apr 30 12:01:25 salon kernel: [ 8273.281575] R10: ffff955c5286bd40 R11: ffff955c727aaa08 R12: ffff955c5b82f300
Apr 30 12:01:25 salon kernel: [ 8273.281581] R13: 0000000000000001 R14: 7fffffffffffffff R15: 0000000000000001
Apr 30 12:01:25 salon kernel: [ 8273.281588] FS: 00007fa96383f700(0000) GS:ffff955c7fc80000(0000) knlGS:0000000000000000
Apr 30 12:01:25 salon kernel: [ 8273.281595] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 30 12:01:25 salon kernel: [ 8273.281601] CR2: 0000000000000021 CR3: 000000011b64f000 CR4: 00000000000006e0
Apr 30 12:01:25 salon kernel: [ 8273.281607] Call Trace:
Apr 30 12:01:25 salon kernel: [ 8273.281623] drm_atomic_helper_wait_for_fences+0x48/0x120 [drm_kms_helper]
Apr 30 12:01:25 salon kernel: [ 8273.281679] nv50_disp_atomic_commit+0x19c/0x2a0 [nouveau]
Apr 30 12:01:25 salon kernel: [ 8273.281703] drm_atomic_commit+0x4b/0x50 [drm]
Apr 30 12:01:25 salon kernel: [ 8273.281714] drm_atomic_helper_update_plane+0xec/0x150 [drm_kms_helper]
Apr 30 12:01:25 salon kernel: [ 8273.281731] __setplane_internal+0x1b4/0x280 [drm]
Apr 30 12:01:25 salon kernel: [ 8273.281738] ? __ww_mutex_lock_slowpath+0x29a/0x3d0
Apr 30 12:01:25 salon kernel: [ 8273.281757] drm_mode_cursor_universal+0x126/0x210 [drm]
Apr 30 12:01:25 salon kernel: [ 8273.281774] drm_mode_cursor_common+0x86/0x180 [drm]
Apr 30 12:01:25 salon kernel: [ 8273.281781] ? ep_poll_callback+0xef/0x1f0
Apr 30 12:01:25 salon kernel: [ 8273.281797] drm_mode_cursor_ioctl+0x50/0x70 [drm]
Apr 30 12:01:25 salon kernel: [ 8273.281812] drm_ioctl+0x21b/0x4c0 [drm]
Apr 30 12:01:25 salon kernel: [ 8273.281828] ? drm_mode_setplane+0x1a0/0x1a0 [drm]
Apr 30 12:01:25 salon kernel: [ 8273.281835] ? _copy_to_user+0x54/0x60
Apr 30 12:01:25 salon kernel: [ 8273.281877] nouveau_drm_ioctl+0x74/0xc0 [nouveau]
Apr 30 12:01:25 salon kernel: [ 8273.281884] do_vfs_ioctl+0xa3/0x610
Apr 30 12:01:25 salon kernel: [ 8273.281890] ? __check_object_size+0x100/0x1d7
Apr 30 12:01:25 salon kernel: [ 8273.281895] SyS_ioctl+0x79/0x90
Apr 30 12:01:25 salon kernel: [ 8273.281901] entry_SYSCALL_64_fastpath+0x1e/0xad
Apr 30 12:01:25 salon kernel: [ 8273.281907] RIP: 0033:0x7fa96e376987
Apr 30 12:01:25 salon kernel: [ 8273.281911] RSP: 002b:00007fa96383d338 EFLAGS: 00003246 ORIG_RAX: 0000000000000010
Apr 30 12:01:25 salon kernel: [ 8273.281918] RAX: ffffffffffffffda RBX: 0000559c9117f930 RCX: 00007fa96e376987
Apr 30 12:01:25 salon kernel: [ 8273.281925] RDX: 00007fa96383d370 RSI: 00000000c01c64a3 RDI: 000000000000000e
Apr 30 12:01:25 salon kernel: [ 8273.281931] RBP: 0000000000000000 R08: 0000559c908510c0 R09: 0000000000000780
Apr 30 12:01:25 salon kernel: [ 8273.282266] R10: 0000559c911ae250 R11: 0000000000003246 R12: 0000000000000000
Apr 30 12:01:25 salon kernel: [ 8273.282935] R13: 0000559c9117e000 R14: 00000000000001e7 R15: 000000000000012b
Apr 30 12:01:25 salon kernel: [ 8273.283668] Code: e5 41 56 41 55 41 54 53 0f 88 b0 00 00 00 49 89 fc 41 89 f5 49 89 d6 66 66 66 66 90 49 8b 44 24 08 41 0f b6 f5 4c 89 f2 4c 89 e7 <ff> 50 20 49 89 c5 66 66 66 66 90 5b 4c 89 e8 41 5c 41 5d 41 5e
Apr 30 12:01:25 salon kernel: [ 8273.284485] RIP: dma_fence_wait_timeout+0x36/0xf0 RSP: ffffac66c175ba38
Apr 30 12:01:25 salon kernel: [ 8273.284881] CR2: 0000000000000021
Apr 30 12:01:25 salon kernel: [ 8273.292413] ---[ end trace 307803d6cee4dc68 ]---
---
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: pascal 1905 F.... pulseaudio
 /dev/snd/controlC0: pascal 1905 F.... pulseaudio
CurrentDesktop: Unity:Unity7
DistroRelease: Ubuntu 17.04
HibernationDevice: RESUME=UUID=2a668880-cef2-4949-975e-48f23c82e6a0
InstallationDate: Installed on 2014-06-05 (1060 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Gigabyte Technology Co., Ltd. EP45-DS3R
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic root=UUID=69f5eae9-a368-4b55-92a3-14220d419f65 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
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:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: zesty
Uname: Linux 4.10.0-20-generic x86_64
UpgradeStatus: Upgraded to zesty on 2017-04-23 (7 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare src sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4
dmi.board.name: EP45-DS3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/28/2008:svnGigabyteTechnologyCo.,Ltd.:pnEP45-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EP45-DS3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1687383

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
Pascal Gicquel (rogbro) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected zesty
description: updated
Revision history for this message
Pascal Gicquel (rogbro) wrote : CRDA.txt

apport information

Revision history for this message
Pascal Gicquel (rogbro) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Pascal Gicquel (rogbro) wrote : IwConfig.txt

apport information

Revision history for this message
Pascal Gicquel (rogbro) wrote : JournalErrors.txt

apport information

Revision history for this message
Pascal Gicquel (rogbro) wrote : Lspci.txt

apport information

Revision history for this message
Pascal Gicquel (rogbro) wrote : Lsusb.txt

apport information

Revision history for this message
Pascal Gicquel (rogbro) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Pascal Gicquel (rogbro) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Pascal Gicquel (rogbro) wrote : ProcEnviron.txt

apport information

Revision history for this message
Pascal Gicquel (rogbro) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Pascal Gicquel (rogbro) wrote : ProcModules.txt

apport information

Revision history for this message
Pascal Gicquel (rogbro) wrote : PulseList.txt

apport information

Revision history for this message
Pascal Gicquel (rogbro) wrote : UdevDb.txt

apport information

Revision history for this message
Pascal Gicquel (rogbro) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Pascal Gicquel (rogbro) wrote :

Did as requested and changed the status to 'Confirmed'. Let me know if I can do anything else that could help to solve it.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Do you have a way to reproduce the bug, or was it a one time event?

Changed in linux (Ubuntu):
importance: Undecided → High
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc8

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-da-key
Revision history for this message
Pascal Gicquel (rogbro) wrote : Re: [Bug 1687383] Re: Complete computer freeze (screen, mouse, keyboard) after 17.04 upgrade

I produced it a few times a day in the last days. At first I thought it
was at random, but now it seems to me that the crash appears each time a
few minutes after coming out of sleep mode.

I just produced it tonight with linux-crashdump installed. I have now a
full /var/crash directory. Is such data useful to anybody ? In this
case, where should I upload it ?

I will try tomorrow the latest upstream kernel as requested.

Le 01/05/2017 à 20:55, Joseph Salisbury a écrit :
> Do you have a way to reproduce the bug, or was it a one time event?
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => High
>

Revision history for this message
Pascal Gicquel (rogbro) wrote :

I installed the upstream kernel 'Linux salon 4.11.0-041100rc8-generic #201704232131 SMP Mon Apr 24 01:32:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux'.
It does not seem to produce the bug. I will add the tag 'kernel-fixed-upstream' as suggested.

tags: added: kernel-fixed-upstream
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you also see if this issue was cc'd to upstream stable and is fixed in the latest 4.10 upstream kernel?

It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.14/

Revision history for this message
Pascal Gicquel (rogbro) wrote :

I tested kernel 4.10.14 and did not produce the crash.

I do not really understand what "see if this issue was cc'd to upstream stable" means ? Could you explain where (or how) I could "see" that ?

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you also see if the bug exists in 4.10.11? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.11/

The purpose of this testing is to see if this bug is specific to Ubuntu. Your testing shows that the bug does not exist in mainline. Many bug fixes are cc'd to the upstream stable kernels, which 4.10.14 is the latest for 4.10.

The Ubuntu -proposed kernel now has the upstream stable 4.10.11 updates. This is the reason I asked to test it. If it is good, I would next ask you to test the Zesty -proposed kernel. If the Zesty -proposed kernel is bad, that means the bug is Ubuntu specific.

Changed in linux (Ubuntu):
status: Incomplete → In Progress
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Zesty):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Joseph Salisbury (jsalisbury)
Revision history for this message
Pascal Gicquel (rogbro) wrote :

I did get a crash with 4.10.11 (mainline) after two hours of work. I am going to attach the log file obtained with crashdump.

Revision history for this message
Pascal Gicquel (rogbro) wrote :
Download full text (7.8 KiB)

It seems the "add attachment" does not work. Here is the interesting part of the log with the last crash (with 4.10.11)
[ 0.000000] Linux version 4.10.11-041011-generic (kernel@gloin) (gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) ) #201704180310 SMP Tue Apr 18 07:12:27 UTC 2017
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.10.11-041011-generic root=UUID=69f5eae9-a368-4b55-92a3-14220d419f65 ro quiet splash crashkernel=384M-:128M vt.handoff=7
...
[ 8443.156255] BUG: unable to handle kernel NULL pointer dereference at 0000000000000020
[ 8443.156280] IP: dma_fence_wait_timeout+0x36/0xf0
[ 8443.156286] PGD 0
[ 8443.156287]
[ 8443.156295] Oops: 0000 [#1] SMP
[ 8443.156300] Modules linked in: ccm gpio_ich snd_hda_codec_hdmi coretemp kvm_intel kvm irqbypass snd_hda_codec_realtek input_leds joydev snd_hda_codec_generic lpc_ich serio_raw snd_hda_intel arc4 snd_hda_codec snd_hda_core ath9k ath9k_common ath9k_hw ath mac80211 snd_seq_midi cfg80211 snd_hwdep snd_seq_midi_event snd_pcm snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore tpm_infineon shpchp mac_hid parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech ff_memless uas psmouse nouveau pata_acpi firewire_ohci usb_storage firewire_core crc_itu_t mxm_wmi wmi video i2c_algo_bit pata_jmicron ttm drm_kms_helper syscopyarea fjes sysfillrect sysimgblt fb_sys_fops drm usbhid hid
[ 8443.156382] CPU: 1 PID: 1278 Comm: InputThread Not tainted 4.10.11-041011-generic #201704180310
[ 8443.156390] Hardware name: Gigabyte Technology Co., Ltd. EP45-DS3R/EP45-DS3R, BIOS F4 05/28/2008
[ 8443.156398] task: ffffa0ee78928000 task.stack: ffffc3364136c000
[ 8443.156405] RIP: 0010:dma_fence_wait_timeout+0x36/0xf0
[ 8443.156411] RSP: 0018:ffffc3364136fa38 EFLAGS: 00010206
[ 8443.156418] RAX: 0000000000000000 RBX: ffffa0edc84b7980 RCX: ffffffffc04e6980
[ 8443.156425] RDX: 7fffffffffffffff RSI: 0000000000000001 RDI: ffffa0ee77d0a3c0
[ 8443.156432] RBP: ffffc3364136fa58 R08: 0000000000000000 R09: ffffa0ee71cc0000
[ 8443.156439] R10: ffffa0ee77087c80 R11: ffffa0ee7244ad08 R12: ffffa0ee77d0a3c0
[ 8443.156445] R13: 0000000000000001 R14: 7fffffffffffffff R15: 0000000000000001
[ 8443.156453] FS: 00007ffa36e09700(0000) GS:ffffa0ee7fc80000(0000) knlGS:0000000000000000
[ 8443.156460] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 8443.156466] CR2: 0000000000000020 CR3: 00000001389d4000 CR4: 00000000000006e0
[ 8443.156473] Call Trace:
[ 8443.156493] drm_atomic_helper_wait_for_fences+0x48/0x120 [drm_kms_helper]
[ 8443.156546] nv50_disp_atomic_commit+0x19c/0x2a0 [nouveau]
[ 8443.156569] drm_atomic_commit+0x4b/0x50 [drm]
[ 8443.156581] drm_atomic_helper_update_plane+0xec/0x150 [drm_kms_helper]
[ 8443.156598] __setplane_internal+0x1b4/0x280 [drm]
[ 8443.156606] ? __ww_mutex_lock_slowpath+0x29a/0x3d0
[ 8443.156623] drm_mode_cursor_universal+0x126/0x210 [drm]
[ 8443.156640] drm_mode_cursor_common+0x86/0x180 [drm]
[ 8443.156647] ? ep_poll_callback+0xef/0x1f0
[ 8443.156664] drm_mode_cursor_ioctl+0x50/0x70 [drm]
[ 8443.156679] drm_ioctl+0x21b/0x4c0 [drm]
[ 8443.156696] ? drm_mode_setplane+0x1a0/0x1a0 [drm]
[ 8443.156739] nouveau_drm_ioctl+0x74/0xc0 [nouveau]
[ 8443.156746] do_vfs_ioct...

Read more...

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

We can perform a "Reverse" bisect to identify the commit that fixes this. We know it is fixed in 4.11-rc8. We need to identify the last bad kernel and the first good one. Can you next test v4.11-rc1? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc1/

Changed in linux (Ubuntu Zesty):
status: In Progress → Invalid
Changed in linux (Ubuntu):
status: In Progress → Invalid
Brad Figg (brad-figg)
tags: added: cscc
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.