Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1197179
| From | Bryan O'Donoghue <pure.logic@nexus-software.ie> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times |
| Date | 2015-07-31 18:50 +0200 |
| Message-ID | <pSlFo-33y-3@gated-at.bofh.it> (permalink) |
| References | (8 earlier) <pS63E-5J4-1@gated-at.bofh.it> <pSfgC-1VW-3@gated-at.bofh.it> <pSfgC-1VW-1@gated-at.bofh.it> <pSfJE-2JP-15@gated-at.bofh.it> <pSlvJ-2Sa-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 31/07/15 17:36, Ilia Mirkin wrote: > On Fri, Jul 31, 2015 at 6:27 AM, Bryan O'Donoghue > <pure.logic@nexus-software.ie> wrote: >> ah no... 2.4.60 is right... >> >> Yes so Ilia - I've switched out 2.4.60 as per your suggestion to 2.4.56 >> (getting the version numbers right :) ) and it's still definitely giving me >> the multiple instances message. > > This is going to sound like a stupid question, but I'll ask anyways -- > you *did* restart chrome after changing libdrm versions, right? There are no stupid questions - just stupid answers like 'whaddya mean restart chrome' Seriously though, I've restarted the machine each time I've tried to switch out those libraries, so it's definitely not that. > I was going to mention that there were a handful of fixes in libdrm, > potentially since 2.4.56 (I forget the exact versions), but if 2.4.60 > also fails, then that would have them. > > There was a final assert() added in 2.4.62, but that was to better > isolate the cause of weirdo crashes (i.e. crash when the thing going > wrong happens rather than stashing bad pointers for later very > confusing dereference). Not GPU crashes. > > Just for your information, > > nouveau E[ PFIFO][0000:01:00.0] PFIFO: read fault at > 0x0003e21000 [PAGE_NOT_PRESENT] from (unknown enum > 0x00000000)/GPC0/(unknown enum 0x0000000f) on channel 0x007f80c000 > [unknown] > > means that there was VM fault from an unknown gpu unit (???) when > reading some resource by the GPU. OK, I was assuming it was a side effect of the -EINVAL when we get the multiple instances message. > (The GPU has its own MMU.) > Unfortunately this can happen for one of a million reasons, the > biggest one being "unknown", but mesa definitely doesn't handle > command submission failures particularly well... should probably add a > "fail 1% of the time" thing to help fix that up. > > Do you have a reproducible way of achieving the multiple buffer on > validation list thing? What GPU do you have? (Looking for a codename, > not a marketing name... lspci should have it... GFxxx or GKxxx or 01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device 0130 Flags: bus master, fast devsel, latency 0, IRQ 45 Memory at c0000000 (32-bit, non-prefetchable) [size=16M] Memory at 80000000 (64-bit, prefetchable) [size=256M] Memory at 90000000 (64-bit, prefetchable) [size=32M] I/O ports at 1000 [size=128] Expansion ROM at c1000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 <?> Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting <?> Capabilities: [420] Advanced Error Reporting Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] #19 Kernel driver in use: nouveau Macbook pro retina 2014 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times Bryan O'Donoghue <pure.logic@nexus-software.ie> - 2015-07-30 12:40 +0200
Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times Ilia Mirkin <imirkin@alum.mit.edu> - 2015-07-30 16:20 +0200
Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times Peter Hurley <peter@hurleysoftware.com> - 2015-07-30 16:50 +0200
Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times Bryan O'Donoghue <pure.logic@nexus-software.ie> - 2015-07-30 17:00 +0200
Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times Ilia Mirkin <imirkin@alum.mit.edu> - 2015-07-30 17:10 +0200
Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times Bryan O'Donoghue <pure.logic@nexus-software.ie> - 2015-07-30 17:20 +0200
Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times Emil Velikov <emil.l.velikov@gmail.com> - 2015-07-30 17:30 +0200
Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times Bryan O'Donoghue <pure.logic@nexus-software.ie> - 2015-07-31 18:20 +0200
Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times Ilia Mirkin <imirkin@alum.mit.edu> - 2015-07-31 18:40 +0200
Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times Bryan O'Donoghue <pure.logic@nexus-software.ie> - 2015-07-31 18:50 +0200
Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times Bryan O'Donoghue <pure.logic@nexus-software.ie> - 2015-08-03 03:00 +0200
Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times Bryan O'Donoghue <pure.logic@nexus-software.ie> - 2015-07-30 17:00 +0200
Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times Bryan O'Donoghue <pure.logic@nexus-software.ie> - 2015-07-30 16:50 +0200
csiph-web