similar to: nouveau graphical corruption in 3.13.2

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

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

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 >>

https://bugs.freedesktop.org/show_bug.cgi?id=77574 Priority: medium Bug ID: 77574 Assignee: nouveau at lists.freedesktop.org Summary: Minor screen corruption on NVAF card QA Contact: xorg-team at lists.x.org Severity: minor Classification: Unclassified OS: Linux (All) Reporter: adonai at xaker.ru

In 3.7-rc4, when starting X with the integrated GPU and suspending the discrete GPU, after one or more 32-bit applications are used (eg Skype) and X is stopped, we hit a panic. Prevent this by testing if the fini function is valid. Full panic bootlog is at: http://quora.org/2012/nouveau/dmesg-crash.txt Xorg.log is at: http://quora.org/2012/nouveau/Xorg.0.log-crash.txt Kernel log after fix is at:

https://bugs.freedesktop.org/show_bug.cgi?id=54056 Bug #: 54056 Summary: plenty of errors trapped write at plus PGRAPH error Classification: Unclassified Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

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

Hi Ladies and Gentlemans. I'd like to report a possible bug and ask for help in solving it. I have a Mid 2010 Macbook Pro running Debian Jessie. The bug seems to happen at random, but mainly when using a 3D application with other apps running, such as Chromium (Chrome) and Iceweasel (Firefox). It happens when watching videos with VLC and mplayer2. I hope someone will manage to help. Thanks.

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 ---

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

https://bugs.freedesktop.org/show_bug.cgi?id=83957 Priority: medium Bug ID: 83957 Assignee: nouveau at lists.freedesktop.org Summary: [NV50 - NVAF][MCP89] Major screen corruption and X crash soon after log in QA Contact: xorg-team at lists.x.org Severity: critical Classification: Unclassified OS:

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

https://bugs.freedesktop.org/show_bug.cgi?id=60150 Priority: medium Bug ID: 60150 Assignee: nouveau at lists.freedesktop.org Summary: [NVAF] Garbled Screen QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: nihilhill at gmail.com Hardware: Other

>From recent additional locking in nouveau, it looks like we see recursive lock acquisition in 3.8-rc6: nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x0e7150a2 nouveau [ DEVICE][0000:01:00.0] Chipset: GK107 (NVE7) nouveau [ DEVICE][0000:01:00.0] Family : NVE0 nouveau [ VBIOS][0000:01:00.0] checking PRAMIN for image... nouveau [ VBIOS][0000:01:00.0] ... appears to be valid nouveau [

Hi HPA et al, When moving from syslinux 4.06 to 5.01, I found serial output isn't working. The issue reproduces simply [1] and I get back serial output when I move back to syslinux 4.06. I also see a regression in booting locally with 'localboot 0' which give a generic 'failed' error message; likely reproducible there also. Let me know if you need more information and

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

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.

Hi Dongyang, Yan, When testing BTRFS with RAID 0 metadata on linux-3.3, we see discard ranges exceeding the end of the block device [1], potentially causing dataloss; when this occurs, filesystem writeback becomes catatonic due to continual resubmission. The reproducer is quite simple [2]. Hope this proves useful... Thanks, Daniel --- [1] attempt to access beyond end of device ram0: rw=129,

https://bugs.freedesktop.org/show_bug.cgi?id=44849 Bug #: 44849 Summary: nouveau loads scrambled garbage Classification: Unclassified Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component:

On Mon, May 27, 2013 at 5:55 AM, Daniel J Blueman <daniel at 1degreenorth.com> wrote: > On 27/05/2013 17:53, Ferenc Wagner wrote: >> >> Daniel J Blueman <daniel at 1degreenorth.com> writes: >> >>> When moving from syslinux 4.06 to 5.01, I found serial output isn't >>> working. The issue reproduces simply [1] and I get back serial output