Bug 111508 - drm_vblank trace on startup - kernel-5.2.10
Summary: drm_vblank trace on startup - kernel-5.2.10
Status: NEEDINFO
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: Triaged
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-28 14:33 UTC by William
Modified: 2019-09-06 11:26 UTC (History)
1 user (show)

See Also:
i915 platform: SKL
i915 features:


Attachments
Extract from dmesg showing traces (9.81 KB, text/plain)
2019-08-28 14:33 UTC, William
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description William 2019-08-28 14:33:02 UTC
Created attachment 145191 [details]
Extract from dmesg showing traces

Three traces during boot up (before networking start up and well before
X windows was started). Subsequently there was a slow response to keyboard
inputs most of the time, though the system was just usable with patience.

CPU usage was normal and the display appeared normal.

There was one further trace later on.

After a reboot everything was ok. I had installed linux-5.2.10 three days
earlier and had no previous problem. I cannot reproduce the bug.

------------------------------------
Hardware:
  Asus P7H55-M SI with Intel Core i5 processor
  and Integrated Graphics [i915 driver].
Currently using a keyboard connected to a PS/2 keyboard port and using a
USB connected mouse.
Distro: Slackware-14.1, but with newer kernel.
------------------------------------
Comment 1 Lakshmi 2019-08-29 08:28:28 UTC
We had this issue on our system (HSW) but not seen for the last 3 months. Can you please verify the issue with Drmtip? (https://cgit.freedesktop.org/drm-tip)
Btw which platform is this? 

If the issue appears on drmtip, please attach the dmesg from boot with kernel parameters drm.debug=0x1e log_buf_len=4M.
Comment 2 William 2019-08-31 15:35:15 UTC
The processor is an Intel Core i5-650

I have added the suggested debug to the boot command line.

Using drmtip is a bit beyond my skills.
Comment 3 Lakshmi 2019-09-02 13:30:04 UTC
(In reply to William from comment #2)
> The processor is an Intel Core i5-650
> 
> I have added the suggested debug to the boot command line.
> 
> Using drmtip is a bit beyond my skills.

Attached dmesg is not complete from boot. so could not find which kernel is the dmesg from. If the issue is not reproducible with 5.2.10, are you expecting a fix for the older kernel (back port)?
Comment 4 William 2019-09-03 20:05:57 UTC
It was kernel 5.2.10 I was using at the time of the traces.

This looks like one of those infrequent happenings. I was reporting it
more as an observation (ie, I am not in a rush for a bug fix).

I have not seen it again since my original report.
Comment 5 Lakshmi 2019-09-06 11:26:14 UTC
Since we are not seeing this issue on our systems anymore. I recommend you to upgrade the kernel to latest and see if you can reproduce the issue.

Otherwise we can close this issue as WORKSFORME.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.