Bug 61158

Summary: [ILK] System hang while running testdisplay to mode 1280x800
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: critical    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Bug Depends on: 45729    
Bug Blocks:    
Attachments:
Description Flags
netconsole.log none

Description shui yangwei 2013-02-20 08:28:15 UTC 
Created attachment 75163 [details]
netconsole.log

Environment:
---------------------------
Kernel: (drm-intel-next-queued)bc555a2f669e3386223ba545abba5b2fd0c73d04
Some additional commit info:
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date:   Tue Feb 19 12:11:38 2013 -0800

    drm/i915: don't restore LVDS enable state blindly v2

Description:
---------------------------
System will be hang, while it's running to mode 1280x800. I tested many times, this issue can be reproduced stably. I have appended netconsole.log in attachment.

CRTS(3):[39]  1280x800 75 1280 1360 1488 1696 800 803 809 838 0x6 0x40 106500

Reducing step:
---------------------------
1. ./testdisplay -a -s 10
Comment 1 Daniel Vetter 2013-02-20 11:03:18 UTC 
Usual pack of questions:
- Is this a regression?
- Is the system completely dead (network ping, ...)?
- Does the crash only happen when you test a specific output configuration with testdisplay (i.e. specify the mode on the cmdline), or do you just need to run it for a while?

The WARN in the netconsole output is a duplicate of bug #54687
Comment 2 shui yangwei 2013-02-20 11:20:00 UTC 
(In reply to comment #1)
> Usual pack of questions:
> - Is this a regression?
> - Is the system completely dead (network ping, ...)?
It's completely dead, the machine is unreachable.
> - Does the crash only happen when you test a specific output configuration
> with testdisplay (i.e. specify the mode on the cmdline), or do you just need
> to run it for a while?
> 
> The WARN in the netconsole output is a duplicate of bug #54687

I find this bug in this round biweekly testing, It might be a regression, and I will give you a detail description tomorrow. If you need more information, please let me know.
Comment 3 shui yangwei 2013-02-21 06:07:10 UTC 
Description:
------------------------
I can't find a good commit. Isolated to run the mode below for a few times, may be one or three or more, this issue will come up.

[38]  1280x800 85 1280 1360 1496 1712 800 803 809 843 0x6 0x40 122500

Reproduce step:
------------------------
./testdisplay -o 14,38 (single running this mode)
Comment 4 Chris Wilson 2013-05-08 15:44:05 UTC 
Is this hard hang still reproducible?
Comment 5 shui yangwei 2013-05-10 07:00:17 UTC 
(In reply to comment #4)
> Is this hard hang still reproducible?

Now I can't find the mode by checking ./testdisplay -i. This bug is there for a long time that there's no person response. I think it could closed now, and we will report new bug if there's any issues come up again.
Comment 6 Elizabeth 2017-10-06 14:46:54 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.