Re: [Intel-gfx] [regression] 3.6-rc6, gpu hang with vaapi
> Hi, > > I get a GPU hang every time i play an mkv using mplayer -vo vaapi with 3.6- > rc6. > With 3.5.4 no GPU hang at all. > > I'm using xf86-video-intel 2.20.8, xorg-server 1.12.4 and libva-1.1.0 on Intel(R) > Sandybridge Mobile (GT2+). > I have a SandyBridge 2600K and had problems running mythtv. However mplayer worked. It depends highly on the application and libraries used. Try with the special versioned mplayer and let us know: https://bugs.freedesktop.org/show_bug.cgi?id=51061#c4 > # cat /sys/kernel/debug/dri/0/i915_error_state > cat: /sys/kernel/debug/dri/0/i915_error_state: Cannot allocate memory Didn't work for me too. Angela ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [Bug 51061] GPU Hang using VAAPI
> > No need to bisect, we've dug out the issue on latest > > drm-intel-next-queued: One of Jesse Barnes' patches that shouldn't have > > affected anything else than unreleased hw blew up snb & ivb. I've updated > > the branch, it should work now. > > What should work, VAAPI or the error_state ? > > git reset --hard HEAD > git checkout -b mine35031 > git merge daniel/for-angela > git merge drm-intel/drm-intel-next-queued > > Running with VAAPI still has the same result. > > Angela I didn't get a reply on my last mail. The test failed. Just wondering if the merging was done right. I like to "help", but need some pointers. Angela > > cat: /sys/kernel/debug/dri/0/i915_error_state: Cannot allocate memory > > [ 603.833161] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer > elapsed... > GPU hung > [ 603.833163] [drm] capturing error event; look for more information in > /debug/dri/0/i915_error_state > [ 603.889576] [ cut here ] > [ 603.889589] kernel BUG at drivers/gpu/drm/i915/i915_gem.c:3257! > [ 603.889605] invalid opcode: [#1] SMP > [ 603.889616] CPU 2 > [ 603.889643] Modules linked in: xts gf128mul autofs4 dm_crypt binfmt_misc > ipt_MASQUERADE snd_hda_codec_hdmi snd_hda_codec_realtek > xt_conntrack > iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 > iptable_filter ip_tables x_tables snd_hda_intel snd_hda_codec snd_hwdep > snd_pcm snd_seq_midi tda18271c2dd snd_rawmidi snd_seq_midi_event > arc4 ath9k > snd_seq mac80211 btusb ath9k_common ath9k_hw snd_timer > snd_seq_device snd > drxk ath soundcore ddbridge psmouse mei bluetooth snd_page_alloc > hid_generic > coretemp cfg80211 eeepc_wmi dvb_core asus_wmi lpc_ich sparse_keymap > lp > serio_raw microcode parport usbhid hid usb_storage uas > ghash_clmulni_intel > aesni_intel firewire_ohci firewire_core cryptd crc_itu_t 8139too 8139cp > aes_x86_64 mxm_wmi i915 ahci libahci drm_kms_helper xhci_hcd drm > e1000e > i2c_algo_bit video wmi [last unloaded: kvm] > [ 603.889802] > [ 603.889809] Pid: 4429, comm: Xorg Not tainted 3.5.0-rc3-mine353+ #10 > System manufacturer System Product Name/P8Z68-V PRO > [ 603.889843] RIP: 0010:[] [] > i915_gem_object_unpin+0x4f/0x60 [i915] > [ 603.889865] RSP: 0018:8801d3985b48 EFLAGS: 00010246 > [ 603.889878] RAX: 00ff RBX: 88020f7fb800 RCX: > a016014d > [ 603.889895] RDX: 014204ff RSI: 00070008 RDI: > 8801d998c200 > [ 603.889912] RBP: 8801d3985b48 R08: a0154d60 R09: > 02bc > [ 603.889929] R10: a0154cc0 R11: R12: > 88020f6e2020 > [ 603.889946] R13: 88020ed38000 R14: 88020f6e2000 R15: > 8801d3985c98 > [ 603.889963] FS: 7fc0075e9880() GS:88021f28() > knlGS: > [ 603.889982] CS: 0010 DS: ES: CR0: 8005003b > [ 603.889996] CR2: 00bbd7e0 CR3: 0001d9a49000 CR4: > 000407e0 > [ 603.890013] DR0: DR1: DR2: > > [ 603.890030] DR3: DR6: 0ff0 DR7: > 0400 > [ 603.890047] Process Xorg (pid: 4429, threadinfo 8801d3984000, task > 8801dcc816f0) > [ 603.890066] Stack: > [ 603.890074] 8801d3985b58 a0121b7c 8801d3985b88 > a012524c > [ 603.890092] 88020f6e2438 88020f7fb800 a01665e0 > 88020f6e2468 > [ 603.890111] 8801d3985bb8 a00ef6a5 8801d3985fd8 > 88020f7fb800 > [ 603.890128] Call Trace: > [ 603.890143] [] intel_unpin_fb_obj+0x3c/0x40 [i915] > [ 603.890164] [] intel_crtc_disable+0x8c/0xb0 [i915] > [ 603.890183] [] > drm_helper_disable_unused_functions+0x115/0x190 [drm_kms_helper] > [ 603.890207] [] > drm_crtc_helper_set_config+0xa6e/0xb00 > [drm_kms_helper] > [ 603.890229] [] ? __generic_file_aio_write+0x235/0x440 > [ 603.890252] [] drm_framebuffer_cleanup+0xfe/0x180 > [drm] > [ 603.890275] [] > intel_user_framebuffer_destroy+0x21/0x80 [i915] > [ 603.890298] [] drm_mode_rmfb+0xfb/0x100 [drm] > [ 603.890317] [] drm_ioctl+0x47c/0x540 [drm] > [ 603.890332] [] ? default_spin_lock_flags+0x9/0x10 > [ 603.890353] [] ? drm_mode_addfb2+0x690/0x690 [drm] > [ 603.890371] [] ? do_sync_write+0xd2/0x110 > [ 603.890386] [] ? fsnotify+0x1d2/0x2b0 > [ 603.890400] [] do_vfs_ioctl+0x98/0x550 > [ 603.890414] [] sys_ioctl+0x91/0xa0 > [ 603.890428] [] system_call_fastpath+0x16/0x1b > [ 603.890457] Code: e2 ff 1f fe ff c1 e8 0d 83 c0 0f 83 e0 0f 89 c1 83 e1 > 0f c1 e1 0d 09 ca 84 c0 89 97 f0 00 00 00 75 07 80 a7 f2 00 00 00 f7 5d c3 > <0f> 0b 0f 0b 66
Re: [Intel-gfx] [Bug 51061] GPU Hang using VAAPI
> No need to bisect, we've dug out the issue on latest > drm-intel-next-queued: One of Jesse Barnes' patches that shouldn't have > affected anything else than unreleased hw blew up snb & ivb. I've updated > the branch, it should work now. What should work, VAAPI or the error_state ? git reset --hard HEAD git checkout -b mine35031 git merge daniel/for-angela git merge drm-intel/drm-intel-next-queued Running with VAAPI still has the same result. Angela cat: /sys/kernel/debug/dri/0/i915_error_state: Cannot allocate memory [ 603.833161] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [ 603.833163] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state [ 603.889576] [ cut here ] [ 603.889589] kernel BUG at drivers/gpu/drm/i915/i915_gem.c:3257! [ 603.889605] invalid opcode: [#1] SMP [ 603.889616] CPU 2 [ 603.889643] Modules linked in: xts gf128mul autofs4 dm_crypt binfmt_misc ipt_MASQUERADE snd_hda_codec_hdmi snd_hda_codec_realtek xt_conntrack iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi tda18271c2dd snd_rawmidi snd_seq_midi_event arc4 ath9k snd_seq mac80211 btusb ath9k_common ath9k_hw snd_timer snd_seq_device snd drxk ath soundcore ddbridge psmouse mei bluetooth snd_page_alloc hid_generic coretemp cfg80211 eeepc_wmi dvb_core asus_wmi lpc_ich sparse_keymap lp serio_raw microcode parport usbhid hid usb_storage uas ghash_clmulni_intel aesni_intel firewire_ohci firewire_core cryptd crc_itu_t 8139too 8139cp aes_x86_64 mxm_wmi i915 ahci libahci drm_kms_helper xhci_hcd drm e1000e i2c_algo_bit video wmi [last unloaded: kvm] [ 603.889802] [ 603.889809] Pid: 4429, comm: Xorg Not tainted 3.5.0-rc3-mine353+ #10 System manufacturer System Product Name/P8Z68-V PRO [ 603.889843] RIP: 0010:[] [] i915_gem_object_unpin+0x4f/0x60 [i915] [ 603.889865] RSP: 0018:8801d3985b48 EFLAGS: 00010246 [ 603.889878] RAX: 00ff RBX: 88020f7fb800 RCX: a016014d [ 603.889895] RDX: 014204ff RSI: 00070008 RDI: 8801d998c200 [ 603.889912] RBP: 8801d3985b48 R08: a0154d60 R09: 02bc [ 603.889929] R10: a0154cc0 R11: R12: 88020f6e2020 [ 603.889946] R13: 88020ed38000 R14: 88020f6e2000 R15: 8801d3985c98 [ 603.889963] FS: 7fc0075e9880() GS:88021f28() knlGS: [ 603.889982] CS: 0010 DS: ES: CR0: 8005003b [ 603.889996] CR2: 00bbd7e0 CR3: 0001d9a49000 CR4: 000407e0 [ 603.890013] DR0: DR1: DR2: [ 603.890030] DR3: DR6: 0ff0 DR7: 0400 [ 603.890047] Process Xorg (pid: 4429, threadinfo 8801d3984000, task 8801dcc816f0) [ 603.890066] Stack: [ 603.890074] 8801d3985b58 a0121b7c 8801d3985b88 a012524c [ 603.890092] 88020f6e2438 88020f7fb800 a01665e0 88020f6e2468 [ 603.890111] 8801d3985bb8 a00ef6a5 8801d3985fd8 88020f7fb800 [ 603.890128] Call Trace: [ 603.890143] [] intel_unpin_fb_obj+0x3c/0x40 [i915] [ 603.890164] [] intel_crtc_disable+0x8c/0xb0 [i915] [ 603.890183] [] drm_helper_disable_unused_functions+0x115/0x190 [drm_kms_helper] [ 603.890207] [] drm_crtc_helper_set_config+0xa6e/0xb00 [drm_kms_helper] [ 603.890229] [] ? __generic_file_aio_write+0x235/0x440 [ 603.890252] [] drm_framebuffer_cleanup+0xfe/0x180 [drm] [ 603.890275] [] intel_user_framebuffer_destroy+0x21/0x80 [i915] [ 603.890298] [] drm_mode_rmfb+0xfb/0x100 [drm] [ 603.890317] [] drm_ioctl+0x47c/0x540 [drm] [ 603.890332] [] ? default_spin_lock_flags+0x9/0x10 [ 603.890353] [] ? drm_mode_addfb2+0x690/0x690 [drm] [ 603.890371] [] ? do_sync_write+0xd2/0x110 [ 603.890386] [] ? fsnotify+0x1d2/0x2b0 [ 603.890400] [] do_vfs_ioctl+0x98/0x550 [ 603.890414] [] sys_ioctl+0x91/0xa0 [ 603.890428] [] system_call_fastpath+0x16/0x1b [ 603.890457] Code: e2 ff 1f fe ff c1 e8 0d 83 c0 0f 83 e0 0f 89 c1 83 e1 0f c1 e1 0d 09 ca 84 c0 89 97 f0 00 00 00 75 07 80 a7 f2 00 00 00 f7 5d c3 <0f> 0b 0f 0b 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 [ 603.890504] RIP [] i915_gem_object_unpin+0x4f/0x60 [i915] [ 603.890521] RSP [ 634.871488] [ cut here ] [ 634.871516] WARNING: at mm/page_alloc.c:2298 __alloc_pages_nodemask+0x2f2/0x930() [ 634.871545] Hardware name: System Product Name [ 634.871588] Modules linked in: xts gf128mul autofs4 dm_crypt binfmt_misc ipt_MASQUERADE snd_hda_codec_hdmi snd_hda_codec_realtek xt_conntrack iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi tda18271c2dd snd_rawmidi snd_seq_midi_event arc4 ath9k snd_seq mac8
Re: [Intel-gfx] [Bug 51061] GPU Hang using VAAPI
> From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel > Vetter > Sent: Wednesday, 20 June, 2012 21:29 > To: Angela > Cc: 'Daniel Vetter'; intel-gfx@lists.freedesktop.org > Subject: Re: [Intel-gfx] [Bug 51061] GPU Hang using VAAPI > > On Wed, Jun 20, 2012 at 09:21:07PM +0200, Angela wrote: > > > > Updated xorg-edgers, updated kernel (>3.5-rc3), merged > > > > drm-intel-next-queued. "Fixed" the two conflicts, are they OK ? > > > > > > > > No console, X starts in Vesa Mode. > > > > > > > > Added the new kernel dmesg, my "fixed" conflict's and a good > > > > kernel > > > dmesg. > > > > > > > > What's next. > > > > > > Looks like the kernel couldn't communicate with the chip at all, all > > > reads > > just > > > fail. I've pushed out a for-angela branch to my kernel playground at > > > > > > http://cgit.freedesktop.org/~danvet/drm > > > > > > Which contains recent drm-intel-next-queued with rc3 merged. That > > > one boots at least correctly here. Although your merge resolution > > > looks > > correct, > > > so I have no idea what exactly went wrong. > > > -Daniel > > > > > > > Used head kernel and merged for-angela. Console and X are fine now, > > for drm dmesg see below. > > > > > contains recent drm-intel-next-queued with rc3 merged > > I could also have taken for-angela alone, does it matter ? > > > > Still have the VAAPI problem and still cannot grab error_state > > > > [ 416.677] (WW) intel(0): flip queue failed: Input/output error > > > > cat: /sys/kernel/debug/dri/0/i915_error_state: Cannot allocate memory > > > > With ppa kernel I didn't had a console and the system hung (could not > > ssh), will you add the "couldn't communicate with the chip at all" > > patch to drm-intel-next-queued, so I could check the error_state once > > again with the generated ppa 3.4 kernel. Will we be more lucky ? When > > will it be ready to try ? > > It should all work, but something is seriously broken for you. Could you bisect > where this started to blow up for you maybe? I never had VAAPI running, I reported 24-mar-2012 for the first time. What you mean VAAPI or to fetch the error_state ? I can bisect, where to start ? Which sources/kernel ? Angela ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [Bug 51061] GPU Hang using VAAPI
> > Updated xorg-edgers, updated kernel (>3.5-rc3), merged > > drm-intel-next-queued. "Fixed" the two conflicts, are they OK ? > > > > No console, X starts in Vesa Mode. > > > > Added the new kernel dmesg, my "fixed" conflict's and a good kernel > dmesg. > > > > What's next. > > Looks like the kernel couldn't communicate with the chip at all, all reads just > fail. I've pushed out a for-angela branch to my kernel playground at > > http://cgit.freedesktop.org/~danvet/drm > > Which contains recent drm-intel-next-queued with rc3 merged. That one > boots at least correctly here. Although your merge resolution looks correct, > so I have no idea what exactly went wrong. > -Daniel > Used head kernel and merged for-angela. Console and X are fine now, for drm dmesg see below. > contains recent drm-intel-next-queued with rc3 merged I could also have taken for-angela alone, does it matter ? Still have the VAAPI problem and still cannot grab error_state [ 416.677] (WW) intel(0): flip queue failed: Input/output error cat: /sys/kernel/debug/dri/0/i915_error_state: Cannot allocate memory With ppa kernel I didn't had a console and the system hung (could not ssh), will you add the "couldn't communicate with the chip at all" patch to drm-intel-next-queued, so I could check the error_state once again with the generated ppa 3.4 kernel. Will we be more lucky ? When will it be ready to try ? Any other thoughts ? Angela [ 416.868719] kernel BUG at drivers/gpu/drm/i915/i915_gem.c:3242! [ 416.868752] invalid opcode: [#1] SMP [ 416.868776] CPU 0 [ 416.868833] Modules linked in: xts gf128mul autofs4 dm_crypt binfmt_misc ipt_MASQUERADE xt_conntrack iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack n f_defrag_ipv4 iptable_filter ip_tables x_tables snd_hda_codec_hdmi snd_hda_codec_realtek arc4 tda18271c2dd ath9k snd_hda_intel snd_hda_codec snd_hwdep mac8 0211 snd_pcm snd_seq_midi ath9k_common snd_rawmidi snd_seq_midi_event ath9k_hw ath snd_seq drxk snd_timer snd_seq_device snd eeepc_wmi coretemp soundcore p smouse ddbridge btusb bluetooth dvb_core asus_wmi mei snd_page_alloc serio_raw hid_generic microcode cfg80211 sparse_keymap lpc_ich lp parport usbhid hid u sb_storage uas mxm_wmi ghash_clmulni_intel aesni_intel cryptd firewire_ohci firewire_core aes_x86_64 i915 crc_itu_t 8139too 8139cp drm_kms_helper ahci liba hci xhci_hcd drm e1000e i2c_algo_bit video wmi [last unloaded: kvm] [ 416.869171] [ 416.869187] Pid: 4382, comm: Xorg Not tainted 3.5.0-rc3-mine353+ #7 System manufacturer System Product Name/P8Z68-V PRO [ 416.869257] RIP: 0010:[] [] i915_gem_object_unpin+0x4f/0x60 [i915] [ 416.869304] RSP: 0018:880213061b48 EFLAGS: 00010246 [ 416.869334] RAX: 88020f6e4000 RBX: 88020f732000 RCX: 0a2e [ 416.869371] RDX: 03020402 RSI: 00070008 RDI: 88020f590a00 [ 416.869408] RBP: 880213061b48 R08: 000a R09: [ 416.869445] R10: R11: R12: 88020f731020 [ 416.869482] R13: 88020f6e4000 R14: 88020f731000 R15: 880213061c98 [ 416.869520] FS: 7f1a6027c880() GS:88021f20() knlGS: [ 416.869562] CS: 0010 DS: ES: CR0: 80050033 [ 416.869592] CR2: 7f728018a4e0 CR3: 0001db2b2000 CR4: 000407f0 [ 416.869629] DR0: DR1: DR2: [ 416.869666] DR3: DR6: 0ff0 DR7: 0400 [ 416.869704] Process Xorg (pid: 4382, threadinfo 88021306, task 88020d8b16f0) [ 416.869745] Stack: [ 416.869761] 880213061b58 a012750c 880213061b88 a012a8ac [ 416.869801] 88020f731438 88020f732000 a016b5e0 88020f731468 [ 416.869841] 880213061bb8 a00f06a5 880213061fd8 88020f732000 [ 416.869879] Call Trace: [ 416.869911] [] intel_unpin_fb_obj+0x3c/0x40 [i915] [ 416.869957] [] intel_crtc_disable+0x8c/0xb0 [i915] [ 416.869998] [] drm_helper_disable_unused_functions+0x115/0x190 [drm_kms_helper] [ 416.870049] [] drm_crtc_helper_set_config+0xa6e/0xb00 [drm_kms_helper] [ 416.870096] [] ? __generic_file_aio_write+0x235/0x440 [ 416.870146] [] drm_framebuffer_cleanup+0xfe/0x180 [drm] [ 416.870194] [] intel_user_framebuffer_destroy+0x21/0x80 [i915] [ 416.870245] [] drm_mode_rmfb+0xfb/0x100 [drm] [ 416.870288] [] drm_ioctl+0x47c/0x540 [drm] [ 416.870321] [] ? default_spin_lock_flags+0x9/0x10 [ 416.870367] [] ? drm_mode_addfb2+0x690/0x690 [drm] [ 416.870404] [] ? do_sync_write+0xd2/0x110 [ 416.870437] [] ? fsnotify+0x1d2/0x2b0 [ 416.870468] [] do_vfs_ioctl+0x98/0x550 [ 416.870498] [] sys_ioctl+0x91/0xa0 [ 416.870530] [] system_call_fas
Re: [Intel-gfx] [Bug 51061] GPU Hang using VAAPI
> From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel > Dunno which kernel the -extra one is built from, but there's a drm-intel- > experimental ppa at > > http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-experimental/ > > which is built from the drm-intel-next-queued branch from > > http://cgit.freedesktop.org/~danvet/drm-intel > > That's pretty much the latest stuff. Note though that merging this into 3.5-rc > has 2 simple merge conflicts. Hello Daniel Updated xorg-edgers, updated kernel (>3.5-rc3), merged drm-intel-next-queued. "Fixed" the two conflicts, are they OK ? No console, X starts in Vesa Mode. Added the new kernel dmesg, my "fixed" conflict's and a good kernel dmesg. What's next. Angela [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.5.0-rc3-mine353+ root=UUID=8d6b1917-e239-43f0-a957-a5aa181e0255 ro drm.debug=0x06 [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-3.5.0-rc3-mine353+ root=UUID=8d6b1917-e239-43f0-a957-a5aa181e0255 ro drm.debug=0x06 [1.103072] [drm] Initialized drm 1.1.0 20060810 [1.421330] [drm:intel_opregion_setup], graphic opregion physical addr: 0xbebbc018 [1.421341] [drm:intel_opregion_setup], SWSCI supported [1.421360] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [1.421362] [drm] Driver supports precise vblank timestamp query. [1.421365] [drm:intel_detect_pch], Found CougarPoint PCH [1.421366] [drm:init_vbt_defaults], Set default to SSC at 100MHz [1.421368] [drm:intel_parse_bios], Using VBT from OpRegion: $VBT SNB/IVB-DESKTOPd [1.421369] [drm:parse_general_features], BDB_GENERAL_FEATURES int_tv_support 0 int_crt_support 1 lvds_use_ssc 0 lvds_ssc_freq 120 display_clock_mode 0 [1.421370] [drm:parse_general_definitions], crt_ddc_bus_pin: 2 [1.421373] [drm:parse_lfp_panel_data], Found panel mode in BIOS VBT tables: [1.421375] [drm:drm_mode_debug_printmodeline], Modeline 0:"1024x768" 0 65000 1024 1048 1184 1344 768 771 777 806 0x8 0xa [1.421376] [drm:parse_lfp_panel_data], VBT initial LVDS value 300 [1.421377] [drm:parse_sdvo_panel_data], Found SDVO panel mode in BIOS VBT tables: [1.421379] [drm:drm_mode_debug_printmodeline], Modeline 0:"1600x1200" 0 162000 1600 1664 1856 2160 1200 1201 1204 1250 0x8 0xa [1.421380] [drm:parse_sdvo_device_mapping], No SDVO device info is found in VBT [1.421385] [drm:intel_dsm_pci_probe], no _DSM method for intel device [1.421392] [drm:intel_modeset_init], 2 display pipes available. [1.421710] [drm:intel_lvds_init], LVDS is not present in VBT [1.421727] [drm:intel_crt_init], pch crt adpa set to 0xf4 [1.422087] [drm:intel_sdvo_read_byte], i2c transfer returned -6 [1.422087] [drm:intel_sdvo_init], No SDVO device found on SDVOB [1.422128] [drm:intel_dp_i2c_init], i2c_init DPDDC-B [1.424649] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5143003f [1.424650] [drm:intel_dp_i2c_aux_ch], aux_ch failed -110 [1.427171] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5143003f [1.427172] [drm:intel_dp_i2c_aux_ch], aux_ch failed -110 [1.427220] [drm:intel_dp_i2c_init], i2c_init DPDDC-C [1.429741] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5143003f [1.429742] [drm:intel_dp_i2c_aux_ch], aux_ch failed -110 [1.432266] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5143003f [1.432266] [drm:intel_dp_i2c_aux_ch], aux_ch failed -110 [1.432295] [drm:intel_dp_i2c_init], i2c_init DPDDC-D [1.434816] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5143003f [1.434817] [drm:intel_dp_i2c_aux_ch], aux_ch failed -110 [1.437338] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5143003f [1.437339] [drm:intel_dp_i2c_aux_ch], aux_ch failed -110 [1.437377] [drm:ironlake_crtc_dpms], crtc 0/0 dpms off [1.437379] [drm:i915_get_vblank_timestamp], crtc 0 is disabled [1.484212] [drm:intel_update_fbc], [1.484215] [drm:ironlake_crtc_dpms], crtc 1/1 dpms off [1.484216] [drm:gm45_get_vblank_counter], trying to get vblank count for disabled pipe B [1.484217] [drm:i915_get_vblank_timestamp], crtc 1 is disabled [1.484219] [drm:gm45_get_vblank_counter], trying to get vblank count for disabled pipe B [1.484657] [drm:intel_update_fbc], [1.484659] [drm:ironlake_init_pch_refclk], has_panel 0 has_lvds 0 has_pch_edp 0 has_cpu_edp 0 has_ck505 0 [1.484661] [drm:ironlake_init_pch_refclk], Disabling SSC entirely [1.507012] [drm:init_status_page], render ring hws offset: 0x [1.559930] [drm:init_ring_common] *ERROR* render ring initialization failed ctl head tail start [1.560018] [drm:init_status_page], bsd ring hws offset: 0x00022000 [1.615897] [drm:init_ring_common] *ERROR* bsd ring initialization failed ctl head tail start [1.616018
Re: [Intel-gfx] [Bug 51061] GPU Hang using VAAPI
> > Subject: [Bug 51061] GPU Hang using VAAPI > > > > https://bugs.freedesktop.org/show_bug.cgi?id=51061 > > > > Chris Wilson changed: > > > >What|Removed |Added > > > > Status|NEW |NEEDINFO > > > > --- Comment #1 from Chris Wilson 2012-06-14 > > 00:30:02 PDT --- Install the drm-intel-experimental from the mainline > > kernel ppa and regrab the error state. > > Upgraded xorg-edgers. > > No console output and no login after booting with > http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel- > experimental/current/linux-extra-3.4.0-994-generic_3.4.0- > 994.201206150421_amd64.deb > In recovery mode keyboard did not work. > > Added > http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel- > experimental/current/linux-image-extra-3.4.0-994-generic_3.4.0- > 994.201206150421_amd64.deb > Could boot, but got many > BUG: Soft lockup - CPU#x stuck for 22s! > and after 2 minutes a complete lockup. > > What is in "extra" ? > Is there an intel git which I can merge into my git head (>3.5-rc2) kernel ? Or > does it not make any sense because you are still based on 3.4 ? > > Angela Anyone ? ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [Bug 51061] GPU Hang using VAAPI
> Subject: [Bug 51061] GPU Hang using VAAPI > > https://bugs.freedesktop.org/show_bug.cgi?id=51061 > > Chris Wilson changed: > >What|Removed |Added > > Status|NEW |NEEDINFO > > --- Comment #1 from Chris Wilson 2012-06-14 > 00:30:02 PDT --- Install the drm-intel-experimental from the mainline > kernel ppa and regrab the error state. Upgraded xorg-edgers. No console output and no login after booting with http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-experimental/current/linux-extra-3.4.0-994-generic_3.4.0-994.201206150421_amd64.deb In recovery mode keyboard did not work. Added http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-experimental/current/linux-image-extra-3.4.0-994-generic_3.4.0-994.201206150421_amd64.deb Could boot, but got many BUG: Soft lockup - CPU#x stuck for 22s! and after 2 minutes a complete lockup. What is in "extra" ? Is there an intel git which I can merge into my git head (>3.5-rc2) kernel ? Or does it not make any sense because you are still based on 3.4 ? Angela ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [libva] GPU hung
> Am Mittwoch, den 13.06.2012, 00:09 +0200 schrieb Angela: > > >> >For gpu hangs the important thing is the i915_error_state file > > >> >from sysfs > > >> (the files you've attached are mainly interesting for modeset issues). > > >> I guess the best thing would be to file a bug on > > >> bugs.freedesktop.org with that. > > >> > > >> # cat /sys/kernel/debug/dri/0/i915_error_state > > >> no error state collected > > >> # cat /sys/kernel/debug/dri/64/i915_error_state > > >> no error state collected I copied the wrong line from mount, debugfs is always mounted on Ubuntu none on /sys/kernel/debug type debugfs (rw) Still, I don't have any output right after the crash, see above. Tried several times 1080i recordings, either no error state collected Below error is with a 720p recording, which behaves and looks different cat .../debug/dri/0/i915_error_state, blocks Jun 13 17:35:39 minerva11 kernel: [68682.433743] [drm:i915_driver_open], Jun 13 17:35:39 minerva11 kernel: [68682.691256] [drm:i915_driver_open], Jun 13 17:35:39 minerva11 kernel: [68682.860834] [drm:i915_driver_open], Jun 13 17:35:40 minerva11 kernel: [68683.185483] [drm:drm_mode_addfb], [FB:27] Jun 13 17:35:46 minerva11 kernel: [68689.196485] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung Jun 13 17:35:46 minerva11 kernel: [68689.196946] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state Jun 13 17:35:46 minerva11 kernel: [68689.199780] [drm:i915_error_work_func], resetting chip Jun 13 17:35:46 minerva11 kernel: [68689.199843] [drm:drm_crtc_helper_set_config], Jun 13 17:35:46 minerva11 kernel: [68689.199845] [drm:drm_crtc_helper_set_config], [CRTC:3] [NOFB] Jun 13 17:35:46 minerva11 kernel: [68689.199867] [drm:ironlake_crtc_dpms], crtc 0/0 dpms off Jun 13 17:35:46 minerva11 kernel: [68689.199869] [drm:i915_get_vblank_timestamp], crtc 0 is disabled Jun 13 17:35:46 minerva11 kernel: [68689.205723] [drm:intel_prepare_page_flip], preparing flip with no unpin work? Jun 13 17:35:46 minerva11 udevd[19509]: failed to execute '/usr/share/apport/apport-gpu-error-intel.py' '/usr/share/apport/apport-gpu-error-intel.py': No such file or directory Jun 13 17:36:46 dhclient: last message repeated 4 times Jun 13 17:36:46 minerva11 kernel: [68689.252474] [drm:intel_disable_pch_pll], disable PCH PLL c6014 (active 1, on? 1) for crtc 3 Jun 13 17:36:46 minerva11 kernel: [68689.252476] [drm:intel_disable_pch_pll], disabling PCH PLL c6014 Jun 13 17:36:46 minerva11 kernel: [68689.252882] [drm:intel_update_fbc], Jun 13 17:36:46 minerva11 kernel: [68689.252906] [ cut here ] Jun 13 17:36:46 minerva11 kernel: [68689.253355] kernel BUG at drivers/gpu/drm/i915/i915_gem.c:3084! Jun 13 17:36:46 minerva11 kernel: [68689.253795] invalid opcode: [#1] SMP Jun 13 17:36:46 minerva11 kernel: [68689.254227] CPU 3 Jun 13 17:36:46 minerva11 kernel: [68689.254672] Modules linked in: des_generic md4 nls_utf8 cifs xts gf128mul autofs4 dm_crypt binfmt_misc ipt_MASQUERADE xt_conntrack snd_hda_codec_hdmi snd_hda_codec_realtek iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables tda18271c2dd(O) snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event drxk(O) snd_seq arc4 ath9k mac80211 ath9k_common ath9k_hw eeepc_wmi ddbridge(O) snd_timer snd_seq_device dvb_core(O) asus_wmi cxd2099(O) coretemp hid_generic ath btusb snd mei bluetooth psmouse serio_raw lpc_ich sparse_keymap soundcore cfg80211 snd_page_alloc microcode lp parport usbhid hid usb_storage uas 8139too mxm_wmi 8139cp ghash_clmulni_intel aesni_intel cryptd firewire_ohci aes_x86_64 firewire_core crc_itu_t i915 drm_kms_helper drm ahci e1000e libahci i2c_algo_bit xhci_hcd video wmi [last unloaded: kvm] Jun 13 17:36:46 minerva11 kernel: [68689.256832] Jun 13 17:36:46 miJun 13 17:44:59 minerva11 kernel: imklog 5.8.6, log source = /proc/kmsg started. Again with 1080i, I also noticed the stacktrace is not always the same, however ends always at the same point (intel_unpin_fb_obj): Jun 13 18:13:36 minerva11 kernel: [ 1737.267614] [ cut here ] Jun 13 18:13:36 minerva11 kernel: [ 1737.267630] kernel BUG at drivers/gpu/drm/i915/i915_gem.c:3084! Jun 13 18:13:36 minerva11 kernel: [ 1737.267646] invalid opcode: [#1] SMP Jun 13 18:13:36 minerva11 kernel: [ 1737.267657] CPU 2 Jun 13 18:13:36 minerva11 kernel: [ 1737.267683] Modules linked in: xts gf128mul autofs4 binfmt_misc dm_crypt btusb ipt_MASQUERADE xt_conntrack iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables snd_hda_codec_hdmi snd_hda_codec_realtek tda18271c2dd(O) arc4 ath9k mac80211 snd_hda_intel ath9k_common snd_hda_codec snd_hwdep snd_pcm snd_seq_mi
Re: [Intel-gfx] [libva] GPU hung
>> >For gpu hangs the important thing is the i915_error_state file from >> >sysfs >> (the files you've attached are mainly interesting for modeset issues). >> I guess the best thing would be to file a bug on bugs.freedesktop.org >> with that. >> >> # cat /sys/kernel/debug/dri/0/i915_error_state >> no error state collected >> # cat /sys/kernel/debug/dri/64/i915_error_state >> no error state collected >> >> mount: >> sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) >I guess you need to rehang your machine, the error_state doesn't survive a reboot. Hung the system and checked i915_error_state before reboot. Any other hints ? Angela ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [libva] GPU hung
>For gpu hangs the important thing is the i915_error_state file from sysfs (the files you've attached are mainly interesting for modeset issues). I guess the best thing would be to file a bug on bugs.freedesktop.org with that. Hello Daniel I get the following: # cat /sys/kernel/debug/dri/0/i915_error_state no error state collected # cat /sys/kernel/debug/dri/64/i915_error_state no error state collected mount: sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) What is wrong ? Angela On Tue, Jun 12, 2012 at 9:13 PM, Angela wrote: > Hello > Playing recordings with Mythtv 0.25 VAAPI I get 0.05 sec sound, > nothing gets displayed and have the following reproducible error > > dmesg.txt:[ 1104.077320] [drm:i915_hangcheck_hung] *ERROR* Hangcheck > timer elapsed... GPU hung > > Killing mythfrontend does not work. Running intel_reg_dumper, xvinfo, etc. > afterwards hang. System needs rebooting. > > This is on SandyBridge 2600K, 1080i HDMI on today's head kernel > (>3.5-rc2) and updated xorg-edgers on Ubuntu 12.04. No xorg.conf. > > Please find debugging info in attached problem_gpu_hang.zip (50KB), > with drm.debug=0x06. > > I reported some months ago a GPU hung issue, but didn't receive an > answer, I hope to get a reply this time (I don't mean an immediate > fix, but like to hear that someone will have a look into it in the next days/weeks). > I hope to get this fixed as many new 1080i channels are available, > which are not viewable atm and hope to have better luck with VAAPI. I > have a spare Nvidia GPU with cooler, but like to stick with Intel > Onboard GPU as it is already cooled. > > Angela > > > ___ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/intel-gfx > -- Daniel Vetter daniel.vet...@ffwll.ch - +41 (0) 79 364 57 48 - http://blog.ffwll.ch ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] 1080i content on 1080i shakes
> > > I have the interlaced patch running (kernel 3.3, not updated since > > > February) and is working perfect for up to 720p TV content. > > > However with 1080i TV content the picture shakes almost > > > continuously. The shaking is also viewable when the recording is > > > paused. Only some 1080i channels are almost OK. Others are not viewable. > > > I have updated with xorg-edgers several times for the last three > > > months without any improvement. > > > > > > While shooting a movie (25fp) I could not capture the shaking also > > > not when paused. So I paused a recording and shot continuously > > > pictures (iso1600) showing how the picture (shirt) shakes. The > > > pictures can be downloaded http://www.filedropper.com/1080iplayedon1080ipaused 10MB. > > > > Hm, to me that just looks like interlaced being interlaced. We scan > > out a progressive framebuffer, so when you display interlaced > > content it first gets deinterlaced, then the hw again makes an > > interlaced stream out of it. > > Maybe we could improve things by picking a different > > progressive->interlaced mode in the hw, but otherwise I dunno. > > Angela - Try turning on deinterlacing in your software player. >For the non optimized display settings in Mythtv I don't see any deinterlacing options. OpenGL in Mythtv has deinterlacing options, which I can deactivate. >Maybe I have to make a step back. I tried several times to get OpenGL working and hoped with newer Installation of Ubuntu and xorg-edgers that the following errors got fixed. But they still exist: >[324443.064] (WW) intel(0): cannot enable DRI2 whilst forcing software fallbacks >mythfrontend[22959]: E CoreContext vaapicontext.cpp:143 (Create) VAAPI: Error at vaapicontext.cpp:143 (#-1, unknown libva error) >mythfrontend[22959]: E CoreContext vaapicontext.cpp:311 (CreateDisplay) VAAPI: Invalid display Try to go the VAAPI was. The kernel provides the wrong Vendor, see detailed glxinfo output below. OpenGL vendor string: VMware, Inc. Which I could fix with an updated to head kernel. However with VAAPI, I get a GPU hang. I will investigate and report it in a new issue. Angela I don't have a xorg.conf. What can be wrong here ? Angela $ LIBGL_DEBUG=verbose glxinfo name of display: :0 libGL: screen 0 does not appear to be DRI2 capable libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/tls/swrast_dri.so libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so libGL: Can't open configuration file /home/angela/.drirc: No such file or directory. display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_MESA_copy_sub_buffer, GLX_INTEL_swap_event client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_framebuffer_sRGB, GLX_EXT_create_context_es2_profile, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap, GLX_INTEL_swap_event GLX version: 1.4 GLX extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_multithread_makecurrent, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_EXT_texture_from_pixmap OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x300) OpenGL version string: 2.1 Mesa 8.1-devel OpenGL shading language version string: 1.20 OpenGL extensions: GL_ARB_multisample, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_copy_texture, GL_EXT_polygon_offset, GL_EXT_subtexture, GL_EXT_texture_object, GL_EXT_vertex_array, GL_EXT_compiled_vertex_array, GL_EXT_texture, GL_EXT_texture3D, GL_IBM_rasterpos_clip, GL_ARB_point_parameters, GL_EXT_draw_range_elements, GL_EXT_packed_pixels, GL_EXT_point_parameters, GL_EXT_rescale_normal, GL_EXT_separate_specular_color, GL_EXT_texture_edge_clamp, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, GL
Re: [Intel-gfx] 1080i content on 1080i shakes
> > > I have the interlaced patch running (kernel 3.3, not updated since > > > February) and is working perfect for up to 720p TV content. However > > > with 1080i TV content the picture shakes almost continuously. The > > > shaking is also viewable when the recording is paused. Only some > > > 1080i channels are almost OK. Others are not viewable. > > > I have updated with xorg-edgers several times for the last three > > > months without any improvement. > > > > > > While shooting a movie (25fp) I could not capture the shaking also > > > not when paused. So I paused a recording and shot continuously > > > pictures (iso1600) showing how the picture (shirt) shakes. The > > > pictures can be downloaded http://www.filedropper.com/1080iplayedon1080ipaused 10MB. > > > > Hm, to me that just looks like interlaced being interlaced. We scan > > out a progressive framebuffer, so when you display interlaced content > > it first gets deinterlaced, then the hw again makes an interlaced stream out of it. > > Maybe we could improve things by picking a different > > progressive->interlaced mode in the hw, but otherwise I dunno. > > Angela - Try turning on deinterlacing in your software player. For the non optimized display settings in Mythtv I don't see any deinterlacing options. OpenGL in Mythtv has deinterlacing options, which I can deactivate. Maybe I have to make a step back. I tried several times to get OpenGL working and hoped with newer Installation of Ubuntu and xorg-edgers that the following errors got fixed. But they still exist: [324443.064] (WW) intel(0): cannot enable DRI2 whilst forcing software fallbacks mythfrontend[22959]: E CoreContext vaapicontext.cpp:143 (Create) VAAPI: Error at vaapicontext.cpp:143 (#-1, unknown libva error) mythfrontend[22959]: E CoreContext vaapicontext.cpp:311 (CreateDisplay) VAAPI: Invalid display I don't have a xorg.conf. What can be wrong here ? Angela $ LIBGL_DEBUG=verbose glxinfo name of display: :0 libGL: screen 0 does not appear to be DRI2 capable libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/tls/swrast_dri.so libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so libGL: Can't open configuration file /home/angela/.drirc: No such file or directory. display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_MESA_copy_sub_buffer, GLX_INTEL_swap_event client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_framebuffer_sRGB, GLX_EXT_create_context_es2_profile, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap, GLX_INTEL_swap_event GLX version: 1.4 GLX extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_multithread_makecurrent, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_EXT_texture_from_pixmap OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x300) OpenGL version string: 2.1 Mesa 8.1-devel OpenGL shading language version string: 1.20 OpenGL extensions: GL_ARB_multisample, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_copy_texture, GL_EXT_polygon_offset, GL_EXT_subtexture, GL_EXT_texture_object, GL_EXT_vertex_array, GL_EXT_compiled_vertex_array, GL_EXT_texture, GL_EXT_texture3D, GL_IBM_rasterpos_clip, GL_ARB_point_parameters, GL_EXT_draw_range_elements, GL_EXT_packed_pixels, GL_EXT_point_parameters, GL_EXT_rescale_normal, GL_EXT_separate_specular_color, GL_EXT_texture_edge_clamp, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_ARB_multitexture, GL_IBM_multimode_draw_arrays, GL_IBM_texture_mirrored_repeat, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_transpose_matrix, GL_EXT_blend_func_separate, GL_EXT_fog_coord, GL_EXT_multi_draw_arrays, GL_EXT_seco
[Intel-gfx] 1080i content on 1080i shakes
Hello I have the interlaced patch running (kernel 3.3, not updated since February) and is working perfect for up to 720p TV content. However with 1080i TV content the picture shakes almost continuously. The shaking is also viewable when the recording is paused. Only some 1080i channels are almost OK. Others are not viewable. I have updated with xorg-edgers several times for the last three months without any improvement. While shooting a movie (25fp) I could not capture the shaking also not when paused. So I paused a recording and shot continuously pictures (iso1600) showing how the picture (shirt) shakes. The pictures can be downloaded http://www.filedropper.com/1080iplayedon1080ipaused 10MB. I am using Sandybridge 2600K over HDMI to a 1080i television. Using mythtv with a dedicated X Server, no Desktop, on Ubuntu 12.04 LTS. Is this a known problem ? Any fixes ? Thanks Angela ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] VAAPI crashes X
> > > > I switched to Mythtv 0.25 using VAAPI and playing a recording crashes X > > immediately, I see following messages, > see run.log: > > > > OpenGL: Could not determine whether Sync to VBlank is enabled. > > > > libva: VA-API version 0.32.0 > > libva: va_getDriverName() returns 0 > > libva: Trying to open /usr/lib/dri/i965_drv_video.so > > libva: va_openDriver() returns 0 > > > > (WW) intel(0): flip queue failed: Input/output error > > (WW) intel(0): Page flip failed: Input/output error > > (WW) intel(0): divisor 0 get vblank counter failed: Invalid argument > > (EE) intel(0): Detected a hung GPU, disabling acceleration. > > (EE) intel(0): When reporting this, please include i915_error_state from > > debugfs and the full dmesg. > > intel_do_flush_locked failed: Input/output error > > /usr/bin/xinit: connection to X server lost > > > > > > [ 663.812879] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer > > elapsed... GPU hung > > [ 663.815205] [drm] capturing error event; look for more information in > > /debug/dri/0/i915_error_state > > [ 663.821719] [drm:i915_wait_request] *ERROR* i915_wait_request returns > > -11 (awaiting 791 at 785, next 792) > > [ 663.825652] HDMI hot plug event: Codec=3 Pin=7 Presence_Detect=0 > > ELD_Valid=1 > > [ 663.825690] HDMI status: Codec=3 Pin=7 Presence_Detect=0 ELD_Valid=0 > > [ 664.037996] [ cut here ] > > [ 664.038016] WARNING: at drivers/gpu/drm/i915/i915_gem.c:2397 > > i915_gem_object_put_fence+0xab/0xc0 [i915]() > > [ 664.038018] Hardware name: System Product Name > > [ 664.038019] Modules linked in: dvbloopback(O) rfcomm bnep bluetooth > > parport_pc ppdev binfmt_misc dm_crypt > ipt_MASQUERADE > > iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 > > iptable_filter ip_tables x_tables > snd_hda_codec_hdmi > > snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm > > snd_seq_midi tda18271c2dd(O) snd_rawmidi > arc4 ath9k > > snd_seq_midi_event mac80211 snd_seq drxk(O) snd_timer snd_seq_device snd > > ddbridge(O) dvb_core(O) ath9k_common > psmouse ath9k_hw ath > > eeepc_wmi asus_wmi sparse_keymap soundcore serio_raw snd_page_alloc > > cxd2099(O) mei(C) cfg80211 lp parport > usbhid hid usb_storage uas > > 8139too mxm_wmi 8139cp firewire_ohci firewire_core crc_itu_t i915 ahci > > libahci drm_kms_helper xhci_hcd e1000e > drm i2c_algo_bit video > > wmi > > [ 664.038054] Pid: 3156, comm: Xorg Tainted: G C O > > 3.3.0-rc2-angela2+ #1 > > [ 664.038055] Call Trace: > > [ 664.038061] [] warn_slowpath_common+0x7f/0xc0 > > [ 664.038064] [] warn_slowpath_null+0x1a/0x20 > > [ 664.038072] [] i915_gem_object_put_fence+0xab/0xc0 > > [i915] > > [ 664.038079] [] i915_gem_object_unbind+0xa3/0x2d0 > > [i915] > > [ 664.038090] [] ? drm_mode_object_put+0x47/0x60 [drm] > > [ 664.038097] [] i915_gem_free_object_tail+0x34/0x150 > > [i915] > > [ 664.038105] [] i915_gem_free_object+0x51/0x60 [i915] > > [ 664.038112] [] drm_gem_object_free+0x2a/0x30 [drm] > > [ 664.038121] [] > > intel_user_framebuffer_destroy+0x70/0x80 [i915] > > [ 664.038129] [] drm_fb_release+0x83/0xb0 [drm] > > [ 664.038136] [] drm_release+0x5e0/0x6e0 [drm] > > [ 664.038139] [] fput+0xea/0x220 > > [ 664.038141] [] filp_close+0x66/0x90 > > [ 664.038143] [] put_files_struct+0x88/0xf0 > > [ 664.038145] [] exit_files+0x54/0x70 > > [ 664.038147] [] do_exit+0x19a/0x8c0 > > [ 664.038150] [] do_group_exit+0x44/0xa0 > > [ 664.038152] [] sys_exit_group+0x17/0x20 > > [ 664.038155] [] system_call_fastpath+0x16/0x1b > > [ 664.038156] ---[ end trace 5bed8a9786c4dd85 ]--- > > > > > > cat /sys/kernel/debug/dri/0/i915_error_state > > cat: /sys/kernel/debug/dri/0/i915_error_state: Cannot allocate memory > > We're dumping a few megabytes of data through that file, and because we're > using simple helper routines we need to allocate all that data as a > contigious chunk. Which can easily fail if you're system has been up for a > longer time. Kill all applications and then retrying to grab the > error_state helps sometimes. > > Fixing that is on our todo, albeit quite a bit down ... > > Yours, Daniel Hello Daniel, This happens immediately after a reboot and start of a recording. It's a 8GB system, I killed all programs, but still can't collect from i915_error_state. Are the rest of the errors of any help to identify the problem ? Is userspace out-of-sync i
Re: [Intel-gfx] Television turns greenish after stand-by
> -Original Message- > From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter > Sent: 13 February 2012 09:32 > > All interlaced patches including the TRANSCONF patch from Paulo have been > merged to drm-intel-next-queued in my official drm-intel repo at: > > http://cgit.freedesktop.org/~danvet/drm-intel/ > Hello Daniel I can't fetch from the repository. git remote -v daniel git://people.freedesktop.org/~danvet/drm (fetch) daniel git://people.freedesktop.org/~danvet/drm (push) drm-intel http://cgit.freedesktop.org/~danvet/drm-intel (fetch) drm-intel http://cgit.freedesktop.org/~danvet/drm-intel (push) origin git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git (fetch) origin git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git (push) git fetch drm-intel error: Unable to find 396ee23db6b76354e487fd2cfdacbd989442f81d under http://cgit.freedesktop.org/~danvet/drm-intel Cannot obtain needed object 396ee23db6b76354e487fd2cfdacbd989442f81d error: Fetch failed. And with git clone http://cgit.freedesktop.org/~danvet/drm-intel Cloning into drm-intel... warning: remote HEAD refers to nonexistent ref, unable to checkout. What is wrong ? Angela ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Television turns greenish after stand-by
Hello Daniel There is no difference with intel_reg_dumper. I took a probe during correct display (1080i), after 2 days, when I moved the television out of stand-by (display is green) and after a shutdown/start during a correct display. See below. Also dmesg at start and when coming out of stand-by is the same. I have seen messages from Paulo Zanoni: [Intel-gfx] [PATCH 1/2] drm/i915: set interlaced bits for TRANSCONF Are they eventually needed in my case ? Could you incorporate these in your git interlace tree or otherwise tell me where to find them. As I reread the messages, there seem to be occasions that when HDMI is only connected the display can't come up correct. I have also only HDMI connected, but never have seen any misbehavior, it comes up in 1080i. What can I do to isolate the problem. Angela [9.527763] HDMI hot plug event: Codec=3 Pin=7 Presence_Detect=1 ELD_Valid=1 [9.527845] HDMI status: Codec=3 Pin=7 Presence_Detect=1 ELD_Valid=1 [9.527885] HDMI status: Codec=3 Pin=7 Presence_Detect=1 ELD_Valid=1 [9.534461] HDMI: detected monitor Philips FTV at connection type HDMI [9.534462] HDMI: available speakers: FL/FR [9.534464] HDMI: supports coding type LPCM: channels = 2, rates = 32000 44100 48000 96000 176400, bits = 16 20 24 [9.534466] HDMI: supports coding type AC-3: channels = 6, rates = 32000 44100 48000, max bitrate = 64 [9.534468] HDMI: supports coding type MPEG1: channels = 2, rates = 32000 44100 48000, max bitrate = 1072000 [374280.746752] HDMI hot plug event: Codec=3 Pin=7 Presence_Detect=1 ELD_Valid=1 [374280.746799] HDMI status: Codec=3 Pin=7 Presence_Detect=1 ELD_Valid=1 [374280.750481] HDMI: detected monitor Philips FTV at connection type HDMI [374280.750483] HDMI: available speakers: FL/FR [374280.750486] HDMI: supports coding type LPCM: channels = 2, rates = 32000 44100 48000 96000 176400, bits = 16 20 24 [374280.750489] HDMI: supports coding type AC-3: channels = 6, rates = 32000 44100 48000, max bitrate = 64 [374280.750491] HDMI: supports coding type MPEG1: channels = 2, rates = 32000 44100 48000, max bitrate = 1072000 PGETBL_CTL: 0x GEN6_INSTDONE_1: 0xfffe GEN6_INSTDONE_2: 0x CPU_VGACNTRL: 0x8000 (disabled) DIGITAL_PORT_HOTPLUG_CNTRL: 0x RR_HW_CTL: 0x (low 0, high 0) FDI_PLL_BIOS_0: 0x FDI_PLL_BIOS_1: 0x FDI_PLL_BIOS_2: 0x DISPLAY_PORT_PLL_BIOS_0: 0x DISPLAY_PORT_PLL_BIOS_1: 0x DISPLAY_PORT_PLL_BIOS_2: 0x FDI_PLL_FREQ_CTL: 0x PIPEACONF: 0xc060 (enabled, active, 8bpc) HTOTAL_A: 0x0a4f077f (1920 active, 2640 total) HBLANK_A: 0x0a4f077f (1920 start, 2640 end) HSYNC_A: 0x09bb098f (2448 start, 2492 end) VTOTAL_A: 0x04630437 (1080 active, 1124 total) VBLANK_A: 0x04630437 (1080 start, 1124 end) VSYNC_A: 0x0445043b (1084 start, 1094 end) VSYNCSHIFT_A: 0x0468 PIPEASRC: 0x077f0437 (1920, 1080) PIPEA_DATA_M1: 0x7e1b30f0 (TU 64, val 0x1b30f0 1782000) PIPEA_DATA_N1: 0x0020f580 (val 0x20f580 216) PIPEA_DATA_M2: 0x (TU 1, val 0x0 0) PIPEA_DATA_N2: 0x (val 0x0 0) PIPEA_LINK_M1: 0x0001220a (val 0x1220a 74250) PIPEA_LINK_N1: 0x00041eb0 (val 0x41eb0 27) PIPEA_LINK_M2: 0x (val 0x0 0) PIPEA_LINK_N2: 0x (val 0x0 0) DSPACNTR: 0xd8004400 (enabled) DSPABASE: 0x DSPASTRIDE: 0x1e00 (120) DSPASURF: 0x0084d000 DSPATILEOFF: 0x (0, 0) PIPEBCONF: 0x (disabled, inactive, 8bpc) HTOTAL_B: 0x (1 active, 1 total) HBLANK_B: 0x (1 start, 1 end) HSYNC_B: 0x (1 start, 1 end) VTOTAL_B: 0x (1 active, 1 total) VBLANK_B: 0x (1 start, 1 end) VSYNC_B: 0x (1 start, 1 end) VSYNCSHIFT_B: 0x DSPBCNTR: 0x4000 (disabled) DSPBBASE: 0x DSPBSTRIDE: 0x (0) DSPBSURF: 0x DSPBTILEOFF: 0x (0, 0) PIPEBSRC: 0x (1, 1) PIPEB_DATA_M1: 0x (TU 1, val 0x0 0) PIPEB_DATA_N1: 0x (val 0x0 0) PIPEB_DATA_M2: 0x (TU 1, val 0x0 0) PIPEB_DA
Re: [Intel-gfx] Television turns greenish after stand-by
Hello I have Linux 3.3-rc2 with daniels interlace patches. When the television turns off (dpms) and after turning on, the blacks are green. This is highly reproducable, however I don't know exactly which conditions have to exist. Restarting X, putting television once again to stand-by and turning on does not work. I have to shut down the television for a while. Is it a television problem or eventually produced by the driver ? Any help appreciated. Angela ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH 0/8] interlaced support v2
Hello Daniel I also want to confirm that interlacing is working over HDMI with 1920x1080i@50hz for Sandy Bridge 2600k. Thanks a lot. The fixes are not part of the intel gfx driver, correct ? When will it be pushed and to which kernel release will it presumably be addressed to. Angela > -Original Message- > From: intel-gfx-bounces+angela.schmid=wolke7@lists.freedesktop.org > [mailto:intel-gfx- > bounces+angela.schmid=wolke7@lists.freedesktop.org] On Behalf Of Alfonso > Fiore > Sent: 28 January 2012 19:30 > To: Daniel Vetter > Cc: Intel Graphics Development > Subject: Re: [Intel-gfx] [PATCH 0/8] interlaced support v2 > > On Sat, Jan 28, 2012 at 2:49 PM, Daniel Vetter wrote: > > Hi all, > > > > These are the patches I'd like to queue to -next for interlaced support. > > Needs > > the patch "fixup interlaced bits clearing in PIPECONF on PCH_SPLIT" and > > also the > > drm core fix "drm/modes: do not enforce an odd vtotal for interlaced modes" > > if > > you want to use interlaced modelines with an even vtotal. > > > > The entire series is available in my interlaced branch at > > > > http://cgit.freedesktop.org/~danvet/drm/log/?h=interlaced > > > > Review, comments and testing highly welcome. > > Tested-by: Alfonso Fiore > > i3 2130 connected to a Philips 32pf9731d over HDMI: > - 1920x1080i@30Hz > - 1280x720p@60Hz > - 1024x768p@60Hz > > thanks again, > alfonso > ___ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/intel-gfx ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working
Hello Alfonso The patches are not yet merged http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=history;f=drivers/gpu/drm/i915;hb=HEAD I also don't see them at the repository I received from Daniel https://git.kernel.org/?p=linux/kernel/git/keithp/linux.git;a=history;f=drivers/gpu/drm/i915 When will the patches be commited or merged ? Angela From: Alfonso Fiore [mailto:alfonso.fi...@gmail.com] Sent: 18 January 2012 15:28 To: Peter Ross Cc: Angela Schmid Subject: Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working Hi Peter! Thank you, fantastic news! :) > Version 2 of the patch set will work on a broader range of chipsets including > Sandy Bridge. I have just posted this to the list. It is also available here: > <http://lists.freedesktop.org/archives/intel-gfx/2012-January/014504.html> thank you! > To test you will need to recompile your kernel. In my case there was no need > to recompile Xorg, as the problem is confined to the kernel drm driver. If > you are running Debian or Ubuntu I can walk you through it. I absolutely accept your help. Thank you! As far as I understand I need to compile kernel from git. I use Ubuntu Oneiric 11.10. I found this article. Maybe you can have a look and tell me if these are the right steps to follow: https://wiki.ubuntu.com/KernelTeam/GitKernelBuild Basically what I don't know is at which step and how apply your patch. Just to confirm with you, I run Xorg 1.10.4 (xorg-edgers crashes after a few mins for me). I will have time to try tomorrow evening and over the weekend. Awesome! :) regards, alfonso On Wed, Jan 18, 2012 at 2:55 PM, Peter Ross wrote: On Tue, Jan 17, 2012 at 10:01:59PM +0100, Alfonso Fiore wrote: > On Tue, Jan 17, 2012 at 9:25 PM, Eugeni Dodonov wrote: > > > On Tue, Jan 17, 2012 at 18:14, Alfonso Fiore wrote: > > > >> > >> Hi Angela, > >> > >> I have a very similar problem! > >> Hi Angela and Alfonso, You may be in luck. I encountered the same interlace problem last weekend with my 1080i television and G35 chipset, and wrote a patch. While my chipset is not a Sandy Bridge chipset, they apparently share the same interlace logic. > >> I have Sandy Bridge (i3 2130) and a Philips 32pf9731d (coincidence?). > >> With my previous i3 550 I didn't have any problem. > >> > >> I tried all possible resolutions over HDMI and all the time the screen is > >> split in two (twice the top half) and flickering. I also can't manage to > >> use VGA (TV has VGA input). > >> > >> I also tried with the latest kernel and latest X. > >> > >> Can you try to run this tool? http://polypux.org/projects/read-edid/ > >> > >> I'm absolutely not an expert, but the output I get (Your EDID is probably > >> invalid.) is not encouraging. > >> > >> I'd love to know if you get the same error. > >> > > > > Could you try with the following two patches which just came to this list > > this week? > > http://comments.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/8006 > > > > Don't know if they will fix the problem, but they could help perhaps. > > Nb: The initial version of the patch set (given above) enables interlacing only on generation 4 chipsets, such as G35 and Q45. Version 2 of the patch set will work on a broader range of chipsets including Sandy Bridge. I have just posted this to the list. It is also available here: <http://lists.freedesktop.org/archives/intel-gfx/2012-January/014504.html> > I'm just an end-user. I have the willingness to try, but I need a bit more > guidance... I've never compiled X. If you can point me to some page that > explains the process I'll be more than happy to try. To test you will need to recompile your kernel. In my case there was no need to recompile Xorg, as the problem is confined to the kernel drm driver. If you are running Debian or Ubuntu I can walk you through it. -- Peter (A907 E02F A6E5 0CD2 34CD 20D2 6760 79C5 AC40 DD6B) ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working
Hello Daniel >Your TV likely sends a CEA block with some HDMI default modes set. Since >linux-3.3-rc1 (to be released in a few days) we should be able to decode that. >Can you grab the latest -linus kernel git and try that? I wanted to remind, that the interlaced modes work with the noveau driver with the 3.0.0 Kernel. Do they ignore the kernel routines and have their own code ? [ 18.242858] [drm:drm_mode_debug_printmodeline], Modeline 28:"1920x1080i" 0 74250 1920 2008 2052 2200 1080 1084 1094 1125 0x40 0x15 [ 18.242861] [drm:drm_mode_prune_invalid], Not using 1920x1080i mode 7 [ 18.242863] [drm:drm_mode_debug_printmodeline], Modeline 27:"1920x1080i" 0 74250 1920 2448 2492 2640 1080 1084 1094 1125 0x48 0x15 [ 18.242865] [drm:drm_mode_prune_invalid], Not using 1920x1080i mode 7 At this point, does the drm driver call kernel routines and decide on your mentioned kernel routines return to ignore those modes ? Angela > -Original Message- > From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter > Sent: 18 January 2012 00:13 > To: Angela Schmid > Cc: 'Alfonso Fiore'; 'Daniel Vetter'; intel-gfx@lists.freedesktop.org; > 'Rodrigo Vivi' > Subject: Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not > working > > On Tue, Jan 17, 2012 at 11:53:47PM +0100, Angela Schmid wrote: > > Over HDMI works: > > > > "1280x720@50hz" 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync > > > > 1280x720@50hz (0xb4) 74.2MHz +HSync +VSync *current > > > > h: width 1280 start 1720 end 1760 total 1980 skew0 clock > > 37.5KHz > > > > v: height 720 start 725 end 730 total 750 clock > > 50.0Hz > > > > > > > > > > > > "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace > > -hsync -vsync > > > > 1440x576ix0.0 (0xbd) 27.0MHz -HSync -VSync Interlace *current > > > > h: width 1440 start 1464 end 1590 total 1728 skew0 clock > > 15.6KHz > > > > v: height 576 start 580 end 586 total 625 clock > > 25.0Hz > > > > and > > > > "1440x288"x0.0 27.00 1440 1464 1590 1728 288 290 293 312 -hsync -vsync > > > > > > > > Have a lot of horizontal overscan, vertical very small, useless. > > Yeah, many TVs send out a different edid depending upon what connector > they are plugged in. Also we currently don't handle overscan compensation > at all, Rodrigo is working on that. > > > It is some time ago, that I compiled kernels myself. I compile drivers > > regularly. I will have a look next > week. > > > > > > > > >Your TV likely sends a CEA block with some HDMI default modes set. Since > > > > >linux-3.3-rc1 (to be released in a few days) we should be able to decode > > >that. > > > > >Can you grab the latest -linus kernel git and try that? > > > > > > > > Too many ways described on one page: > > http://wiki.ubuntuusers.de/Kernel/Kompilierung > > > > Kernel.org links to kernel newbies website. Do you have a link how to > > compile/install ? > > Maybe ask on irc about what's suggested. Way back I've used "Die > klassische Debian-Methode". > > > >You need to compile a new kernel, the output handling part of the graphics > > >driver is there. Best is to try > the latest > > drm-intel-fixes tree available > > > > >at: > > >https://git.kernel.org/?p=linux/kernel/git/keithp/linux.git;a=shortlog;h=refs/heads/drm-intel-fixes > > > > Can I wait for the ppa:xorg-edgers ? > > If they track drm-intel-fixes, yeah. But you might want to try to compile > the kernel, too, in case we have some additional patches for you to apply. > > Yours, Daniel > -- > Daniel Vetter > Mail: dan...@ffwll.ch > Mobile: +41 (0)79 365 57 48 ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working
Hello Over HDMI works: "1280x720@50hz" 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync 1280x720@50hz (0xb4) 74.2MHz +HSync +VSync *current h: width 1280 start 1720 end 1760 total 1980 skew0 clock 37.5KHz v: height 720 start 725 end 730 total 750 clock 50.0Hz "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync 1440x576ix0.0 (0xbd) 27.0MHz -HSync -VSync Interlace *current h: width 1440 start 1464 end 1590 total 1728 skew0 clock 15.6KHz v: height 576 start 580 end 586 total 625 clock 25.0Hz and "1440x288"x0.0 27.00 1440 1464 1590 1728 288 290 293 312 -hsync -vsync Have a lot of horizontal overscan, vertical very small, useless. It is some time ago, that I compiled kernels myself. I compile drivers regularly. I will have a look next week. >Your TV likely sends a CEA block with some HDMI default modes set. Since >linux-3.3-rc1 (to be released in a few days) we should be able to decode that. >Can you grab the latest -linus kernel git and try that? Too many ways described on one page: http://wiki.ubuntuusers.de/Kernel/Kompilierung Kernel.org links to kernel newbies website. Do you have a link how to compile/install ? >You need to compile a new kernel, the output handling part of the graphics >driver is there. Best is to try the latest drm-intel-fixes tree available >at: >https://git.kernel.org/?p=linux/kernel/git/keithp/linux.git;a=shortlog;h=refs/heads/drm-intel-fixes Can I wait for the ppa:xorg-edgers ? Angela From: Alfonso Fiore [mailto:alfonso.fi...@gmail.com] Sent: 17 January 2012 22:53 To: Daniel Vetter Cc: Angela Schmid; intel-gfx@lists.freedesktop.org; Rodrigo Vivi Subject: Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working > Ok, your TV only reports 1080i as a mode (at least that's the only thing > your kernel can decode). true, it's non a Full HD TV. > we unfortunately do not yet support interlaced everywhere we could when do you think the support will be added? weeks? months? > can you add a short list of the modelines you've manually added that work > with your TV? not sure I understand your question... The TV works with nomodeset and then I tried a bunch of resolutions with xrandr (when running without nomodeset) that ALL didn't work: I tried some of the modes I got from Xorg.0.log: [88.893] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz) [88.893] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) [88.893] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz) [88.893] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz) [88.893] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz) [88.893] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz) [88.893] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 483 489 525 -hsync -vsync (31.5 kHz) [88.893] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) [88.893] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) [88.893] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz) [88.893] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz) [88.893] (II) intel(0): Modeline "1440x240"x0.0 27.00 1440 1478 1602 1716 240 244 247 262 -hsync -vsync (15.7 kHz) [88.893] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz) [88.893] (II) intel(0): Modeline "1440x288"x0.0 27.00 1440 1464 1590 1728 288 290 293 312 -hsync -vsync (15.6 kHz) 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync nothing - blue screen (and now I know why since it's interlaced) 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync back to the original situation (two bands, flickering) 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync nothing - blue screen 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync three bands, flickering 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsyn
