Re: [drm2][panic] Running XOrg with SNA enabled causes system panic after few hours on G33
Unfortunately log is empty as a well as a lot of user files :( because of fsck. On Friday 21 June 2013 01:45:33 Oleg Sidorkin wrote: Check the logs for messages that can help to investigate the problem. If there is nothing helpful, I have no idea but to configure a serial console and see if there is something that helps to understand the problem. -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [drm2][panic] Running XOrg with SNA enabled causes system panic after few hours on G33
On Wed, Jun 19, 2013 at 5:27 PM, Artyom Mirgorodskiy artyom.mirgorod...@gmail.com wrote: Hm, yesterday I turn off SNA optimization and got hang when shutdown :( Check the logs for messages that can help to investigate the problem. If there is nothing helpful, I have no idea but to configure a serial console and see if there is something that helps to understand the problem. On Wednesday 19 June 2013 00:25:55 Konstantin Belousov wrote: On Wed, Jun 19, 2013 at 01:11:19AM +0400, Oleg Sidorkin wrote: On Sun, Jun 16, 2013 at 6:27 PM, Konstantin Belousov kostik...@gmail.com 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 ? Now 48h are passed without panics. Fix definitely works. Thanks. Thank you. I tested it locally (without SNA) and committed the change a hour ago. It is required anyway, since the race sounds possible. I was mostly concerned with a thinko in the logic. -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [drm2][panic] Running XOrg with SNA enabled causes system panic after few hours on G33
Hm, yesterday I turn off SNA optimization and got hang when shutdown :( On Wednesday 19 June 2013 00:25:55 Konstantin Belousov wrote: On Wed, Jun 19, 2013 at 01:11:19AM +0400, Oleg Sidorkin wrote: On Sun, Jun 16, 2013 at 6:27 PM, Konstantin Belousov kostik...@gmail.com 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 ? Now 48h are passed without panics. Fix definitely works. Thanks. Thank you. I tested it locally (without SNA) and committed the change a hour ago. It is required anyway, since the race sounds possible. I was mostly concerned with a thinko in the logic. -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [drm2][panic] Running XOrg with SNA enabled causes system panic after few hours on G33
On Sun, Jun 16, 2013 at 6:27 PM, Konstantin Belousov kostik...@gmail.com 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 ? Now 48h are passed without panics. Fix definitely works. Thanks. On Sat, Jun 15, 2013 at 11:54 PM, Artyom Mirgorodskiy artyom.mirgorod...@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. -- Artyom Mirgorodskiy -- Oleg Sidorkin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [drm2][panic] Running XOrg with SNA enabled causes system panic after few hours on G33
On Wed, Jun 19, 2013 at 01:11:19AM +0400, Oleg Sidorkin wrote: On Sun, Jun 16, 2013 at 6:27 PM, Konstantin Belousov kostik...@gmail.com 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 ? Now 48h are passed without panics. Fix definitely works. Thanks. Thank you. I tested it locally (without SNA) and committed the change a hour ago. It is required anyway, since the race sounds possible. I was mostly concerned with a thinko in the logic. pgpMV29_6P8LH.pgp Description: PGP signature
Re: [drm2][panic] Running XOrg with SNA enabled causes system panic after few hours on G33
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? 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.mirgorod...@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. -- Artyom Mirgorodskiy -- Oleg Sidorkin -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [drm2][panic] Running XOrg with SNA enabled causes system panic after few hours on G33
I have this problem from the beginning (more than year now), I already wrote about that on current@ 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 0xc000-0xd000 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.mirgorod...@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. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [drm2][panic] Running XOrg with SNA enabled causes system panic after few hours on G33
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.mirgorod...@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. -- Artyom Mirgorodskiy -- Oleg Sidorkin pgpplxLIj_vWD.pgp Description: PGP signature
Re: [drm2][panic] Running XOrg with SNA enabled causes system panic after few hours on G33
Thanks for the patch. I've adapted the proposed patch for stable/9 and it is running with SNA enabled now. On Sat, Jun 15, 2013 at 11:54 PM, Artyom Mirgorodskiy artyom.mirgorod...@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. -- Artyom Mirgorodskiy -- Oleg Sidorkin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [drm2][panic] Running XOrg with SNA enabled causes system panic after few hours on G33
Seems to be yes. But I will be sure after 48h of uptime in KDE without panics. On Sun, Jun 16, 2013 at 6:27 PM, Konstantin Belousov kostik...@gmail.com 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.mirgorod...@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. -- Artyom Mirgorodskiy -- Oleg Sidorkin -- Oleg Sidorkin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [drm2][panic] Running XOrg with SNA enabled causes system panic after few hours on G33
Can you please also create patch for -current?
On Saturday 15 June 2013 08:17:46 Konstantin Belousov wrote:
On Fri, Jun 14, 2013 at 10:16:15AM +0300, Artyom Mirgorodskiy wrote:
Thank you! This patch also solve my issue (unable shutdown):
http://lists.freebsd.org/pipermail/freebsd-current/2013-May/042011.html
On Tuesday 11 June 2013 12:34:16 Oleg Sidorkin wrote:
Hello.
I'm running recent 9.1/stable with the recent XOrg on the system with
G33 chipset.
My pciconf -lvb output is here: http://pastebin.com/LDzKzf1i
If I add
Option AccelMethod sna
to my xorg.conf system panics after few hours:
(kgdb) bt
#0 doadump (textdump=value optimized out)
at /usr/src/sys/kern/kern_
shutdown.c:272
#1 0x8050a19f in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:449
#2 0x8050a6a3 in panic (fmt=0x104 Address 0x104 out of bounds)
at /usr/src/sys/kern/kern_shutdown.c:637
#3 0x80765f77 in vm_page_insert (m=0xfe0226126b50,
object=0xfe0208de8488, pindex=3) at /usr/src/sys/vm/vm_page.c:914
#4 0x814a889d in i915_gem_pager_fault (vm_obj=0xfe0208de8488,
offset=3, prot=value optimized out, mres=0xff824705b680)
at
/usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/i915_gem.c:1429
#5 0x80747fe3 in dev_pager_getpages (object=0xfe0208de8488,
ma=0xff824705b680, count=1, reqpage=value optimized out)
at /usr/src/sys/vm/device_pager.c:260
#6 0x80754bb6 in vm_fault_hold (map=0xfe000c247188,
vaddr=34458505216, fault_type=2 '\002', fault_flags=0, m_hold=0x0)
at vm_pager.h:128
#7 0x80756ca3 in vm_fault (map=0xfe000c247188,
vaddr=34458505216,
fault_type=value optimized out, fault_flags=0)
at /usr/src/sys/vm/vm_fault.c:229
#8 0x8078e01f in trap_pfault (frame=0xff824705bc40,
usermode=1)
at /usr/src/sys/amd64/amd64/trap.c:762
#9 0x8078e864 in trap (frame=0xff824705bc40)
(kgdb) bt full
#0 doadump (textdump=value optimized out)
at /usr/src/sys/kern/kern_shutdown.c:272
No locals.
#1 0x8050a19f in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:449
_ep = (struct eventhandler_entry *) 0x0
_el = (struct eventhandler_list *) 0xfe0009c7f700
first_buf_printf = 1
#2 0x8050a6a3 in panic (fmt=0x104 Address 0x104 out of bounds)
at /usr/src/sys/kern/kern_shutdown.c:637
td = (struct thread *) 0x0
bootopt = value optimized out
newpanic = value optimized out
ap = {{gp_offset = 8, fp_offset = 48,
overflow_arg_area = 0xff824705b570,
reg_save_area = 0xff824705b490}}
panic_cpu = 3
buf = vm_page_insert: page already inserted, '\0' repeats 218
times
#3 0x80765f77 in vm_page_insert (m=0xfe0226126b50,
object=0xfe0208de8488, pindex=3) at /usr/src/sys/vm/vm_page.c:914
root = 0x0
#4 0x814a889d in i915_gem_pager_fault (vm_obj=0xfe0208de8488,
offset=3, prot=value optimized out, mres=0xff824705b680)
(kgdb) up 4
#4 0x814a889d in i915_gem_pager_fault (vm_obj=0xfe0208de8488,
offset=3, prot=value optimized out, mres=0xff824705b680)
at
/usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/i915_gem.c:1429
1429vm_page_insert(m, vm_obj, OFF_TO_IDX(offset));
(kgdb) p vm_obj
$1 = 0xfe0208de8488
(kgdb) p m-object
$2 = 0xfe0208de8488
It works fine for weeks without Option AccelMethod sna.
I replaced
vm_page_insert(m, vm_obj, OFF_TO_IDX(offset));
with the code
if (m-object==NULL){
vm_page_insert(m, vm_obj, OFF_TO_IDX(offset));
}
else{
if(m-object!=vm_obj)
panic(i915_gem_pager_fault: tried to assign already
assigned page to the different object);
}
and it worked with SNA enabled for about a week with no problems. But
I'm not sure that is a good solution.
I can provide additional info if required.
Thanks
--
Oleg Sidorkin
___
freebsd-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-x11
To unsubscribe, send any mail to freebsd-x11-unsubscr...@freebsd.org
I did not see the original mail with the backtrace.
FWIW, it seems that the issue is that other thread might have faulted
on the same GTT offset and bound the page before the paniced thread.
If this is indeed the situation, then the proper fix is to check for
the race, and not to just avoid the insertion. Re-instantiating the
fences is particularly wrong IMO.
Try this patch (untested, I only compiled it).
diff --git a/sys/dev/drm2/i915/i915_gem.c
Re: [drm2][panic] Running XOrg with SNA enabled causes system panic after few hours on G33
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. pgp78Kyej0eyX.pgp Description: PGP signature
Re: [drm2][panic] Running XOrg with SNA enabled causes system panic after few hours on G33
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. -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [drm2][panic] Running XOrg with SNA enabled causes system panic after few hours on G33
Thank you! This patch also solve my issue (unable shutdown):
http://lists.freebsd.org/pipermail/freebsd-current/2013-May/042011.html
On Tuesday 11 June 2013 12:34:16 Oleg Sidorkin wrote:
Hello.
I'm running recent 9.1/stable with the recent XOrg on the system with
G33 chipset.
My pciconf -lvb output is here: http://pastebin.com/LDzKzf1i
If I add
Option AccelMethod sna
to my xorg.conf system panics after few hours:
(kgdb) bt
#0 doadump (textdump=value optimized out)
at /usr/src/sys/kern/kern_
shutdown.c:272
#1 0x8050a19f in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:449
#2 0x8050a6a3 in panic (fmt=0x104 Address 0x104 out of bounds)
at /usr/src/sys/kern/kern_shutdown.c:637
#3 0x80765f77 in vm_page_insert (m=0xfe0226126b50,
object=0xfe0208de8488, pindex=3) at /usr/src/sys/vm/vm_page.c:914
#4 0x814a889d in i915_gem_pager_fault (vm_obj=0xfe0208de8488,
offset=3, prot=value optimized out, mres=0xff824705b680)
at
/usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/i915_gem.c:1429
#5 0x80747fe3 in dev_pager_getpages (object=0xfe0208de8488,
ma=0xff824705b680, count=1, reqpage=value optimized out)
at /usr/src/sys/vm/device_pager.c:260
#6 0x80754bb6 in vm_fault_hold (map=0xfe000c247188,
vaddr=34458505216, fault_type=2 '\002', fault_flags=0, m_hold=0x0)
at vm_pager.h:128
#7 0x80756ca3 in vm_fault (map=0xfe000c247188, vaddr=34458505216,
fault_type=value optimized out, fault_flags=0)
at /usr/src/sys/vm/vm_fault.c:229
#8 0x8078e01f in trap_pfault (frame=0xff824705bc40, usermode=1)
at /usr/src/sys/amd64/amd64/trap.c:762
#9 0x8078e864 in trap (frame=0xff824705bc40)
(kgdb) bt full
#0 doadump (textdump=value optimized out)
at /usr/src/sys/kern/kern_shutdown.c:272
No locals.
#1 0x8050a19f in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:449
_ep = (struct eventhandler_entry *) 0x0
_el = (struct eventhandler_list *) 0xfe0009c7f700
first_buf_printf = 1
#2 0x8050a6a3 in panic (fmt=0x104 Address 0x104 out of bounds)
at /usr/src/sys/kern/kern_shutdown.c:637
td = (struct thread *) 0x0
bootopt = value optimized out
newpanic = value optimized out
ap = {{gp_offset = 8, fp_offset = 48,
overflow_arg_area = 0xff824705b570,
reg_save_area = 0xff824705b490}}
panic_cpu = 3
buf = vm_page_insert: page already inserted, '\0' repeats 218
times
#3 0x80765f77 in vm_page_insert (m=0xfe0226126b50,
object=0xfe0208de8488, pindex=3) at /usr/src/sys/vm/vm_page.c:914
root = 0x0
#4 0x814a889d in i915_gem_pager_fault (vm_obj=0xfe0208de8488,
offset=3, prot=value optimized out, mres=0xff824705b680)
(kgdb) up 4
#4 0x814a889d in i915_gem_pager_fault (vm_obj=0xfe0208de8488,
offset=3, prot=value optimized out, mres=0xff824705b680)
at
/usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/i915_gem.c:1429
1429vm_page_insert(m, vm_obj, OFF_TO_IDX(offset));
(kgdb) p vm_obj
$1 = 0xfe0208de8488
(kgdb) p m-object
$2 = 0xfe0208de8488
It works fine for weeks without Option AccelMethod sna.
I replaced
vm_page_insert(m, vm_obj, OFF_TO_IDX(offset));
with the code
if (m-object==NULL){
vm_page_insert(m, vm_obj, OFF_TO_IDX(offset));
}
else{
if(m-object!=vm_obj)
panic(i915_gem_pager_fault: tried to assign already
assigned page to the different object);
}
and it worked with SNA enabled for about a week with no problems. But
I'm not sure that is a good solution.
I can provide additional info if required.
Thanks
--
Oleg Sidorkin
___
freebsd-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-x11
To unsubscribe, send any mail to freebsd-x11-unsubscr...@freebsd.org
--
Artyom Mirgorodskiy
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [drm2][panic] Running XOrg with SNA enabled causes system panic after few hours on G33
On Fri, Jun 14, 2013 at 10:16:15AM +0300, Artyom Mirgorodskiy wrote:
Thank you! This patch also solve my issue (unable shutdown):
http://lists.freebsd.org/pipermail/freebsd-current/2013-May/042011.html
On Tuesday 11 June 2013 12:34:16 Oleg Sidorkin wrote:
Hello.
I'm running recent 9.1/stable with the recent XOrg on the system with
G33 chipset.
My pciconf -lvb output is here: http://pastebin.com/LDzKzf1i
If I add
Option AccelMethod sna
to my xorg.conf system panics after few hours:
(kgdb) bt
#0 doadump (textdump=value optimized out)
at /usr/src/sys/kern/kern_
shutdown.c:272
#1 0x8050a19f in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:449
#2 0x8050a6a3 in panic (fmt=0x104 Address 0x104 out of bounds)
at /usr/src/sys/kern/kern_shutdown.c:637
#3 0x80765f77 in vm_page_insert (m=0xfe0226126b50,
object=0xfe0208de8488, pindex=3) at /usr/src/sys/vm/vm_page.c:914
#4 0x814a889d in i915_gem_pager_fault (vm_obj=0xfe0208de8488,
offset=3, prot=value optimized out, mres=0xff824705b680)
at
/usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/i915_gem.c:1429
#5 0x80747fe3 in dev_pager_getpages (object=0xfe0208de8488,
ma=0xff824705b680, count=1, reqpage=value optimized out)
at /usr/src/sys/vm/device_pager.c:260
#6 0x80754bb6 in vm_fault_hold (map=0xfe000c247188,
vaddr=34458505216, fault_type=2 '\002', fault_flags=0, m_hold=0x0)
at vm_pager.h:128
#7 0x80756ca3 in vm_fault (map=0xfe000c247188,
vaddr=34458505216,
fault_type=value optimized out, fault_flags=0)
at /usr/src/sys/vm/vm_fault.c:229
#8 0x8078e01f in trap_pfault (frame=0xff824705bc40, usermode=1)
at /usr/src/sys/amd64/amd64/trap.c:762
#9 0x8078e864 in trap (frame=0xff824705bc40)
(kgdb) bt full
#0 doadump (textdump=value optimized out)
at /usr/src/sys/kern/kern_shutdown.c:272
No locals.
#1 0x8050a19f in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:449
_ep = (struct eventhandler_entry *) 0x0
_el = (struct eventhandler_list *) 0xfe0009c7f700
first_buf_printf = 1
#2 0x8050a6a3 in panic (fmt=0x104 Address 0x104 out of bounds)
at /usr/src/sys/kern/kern_shutdown.c:637
td = (struct thread *) 0x0
bootopt = value optimized out
newpanic = value optimized out
ap = {{gp_offset = 8, fp_offset = 48,
overflow_arg_area = 0xff824705b570,
reg_save_area = 0xff824705b490}}
panic_cpu = 3
buf = vm_page_insert: page already inserted, '\0' repeats 218
times
#3 0x80765f77 in vm_page_insert (m=0xfe0226126b50,
object=0xfe0208de8488, pindex=3) at /usr/src/sys/vm/vm_page.c:914
root = 0x0
#4 0x814a889d in i915_gem_pager_fault (vm_obj=0xfe0208de8488,
offset=3, prot=value optimized out, mres=0xff824705b680)
(kgdb) up 4
#4 0x814a889d in i915_gem_pager_fault (vm_obj=0xfe0208de8488,
offset=3, prot=value optimized out, mres=0xff824705b680)
at
/usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/i915_gem.c:1429
1429vm_page_insert(m, vm_obj, OFF_TO_IDX(offset));
(kgdb) p vm_obj
$1 = 0xfe0208de8488
(kgdb) p m-object
$2 = 0xfe0208de8488
It works fine for weeks without Option AccelMethod sna.
I replaced
vm_page_insert(m, vm_obj, OFF_TO_IDX(offset));
with the code
if (m-object==NULL){
vm_page_insert(m, vm_obj, OFF_TO_IDX(offset));
}
else{
if(m-object!=vm_obj)
panic(i915_gem_pager_fault: tried to assign already
assigned page to the different object);
}
and it worked with SNA enabled for about a week with no problems. But
I'm not sure that is a good solution.
I can provide additional info if required.
Thanks
--
Oleg Sidorkin
___
freebsd-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-x11
To unsubscribe, send any mail to freebsd-x11-unsubscr...@freebsd.org
--
Artyom Mirgorodskiy
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
I did not see the original mail with the backtrace.
FWIW, it seems that the issue is that other thread might have faulted
on the same GTT offset and bound the page before the paniced thread.
If this is indeed the situation, then the proper fix is to check for
the race, and not to just avoid the insertion. Re-instantiating the
fences is particularly wrong IMO.
Try this patch (untested, I only compiled it).
diff --git
