i915 freeze

Bug #1535714 reported by Daniel Walton
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

randomly system will freeze. Freeze in that screen will be blank and system will not accept keyboard commands to change to a terminal or to chagne the caps lock light.

Can ssh into the laptop while its "frozen". The syslog/journal shows a kenel stacktrace (below)

Seems more common after suspending.

don't recall it happening with 15.04. If it did start with 15.04 it would of been with the latter kernels.

Seems similar to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1454868

### kenel crash log from logs ###

Jan 19 23:23:10 ath lightdm[6665]: pam_unix(lightdm:session): session closed for user bob
Jan 19 23:23:10 ath kernel: ------------[ cut here ]------------
Jan 19 23:23:10 ath kernel: WARNING: CPU: 2 PID: 6493 at /home/kernel/COD/linux/include/linux/kref.h:46 drm_framebuffer_reference+0x64/0x70 [d
Jan 19 23:23:10 ath kernel: Modules linked in: ctr ccm rfcomm xt_recent xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptab
Jan 19 23:23:10 ath kernel: snd_hda_core memstick serio_raw snd_pcm_dmaengine snd_hwdep snd_pcm snd_seq_midi i2c_designware_platform snd_seq_
Jan 19 23:23:10 ath kernel: ppdev lp parport autofs4 btrfs drbg ansi_cprng xts gf128mul algif_skcipher af_alg dm_crypt raid10 raid456 async_r
Jan 19 23:23:10 ath kernel: CPU: 2 PID: 6493 Comm: Xorg Not tainted 4.4.0-040400rc7-generic #201512272230
Jan 19 23:23:10 ath kernel: Hardware name: ASUSTeK COMPUTER INC. X200MA/X200MA, BIOS X200MA.302 01/21/2014
Jan 19 23:23:10 ath kernel: 0000000000000000 00000000d23b3796 ffff880019dc3948 ffffffff813c9124
Jan 19 23:23:10 ath kernel: 0000000000000000 ffff880019dc3980 ffffffff8107db92 ffff880035b446c0
Jan 19 23:23:10 ath kernel: ffff88001834c300 ffff88001834c300 ffff88010b10ac00 ffff880035484000
Jan 19 23:23:10 ath kernel: Call Trace:
Jan 19 23:23:10 ath kernel: [<ffffffff813c9124>] dump_stack+0x44/0x60
Jan 19 23:23:10 ath kernel: [<ffffffff8107db92>] warn_slowpath_common+0x82/0xc0
Jan 19 23:23:10 ath kernel: [<ffffffff8107dcda>] warn_slowpath_null+0x1a/0x20
Jan 19 23:23:10 ath kernel: [<ffffffffc00d4704>] drm_framebuffer_reference+0x64/0x70 [drm]
Jan 19 23:23:10 ath kernel: [<ffffffffc00e6a0d>] drm_atomic_set_fb_for_plane+0x2d/0x90 [drm]
Jan 19 23:23:10 ath kernel: [<ffffffffc016bdde>] __drm_atomic_helper_set_config+0xde/0x3c0 [drm_kms_helper]
Jan 19 23:23:10 ath kernel: [<ffffffffc016cd01>] restore_fbdev_mode+0x221/0x260 [drm_kms_helper]
Jan 19 23:23:10 ath kernel: [<ffffffffc016ef13>] drm_fb_helper_restore_fbdev_mode_unlocked+0x33/0x80 [drm_kms_helper]
Jan 19 23:23:10 ath kernel: [<ffffffffc016ef8d>] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper]
Jan 19 23:23:10 ath kernel: [<ffffffffc024ecca>] intel_fbdev_set_par+0x1a/0x60 [i915]
Jan 19 23:23:10 ath kernel: [<ffffffff8144bf06>] fb_set_var+0x236/0x460
Jan 19 23:23:10 ath kernel: [<ffffffff810b4df4>] ? enqueue_task_fair+0xa4/0x8b0
Jan 19 23:23:10 ath kernel: [<ffffffff8101fd59>] ? sched_clock+0x9/0x10
Jan 19 23:23:10 ath kernel: [<ffffffff810ad9bf>] ? sched_clock_cpu+0x8f/0xa0
Jan 19 23:23:10 ath kernel: [<ffffffff8144221f>] fbcon_blank+0x30f/0x350
Jan 19 23:23:10 ath kernel: [<ffffffffc03b6b18>] ? set_extent_buffer_dirty+0x78/0xd0 [btrfs]
Jan 19 23:23:10 ath kernel: [<ffffffff814d8e33>] do_unblank_screen+0xd3/0x1a0
Jan 19 23:23:10 ath kernel: [<ffffffff814ce4fa>] vt_ioctl+0x50a/0x12f0
Jan 19 23:23:10 ath kernel: [<ffffffff814c1aff>] tty_ioctl+0x35f/0xc30
Jan 19 23:23:10 ath kernel: [<ffffffff811e5dc5>] ? kfree+0x115/0x130
Jan 19 23:23:10 ath kernel: [<ffffffff8121ca73>] ? dput+0xb3/0x220
Jan 19 23:23:10 ath kernel: [<ffffffff81226044>] ? mntput+0x24/0x40
Jan 19 23:23:10 ath kernel: [<ffffffff812192a8>] do_vfs_ioctl+0x298/0x480
Jan 19 23:23:10 ath kernel: [<ffffffff81207ade>] ? ____fput+0xe/0x10
Jan 19 23:23:10 ath kernel: [<ffffffff8109b138>] ? task_work_run+0x78/0x90
Jan 19 23:23:10 ath kernel: [<ffffffff81219509>] SyS_ioctl+0x79/0x90
Jan 19 23:23:10 ath kernel: [<ffffffff817fcff6>] entry_SYSCALL_64_fastpath+0x16/0x75
Jan 19 23:23:10 ath kernel: ---[ end trace 65a51a25ba0b2f99 ]---
Jan 19 23:23:10 ath kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000060
Jan 19 23:23:10 ath kernel: IP: [<ffffffffc0245bbc>] intel_fb_obj_invalidate+0x1c/0xf0 [i915]
Jan 19 23:23:10 ath kernel: PGD 0
Jan 19 23:23:10 ath kernel: Oops: 0000 [#1] SMP
Jan 19 23:23:10 ath kernel: Modules linked in: ctr ccm rfcomm xt_recent xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptab
Jan 19 23:23:10 ath kernel: snd_hda_core memstick serio_raw snd_pcm_dmaengine snd_hwdep snd_pcm snd_seq_midi i2c_designware_platform snd_seq_
Jan 19 23:23:10 ath kernel: ppdev lp parport autofs4 btrfs drbg ansi_cprng xts gf128mul algif_skcipher af_alg dm_crypt raid10 raid456 async_r
Jan 19 23:23:10 ath kernel: CPU: 2 PID: 6493 Comm: Xorg Tainted: G W 4.4.0-040400rc7-generic #201512272230
Jan 19 23:23:10 ath kernel: Hardware name: ASUSTeK COMPUTER INC. X200MA/X200MA, BIOS X200MA.302 01/21/2014
Jan 19 23:23:10 ath kernel: task: ffff88006797be80 ti: ffff880019dc0000 task.ti: ffff880019dc0000
Jan 19 23:23:10 ath kernel: RIP: 0010:[<ffffffffc0245bbc>] [<ffffffffc0245bbc>] intel_fb_obj_invalidate+0x1c/0xf0 [i915]
Jan 19 23:23:10 ath kernel: RSP: 0018:ffff880019dc3a80 EFLAGS: 00010246
Jan 19 23:23:10 ath kernel: RAX: ffff88006797be80 RBX: ffff880110267500 RCX: 00000000000f7e8c
Jan 19 23:23:10 ath kernel: RDX: ffff880035b446c0 RSI: 0000000000000000 RDI: ffff880110267500
Jan 19 23:23:10 ath kernel: RBP: ffff880019dc3aa8 R08: 0000000000019d80 R09: ffffffffc00e4d46
Jan 19 23:23:10 ath kernel: R10: ffffea0002489500 R11: ffff8800b2d5b600 R12: 0000000000000000
Jan 19 23:23:10 ath kernel: R13: 0000000000000000 R14: 0000000000200001 R15: 0000000000000080
Jan 19 23:23:10 ath kernel: FS: 00007f17d8149980(0000) GS:ffff88013fd00000(0000) knlGS:0000000000000000
Jan 19 23:23:10 ath kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Jan 19 23:23:10 ath kernel: CR2: 0000000000000060 CR3: 000000011a128000 CR4: 00000000001006e0
Jan 19 23:23:10 ath kernel: Stack:
Jan 19 23:23:10 ath kernel: ffff880035475e00 ffff88003532b000 0000000000000000 0000000000200001
Jan 19 23:23:10 ath kernel: 0000000000000080 ffff880019dc3ac8 ffffffffc024ecf3 000000000004aa1e
Jan 19 23:23:10 ath kernel: ffff880019dc3c70 ffff880019dc3c40 ffffffff8144bf06 ffff88003532b060
Jan 19 23:23:10 ath kernel: Call Trace:
Jan 19 23:23:10 ath kernel: [<ffffffffc024ecf3>] intel_fbdev_set_par+0x43/0x60 [i915]
Jan 19 23:23:10 ath kernel: [<ffffffff8144bf06>] fb_set_var+0x236/0x460
Jan 19 23:23:10 ath kernel: [<ffffffff810b4df4>] ? enqueue_task_fair+0xa4/0x8b0
Jan 19 23:23:10 ath kernel: [<ffffffff8101fd59>] ? sched_clock+0x9/0x10
Jan 19 23:23:10 ath kernel: [<ffffffff810ad9bf>] ? sched_clock_cpu+0x8f/0xa0
Jan 19 23:23:10 ath kernel: [<ffffffff8144221f>] fbcon_blank+0x30f/0x350
Jan 19 23:23:10 ath kernel: [<ffffffffc03b6b18>] ? set_extent_buffer_dirty+0x78/0xd0 [btrfs]
Jan 19 23:23:10 ath kernel: [<ffffffff814d8e33>] do_unblank_screen+0xd3/0x1a0
Jan 19 23:23:10 ath kernel: [<ffffffff814ce4fa>] vt_ioctl+0x50a/0x12f0
Jan 19 23:23:10 ath kernel: [<ffffffff814c1aff>] tty_ioctl+0x35f/0xc30
Jan 19 23:23:10 ath kernel: [<ffffffff811e5dc5>] ? kfree+0x115/0x130
Jan 19 23:23:10 ath kernel: [<ffffffff8121ca73>] ? dput+0xb3/0x220
Jan 19 23:23:10 ath kernel: [<ffffffff81226044>] ? mntput+0x24/0x40
Jan 19 23:23:10 ath kernel: [<ffffffff812192a8>] do_vfs_ioctl+0x298/0x480
Jan 19 23:23:10 ath kernel: [<ffffffff81207ade>] ? ____fput+0xe/0x10
Jan 19 23:23:10 ath kernel: [<ffffffff8109b138>] ? task_work_run+0x78/0x90
Jan 19 23:23:10 ath kernel: [<ffffffff81219509>] SyS_ioctl+0x79/0x90
Jan 19 23:23:10 ath kernel: [<ffffffff817fcff6>] entry_SYSCALL_64_fastpath+0x16/0x75
Jan 19 23:23:10 ath kernel: Code: 41 5f 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55 41 54 41 89 f5 53
Jan 19 23:23:10 ath kernel: RIP [<ffffffffc0245bbc>] intel_fb_obj_invalidate+0x1c/0xf0 [i915]
Jan 19 23:23:10 ath kernel: RSP <ffff880019dc3a80>
Jan 19 23:23:10 ath kernel: CR2: 0000000000000060
Jan 19 23:23:10 ath kernel: ---[ end trace 65a51a25ba0b2f9a ]---

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
Uname: Linux 4.4.0-040400rc7-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
Date: Tue Jan 19 23:32:16 2016
DistUpgraded: 2015-10-26 07:28:02,425 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:15bd]
InstallationDate: Installed on 2014-07-31 (537 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: ASUSTeK COMPUTER INC. X200MA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-040400rc7-generic root=UUID=5e8a8002-00f4-434f-a107-f6427d316379 ro rootflags=subvol=@ quiet splash zswap.enabled=1 nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to wily on 2015-10-25 (85 days ago)
dmi.bios.date: 01/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X200MA.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X200MA
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.:bvrX200MA.302:bd01/21/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X200MA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Tue Jan 19 13:52:59 2016
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 4377
 vendor CMN
xserver.version: 2:1.17.2-1ubuntu9.1

Revision history for this message
Daniel Walton (daniel-walton) wrote :
penalvch (penalvch)
tags: added: bios-outdated-506
Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Daniel Walton (daniel-walton) wrote :

Many thanks for your help. much appreciated.

I have updated the bios to v506 (04/15/2015 MDY) today.

It is an intermittent bug, so I'll report back after two weeks.
( If it works fine for two weeks then I expect it is fixed.)

Revision history for this message
Daniel Walton (daniel-walton) wrote :

Time: Yesterday morning

symptoms:
found laptop frozen with black screen, was working the night before and was left on.
Using a Ubuntu mainline 4.4.x kernel.

Unable to ping or connect to over the network, where with the above bug I was able to.

Actions:
Have removed the 4.4.x kernels, now using standard 4.2 Wily kernel.
Will report back

Revision history for this message
Daniel Walton (daniel-walton) wrote :

using std wily kernel "4.2.0-25-generic" my system will freeze over night.
Happened 2 nights in a row. Leave the laptop plugged in and turned on, in the morning system is unresponsive. capslock light doesn't change.
Cannot be pinged or ssh'ed into across network (wifi)
When booting usual spach screen doesn't appear. Need to gues it's at encryption dialog entry, and type passwords to boot.
so have removed "quiet splash" boot options.

Initial bug report above was done while ssh'ed in, as keyboard not working, screen blank.
Seemed like a video card driver issue as i was unable to get the screen to appear after attempting to restart lightdm service.

have installed and have been running "4.4.0-997-generic" from ubuntu mainline intel driver kernel. (linux-image-4.4.0-997-generic_4.4.0-997.201601242100_amd64.deb)
(after 4.2 kernel)
Has been stable and wakes from suspend mode happily.

Will continue to report back if chagnes in behaviour.

Timo Aaltonen (tjaalton)
summary: - Xorg freeze
+ i915 freeze
affects: xorg (Ubuntu) → linux (Ubuntu)
Revision history for this message
Daniel Walton (daniel-walton) wrote :

using standard 4.2 Wily kernel, system will freeze commonly while unlocking. (unsing gnome & lightdm)

Have switched to a older kernel which has been very stable so far. no errors.
Will report back.

Revision history for this message
Vegard Vesterheim (vegard-vesterheim) wrote :
Download full text (9.6 KiB)

I am having similar problems with xenial (Kernel 4.4). Xorg crash, console is "frozen". Machine is up and running (can log in via ssh).

Shutdown/reboot does not work. Machine must be powercycled to be usable again.

 Seems to occur after screen has been idle for sometime.

[ 3301.824747] ------------[ cut here ]------------
[ 3301.824763] WARNING: CPU: 1 PID: 3465 at /build/linux-H9bHY_/linux-4.4.0/include/linux/kref.h:46 drm_framebuffer_reference+0x64/0x70 [drm]()
[ 3301.824785] Modules linked in: rfcomm veth ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables nls_utf8 cifs fscache xt_addrtype xt_conntrack aufs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp iptable_filter ip_tables x_tables uas usb_storage bnep binfmt_misc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core btusb v4l2_common btrtl btbcm joydev btintel videodev snd_usb_audio bluetooth input_leds snd_usbmidi_lib media bridge snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic hp_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm 8021q intel_rapl x86_pkg_temp_thermal garp intel_powerclamp mrp coretemp crct10dif_pclmul
[ 3301.824804] stp crc32_pclmul llc aesni_intel snd_seq_midi snd_seq_midi_event aes_x86_64 lrw gf128mul snd_rawmidi glue_helper ablk_helper cryptd snd_seq serio_raw snd_seq_device snd_timer mei_me mei snd lpc_ich soundcore 8250_fintek tpm_infineon mac_hid kvm_intel kvm irqbypass ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev sunrpc lp parport autofs4 hid_lenovo hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect e1000e sysimgblt fb_sys_fops psmouse ahci drm ptp libahci pps_core wmi fjes video
[ 3301.824806] CPU: 1 PID: 3465 Comm: Xorg Not tainted 4.4.0-11-generic #26-Ubuntu
[ 3301.824807] Hardware name: Hewlett-Packard HP EliteDesk 800 G1 USDT/18E5, BIOS L01 v02.21 12/17/2013
[ 3301.824808] 0000000000000286 00000000e8c70193 ffff880404323920 ffffffff813e1ec3
[ 3301.824809] 0000000000000000 ffffffffc0080800 ffff880404323958 ffffffff8107fe12
[ 3301.824810] ffff88040551f240 ffff8800d53da900 ffff8800d53da900 ffff88040986d000
[ 3301.824810] Call Trace:
[ 3301.824814] [<ffffffff813e1ec3>] dump_stack+0x63/0x90
[ 3301.824817] [<ffffffff8107fe12>] warn_slowpath_common+0x82/0xc0
[ 3301.824818] [<ffffffff8107ff5a>] warn_slowpath_null+0x1a/0x20
[ 3301.824826] [<ffffffffc00589b4>] drm_framebuffer_reference+0x64/0x70 [drm]
[ 3301.824835] [<ffffffffc0069c6d>] drm_atomic_set_fb_for_plane+0x2d/0x90 [drm]
[ 3301.824842] [<ffffffffc016b47e>] __drm_atomic_helper_set_config+0xde/0x3c0 [drm_kms_helper]
[ 3301.824846] [<ffffffffc016c3b1>] restore_fbdev_mode+0x221/0x260 [drm_kms_helper]
[ 3301.824855] [<ffffffffc00683da>] ? drm_modeset_lock_all_ctx+0x9a/0xb0 [drm]
[ 3301.824860] [<ffffffffc016e593>] drm_fb_helper_restore_fbdev_mode_unlocked+0x33/0x80 [drm_kms_helper]
[ 3301.824864] [<ffffffffc016e60d>] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper]
[ 3301.824881] [<ffffffffc02259...

Read more...

Revision history for this message
Daniel Walton (daniel-walton) wrote :

My workaround is to use kernel 3.14.1-031401-generic.

Being that I was able to ssh in when the UI froze suggested to me it was a xorg related bug connected to the kernel.
Kernel as old kernels worked (as above)
So Kernel video drivers ?

Assume its an issue with the Intel drivers.

When ssh'ed in I was unable to get the lightdm service to restart.

Using the above kernel my laptop has been up for 13 days when before it would usually freeze after waking from suspend or after screen turns off. Odd thing was that the keyboard wou;dn't allow switching to a virtual terminal.
Didn't try sysreq keys.

Revision history for this message
penalvch (penalvch) wrote :

Vegard Vesterheim, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Revision history for this message
Vegard Vesterheim (vegard-vesterheim) wrote : Re: [Bug 1535714] Re: i915 freeze

On Fri, 11 Mar 2016 14:42:42 +0000 "Christopher M. Penalver" <email address hidden> wrote:

> Vegard Vesterheim, it will help immensely if you filed a new report
> with the Ubuntu repository kernel (not mainline/upstream) via a
> terminal:
> ubuntu-bug linux
>
> Please feel free to subscribe me to it.

Here you go:

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1556965

 - Vegard V -

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Daniel Walton (daniel-walton) wrote :

X200MA.506
04/15/2015

On Sat, 21 May 2016 at 00:05 Christopher M. Penalver <
<email address hidden>> wrote:

> Daniel Walton, please provide the output of the following terminal command
> (not perform an apport-collect):
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1535714
>
> Title:
> i915 freeze
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535714/+subscriptions
>

Revision history for this message
penalvch (penalvch) wrote :

Daniel Walton, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: latest-bios-506
removed: bios-outdated-506
Changed in linux (Ubuntu):
importance: Low → Medium
Revision history for this message
Daniel Walton (daniel-walton) wrote :

Downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/

Downloaded and installed the following:
linux-headers-4.6.0-040600_4.6.0-040600.201605151930_all.deb
linux-headers-4.6.0-040600-generic_4.6.0-040600.201605151930_amd64.deb
linux-image-4.6.0-040600-generic_4.6.0-040600.201605151930_amd64.deb

Will report back when I have some findings for you.

On Mon, 23 May 2016 at 05:50 Christopher M. Penalver <
<email address hidden>> wrote:

> Daniel Walton, in order to allow additional upstream developers to examine
> the issue, at your earliest convenience, could you please test the latest
> upstream kernel available from
> http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in
> mind the following:
> 1) The one to test is at the very top line at the top of the page (not the
> daily folder).
> 2) The release names are irrelevant.
> 3) The folder time stamps aren't indicative of when the kernel actually
> was released upstream.
> 4) Install instructions are available at
> https://wiki.ubuntu.com/Kernel/MainlineBuilds .
>
> If testing on your main install would be inconvenient, one may:
> 1) Install Ubuntu to a different partition and then test this there.
> 2) Backup, or clone the primary install.
>
> If the latest kernel did not allow you to test to the issue (ex. you
> couldn't boot into the OS) please make a comment in your report about this,
> and continue to test the next most recent kernel version until you can test
> to the issue. Once you've tested the upstream kernel, please comment on
> which kernel version specifically you tested. If this issue is fixed in the
> mainline kernel, please add the following tags by clicking on the yellow
> circle with a black pencil icon, next to the word Tags, located at the
> bottom of the report description:
> kernel-fixed-upstream
> kernel-fixed-upstream-X.Y-rcZ
>
> Where X, and Y are the first two numbers of the kernel version, and Z is
> the release candidate number if it exists.
>
> If the mainline kernel does not fix the issue, please add the following
> tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-X.Y-rcZ
>
> Please note, an error to install the kernel does not fit the criteria of
> kernel-bug-exists-upstream.
>
> Also, you don't need to apport-collect further unless specifically
> requested to do so.
>
> Once testing of the latest upstream kernel is complete, please mark this
> report Status Confirmed. Please let us know your results.
>
> Thank you for your understanding.
>
> ** Tags removed: bios-outdated-506
> ** Tags added: latest-bios-506
>
> ** Changed in: linux (Ubuntu)
> Importance: Low => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1535714
>
> Title:
> i915 freeze
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535714/+subscriptions
>

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.