Re: [drm2][panic] Running XOrg with SNA enabled causes system panic after few hours on G33

From: Ruslan Makhmatkhanov <cvs-src_at_yandex.ru>
Date: Mon, 17 Jun 2013 22:39:13 +0400
I have this problem from the beginning (more than year now), I already 
wrote about that on current_at_ some time ago. The problem is that it 
appears sporadically (but always in not very suitable moment) and I 
can't see anything on terminal, so it's hard to debug/complain.

So I just updated to r251845, applied the Konstantin's patch and rebuild 
world/kernel. Sadly nothing changed this time. I boot into X11,
then shut it down from the gnome menu, waiting for 15 minutes of blank 
screen. Nothing happens. Then doing my everyday procedure: powering it 
down by pressing a button, then usual full fsck (journaling fails) in 
single mode and reboot.

Artyom Mirgorodskiy wrote on 17.06.2013 16:43:
> My laptop can shutdown after this patch, however I receive the following messages:
>
> Jun 17 09:34:03 notebook kernel: error: [drm:pid12:i915_hangcheck_ring_idle] *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 7438, at 7438], missed IRQ?
> Jun 17 09:36:08 notebook kernel: error: [drm:pid12:i915_hangcheck_ring_idle] *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 11914, at 11914], missed IRQ?
> Jun 17 09:45:03 notebook kernel: error: [drm:pid12:i915_hangcheck_ring_idle] *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 69315, at 69315], missed IRQ?
> Jun 17 09:45:45 notebook kernel: error: [drm:pid12:i915_hangcheck_ring_idle] *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 72243, at 72243], missed IRQ?

And I have no that guys in my log files. Only this at booting:

Jun 17 22:27:47 smeshariki4 kernel: info: [drm] Supports vblank 
timestamp caching Rev 1 (10.10.2010).
Jun 17 22:27:47 smeshariki4 kernel: info: [drm] Driver supports precise 
vblank timestamp query.
Jun 17 22:27:47 smeshariki4 kernel: info: [drm] Enabling RC6 states: RC6 
off, RC6p off, RC6pp off
Jun 17 22:27:47 smeshariki4 kernel: drmn1: taking over the fictitious 
range 0xc0000000-0xd0000000
Jun 17 22:27:47 smeshariki4 kernel: info: [drm] GMBUS timed out, falling 
back to bit banging on pin 7 [gmbus bus dpd]
Jun 17 22:27:47 smeshariki4 kernel: info: [drm] Initialized i915 1.6.0 
20080730

Any suggestions?

>
>
> On Sunday 16 June 2013 17:27:49 Konstantin Belousov wrote:
>> On Sun, Jun 16, 2013 at 06:04:39PM +0400, Oleg Sidorkin wrote:
>>> Thanks for the patch.
>>> I've adapted the proposed patch for stable/9 and it is running with
>>> SNA enabled now.
>>
>> In other words, your problem seems to be gone with the patch applied ?
>>
>>>
>>> On Sat, Jun 15, 2013 at 11:54 PM, Artyom Mirgorodskiy
>>> <artyom.mirgorodsky_at_gmail.com> wrote:
>>>> I can't apply patch
>>>>
>>>>
>>>>
>>>> On Saturday 15 June 2013 21:48:08 Konstantin Belousov wrote:
>>>>
>>>>> On Sat, Jun 15, 2013 at 09:46:02PM +0300, Artyom Mirgorodskiy wrote:
>>>>
>>>>>> Can you please also create patch for -current?
>>>>
>>>>> It is for current. Code in stable/9 should be identical though.


-- 
Regards,
Ruslan

Tinderboxing kills... the drives.
Received on Mon Jun 17 2013 - 16:39:34 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:38 UTC