Bug#702809: gnome-shell: gnome randomly freezes
FWIW, I filed bug reports regarding this issue back in December against both the binary nVidia driver and the nouveau package (bugs #696554 and #696360). I ended up chasing this for a few weeks, working with the upstream nouveau devs via IRC. I built dozens of kernels (ranging from the Debian 3.2.0-4, several from the vanilla upstream 3.4.x long-term stable series, and up to the nouveau git master) attempting to bisect the problem, but never found a working kernel which did not exhibit the freezing issue in gnome-shell. This, or a similar issue, is currently being discussed on the Debian forums: http://forums.debian.net/viewtopic.php?f=10t=100041 As the freezing is affecting users of all 3 major graphics chipsets, I am beginning to think this issue is video-device-agnostic and likely specific to gnome-shell itself, perhaps a problem with compositing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696360: nvidia-glx: Sporadic X freezes in gnome shell
This issue is specific to gnome-shell. In the four months since I reported this, I've been running in XFCE without a single problem. Every so often when I build a newer kernel I'll pop back into a gnome session and reproduce this freeze within a short time. I've essentially ruled out the hardware as the culprit. Under XFCE I can run the full suite of piglet openGL tests. Additionally, in Windows 7 I can overclock the GPU and hit it with hours of FurMark stress testing, again without a hiccup. If it can handle such an extreme load, I don't think rendering a few Gnome windows should be too much to ask. After I hit upon this bug back in December I ended up ditching the binary blob and sticking with nouveau. The same (albiet different syslog messages) freezing problem happens with that driver as well. I spent a lot of time trying to track this down with the help of the upstream nouveau folks on IRC and tried out some patches against their git head rev. Still couldn't get to the root cause, so ended up just sticking with XFCE. I do hope this gets some more attention as Wheezy proliferates after release. It may not even be nVidia-specific, as there's a thread on the Debian forums regarding this same problem using ATI graphics as well. If ever we could come up with a reliable STR, this may need to be changed to affecting the gnome-shell package, not the graphics driver. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677682: xfce4: Waking up from hibernation shows what's open before being locked
Showing the contents of the desktop/windows on a system that is supposed to be locked is a serious security issue. I am surprised to find this behavior in the current xscreensaver and more surprised to see this listed as a minor severity bug here on Debian. This same problematic behavior occurred a few years ago with Ubuntu and gnome-screensaver. It was fixed shortly thereafter. Ubuntu took the problem very seriously and the bug in Launchpad was listed as critical: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/390989 Upstream gnome also assigned the bug a severity of critical: https://bugzilla.gnome.org/show_bug.cgi?id=654746 I hope this can be addressed in the current Debian Wheezy with Xfce4. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696554: Processed: change severity 696554 serious
Control: severity -1 important On 2012-12-27 08:15 +0100, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: severity 696554 serious Bug #696554 [xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: Using the open source nouveaux driver is causing sytem to lockup hard Severity set to 'serious' from 'important' Please stop that, changing the severity is wrong and does not help to resolve your problem. Thanks, Sven Please stop downgrading the severity of my bug. I initially reported this as a serious bug, and it is. I reestablished the Serious severity of this issue as it's causing massive system instability and potential data loss. this problem is wheezy release-critical for sure. Additionally, I have a parallel bug (same symptoms) with the non-free nVidia driver filed as bug #696360. That bug carries a severity level of Serious, for the exact same reasons, without anyone downgrading it. Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696554: System freezes and lockups
- Original Message - From: Sven Joachim svenj...@gmx.de To: Mar Mel marmel6...@yahoo.com Cc: 696...@bugs.debian.org; Steven Chamberlain ste...@pyro.eu.org Sent: Thursday, December 27, 2012 2:50 AM Subject: Re: Bug#696554: System freezes and lockups On 2012-12-27 07:47 +0100, Mar Mel wrote: Okay, less than 24hrs uptime and the system froze completely. I was really hoping (with dumb luck) the newly landed 3.2.35 kernel would help out even though there were no specific nouveaux changes. Could you please try a 3.7 kernel, available in experimental, and see if that works better? Cheers, Sven Yes, thanks for the kernel suggestion. I was planning to install 3.6.9 from experimental today but first I wanted to give the latest LTS kernel 3.4.x series a shot. Last night after having another full freeze, I installed the 3.4.23 kernel, but met with the same results of constant nouveaux syslog errors. I've installed 3.7.1 from experimental today, and so far (30 min) have not had a single nouveaux message or freeze. I will continue using this kernel for the next several days if it is problem-free. One issue I have is I can't seem to install the headers I need for Virtualbox to run. $ sudo apt-get -V -s install -t experimental linux-headers-3.7-trunk-amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-headers-3.7-trunk-amd64 : Depends: linux-kbuild-3.7 but it is not installable E: Unable to correct problems, you have held broken packages. It seems the linux-kbuild-3.7 package is not in the experimental repository. Could you please advise how I might get the needed headers installed? Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696554: System freezes and lockups
- Original Message - From: Steven Chamberlain ste...@pyro.eu.org To: Mar Mel marmel6...@yahoo.com Cc: Sven Joachim svenj...@gmx.de; 696...@bugs.debian.org 696...@bugs.debian.org Sent: Thursday, December 27, 2012 1:10 PM Subject: Re: Bug#696554: System freezes and lockups On 27/12/12 17:48, Mar Mel wrote: One issue I have is I can't seem to install the headers I need for Virtualbox to run. Even if you had the headers, I'm not sure VBox as packaged right now can compile against them. See http://bugs.debian.org/696011 I have virtualbox 4.1.24 installed locally. On my laptop (arch linux), the vbox kernel modules build successfully against all kernel series thus far, though I'm still at 3.6.10 there, so haven't tried 3.7.x. series yet. Is there something obvious I'm overlooking in installing the headers for 3.7.1 from experimental? One of my vm's is a critical need. This raises a new question though: Besides the kernel, what else is different about your setup now since yesterday? It seems the virtualbox modules will not be loaded now. The kernel is the only change since yesterday. I'm not aware of any other non-free modules other than virtualbox and truecrypt. The vbox modules were loaded yesterday with the stock wheezy 3.2.0-4 and vanilla 3.4.23. They are not loaded now since I can't build them due to the header installation issue. Also you mentioned truecrypt before - that has non-free kernel modules I think? Were those modules loaded yesterday; are they loaded now? Truecrypt module has been loaded in all instances, including the current 3.7.1 kernel running now. Anything else in the kernel yesterday, especially non-free modules? I'm not sure how to show the kernel taint status, or get the list of modules (as seen in a kernel Oops) where non-free modules are tagged... Not that I know of. I do have a serious _new_ problem though. One of the first things I tested with this new kernel is the suspen/resume function. When the system resumes, the GPU fan runs at full speed! I've verified after multiple reboots and suspend/resume cycles. Any thoughts on how to remedy this problem? In summary: 1) the 3.7.1 kernel from experimental seems to solve this bug. I won't be able to confirm this until at least several days of nouveaux-problem-free uptime. 2) I need to install the matching kernel headers. Help please? 3) After resume, GPU fan runs 100% speed. Help please? Thanks Steven and Sven for followuping up on this so diligently. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696554: System freezes and lockups
- Original Message - From: Sven Joachim svenj...@gmx.de To: Mar Mel marmel6...@yahoo.com Cc: 696...@bugs.debian.org; Steven Chamberlain ste...@pyro.eu.org Sent: Thursday, December 27, 2012 1:32 PM Subject: Re: Bug#696554: System freezes and lockups On 2012-12-27 18:48 +0100, Mar Mel wrote: Yes, thanks for the kernel suggestion. I was planning to install 3.6.9 from experimental today but first I wanted to give the latest LTS kernel 3.4.x series a shot. Last night after having another full freeze, I installed the 3.4.23 kernel, but met with the same results of constant nouveaux syslog errors. I've installed 3.7.1 from experimental today, and so far (30 min) have not had a single nouveaux message or freeze. I will continue using this kernel for the next several days if it is problem-free. One issue I have is I can't seem to install the headers I need for Virtualbox to run. Yes, that is not possible. However, loading the virtualbox kernel module invalidates your warranty on the kernel anyway. Have you tried to reproduce the problem with the 3.2 kernel and vboxdrv.ko _not_ loaded? I have completely purged virtualbox and all kernel headers. Yes, I can reproduce the nouveaux driver errors with the 3.2.0-4 wheezy kernel without vbox modules loaded. Currently no modules taint the kernel. Upon further investigation, truecrypt uses the built-in crypto module, so that is not affecting this issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696554: System freezes and lockups
- Original Message - From: Steven Chamberlain ste...@pyro.eu.org To: Mar Mel marmel6...@yahoo.com; 696...@bugs.debian.org Cc: Sven Joachim svenj...@gmx.de Sent: Thursday, December 27, 2012 3:27 PM Subject: Re: Bug#696554: System freezes and lockups Thanks for the logs. Do you have a dual monitor setup? No I only have a single monitor. If so, set glxgears running on one of them where you'll be able to see it. Then please try this from a terminal window on the other monitor: I've pinned a glxgears window for an hour while playing video at the same time without triggering the freeze. As I've said, it seems comletely independent of the load on the GPU. $ mplayer -nosound -vo xv -dr -fs somefile.avi (Any video file should be okay as long as it's at least 10 seconds long.) I can sometimes play HD (.mkv, .mts) video for hours without fail. The complete system freeze takes up to a full day's useage to happen, or it can happen within minutes of booting. This is just to see if it can trigger the freezes on demand. Last night I thought I'd found a trigger by syncing package database in Synaptic. I had two consecutive full freeze/lockups while the progress bar was displayed. Unfortunately, I cannot reproduce it reliably. Must have been coincidental. Twice now, I've had a hard lockup while _only_ running Synaptic. Last night was one of the quickest @2410 seconds (see below) uptime. I waited for a while to see if it would thaw by itself, but it was locked up hard. 1) I was unable to switch virtual consoles 2) Could not toggle NumLock/CapsLock keys 3) Mouse pointer still moved (as always) 4) Required magic sysrq to reboot 5) There was no suspend/resume cycle before the lockup, so at least I've ruled that out as a culprit. Dec 27 01:38:14 humonculux kernel: [ 9.370761] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Dec 27 01:38:14 humonculux kernel: [ 9.371048] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Dec 27 01:38:14 humonculux dhclient: Internet Systems Consortium DHCP Client 4.2.2 Dec 27 01:38:14 humonculux dhclient: Copyright 2004-2011 Internet Systems Consortium. Dec 27 01:38:14 humonculux dhclient: All rights reserved. Dec 27 01:38:14 humonculux dhclient: For info, please visit https://www.isc.org/software/dhcp/ Dec 27 01:38:14 humonculux dhclient: Dec 27 01:38:14 humonculux NetworkManager[3154]: info (eth0): DHCPv4 state changed nbi - preinit Dec 27 01:38:14 humonculux dhclient: Listening on LPF/eth0/38:60:77:5a:01:9b Dec 27 01:38:14 humonculux dhclient: Sending on LPF/eth0/38:60:77:5a:01:9b Dec 27 01:38:14 humonculux dhclient: Sending on Socket/fallback Dec 27 01:38:14 humonculux dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Dec 27 01:38:14 humonculux dhclient: DHCPACK from 192.168.0.1 Dec 27 01:38:14 humonculux NetworkManager[3154]: info (eth0): DHCPv4 state changed preinit - reboot Dec 27 01:38:14 humonculux dhclient: bound to 192.168.0.100 -- renewal in 2147483648 seconds. Dec 27 01:38:14 humonculux NetworkManager[3154]: info address 192.168.0.100 Dec 27 01:38:14 humonculux NetworkManager[3154]: info prefix 24 (255.255.255.0) Dec 27 01:38:14 humonculux NetworkManager[3154]: info gateway 192.168.0.1 Dec 27 01:38:14 humonculux NetworkManager[3154]: info nameserver '192.168.0.1' Dec 27 01:38:14 humonculux NetworkManager[3154]: info Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled... Dec 27 01:38:14 humonculux NetworkManager[3154]: info Activation (eth0) Stage 5 of 5 (IPv4 Commit) started... Dec 27 01:38:14 humonculux avahi-daemon[3085]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.100. Dec 27 01:38:14 humonculux avahi-daemon[3085]: New relevant interface eth0.IPv4 for mDNS. Dec 27 01:38:14 humonculux avahi-daemon[3085]: Registering new address record for 192.168.0.100 on eth0.IPv4. Dec 27 01:38:15 humonculux avahi-daemon[3085]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::3a60:77ff:fe5a:19b. Dec 27 01:38:15 humonculux avahi-daemon[3085]: New relevant interface eth0.IPv6 for mDNS. Dec 27 01:38:15 humonculux avahi-daemon[3085]: Registering new address record for fe80::3a60:77ff:fe5a:19b on eth0.*. Dec 27 01:38:15 humonculux NetworkManager[3154]: info (eth0): device state change: ip-config - activated (reason 'none') [70 100 0] Dec 27 01:38:15 humonculux NetworkManager[3154]: info Policy set 'MetroCast Cable' (eth0) as default for IPv4 routing and DNS. Dec 27 01:38:15 humonculux NetworkManager[3154]: info Activation (eth0) successful, device activated. Dec 27 01:38:15 humonculux NetworkManager[3154]: info Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete. Dec 27 01:38:15 humonculux dbus[2893]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) Dec 27 01:38:15 humonculux dbus[2893]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Dec 27 01:38:16 humonculux
Bug#696554: System freezes and lockups
- Original Message - From: Steven Chamberlain ste...@pyro.eu.org To: Mar Mel marmel6...@yahoo.com; 696...@bugs.debian.org Cc: Sven Joachim svenj...@gmx.de Sent: Thursday, December 27, 2012 5:44 PM Subject: Re: Bug#696554: System freezes and lockups The reason I ask - is that I can reproduce immediate freezes that way, and errors that resemble the ones from your kernel logs (see attached excerpt). gnome-shell also triggers these often, which I thought was related to acceleration or VBlank; the xfce4 desktop doesn't trigger it at all. So I thought you could maybe try xfce4 for a while just to see if it is any more stable (it can be installed alongside gnome-shell; your login manager should give you a choice of what session to log into). I'd been wondering for some time if our issues had the same cause, as we both have NV50-family cards, but my 8800 GT is a G92 chipset whereas yours is a NVA0/GT200 chipset. So I'm not sure how 'similar' they really are in terms of the driver code. Regards, -- Steven Chamberlain ste...@pyro.eu.org I had no idea that you also were experiencing this, or a very similar issue. That's good to know. For testing purposes, I've installed xfce4 and will hang out in it for a while to see if indeed these freezes are specific to gnome only. I specifically chose debian for my desktop to have the most stable gnome shell experience, so it'll be a real bummer if it turns out to be unusable! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696554: System freezes and lockups
- Original Message - From: Steven Chamberlain ste...@pyro.eu.org To: Mar Mel marmel6...@yahoo.com; 696...@bugs.debian.org Cc: Sent: Tuesday, December 25, 2012 11:00 PM Subject: Re: Bug#696554: System freezes and lockups Control: tags -1 - moreinfo Okay, thanks for checking! And for providing the info Sven asked for. So you're seeing errors already, but there are no ill effects yet? The only ill effect I am seeing is temporary freezing of the display. It has not requred a REISUB yet. I'd like to know if it really does end up crashing this time. And then: * can Alt-F1 still switch consoles? (you said no before) So far with nouveaux I've been able to get to a virtual terminal when the display has frozen. I've not had to take any action. The freezes thus far have lasted for about 10 seconds at the most, and some are just minor (less than 1 second) hiccups. * does the mouse pointer still move? (I guess not?) In the case of both the nouveaux freeze and the non-free driver freeze, the mouse pointer has always been able to be moved. The mouse cursor has _never_ frozen...yet. * can you find anything specific that triggers it? (so far, no?) Definitely not. As I've said there can be barely any windows open and never anything intense. It's not to do with heat or heavy GPU useage. I know how frustrating intermittent issue are to troubleshoot. Hopefully we'll get somewhere with this. And then I think there will be enough information to file an upstream bug report. Hopefully someone else has some ideas though. No freezes, but I am getting constantly hammered with errors in the syslog, so all is clearly _not_ well! Dec 26 17:05:49 humonculux kernel: [19347.541332] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x002001f17c Put 0x0020020ac4 IbGet 0x04cd IbPut 0x04ce State 0x8000f418 (err: INVALID_CMD) Push 0x00400040 Dec 26 17:05:49 humonculux kernel: [19347.554300] [drm] nouveau :01:00.0: PGRAPH - DATA_ERROR INVALID_VALUE Dec 26 17:05:49 humonculux kernel: [19347.554312] [drm] nouveau :01:00.0: PGRAPH - DATA_ERROR Dec 26 17:05:49 humonculux kernel: [19347.554314] [drm] nouveau :01:00.0: PGRAPH - ch 2 (0x0001256000) subc 7 class 0x8397 mthd 0x1414 data 0x0012 Dec 26 17:06:02 humonculux kernel: [19360.520859] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x002003abf0 Put 0x002003c7f0 IbGet 0x0ebf IbPut 0x0ec0 State 0x8054 (err: INVALID_CMD) Push 0x00400040 Dec 26 17:08:37 humonculux kernel: [19514.455322] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x0020032cf4 Put 0x00200348f4 IbGet 0x0991 IbPut 0x0992 State 0x8054 (err: INVALID_CMD) Push 0x00400040 Dec 26 17:09:09 humonculux dbus[2886]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Dec 26 17:09:09 humonculux dbus[2886]: [system] Successfully activated service 'org.freedesktop.PackageKit' Dec 26 17:09:52 humonculux kernel: [19589.424819] [drm] nouveau :01:00.0: PGRAPH - TRAP_TPDMA - TP2: Unhandled ustatus 0x0004 Dec 26 17:09:52 humonculux kernel: [19589.424830] [drm] nouveau :01:00.0: PGRAPH - TRAP_TPDMA - TP6: Unhandled ustatus 0x0004 Dec 26 17:09:52 humonculux kernel: [19589.424834] [drm] nouveau :01:00.0: PGRAPH - TRAP Dec 26 17:09:52 humonculux kernel: [19589.424836] [drm] nouveau :01:00.0: PGRAPH - ch 2 (0x0001256000) subc 7 class 0x8397 mthd 0x15e0 data 0x Dec 26 17:09:52 humonculux kernel: [19589.424942] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 1 - Unknown fault at address 00240e4000 Dec 26 17:09:52 humonculux kernel: [19589.424952] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 1 - e0c: , e18: , e1c: , e20: 2a00, e24: 0003 Dec 26 17:09:52 humonculux kernel: [19589.424959] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 5 - Unknown fault at address 00240e4400 Dec 26 17:09:52 humonculux kernel: [19589.424961] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 5 - e0c: , e18: , e1c: 0010, e20: 2a00, e24: 0003 Dec 26 17:09:52 humonculux kernel: [19589.424964] [drm] nouveau :01:00.0: PGRAPH - TRAP Dec 26 17:09:52 humonculux kernel: [19589.424966] [drm] nouveau :01:00.0: PGRAPH - ch 2 (0x0001256000) subc 7 class 0x8397 mthd 0x15e0 data 0x Dec 26 17:09:52 humonculux kernel: [19589.424973] [drm] nouveau :01:00.0: VM: trapped write at 0x00240e4000 on ch 2 [0x1256] PGRAPH/PROP/RT0 reason: PAGE_NOT_PRESENT Dec 26 17:09:52 humonculux kernel: [19589.424991] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 1 - Unknown fault at address 00240e4000 Dec 26 17:09:52 humonculux kernel: [19589.424993] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 1 - e0c: , e18: , e1c: 0002000e, e20: 2a00, e24: 0003 Dec 26 17:09:52 humonculux kernel: [19589.424999] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP
Bug#696554: System freezes and lockups
Okay, less than 24hrs uptime and the system froze completely. I was really hoping (with dumb luck) the newly landed 3.2.35 kernel would help out even though there were no specific nouveaux changes. * can Alt-F1 still switch consoles? (you said no before) No, this time I was unable to switch to another console * does the mouse pointer still move? (I guess not?) Yes, the mouse pointer was still moving * can you find anything specific that triggers it? (so far, no?) Still no common trigger. This time I was using synaptic package manager. Fortunately no critical operation was underway, just refreshing the package database. Looks like more of the same in the syslog: Dec 27 01:35:50 humonculux kernel: [45064.596966] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x0020029dc0 Put 0x002002cd24 IbGet 0x0592 IbPut 0x0593 State 0x80004290 (err: INVALID_CMD) Push 0x00702031 Dec 27 01:35:50 humonculux kernel: [45064.606763] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x002002cd24 Put 0x002002cd24 IbGet 0x0592 IbPut 0x0595 State 0x8000 (err: INVALID_CMD) Push 0x00400040 Dec 27 01:37:27 humonculux kernel: [45162.192607] SysRq : Keyboard mode set to system default Dec 27 01:37:29 humonculux kernel: [45163.851215] SysRq : This sysrq operation is disabled. Dec 27 01:37:31 humonculux kernel: [45166.099870] SysRq : This sysrq operation is disabled. Dec 27 01:37:33 humonculux kernel: [45167.973780] SysRq : Emergency Sync Dec 27 01:37:33 humonculux kernel: [45167.974274] Emergency Sync complete Dec 27 01:37:35 humonculux kernel: [45169.951357] SysRq : Emergency Remount R/O -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696678: tomboy: Segfault crashes tomboy during synchronization
Package: tomboy Version: 1.10.0-2 Severity: important Dear Maintainer, I filed an upstream bug report for this issue and it was duped to the following bug: https://bugzilla.gnome.org/show_bug.cgi?id=662358 When syncing notes, Tomboy crashes. it appears the notes are successfully synchronized. However, I need to restart Tomboy after every sync due to the segfault. $ [INFO 20:33:14.613] Initializing Mono.Addins (Tomboy:26514): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference. Native stacktrace: [1]+ Segmentation fault tomboy -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tomboy depends on: ii gconf2 3.2.5-1+build1 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-37 ii libcairo2 1.12.2-2 ii libdbus-glib1.0-cil 0.5.0-4 ii libdbus1.0-cil 0.7.0-5 ii libfontconfig1 2.9.0-7.1 ii libfreetype62.4.9-1 ii libgconf2.0-cil 2.24.2-2 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.33.12+really2.32.4-3 ii libglib2.0-cil 2.12.10-5 ii libgmime2.6-cil 2.6.10-1 ii libgtk2.0-0 2.24.10-2 ii libgtk2.0-cil 2.12.10-5 ii libgtkspell02.0.16-1 ii libice6 2:1.0.8-2 ii libmono-addins-gui0.2-cil 0.6.2-2 ii libmono-addins0.2-cil 0.6.2-2 ii libmono-cairo4.0-cil2.10.8.1-5 ii libmono-corlib4.0-cil 2.10.8.1-5 ii libmono-posix4.0-cil2.10.8.1-5 ii libmono-system-core4.0-cil 2.10.8.1-5 ii libmono-system-xml4.0-cil 2.10.8.1-5 ii libmono-system4.0-cil 2.10.8.1-5 ii libpango1.0-0 1.30.0-1 ii libproxy0 0.3.1-5.1 ii libsm6 2:1.2.1-2 ii libx11-62:1.5.0-1 ii mono-runtime2.10.8.1-5 tomboy recommends no packages. Versions of packages tomboy suggests: ii evolution 3.4.4-1 pn tasque none -- no debconf information ** Running Mono with --debug** [DEBUG 11:53:24.340] NoteManager created with note path /home/marc/.local/share/tomboy. [DEBUG 11:53:24.359] EnableDisable Called: enabling... True [DEBUG 11:53:24.359] Binding key 'AltF12' for '/apps/tomboy/global_keybindings/show_note_menu' [DEBUG 11:53:24.361] Binding key 'AltF11' for '/apps/tomboy/global_keybindings/open_start_here' [DEBUG 11:53:24.368] Unable to load icon 'tomboy-panel'. [INFO 11:53:24.851] Initializing Mono.Addins [DEBUG 11:53:24.882] AddinManager.OnAddinLoaded: Tomboy.Tomboy [DEBUG 11:53:24.882] Name: Tomboy.Tomboy,0.10 [DEBUG 11:53:24.882]Description: [DEBUG 11:53:24.882] Namespace: Tomboy [DEBUG 11:53:24.882]Enabled: True [DEBUG 11:53:24.883] File: /usr/lib/tomboy/Tomboy.exe [DEBUG 11:53:25.159] AddinManager.OnAddinLoaded: Tomboy.ExportToHtmlAddin [DEBUG 11:53:25.159] Name: Export to HTML [DEBUG 11:53:25.159]Description: Exports individual notes to HTML. [DEBUG 11:53:25.159] Namespace: Tomboy [DEBUG 11:53:25.159]Enabled: True [DEBUG 11:53:25.160] File: /usr/lib/tomboy/addins/ExportToHtml.dll [DEBUG 11:53:25.161] AddinManager.OnAddinLoaded: Tomboy.WebSyncServiceAddin [DEBUG 11:53:25.161] Name: Web Sync Service Add-in [DEBUG 11:53:25.161]Description: Synchronize Tomboy Notes with Tomboy Online and other compatible web services [DEBUG 11:53:25.161] Namespace: Tomboy [DEBUG 11:53:25.161]Enabled: True [DEBUG 11:53:25.161] File: /usr/lib/tomboy/addins/WebSyncServiceAddin.dll [DEBUG 11:53:25.162] AddinManager.OnAddinLoaded: Tomboy.WebDavSyncServiceAddin [DEBUG 11:53:25.162] Name: WebDav Sync Service Add-in [DEBUG 11:53:25.162]Description: Synchronize Tomboy Notes to a WebDav URL [DEBUG 11:53:25.162] Namespace: Tomboy [DEBUG 11:53:25.162]Enabled: True [DEBUG 11:53:25.163] File: /usr/lib/tomboy/addins/WebDavSyncService.dll [DEBUG 11:53:25.163] Unable to locate 'gnomesu' in your PATH [DEBUG 11:53:25.164] Using '/usr/bin/gksu' as GUI 'su' tool [DEBUG 11:53:25.164] Successfully found all system tools [DEBUG 11:53:25.164] Unable to locate 'wdfs' in your PATH [DEBUG 11:53:25.164] AddinManager.OnAddinLoaded: Tomboy.FileSystemSyncServiceAddin [DEBUG 11:53:25.164] Name: Local Directory Sync Service Add-in [DEBUG 11:53:25.164]Description: Synchronize Tomboy Notes to a local file system path [DEBUG 11:53:25.165] Namespace: Tomboy [DEBUG 11:53:25.165]Enabled: True [DEBUG
Bug#684620: gnome-screenshot: Alt+Print gives corrupted image
I am seeing this same bug on current Wheezy with nVidia drivers 304.48. Is this an nVidia bug for sure or could it be an issue with gnome-screenshot? Is there a bug filed against the nVidia drivers for this issue? I _do not_ have the same problem with gnome-screenshot on Ubuntu 12.04.1 LTS (gnome 3.4.2) using the Intel video driver. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696554: System freezes and lockups
Wow, thanks so much for the speedy response! I would really like to stay with gnome-shell on this system if possible. I have been playing HD videos to try to trigger the problem, but I believe it took either hours or days for the crash to occur originally. I will use nouveaux full-time until I run into the issue again and report back right away. Thanks. - Original Message - From: Steven Chamberlain ste...@pyro.eu.org To: Mar Mel marmel6...@yahoo.com; 696...@bugs.debian.org Cc: Sent: Tuesday, December 25, 2012 8:13 PM Subject: Re: Bug#696554: System freezes and lockups Hello, Just an idea of mine, but if this issue only happens after logging in (to gnome-shell?), perhaps you could try installing+logging into the xfce4-desktop? Just to see if that still triggers the nouveau bug. And then if xfce4 is stable, you could perhaps try `mplayer -vo xv somefile.avi` to see if that will trigger the problem instead. Thanks! Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696554: System freezes and lockups
Okay, unfortunately it hasn't taken long to see a problem from nouveaux. While tailing syslog, I just noticed these messages cropping up from a few moments ago: Dec 25 21:14:22 humonculux kernel: [ 3718.821137] [drm] nouveau :01:00.0: PGRAPH - TRAP_TPDMA - TP1: Unhandled ustatus 0x0008 Dec 25 21:14:22 humonculux kernel: [ 3718.821147] [drm] nouveau :01:00.0: PGRAPH - TRAP_TPDMA - TP2: Unhandled ustatus 0x0008 Dec 25 21:14:22 humonculux kernel: [ 3718.821153] [drm] nouveau :01:00.0: PGRAPH - TRAP Dec 25 21:14:22 humonculux kernel: [ 3718.821155] [drm] nouveau :01:00.0: PGRAPH - ch 2 (0x0001256000) subc 7 class 0x8397 mthd 0x15e0 data 0x Dec 25 21:14:22 humonculux kernel: [ 3718.821164] [drm] nouveau :01:00.0: VM: trapped write at 0x004d5d1c00 on ch 2 [0x1256] PGRAPH/PROP/RT0 reason: PAGE_NOT_PRESENT System still hasn't hung or crashed...yet. Any idea what these messages could indicate? - Original Message - From: Steven Chamberlain ste...@pyro.eu.org To: Mar Mel marmel6...@yahoo.com; 696...@bugs.debian.org Cc: Sent: Tuesday, December 25, 2012 8:13 PM Subject: Re: Bug#696554: System freezes and lockups Hello, Just an idea of mine, but if this issue only happens after logging in (to gnome-shell?), perhaps you could try installing+logging into the xfce4-desktop? Just to see if that still triggers the nouveau bug. And then if xfce4 is stable, you could perhaps try `mplayer -vo xv somefile.avi` to see if that will trigger the problem instead. Thanks! Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696554: System freezes and lockups
I have indeed been having similar intermittent freeze issues with the non-free driver and have filed bug #696360. Troubleshooting hardware issues is a routine part of my life in IT and your suggestion regarding heat is the first thing I checked to make sure that the linux driver was not somehow causing my card to overheat. The highest temp I can achive using my current software loadout is 53°C. Under Windows, the card regularly hits 65-70° when stressed. Strangely, I am never doing anything to stress the GPU when these crashes occur. I have no 3D-intensive software installed and the CPU GPU % demands on modern hardware are relatively minimal these days. I can boot into Windows and run FurMark for hours without any issue on this hardware. It's been rock-stable for years under windows (my gaming paritition) and I use MSI Afterburner (formerly RivaTuner) to monitor fan speeds and temp. Here's my current temps: $ sensors coretemp-isa- Adapter: ISA adapter Physical id 0: +34.0°C (high = +80.0°C, crit = +98.0°C) Core 0: +30.0°C (high = +80.0°C, crit = +98.0°C) Core 1: +32.0°C (high = +80.0°C, crit = +98.0°C) Core 2: +32.0°C (high = +80.0°C, crit = +98.0°C) Core 3: +32.0°C (high = +80.0°C, crit = +98.0°C) adt7473-i2c-1-2e Adapter: nouveau-:01:00.0-3 in1: +3.00 V (min = +0.00 V, max = +2.99 V) +3.3V: +3.30 V (min = +0.00 V, max = +4.39 V) fan1: 668 RPM (min = 0 RPM) fan2: 0 RPM (min = 0 RPM) fan3: 0 RPM (min = 164 RPM) ALARM temp1: +36.2°C (low = +65.0°C, high = +85.0°C) ALARM (crit = +97.0°C, hyst = +97.0°C) Board Temp: +34.2°C (low = +20.0°C, high = +60.0°C) (crit = +100.0°C, hyst = +100.0°C) temp3: +36.2°C (low = +80.0°C, high = +105.0°C) ALARM (crit = +107.0°C, hyst = +103.0°C) Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696554: System freezes and lockups
- DATA_ERROR BEGIN_END_ACTIVE Dec 25 22:24:45 humonculux kernel: [ 6341.656145] [drm] nouveau :01:00.0: PGRAPH - DATA_ERROR Dec 25 22:24:45 humonculux kernel: [ 6341.656147] [drm] nouveau :01:00.0: PGRAPH - ch 2 (0x0001256000) subc 7 class 0x8397 mthd 0x134c data 0x8006 Dec 25 22:24:45 humonculux kernel: [ 6341.656154] [drm] nouveau :01:00.0: PGRAPH - DATA_ERROR BEGIN_END_ACTIVE Dec 25 22:24:45 humonculux kernel: [ 6341.656155] [drm] nouveau :01:00.0: PGRAPH - DATA_ERROR Dec 25 22:24:45 humonculux kernel: [ 6341.656156] [drm] nouveau :01:00.0: PGRAPH - ch 2 (0x0001256000) subc 7 class 0x8397 mthd 0x1350 data 0x4001 Dec 25 22:24:45 humonculux kernel: [ 6341.656164] [drm] nouveau :01:00.0: PGRAPH - DATA_ERROR BEGIN_END_ACTIVE Dec 25 22:24:45 humonculux kernel: [ 6341.656165] [drm] nouveau :01:00.0: PGRAPH - DATA_ERROR Dec 25 22:24:45 humonculux kernel: [ 6341.656166] [drm] nouveau :01:00.0: PGRAPH - ch 2 (0x0001256000) subc 7 class 0x8397 mthd 0x1358 data 0x4303 Dec 25 22:29:06 humonculux kernel: [ 6602.329083] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 1 - Unknown fault at address 004f260100 Dec 25 22:29:06 humonculux kernel: [ 6602.329085] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 1 - e0c: , e18: , e1c: 00060500, e20: 2a00, e24: 0003 Dec 25 22:29:06 humonculux kernel: [ 6602.329095] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 2 - Unknown fault at address 004f261000 Dec 25 22:29:06 humonculux kernel: [ 6602.329096] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 2 - e0c: , e18: , e1c: 00020510, e20: 2a00, e24: 0003 Dec 25 22:29:06 humonculux kernel: [ 6602.329105] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 3 - Unknown fault at address 004f262100 Dec 25 22:29:06 humonculux kernel: [ 6602.329106] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 3 - e0c: , e18: , e1c: 00060520, e20: 2a00, e24: 0003 Dec 25 22:29:06 humonculux kernel: [ 6602.329116] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 5 - Unknown fault at address 004f263000 Dec 25 22:29:06 humonculux kernel: [ 6602.329117] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 5 - e0c: , e18: , e1c: 00020530, e20: 2a00, e24: 0003 Dec 25 22:29:06 humonculux kernel: [ 6602.329126] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 6 - Unknown fault at address 004f264000 Dec 25 22:29:06 humonculux kernel: [ 6602.329127] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 6 - e0c: , e18: , e1c: 00020540, e20: 2a00, e24: 0003 Dec 25 22:29:06 humonculux kernel: [ 6602.329136] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 7 - Unknown fault at address 004f265000 Dec 25 22:29:06 humonculux kernel: [ 6602.329138] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 7 - e0c: , e18: , e1c: 00020550, e20: 2a00, e24: 0003 Dec 25 22:29:06 humonculux kernel: [ 6602.329147] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 8 - Unknown fault at address 004f266000 Dec 25 22:29:06 humonculux kernel: [ 6602.329148] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_RT - TP 8 - e0c: , e18: , e1c: 00020562, e20: 2a00, e24: 0003 Dec 25 22:29:06 humonculux kernel: [ 6602.329150] [drm] nouveau :01:00.0: PGRAPH - TRAP Dec 25 22:29:06 humonculux kernel: [ 6602.329152] [drm] nouveau :01:00.0: PGRAPH - ch 2 (0x0001256000) subc 7 class 0x8397 mthd 0x15e0 data 0x Dec 25 22:29:06 humonculux kernel: [ 6602.329161] [drm] nouveau :01:00.0: VM: trapped write at 0x004f260100 on ch 2 [0x1256] PGRAPH/PROP/RT0 reason: PAGE_NOT_PRESENT - Original Message - From: Steven Chamberlain ste...@pyro.eu.org To: Mar Mel marmel6...@yahoo.com Cc: 696...@bugs.debian.org 696...@bugs.debian.org Sent: Tuesday, December 25, 2012 9:34 PM Subject: Re: Bug#696554: System freezes and lockups Hi, I wonder, if these errors only appear after some time - and if you've had problems with the non-free driver too - maybe it has to do with the buildup of heat? Are you able to check temperature sensors on the card? I don't know how to do that for your particular model, but on my card (NV92 / 8800 GT) I can do it like this (as root) : # apt-get install lm-sensors # modprobe adt7473 # modprobe adt7475 # sensors adt7473-i2c-4-2e Adapter: nouveau-:18:00.0-2 in1: +3.00 V (min = +0.00 V, max = +2.99 V) +3.3V: +3.34 V (min = +0.00 V, max = +4.39 V) fan1: 2277 RPM (min = 2000 RPM) fan2: 0 RPM (min = 0 RPM) fan3: 0 RPM (min = 164 RPM) ALARM temp1: +52.5°C (low = +20.0°C, high = +68.0°C) (crit = +100.0°C, hyst = +98.0°C) Board Temp: +48.0°C (low = +20.0°C, high = +60.0°C) (crit = +100.0°C, hyst = +96.0°C) temp3: +52.5°C
Bug#696360: (no subject)
I have upgraded the severity of this issue as it's causing massive system instability and potential data loss. Some further details of the problem: * When the freeze occurs the mouse pointer is still movable. However, the interface is non-responsive. It will accept neither mouse nor keyboard input. * ~50% of the time I am able to switch to a virtual terminal and either restart gnome-shell or at least safely restart the system. I always lose the data I'm working on in this case * When I am unable to switch to a tty, I am forced to REISUB. While this emergency shutdown has been successful in restarting the system without a hard power-off, it has caused my RAID set to go dirty and trigger a rebuild. I've got my main data-store in a truecrypt volume mounted on a RAID-5 set. When my system freezes, the truecrypt volume does not have an opportunity to unmount safely. * I have tested the 304.64-2 driver from unstable and experienced the exact same behavior of freezing. I also built a vanilla 3.4.24 kernel from upstream with only the Wheezy config options and tested this using the Wheezy 304.48-1 driver. The results were the same and I encountered the hard lockup requiring REISUB. Please let me know what other information I can provide to help resolve this issue. Currently this compromises the stability of Wheezy as a platform. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696554: xserver-xorg-video-nouveau: Using the open source nouveaux driver is causing sytem to lockup hard
Package: xserver-xorg-video-nouveau Version: 1:1.0.1-4 Severity: serious Justification: 5 Dear Maintainer, * What led up to the situation? I performed a clean installation of Wheezy Beta 4. * What exactly did you do (or not do) that was effective (or ineffective)? I attempted to use software under gnome-shell * What was the outcome of this action? The system froze and locked up completely requiring REISUB as I could not access a virtual terminal. * What outcome did you expect instead? The system to remain stable. This is what I see in the syslog when the freezes occur: Dec 10 20:10:00 humonculux kernel: [ 587.260611] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x0020026788 Put 0x002002cfb8 IbGet 0x09b7 IbPut 0x09b8 State 0x80004844 (err: INVALID_CMD) Push 0x00502031 Dec 10 20:10:00 humonculux kernel: [ 587.277649] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x002002cff4 Put 0x002002cfb8 IbGet 0x09b7 IbPut 0x09b8 State 0x80004861 (err: INVALID_CMD) Push 0x00400040 Dec 10 20:10:00 humonculux kernel: [ 587.278367] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_2D - TP 1 - Unknown fault at address 00208f6700 Dec 10 20:10:00 humonculux kernel: [ 587.278368] [drm] nouveau :01:00.0: PGRAPH_TRAP_TPDMA_2D - TP 1 - e0c: , e18: , e1c: 001c, e20: 0037, e24: 0c03 Dec 10 20:10:00 humonculux kernel: [ 587.278377] [drm] nouveau :01:00.0: PGRAPH - TRAP Dec 10 20:10:00 humonculux kernel: [ 587.278378] [drm] nouveau :01:00.0: PGRAPH - ch 2 (0x0001256000) subc 2 class 0x502d mthd 0x0860 data 0x00fefefe Dec 10 20:10:00 humonculux kernel: [ 587.278387] [drm] nouveau :01:00.0: VM: trapped write at 0x00208f6700 on ch 2 [0x1256] PGRAPH/PROP/DST2D reason: PAGE_NOT_PRESENT Dec 10 20:13:21 humonculux kernel: [ 788.349804] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x002002d3c4 Put 0x0020031590 IbGet 0x06d0 IbPut 0x06d1 State 0x80004200 (err: INVALID_CMD) Push 0x00702031 Dec 10 20:13:21 humonculux kernel: [ 788.362058] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x0020031590 Put 0x0020031590 IbGet 0x06d0 IbPut 0x06d1 State 0x8000 (err: INVALID_CMD) Push 0x00400040 Dec 10 20:15:37 humonculux kernel: [ 924.315497] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x0020028430 Put 0x0020029918 IbGet 0x0b51 IbPut 0x0b52 State 0x8000 (err: INVALID_CMD) Push 0x00400040 Dec 10 20:15:39 humonculux kernel: [ 926.250959] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x002003ad7c Put 0x002003c844 IbGet 0x001d IbPut 0x001e State 0x8090 (err: INVALID_CMD) Push 0x00400040 Dec 10 20:20:42 humonculux kernel: [ 1229.430850] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x002001d430 Put 0x002002075c IbGet 0x0cdf IbPut 0x0ce0 State 0x8054 (err: INVALID_CMD) Push 0x00400040 Dec 10 20:22:31 humonculux kernel: [ 1338.904516] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x002001f7fc Put 0x0020023048 IbGet 0x0f78 IbPut 0x0f79 State 0x80004200 (err: INVALID_CMD) Push 0x00502031 Dec 10 20:22:31 humonculux kernel: [ 1338.916828] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x0020023048 Put 0x0020023048 IbGet 0x0f78 IbPut 0x0f79 State 0x8000 (err: INVALID_CMD) Push 0x00400040 Dec 10 20:24:06 humonculux kernel: [ 1433.720916] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x002002d39c Put 0x002003177c IbGet 0x0e83 IbPut 0x0e84 State 0x80004200 (err: INVALID_CMD) Push 0x00500031 Dec 10 20:24:06 humonculux kernel: [ 1433.733575] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x002003177c Put 0x002003177c IbGet 0x0e83 IbPut 0x0e84 State 0x8000 (err: INVALID_CMD) Push 0x00400040 Dec 10 20:24:13 humonculux kernel: [ 1440.414855] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x0020025308 Put 0x002002800c IbGet 0x0474 IbPut 0x0475 State 0x80004210 (err: INVALID_CMD) Push 0x00700031 Dec 10 20:24:13 humonculux kernel: [ 1440.427504] [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 Get 0x002002800c Put 0x002002800c IbGet 0x0474 IbPut 0x0475 State 0x8000 (err: INVALID_CMD) Push 0x00400040 -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Dec 4 19:41 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2044664 Nov 29 14:34 /usr/bin/Xorg Diversions concerning libGL are in place diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by glx-diversions diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so to
Bug#696554: Acknowledgement (xserver-xorg-video-nouveau: Using the open source nouveaux driver is causing sytem to lockup hard)
summary 696554 System freezes and lockups -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696360: nvidia-glx: Sporadic X freezes
Package: nvidia-glx Version: 304.48-1 Severity: important I am seeing freezes of X on Wheezy with nVidia driver 304.48. There are several similar reports from the past few months on various distros, but I've not seen one particular to the current Debian Wheezy. Freezing of X can occur within hours of booting the system, or after several days with multiple suspend/resume cycles. The lockups can occur with many applications open or none. At each occurance of the freeze I get one or many of this message in the syslog: kernel: [62905.059965] NVRM: Xid (:01:00): 13, 0003 8397 1530 0001 0040 I've also tested 304.64-2 drivers from unstable, hoping that might be better, but I had freezes/lockups of the same symptoms with that driver as well. -- Package-specific info: uname -a: Linux humonculux 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux /proc/version: Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-12) ) #1 SMP Debian 3.2.32-1 /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.48 Sun Sep 9 20:22:27 PDT 2012 GCC version: gcc version 4.6.3 (Debian 4.6.3-10) lspci 'VGA compatible controller [0300]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT200 [GeForce GTX 260] [10de:05e2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0585] 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 Interrupt: pin A routed to IRQ 16 Region 0: Memory at f600 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at e000 (64-bit, prefetchable) [size=256M] Region 3: Memory at f400 (64-bit, non-prefetchable) [size=32M] Region 5: I/O ports at e000 [size=128] [virtual] Expansion ROM at f700 [disabled] [size=512K] Capabilities: access denied Kernel driver in use: nvidia dmesg: [0.00] No AGP bridge found [0.00] No AGP bridge found [0.00] Console: colour VGA+ 80x25 [0.757519] vgaarb: device added: PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none [0.757521] vgaarb: loaded [0.757522] vgaarb: bridge control possible :01:00.0 [1.092223] Linux agpgart interface v0.103 [3.940664] nvidia: module license 'NVIDIA' taints kernel. [3.998027] nvidia :01:00.0: setting latency timer to 64 [3.998030] vgaarb: device changed decodes: PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem [3.998071] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 304.48 Sun Sep 9 20:22:27 PDT 2012 [6.922079] NVRM: GPU at :01:00: GPU-1b0bf4e5-c0a0-b72e-04cd-d3d55832250b [62905.059965] NVRM: Xid (:01:00): 13, 0003 8397 1530 0001 0040 OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Dec 17 16:05 /etc/alternatives/glx - /usr/lib/nvidia lrwxrwxrwx 1 root root 43 Dec 17 16:05 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Dec 17 16:05 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 51 Dec 17 16:05 /etc/alternatives/glx--libXvMCNVIDIA.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 59 Dec 17 16:05 /etc/alternatives/glx--libXvMCNVIDIA_dynamic.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libXvMCNVIDIA_dynamic.so.1 lrwxrwxrwx 1 root root 51 Dec 17 16:05 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 25 Dec 17 16:05 /etc/alternatives/glx--linux-libglx.so - /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 36 Dec 17 16:05 /etc/alternatives/glx--nvidia-bug-report.sh - /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 29 Dec 17 16:05 /etc/alternatives/glx--nvidia_drv.so - /usr/lib/nvidia/nvidia_drv.so lrwxrwxrwx 1 root root 23 Dec 17 16:05 /etc/alternatives/nvidia - /usr/lib/nvidia/current lrwxrwxrwx 1 root root 51 Dec 17 16:05 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1 lrwxrwxrwx 1 root root 51 Dec 17 16:05 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1 lrwxrwxrwx 1 root root 59 Dec 17 16:05 /etc/alternatives/nvidia--libXvMCNVIDIA.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/current/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 67 Dec 17 16:05 /etc/alternatives/nvidia--libXvMCNVIDIA_dynamic.so.1-x86_64-linux-gnu -
Bug#679105: printing PDF documents from evince is broken with cairo 1.12.2
Printing PDF documents with evince is still broken on Wheezy. This bug was fixed in the 1.12.4 release of cairo. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688860: xserver-xorg-input-evdev: mouse cursor jumping with absolute input device
I hit this bug while testing Wheezy Beta 4. I hope the patch makes in ASAP as this is a showstopper. The gnome desktop is virtually [pun intended] unusable until this is fixed in Debian. Strange to see such a critical bug this late in the freeze for stable. Currently using the workaround from FDO Bug #54353 comment #8 successfully. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
