On Tue, Jan 25, 2011 at 12:04 AM, Maarten Maathuis <madman2003 at gmail.com> wrote: > Just wanted to ask, before trying to hunt it down :) > > Display does come back, but it stays stuck with a blinking cursors, > nothing in logs related to resume, even when doing an Emergency-Sync > (i do see the message that sync happened, other keys just don't work). > > Maarten. > > -- > Far away from the primal instinct, the song seems to fade away, the > river get wider between your thoughts and the things we do and say. > It turned out to be a missing firmware for a realtek 8168 NIC. For some reason it was causing delay of around a minute when resuming. No idea yet why it takes so long to time out. -- Far away from the primal instinct, the song seems to fade away, the river get wider between your thoughts and the things we do and say. From bugzilla-daemon at freedesktop.org Wed Feb 2 07:48:03 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Wed, 2 Feb 2011 07:48:03 -0800 (PST) Subject: [Bug 33841] New: Fedora 14 randomly crashes Message-ID: <bug-33841-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> https://bugs.freedesktop.org/show_bug.cgi?id=33841 Summary: Fedora 14 randomly crashes Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: franzmariamd at gmail.com QAContact: xorg-team at lists.x.org Created an attachment (id=42855) --> (https://bugs.freedesktop.org/attachment.cgi?id=42855) output dmesg after crash and restart with a rescue dvd My computer randomly crashes with Fedora 14. I had the same problem with Fedora 12 one year ago; so I returned to use Fedora 11. I used Fedora 11 for more than a year without problems. One month ago I had to pass to Fedora 14, fresh installation. I use the default driver nouveau. It seems ok, it recognizes the hardware (video card and monitor) and set the correct resolution 1440x900. But randomly my computer freezes. The problems with Fedora 14 is the same encountered with Fedora 12. Level of hang = 3: Display is frozen, no reaction at all to key presses or mouse. NumLock etc. keyboard lights do not react. I passed to use nvidia rpmfusion driver, but I had the same problem. My motherboard is MSI MS-7301. Video card Nvidia 8300GS 128M. Monitor Packard Bell PKB VIS 190WS. If I start with kernel option nouveau.modeset=0 computer never freezes; but resolution is set to 1280x1024 and not to correct one (1440x900). I suppose with this kernel option I'm using the vesa driver. So with vesa driver is all OK. After a crash using nouveau driver I restart with the rescue DVD and I save dmesg output. I hope it is useful. Best regards. Franco -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla-daemon at freedesktop.org Wed Feb 2 08:08:05 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Wed, 2 Feb 2011 08:08:05 -0800 (PST) Subject: [Bug 33841] Fedora 14 randomly crashes In-Reply-To: <bug-33841-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-33841-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110202160805.CACF313004D@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=33841 --- Comment #1 from Franco <franzmariamd at gmail.com> 2011-02-02 08:08:04 PST --- Created an attachment (id=42856) --> (https://bugs.freedesktop.org/attachment.cgi?id=42856) Xorg.0.log after boot without nouveau.modeset=0 Xorg.0.log after boot without nouveau.modeset=0. Using nouveau driver. 1440x900 60Hz. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla-daemon at freedesktop.org Wed Feb 2 08:11:27 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Wed, 2 Feb 2011 08:11:27 -0800 (PST) Subject: [Bug 33841] Fedora 14 randomly crashes In-Reply-To: <bug-33841-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-33841-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110202161127.A3B1213004D@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=33841 --- Comment #2 from Franco <franzmariamd at gmail.com> 2011-02-02 08:11:27 PST --- Created an attachment (id=42857) --> (https://bugs.freedesktop.org/attachment.cgi?id=42857) dmesg.log after boot without nouveau.modeset=0. dmesg.log using nouveau driver. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla-daemon at freedesktop.org Wed Feb 2 08:38:23 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Wed, 2 Feb 2011 08:38:23 -0800 (PST) Subject: [Bug 32959] 2.6.37 - NV11 goes into GPU hang In-Reply-To: <bug-32959-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-32959-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110202163823.59B9513004F@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=32959 --- Comment #31 from Francisco Jerez <currojerez at riseup.net> 2011-02-02 08:38:19 PST --- Created an attachment (id=42858) View: https://bugs.freedesktop.org/attachment.cgi?id=42858 Review: https://bugs.freedesktop.org/review?bug=32959&attachment=42858 nv04_lvds_no_native_mode.patch (In reply to comment #29) > Here's some extra information. > > Apparently if I add 'video=LVDS:d' to the kernel parameter line, the hang with > 2.6.37 doesn't happen. This definitely was not needed with 2.6.36. The attached patch should help with that crash. To find out why we can't find a native mode for your LVDS panel, can you get me a BIOS dump? (see [1]) [1] http://nouveau.freedesktop.org/wiki/DumpingVideoBios -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla-daemon at freedesktop.org Wed Feb 2 09:15:51 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Wed, 2 Feb 2011 09:15:51 -0800 (PST) Subject: [Bug 32959] 2.6.37 - NV11 goes into GPU hang In-Reply-To: <bug-32959-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-32959-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110202171551.D27CF13004F@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=32959 --- Comment #32 from Alex Buell <alex.buell at munted.org.uk> 2011-02-02 09:15:51 PST --- Created an attachment (id=42860) --> (https://bugs.freedesktop.org/attachment.cgi?id=42860) dell-inspiron-8100-vbios.rom -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla-daemon at freedesktop.org Wed Feb 2 09:22:41 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Wed, 2 Feb 2011 09:22:41 -0800 (PST) Subject: [Bug 32959] 2.6.37 - NV11 goes into GPU hang In-Reply-To: <bug-32959-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-32959-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110202172241.F306013004D@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=32959 --- Comment #33 from Alex Buell <alex.buell at munted.org.uk> 2011-02-02 09:22:40 PST --- Created an attachment (id=42861) --> (https://bugs.freedesktop.org/attachment.cgi?id=42861) drm.debug=6 output via netconsole w/ nv04 lvds no native mode patch -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From mahatma at bspu.unibel.by Wed Feb 2 09:28:36 2011 From: mahatma at bspu.unibel.by (Dzianis Kahanovich) Date: Wed, 02 Feb 2011 19:28:36 +0200 Subject: nv4c broken after october (approx.) Message-ID: <4D499444.20009@xxxxxxxxxxxxxx> After october I got broken image on my integrated nv4c chip (are you need precise model?). I don't know precise time points, but now known: in Gentoo portage still 20101010 - good, 20101130 - bad (but I use git version before problems and now - without acceleration/with shadowfb). If I set 32M VRAM - image is semi-broken. I may to do some testings (like testing git by day or try to trace registers), but in first point IMHO this minimal info may help to developers too. Last actions was: installing current kernel (2.6.38-rc2-git8), known nouveau-firmware and current driver & libdrm snapshots. This is my screen: http://mahatma.bspu.unibel.by/IMG0035A.jpg (default it was green MJ leafs on background, terminal window and panel on top) PS Even if you omit support of old chips, this is looks semi-working but memory misorganized and in theory still possible to fix. Or no? -- WBR, Dzianis Kahanovich AKA Denis Kaganovich, http://mahatma.bspu.unibel.by/ From chantry.xavier at gmail.com Wed Feb 2 14:38:06 2011 From: chantry.xavier at gmail.com (Xavier Chantry) Date: Wed, 2 Feb 2011 23:38:06 +0100 Subject: nv4c broken after october (approx.) In-Reply-To: <4D499444.20009@xxxxxxxxxxxxxx> References: <4D499444.20009@xxxxxxxxxxxxxx> Message-ID: <AANLkTi=Ts_vC9BP6YTqNWn93zpFTTwZCbs3__-TyHbSR@xxxxxxxxxxxxxx> On Wed, Feb 2, 2011 at 6:28 PM, Dzianis Kahanovich <mahatma at bspu.unibel.by> wrote: > After october I got broken image on my integrated nv4c chip (are you need > precise model?). I don't know precise time points, but now known: in Gentoo > portage still 20101010 - good, 20101130 - bad (but I use git version before > problems and now - without acceleration/with shadowfb). If I set 32M VRAM - > image is semi-broken. I may to do some testings (like testing git by day or try > to trace registers), but in first point IMHO this minimal info may help to > developers too. > > Last actions was: installing current kernel (2.6.38-rc2-git8), known > nouveau-firmware and current driver & libdrm snapshots. > > This is my screen: http://mahatma.bspu.unibel.by/IMG0035A.jpg > (default it was green MJ leafs on background, terminal window and panel on top) > > PS Even if you omit support of old chips, this is looks semi-working but memory > misorganized and in theory still possible to fix. Or no? > This is the third report I see today.. for a patch 3-4 months old. At least according to wilder on IRC. http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=c88f13e25b0040c1dd0f93e0ac40f62a6005ce59 17:44 curro >> wilder: do you get the same corruption with a 1024x768 framebuffer? So what's your resolution and can you try to force 1024x768, as explained there : http://nouveau.freedesktop.org/wiki/KernelModeSetting From bugzilla-daemon at freedesktop.org Wed Feb 2 15:37:42 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Wed, 2 Feb 2011 15:37:42 -0800 (PST) Subject: [Bug 32959] 2.6.37 - NV11 goes into GPU hang In-Reply-To: <bug-32959-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-32959-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110202233742.D575513004F@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=32959 --- Comment #34 from Alex Buell <alex.buell at munted.org.uk> 2011-02-02 15:37:42 PST --- http://annarchy.freedesktop.org/~currojerez/nv10_invalid_placement_range.patch This patch is also required to prevent X crashes. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla-daemon at freedesktop.org Wed Feb 2 16:12:56 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Wed, 2 Feb 2011 16:12:56 -0800 (PST) Subject: [Bug 32959] 2.6.37 - NV11 goes into GPU hang In-Reply-To: <bug-32959-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-32959-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110203001256.D12AF13004D@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=32959 --- Comment #35 from Alex Buell <alex.buell at munted.org.uk> 2011-02-02 16:12:56 PST --- Thank you, the two patches given above fixed the problem entirely for me, no more X or kernel hangs with 2.6.37. I now consider this report closed. Until the next time :) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From martin.peres at free.fr Wed Feb 2 16:22:11 2011 From: martin.peres at free.fr (Martin Peres) Date: Thu, 03 Feb 2011 01:22:11 +0100 Subject: [Patch] Yet another version of the card pausing patch In-Reply-To: <4D3C37BA.6050503@xxxxxxx> References: <4D3C37BA.6050503@xxxxxxx> Message-ID: <4D49F533.4080301@xxxxxxx> Le 23/01/2011 15:14, Martin Peres a ?crit : > Hi everyone, > > I would like devs to test this patch on all their cards(<nvc0) and > report bugs/instability. It shouldn't ever crash (but it may not > always work and return -EAGAIN). > > I've attached a little bash script that you need to modify according > to the available perf levels. Please launch it and play, watch videos > or browse the internet. > > Also, if you could look at the hold_spin variable and tell me how you > would deal with that, it would be kind of you. The problem is that > PGRAPH may take an awful lot > of time to pause in certain conditions and holding the lock at this > position isn't needed (as far as I can tell, the critical ressource is > fifo_reassign). > > Martin > > PS: I'll be out in an hour for a week so I may be slower to answer > messages. Patch 3: Don't forget to set the name of the boot perf level. From martin.peres at ensi-bourges.fr Wed Feb 2 15:51:00 2011 From: martin.peres at ensi-bourges.fr (Martin Peres) Date: Thu, 3 Feb 2011 00:51:00 +0100 Subject: [PATCH 3/3] Don't forget to name the boot perflvl "boot" Message-ID: <mailman.0.1296692536.7312.nouveau@xxxxxxxxxxxxxxxxxxxxx> --- drivers/gpu/drm/nouveau/nouveau_pm.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_pm.c b/drivers/gpu/drm/nouveau/nouveau_pm.c index de18bf2..201a15f 100644 --- a/drivers/gpu/drm/nouveau/nouveau_pm.c +++ b/drivers/gpu/drm/nouveau/nouveau_pm.c @@ -510,6 +510,7 @@ nouveau_pm_init(struct drm_device *dev) /* determine current ("boot") performance level */ ret = nouveau_pm_perflvl_get(dev, &pm->boot); if (ret == 0) { + strcpy(pm->boot.name, "boot"); pm->cur = &pm->boot; nouveau_pm_perflvl_info(&pm->boot, info, sizeof(info)); -- 1.7.4 --------------010907050904040909000000-- From bugzilla-daemon at freedesktop.org Wed Feb 2 17:48:39 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Wed, 2 Feb 2011 17:48:39 -0800 (PST) Subject: [Bug 32959] 2.6.37 - NV11 goes into GPU hang In-Reply-To: <bug-32959-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-32959-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110203014839.62F6113004E@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=32959 Francisco Jerez <currojerez at riseup.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #36 from Francisco Jerez <currojerez at riseup.net> 2011-02-02 17:48:38 PST --- (In reply to comment #35) > Thank you, the two patches given above fixed the problem entirely for me, no > more X or kernel hangs with 2.6.37. I now consider this report closed. Until > the next time :) This should be fixed in nouveau/master now, marking as resolved. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From ef at math.uni-bonn.de Thu Feb 3 10:59:43 2011 From: ef at math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=) Date: Thu, 3 Feb 2011 19:59:43 +0100 Subject: TDMS bandwidth limits Message-ID: <DE8B09DD-4ACE-499A-A33C-C12C005803F0@xxxxxxxxxxxxxxxx> I'm curious what the TDMS bandwidth limit values in get_tmds_link_bandwidth() are based on. We're using chipset == 44 cards that happily run 1600x1200 at 60 using the propriety driver and which also used to work with nouveau up to Linux 2.6.36.2. Since 2.6.37, nouveau refuses to use that mode because the required 163M pixel clock exceeds the computed TDMS bandwidth of 155M (earlier versions allowed for 165M regardless of chipset value). Although I cannot tell for sure which timing the closed-source driver runs 1600x1200 at 60 with on these monitors, I find it unlikely that it uses some built-in, non-EDID timing requiring a lower pixel clock. I also don't suspect NVidia running their own chips above specs. So either NVidia doesn't disclose the specs even to their own programmers, the values in get_tmds_link_bandwidth() are wrong, or, more likely, I'm missing something. Patching get_tmds_link_bandwidth() to allow for 165M already for chipset >= 0x44 appears to work. However, I don't feel comfortable with stretching rates above spec. From mahatma at bspu.unibel.by Thu Feb 3 11:26:34 2011 From: mahatma at bspu.unibel.by (Dzianis Kahanovich) Date: Thu, 03 Feb 2011 21:26:34 +0200 Subject: nv4c broken after october (approx.) In-Reply-To: <AANLkTi=Ts_vC9BP6YTqNWn93zpFTTwZCbs3__-TyHbSR@xxxxxxxxxxxxxx> References: <4D499444.20009@xxxxxxxxxxxxxx> <AANLkTi=Ts_vC9BP6YTqNWn93zpFTTwZCbs3__-TyHbSR@xxxxxxxxxxxxxx> Message-ID: <4D4B016A.2040704@xxxxxxxxxxxxxx> Xavier Chantry wrote: >> After october I got broken image on my integrated nv4c chip (are you need >> precise model?). I don't know precise time points, but now known: in Gentoo ... > This is the third report I see today.. for a patch 3-4 months old. At > least according to wilder on IRC. > > http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=c88f13e25b0040c1dd0f93e0ac40f62a6005ce59 Thanx! I reverse this patch and return to accelerated... > 17:44 curro >> wilder: do you get the same corruption with a > 1024x768 framebuffer? > > So what's your resolution and can you try to force 1024x768, as > explained there : > http://nouveau.freedesktop.org/wiki/KernelModeSetting Not so trivial, becouse fb.ko (fbmem.c) module not listen for cmdline. But I use harcoded into drm_fb_helper.c (this is faster then full rebuild to integrate fb.ko). So, all combinations pairs - fb 1024x768,1280x1024 and xorg.conf 1024x768,1280x1024 make same corruption without patch rollback. -- WBR, Dzianis Kahanovich AKA Denis Kaganovich, http://mahatma.bspu.unibel.by/ From currojerez at riseup.net Thu Feb 3 13:40:52 2011 From: currojerez at riseup.net (Francisco Jerez) Date: Thu, 03 Feb 2011 22:40:52 +0100 Subject: TDMS bandwidth limits In-Reply-To: <DE8B09DD-4ACE-499A-A33C-C12C005803F0@xxxxxxxxxxxxxxxx> ("Edgar =?utf-8?Q?Fu=C3=9F=22's?= message of "Thu, 3 Feb 2011 19:59:43 +0100") References: <DE8B09DD-4ACE-499A-A33C-C12C005803F0@xxxxxxxxxxxxxxxx> Message-ID: <87k4hg4x0b.fsf@xxxxxxxxxx> Edgar Fu? <ef at math.uni-bonn.de> writes: > I'm curious what the TDMS bandwidth limit values in get_tmds_link_bandwidth() are based on. They're based on what the nvidia proprietary driver itself refuses to do, though, I'm not 100% sure that I had nv44 in my sample when I made that change. > We're using chipset == 44 cards that happily run 1600x1200 at 60 using the propriety driver and which also used to work with nouveau up to Linux 2.6.36.2. Since 2.6.37, nouveau refuses to use that mode because the required 163M pixel clock exceeds the computed TDMS bandwidth of 155M (earlier versions allowed for 165M regardless of chipset value). > Although I cannot tell for sure which timing the closed-source driver runs 1600x1200 at 60 with on these monitors, I find it unlikely that it uses some built-in, non-EDID timing requiring a lower pixel clock. I also don't suspect NVidia running their own chips above specs. It might be using a reduced-blanking mode, check your Xorg.0.log to be sure. See the "-logverbose" option if you don't get all the timings printed out with the default verbosity level. > So either NVidia doesn't disclose the specs even to their own programmers, the values in get_tmds_link_bandwidth() are wrong, or, more likely, I'm missing something. > Patching get_tmds_link_bandwidth() to allow for 165M already for chipset >= 0x44 appears to work. However, I don't feel comfortable with stretching rates above spec. > _______________________________________________ > Nouveau mailing list > Nouveau at lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/nouveau -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 229 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20110203/f6fb6ae2/attachment.pgp> From bugzilla-daemon at freedesktop.org Thu Feb 3 16:34:25 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Thu, 3 Feb 2011 16:34:25 -0800 (PST) Subject: [Bug 33445] NVS 3100M : Blank screen on kernel module loading In-Reply-To: <bug-33445-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-33445-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110204003425.AC4A513004F@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=33445 --- Comment #4 from Tomasz Wasiak <tjwasiak at poczta.onet.pl> 2011-02-03 16:34:25 PST --- Do you have fbcon configured as a module? You have to load it then... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla-daemon at freedesktop.org Thu Feb 3 19:15:58 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Thu, 3 Feb 2011 19:15:58 -0800 (PST) Subject: [Bug 33887] New: nouveau causes graphic corruption were you cant do anything Message-ID: <bug-33887-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> https://bugs.freedesktop.org/show_bug.cgi?id=33887 Summary: nouveau causes graphic corruption were you cant do anything Product: xorg Version: 7.6 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: blocker Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: oninekoze at gmail.com QAContact: xorg-team at lists.x.org Created an attachment (id=42914) --> (https://bugs.freedesktop.org/attachment.cgi?id=42914) snapshot of graphic coruption with ubuntu on an hp pavilion dv6605us(dv6500) and a GeForce 7150m / nForce 630M built in graphics theres so bad of graphic corruption where you can only see the mouse correctly which is shown in the snapshot attachment the only way to get past it is by disabling and/or completely removing nouveau i have made a report to ubuntu's launchpad https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/711591 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From ef at math.uni-bonn.de Fri Feb 4 03:33:48 2011 From: ef at math.uni-bonn.de (Edgar =?iso-8859-1?B?RnXf?=) Date: Fri, 4 Feb 2011 12:33:48 +0100 Subject: TDMS bandwidth limits In-Reply-To: <87k4hg4x0b.fsf@xxxxxxxxxx> References: <DE8B09DD-4ACE-499A-A33C-C12C005803F0@xxxxxxxxxxxxxxxx> <87k4hg4x0b.fsf@xxxxxxxxxx> Message-ID: <20110204113348.GQ26554@xxxxxxxxxxxxxxxxxxxxxx> > They're based on what the nvidia proprietary driver itself refuses to do, Ah, I see. Thanks. > though, I'm not 100% sure that I had nv44 in my sample when I made > that change. Looks like you were correct with the 155 limit for 44. > It might be using a reduced-blanking mode, Indeed it does. I had regarded this as unlikely given that, after all, the driver simply can't know how much blanking reduction the monitor will be able to cope with. > check your Xorg.0.log to be sure. See the "-logverbose" option if you don't > get all the timings printed out with the default verbosity level. I do get the timings printed with -logverbose 9. I also get a message to the effect that reduced blanking was used to get the pixel clock within limits. What I don't get is the timing actually being used. Looks I have to figure out the values myself (and see how to teach the nouveau fb to use it). Thanks for your help. From bugzilla-daemon at freedesktop.org Fri Feb 4 04:04:00 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Fri, 4 Feb 2011 04:04:00 -0800 (PST) Subject: [Bug 30135] The KDE icons is broken In-Reply-To: <bug-30135-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-30135-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110204120400.89BBC13004E@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=30135 --- Comment #5 from Dmitry Samoyloff <dmitry at obscurehalt.org> 2011-02-04 04:04:00 PST --- This bug doesn't show up anymore: Nouveau from VCS, xorg-server-1.9.2. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla-daemon at freedesktop.org Fri Feb 4 05:59:12 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Fri, 4 Feb 2011 05:59:12 -0800 (PST) Subject: [Bug 33887] nouveau causes graphic corruption were you cant do anything In-Reply-To: <bug-33887-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-33887-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110204135912.D6DB613004D@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=33887 --- Comment #1 from berbae <roger.berny at sfr.fr> 2011-02-04 05:59:12 PST --- I have the same display corruption with : nVidia Corporation C73 [GeForce 7100 / nForce 630i] (rev a2) Linux arch64 2.6.37-ARCH #1 SMP PREEMPT Sat Jan 29 20:00:33 CET 2011 x86_64 Pentium(R) Dual-Core CPU E5200 @ 2.50GHz GenuineIntel GNU/Linux In the Arch Linux forum thread : https://bbs.archlinux.org/viewtopic.php?id=112758 other persons mentioned the same problem. It seems to concern NV3x and NV4x chipsets. It happens with the upgrades : libdrm 2.4.22 -> 2.4.23 libgl 7.9.0.git20101207 -> 7.10 libva 1.0.6 -> 1.0.8 mesa 7.9.0.git20101207 -> 7.10 xf86-video-nouveau 0.0.16_git20100819 -> 0.0.16_git20101217 See also the bug report in the Arch Linux flyspray : https://bugs.archlinux.org/task/22700?project=1 Everything seems normal in the log files, and the processes are running ok, X server and the WM processes are started normally. Only the mouse cursor works and the display is totally unusable as shown in the screenshots. Downgrading to the previous release version restore the display as normal. Please look into this horrible regression to fix it, because the recent release of the nouveau driver is totally unusable. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla-daemon at freedesktop.org Fri Feb 4 07:27:11 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Fri, 4 Feb 2011 07:27:11 -0800 (PST) Subject: [Bug 30135] The KDE icons is broken In-Reply-To: <bug-30135-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-30135-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110204152711.9C4F913004D@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=30135 Lucas Stach <dev at lynxeye.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #6 from Lucas Stach <dev at lynxeye.de> 2011-02-04 07:27:10 PST --- This was likely a bug in the now reworked kernel vm part. As there are two reports of "working with recent code" I'm closing this as fixed. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From rambham at gmail.com Wed Feb 2 21:16:25 2011 From: rambham at gmail.com (Ram Bhamidipaty) Date: Wed, 2 Feb 2011 21:16:25 -0800 Subject: dual display - one LCD panel flashing on and off Message-ID: <AANLkTin+4J7oD6x2LKoB1VCkZqUqC34c0Yz=pPY2bZye@xxxxxxxxxxxxxx> Hi, I run Arch Linux and ran into a problem with the nouveau driver that was fixed by reverting back to the nvidia driver. I have a GeForce 6600 LE card - and two LCD panels - one VGA and the other DVI. The DVI panel was switching on and off - what I mean is that for 30-40 seconds the display would be normal and then for maybe 2 or 5 seconds the display would go blank. The monitors power display suggested that the screen image was all black - I don't think the LCD was going into a low power mode. Switching back to the nvidia driver fixed the problem. I am running 2.6.37-ARCH. I'm not on the nouveau email list. -Ram From jasper.mackenzie at gmail.com Fri Feb 4 19:58:57 2011 From: jasper.mackenzie at gmail.com (Jasper Mackenzie) Date: Sat, 05 Feb 2011 16:58:57 +1300 Subject: Black screen of death Message-ID: <op.vqev0hi1o2qfwp@localhost> Good day All. I switched to nouveau some months back with all packages from Ubuntu Natty and xorg-edgers ppa on an Nvidia Go 7950 GTX in a Dell XPS M1710. All worked very well, better if you dont count 3d speed, and thermal management... These cards are aprently renoun to burn up, and a month ago I thought I had fried it, as I could not get it to start X with the nv, Nvidia, or Nouveau driver. Eventually it worked with Nvidia again. With the new xorg, 1.10, Nvidia is not an option. Reverting to nouveau had the same troubles as previously. Screen goes blank soon after initrd loads, and does not return. Ubuntu adds "set gfxpayload=$linux_gfx_mode" to grub.cfg, and removing this option, and splash and quiet, _sometimes_ allowed console login, but always black screen if X tried to start Blacklisting the nouveau kernel module stopped the black screen of death, but X would not start with boot option nouveau.modeset=0 stoppes black screen of death stops, but X fails to start with nouveau driver. nv works with nouveau blacklisted or modeset disabled. nv does not resume 1 in 3. Some logs: http://pastebin.com/4wYuV0RX More specific logs available if needed, cant find the pastebin links atm lynxeye suggested that this is an issue with "shit in EDID", I tried adding the video=LVDS option to no effect, and xrandr via ssh into running X (with blank screen). I have tried various kernel/userspace configuartions (2.6.33-38), ubuntu natty X, xorg-edgers X, recent opensuse, fedora, and mint live images, all with the same issues. To reiterate, it was working well with nouveau, then suddenly stopped. It must have been after an upgrade, but I cannot be sure. TIA Jasper From bugzilla-daemon at freedesktop.org Fri Feb 4 22:49:09 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Fri, 4 Feb 2011 22:49:09 -0800 (PST) Subject: [Bug 33668] [regression] [nv4c] Screen corruption In-Reply-To: <bug-33668-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-33668-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110205064909.7A12E13004D@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=33668 --- Comment #5 from Tomasz Wasiak <tjwasiak at poczta.onet.pl> 2011-02-04 22:49:09 PST --- Did some additional tests yesterday. Using newest sources from git I found using NoAccel is sufficient to make it working... But having no acceleration is not what I was looking for. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla-daemon at freedesktop.org Fri Feb 4 22:53:51 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Fri, 4 Feb 2011 22:53:51 -0800 (PST) Subject: [Bug 33887] nouveau causes graphic corruption were you cant do anything In-Reply-To: <bug-33887-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-33887-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110205065351.0AC1613004F@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=33887 --- Comment #2 from Tomasz Wasiak <tjwasiak at poczta.onet.pl> 2011-02-04 22:53:50 PST --- This is same corruption I am having on GeForce 6100/nForce 430 (bug #33688). Try using NoAccel or ShadowFB option in xorg.conf and check if that helps... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla-daemon at freedesktop.org Fri Feb 4 23:00:45 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Fri, 4 Feb 2011 23:00:45 -0800 (PST) Subject: [Bug 33887] nouveau causes graphic corruption were you cant do anything In-Reply-To: <bug-33887-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-33887-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110205070045.2D0C213004F@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=33887 --- Comment #3 from Tomasz Wasiak <tjwasiak at poczta.onet.pl> 2011-02-04 23:00:44 PST --- (In reply to comment #2) > This is same corruption I am having on GeForce 6100/nForce 430 (bug #33688). > > Try using NoAccel or ShadowFB option in xorg.conf and check if that helps... I do not know why BugZilla refers to wrong bug (I was writing about https://bugs.freedesktop.org/show_bug.cgi?id=33668)... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla-daemon at freedesktop.org Sat Feb 5 01:32:22 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Sat, 5 Feb 2011 01:32:22 -0800 (PST) Subject: [Bug 33887] nouveau causes graphic corruption were you cant do anything In-Reply-To: <bug-33887-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-33887-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110205093222.3678C13004E@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=33887 --- Comment #4 from zeruke <oninekoze at gmail.com> 2011-02-05 01:32:21 PST --- @Tomasz Wasiak both of those options don't work but i did find a thing in tty1 stating [ 8.520202] [drm] nouveau 0000:00:12.0: ======= misaligned reg 0x001020FB ======= [ 8.520217] [drm] nouveau 0000:00:12.0: ======= misaligned reg 0x001020FB ======= -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla-daemon at freedesktop.org Sat Feb 5 05:26:02 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Sat, 5 Feb 2011 05:26:02 -0800 (PST) Subject: [Bug 33887] nouveau causes graphic corruption were you cant do anything In-Reply-To: <bug-33887-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-33887-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110205132602.E8C5013004E@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=33887 --- Comment #5 from Maarten Maathuis <madman2003 at gmail.com> 2011-02-05 05:26:01 PST --- My guess is that something is wrong with tiled scanout. This was enabled with commit http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=c88f13e25b0040c1dd0f93e0ac40f62a6005ce59 You're not the first to complain, and it's maybe a good to gather the "real" names of problem cards. In my log i have: [drm] nouveau 0000:01:00.0: Detected an NV50 generation card (0x096000c1) You should have something with NV40 or NV44 generation card, the 96 in my case means that i have an NV96. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla-daemon at freedesktop.org Sat Feb 5 05:46:57 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Sat, 5 Feb 2011 05:46:57 -0800 (PST) Subject: [Bug 33887] nouveau causes graphic corruption were you cant do anything In-Reply-To: <bug-33887-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-33887-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110205134657.5385413004D@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=33887 --- Comment #6 from Xavier <shiningxc at gmail.com> 2011-02-05 05:46:57 PST --- List of cards reported so far, I looked up for codenames on http://nouveau.freedesktop.org/wiki/CodeNames GeForce 7150m / nForce 630M - nv67 GeForce 7100 / nForce 630i - nv67? GeForce 6100 / nForce 430 - nv4e GeForce 6150SE nForce 430 - nv4c GeForce FX Go5700 - nv36 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla-daemon at freedesktop.org Sat Feb 5 06:13:02 2011 From: bugzilla-daemon at freedesktop.org (bugzilla-daemon at freedesktop.org) Date: Sat, 5 Feb 2011 06:13:02 -0800 (PST) Subject: [Bug 33887] nouveau causes graphic corruption were you cant do anything In-Reply-To: <bug-33887-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> References: <bug-33887-8800@xxxxxxxxxxxxxxxxxxxxxxxxx/> Message-ID: <20110205141303.0A64F13004E@xxxxxxxxxxxxxxxxxxxxxxxx> https://bugs.freedesktop.org/show_bug.cgi?id=33887 --- Comment #7 from berbae <roger.berny at sfr.fr> 2011-02-05 06:13:02 PST --- For the GeForce 7100 / nForce 630i I have in the log : [drm] nouveau 0000:00:10.0: Detected an NV40 generation card (0x063000a2)
