[Kernel-packages] [Bug 1234232] Re: check_crtc_state: pipe state doesn't match!

2013-12-09 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1234232] Re: check_crtc_state: pipe state doesn't match!

2013-10-10 Thread Ralf Hildebrandt
Which previous kernel do you have in mind? Something from raring? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1234232 Title: check_crtc_state: pipe state doesn't match! Status in

[Kernel-packages] [Bug 1234232] Re: check_crtc_state: pipe state doesn't match!

2013-10-10 Thread Ralf Hildebrandt
I'll boot into 3.8.x from raring and see what's going on there -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1234232 Title: check_crtc_state: pipe state doesn't match! Status in

[Kernel-packages] [Bug 1234232] Re: check_crtc_state: pipe state doesn't match!

2013-10-10 Thread Joseph Salisbury
You mentioned this started happening in a recent kernel. Did this happen in earlier Saucy kernels? Basically we would like to know what was the last good version and first bad version, then we can perform a kernel bisect. -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1234232] Re: check_crtc_state: pipe state doesn't match!

2013-10-02 Thread Ralf Hildebrandt
Seems to be happening quite a lot: [5.127523] WARNING: CPU: 1 PID: 457 at /build/buildd/linux-3.11.0/drivers/gpu/drm/i915/intel_display.c:8292 check_crtc_state+0x58f/0x9c0 [i915]() [7.336903] WARNING: CPU: 0 PID: 202 at

[Kernel-packages] [Bug 1234232] Re: check_crtc_state: pipe state doesn't match!

2013-10-02 Thread Joseph Salisbury
Does this issue go away if you boot back into the previous kernel? ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Tags added: regression-update ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Tags added: kernel-da-key -- You received this bug