[Bug 372856] Re: invalid opcode: 0000 [#1] PREEMPT SMP at __find_get_block+0x21/0x1a0
Looks like the same crash that I was getting with that Kernel, so it doesn't seem to be file system specific. I'm still using the stock 2.6.29.4 Kernel that I built with make-kpkg and have not had any crashes. It gets fairly good latency response (only occasional underruns with 5ms latency on my Edirol UA-25 USB audio interface). It would probably improve if I patched the kernel with the low latency patch. I wonder how many other users are getting crashes with 2.6.28-3-rt though. Seems like a pretty critical issue to me. A couple crashes a day, is a couple too many! -- invalid opcode: [#1] PREEMPT SMP at __find_get_block+0x21/0x1a0 https://bugs.launchpad.net/bugs/372856 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366952] Re: Ubuntu 9.04 freezes when using rt kernel
I ended up building my own kernel using make-kpkg and stock Linux 2.6.29.4, with the .config from /boot/config-2.6.28-3-rt. No lockups in several days now, so whatever issue I was having is fixed in at least 2.6.29.4. I have not tested latency with this kernel, so I'm not sure how well it performs in regards to software running RT. -- Ubuntu 9.04 freezes when using rt kernel https://bugs.launchpad.net/bugs/366952 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372856] Re: invalid opcode: 0000 [#1] PREEMPT SMP at __find_get_block+0x21/0x1a0
I ended up building my own kernel using make-kpkg and stock Linux 2.6.29.4, with the .config from /boot/config-2.6.28-3-rt. No lockups in several days now, so whatever issue I was having is fixed in at least 2.6.29.4. I have not tested latency with this kernel, so I'm not sure how well it performs in regards to software running RT. Both the -generic and -rt kernels in Ubuntu 9.04 would frequently lockup my system. -- invalid opcode: [#1] PREEMPT SMP at __find_get_block+0x21/0x1a0 https://bugs.launchpad.net/bugs/372856 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366952] Re: Ubuntu 9.04 freezes when using rt kernel
Ok. So either you are experiencing the same lockup and its not ext4 related or its a different lockup. I haven't gotten a lockup in quite some time now, but I'm not sure if it is fixed or why it would be (perhaps software updates). -- Ubuntu 9.04 freezes when using rt kernel https://bugs.launchpad.net/bugs/366952 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366952] Re: Ubuntu 9.04 freezes when using rt kernel
Edetano: Are you using ext4? It sounds like you might be from your comment on fsck not needing to be used for a long time. -- Ubuntu 9.04 freezes when using rt kernel https://bugs.launchpad.net/bugs/366952 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 39328] Re: Offer option to disable scroll wheel on task list
Wanted to chime in on how annoying this "feature" is. In particular the desktop switch when mouse wheel event occurs on desktop. Whats worse is that certain parts of some GTK interfaces (labels, for example on the nvidia-settings program) and other unexpected parts of some GUIs will also cause this desktop switching behavior, despite the fact the cursor is over the application window (its really bad when its things like the trough near a scroll bar). I've been using Linux for about 12 years now and gnome since early 1.0 releases and its things like this, that make it feel like its progressing backwards in usability, probably an exaggeration, but reflects just how $&*...@ing annoying this is. I think this option should be disabled by default. If some masochistic user wants to enable it, give them a gconf option somewhere, call it something like "/desktop/gnome/really-annoying-desktop-switch-mouse- wheel-hell". -- Offer option to disable scroll wheel on task list https://bugs.launchpad.net/bugs/39328 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366952] Re: Ubuntu 9.04 freezes when using rt kernel
I'm also getting lockups on my Ubuntu Studio 9.04 system. I've tried the -rt kernel, the generic kernel and Daniel T Chen's kernel (see #367671). At first I suspected an issue with PulseAudio running rt SCHED_FIFO and starving the CPU. But now PulseAudio is not running RT on my system and I'm getting complete lockups with generic and Daniel's kernel and with the -rt kernel I get lockups related to the root file system (applications continue to run, but any process attempting to write to the rootfs locks up). I created a bug for this last issue: #372856 Are you using ext4? I suspect that might be the problem with the generic kernels locking up too, but I haven't been able to get a OOPs message from those, due to complete system lockup. -- Ubuntu 9.04 freezes when using rt kernel https://bugs.launchpad.net/bugs/366952 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372858] Re: invalid opcode: 0000 [#1] PREEMPT SMP at __find_get_block+0x21/0x1a0
*** This bug is a duplicate of bug 372856 *** https://bugs.launchpad.net/bugs/372856 Oops, due to launchpad connection issues this bug got added twice. ** This bug has been marked a duplicate of bug 372856 invalid opcode: [#1] PREEMPT SMP at __find_get_block+0x21/0x1a0 -- invalid opcode: [#1] PREEMPT SMP at __find_get_block+0x21/0x1a0 https://bugs.launchpad.net/bugs/372858 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372856] Re: invalid opcode: 0000 [#1] PREEMPT SMP at __find_get_block+0x21/0x1a0
** Attachment added: "Kernel OOPS dump" http://launchpadlibrarian.net/26405864/crash.txt -- invalid opcode: [#1] PREEMPT SMP at __find_get_block+0x21/0x1a0 https://bugs.launchpad.net/bugs/372856 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372858] [NEW] invalid opcode: 0000 [#1] PREEMPT SMP at __find_get_block+0x21/0x1a0
Public bug reported: I'm getting daily crashes on my Ubuntu Studio 9.04 system running the 2.6.28-3-rt. Applications which attempt to write the ext4 root file system lock up and become unresponsive following an oops message like the one attached. I had to save the oops message to a USB memory stick, since attempts to store it to the rootfs would also freeze. The other crashes I have seen have all been at __find_get_block+0x21/0x1a0 within ext4 related operations. ** Affects: linux-rt (Ubuntu) Importance: Undecided Status: New -- invalid opcode: [#1] PREEMPT SMP at __find_get_block+0x21/0x1a0 https://bugs.launchpad.net/bugs/372858 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372856] [NEW] invalid opcode: 0000 [#1] PREEMPT SMP at __find_get_block+0x21/0x1a0
Public bug reported: I'm getting daily crashes on my Ubuntu Studio 9.04 system running the 2.6.28-3-rt. Applications which attempt to write the ext4 root file system lock up and become unresponsive following an oops message like the one attached. I had to save the oops message to a USB memory stick, since attempts to store it to the rootfs would also freeze. The other crashes I have seen have all been at __find_get_block+0x21/0x1a0 within ext4 related operations. ** Affects: linux-rt (Ubuntu) Importance: Undecided Status: New -- invalid opcode: [#1] PREEMPT SMP at __find_get_block+0x21/0x1a0 https://bugs.launchpad.net/bugs/372856 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372858] Re: invalid opcode: 0000 [#1] PREEMPT SMP at __find_get_block+0x21/0x1a0
** Attachment added: "Kernel OOPS dump" http://launchpadlibrarian.net/26405878/crash.txt -- invalid opcode: [#1] PREEMPT SMP at __find_get_block+0x21/0x1a0 https://bugs.launchpad.net/bugs/372858 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367671] Re: PulseAudio gets killed mysteriously
Daniel T Chen: After additional testing I experienced a complete system lockup with the stock Ubuntu 9.04 generic kernel. I suspect it was because I had the PulseAudio option "no-cpu-limit = yes" enabled with SCHED_FIFO RT as well and it got in a loop. So this is starting to sound exactly as you describe. I have been testing your posted kernel for a couple days now and its working great. Sorry for doubting you! ;-) It seems the -rt kernel has some sort of SCHED_FIFO lockup protection though which was killing the PulseAudio task when it got too CPU hungry. I'm curious what particular option this is in the Kernel. At any rate, this bug can probably just be marked as a duplicate and closed. -- PulseAudio gets killed mysteriously https://bugs.launchpad.net/bugs/367671 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367671] Re: PulseAudio gets killed mysteriously
I installed the 2.6.28-11-generic Kernel, rather than the Ubuntu Studio RT Kernel, and so far PulseAudio has been running fine. So I think it is something specific with the RT Kernel. I haven't yet found a concise description of the differences between the two kernel builds though. -- PulseAudio gets killed mysteriously https://bugs.launchpad.net/bugs/367671 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367671] Re: PulseAudio gets killed mysteriously
I'm still unsure why that would cause PulseAudio to get killed though. Is there some sort of RT process killer running on Ubuntu Studio? I should probably try the regular "generic" kernel in addition to yours, since just trying yours would be inconclusive, even if it worked, since I'm running the -rt kernel at the moment. Thanks for the info. -- PulseAudio gets killed mysteriously https://bugs.launchpad.net/bugs/367671 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367671] Re: PulseAudio gets killed mysteriously
** Summary changed: - PulseAudio gets killed by SIGXCPU + PulseAudio gets killed mysteriously ** Description changed: Binary package hint: pulseaudio I'm using Ubuntu Studio 9.04 and have enabled PulseAudio (0.9.14-0ubuntu20) with real time enabled. While playing music I noticed that the audio output would suddenly stop, though Amarok kept on as if everything was fine. I noticed that pulseaudio was no longer running, when running it from the command line I observed again the same behavior and the last output line from PulseAudio was "Killed". By attaching strace with -e trace=signal I found that it would occasionally get a SIGXCPU signal. On the 3rd signal, pulseaudio gets killed, presumably by the Linux kernel. - I resolved this issue on my system by setting "no-cpu-limit = yes" in - the /etc/pulse/daemon.conf file. It seems by default the soft limit of - "Max cpu time" was set to 10ms (as reported from /proc/PID/limits), - which was getting exceeded. Since PulseAudio has been otherwise running - just fine, I think this rlimit setting is too conservative and should - probably be raised (not sure if this is possible via the daemon.conf). - One additional note is that I changed the resample-method to speex- - float-1 from the default of src-linear. + By setting "no-cpu-limit = yes" in the /etc/pulse/daemon.conf file, it + got rid of the SIGXCPU signals, which didn't seem to be the problem, + since it is still getting a SIGKILL signal. One additional note is that + I changed the resample-method to speex-float-1 from the default of src- + linear. I'm not experiencing any perceptible system lockup when this + occurs, so I don't think the RT PulseAudio is taking up extended amounts + of CPU. I'm at a loss as to where the SIGKILL is coming from. -- PulseAudio gets killed mysteriously https://bugs.launchpad.net/bugs/367671 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366708] Re: Pulseaudio dies after a while, usb audio card
I'm experiencing a similar issue and would like to find out if its the same problem. Try running PulseAudio from the command line (after it has crashed or kill it if it is already running), for example: pulseaudio -vv In my case the last line printed before dying is: Killed Which indicates it is receiving a SIGKILL for some reason. -- Pulseaudio dies after a while, usb audio card https://bugs.launchpad.net/bugs/366708 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367671] Re: PulseAudio gets killed by SIGXCPU
I spoke too soon in regards to "no-cpu-limit = yes" fixing the issue. Its not fixed and is still occurring on my system. Its no longer receiving SIGXCPU signals, but it does still get a SIGKILL, the source of which I am still unsure of. Daniel T Chen: How can you be sure its a bi-product of bug #345627 ? The description of that bug sounds nothing like what I am experiencing. The audio output is totally fine on my system (no crackles or pops). Perhaps you posted the wrong bug link? Bug #366708 seems like it could be the same, thought that could just be a PulseAudio crash. In this case, its not crashing, its getting killed. -- PulseAudio gets killed by SIGXCPU https://bugs.launchpad.net/bugs/367671 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367671] Re: PulseAudio gets killed by SIGXCPU
** Attachment added: "daemon.conf" http://launchpadlibrarian.net/26013559/daemon.conf -- PulseAudio gets killed by SIGXCPU https://bugs.launchpad.net/bugs/367671 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367671] [NEW] PulseAudio gets killed by SIGXCPU
Public bug reported: Binary package hint: pulseaudio I'm using Ubuntu Studio 9.04 and have enabled PulseAudio (0.9.14-0ubuntu20) with real time enabled. While playing music I noticed that the audio output would suddenly stop, though Amarok kept on as if everything was fine. I noticed that pulseaudio was no longer running, when running it from the command line I observed again the same behavior and the last output line from PulseAudio was "Killed". By attaching strace with -e trace=signal I found that it would occasionally get a SIGXCPU signal. On the 3rd signal, pulseaudio gets killed, presumably by the Linux kernel. I resolved this issue on my system by setting "no-cpu-limit = yes" in the /etc/pulse/daemon.conf file. It seems by default the soft limit of "Max cpu time" was set to 10ms (as reported from /proc/PID/limits), which was getting exceeded. Since PulseAudio has been otherwise running just fine, I think this rlimit setting is too conservative and should probably be raised (not sure if this is possible via the daemon.conf). One additional note is that I changed the resample-method to speex- float-1 from the default of src-linear. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- PulseAudio gets killed by SIGXCPU https://bugs.launchpad.net/bugs/367671 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190754] Re: Over-optimistic buffering in PulseAudio causes underruns (audible stuttering, pops)
I just upgraded to 2.6.24-18 kernel as well. At first I was using the rt kernel, which did not behave any better in regards to audio drop outs (than previous versions in Hardy). Of note is that I'm NOT using PulseAudio, but just plain ALSA. I then tried the regular 2.6.24-18 kernel and I have yet to been able to get Rhythmbox to drop out. Using a small test application I wrote which does system calls like malloc() and chdir() and times how long they take, I found that running this app as a normal user with the rt kernel can spike up over 400ms for system calls when doing things like minimizing/maximizing windows, whereas the generic 2.6.24-18 kernel max is under 80ms. I believe the default gstreamer buffer size is 300ms. So there still exist some differences between the rt and non-rt 2.6.24-18 Ubuntu kernel which are causing rather significant system call latencies. Of note though, is that SCHED_FIFO audio applications are able to run on my system with the rt kernel at sub 4ms latency, without issues, so the problem is for the SCHED_OTHER normal user case. I was previously using the rt kernel in Gutsy without these issues, so there is likely still something to be fixed in the latest rt kernel. -- Over-optimistic buffering in PulseAudio causes underruns (audible stuttering, pops) https://bugs.launchpad.net/bugs/190754 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190754] Re: Over-optimistic buffering in PulseAudio causes underruns (audible stuttering, pops)
Just a follow up on my previous post concerning stuttering with gstreamer and ALSA. Sorry if its a little off topic (not directly related to PulseAudio). I was able to get gstreamer based applications to not drop out anymore by increasing the buffer size. With gconf-editor add the parameter "buffer-time=40" (for 400ms buffer size) to the audiosink, chataudiosink and musicaudiosink keys in /system/gstreamer/0.10/default. So the key values should look like: alsasink buffer-time=40 The default is 200ms though, which seems like more than enough. This suggests that there is something more sinister going on in regards to latency (as others have suggested). I think the nvidia driver is a good candidate, since it seems like it most often occurs when doing min/maximize of windows and not when other non graphics processes are consuming all of CPU (at least in my case). -- Over-optimistic buffering in PulseAudio causes underruns (audible stuttering, pops) https://bugs.launchpad.net/bugs/190754 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190754] Re: Over-optimistic buffering in PulseAudio causes underruns (audible stuttering, pops)
I'm also experiencing audio stuttering and wanted to contribute my findings. I'm using Ubuntu 8.04 with the rt kernel. First off, I think there are many sources of this problem which all result in audio drop outs, which is likely why this bug has become so confusing. I was also experiencing various issues with PulseAudio, so I have completely disabled it and am now using ALSA dmix. For this reason, I should probably be filing this under another bug, which I will do as I gather more information. In my case, the audio drop out issue does not occur with applications like MPlayer, Amarok and aplay. I also tried VLC, which suffers very slightly from this issue (which I suspect is another issue). Rhythmbox, Totem, and Sound Recorder on the other hand are really bad. Minimizing/maximizing windows causes a rather large audio drop out about 50% of the time. This lead me to believe there is something wrong with gstreamer. So I decided to try gst-launch: gst-launch-0.10 filesrc location=test.mp3 ! mad ! audioconvert ! audioresample ! alsasink Indeed, this gstreamer pipeline has the same audio drop out behavior as all the other applications using gstreamer. I also tested ogg files with a gst-launch pipeline, with the same poor results. So in this case, I think I am experiencing some issue involving gstreamer. I'll be sure to post any more info as I discover it. -- Over-optimistic buffering in PulseAudio causes underruns (audible stuttering, pops) https://bugs.launchpad.net/bugs/190754 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 114930] Re: Python C API version mismatch
I was also having this problem, but I fixed it by adding '--with- python=/usr/bin/python' to the configure flags. Seems both Python 2.4 and 2.5 are installed and it was getting built against 2.4. Here is what I did to build a deb package (if anyone is interested): apt-get source python-clearsilver apt-get build-dep python-clearsilver cd clearsilver-0.10.4 nano -w debian/rules # Add '--with-python=/usr/bin/python \' to the DEB_CONFIGURE_EXTRA_FLAGS, save and exit dpkg-buildpackage -rfakeroot -uc -b cd .. sudo dpkg -i python-clearsilver_0.10.4-1ubuntu1_i386.deb -- Python C API version mismatch https://bugs.launchpad.net/bugs/114930 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
