Kernel freezes after drm_wait_one_vblank timed out

Bug #1580697 reported by Klaus Bielke
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Using kernel 4.4.0 from Ubuntu GNOME 16.04 I get a lot of warnings 'drm_wait_one_vblank timed out' while booting and every time when I switch user or session via Alt-Fn. Example logs will be attached, I used this for saving the log:

journalctl -b --system --no-pager |tee bootlog-$(uname -r)-$(lsb_release -sr)

I suspect this may be related to some of my problems (slow switch, freeze, wrong VT: Alt-Fn6 roots to tty3) when switching virtual terminal.

I see these messages on 16.04 or 14.04 when using kernel 4.4.0-21-generic, 4.4.0-22-generic or mainline kernel 4.4.0-040400-generic or 4.5.2-040502-generic, but mainline kernel 4.3.6-040306-generic does not throw this message and there are no problems with 4.3.6 while switching VT.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: k2 1475 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=8e0701ee-0c76-4396-bdd9-f406da205c7b
InstallationDate: Installed on 2016-03-31 (41 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta i386 (20160323.1)
MachineType: FUJITSU SIEMENS LIFEBOOK E8310
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=5811fae8-2bd0-46c0-a1b3-4bd8b9f2c821 ro
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic N/A
 linux-firmware 1.157
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-22-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/27/2007
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.10
dmi.board.name: FJNB1CE
dmi.board.vendor: FUJITSU
dmi.board.version: 1PCP331350-03
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: E8310
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd12/27/2007:svnFUJITSUSIEMENS:pnLIFEBOOKE8310:pvr:rvnFUJITSU:rnFJNB1CE:rvr1PCP331350-03:cvnFUJITSUSIEMENS:ct10:cvrE8310:
dmi.product.name: LIFEBOOK E8310
dmi.sys.vendor: FUJITSU SIEMENS

Revision history for this message
Klaus Bielke (k-bielke) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1580697/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → linux (Ubuntu)
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 1580697

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
Klaus Bielke (k-bielke) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Klaus Bielke (k-bielke) wrote : CRDA.txt

apport information

Revision history for this message
Klaus Bielke (k-bielke) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Klaus Bielke (k-bielke) wrote : IwConfig.txt

apport information

Revision history for this message
Klaus Bielke (k-bielke) wrote : JournalErrors.txt

apport information

Revision history for this message
Klaus Bielke (k-bielke) wrote : Lspci.txt

apport information

Revision history for this message
Klaus Bielke (k-bielke) wrote : Lsusb.txt

apport information

Revision history for this message
Klaus Bielke (k-bielke) wrote : PccardctlIdent.txt

apport information

Revision history for this message
Klaus Bielke (k-bielke) wrote : PccardctlStatus.txt

apport information

Revision history for this message
Klaus Bielke (k-bielke) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Klaus Bielke (k-bielke) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Klaus Bielke (k-bielke) wrote : ProcModules.txt

apport information

Revision history for this message
Klaus Bielke (k-bielke) wrote : PulseList.txt

apport information

Revision history for this message
Klaus Bielke (k-bielke) wrote : UdevDb.txt

apport information

Revision history for this message
Klaus Bielke (k-bielke) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
oleg (overlayfs) wrote :
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.6 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.6-rc7-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Klaus Bielke (k-bielke) wrote :

@20: Bootet with mainline kernel 4.6-rc7
(uname -rv says: 4.6.0-040600rc7-generic #201605081830 SMP Sun May 8 22:48:45 UTC 2016 ).

Still same behavior as with kernel 4.4.0:
Messages 'vblank wait timed out' present in bootlog, see appended file.
Every user/session switch (Crtl-Alt-Fn) to a X11-screen generates 3 of these messages.
VT-switch to an non X11-screen does not produce these messages.

Need time for testing, if freeze still occures.

tags: added: kernel-bug-exists-upstreamtrusty
removed: trusty
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Klaus Bielke (k-bielke) wrote :

@19:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1542939/comments/20 states that bug 1542939 is fixed in kernel version 4.5.
I still see this bug (#1580697) when I run a mainstream kernel 4.5 or 4.6, so I suspect it is not a duplicate.

penalvch (penalvch)
tags: added: bios-outdated-1.16 kernel-bug-exists-upstream kernel-bug-exists-upstream-4.6-rc7
removed: 4.4.0 kernel-bug-exists-upstreamtrusty
tags: added: needs-bisect regression-release
Revision history for this message
Giorgio Vazzana (mywing) 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.