All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Chunyu Hu <chuhu@redhat.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Fedora 30 drm error
Date: Mon, 8 Jul 2019 07:33:01 -0700	[thread overview]
Message-ID: <20190708143301.GG779@intel.com> (raw)
In-Reply-To: <1782382775.19873944.1562042522727.JavaMail.zimbra@redhat.com>

Hi Chunyu,

First of all sorry for the delay on the response here.
Many of us were out on vacation and holidays.

Also in general please use https://bugs.freedesktop.org/
to report bugs.

Please make sure you read this before:
https://01.org/linuxgraphics/documentation/how-report-bugs

(more inline)

On Tue, Jul 02, 2019 at 12:42:02AM -0400, Chunyu Hu wrote:
> Hi Rodrigo, Joonas and Jani,
> 
> I'm meeting some drm issues when using Fedora 30. I'm using a Lenovo box, and I met some error message in
> dmesg, (not panic). Could you take a look at the warning, and do we have already fixes for this? Thanks!

Best way to find out if we have had a fix for that is to try out drm-tip:

https://cgit.freedesktop.org/drm-tip/

> 
>       [43401.062181] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

Recently we had many patches touching watermarks and other related areas
that usually are known for FIFO underruns.

Another good reason to try drm-tip. And if that is fixed on drm-tip and
you need to find the exact patch that fixed the issue you need to perform
a reversed bisect.

> 
> 
> What's worse, I met a gnome-shell broken when reading drm :

It seems yet another issue to be reported at bugzilla.freedesktop.org
And also to check reproduciablitity with drm-tip...

Thanks,
Rodrigo.

> 
> Jul 01 16:26:31 kernel: general protection fault: 0000 [#1] SMP PTI
> Jul 01 16:26:31 kernel: CPU: 0 PID: 1896 Comm: gnome-shell Not tainted 5.1.12-300.fc30.x86_64 #1
> Jul 01 16:26:31 kernel: Hardware name: LENOVO 10N9CTO1WW/3107, BIOS M1AKT3EA 01/21/2019
> Jul 01 16:26:31 kernel: RIP: 0010:find_get_entry+0x7a/0x1d0
> Jul 01 16:26:31 kernel: Code: 00 00 48 89 e7 e8 f6 ea 75 00 48 89 c2 48 3d 06 04 00 00 74 e4 48 3d 02 04 00 00 74 dc 48 85 c0 0f 84 19 01 00 00 a8 01 75 5f <48> 8b 40 08 48>
> Jul 01 16:26:31 kernel: RSP: 0018:ffffae8083c87a90 EFLAGS: 00010246
> Jul 01 16:26:31 kernel: RAX: 0000800000000000 RBX: ffff9b8207ecbba0 RCX: 0000000000000000
> Jul 01 16:26:31 kernel: RDX: 0000800000000000 RSI: ffff9b7f761066c8 RDI: ffffae8083c87a90
> Jul 01 16:26:31 kernel: RBP: 00000000000004c2 R08: 00000000001120d2 R09: 0000000000000000
> Jul 01 16:26:31 kernel: R10: ffff9b8207ecba30 R11: ffff9b7f76107458 R12: 0000000000000000
> Jul 01 16:26:31 kernel: R13: 00000000001120d2 R14: 0000000000000001 R15: ffff9b8207ecbba0
> Jul 01 16:26:31 kernel: FS:  00007fba5c080d00(0000) GS:ffff9b820da00000(0000) knlGS:0000000000000000
> Jul 01 16:26:31 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> Jul 01 16:26:31 kernel: CR2: 00007fba5ac4f000 CR3: 0000000406584003 CR4: 00000000003606f0
> Jul 01 16:26:31 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> Jul 01 16:26:31 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Jul 01 16:26:31 kernel: Call Trace:
> Jul 01 16:26:31 kernel:  find_lock_entry+0x1a/0x190
> Jul 01 16:26:31 kernel:  shmem_getpage_gfp+0xf4/0xaa0
> Jul 01 16:26:31 kernel:  ? sg_init_table+0x11/0x30
> Jul 01 16:26:31 kernel:  shmem_read_mapping_page_gfp+0x42/0x80
> Jul 01 16:26:31 kernel:  i915_gem_object_get_pages_gtt+0x206/0x5c0 [i915]
> Jul 01 16:26:31 kernel:  ? _cond_resched+0x15/0x30
> Jul 01 16:26:31 kernel:  ? kmem_cache_alloc_trace+0x154/0x1c0
> Jul 01 16:26:31 kernel:  ? drm_vma_node_allow+0x27/0xd0 [drm]
> Jul 01 16:26:31 kernel:  ? drm_vma_node_allow+0xae/0xd0 [drm]
> Jul 01 16:26:31 kernel:  __i915_gem_object_get_pages+0x54/0x60 [i915]
> Jul 01 16:26:31 kernel:  i915_gem_set_domain_ioctl+0x1c9/0x200 [i915]
> Jul 01 16:26:31 kernel:  ? i915_gem_create+0x8b/0xd0 [i915]
> Jul 01 16:26:31 kernel:  ? i915_gem_obj_prepare_shmem_write+0x120/0x120 [i915]
> Jul 01 16:26:31 kernel:  drm_ioctl_kernel+0xaa/0xf0 [drm]
> Jul 01 16:26:31 kernel:  drm_ioctl+0x208/0x390 [drm]
> Jul 01 16:26:31 kernel:  ? i915_gem_obj_prepare_shmem_write+0x120/0x120 [i915]
> Jul 01 16:26:31 kernel:  ? ep_scan_ready_list.constprop.0+0x1d5/0x200
> Jul 01 16:26:31 kernel:  do_vfs_ioctl+0x405/0x660
> Jul 01 16:26:31 kernel:  ? __sys_recvmsg+0x85/0xa0
> Jul 01 16:26:31 kernel:  ksys_ioctl+0x5e/0x90
> Jul 01 16:26:31 kernel:  __x64_sys_ioctl+0x16/0x20
> Jul 01 16:26:31 kernel:  do_syscall_64+0x5b/0x170
> Jul 01 16:26:31 kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
> Jul 01 16:26:31 kernel: RIP: 0033:0x7fba5fdd91fb
> Jul 01 16:26:31 kernel: Code: 0f 1e fa 48 8b 05 8d dc 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff>
> Jul 01 16:26:31 kernel: RSP: 002b:00007fff89e91148 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
> Jul 01 16:26:31 kernel: RAX: ffffffffffffffda RBX: 00007fff89e911c4 RCX: 00007fba5fdd91fb
> Jul 01 16:26:31 kernel: RDX: 00007fff89e911c4 RSI: 00000000400c645f RDI: 000000000000000b
> Jul 01 16:26:31 kernel: RBP: 00000000400c645f R08: 0000557684761690 R09: 0000000000000007
> Jul 01 16:26:31 kernel: R10: 0000557683dc3010 R11: 0000000000000246 R12: 00007fff89e911d0
> Jul 01 16:26:31 kernel: R13: 000000000000000b R14: 0000557683e5b550 R15: 0000557684761690
> Jul 01 16:26:31 kernel: Modules linked in: xt_CHECKSUM ipt_MASQUERADE tun bridge stp llc nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_r>
> Jul 01 16:26:31 kernel:  i2c_algo_bit drm_kms_helper e1000e drm crc32c_intel wmi video fuse
> Jul 01 16:26:31 kernel: ---[ end trace ffb9153f9312e14b ]---
> Jul 01 16:26:31 kernel: RIP: 0010:find_get_entry+0x7a/0x1d0
> Jul 01 16:26:31 kernel: Code: 00 00 48 89 e7 e8 f6 ea 75 00 48 89 c2 48 3d 06 04 00 00 74 e4 48 3d 02 04 00 00 74 dc 48 85 c0 0f 84 19 01 00 00 a8 01 75 5f <48> 8b 40 08 48>
> Jul 01 16:26:31 kernel: RSP: 0018:ffffae8083c87a90 EFLAGS: 00010246
> Jul 01 16:26:31 kernel: RAX: 0000800000000000 RBX: ffff9b8207ecbba0 RCX: 0000000000000000
> Jul 01 16:26:31 kernel: RDX: 0000800000000000 RSI: ffff9b7f761066c8 RDI: ffffae8083c87a90
> Jul 01 16:26:31 kernel: RBP: 00000000000004c2 R08: 00000000001120d2 R09: 0000000000000000
> Jul 01 16:26:31 kernel: R10: ffff9b8207ecba30 R11: ffff9b7f76107458 R12: 0000000000000000
> Jul 01 16:26:31 kernel: R13: 00000000001120d2 R14: 0000000000000001 R15: ffff9b8207ecbba0
> Jul 01 16:26:31 kernel: FS:  00007fba5c080d00(0000) GS:ffff9b820da00000(0000) knlGS:0000000000000000
> Jul 01 16:26:31 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> Jul 01 16:26:31 kernel: CR2: 00007fba5ac4f000 CR3: 0000000406584003 CR4: 00000000003606f0
> Jul 01 16:26:31 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> Jul 01 16:26:31 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Jul 01 16:26:33 abrt-dump-journal-oops[993]: abrt-dump-journal-oops: Found oopses: 1
> Jul 01 16:26:33 abrt-dump-journal-oops[993]: abrt-dump-journal-oops: Creating problem directories
> Jul 01 16:26:34 abrt-dump-journal-oops[993]: Reported 1 kernel oopses to Abrt
> 
> 
> 
> 
> kernel version:
> 5.1.12-300.fc30.x86_64
> 
> 
> System Information                                                                                                                                                           
>     Manufacturer: LENOVO
>     Product Name: 10N9CTO1WW
>     Version: ThinkCentre M910t-N000
>     Serial Number: P508XK8Q
> 
> 
> 
> 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) (prog-if 00 [VGA controller])
> 	DeviceName:  Onboard IGD
> 	Subsystem: Lenovo Device 3107
> 	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
> 	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> 	Latency: 0, Cache Line Size: 64 bytes
> 	Interrupt: pin A routed to IRQ 126
> 	Region 0: Memory at f6000000 (64-bit, non-prefetchable) [size=16M]
> 	Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M]
> 	Region 4: I/O ports at f000 [size=64]
> 	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
> 	Capabilities: [40] Vendor Specific Information: Len=0c <?>
> 	Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
> 		DevCap:	MaxPayload 128 bytes, PhantFunc 0
> 			ExtTag- RBE+
> 		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
> 			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
> 			MaxPayload 128 bytes, MaxReadReq 128 bytes
> 		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
> 		DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported
> 			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
> 		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
> 			 AtomicOpsCtl: ReqEn-
> 	Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
> 		Address: fee00018  Data: 0000
> 	Capabilities: [d0] Power Management version 2
> 		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> 		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
> 	Capabilities: [100 v1] Process Address Space ID (PASID)
> 		PASIDCap: Exec- Priv-, Max PASID Width: 14
> 		PASIDCtl: Enable- Exec- Priv-
> 	Capabilities: [200 v1] Address Translation Service (ATS)
> 		ATSCap:	Invalidate Queue Depth: 00
> 		ATSCtl:	Enable-, Smallest Translation Unit: 00
> 	Capabilities: [300 v1] Page Request Interface (PRI)
> 		PRICtl: Enable- Reset-
> 		PRISta: RF- UPRGI- Stopped+
> 		Page Request Capacity: 00008000, Page Request Allocation: 00000000
> 	Kernel driver in use: i915
> 	Kernel modules: i915
> 
> 
> -- 
> Regards,
> Chunyu Hu
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-07-08 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1067393012.19872741.1562041936223.JavaMail.zimbra@redhat.com>
2019-07-02  4:42 ` Fedora 30 drm error Chunyu Hu
2019-07-08 14:33   ` Rodrigo Vivi [this message]
2019-07-10  9:55     ` Chunyu Hu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190708143301.GG779@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=chuhu@redhat.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.