similar to: [Bug 105722] New: Nouveau driver hangs when closing video playback

I want to build a dedicated MythTV box using CentOS5. I need a lightweight desktop environment, something extremely simple that does not use much memory. Gnome and KDE use way too much memory and are too complex for what I want to do. The system will login automatically to a certain account after booting up. After the automatic login, it will start immediately the MythTV frontend full-screen.

Caught a message in /var/log/messages about the time Nouveau went out to lunch: Oct 22 19:40:12 one kernel: [drm] nouveau 0000:06:00.0: EvoCh 0 Mthd 0x0000 Data 0x00000400 (0x1002 0x01) This was with kernel 2.6.38.8-server-10.mga on Mageia 1, and I don't see any other version number in modinfo output. The graphics card is an Asus ENGT430. Motherboard is an Asus P6T6 WS Revolution. CPU is

In 1.0.8 I am able to nest describe blocks, but in moving to trunk, revision 2971, I am unable to have the expected results. Here is an example nested describe block: describe "foo" do describe "with no arguments" do before do puts "a" end it "should" do puts "SHOULD" end end describe "with invalid

https://bugzilla.mindrot.org/show_bug.cgi?id=2971 Bug ID: 2971 Summary: Prevent OpenSSH from advertising its version number Product: Portable OpenSSH Version: 7.6p1 Hardware: All OS: Linux Status: NEW Severity: security Priority: P5 Component: sshd Assignee: unassigned-bugs at

https://bugzilla.mindrot.org/show_bug.cgi?id=2971 Bug ID: 2971 Summary: Prevent OpenSSH from advertising its version number Product: Portable OpenSSH Version: 7.6p1 Hardware: All OS: Linux Status: NEW Severity: security Priority: P5 Component: sshd Assignee: unassigned-bugs at

https://bugs.freedesktop.org/show_bug.cgi?id=93828 Bug ID: 93828 Summary: Xorg hangs randomly with nouveau driver Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: Driver/nouveau Assignee:

Hi, I would like to use a digum card to call an external number through my PSTN. I think that I have a problem in the configuration. Asterisk returns me app_dial.c:764 dial_exec: Unable to create channel of type 'Zap' I use Fedora core 3. I installed libpri, zaptel and asterisk. I plugged my line on the FXS module (green part). I make modprobe zaptel && modprobe wctdm without

An update - I ran a test by unplugging my UPS and letting it run down. The system shut down as it should. However, the /etc/killpower file was not created, and the UPS did not shut off power as it should from the shutdown scripts. This may be because the command to kill the output of the UPS isn't available, or that by not being able to log in as master prevents this. The permissions on the

https://bugs.freedesktop.org/show_bug.cgi?id=92971 --- Comment #4 from Ilia Mirkin <imirkin at alum.mit.edu> --- Nov 14 19:06:12 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: PBDMA0: 80000000 [] ch 30 [007e6ab000 kscreenlocker_g[4257]] subc 6 mthd 2878 data a0c02020 A few things wrong with this picture... first off, nouveau never uses subchannel 6. Method 2878 is: lookup -a c8 -d SUBCHAN --

https://bugs.freedesktop.org/show_bug.cgi?id=94367 --- Comment #3 from Riku Voipio <riku.voipio at iki.fi> --- I have similar corruption on GK107, and also in the closed: https://bugs.freedesktop.org/show_bug.cgi?id=98266 Debian stretch up date Kernel: 4.9.0-1 xserver: 1.19.0-3 nouveau: 1.0.13-1 Nothing else seems common with the other reporters but the use of modeset and kde5. -- You

https://bugs.freedesktop.org/show_bug.cgi?id=47306 Bug #: 47306 Summary: segfault in nouveau_fence_update Classification: Unclassified Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: blocker Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=92971 --- Comment #7 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to Philippe Condé from comment #6) > Hello, > > I tested with the non Xen kernel vmlinux-4.3.0-1-default. > The crash exists also with this kernel > > here the journalctl output with a crash when loading a page in the browser: > The screen was

I had a rather large ext4 partition on an Areca RAID shut down uncleanly while it was writing. When I mount it again, it recommends fsck, which I do, and I get the following error: Failed to optimize directory ... EXT2 directory corrupted This error shows up every time I run fsck.ext4 on this partition. How can I fix this? The file system seems to work ok otherwise, I can mount it and it

I have a mixture of Win95 and Win98 computers. From the Samba host I mount the Win95/98 host using a script containing commands similar to the following text. mount -t smbfs //pent14/pent14-e /dosworld/pent14/e -o username=fred\%xxxxxxx After I have mounted all the drives I issue the following command. df -h Results show the available space on the Win98 hosts properly, however all the

https://bugs.freedesktop.org/show_bug.cgi?id=92971 --- Comment #5 from Philippe Condé <conde.philippe at skynet.be> --- hello, it is kde5 (KF5). With opensuse Tumbleweed we do a global update (snapshot). Difficult to see thereafter if this is due to KDE or the kernel. Three examples from journalctl: the very first error after the boot message: the lock occurred during reactivation of

I know some of this doesn't belong on this list, but I am just including it for problem history. I am trying to setup IMAP Voicemail with our email server. We are using a non-standards based groupware server called FirstClass. The server has some built in support for IMAP. My problem seems to be that the authuser flag is not supported. When I use mtest in the imap toolkit to connect to

Hello, today I noticed the following on *only* one node: ----- cut here ----- Apr 29 11:01:18 node06 kernel: [2569440.616036] INFO: task ocfs2_wq:5214 blocked for more than 120 seconds. Apr 29 11:01:18 node06 kernel: [2569440.616056] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 29 11:01:18 node06 kernel: [2569440.616080] ocfs2_wq D

An embedded message was scrubbed... From: "niupei" <niupei at web.de> Subject: 16 bit processor Date: Thu, 28 Jul 2005 22:57:14 +0200 Size: 2971 URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050728/6e61c5f8/attachment.mht>

I'm having an occasional problem with a box. It's a Supermicro 16-core Xeon, running CentOS 6.3 with kernel 2.6.32-279.el6.x86_64, 96 gigs of RAM, and an Areca 1882ix-24 RAID controller with 24 disks, 23 in RAID6 plus a hot spare. The RAID is divided into 3 partitions, two of 25 TB plus one for the rest. Lately, I've noticed sporadic hangs on writing to the RAID, which

I'm on Fedora 6.3. After a reboot, some proprietary software didn't want to run. I found out that the startup script for said software manually sets DISPLAY to :0.0, which I know is not a good idea, and I can fix. However, this still doesn't explain why my default X DISPLAY is suddenly :3.0. -- Joakim Ziegler - Supervisor de postproducci?n - Terminal joakim at terminalmx.com