[Bug 207135] Re: pulseaudio uses too much CPU
My system was doing the same thing. It went from working properly one minute then broken for no reason. Very high CPU usage for pulseaudio, polkitd, dbus-daemon. PulseAudio sound was stuttering. Trying to edit the sound settings in the volume control was impossible because it kept losing the connection to PulseAudio. Syslog was full of thousands of this message repeated: [pulseaudio] alsa-mixer.c: Failed to set switch of IEC958: Operation not permitted I've had issues on this system where the sound output would randomly switch from analog out to some other method or even another device like HDMI which I don't use. I believe due to the plug auto-detection on the audio connector. So I unplugged, replugged, and jiggled the audio connector on the back of the computer and that fixed everything. I guess the plug was loose or the motherboard is buggy and doesn't properly detect when an analog plug is in the audio connector. This was causing pulseaudio to go haywire and hammer the system (not a surprise considering the history of that software). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/207135 Title: pulseaudio uses too much CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/207135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
Seeing a similar issue here with so called "diskless" clients. That is, all of their filesystems are network mounts including the root filesystem. These systems use iscsi targets for the root filesystem and during shutdown the network is turned off before the file I/O operations are completed which causes the system to hang with filesystem IO errors. I'm currently looking to see if there is some way to make systemd keep the network up no matter what, all the way until the machine physically reboots or shuts down (ie. disable the network shutdown completely). This worked in 14.04 and got broken in 16.04 apparently due to the switch to systemd as far as I can tell (great tool, isn't it?). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511855] Re: Some Sony Dualshock 4 controllers do not work in kernel 3.15+
Reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=107081 ** Bug watch added: Linux Kernel Bug Tracker #107081 http://bugzilla.kernel.org/show_bug.cgi?id=107081 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511855 Title: Some Sony Dualshock 4 controllers do not work in kernel 3.15+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511855] [NEW] Some Sony Dualshock 4 controllers do not work in kernel 3.15+
Public bug reported: I'm testing in Ubuntu 15.10 with kernel 4.2.0-16.19 but this bug report actually applies to ALL kernels starting at 3.15 until the current 4.3rc7 and is not limited to Ubuntu. I have a brand new Sony DualShock 4 that seems to use a slightly different protocol than the hid-sony driver expects. I'm not sure why this controller is different. Maybe updated firmware from Sony or maybe because it has never been connected to a PS4. Whatever the case, the device descriptor size is different from what hid-sony expects and because of that it does not remap the descriptor table as required. This causes only the trackpad to function (the trackpad uses a different code path) and none of the other controls work. So basically the controller does not work at all. I have created a patch that fixes it. I have only tested the patch against kernel 4.2 and 4.3 but it's simple enough that it should be trivially portable to any 3.15+ kernel. The attached patch is based against the Ubuntu mainline-crack git v4.2 kernel. I posted to the LKML asking if the descriptor size check was even necessary but never got a response so I left it in. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Patch added: "hid-sony-ds4.patch" https://bugs.launchpad.net/bugs/1511855/+attachment/4509539/+files/hid-sony-ds4.patch ** Package changed: apport (Ubuntu) => linux-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511855 Title: Some Sony Dualshock 4 controllers do not work in kernel 3.15+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511402] Re: Xubuntu not suspending on lid close
I forgot to mention that I do have one 15.10 Xubuntu install on a Dell M731 laptop and the power management on that works fine, including sleep when closing the lid. I'm thinking that there is some package/setting that gets installed that breaks it which is why I mentioned the GNOME power manager being installed on my desktop installs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511402 Title: Xubuntu not suspending on lid close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1511402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511402] Re: Xubuntu not suspending on lid close
I can't say I have the exact same problem because I'm on a desktop machine but I have noticed that the power management in general seems to be broken. For example, in XFCE power manager I have the screen to blank at 15 minutes, sleep at 25, and off at 35. Even after many hours it never even blanks the screen. Fresh clean Xubuntu 15.10 install here. Tried on 3 different desktop machines with various hardware (some UEFI, some old BIOS, some nVidia, some AMD) and the power management doesn't work on any of them. I also notice that for some reason the GNOME power manager is installed. Maybe it was pulled in by some other package? (not sure which but I do not have the gnome or ubuntu desktop installed, only xubuntu). It does not appear to be running though. I have these processes running related to "power": /usr/lib/upower/upowerd xfce4-power-manager --restart --sm-client-id 2f123... /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-1.0 /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libxfce4powermanager.so.. /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service xfce4-power-manager-settings -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511402 Title: Xubuntu not suspending on lid close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1511402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380080] Re: Cannot make directory '/var/run/screen': Permission denied (convert init to upstart)
Same problem here. I have several machines that run "screen -d -m" from an @reboot crontab entry and they all get the error at every boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380080 Title: Cannot make directory '/var/run/screen': Permission denied (convert init to upstart) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1380080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 755148] Re: metacity performance regression in natty/nvidia
This appears to be fixed for me when using the current version of Metacity (2.34). I built the current version of Metacity using the package information here: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/784838 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/755148 Title: metacity performance regression in natty/nvidia -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 755148] Re: metacity performance regression in natty/nvidia
I'm seeing the same problem with NVIDIA hardware and NVIDIA drivers. Even in "Classic No Effects" mode Metacity is causing significant performance problems with OpenGL applications. Confirmed by switching between OpenBox and Metacity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/755148 Title: metacity performance regression in natty/nvidia -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736579] Re: 2nd GPU card temp incorrectly reported in sensors-applet
I briefly looked at the source for this and I think the issue is the use of XNVCTRLQueryTargetAttribute which seems to be broken. The nvidia-settings application uses NvCtrlGetAttribute directly (ie. it doesn't use the X event mechanism) and it works fine. Not sure what the problem is with XNVCTRLQueryTargetAttribute. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736579 Title: 2nd GPU card temp incorrectly reported in sensors-applet -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736579] Re: 2nd GPU card temp incorrectly reported in sensors-applet
I'm seeing this problem too. nvclock and other programs report the temperature of all the GPU's correctly but the sensors applet seems broken. The sensors applet shows zero degrees for the second GPU. GPU0CoreTemp is correct while GPU1CoreTemp is always zero. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736579 Title: 2nd GPU card temp incorrectly reported in sensors-applet -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606491] Re: start: Job is already running: anacron
Had this happen again this morning and I checked to see if apt was stuck. Sure enough: root 947 0.0 0.0 0 0 ?ZN Apr26 0:00 [apt] That process can not be killed either, not even with -9. At least in my case I'm pretty sure this has to do with the automatic updates. For some reason apt gets wedged occasionally. Still running 10.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606491 Title: start: Job is already running: anacron -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606491] Re: start: Job is already running: anacron
Been seeing the same problem in Maverick lately. I believe it may have something to do with automatic upgrades. Do the other people experiencing this issue have automatic updates turned on? When manually running apt-get update/upgrade I have seen it hang indefinitely before possibly due to network issues and this may be what is happening when the system does the automatic updates. Maybe apt needs better network error handling or something (just a guess without actually looking into this problem very closely). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606491 Title: start: Job is already running: anacron -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 246413] Re: kcryptd process doesn't utilize multiple cpus
My CPU is capable of 130MB/sec AES-256. My drives, 119MB/sec write. Combine this into a dm-crypt volume: 11MB/sec (eleven megabytes per second [!]). Uh, this thing seems broken to me. I'm using xfs on dm-crypt. Anyone know if iostat can provide some useful information? I'm wondering about I/O thrashing like we have been seeing with grub and apt lately. Something is/was seriously wrong with those too. -- kcryptd process doesn't utilize multiple cpus https://bugs.launchpad.net/bugs/246413 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 312163] Re: RAID array causing "BUG: soft lockup" errors/system freeze
As far as I can tell this issue is fixed in Jaunty. I have been really hammering the system for several weeks and have not seen the original problem. I believe some of issues posted here lately are not related to the original bug. The stack traces look different. -- RAID array causing "BUG: soft lockup" errors/system freeze https://bugs.launchpad.net/bugs/312163 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 312163] Re: RAID array causing "BUG: soft lockup" errors/system freeze
I spent the last few days testing on Jaunty and it seems to be fixed there. Kernel is 2.6.28-11.42 x86_64. I will have more confidence after a few weeks of testing but I think it looks good so far. -- RAID array causing "BUG: soft lockup" errors/system freeze https://bugs.launchpad.net/bugs/312163 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 362396] [NEW] loop-aes module does not compile
Public bug reported: Binary package hint: loop-aes-source Using module assistant to built loop-aes-source (3.2c) kernel module fails: make[3]: Entering directory `/usr/src/linux-headers-2.6.28-11-generic' CC [M] /usr/src/modules/loop-aes/tmp-d-kbuild/patched-loop.o /usr/src/modules/loop-aes/tmp-d-kbuild/patched-loop.c: In function ‘loop_get_buffer’: /usr/src/modules/loop-aes/tmp-d-kbuild/patched-loop.c:587: error: ‘struct bio’ has no member named ‘bi_hw_front_size’ /usr/src/modules/loop-aes/tmp-d-kbuild/patched-loop.c:597: error: ‘struct bio’ has no member named ‘bi_hw_front_size’ /usr/src/modules/loop-aes/tmp-d-kbuild/patched-loop.c:609: error: ‘struct bio’ has no member named ‘bi_hw_segments’ /usr/src/modules/loop-aes/tmp-d-kbuild/patched-loop.c:612: error: ‘struct bio’ has no member named ‘bi_hw_front_size’ /usr/src/modules/loop-aes/tmp-d-kbuild/patched-loop.c:613: error: ‘struct bio’ has no member named ‘bi_hw_back_size’ /usr/src/modules/loop-aes/tmp-d-kbuild/patched-loop.c: In function ‘loop_make_request_real’: /usr/src/modules/loop-aes/tmp-d-kbuild/patched-loop.c:906: error: ‘struct bio’ has no member named ‘bi_hw_front_size’ /usr/src/modules/loop-aes/tmp-d-kbuild/patched-loop.c:911: error: ‘struct bio’ has no member named ‘bi_hw_front_size’ /usr/src/modules/loop-aes/tmp-d-kbuild/patched-loop.c: At top level: /usr/src/modules/loop-aes/tmp-d-kbuild/patched-loop.c:1994: warning: initialization from incompatible pointer type /usr/src/modules/loop-aes/tmp-d-kbuild/patched-loop.c:1995: warning: initialization from incompatible pointer type /usr/src/modules/loop-aes/tmp-d-kbuild/patched-loop.c:1996: warning: initialization from incompatible pointer type /usr/src/modules/loop-aes/tmp-d-kbuild/patched-loop.c:1998: warning: initialization from incompatible pointer type make[4]: *** [/usr/src/modules/loop-aes/tmp-d-kbuild/patched-loop.o] Error 1 make[3]: *** [_module_/usr/src/modules/loop-aes/tmp-d-kbuild] Error 2 make[3]: Leaving directory `/usr/src/linux-headers-2.6.28-11-generic' make[2]: *** [all] Error 2 make[2]: Leaving directory `/usr/src/modules/loop-aes' make[1]: *** [build-stamp] Error 2 make[1]: Leaving directory `/usr/src/modules/loop-aes' make: *** [kdist_build] Error 2 ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 NonfreeKernelModules: nvidia Package: loop-aes-source 3.2c-2 PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: loop-aes Uname: Linux 2.6.28-11-generic x86_64 ** Affects: loop-aes-source (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- loop-aes module does not compile https://bugs.launchpad.net/bugs/362396 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 362396] Re: loop-aes module does not compile
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/25544324/Dependencies.txt -- loop-aes module does not compile https://bugs.launchpad.net/bugs/362396 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 312163] Re: RAID array causing "BUG: soft lockup" errors/system freeze
The patch that I mentioned above is in the 2.6.28-11 kernel used in Jaunty so it might work also. I'm not sure when I will get a chance to test it though. -- RAID array causing "BUG: soft lockup" errors/system freeze https://bugs.launchpad.net/bugs/312163 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 312163] Re: RAID array causing "BUG: soft lockup" errors/system freeze
I have been running for over a month now on the older Hardy kernel (2.6.24-23-generic x86_64) and have not seen this issue at all. So it appears it's almost definitely something broken in the newer kernels. At this point it's unclear if it is an Ubuntu or Linux kernel problem. With that said, I found this: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=e8c82c2e23e3527e0c9dc195e432c16784d270fa Has anyone tried this simple patch against the Ubuntu kernel? See also: http://oss.sgi.com/bugzilla/show_bug.cgi?id=805 http://lkml.org/lkml/2009/1/5/307 -- RAID array causing "BUG: soft lockup" errors/system freeze https://bugs.launchpad.net/bugs/312163 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 312163] Re: RAID array causing "BUG: soft lockup" errors/system freeze
I'm still testing but I have been using the kernel from 8.04 Hardy 2.6.24-23-generic and problem has not appeared for several days now. I'm still running Intrepid but with the older kernel. If this is true then this bug must have been introduced somewhere between 2.6.24 and 2.6.27 (and as I mentioned 2.6.28 is affected as well). -- RAID array causing "BUG: soft lockup" errors/system freeze https://bugs.launchpad.net/bugs/312163 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 312163] Re: RAID array causing "BUG: soft lockup" errors/system freeze
I built the current Jaunty kernel (2.6.28-4-generic) and tried that but it has the same problem. It seems the error happens much more often when using XFS but I'm not sure if it's related to XFS or not. I have found that doing very long running large SqLite operations is the best way to recreate the error (disk I/O is very high). Sometimes it can take hours of hammering the disks before the error appears (race condition I'm guessing). Often it hard-locks the OS and the RAID arrays have to be resynced (which takes several hours) after reset/reboot. -- RAID array causing "BUG: soft lockup" errors/system freeze https://bugs.launchpad.net/bugs/312163 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 312163] Re: RAID array causing "BUG: soft lockup" errors/system freeze
After more testing I have modified the original description because originally I was thinking it just affected XFS but now I don't think that is the case. I just got another crash when using Ext3 so now I'm not sure where the problem might be. It still looks like it probably has something to do with the filesystem layers though. In this latest case all I did was start a 'grep' on a file and the CPU went to 100% and the process froze completely (could not be killed even with kill -KILL). A few seconds later I started getting the "BUG: soft lockup" errors. I have attached the latest error. ** Summary changed: - XFS on RAID array causing "BUG: soft lockup" errors/system freeze + RAID array causing "BUG: soft lockup" errors/system freeze ** Description changed: Running Ubuntu 8.10 Intrepid Desktop 64-bit with all current updates. Kernel is 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 GNU/Linux. System is Abit IP35-Pro motherboard, Q9550 CPU, 8 GB RAM, 4 Western Digital WD6401AALS-00L3B2 drives (640 GB, SATA). - MemTest and drive tests returns no errors. Using a RAID5 array across the 4 drives with XFS as the file system. + MemTest and drive tests returns no errors. Using a RAID5 array across the 4 drives with XFS and Ext3 as the file systems. It seems when the system gets under heavy I/O load on the RAID array it will eventually freeze (requiring a hard reboot). The errors are inconsistent in how long they take to show up and the specific applications causing the I/O load don't seem to matter but the error always shows up eventually. It has already happened dozens of times after I start a load on the machine. Examples of scenarios where the bug has appeared: * Running Bonnie++ benchmarks. I have seen this kill the system within 30 seconds. Other times it causes no problems. * Running a large SQlite import while simultaneously tar/gzip'ing a large directory structure. * Running a large MySql import while tar/gzip'ing a large directory structure. * Multiple tar/gzip processes running at the same time. The specific process that gets the "CPU: soft lockup" error varies. I have seen it lockup in kswapd, pdflush, gzip, sqlite3, bonnie++ (see attached logs). - The error appears to be related to XFS because all the stack traces have - XFS calls in them. I have attached some of my stack traces. They - repeat many times and I have only included the first distinct events - before my system crashed. + I have attached some of my stack traces. They repeat many times and I + have only included the first distinct events before my system crashed. ** Attachment added: "lockups2.txt" http://launchpadlibrarian.net/20864107/lockups2.txt -- RAID array causing "BUG: soft lockup" errors/system freeze https://bugs.launchpad.net/bugs/312163 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 312163] Re: XFS on RAID array causing "BUG: soft lockup" errors/system freeze
I meant to note that the RAID5 array is a software RAID array created with: mdadm --create /dev/md1 --chunk=256 --level=5 --raid-devices=4 /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sde2 This same system was running XFS on a single drive without problems so it may be some sort of RAID/XFS interaction or bandwidth issue as the performance is much higher than previously. -- XFS on RAID array causing "BUG: soft lockup" errors/system freeze https://bugs.launchpad.net/bugs/312163 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 312163] Re: XFS on RAID array causing "BUG: soft lockup" errors/system freeze
** Attachment added: "lockups.txt" http://launchpadlibrarian.net/20795616/lockups.txt -- XFS on RAID array causing "BUG: soft lockup" errors/system freeze https://bugs.launchpad.net/bugs/312163 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 312163] [NEW] XFS on RAID array causing "BUG: soft lockup" errors/system freeze
Public bug reported: Running Ubuntu 8.10 Intrepid Desktop 64-bit with all current updates. Kernel is 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 GNU/Linux. System is Abit IP35-Pro motherboard, Q9550 CPU, 8 GB RAM, 4 Western Digital WD6401AALS-00L3B2 drives (640 GB, SATA). MemTest and drive tests returns no errors. Using a RAID5 array across the 4 drives with XFS as the file system. It seems when the system gets under heavy I/O load on the RAID array it will eventually freeze (requiring a hard reboot). The errors are inconsistent in how long they take to show up and the specific applications causing the I/O load don't seem to matter but the error always shows up eventually. It has already happened dozens of times after I start a load on the machine. Examples of scenarios where the bug has appeared: * Running Bonnie++ benchmarks. I have seen this kill the system within 30 seconds. Other times it causes no problems. * Running a large SQlite import while simultaneously tar/gzip'ing a large directory structure. * Running a large MySql import while tar/gzip'ing a large directory structure. * Multiple tar/gzip processes running at the same time. The specific process that gets the "CPU: soft lockup" error varies. I have seen it lockup in kswapd, pdflush, gzip, sqlite3, bonnie++ (see attached logs). The error appears to be related to XFS because all the stack traces have XFS calls in them. I have attached some of my stack traces. They repeat many times and I have only included the first distinct events before my system crashed. ** Affects: ubuntu Importance: Undecided Status: New -- XFS on RAID array causing "BUG: soft lockup" errors/system freeze https://bugs.launchpad.net/bugs/312163 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
