similar to: [PATCH] nouveau: Fix crash after D3

On 9 February 2014 02:57, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Sat, Feb 8, 2014 at 10:38 AM, Daniel J Blueman <daniel at quora.org> wrote: >> Interestingly, there was graphical failure booting 3.6.11, even >> nvidia-current fails to initialise, but these two issues could be due >> to running the Xorg stack in Ubuntu 14.04 pre-release. Using >>

On 8 February 2014 16:33, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Sat, Feb 8, 2014 at 2:58 AM, Daniel J Blueman <daniel at quora.org> wrote: >> Hi guys, >> >> With a GeForce 320M GPU running linux 3.13.2 and Xorg 1.15.0, I'm >> seeing significant graphical corruption and later unrecoverable GPU >> lockup, accompanied by thousands of

Hi guys, With a GeForce 320M GPU running linux 3.13.2 and Xorg 1.15.0, I'm seeing significant graphical corruption and later unrecoverable GPU lockup, accompanied by thousands of ILLEGAL_MTHD or related kernel messages [1]. I see similar issues on 3.12 also. Is there any debugging or testing I can do to help diagnose this? Many thanks, Daniel --- [1] http://quora.org/nouveau-dmesg.txt

On 13 October 2012 15:12, Daniel J Blueman <daniel at quora.org> wrote: > On my Macbook Retina, when switching to the integrated GPU, we see a > ioread32 issued to the discrete GPU, which hangs as it is in D3 [1] > (drm.debug is set to 14 here). > > Full kernel 3.6.2 boot logs with drm.debug=5 are at: > http://quora.org/2012/mbp-i915-panel.txt > > What additional

New Gluster Community Platform: http://community.gluster.org We are pleased to announce a Quora like community platform (beta), where the focus is on *YOU* and your peers in the Community. We wanted to provide a platform for all of you to engage with each other and share everything (ugly, bad and the good) with other community members and us. We want your questions heard and answers recognized.

On Sat, Feb 22, 2014 at 10:45 PM, Daniel J Blueman <daniel at quora.org> wrote: > On 9 February 2014 02:57, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> On Sat, Feb 8, 2014 at 10:38 AM, Daniel J Blueman <daniel at quora.org> wrote: >>> Interestingly, there was graphical failure booting 3.6.11, even >>> nvidia-current fails to initialise, but these

Having a RAM device does not make sense for chips like GK20A which have no dedicated video memory. The dummy RAM device that we used so far works as a temporary band-aid, but in the long-term it is desirable for the driver to be able to work without any kind of VRAM. This patch adds a few conditionals in places where a RAM device was assumed to be present and allows some more objects to be

Having a RAM device does not make sense for chips like GK20A which have no dedicated video memory. The dummy RAM device that we used so far works as a temporary band-aid, but in the long-term it is desirable for the driver to be able to work without any kind of VRAM. This patch adds a few conditionals in places where a RAM device was assumed to be present and allows some more objects to be

Having a RAM device does not make sense for chips like GK20A which have no dedicated video memory. The dummy RAM device that we used so far works as a temporary band-aid, but in the long-term it is desirable for the driver to be able to work without any kind of VRAM. This patch adds a few conditionals in places where a RAM device was assumed to be present and allows some more objects to be

On Sat, Feb 8, 2014 at 10:38 AM, Daniel J Blueman <daniel at quora.org> wrote: > Interestingly, there was graphical failure booting 3.6.11, even > nvidia-current fails to initialise, but these two issues could be due > to running the Xorg stack in Ubuntu 14.04 pre-release. Using > nouveau.noaccel=1 works great for the first X session, but after > logging out, lightdm and the

hi,everyone. now i start to design a api. the url like this http://localhost:3000/api?seckey=123&&post_id=1 the visitor need a seckey to access auth.and get info via json. so i dont think thats a good api. i need your answers.thx -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

On Tue, Feb 17, 2015 at 5:47 PM, Alexandre Courbot <acourbot at nvidia.com> wrote: > Having a RAM device does not make sense for chips like GK20A which have > no dedicated video memory. The dummy RAM device that we used so far > works as a temporary band-aid, but in the long-term it is desirable for > the driver to be able to work without any kind of VRAM. > > This patch

Hi Marcin et al, When booting my Macbook Pro into 3.12 and powering off the Nvidia GPU, we see nouveau try to dequeue an item which isn't present, leading to a page-not-present fault. 3.11 works just nice. It looks like I should add some debug, as there aren't event enqueuing/dequeueing debug flags, or as you suggest? http://quora.org/2013/dmesg.txt http://quora.org/2013/config (same as

On 3.8-rc2 with lockdep enabled and dual-GPU setup (Macbook Pro Retina), I see two releated lock inversion issues with the EFI framebuffer, leading to possible deadlock: when X takes over from the EFI framebuffer [1] and when nouveau releases the framebuffer when being vgaswitcherood [2]. Let me know if you'd like any testing or analysis when I can get the time. Many thanks, Daniel ---

I'm attempting to fetch a kernel over http using lpxelinux.0, as documented in http://www.syslinux.org/wiki/index.php/Syslinux_5_Changelog and it took me far too long to succeed... My first attempt was via pxelinux.0 as embedded in the Ubuntu 13.04 installer, this gave me the error that gPXE/iPXE extentions weren't available. So I inferred that this wasn't v5.10 or greater. Then I

After switcherooing to integrated and starting X, when X fails to start and causes a console switch, we get hit with a hanger (below). Fix by checking if we're already in D3. BUG: soft lockup - CPU#0 stuck for 22s! [Xorg:1703] [<ffffffffa037c538>] nv04_timer_read+0x28/0x70 [nouveau] [<ffffffffa037bfec>] nouveau_timer_wait_eq+0x7c/0xe0 [nouveau] [<ffffffffa03f4f4e>]

Thanks Ilia for the v2 review! Here is the v3 of this IOMMU support for GK20A series. Changes since v2: - Cleaner changes for ltc - Fixed typos in gk20a instmem IOMMU comments Changes since v1: - Add missing else condition in ltc - Remove extra flags that slipped into nouveau_display.c and nv84_fence.c. Original cover letter: Patches 1-3 make the presence of a RAM device optional, and remove

On Sat, Feb 8, 2014 at 2:58 AM, Daniel J Blueman <daniel at quora.org> wrote: > Hi guys, > > With a GeForce 320M GPU running linux 3.13.2 and Xorg 1.15.0, I'm > seeing significant graphical corruption and later unrecoverable GPU > lockup, accompanied by thousands of ILLEGAL_MTHD or related kernel > messages [1]. I see similar issues on 3.12 also. > > Is there any

2010/10/9 António Saragga Seabra <antseabra at gmail.com>: > I'm on Windows using MinGW... > > 2010/10/9 OvermindDL1 <overminddl1 at gmail.com> >> >> 2010/10/5 António Saragga Seabra <antseabra at gmail.com>: >> > Hi >> > >> > Thank you for your help! Followed your suggestion closely and changed >> > the >> >

Hi I try parallelising some code using the snow package and the following lines: cl <- makeSOCKcluster(8) pfunc <- function (x) (if(x <= (-th)) 1 else 0) ###correlation coefficient clusterExport(cl,c("pfunc","th")) cor.c.f <- parApply(cl,tms,c(1,2),FUN=pfunc) The parApply results in the error message: > cor.c.f <- parApply(cl,tms,c(1,2),FUN=pfunc) Error