Launchpad has imported 15 comments from the remote bug at https://bugzilla.opensuse.org/show_bug.cgi?id=1058870.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2017-09-15T13:31:31+00:00 Axel Braun wrote: Created attachment 740759 Screenshot Did an update on an old ASUS eeePC to the above TW. With Kernel 4.13.1 2/3 of the screen is black. Switching back to Kernel 4.12.11 fixes the problem. See attached screenshot Graphics chip is a Intel mobile GM945 GM Let me know if I can provide further information Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/0 ------------------------------------------------------------------------ On 2017-09-18T14:28:03+00:00 Ada-lovelace wrote: I have the same problem with a Lenovo ThinkPad 13 (Ultrabook) with Intel Come i5. I receive a error message with "Failed to start Setup Virtual System Console". After that I have a black window. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/1 ------------------------------------------------------------------------ On 2017-09-18T14:32:45+00:00 Ada-lovelace wrote: I have the same problem with a Lenovo ThinkPad S2 (Ultrabook) with Intel Core i5. I receive a error message with "Failed to start Setup Virtual System Console". After that I have a black window. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/2 ------------------------------------------------------------------------ On 2017-09-18T16:03:50+00:00 Ada-lovelace wrote: My graphic card is a Intel(R) Graphics 520. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/3 ------------------------------------------------------------------------ On 2017-09-19T14:15:32+00:00 Jslaby-h wrote: Could you attach output of dmesg? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/4 ------------------------------------------------------------------------ On 2017-09-20T06:09:49+00:00 Axel Braun wrote: Created attachment 741173 dmesg It should be noted that the screen distortion appears in runlevel 3 as well. so it is not an issue of the video driver! Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/5 ------------------------------------------------------------------------ On 2017-09-21T07:27:27+00:00 Jslaby-h wrote: Hmm... Can you create a bug at https://bugs.freedesktop.org -- product DRI, component DRM/Intel? plane B assertion failure, should be off on pipe B but is still active ------------[ cut here ]------------ WARNING: CPU: 1 PID: 259 at ../drivers/gpu/drm/i915/intel_display.c:1252 assert_planes_disabled+0x128/0x140 [i915] Modules linked in: ata_piix i915(+) serio_raw i2c_algo_bit uhci_hcd ehci_pci drm_kms_helper ehci_hcd syscopyarea sysfillrect sysimgblt usbcore fb_sys_fops drm video button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua CPU: 1 PID: 259 Comm: systemd-udevd Not tainted 4.13.1-1-pae #1 Hardware name: ASUSTeK Computer INC. 901/901, BIOS 1903 03/17/2009 task: f4ae4700 task.stack: f4b3c000 EIP: assert_planes_disabled+0x128/0x140 [i915] EFLAGS: 00010286 CPU: 1 EAX: 00000046 EBX: f4bbc000 ECX: f71eb340 EDX: f71e486c ESI: 00000001 EDI: 00000001 EBP: f4b3dbe4 ESP: f4b3dbc8 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 CR0: 80050033 CR2: b7152000 CR3: 34aeca60 CR4: 000006f0 Call Trace: ? intel_disable_pipe+0x45/0x220 [i915] ? i9xx_crtc_disable+0x5c/0x3a0 [i915] ? drm_connector_list_iter_next+0x71/0xa0 [drm] ? drm_atomic_add_affected_connectors+0xd0/0xf0 [drm] ? intel_crtc_disable_noatomic+0xb5/0x290 [i915] ? intel_modeset_setup_hw_state+0xa58/0xc40 [i915] ? intel_modeset_setup_hw_state+0xa85/0xc40 [i915] ? intel_modeset_init+0x4d1/0xea0 [i915] ? intel_setup_gmbus+0x1e1/0x270 [i915] ? i915_driver_load+0xa4c/0x1330 [i915] ? local_pci_probe+0x35/0x80 ? pci_device_probe+0x158/0x170 ? driver_probe_device+0x2b9/0x410 ? __driver_attach+0x99/0xe0 ? driver_probe_device+0x410/0x410 ? bus_for_each_dev+0x4f/0x80 ? driver_attach+0x19/0x20 ? driver_probe_device+0x410/0x410 ? bus_add_driver+0x187/0x230 ? 0xf8306000 ? driver_register+0x56/0xd0 ? 0xf8306000 ? do_one_initcall+0x46/0x170 ? do_init_module+0x21/0x1d9 ? do_init_module+0x50/0x1d9 ? load_module+0x1435/0x1980 ? SyS_finit_module+0x79/0xc0 ? do_fast_syscall_32+0x71/0x150 ? entry_SYSENTER_32+0x4e/0x7c Code: ff 83 c4 10 e9 44 ff ff ff 57 68 a0 91 29 f8 e8 cc 8c 2d e0 0f ff 58 5a e9 30 ff ff ff ff 75 f0 50 68 d8 91 29 f8 e8 b5 8c 2d e0 <0f> ff 83 c4 0c e9 3e ff ff ff 8d b4 26 00 00 00 00 8d bc 27 00 ---[ end trace 0e7d08f54709149f ]--- Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/6 ------------------------------------------------------------------------ On 2017-09-21T16:17:32+00:00 Axel Braun wrote: https://bugs.freedesktop.org/show_bug.cgi?id=102929 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/7 ------------------------------------------------------------------------ On 2017-09-22T05:10:27+00:00 Axel Braun wrote: BTW, I noticed the same exception when booting kernel 4.12.11, but with no further impact Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/8 ------------------------------------------------------------------------ On 2017-09-22T15:18:18+00:00 Jslaby-h wrote: (In reply to Axel Braun from comment #8) > BTW, I noticed the same exception when booting kernel 4.12.11, but with no > further impact So are any of these (there are more of them) actually new? We need to know if this is something related to any of those warnings as it can help debugging. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/9 ------------------------------------------------------------------------ On 2017-09-26T05:36:02+00:00 Axel Braun wrote: There is indeed a difference: Kernel 4.13.1 throws 2 exceptions: [ 7.353528] ------------[ cut here ]------------ [ 7.353698] WARNING: CPU: 1 PID: 259 at ../drivers/gpu/drm/i915/intel_display.c:1252 assert_planes_disabled+0x128/0x140 [i915] [ 7.353703] Modules linked in: ata_piix i915(+) serio_raw i2c_algo_bit uhci_hcd ehci_pci drm_kms_helper ehci_hcd syscopyarea sysfillrect sysimgblt usbcore fb_sys_fops drm video button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua [ 7.353757] CPU: 1 PID: 259 Comm: systemd-udevd Not tainted 4.13.1-1-pae #1 [ 7.353777] Hardware name: ASUSTeK Computer INC. 901/901, BIOS 1903 03/17/2009 [ 7.353793] task: f4ae4700 task.stack: f4b3c000 [ 7.353956] EIP: assert_planes_disabled+0x128/0x140 [i915] [ 7.353960] EFLAGS: 00010286 CPU: 1 [ 7.353965] EAX: 00000046 EBX: f4bbc000 ECX: f71eb340 EDX: f71e486c and [ [ 7.448321] ------------[ cut here ]------------ [ 7.448362] WARNING: CPU: 0 PID: 270 at ../drivers/gpu/drm/drm_atomic_helper.c:912 drm_atomic_helper_update_legacy_modeset_state+0x220/0x230 [drm_kms_helper] [ 7.448365] Modules linked in: ata_piix i915 serio_raw i2c_algo_bit uhci_hcd ehci_pci drm_kms_helper ehci_hcd syscopyarea sysfillrect sysimgblt usbcore fb_sys_fops drm video button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua [ 7.448407] CPU: 0 PID: 270 Comm: kworker/u4:2 Tainted: G W 4.13.1-1-pae #1 [ 7.448410] Hardware name: ASUSTeK Computer INC. 901/901, BIOS 1903 03/17/2009 [ 7.448422] Workqueue: events_unbound async_run_entry_fn [ 7.448427] task: f4bb2780 task.stack: f4bb4000 [ 7.448457] EIP: drm_atomic_helper_update_legacy_modeset_state+0x220/0x230 [drm_kms_helper] [ 7.448460] EFLAGS: 00010246 CPU: 0 [ 7.448464] EAX: f4b6e800 EBX: f4b0ac00 ECX: f4bc5e00 EDX: f4ba1b00 [ 7.448468] ESI: f4ba2780 EDI: 00000000 EBP: f4bb5c38 ESP: f4bb5c1c [ 7.448473] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 7.448477] CR0: 80050033 CR2: b7153000 CR3: 349d0060 CR4: 000006f0 7.353969] ESI: 00000001 EDI: 00000001 EBP: f4b3dbe4 ESP: f4b3dbc8 [ 7.353975] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 7.353980] CR0: 80050033 CR2: b7152000 CR3: 34aeca60 CR4: 000006f0 while Kernel 4.12.11 has only one: [ 7.349601] ------------[ cut here ]------------ [ 7.349637] WARNING: CPU: 1 PID: 276 at ../drivers/gpu/drm/drm_atomic_helper.c:842 drm_atomic_helper_update_legacy_modeset_state+0x220/0x230 [drm_kms_helper] [ 7.349640] Modules linked in: ata_piix i915 serio_raw i2c_algo_bit drm_kms_helper ehci_pci uhci_hcd ehci_hcd usbcore syscopyarea sysfillrect sysimgblt fb_sys_fops drm video button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua [ 7.349680] CPU: 1 PID: 276 Comm: kworker/u4:2 Not tainted 4.12.11-1-pae #1 [ 7.349683] Hardware name: ASUSTeK Computer INC. 901/901, BIOS 1903 03/17/2009 [ 7.349696] Workqueue: events_unbound async_run_entry_fn [ 7.349700] task: f4aec6c0 task.stack: f4be6000 [ 7.349728] EIP: drm_atomic_helper_update_legacy_modeset_state+0x220/0x230 [drm_kms_helper] [ 7.349731] EFLAGS: 00010246 CPU: 1 [ 7.349735] EAX: f56ce400 EBX: f4bb7c00 ECX: f4bf3500 EDX: f4bf0e00 [ 7.349738] ESI: f4bf3700 EDI: 00000000 EBP: f4be7c38 ESP: f4be7c1c [ 7.349742] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 7.349746] CR0: 80050033 CR2: b74dd8e0 CR3: 34ae1160 CR4: 000006f0 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/10 ------------------------------------------------------------------------ On 2017-09-26T06:05:48+00:00 Axel Braun wrote: There is indeed a difference: Kernel 4.13.1 throws 2 exceptions: [ 7.353528] ------------[ cut here ]------------ [ 7.353698] WARNING: CPU: 1 PID: 259 at ../drivers/gpu/drm/i915/intel_display.c:1252 assert_planes_disabled+0x128/0x140 [i915] [ 7.353703] Modules linked in: ata_piix i915(+) serio_raw i2c_algo_bit uhci_hcd ehci_pci drm_kms_helper ehci_hcd syscopyarea sysfillrect sysimgblt usbcore fb_sys_fops drm video button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua [ 7.353757] CPU: 1 PID: 259 Comm: systemd-udevd Not tainted 4.13.1-1-pae #1 [ 7.353777] Hardware name: ASUSTeK Computer INC. 901/901, BIOS 1903 03/17/2009 [ 7.353793] task: f4ae4700 task.stack: f4b3c000 [ 7.353956] EIP: assert_planes_disabled+0x128/0x140 [i915] [ 7.353960] EFLAGS: 00010286 CPU: 1 [ 7.353965] EAX: 00000046 EBX: f4bbc000 ECX: f71eb340 EDX: f71e486c and [ [ 7.448321] ------------[ cut here ]------------ [ 7.448362] WARNING: CPU: 0 PID: 270 at ../drivers/gpu/drm/drm_atomic_helper.c:912 drm_atomic_helper_update_legacy_modeset_state+0x220/0x230 [drm_kms_helper] [ 7.448365] Modules linked in: ata_piix i915 serio_raw i2c_algo_bit uhci_hcd ehci_pci drm_kms_helper ehci_hcd syscopyarea sysfillrect sysimgblt usbcore fb_sys_fops drm video button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua [ 7.448407] CPU: 0 PID: 270 Comm: kworker/u4:2 Tainted: G W 4.13.1-1-pae #1 [ 7.448410] Hardware name: ASUSTeK Computer INC. 901/901, BIOS 1903 03/17/2009 [ 7.448422] Workqueue: events_unbound async_run_entry_fn [ 7.448427] task: f4bb2780 task.stack: f4bb4000 [ 7.448457] EIP: drm_atomic_helper_update_legacy_modeset_state+0x220/0x230 [drm_kms_helper] [ 7.448460] EFLAGS: 00010246 CPU: 0 [ 7.448464] EAX: f4b6e800 EBX: f4b0ac00 ECX: f4bc5e00 EDX: f4ba1b00 [ 7.448468] ESI: f4ba2780 EDI: 00000000 EBP: f4bb5c38 ESP: f4bb5c1c [ 7.448473] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 7.448477] CR0: 80050033 CR2: b7153000 CR3: 349d0060 CR4: 000006f0 7.353969] ESI: 00000001 EDI: 00000001 EBP: f4b3dbe4 ESP: f4b3dbc8 [ 7.353975] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 7.353980] CR0: 80050033 CR2: b7152000 CR3: 34aeca60 CR4: 000006f0 while Kernel 4.12.11 has only one: [ 7.349601] ------------[ cut here ]------------ [ 7.349637] WARNING: CPU: 1 PID: 276 at ../drivers/gpu/drm/drm_atomic_helper.c:842 drm_atomic_helper_update_legacy_modeset_state+0x220/0x230 [drm_kms_helper] [ 7.349640] Modules linked in: ata_piix i915 serio_raw i2c_algo_bit drm_kms_helper ehci_pci uhci_hcd ehci_hcd usbcore syscopyarea sysfillrect sysimgblt fb_sys_fops drm video button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua [ 7.349680] CPU: 1 PID: 276 Comm: kworker/u4:2 Not tainted 4.12.11-1-pae #1 [ 7.349683] Hardware name: ASUSTeK Computer INC. 901/901, BIOS 1903 03/17/2009 [ 7.349696] Workqueue: events_unbound async_run_entry_fn [ 7.349700] task: f4aec6c0 task.stack: f4be6000 [ 7.349728] EIP: drm_atomic_helper_update_legacy_modeset_state+0x220/0x230 [drm_kms_helper] [ 7.349731] EFLAGS: 00010246 CPU: 1 [ 7.349735] EAX: f56ce400 EBX: f4bb7c00 ECX: f4bf3500 EDX: f4bf0e00 [ 7.349738] ESI: f4bf3700 EDI: 00000000 EBP: f4be7c38 ESP: f4be7c1c [ 7.349742] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 7.349746] CR0: 80050033 CR2: b74dd8e0 CR3: 34ae1160 CR4: 000006f0 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/11 ------------------------------------------------------------------------ On 2017-10-12T17:33:53+00:00 Holger-stock wrote: The same Problem appeares on an Acer Aspire One A110L Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/12 ------------------------------------------------------------------------ On 2017-12-30T04:38:04+00:00 Svella wrote: I'm seeing the same problem on Gateway LT2030u with Intel Mobile 945 GME Graphics Chipset, after an autoupdate of the kernel from 4.12.9-1-default to 4.14.8-1-default Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/83 ------------------------------------------------------------------------ On 2017-12-30T08:57:09+00:00 Axel Braun wrote: (In reply to Shon Vella from comment #13) > I'm seeing the same problem on Gateway LT2030u with Intel Mobile 945 GME > Graphics Chipset, after an autoupdate of the kernel from 4.12.9-1-default to > 4.14.8-1-default The patch is not yet in Kernel 4.15 - see link in comment 7 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/84 ** Changed in: opensuse Status: Unknown => Confirmed ** Changed in: opensuse Importance: Unknown => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724639 Title: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in openSUSE: Confirmed Bug description: Installed O.S. on Samsung NC10. Display worked O.K. in text mode so the install went smoothly. When the system is rebooted, however, switching to graphics mode results in the below described screen corruption:- Left Hand Side 80% of screen black with a blue of white pixels and some blue lines at the top Right Hand Side 20% of screen OK. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-16-generic. AplayDevices: **** List of PLAYBACK Hardware Devices **** card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.20.7-0ubuntu3 Architecture: i386 ArecordDevices: **** List of CAPTURE Hardware Devices **** card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ian 918 F.... pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf0340000 irq 25' Mixer name : 'Realtek ALC272' Components : 'HDA:10ec0272,144dca00,00100001' Controls : 25 Simple ctrls : 12 CurrentDesktop: LXDE Date: Wed Oct 18 18:30:15 2017 HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75 InstallationDate: Installed on 2017-10-18 (0 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2009 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 07CA.M002.20090414.KTW dmi.board.name: NC10 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: NC10 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1724639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
