This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1522094
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
** Tags added: vivid
--
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/1522094
Title:
WARNING: CPU: 0 PID: 233 at /build/linux-lts-vivid-pTjnAT/linux-lts-
vivid-3.19.0/drivers/gpu/drm/i915/intel_crt.c:145
hsw_crt_pre_enable+0x7f/0x90 [i915]()
Status in linux package in Ubuntu:
Incomplete
Bug description:
When I connect a monitor the VGA port on the laptop - this is found in
dmesg, and some of the kernel modules linked in become unstable [
btrfs for instance, if it's in use].
[ 2.962400] ------------[ cut here ]------------
[ 2.962424] WARNING: CPU: 0 PID: 233 at
/build/linux-lts-vivid-pTjnAT/linux-lts-vivid-3.19.0/drivers/gpu/drm/i915/intel_crt.c:145
hsw_crt_pre_enable+0x7f/0x90 [i915]()
[ 2.962425] SPLL already enabled
[ 2.962426] Modules linked in: uas usb_storage hid_generic usbhid hid i915
psmouse i2c_algo_bit e1000e drm_kms_helper ahci libahci sdhci_pci drm ptp
pps_core pata_acpi wmi sdhci_acpi video sdhci
[ 2.962437] CPU: 0 PID: 233 Comm: plymouthd Not tainted 3.19.0-37-generic
#42~14.04.1-Ubuntu
[ 2.962438] Hardware name: Dell Inc. Latitude E6540/0PXPYJ, BIOS A15
05/19/2015
[ 2.962439] ffffffffc02fd7f8 ffff880220d23ab8 ffffffff817af92b
0000000000003a7a
[ 2.962440] ffff880220d23b08 ffff880220d23af8 ffffffff81074e0a
0000000000000046
[ 2.962442] ffff880035fb0000 ffff88003615eb60 ffff880035f8f400
ffff88003615e800
[ 2.962444] Call Trace:
[ 2.962449] [<ffffffff817af92b>] dump_stack+0x45/0x57
[ 2.962452] [<ffffffff81074e0a>] warn_slowpath_common+0x8a/0xc0
[ 2.962453] [<ffffffff81074e86>] warn_slowpath_fmt+0x46/0x50
[ 2.962464] [<ffffffffc02b601f>] hsw_crt_pre_enable+0x7f/0x90 [i915]
[ 2.962475] [<ffffffffc02a1a7c>] haswell_crtc_enable+0x3fc/0xaf0 [i915]
[ 2.962485] [<ffffffffc029f1a2>] __intel_set_mode+0x872/0xc60 [i915]
[ 2.962495] [<ffffffffc02a5af2>] intel_crtc_set_config+0x9e2/0xf60 [i915]
[ 2.962506] [<ffffffffc010382f>] drm_mode_set_config_internal+0x6f/0x110
[drm]
[ 2.962511] [<ffffffffc019e5c8>] restore_fbdev_mode+0xc8/0xf0
[drm_kms_helper]
[ 2.962515] [<ffffffffc01a04e9>]
drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x80 [drm_kms_helper]
[ 2.962525] [<ffffffffc02b31ee>] intel_fbdev_restore_mode+0x1e/0x50 [i915]
[ 2.962536] [<ffffffffc02d787e>] i915_driver_lastclose+0xe/0x20 [i915]
[ 2.962541] [<ffffffffc00f6c4e>] drm_lastclose+0x2e/0x130 [drm]
[ 2.962546] [<ffffffffc00f7088>] drm_release+0x338/0x540 [drm]
[ 2.962549] [<ffffffff811ee077>] __fput+0xe7/0x220
[ 2.962551] [<ffffffff811ee1fe>] ____fput+0xe/0x10
[ 2.962553] [<ffffffff81091e3c>] task_work_run+0xac/0xd0
[ 2.962556] [<ffffffff81015007>] do_notify_resume+0x97/0xb0
[ 2.962558] [<ffffffff817b762f>] int_signal+0x12/0x17
[ 2.962559] ---[ end trace b6b778d930eaeda7 ]---
This is the lts-vivid kernel. downgrading to the lts-utopic kernel fixes the
issue.
I tried the wily-lts, same issue.
I've also tried to recent kernels in http://kernel.ubuntu.com/~kernel-
ppa :
linux-image-4.3.0-040300-generic_4.3.0-040300 is still broken
linux-image-4.4.0-040400rc3-generic_4.4.0-040400rc3.201511300321
works fine! :)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522094/+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
