[Intel-gfx] i915: crash with 5.19-rc2
Hello While somewhat oldish hw (T61, 4G, C2D) - I've now witnessed new crash with Xorg: (happened while reopening iconified Firefox window - running 'standard' rawhide -nodebug kernel 5.19.0-0.rc2.21.fc37.x86_64) page:577758b3 refcount:0 mapcount:0 mapping: index:0x1 pfn:0x1192cc flags: 0x17c000(node=0|zone=2|lastcpupid=0x1f) raw: 0017c000 e683c47171c8 8fa3f79377a8 raw: 0001 page dumped because: VM_BUG_ON_FOLIO(!folio_test_locked(folio)) [ cut here ] kernel BUG at mm/shmem.c:708! invalid opcode: [#1] PREEMPT SMP NOPTI CPU: 1 PID: 42896 Comm: Xorg Not tainted 5.19.0-0.rc2.21.fc37.x86_64 #1 Hardware name: LENOVO 6464CTO/6464CTO, BIOS 7LETC9WW (2.29 ) 03/18/2011 RIP: 0010:shmem_add_to_page_cache+0x48e/0x500 Code: 01 0f 84 0a fc ff ff 48 8d 4a ff 31 d2 48 39 cb 0f 85 ff fb ff ff e9 f6 fb ff ff 48 c7 c6 70 01 64 bb 48 89 df e8 f2 99 01 00 <0f> 0b 48 c7 c6 a0 1b 64 bb 48 89 df e8 e1 99 01 00 0f 0b 48 8b 13 RSP: 0018:9ce7c047f6b0 EFLAGS: 00010286 RAX: 003f RBX: e683c464b300 RCX: RDX: 0001 RSI: bb67b8e8 RDI: RBP: 00023f97 R08: bca122a0 R09: 64656b636f6c5f74 R10: 747365745f6f696c R11: 6f6621284f494c4f R12: 001120d4 R13: 8fa2c6ae7890 R14: e683c464b300 R15: 0001 FS: 7fc1cea31380() GS:8fa3f790() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6972e228c8 CR3: 000104ba8000 CR4: 06e0 Call Trace: shmem_swapin_folio+0x274/0x980 shmem_getpage_gfp+0x234/0x990 shmem_read_mapping_page_gfp+0x36/0xf0 shmem_sg_alloc_table+0x11b/0x250 [i915] shmem_get_pages+0xaa/0x310 [i915] __i915_gem_object_get_pages+0x31/0x40 [i915] i915_vma_pin_ww+0x69d/0x920 [i915] eb_validate_vmas+0x17d/0x7a0 [i915] ? eb_pin_engine+0x262/0x2d0 [i915] i915_gem_do_execbuffer+0xd43/0x2c00 [i915] ? refill_obj_stock+0x102/0x1a0 ? unix_stream_read_generic+0x1ea/0xa60 ? unix_stream_read_generic+0x1ea/0xa60 ? _raw_spin_lock_irqsave+0x23/0x50 ? _atomic_dec_and_lock_irqsave+0x38/0x60 ? __active_retire+0xb7/0x100 [i915] ? _raw_spin_unlock_irqrestore+0x23/0x40 ? dma_fence_signal+0x39/0x50 ? dma_resv_iter_walk_unlocked.part.0+0x164/0x170 i915_gem_execbuffer2_ioctl+0x115/0x270 [i915] ? i915_gem_do_execbuffer+0x2c00/0x2c00 [i915] drm_ioctl_kernel+0x9b/0x140 ? __check_object_size+0x47/0x260 drm_ioctl+0x21c/0x410 ? i915_gem_do_execbuffer+0x2c00/0x2c00 [i915] ? exit_to_user_mode_prepare+0x17d/0x1f0 __x64_sys_ioctl+0x8a/0xc0 do_syscall_64+0x58/0x80 ? syscall_exit_to_user_mode+0x17/0x40 ? do_syscall_64+0x67/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 RIP: 0033:0x7fc1cf28da9f Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 RSP: 002b:7ffe5f52e1c0 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 7ffe5f52e250 RCX: 7fc1cf28da9f RDX: 7ffe5f52e250 RSI: 40406469 RDI: 000d RBP: 000d R08: 7fc1ce938410 R09: 7fc1cf2fa4c0 R10: R11: 0246 R12: 55e2dde0d340 R13: 0114 R14: 7ffe5f52e250 R15: 7fc1cdc49000 Modules linked in: tls rfcomm snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter ip_tables bridge stp llc bnep binfmt_misc btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic snd_hda_codec_analog snd_hda_codec_generic iwl3945 iwlegacy coretemp kvm_intel mac80211 snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi libarc4 kvm iTCO_wdt snd_hda_codec intel_pmc_bxt iTCO_vendor_support snd_hda_core snd_hwdep snd_seq snd_seq_device cfg80211 irqbypass snd_pcm thinkpad_acpi pcspkr joydev i2c_i801 snd_timer i2c_smbus ledtrig_audio wmi_bmof r592 platform_profile snd memstick rfkill lpc_ich soundcore acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd grace sunrpc fuse zram i915 sdhci_pci cqhci sdhci drm_buddy drm_display_helper e1000e mmc_core cec serio_raw yenta_socket ttm wmi video ata_generic pata_acpi scsi_dh_rdac scsi_dh_emc scsi_dh_alua dm_multipath ---[ end trace ]--- RIP: 0010:shmem_add_to_page_cache+0x48e/0x500 Code: 01 0f 84 0a fc ff ff 48 8d 4a ff 31 d2 48 39 cb 0f 85 ff fb ff ff e9 f6 fb ff ff 48 c7 c6 70 01 64 bb 48 89 df e8 f2 99 01 00 <0f> 0b 48 c7 c6 a0 1b 64 bb 48 89 df e8 e1 99 01 00 0f 0b 48 8b 13 RSP: 0018:9ce7c047f6b0 EFLAGS: 00010286 RAX: 003f RBX: e683c464b300 RCX: RDX: 0001 RSI: bb67b8e8 RDI: ff
Re: [Intel-gfx] i915: crash with 5.19-rc2
Dne 22. 06. 22 v 22:46 Rodrigo Vivi napsal(a): Hi Zdenek, On Wed, Jun 22, 2022 at 01:18:42PM +0200, Zdenek Kabelac wrote: Hello While somewhat oldish hw (T61, 4G, C2D) - I've now witnessed new crash with Xorg: (happened while reopening iconified Firefox window - running 'standard' rawhide -nodebug kernel 5.19.0-0.rc2.21.fc37.x86_64) any bisect possible? if possible, could you please file a bug? https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs I know I know, the account requirement :/ also on main kernel bugzilla is probably better than the email here. Hi So far this bisect does not seem doable, since this crash happened after several days of uptime and so far happened just once (and I'm now already on -rc3). If I'll spot any more regular approach to hit this crash, I may try bisecting. Meanwhile I just hope, someone will get an idea what has changed recently (I'd not seen such crash with 5.18). Although I need to say that I'm witnessing some GPU restarts lately causing just some 'temporary hanging' of Xorg desktop, but that's not such a big deal. Zdenek
Re: [Intel-gfx] i915: crash with 5.19-rc2
Dne 22. 06. 22 v 13:18 Zdenek Kabelac napsal(a): Hello While somewhat oldish hw (T61, 4G, C2D) - I've now witnessed new crash with Xorg: (happened while reopening iconified Firefox window - running 'standard' rawhide -nodebug kernel 5.19.0-0.rc2.21.fc37.x86_64) Hello Ok, I think I now know what is behind this BUG/crash of intel graphics - interestingly it took me a few weeks to realize this. So I've actually installed with some Rawhide update 'zram-generator' package to use zram swap to help with memory of Firefox & Thunderbird a bit with this 4G RAM laptop. All worked fine. However side effect of usage of ZRAM swapping became actually this occasional kernel BUG hitting. When I've stopped using Zram swap - it now runs for 2 weeks without a single deadlock - with single or dual screen monitor setup with many suspends & resumes in between. So I'm likely 100% sure that ZRAM usage is triggering this issue. While I know this laptop is old and likely with low memory and so on - no sure if it's worth to solve it - maybe good enough solution is to issue a warning user should no comibine this old piece with ZRAM - but I'm all open to do some testing for fix - although I still don't have a simple triggering path for this issue to happen within short period of time. Maybe driver is missing tomark some pages as pined into memory so ZRAM can't swap them out ?. page:577758b3 refcount:0 mapcount:0 mapping: index:0x1 pfn:0x1192cc flags: 0x17c000(node=0|zone=2|lastcpupid=0x1f) raw: 0017c000 e683c47171c8 8fa3f79377a8 raw: 0001 page dumped because: VM_BUG_ON_FOLIO(!folio_test_locked(folio)) [ cut here ] kernel BUG at mm/shmem.c:708! invalid opcode: [#1] PREEMPT SMP NOPTI CPU: 1 PID: 42896 Comm: Xorg Not tainted 5.19.0-0.rc2.21.fc37.x86_64 #1 Hardware name: LENOVO 6464CTO/6464CTO, BIOS 7LETC9WW (2.29 ) 03/18/2011 RIP: 0010:shmem_add_to_page_cache+0x48e/0x500 Code: 01 0f 84 0a fc ff ff 48 8d 4a ff 31 d2 48 39 cb 0f 85 ff fb ff ff e9 f6 fb ff ff 48 c7 c6 70 01 64 bb 48 89 df e8 f2 99 01 00 <0f> 0b 48 c7 c6 a0 1b 64 bb 48 89 df e8 e1 99 01 00 0f 0b 48 8b 13 RSP: 0018:9ce7c047f6b0 EFLAGS: 00010286 RAX: 003f RBX: e683c464b300 RCX: RDX: 0001 RSI: bb67b8e8 RDI: RBP: 00023f97 R08: bca122a0 R09: 64656b636f6c5f74 R10: 747365745f6f696c R11: 6f6621284f494c4f R12: 001120d4 R13: 8fa2c6ae7890 R14: e683c464b300 R15: 0001 FS: 7fc1cea31380() GS:8fa3f790() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6972e228c8 CR3: 000104ba8000 CR4: 06e0 Call Trace: shmem_swapin_folio+0x274/0x980 shmem_getpage_gfp+0x234/0x990 shmem_read_mapping_page_gfp+0x36/0xf0 shmem_sg_alloc_table+0x11b/0x250 [i915] Regards Zdenek
[Intel-gfx] Regression on GMA965 - display seems to have slow jump changes in brightness
Hi I've updated to 3.4 kernel, and now I'm noticing slight changes in brightness on colorful images. It seems the change is mostly visibly on 'darker' images i.e. it's not really visible on white background. When I reboot back to 3.3 kernel - brightness changes are gone - so I do not suspect hw fault of my T61 display. I guess once in past there has been already such bug, so this problem seems to me like reintroducing the same problem again. xorg-x11-server-Xorg-1.12.1-1.fc18.x86_64 with SNA intel driver build from git repo. T61, 965GM Is this a know issue ? Is bisect needed ? Zdenek ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Regression on GMA965 - display seems to have slow jump changes in brightness
2012/5/22 Daniel Vetter : > On Tue, May 22, 2012 at 02:08:46PM +0200, Zdenek Kabelac wrote: >> Hi >> >> I've updated to 3.4 kernel, and now I'm noticing slight changes in >> brightness on colorful images. >> It seems the change is mostly visibly on 'darker' images i.e. it's >> not really visible on white background. >> >> When I reboot back to 3.3 kernel - brightness changes are gone - so I >> do not suspect hw fault of my T61 display. >> I guess once in past there has been already such bug, so this problem >> seems to me like reintroducing the same >> problem again. >> >> xorg-x11-server-Xorg-1.12.1-1.fc18.x86_64 >> with SNA intel driver build from git repo. >> T61, 965GM >> >> Is this a know issue ? >> Is bisect needed ? > > You're the first one to report things, so a bisect would be highly > appreciated. Also I'm a bit confused about what you mean by 'changing > brightness'. Can you please try to explain this a bit more? > I've some default gnome picture like this one: https://lh6.googleusercontent.com/-96ZhFbfLX_M/ThHsm0ZxBgI/FQQ/3ApjzYgulso/s400/gnome-3-login-screen.png When I watch the picture for some period of time I'm noticing slight changes in the picture brightness looking like small change in LUT table or something like that. If the picture is white I'm not noticing any change. (Initially I've thought my display dies - but reboot to 3.3 fixed the issue immediately). Is there any suspecting patch for this chipset I should try to revert ? Zdenek ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Regression on GMA965 - display seems to have slow jump changes in brightness
2012/5/22 Daniel Vetter :
> On Tue, May 22, 2012 at 04:36:30PM +0200, Zdenek Kabelac wrote:
>> 2012/5/22 Daniel Vetter :
>> > On Tue, May 22, 2012 at 02:08:46PM +0200, Zdenek Kabelac wrote:
>> >> Hi
>> >>
>> >> I've updated to 3.4 kernel, and now I'm noticing slight changes in
>> >> brightness on colorful images.
>> >> It seems the change is mostly visibly on 'darker' images i.e. it's
>> >> not really visible on white background.
>> >>
>> >> When I reboot back to 3.3 kernel - brightness changes are gone - so I
>> >> do not suspect hw fault of my T61 display.
>> >> I guess once in past there has been already such bug, so this problem
>> >> seems to me like reintroducing the same
>> >> problem again.
>> >>
>> >> xorg-x11-server-Xorg-1.12.1-1.fc18.x86_64
>> >> with SNA intel driver build from git repo.
>> >> T61, 965GM
>> >>
>> >> Is this a know issue ?
>> >> Is bisect needed ?
>> >
>> > You're the first one to report things, so a bisect would be highly
>> > appreciated. Also I'm a bit confused about what you mean by 'changing
>> > brightness'. Can you please try to explain this a bit more?
>> >
>>
>> I've some default gnome picture like this one:
>> https://lh6.googleusercontent.com/-96ZhFbfLX_M/ThHsm0ZxBgI/FQQ/3ApjzYgulso/s400/gnome-3-login-screen.png
>>
>> When I watch the picture for some period of time I'm noticing slight
>> changes in the picture brightness looking like small change in LUT
>> table or something like that.
>> If the picture is white I'm not noticing any change.
>> (Initially I've thought my display dies - but reboot to 3.3 fixed the
>> issue immediately).
>
> "for some period", does that mean it takes you a while to notice the
> changes (because they're tiny), or are the changes happend just rather slowly?
>
Deviation in picture is not huge - but gets noticeable by my eyes and
it's annoying,
it's like several seconds between each minor change.
If I've monotone background in i.e. text editor the change is
practically not visibible,
but if watch some digicam photos full screen they are quite obvious.
Not sure if that has any influence (not tested without) I'm using
some icc profile
('xcalib') to get away from blue of IBM display.
>> Is there any suspecting patch for this chipset I should try to revert ?
>
> Tbh I have no idea. If there's no changes when the picture is white, it
> can't be the backlight, we haven't frobbed around with the gamma stuff and
> temporal dithering is disabled, too. If you can bisect this it would
> greatly help.
ok, I'll play this game in the evening if there is nothing obvious.
Zdenek
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Regression on GMA965 - display seems to have slow jump changes in brightness
2012/5/22 Zdenek Kabelac :
> 2012/5/22 Daniel Vetter :
>> On Tue, May 22, 2012 at 04:36:30PM +0200, Zdenek Kabelac wrote:
>>> 2012/5/22 Daniel Vetter :
>>> > On Tue, May 22, 2012 at 02:08:46PM +0200, Zdenek Kabelac wrote:
>>> >> Hi
>>> >>
>>> >> I've updated to 3.4 kernel, and now I'm noticing slight changes in
>>> >> brightness on colorful images.
>>> >> It seems the change is mostly visibly on 'darker' images i.e. it's
>>> >> not really visible on white background.
>>> >>
>>> >> When I reboot back to 3.3 kernel - brightness changes are gone - so I
>>> >> do not suspect hw fault of my T61 display.
>>> >> I guess once in past there has been already such bug, so this problem
>>> >> seems to me like reintroducing the same
>>> >> problem again.
>>> >>
>>> >> xorg-x11-server-Xorg-1.12.1-1.fc18.x86_64
>>> >> with SNA intel driver build from git repo.
>>> >> T61, 965GM
>>> >>
>>> >> Is this a know issue ?
>>> >> Is bisect needed ?
>>> >
>>> > You're the first one to report things, so a bisect would be highly
>>> > appreciated. Also I'm a bit confused about what you mean by 'changing
>>> > brightness'. Can you please try to explain this a bit more?
>>> >
>>>
>>> I've some default gnome picture like this one:
>>> https://lh6.googleusercontent.com/-96ZhFbfLX_M/ThHsm0ZxBgI/FQQ/3ApjzYgulso/s400/gnome-3-login-screen.png
>>>
>>> When I watch the picture for some period of time I'm noticing slight
>>> changes in the picture brightness looking like small change in LUT
>>> table or something like that.
>>> If the picture is white I'm not noticing any change.
>>> (Initially I've thought my display dies - but reboot to 3.3 fixed the
>>> issue immediately).
>>
>> "for some period", does that mean it takes you a while to notice the
>> changes (because they're tiny), or are the changes happend just rather
>> slowly?
>>
>
> Deviation in picture is not huge - but gets noticeable by my eyes and
> it's annoying,
> it's like several seconds between each minor change.
>
> If I've monotone background in i.e. text editor the change is
> practically not visibible,
> but if watch some digicam photos full screen they are quite obvious.
>
> Not sure if that has any influence (not tested without) I'm using
> some icc profile
> ('xcalib') to get away from blue of IBM display.
>
>>> Is there any suspecting patch for this chipset I should try to revert ?
>>
>> Tbh I have no idea. If there's no changes when the picture is white, it
>> can't be the backlight, we haven't frobbed around with the gamma stuff and
>> temporal dithering is disabled, too. If you can bisect this it would
>> greatly help.
>
> ok, I'll play this game in the evening if there is nothing obvious.
>
And we have a winner - cec2f356d59d9e070413e5966a3c5a1af136d948
drm/i915: Only look for matching clocks for LVDS downclock
reverting just this patch for vanilla 3.4 fixes the problem for my T61.
(I've not tried to play with those individial 3 pieces inside this patch
to check exactly which one is responsible)
Zdenek
Here is the bisect game:
git bisect start
# bad: [acc73fb11695b564dc485b1f98f8237bbdc0742f] Remove ioctl warning
git bisect bad acc73fb11695b564dc485b1f98f8237bbdc0742f
# good: [c16fa4f2ad19908a47c63d8fa436a1178438c7e7] Linux 3.3
git bisect good c16fa4f2ad19908a47c63d8fa436a1178438c7e7
# bad: [141124c02059eee9dbc5c86ea797b1ca888e77f7] Delete all instances
of asm/system.h
git bisect bad 141124c02059eee9dbc5c86ea797b1ca888e77f7
# good: [3b59bf081622b6446db77ad06c93fe23677bc533] Merge
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next
git bisect good 3b59bf081622b6446db77ad06c93fe23677bc533
# good: [424a6f6ef990b7e9f56f6627bfc6c46b493faeb4] Merge tag
'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6
git bisect good 424a6f6ef990b7e9f56f6627bfc6c46b493faeb4
# bad: [be53bfdb8088e9d1924199cc1a96e113756b1075] Merge branch
'drm-next' of git://people.freedesktop.org/~airlied/linux
git bisect bad be53bfdb8088e9d1924199cc1a96e113756b1075
# good: [828006de1bddf83b6ecf03ec459c15f7c7c22db7] Merge tag
'asoc-3.4' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound
into topic/asoc
git bisect good 828006de1bddf83b6ecf03ec459c15f7c7c22db7
# skip: [496a73bbecb81e6753715995e4
Re: [Intel-gfx] Regression on GMA965 - display seems to have slow jump changes in brightness
2012/5/23 Sean Paul :
> On Tue, May 22, 2012 at 6:15 PM, Zdenek Kabelac
> wrote:
>> 2012/5/22 Zdenek Kabelac :
>>> 2012/5/22 Daniel Vetter :
>>>> On Tue, May 22, 2012 at 04:36:30PM +0200, Zdenek Kabelac wrote:
>>>>> 2012/5/22 Daniel Vetter :
>>>>> > On Tue, May 22, 2012 at 02:08:46PM +0200, Zdenek Kabelac wrote:
>>>>> >> Hi
>>>>> >>
>>>>> >> I've updated to 3.4 kernel, and now I'm noticing slight changes in
>>>>> >> brightness on colorful images.
>>>>> >> It seems the change is mostly visibly on 'darker' images i.e. it's
>>>>> >> not really visible on white background.
>>>>> >>
>>>>> >> When I reboot back to 3.3 kernel - brightness changes are gone - so I
>>>>> >> do not suspect hw fault of my T61 display.
>>>>> >> I guess once in past there has been already such bug, so this problem
>>>>> >> seems to me like reintroducing the same
>>>>> >> problem again.
>>>>> >>
>>>>> >> xorg-x11-server-Xorg-1.12.1-1.fc18.x86_64
>>>>> >> with SNA intel driver build from git repo.
>>>>> >> T61, 965GM
>>>>> >>
>>>>> >> Is this a know issue ?
>>>>> >> Is bisect needed ?
>>>>> >
>>>>> > You're the first one to report things, so a bisect would be highly
>>>>> > appreciated. Also I'm a bit confused about what you mean by 'changing
>>>>> > brightness'. Can you please try to explain this a bit more?
>>>>> >
>>>>>
>>>>> I've some default gnome picture like this one:
>>>>> https://lh6.googleusercontent.com/-96ZhFbfLX_M/ThHsm0ZxBgI/FQQ/3ApjzYgulso/s400/gnome-3-login-screen.png
>>>>>
>>>>> When I watch the picture for some period of time I'm noticing slight
>>>>> changes in the picture brightness looking like small change in LUT
>>>>> table or something like that.
>>>>> If the picture is white I'm not noticing any change.
>>>>> (Initially I've thought my display dies - but reboot to 3.3 fixed the
>>>>> issue immediately).
>>>>
>>>> "for some period", does that mean it takes you a while to notice the
>>>> changes (because they're tiny), or are the changes happend just rather
>>>> slowly?
>>>>
>>>
>>> Deviation in picture is not huge - but gets noticeable by my eyes and
>>> it's annoying,
>>> it's like several seconds between each minor change.
>>>
>>> If I've monotone background in i.e. text editor the change is
>>> practically not visibible,
>>> but if watch some digicam photos full screen they are quite obvious.
>>>
>>> Not sure if that has any influence (not tested without) I'm using
>>> some icc profile
>>> ('xcalib') to get away from blue of IBM display.
>>>
>>>>> Is there any suspecting patch for this chipset I should try to revert ?
>>>>
>>>> Tbh I have no idea. If there's no changes when the picture is white, it
>>>> can't be the backlight, we haven't frobbed around with the gamma stuff and
>>>> temporal dithering is disabled, too. If you can bisect this it would
>>>> greatly help.
>>>
>>> ok, I'll play this game in the evening if there is nothing obvious.
>>>
>>
>> And we have a winner - cec2f356d59d9e070413e5966a3c5a1af136d948
>>
>
> Hmm, seems like your display doesn't like to be downclocked, or rather
> you don't like it to be downclocked :) The reason this patch triggered
> it is because it does a better job of finding a compatible clock. You
> can disable lvds downclocking on the kernel command line by setting
> i915.lvds_downclock=0
>
Hmm I've been using i915.lvds_downclock=1 on grub command line, and
haven't noticed any visible problems with 3.3 kernel. So I'd rather
ask if the problematic patch isn't doing downclocking in a wrong way?
Or maybe detection that downclocking is not supported properly is not
correct now ?
Zdenek
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Regression on GMA965 - display seems to have slow jump changes in brightness
2012/5/23 Daniel Vetter : > On Wed, May 23, 2012 at 09:07:28AM +0200, Daniel Vetter wrote: >> On Wed, May 23, 2012 at 08:59:07AM +0200, Zdenek Kabelac wrote: >> > Hmm I've been using i915.lvds_downclock=1 on grub command line, and >> > haven't noticed any visible problems with 3.3 kernel. So I'd rather >> > ask if the problematic patch isn't doing downclocking in a wrong way? >> > Or maybe detection that downclocking is not supported properly is not >> > correct now ? >> >> Nope, Sean's analysis is pretty much correct, that patch only makes >> downclocking possible in more circumstances. And downclocking can >> certainly explain what you're seeing, the backlight pwm signal is driven >> off the panel dotclock, so if we change that we can very likely cause some >> funny interference. I guess we could frob the backligth control settings >> and adjust them for the change in clockspeed, but the current backlight >> code is a bit a mess. So right now I suggest you just drop that option - >> there are reasons it's not the default ;-) > > Quick question: What's the frequency of the brightness change? And how > regular are the changes? > -Daniel Now when it's obvious it's related to powersaving - it's probably much easier to explain, that I've been observing those changes when some activity was happing - i.e. opening picture - and after like 1 second image has flashed, - then I've moved the mouse stopped - and again image has flashed with brightness a bit. The issue would be probably far less noticeable if the period of time of idle GPU would have to be much longer (i.e. in minute range) Zdenek ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] SNA crashes
Hi
Since I've started to use SNA driver (when UXA appeared to be very
slow), I'm facing higher number of Xorg crashes.
SNA is faster, but less stable then UXA is.
So I'll start posting backtraces since I've recompiled driver with
--enable-debug.
They all happend with stock 3.4 kernel and
xorg-x11-server-Xorg-1.12.1-1.fc18.x86_64
I'm not really sure if that's important - but usually typing in pidgin
window is highly risky operation,
since typically when I need to write something 'important' my screen
goes to black.
My system is T61, GMA965
Zdenek
git commit for SNA driver in use: fb9da4cb9e12ca733c31879b8b37906f361a8c35
#0 0x7f96025f7935 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
64return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) bt
#0 0x7f96025f7935 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x7f96025f90e8 in __GI_abort () at abort.c:91
#2 0x7f96025f06b2 in __assert_fail_base (fmt=0x7f960273a408
"%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
assertion=assertion@entry=0x7f96009e743b "!kgem->wedged",
file=file@entry=0x7f96009e6f15 "kgem.h", line=line@entry=295,
function=function@entry=0x7f96009ec795 "kgem_set_mode") at assert.c:94
#3 0x7f96025f0762 in __GI___assert_fail
(assertion=assertion@entry=0x7f96009e743b "!kgem->wedged",
file=file@entry=0x7f96009e6f15 "kgem.h", line=line@entry=295,
function=function@entry=0x7f96009ec795 "kgem_set_mode")
at assert.c:103
#4 0x7f960099b619 in kgem_set_mode (kgem=0x7f9604693218,
mode=) at kgem.h:295
#5 gen4_get_batch (sna=sna@entry=0x7f9604693010) at gen4_render.c:1303
#6 0x7f960099c5e3 in gen4_bind_surfaces
(sna=sna@entry=0x7f9604693010, op=op@entry=0x7fff4fb65580) at
gen4_render.c:1505
#7 0x7f96009a03dd in gen4_render_composite (tmp=0x7fff4fb65580,
height=28, width=2, dst_y=0, dst_x=21968, msk_y=0,
msk_x=0, src_y=0, src_x=0, dst=0x47ffea0, mask=,
src=0x4b97190, op=, sna=0x7f9604693010)
at gen4_render.c:2512
#8 gen4_render_composite (sna=0x7f9604693010, op=,
src=0x4b97190, mask=, dst=0x47ffea0,
src_x=0, src_y=0, msk_x=0, msk_y=0, dst_x=21, dst_y=105, width=2,
height=28, tmp=0x7fff4fb65580) at gen4_render.c:2351
#9 0x7f960095c301 in sna_composite (op=3 '\003', src=0x4b97190,
mask=0x0, dst=0x47ffea0, src_x=0, src_y=0, mask_x=0,
mask_y=0, dst_x=21, dst_y=105, width=2, height=28) at sna_composite.c:504
#10 0x005019f9 in damageComposite (op=3 '\003',
pSrc=0x4b97190, pMask=0x0, pDst=0x47ffea0, xSrc=0, ySrc=0, xMask=0,
yMask=0, xDst=21, yDst=105, width=2, height=28) at damage.c:562
#11 0x004fa964 in ProcRenderComposite (client=0x2a0e6f0) at render.c:707
#12 0x004343ba in Dispatch () at dispatch.c:425
#13 0x00423405 in main (argc=4, argv=0x7fff4fb65a28,
envp=) at main.c:288
(same as above with full)
(gdb) bt full
#0 0x7f96025f7935 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
resultvar = 0
pid = 3805
selftid = 3805
#1 0x7f96025f90e8 in __GI_abort () at abort.c:91
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x7fff4fb6655f,
sa_sigaction = 0x7fff4fb6655f}, sa_mask = {__val = {
140282262944941, 140282232205077, 295, 28,
140282261610737, 105, 4294967253, 17179869184, 4, 140734530736752,
0, 0, 0, 140282262944747, 140282296639488,
140282262955016}}, sa_flags = 10384443,
sa_restorer = 0x7f96009ec795 <__PRETTY_FUNCTION__.19690>}
sigs = {__val = {32, 0 }}
#2 0x7f96025f06b2 in __assert_fail_base (fmt=0x7f960273a408
"%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
assertion=assertion@entry=0x7f96009e743b "!kgem->wedged",
file=file@entry=0x7f96009e6f15 "kgem.h", line=line@entry=295,
function=function@entry=0x7f96009ec795 "kgem_set_mode") at assert.c:94
str = 0x2fe18b0 ""
total = 4096
#3 0x7f96025f0762 in __GI___assert_fail
(assertion=assertion@entry=0x7f96009e743b "!kgem->wedged",
file=file@entry=0x7f96009e6f15 "kgem.h", line=line@entry=295,
function=function@entry=0x7f96009ec795 "kgem_set_mode")
at assert.c:103
No locals.
#4 0x7f960099b619 in kgem_set_mode (kgem=0x7f9604693218,
mode=) at kgem.h:295
No locals.
#5 gen4_get_batch (sna=sna@entry=0x7f9604693010) at gen4_render.c:1303
No locals.
#6 0x7f960099c5e3 in gen4_bind_surfaces
(sna=sna@entry=0x7f9604693010, op=op@entry=0x7fff4fb65580) at
gen4_render.c:1505
binding_table =
offset =
#7 0x7f96009a03dd in gen4_render_composite (tmp=0x7fff4fb65580,
height=28, width=2, dst_y=0, dst_x=21968, msk_y=0,
msk_x=0, src_y=0, src_x=0, dst=0x47ffea0, mask=,
src=0x4b97190, op=, sna=0x7f9604693010)
at gen4_render.c:2512
No locals.
---
another one:
#0 0x7f47fedde935 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
64return IN
Re: [Intel-gfx] Regression on GMA965 - display seems to have slow jump changes in brightness
2012/5/23 Daniel Vetter : > On Wed, May 23, 2012 at 01:48:41PM +0200, Zdenek Kabelac wrote: >> 2012/5/23 Daniel Vetter : >> > On Wed, May 23, 2012 at 09:07:28AM +0200, Daniel Vetter wrote: >> >> On Wed, May 23, 2012 at 08:59:07AM +0200, Zdenek Kabelac wrote: >> >> > Hmm I've been using i915.lvds_downclock=1 on grub command line, and >> >> > haven't noticed any visible problems with 3.3 kernel. So I'd rather >> >> > ask if the problematic patch isn't doing downclocking in a wrong way? >> >> > Or maybe detection that downclocking is not supported properly is not >> >> > correct now ? >> >> >> >> Nope, Sean's analysis is pretty much correct, that patch only makes >> >> downclocking possible in more circumstances. And downclocking can >> >> certainly explain what you're seeing, the backlight pwm signal is driven >> >> off the panel dotclock, so if we change that we can very likely cause some >> >> funny interference. I guess we could frob the backligth control settings >> >> and adjust them for the change in clockspeed, but the current backlight >> >> code is a bit a mess. So right now I suggest you just drop that option - >> >> there are reasons it's not the default ;-) >> > >> > Quick question: What's the frequency of the brightness change? And how >> > regular are the changes? >> > -Daniel >> >> >> Now when it's obvious it's related to powersaving - it's probably >> much easier to explain, >> that I've been observing those changes when some activity was happing - >> i.e. opening picture - and after like 1 second image has flashed, - >> then I've moved the mouse >> stopped - and again image has flashed with brightness a bit. >> >> The issue would be probably far less noticeable if the period of time >> of idle GPU would have to be >> much longer (i.e. in minute range) > > Hm, that sounds more like something ugly is happening when we switch > frequencies as opposed to the different frequency causing interference > with the backlight. Just to check: You only see a quick flash, then > brightness is back to normal? In fact I'm not really noticing the moment it goes back to normal - I'll notice when it gets darker. i.e. when I open picture with 'qiv' - after a second I notice that picture becomes a bit darker. If I do not move with anything - it stays this way. > > If that's the case, please try Chris' fastboot branch. vsyncing the > frequency change might indeed fix this. > I've tried to compile, but compilation finished with some errors - so I've tried to rebase branch on master 3.4 - tried to resolve some error - but probably in a wrong thus resulted kernel given me just black screen when X has been initialized. So I'll try to remove some config options and I'll try to rebuild original fastboot branch later. Zdenek ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] SNA crashes
2012/5/24 Chris Wilson : > On Thu, 24 May 2012 16:15:41 +0200, Zdenek Kabelac > wrote: >> Hi >> >> Since I've started to use SNA driver (when UXA appeared to be very >> slow), I'm facing higher number of Xorg crashes. >> SNA is faster, but less stable then UXA is. > > They are all debugging assertions caused by the earlier GPU hang, to > catch instances were we are losing commands and thus potentially > corrupting the output due to the loss of the GPU. Tip, don't hang the > GPU or don't ask for the bt. > -Chris > > -- Ok - I think I've figured out relatively simple way to trigger this issue on my machine. I'll also probably provide a list of memleaks which popped out and other sets of problem. So I just have to run Xorg server with valgrind and run couple programs. What I've not yet figured out is - if the is really fault of intel driver - or synaptic handle (which seems to have higher probability) Anyway - here is the log from valgring just in the moment of kernel reported GPU hang. Process terminating with default action of signal 11 (SIGSEGV): dumping core General Protection Fault at 0x6B23165: __sprintf_chk (sprintf_chk.c:27) by 0x468E0C: LogVWrite (stdio2.h:34) by 0x468B3B: ErrorF (log.c:641) by 0x550765: mieqEnqueue (mieq.c:280) by 0x447F01: queueEventList (getevents.c:974) by 0x48F9CF: xf86PostMotionEvent (xf86Xinput.c:1045) by 0xB294D14: HandleState (synaptics.c:3370) by 0xB296D91: ReadInput (synaptics.c:1721) by 0x480206: xf86SigioReadInput (xf86Events.c:298) by 0x4A439F: xf86SIGIO (sigio.c:108) by 0x582054F: ??? (in /usr/lib64/libpthread-2.15.90.so) by 0x6B06316: ioctl (syscall-template.S:81) by 0x8775807: drmIoctl (xf86drm.c:167) by 0x8777B55: drmCommandNone (xf86drm.c:2357) by 0x8BBC84F: kgem_throttle (kgem.c:1924) by 0x8BE4A16: sna_accel_block_handler (sna_accel.c:12069) by 0x438149: BlockHandler (dixutils.c:387) by 0x462313: WaitForSomething (WaitFor.c:210) by 0x434080: Dispatch (dispatch.c:357) by 0x423404: main (main.c:288) (using git 8ea4ba081de0206351394481f54dcbe6922a085b for intel driver (to match code lines)) I'm unsure how the handling of synaptic events and mouse cursor movement are related together. Is there something I should enable for kernel part of intel driver to get better explanation for GPU hang ? Zdenek ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] SNA crashes
2012/5/27 Zdenek Kabelac : > 2012/5/24 Chris Wilson : >> On Thu, 24 May 2012 16:15:41 +0200, Zdenek Kabelac >> wrote: >>> Hi >>> >>> Since I've started to use SNA driver (when UXA appeared to be very >>> slow), I'm facing higher number of Xorg crashes. >>> SNA is faster, but less stable then UXA is. >> >> They are all debugging assertions caused by the earlier GPU hang, to >> catch instances were we are losing commands and thus potentially >> corrupting the output due to the loss of the GPU. Tip, don't hang the >> GPU or don't ask for the bt. >> -Chris >> >> -- > > > Ok - I think I've figured out relatively simple way to trigger this > issue on my machine. > I'll also probably provide a list of memleaks which popped out and > other sets of problem. > > So I just have to run Xorg server with valgrind and run couple programs. > What I've not yet figured out is - if the is really fault of intel > driver - or synaptic handle > (which seems to have higher probability) > > Anyway - here is the log from valgring just in the moment of kernel > reported GPU hang. > > Process terminating with default action of signal 11 (SIGSEGV): dumping core > General Protection Fault > at 0x6B23165: __sprintf_chk (sprintf_chk.c:27) > by 0x468E0C: LogVWrite (stdio2.h:34) > by 0x468B3B: ErrorF (log.c:641) > by 0x550765: mieqEnqueue (mieq.c:280) > by 0x447F01: queueEventList (getevents.c:974) > by 0x48F9CF: xf86PostMotionEvent (xf86Xinput.c:1045) > by 0xB294D14: HandleState (synaptics.c:3370) > by 0xB296D91: ReadInput (synaptics.c:1721) > by 0x480206: xf86SigioReadInput (xf86Events.c:298) > by 0x4A439F: xf86SIGIO (sigio.c:108) > by 0x582054F: ??? (in /usr/lib64/libpthread-2.15.90.so) > by 0x6B06316: ioctl (syscall-template.S:81) > by 0x8775807: drmIoctl (xf86drm.c:167) > by 0x8777B55: drmCommandNone (xf86drm.c:2357) > by 0x8BBC84F: kgem_throttle (kgem.c:1924) > by 0x8BE4A16: sna_accel_block_handler (sna_accel.c:12069) > by 0x438149: BlockHandler (dixutils.c:387) > by 0x462313: WaitForSomething (WaitFor.c:210) > by 0x434080: Dispatch (dispatch.c:357) > by 0x423404: main (main.c:288) > > (using git 8ea4ba081de0206351394481f54dcbe6922a085b for intel driver > (to match code lines)) > > I'm unsure how the handling of synaptic events and mouse cursor > movement are related together. > > Is there something I should enable for kernel part of intel driver to > get better explanation for GPU hang ? > So to make tracking easier: https://bugs.freedesktop.org/show_bug.cgi?id=50393 Looks like drm-intel-next fixes the problem. Zdenek ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] kernel BUG at drivers/gpu/drm/i915/i915_gem.c:3459
Hi This happened to today probably in the moment, LCD was turned off by Xserver as a screenblank My hw is Lenovo T61 4GB, intel driver. Seem to be related to: https://bbs.archlinux.org/viewtopic.php?id=124900 However my machine is good old C2D - no SandyBridge in my case. xorg-x11-drv-intel-2.16.0-2.fc17.x86_64 xorg-x11-server-Xorg-1.10.99.902-1.20110818.fc17.x86_64 3.1.0-rc5 (with my 8 unrelated patches) kernel BUG at drivers/gpu/drm/i915/i915_gem.c:3459! invalid opcode: [#1] PREEMPT SMP CPU 1 Modules linked in: nls_iso8859_1 nls_cp1250 vfat fat dm_zero dm_mirror dm_region_hash dm_log dm_snapshot cryptd crypto_hash crypto_wq crypto_blkcipher aes_x86_64 aes_generic dm_raid raid1 raid456 md_mod async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx i915 drm_kms_helper drm i2c_algo_bit lockd sunrpc snd_hda_codec_analog cryptomgr aead arc4 crypto_algapi iwl3945 iwl_legacy mac80211 usbhid snd_hda_intel hid snd_hda_codec snd_pcm cfg80211 binfmt_misc psmouse e1000e snd_timer serio_raw i2c_i801 iTCO_wdt thinkpad_acpi i2c_core snd iTCO_vendor_support snd_page_alloc soundcore wmi nvram evdev dm_mod loop virtio_net kvm_intel kvm uinput ipv6 autofs4 mmc_block pcmcia uhci_hcd ehci_hcd yenta_socket sdhci_pci sdhci mmc_core sr_mod cdrom usbcore video backlight Pid: 1029, comm: X Not tainted 3.1.0-rc5-8-gedaa057 #11 LENOVO 6464CTO/6464CTO RIP: 0010:[] [] i915_gem_object_unpin+0xab/0xb0 [i915] RSP: 0018:880130db3b98 EFLAGS: 00010246 RAX: 880128ea9000 RBX: 880128d7d800 RCX: 0006 RDX: 00020427 RSI: 88012d73a000 RDI: 880119ca8600 RBP: 880130db3b98 R08: R09: R10: R11: R12: 880128ea9068 R13: 880128ea9920 R14: R15: 8800283ec300 FS: 7fb25ca178a0() GS:88013bc0() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 7fb258d65982 CR3: 000133746000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process X (pid: 1029, threadinfo 880130db2000, task 88012d53a350) Stack: 880130db3bb8 a0498ffb 880128d7d800 a04efda0 880130db3be8 a02567d5 0001 880128d7d800 880130db3ca8 880128ea98f0 880130db3c98 a025805b Call Trace: [] intel_crtc_disable+0x4b/0x60 [i915] [] drm_helper_disable_unused_functions+0x115/0x190 [drm_kms_helper] [] drm_crtc_helper_set_config+0x8db/0x9f0 [drm_kms_helper] [] ? mark_held_locks+0x86/0x150 [] drm_framebuffer_cleanup+0xce/0x100 [drm] [] intel_user_framebuffer_destroy+0x21/0x70 [i915] [] drm_mode_rmfb+0xd3/0x130 [drm] [] drm_ioctl+0x3d4/0x4b0 [drm] [] ? drm_mode_addfb+0x180/0x180 [drm] [] ? sub_preempt_count+0xa9/0xe0 [] ? __srcu_read_unlock+0x41/0x70 [] ? fsnotify+0x282/0x5b0 [] ? fsnotify+0x93/0x5b0 [] do_vfs_ioctl+0x98/0x570 [] ? fget_light+0x340/0x3a0 [] sys_ioctl+0x91/0xa0 [] system_call_fastpath+0x16/0x1b Code: 00 48 89 96 f8 19 00 00 48 81 c6 f0 19 00 00 48 89 b7 b0 00 00 00 48 89 87 b8 00 00 00 48 89 10 80 a7 e2 00 00 00 f7 5d c3 0f 0b <0f> 0b 0f 1f 00 55 48 89 e5 48 81 ec c0 00 00 00 48 89 5d d8 4c RIP [] i915_gem_object_unpin+0xab/0xb0 [i915] RSP INFO: task X:1029 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. X D 0 1029 1028 0x0040 880130db35e8 0046 814b3b40 0046 88012d53a350 880130db3fd8 880130db3fd8 880130db3fd8 8801371446a0 88012d53a350 Call Trace: [] ? schedule+0x920/0xb10 [] mutex_lock_nested+0x1a1/0x3d0 [] ? drm_fb_helper_pan_display+0x39/0xe0 [drm_kms_helper] [] ? drm_fb_helper_pan_display+0x39/0xe0 [drm_kms_helper] [] drm_fb_helper_pan_display+0x39/0xe0 [drm_kms_helper] [] fb_pan_display+0xce/0x190 [] bit_update_start+0x29/0x60 [] fbcon_switch+0x390/0x540 [] redraw_screen+0x179/0x280 [] fbcon_blank+0x21a/0x2d0 [] ? _raw_spin_unlock_irqrestore+0x38/0x80 [] ? sub_preempt_count+0xa9/0xe0 [] ? _raw_spin_unlock_irqrestore+0x42/0x80 [] ? mod_timer+0x13f/0x430 [] do_unblank_screen+0xc4/0x1f0 [] unblank_screen+0x10/0x20 [] bust_spinlocks+0x1d/0x40 [] oops_end+0x40/0xf0 [] die+0x58/0x90 [] do_trap+0xc4/0x170 [] do_invalid_op+0x95/0xb0 [] ? i915_gem_object_unpin+0xab/0xb0 [i915] [] ? trace_hardirqs_off_thunk+0x3a/0x3c [] ? restore_args+0x30/0x30 [] invalid_op+0x15/0x20 [] ? i915_gem_object_unpin+0xab/0xb0 [i915] [] intel_crtc_disable+0x4b/0x60 [i915] [] drm_helper_disable_unused_functions+0x115/0x190 [drm_kms_helper] [] drm_crtc_helper_set_config+0x8db/0x9f0 [drm_kms_helper] [] ? mark_held_locks+0x86/0x150 [] drm_framebuffer_cleanup+0xce/0x100 [drm] [] intel_user_framebuffer_destroy+0x21/0x70 [i915] [] drm_mode_rmfb+0xd3/0x130 [drm] [] drm_ioctl+0x3d4/0x
Re: [Intel-gfx] kernel BUG at drivers/gpu/drm/i915/i915_gem.c:3459
2011/9/8 Keith Packard : > On Wed, 7 Sep 2011 22:50:02 +0200, Zdenek Kabelac > wrote: >> Hi >> >> This happened to today probably in the moment, LCD was turned off by >> Xserver as a screenblank >> My hw is Lenovo T61 4GB, intel driver. > > Can you describe what your desktop software environment looks like? Are > you running mutter, or compiz or some other compositing window manager? > Were you running a full-screen game? In other words, could you have been > hitting the page-flipping paths with a full-screen 3D application? > Hard to tell whether it's desktop environment - but it's so called Gnome3. Desktop/CPU was mostly idle - maybe some Firefox animation running on the screen, but yes it's full-screen 3d desktop. Zdenek ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] WARNING: at drivers/gpu/drm/i915/intel_display.c:792
Hi My Xorg server on rawhide machine is giving me sudden X lockups with 3.1 kernel. There might be couple issue related together as rawhide is now using some experimental Xorg server - but the message from kernel is a bit scary - so reposting to lkml as well. xorg-x11-server-Xorg-1.11.99.1-6.2009.fc17.x86_64 git intel driver: 3b9479dc39d32fd97f80c1e5e0fac67d36ee5e40 drm version (a bit older): 8d055890d90c3d92647e3d8b98d32630ef87c2c8 (since current Fedora rawhide intel driver is so much broken it doesn't even start) Running desktop with only a plain twm (no gnome-shell3 - broken to unusability as well). Happened with just some mouse movement. Might be related to https://bugzilla.redhat.com/show_bug.cgi?id=753703 My HW: Lenovo T61, gma965, 4GB, x86_64 Zdenek [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state [drm:init_ring_common] *ERROR* render ring initialization failed ctl head tail start [drm] Changing LVDS panel from (+hsync, +vsync) to (-hsync, -vsync) [ cut here ] WARNING: at drivers/gpu/drm/i915/intel_display.c:792 intel_enable_pipe+0x14a/0x150 [i915]() Hardware name: 6464CTO PLL state assertion failure (expected on, current off) Modules linked in: vfat fat isofs i915 drm_kms_helper drm i2c_algo_bit ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables tun bridge stp llc lockd sunrpc snd_hda_codec_analog cryptomgr aead arc4 crypto_algapi iwl3945 iwl_legacy mac80211 psmouse iTCO_wdt usbhid serio_raw i2c_i801 hid i2c_core snd_hda_intel snd_hda_codec cfg80211 iTCO_vendor_support e1000e snd_pcm snd_timer thinkpad_acpi snd snd_page_alloc soundcore wmi nvram binfmt_misc evdev loop virtio_net kvm_intel kvm uinput dm_mod ipv6 autofs4 pcmcia ehci_hcd uhci_hcd sdhci_pci sdhci yenta_socket mmc_core usbcore sr_mod cdrom video backlight Pid: 24480, comm: kworker/u:0 Not tainted 3.1.0-8-gba92ff5 #17 Call Trace: [] warn_slowpath_common+0x7f/0xc0 [] warn_slowpath_fmt+0x46/0x50 [] intel_enable_pipe+0x14a/0x150 [i915] [] i9xx_crtc_mode_set+0x6f1/0xd70 [i915] [] intel_crtc_mode_set+0x6f/0xa0 [i915] [] drm_crtc_helper_set_mode+0x32c/0x4d0 [drm_kms_helper] [] ? i915_driver_device_is_agp+0x10/0x10 [i915] [] drm_helper_resume_force_mode+0x73/0x160 [drm_kms_helper] [] ? i915_driver_device_is_agp+0x10/0x10 [i915] [] i915_reset+0x526/0x12c0 [i915] [] ? i915_driver_device_is_agp+0x10/0x10 [i915] [] i915_error_work_func+0xc8/0x110 [i915] [] process_one_work+0x18b/0x6e0 [] ? process_one_work+0x12a/0x6e0 [] ? retint_restore_args+0xe/0xe [] worker_thread+0x15f/0x350 [] ? rescuer_thread+0x240/0x240 [] kthread+0x9b/0xa0 [] kernel_thread_helper+0x4/0x10 [] ? finish_task_switch+0x7c/0x120 [] ? _raw_spin_unlock_irq+0x3b/0x60 [] ? retint_restore_args+0xe/0xe [] ? __init_kthread_worker+0x70/0x70 [] ? gs_change+0xb/0xb ---[ end trace 63d388f543b49f36 ]--- [ cut here ] WARNING: at drivers/gpu/drm/i915/intel_display.c:916 assert_pipe+0x75/0x80 [i915]() Hardware name: 6464CTO pipe B assertion failure (expected on, current off) Modules linked in: vfat fat isofs i915 drm_kms_helper drm i2c_algo_bit ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables tun bridge stp llc lockd sunrpc snd_hda_codec_analog cryptomgr aead arc4 crypto_algapi iwl3945 iwl_legacy mac80211 psmouse iTCO_wdt usbhid serio_raw i2c_i801 hid i2c_core snd_hda_intel snd_hda_codec cfg80211 iTCO_vendor_support e1000e snd_pcm snd_timer thinkpad_acpi snd snd_page_alloc soundcore wmi nvram binfmt_misc evdev loop virtio_net kvm_intel kvm uinput dm_mod ipv6 autofs4 pcmcia ehci_hcd uhci_hcd sdhci_pci sdhci yenta_socket mmc_core usbcore sr_mod cdrom video backlight Pid: 24480, comm: kworker/u:0 Tainted: GW 3.1.0-8-gba92ff5 #17 Call Trace: [] warn_slowpath_common+0x7f/0xc0 [] warn_slowpath_fmt+0x46/0x50 [] assert_pipe+0x75/0x80 [i915] [] intel_enable_plane+0x36/0x90 [i915] [] i9xx_crtc_mode_set+0x72d/0xd70 [i915] [] intel_crtc_mode_set+0x6f/0xa0 [i915] [] drm_crtc_helper_set_mode+0x32c/0x4d0 [drm_kms_helper] [] ? i915_driver_device_is_agp+0x10/0x10 [i915] [] drm_helper_resume_force_mode+0x73/0x160 [drm_kms_helper] [] ? i915_driver_device_is_agp+0x10/0x10 [i915] [] i915_reset+0x526/0x12c0 [i915] [] ? i915_driver_device_is_agp+0x10/0x10 [i915] [] i915_error_work_func+0xc8/0x110 [i915] [] process_one_work+0x18b/0x6e0 [] ? process_one_work+0x12a/0x6e0 [] ? retint_restore_args+0xe/0xe [] worker_thread+0x15f/0x350 [] ? rescuer_thread+0x240/0x240 [] kthread+0x9b/0xa0 [] kernel_thread_helper+0x4/0x10 [] ? finish_task_switch+0x7c/0x120 [] ? _raw_spin_unlock_irq
Re: [Intel-gfx] WARNING: at drivers/gpu/drm/i915/intel_display.c:792
2011/11/21 Zdenek Kabelac : > Hi > > My Xorg server on rawhide machine is giving me sudden X lockups with 3.1 > kernel. > There might be couple issue related together as rawhide is now using > some experimental > Xorg server - but the message from kernel is a bit scary - so > reposting to lkml as well. > > xorg-x11-server-Xorg-1.11.99.1-6.2009.fc17.x86_64 > git intel driver: 3b9479dc39d32fd97f80c1e5e0fac67d36ee5e40 > drm version (a bit older): 8d055890d90c3d92647e3d8b98d32630ef87c2c8 > (since current Fedora rawhide intel driver is so much broken it > doesn't even start) > It's worth to mention - it happens also with kernel 3.0 and the latest updated libdrm (ca4971292cf99e0063416cd1c3467af94637bf2b) The processing of mouse event seems to be always mandatory (i.e. it blacks LCD with some mouse movement). Zdenek ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Regressions in resume on intel graphics
2010/11/12 Zdenek Kabelac : > Hi > > I've noticed that after resume with 2.6.36 kernel I need to switch > between console and back to Xorg to get usable Xsession again. > (my hw - T61, gma965, 4GB) > > I've played bisect game - and this is the first broken kernel: > > --- > commit 8fd4bd22350784d5b2fe9274f6790ba353976415 > Author: Jesse Barnes > Date: Wed Jun 23 12:56:12 2010 -0700 > > vt/console: try harder to print output when panicing > --- I've been able to boot and test with 2.6.37-rc1-00170-gf6614b7 - and this problem seems to be fixed in this version (vt.c file seems to be gone?). > > Also I'd like to increase focus on another suspend/resume killer (at > least on my T61) > https://bugzilla.kernel.org/show_bug.cgi?id=19052 > https://bugzilla.redhat.com/show_bug.cgi?id=617809 > With kernel 2.6.37-rc1-00170-gf6614b7 message has changed (with enabled polling thread) -- [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged! [drm:i915_reset] *ERROR* Failed to reset chip. X[1378]: segfault at 0 ip 7f33409c727d sp 7fff930e7120 error 4 in intel_drv.so[7f334099+4a000] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero. -- But I can't be sure about whether it's the same bug - as display seems to be enabled for a second after resume. and then just everything crashes.. - with original EIR bug 19052 - my display remains completely black I'm using Fedora Rawhide Xorg & driver: xorg-x11-server-Xorg-1.9.1-3.fc15.x86_64 xorg-x11-drv-intel-2.12.0-8.fc15.x86_64 Zdenek ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Regressions in resume on intel graphics
2010/11/19 Jesse Barnes : > On Fri, 12 Nov 2010 10:17:07 +0100 > Zdenek Kabelac wrote: > >> 2010/11/12 Zdenek Kabelac : >> > Hi >> > >> > I've noticed that after resume with 2.6.36 kernel I need to switch >> > between console and back to Xorg to get usable Xsession again. >> > (my hw - T61, gma965, 4GB) >> > >> > I've played bisect game - and this is the first broken kernel: >> > >> > --- >> > commit 8fd4bd22350784d5b2fe9274f6790ba353976415 >> > Author: Jesse Barnes >> > Date: Wed Jun 23 12:56:12 2010 -0700 >> > >> > vt/console: try harder to print output when panicing >> > --- >> >> I've been able to boot and test with 2.6.37-rc1-00170-gf6614b7 >> - and this problem seems to be fixed in this version (vt.c file seems >> to be gone?). > > This is really weird; there was one issue Dave tracked down related to > lockdep and the new oops code, but I think it's been fixed. And it > should manifest as something other than a GPU hang... > Well - unsure - how this worked ok - for 2.6.37-rc1-00170-gf6614b7 (I could try few more times - though this kernel seems to be crashing for various other reasons - so I've had quite few testruns before I've been able to test this in some very limited X environment - so maybe it was just some lucky case - but I still keep it on my disk) Anyway - as an update - I'm now regularly using 2.6.37-rc2 - and it has exactly same problems - as in my original report - so the problem has not magically disappeared and it is still there. Is there anything I should try ? Basically every time after resume from suspend I have to switch from X to console and back to get usable screen back. Without this I seen only black screen with mouse over it - is there some way for reverting of this patch - or maybe just disabling some part of it ? To have reliable resume I still have to keep drm_kms_help thread disable - otherwise I observe GPU errors. Switch between consoles is 'relatively' easy to overcome. And another thing which might help - during suspend/resume I could usually see weird switch to console with some special text on the whole console screen - [ ### ] [ ### ] where '###' is some changing number - and it seems to be different between resumes. Also I should add I'm using 'no-console-suspend' kernel boot option. Zdenek ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Regressions in resume on intel graphics
2010/11/19 Dave Airlie : > On Fri, 2010-11-19 at 22:35 +0100, Zdenek Kabelac wrote: >> 2010/11/19 Jesse Barnes : >> > On Fri, 12 Nov 2010 10:17:07 +0100 >> > Zdenek Kabelac wrote: >> > >> >> 2010/11/12 Zdenek Kabelac : >> >> > Hi >> >> > >> >> > I've noticed that after resume with 2.6.36 kernel I need to switch >> >> > between console and back to Xorg to get usable Xsession again. >> >> > (my hw - T61, gma965, 4GB) >> >> > >> >> > I've played bisect game - and this is the first broken kernel: >> >> > >> >> > --- >> >> > commit 8fd4bd22350784d5b2fe9274f6790ba353976415 >> >> > Author: Jesse Barnes >> >> > Date: Wed Jun 23 12:56:12 2010 -0700 >> >> > >> >> > vt/console: try harder to print output when panicing >> >> > --- >> >> >> >> I've been able to boot and test with 2.6.37-rc1-00170-gf6614b7 >> >> - and this problem seems to be fixed in this version (vt.c file seems >> >> to be gone?). >> > >> > This is really weird; there was one issue Dave tracked down related to >> > lockdep and the new oops code, but I think it's been fixed. And it >> > should manifest as something other than a GPU hang... >> > >> >> Well - unsure - how this worked ok - for 2.6.37-rc1-00170-gf6614b7 (I >> could try few more times - though this kernel seems to be crashing for >> various other reasons - so I've had quite few testruns before I've >> been able to test this in some very limited X environment - so maybe >> it was just some lucky case - but I still keep it on my disk) >> >> Anyway - as an update - I'm now regularly using 2.6.37-rc2 - and it >> has exactly same problems - as in my original report - so the problem >> has not magically disappeared and it is still there. Is there >> anything I should try ? >> >> Basically every time after resume from suspend I have to switch from X >> to console and back to get usable screen back. Without this I seen >> only black screen with mouse over it - is there some way for reverting >> of this patch - or maybe just disabling some part of it ? >> >> >> To have reliable resume I still have to keep drm_kms_help thread >> disable - otherwise I observe GPU errors. >> Switch between consoles is 'relatively' easy to overcome. >> >> And another thing which might help - during suspend/resume I could >> usually see weird switch to console with some special text on the >> whole console screen - >> >> [ ### ] >> [ ### ] >> >> where '###' is some changing number - and it seems to be different >> between resumes. >> Also I should add I'm using 'no-console-suspend' kernel boot option. > > Can you see if e0fdace10e75dac67d906213b780ff1b1a4cc360 reverts cleanly? > and fixes it? > > The problem is I think you are getting a lockdep splat or rcu issue > before suspending, which sets oops_in_progress and never unsets it, > which means on resume the fb resume path kicks in to show you the oops > that is happening when there isn't actually anything to show. I've > gotten acks to have this reverted I just need to send the patch. > Ok - tested currentl 6656b3fc8aba2eb7ca00c06c7fe4917938b0b652 vanilla kernel with reverted commit e0fdace10e75da - and it seems Xorg screen after resume is again properly working. So this was quick - now the remaining problem - https://bugzilla.kernel.org/show_bug.cgi?id=19052 Zdenek ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] drm-intel-fixes queue
2011/3/20 Chris Wilson : > On Sun, 20 Mar 2011 15:22:08 +0100, Jan Niehusmann wrote: >> With these patches applied on top of current linus' tree >> (a952baa034ae7c2e4a66932005cbc7ebbccfe28d), I get a GPU hang after >> resume from suspend-to-ram. > > You would also get the same hang without those patches. > > Please try git revert a7a75c8f70d6f6a2f16c9f627f938bbee2d32718. > -Chris > > -- Ok - I've got this message as well - I've 2.6.39-rc2 kernel - unfortunately I don't know how to trigger this GPU reset error. (I've just plugged in USB phone and started to play some video content) (In fact - I wanted to create a new Intel bugzilla - with longterm resume problem I'm experiencing) [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state render error detected, EIR: 0x0010 page table error PGTBL_ER: 0x0080 [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x0010, masking oming packet received on address that isn't local. oming packet received on address that isn't local. [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung render error detected, EIR: 0x0010 page table error PGTBL_ER: 0x0080 [drm:i915_wait_request] *ERROR* i915_wait_request returns -11 (awaiting 241086 at 241084, next 241087) [drm:init_ring_common] *ERROR* render ring initialization failed ctl head tail start [drm] Changing LVDS panel from (+hsync, +vsync) to (-hsync, -vsync) [ cut here ] WARNING: at drivers/gpu/drm/i915/intel_display.c:1079 intel_enable_pipe+0x12a/0x150 [i915]() Hardware name: 6464CTO PLL state assertion failure (expected on, current off) Modules linked in: nls_cp1250 nls_cp852 vfat fat usb_storage uas binfmt_misc ip6_tables ebtable_nat ebtables iptable_mangle xt_tcpudp bridge ipv6 stp llc sunrpc ipt_REJECT xt_physdev xt_state iptable_filter ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables dm_mirror dm_region_hash dm_log dm_mod snd_hda_codec_analog arc4 ecb crypto_blkcipher cryptomgr aead crypto_algapi snd_hda_intel snd_hda_codec virtio_net snd_seq kvm_intel iwl3945 kvm snd_seq_device iwl_legacy btusb mac80211 snd_pcm bluetooth thinkpad_acpi psmouse snd_timer e1000e serio_raw cfg80211 snd_page_alloc iTCO_wdt wmi iTCO_vendor_support snd i2c_i801 soundcore nvram evdev usbhid hid i915 drm_kms_helper drm i2c_algo_bit i2c_core uinput autofs4 pcmcia sdhci_pci sdhci ehci_hcd uhci_hcd yenta_socket mmc_core sr_mod usbcore cdrom video backlight [last unloaded: scsi_wait_scan] Pid: 5, comm: kworker/u:0 Not tainted 2.6.39-rc2-5-gf04d4dc #119 Call Trace: [] warn_slowpath_common+0x7f/0xc0 [] warn_slowpath_fmt+0x46/0x50 [] intel_enable_pipe+0x12a/0x150 [i915] [] intel_crtc_mode_set+0x9ab/0x1bb0 [i915] [] ? i9xx_crtc_disable+0x137/0x1a0 [i915] [] drm_crtc_helper_set_mode+0x324/0x4c0 [drm_kms_helper] [] ? i915_driver_device_is_agp+0x10/0x10 [i915] [] drm_helper_resume_force_mode+0x72/0x150 [drm_kms_helper] [] ? i915_driver_device_is_agp+0x10/0x10 [i915] [] i915_reset+0x2e5/0x11a0 [i915] [] ? i915_driver_device_is_agp+0x10/0x10 [i915] [] i915_error_work_func+0xc8/0x110 [i915] [] process_one_work+0x18e/0x6d0 [] ? process_one_work+0x12d/0x6d0 [] ? retint_restore_args+0xe/0xe [] worker_thread+0x15e/0x340 [] ? rescuer_thread+0x240/0x240 [] kthread+0x9b/0xa0 [] kernel_thread_helper+0x4/0x10 [] ? finish_task_switch+0x74/0x110 [] ? _raw_spin_unlock_irq+0x3b/0x60 [] ? retint_restore_args+0xe/0xe [] ? __init_kthread_worker+0x70/0x70 [] ? gs_change+0xb/0xb ---[ end trace b2c517350cda74e8 ]--- [ cut here ] WARNING: at drivers/gpu/drm/i915/intel_display.c:1203 assert_pipe+0x75/0x80 [i915]() Hardware name: 6464CTO pipe B assertion failure (expected on, current off) Modules linked in: nls_cp1250 nls_cp852 vfat fat usb_storage uas binfmt_misc ip6_tables ebtable_nat ebtables iptable_mangle xt_tcpudp bridge ipv6 stp llc sunrpc ipt_REJECT xt_physdev xt_state iptable_filter ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables dm_mirror dm_region_hash dm_log dm_mod snd_hda_codec_analog arc4 ecb crypto_blkcipher cryptomgr aead crypto_algapi snd_hda_intel snd_hda_codec virtio_net snd_seq kvm_intel iwl3945 kvm snd_seq_device iwl_legacy btusb mac80211 snd_pcm bluetooth thinkpad_acpi psmouse snd_timer e1000e serio_raw cfg80211 snd_page_alloc iTCO_wdt wmi iTCO_vendor_support snd i2c_i801 soundcore nvram evdev usbhid hid i915 drm_kms_helper drm i2c_algo_bit i2c_core uinput autofs4 pcmcia sdhci_pci sdhci ehci_hcd uhci_hcd yenta_socket mmc_core sr_mod usbcore cdrom video backlight [last unloaded: scsi_wait_scan] Pid: 5, comm: kworker/u:0 Tainted: GW 2.6.39-rc2-5-gf04d4dc #119 Call Trace: [] warn_slowpath_common+0x7f/0xc0 [] warn_slowpath_fmt+0x46/0x50 [] ? intel_wait_for_vblank+0x1d1/0x210 [i915] [] assert_pipe+0x75/0x
