i915 several 'call traces' in dmesg

Bug #1547204 reported by Aapo Rantalainen
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned
Xenial
Confirmed
Medium
Unassigned

Bug Description

Ubuntu 16.04
Kernel: Ubuntu 4.4.0-4.19-generic 4.4.1

There are seven WARNINGS in dmesg during boot.
dmesg | grep "cut here" -A 1
[ 5.916356] ------------[ cut here ]------------
[ 5.916450] WARNING: CPU: 0 PID: 47 at /build/linux-IIZPYL/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12147 intel_atomic_check+0x307/0x6d0 [i915]()
--
[ 5.917586] ------------[ cut here ]------------
[ 5.917661] WARNING: CPU: 0 PID: 47 at /build/linux-IIZPYL/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11695 intel_plane_atomic_calc_changes+0x549/0x6b0 [i915]()
--
[ 5.996083] ------------[ cut here ]------------
[ 5.996176] WARNING: CPU: 0 PID: 47 at /build/linux-IIZPYL/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12724 intel_modeset_check_state+0x556/0x910 [i915]()
--
[ 6.100769] ------------[ cut here ]------------
[ 6.100853] WARNING: CPU: 0 PID: 47 at /build/linux-IIZPYL/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12147 intel_atomic_check+0x307/0x6d0 [i915]()
--
[ 6.336057] ------------[ cut here ]------------
[ 6.336151] WARNING: CPU: 0 PID: 47 at /build/linux-IIZPYL/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12724 intel_modeset_check_state+0x556/0x910 [i915]()
--
[ 6.338439] ------------[ cut here ]------------
[ 6.338516] WARNING: CPU: 0 PID: 47 at /build/linux-IIZPYL/linux-4.4.0/drivers/gpu/drm/i915/intel_fbdev.c:406 intel_fb_initial_config+0x2e4/0x5f0 [i915]()
--
[ 6.342397] ------------[ cut here ]------------
[ 6.342413] WARNING: CPU: 0 PID: 47 at /build/linux-IIZPYL/linux-4.4.0/drivers/gpu/drm/drm_atomic_helper.c:682 drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]()

Happens also with mainline kernel 4.4.1-040401-generic.

Doesn't happen with mainline kernel 4.2.0-040200-generic.
---
ApportVersion: 2.20-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: user 1021 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=67704630-8b83-4442-92fe-7cfeb6200110
InstallationDate: Installed on 2016-02-15 (3 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160214)
MachineType: FUJITSU SIEMENS LIFEBOOK P1610
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   product info: "OMNIKEY
 ", "CardMan 4040
 ", "", ""
   manfid: 0x0223, 0x0200
PccardctlStatus:
 Socket 0:
   5.0V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "cm4040_cs"
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic root=UUID=1756610f-00c1-4886-b55d-e842ffdf62e4 ro nosplash
ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-4-generic N/A
 linux-backports-modules-4.4.0-4-generic N/A
 linux-firmware 1.155
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-4-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/02/2007
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.13
dmi.board.name: FJNB1C5
dmi.board.vendor: FUJITSU
dmi.board.version: CP307305-01
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: P16__
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.13:bd04/02/2007:svnFUJITSUSIEMENS:pnLIFEBOOKP1610:pvr:rvnFUJITSU:rnFJNB1C5:rvrCP307305-01:cvnFUJITSUSIEMENS:ct10:cvrP16__:
dmi.product.name: LIFEBOOK P1610
dmi.sys.vendor: FUJITSU SIEMENS

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 1547204

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
Aapo Rantalainen (aapo-rantalainen) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : CRDA.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : IwConfig.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : JournalErrors.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : Lspci.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : Lsusb.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : ProcEnviron.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : ProcModules.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : PulseList.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : UdevDb.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : WifiSyslog.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote :
Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote :
tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.5 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.5-rc4-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
Changed in linux (Ubuntu Xenial):
status: Confirmed → Incomplete
penalvch (penalvch)
tags: added: bios-outdated-1.15
Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote :

I haven't run older Ubuntu on this machine.

Warnings don't happen with mainline kernel 4.2.0-040200-generic.

Upgrading BIOS (from 1.13 to 1.15) didn't help.

With mainline kernel 4.5: only two warnings: dmesg | grep "cut here" -A 1
[ 8.852365] ------------[ cut here ]------------
[ 8.852476] WARNING: CPU: 0 PID: 75 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_fbdev.c:412 intel_fb_initial_config+0x2e4/0x600 [i915]()
--
[ 8.855788] ------------[ cut here ]------------
[ 8.855807] WARNING: CPU: 0 PID: 75 at /home/kernel/COD/linux/drivers/gpu/drm/drm_atomic_helper.c:715 drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]()

description: updated
Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : JournalErrors.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : ProcEnviron.txt

apport information

Changed in linux (Ubuntu Xenial):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Aapo Rantalainen:
1) You don't need to apport-collect any further unless specifically requested to do so.
2) Please provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
3) To keep this relevant to upstream, could you please test the latest mainline kernel (4.7-rc6) and advise to the results?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
description: updated
Revision history for this message
David Dombrowsky (davek) wrote :

This bug shows up every time I boot linux on this laptop.

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
68YGU Ver. F.07
07/28/2006

Text of the error, from dmesg:

Mar 11 16:46:13 lappy kernel: [ 3.260587] WARNING: CPU: 0 PID: 170 at /build/linux-Nasqxe/linux-4.4.0/drivers/gpu/drm/drm_atomic_helper.c:723 drm_at
omic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]()
Mar 11 16:46:13 lappy kernel: [ 3.260599] Modules linked in: i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci b44
 drm psmouse ssb libahci pata_acpi mii wmi fjes video
Mar 11 16:46:13 lappy kernel: [ 3.260603] CPU: 0 PID: 170 Comm: kworker/u4:6 Tainted: G W 4.4.0-66-generic #87-Ubuntu
Mar 11 16:46:13 lappy kernel: [ 3.260604] Hardware name: Hewlett-Packard HP Compaq nx7400 (RB525UT#ABA)/30A2, BIOS 68YGU Ver. F.07 07/28/2006

I'm not sure what this is breaking in the system.

Revision history for this message
penalvch (penalvch) wrote :

David Dombrowsky, it will help immensely if you filed a new report with Ubuntu, using the default repository kernel (not mainline/upstream/3rd party) 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
David Dombrowsky (davek) wrote :
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.