Bug 64513

Summary: [HSW] Booting up with Call Trace
Product: DRI Reporter: shui yangwei <yangweix.shui>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: major    
Priority: medium CC: przanoni
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg: booting up with call trace none

Description shui yangwei 2013-05-13 03:26:17 UTC 
Created attachment 79222 [details]
dmesg: booting up with call trace

Environment:
--------------------------
Kernel: (drm-intel-next-queued)e2e3de90ee465ae8fffb8095b85c2bdd322c74f7
Some additional commit info:
Author: Paulo Zanoni <paulo.r.zanoni@intel.com>
Date:   Wed Apr 17 18:15:49 2013 -0300

    drm/i915: implement WADPOClockGatingDisable for LPT

Description:
--------------------------
After our HSW machine's BIOS updated, I find our kernel booting up with call trace, We can scan it from dmesg.

BIOS:
--------------------------
Version: HSWLPTU1.86C.0124.R02.1305030131

lspci:
--------------------------
00:02.0 VGA compatible controller: Intel Corporation Device 0d26 (rev 08)
Comment 1 Paulo Zanoni 2013-05-14 14:46:58 UTC 
Hi

Does this result in any black screens or other problems besides the error messages?

Which outputs are plugged when you boot the machine?

When booting, can you see the BIOS screen on your monitor?

Thanks,
Paulo
Comment 2 shui yangwei 2013-05-15 08:05:35 UTC 
(In reply to comment #1)
> Hi
> 
> Does this result in any black screens or other problems besides the error
> messages?
> 
> Which outputs are plugged when you boot the machine?
> 
> When booting, can you see the BIOS screen on your monitor?
> 
> Thanks,
> Paulo

Today I suddenly find the call trace disappeared on top -next-queued kernel. I think now it's fixed, and we can close this bug.
Comment 3 Elizabeth 2017-10-06 14:46:26 UTC 
Closing old verified.

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.