[solved with 4.0] Kernel 3.19 & Intel graphics

[orinoco]

Hello,

after installing the lated kernel I found the attached message repeated many times. I saw a thread on lkml dealing with this topic. At the moment I can't see any resulting problem. I hope there will be a fix quite soon.

Code: [Select]

Feb 13 13:52:18 note kernel: ------------[ cut here ]------------
Feb 13 13:52:18 note kernel: WARNING: CPU: 0 PID: 851 at /tmp/buildd/linux-siduction-3.19/drivers/gpu/drm/drm_irq.c:1121 drm_wait_one_vblank+0x3b/0x167 [drm]()
Feb 13 13:52:18 note kernel: vblank not available on crtc 0, ret=-22
Feb 13 13:52:18 note kernel: Modules linked in: uas usb_storage rfcomm ctr ccm af_packet pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) cpufreq_powersave cpufreq_stats cpufreq_conservative bnep nfsd auth_rpcgss nfs_acl nfs lockd grace fscache sunrpc joydev iTCO_wdt iTCO_vendor_support dell_wmi sparse_keymap dell_laptop dcdbas btusb bluetooth i8k coretemp kvm_intel arc4 kvm evdev psmouse pcspkr serio_raw i2c_i801 b43 i915 snd_hda_codec_idt i2c_algo_bit bcma snd_hda_codec_generic mac80211 yenta_socket pcmcia_rsrc drm_kms_helper lpc_ich snd_hda_intel cfg80211 snd_hda_controller rfkill ssb_hcd rng_core snd_hda_codec 8250_fintek drm wmi video snd_hwdep snd_pcm i2c_core ac snd_timer button snd intel_agp soundcore acpi_cpufreq battery intel_gtt processor loop fuse parport_pc ppdev lp parport autofs4 ext4 crc16
Feb 13 13:52:18 note kernel:  jbd2 mbcache crc32c_generic btrfs xor raid6_pq xts gf128mul algif_skcipher af_alg hid_generic usbhid hid dm_crypt dm_mod md_mod sg sd_mod sr_mod cdrom ata_generic pata_acpi ahci firewire_ohci libahci ata_piix libata firewire_core crc_itu_t scsi_mod tg3 ptp pps_core ssb mmc_core pcmcia pcmcia_core thermal uhci_hcd ehci_pci ehci_hcd usbcore usb_common
Feb 13 13:52:18 note kernel: CPU: 0 PID: 851 Comm: systemd-logind Tainted: G        W  O   3.19-0.towo-siduction-amd64 #1
Feb 13 13:52:18 note kernel: Hardware name: Dell Inc. Latitude D830                   /0HN341, BIOS A17 06/19/2013
Feb 13 13:52:18 note kernel:  0000000000000000 0000000000000009 ffffffff813c9d71 ffff880214eb79d8
Feb 13 13:52:18 note kernel:  ffffffff810428d1 ffffffff81001786 ffffffffa04d4bdf ffff8800d68c97f0
Feb 13 13:52:18 note kernel:  ffff8802151d0000 0000000000000000 0000000000006014 ffff880214cf1000
Feb 13 13:52:18 note kernel: Call Trace:
Feb 13 13:52:18 note kernel:  [<ffffffff813c9d71>] ? dump_stack+0x4a/0x74
Feb 13 13:52:18 note kernel:  [<ffffffff810428d1>] ? warn_slowpath_common+0x93/0xab
Feb 13 13:52:18 note kernel:  [<ffffffff81001786>] ? __switch_to+0x296/0x4a3
Feb 13 13:52:18 note kernel:  [<ffffffffa04d4bdf>] ? drm_wait_one_vblank+0x3b/0x167 [drm]
Feb 13 13:52:18 note kernel:  [<ffffffff8104292e>] ? warn_slowpath_fmt+0x45/0x4a
Feb 13 13:52:18 note kernel:  [<ffffffffa04d4bdf>] ? drm_wait_one_vblank+0x3b/0x167 [drm]
Feb 13 13:52:18 note kernel:  [<ffffffff813cd7e5>] ? _raw_spin_lock_irqsave+0x18/0x57
Feb 13 13:52:18 note kernel:  [<ffffffff8105ddef>] ? get_parent_ip+0x9/0x1b
Feb 13 13:52:18 note kernel:  [<ffffffffa06118bd>] ? intel_enable_tv+0x1c/0x53 [i915]
Feb 13 13:52:18 note kernel:  [<ffffffffa05e660d>] ? i9xx_crtc_enable+0x359/0x3bd [i915]
Feb 13 13:52:18 note kernel:  [<ffffffffa05e5f60>] ? __intel_set_mode+0x85b/0x96a [i915]
Feb 13 13:52:18 note kernel:  [<ffffffffa05ea6df>] ? intel_set_mode+0x65/0x86 [i915]
Feb 13 13:52:18 note kernel:  [<ffffffffa05eaaa1>] ? intel_get_load_detect_pipe+0x3a1/0x416 [i915]
Feb 13 13:52:18 note kernel:  [<ffffffff8105ddef>] ? get_parent_ip+0x9/0x1b
Feb 13 13:52:18 note kernel:  [<ffffffff8105de6f>] ? preempt_count_add+0x6e/0x80
Feb 13 13:52:18 note kernel:  [<ffffffff8116b217>] ? kernfs_put_active+0x9/0x33
Feb 13 13:52:18 note kernel:  [<ffffffff8116c642>] ? kernfs_fop_open+0x219/0x2b4
Feb 13 13:52:18 note kernel:  [<ffffffffa06121bd>] ? intel_tv_detect+0x121/0x45e [i915]
Feb 13 13:52:18 note kernel:  [<ffffffffa04d8dec>] ? status_show+0x33/0x6d [drm]
Feb 13 13:52:18 note kernel:  [<ffffffff81296d3b>] ? dev_attr_show+0x1e/0x46
Feb 13 13:52:18 note kernel:  [<ffffffff8116bae4>] ? kernfs_seq_start+0x31/0x7c
Feb 13 13:52:18 note kernel:  [<ffffffff8116cb90>] ? sysfs_kf_seq_show+0x7b/0xc6
Feb 13 13:52:18 note kernel:  [<ffffffff811336b8>] ? seq_read+0x15a/0x312
Feb 13 13:52:18 note kernel:  [<ffffffff8111a40b>] ? vfs_read+0x7e/0xb6
Feb 13 13:52:18 note kernel:  [<ffffffff8111a488>] ? SyS_read+0x45/0x70
Feb 13 13:52:18 note kernel:  [<ffffffff813cdc2d>] ? system_call_fastpath+0x16/0x1b
Feb 13 13:52:18 note kernel: ---[ end trace dfd61c8260f86803 ]---

[towo]

Try using xserver-xorg-video-intel from experiemntal.

[orinoco]

No improvement, even with the latest kernel (3.19-0.towo.2-siduction-amd64).

[seasons]

https://bugs.freedesktop.org/show_bug.cgi?id=89108
https://bugs.freedesktop.org/show_bug.cgi?id=89209

[orinoco]

No progress. Still the same messages.

Code: [Select]

Linux tuxor2 3.19.3-towo.1-siduction-amd64 #1 SMP PREEMPT siduction 3.19-9 (2015-03-26) x86_64 GNU/Linux


[musca]

Hello orinoco,

debian refused to step up to the latest driver from intel since almost two years, because it wasn't released as stable by intel. Two weeks ago towo has suggested to try the latest from experimental repo, but you only mentioned updating the kernel since.

apt-cache policy xserver-xorg-video-intel
xserver-xorg-video-intel:
  Installed: 2:2.21.15-2+b2
  Candidate: 2:2.21.15-2+b2
  Version table:
     2:2.99.917-1~exp1 0
          1 http://ftp2.de.debian.org/debian/ experimental/main amd64 Packages
 *** 2:2.21.15-2+b2 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status

Did you try version 2.99 from debian experimental?

greetings
musca

[orinoco]

Did you try version 2.99 from debian experimental?

Yes I did.

Code: [Select]

$ LANG=c apt-cache policy xserver-xorg-video-intel
xserver-xorg-video-intel:
  Installed: 2:2.99.917-1~exp1
  Candidate: 2:2.99.917-1~exp1
  Version table:
 *** 2:2.99.917-1~exp1 0
        100 /var/lib/dpkg/status
     2:2.21.15-2+b2 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages

[seasons]

Did you try version 2.99 from debian experimental?

You're referring to intel DDX driver (xserver-xorg-video-intel), but the problem seems to be in the kernel module.

Until upstream intel devs fix it, I don't think there is much you can do except go back to a 3.18 kernel.

[orinoco]

To close this issue: Kernel 4.0 solved it. No more syslog flooding.