[Bug 1865347] [NEW] Wifi Adapter not working. Touchpad not working.
Public bug reported: Release -> 18.04 LTS Laptop Model -> Lenovo Ideapad S145 My wifi device is not detected.( Says Wifi Adapter not found). Touchpad is not working. Everything else is fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-28-generic 5.3.0-28.30~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 19:53:23 2020 InstallationDate: Installed on 2020-03-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865347 Title: Wifi Adapter not working. Touchpad not working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1865347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849669] Re: do-release-upgrade (19.04 -> 19.10) aborts
apport-collect 1849669 says the below... "You are not the reported or subscriber of this problem report, or the report is a duplicate or already closed. Please create a new report using apport-bug" ** Attachment added: "Screenshot from 2019-11-01 07-26-19.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1849669/+attachment/5301910/+files/Screenshot%20from%202019-11-01%2007-26-19.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849669 Title: do-release-upgrade (19.04 -> 19.10) aborts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1849669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849669] Re: do-release-upgrade (19.04 -> 19.10) aborts
i some how upgraded with reinstalling all *ubuntu-desktop versions and reinstalling gdm3/lightdm/python3 etc.. which one exactly worked.. i did't know.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849669 Title: do-release-upgrade (19.04 -> 19.10) aborts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1849669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849669] Re: do-release-upgrade (19.04 -> 19.10) aborts
distro-info: Installed: 0.21ubuntu2 Candidate: 0.21ubuntu2 Version table: *** 0.21ubuntu2 500 500 http://in.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status This is what i got -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849669 Title: do-release-upgrade (19.04 -> 19.10) aborts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1849669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849669] Re: do-release-upgrade (19.04 -> 19.10) aborts
Yes. I have exact same bug. Still unable to upgrade :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849669 Title: do-release-upgrade (19.04 -> 19.10) aborts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1849669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848829] Re: upgrade from 19.04 to 19.10 fails
2019-10-19 13:05:38,522 INFO Using config files '['./DistUpgrade.cfg']' 2019-10-19 13:05:38,522 INFO uname information: 'Linux DreamServer 5.0.0-32-generic #34-Ubuntu SMP Wed Oct 2 02:06:48 UTC 2019 x86_64' 2019-10-19 13:05:38,912 INFO apt version: '1.8.3' 2019-10-19 13:05:38,912 INFO python version: '3.7.3 (default, Oct 7 2019, 12:56:13) [GCC 8.3.0]' 2019-10-19 13:05:38,916 INFO release-upgrader version '19.10.12' started 2019-10-19 13:05:38,924 INFO locale: 'en_US' 'UTF-8' 2019-10-19 13:05:38,969 INFO screen could not be run 2019-10-19 13:05:39,003 DEBUG Using 'DistUpgradeViewText' view 2019-10-19 13:05:39,042 DEBUG enable dpkg --force-overwrite 2019-10-19 13:05:39,084 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' 2019-10-19 13:05:43,722 DEBUG lsb-release: 'disco' 2019-10-19 13:05:43,723 DEBUG _pythonSymlinkCheck run 2019-10-19 13:05:43,724 DEBUG openCache() 2019-10-19 13:05:43,724 DEBUG quirks: running PreCacheOpen 2019-10-19 13:05:43,724 DEBUG running Quirks.PreCacheOpen 2019-10-19 13:05:44,336 DEBUG /openCache(), new cache size 95561 2019-10-19 13:05:44,336 DEBUG need_server_mode(): run in 'desktop' mode, (because of pkg 'ubuntu-desktop') 2019-10-19 13:05:44,336 DEBUG checkViewDepends() 2019-10-19 13:05:44,337 DEBUG running doUpdate() (showErrors=False) 2019-10-19 13:05:46,638 DEBUG openCache() 2019-10-19 13:05:47,275 DEBUG /openCache(), new cache size 95561 2019-10-19 13:05:47,275 DEBUG doPostInitialUpdate 2019-10-19 13:05:47,275 DEBUG quirks: running eoanPostInitialUpdate 2019-10-19 13:05:47,275 DEBUG running Quirks.eoanPostInitialUpdate 2019-10-19 13:05:52,295 DEBUG abort called 2019-10-19 13:05:52,295 DEBUG openCache() 2019-10-19 13:05:52,950 DEBUG /openCache(), new cache size 95561 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848829 Title: upgrade from 19.04 to 19.10 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848829] Re: upgrade from 19.04 to 19.10 fails
Upgrade from 19.04 to 19.10 failed for me Fetched 586 B in 0s (0 B/s) Reading package lists... Done Building dependency tree Reading state information... Done Restoring original system state Aborting Reading package lists... Done Building dependency tree Reading state information... Done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848829 Title: upgrade from 19.04 to 19.10 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)
Update: After upgrading to 17.04 (i.e. kernel 4.10*), I no longer have this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1173915] Re: initctl continuously takes 100% of CPU
Just upgraded to 17.04 and this appears to be fixed i.e. I don't see the stupid 'initctl' running anymore! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1173915 Title: initctl continuously takes 100% of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1173915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1173915] Re: initctl continuously takes 100% of CPU
Any update on a fix to this problem? My work around is to kill the initctl if/when I restart; I haven't noticed any adverse effect on anything I do on a daily basis and it is running more than 2+ weeks with no sign of initctl going crazy. Since I very rarely reboot (only after any updates and such), it is not a big deal for me now but would be nice to get a fix to this problem. Not sure the following info helps but I am sure it will give some clue. I attached gdb and dumped the stack trace after a fresh reboot (i.e. when initctl is fine) as well as the same when it goes crazy to compare. Here are the two traces. stack trace normal (siting in poll() normally) == (gdb) where #0 0x7f00ff2ba0a0 in __poll_nocancel () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f00ff5ae78f in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7f00ff5ad3fe in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7f00ff596164 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7f00ff596c5c in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x559a959932c9 in ?? () #6 0x7f00ff9e9ef0 in ?? () from /lib/x86_64-linux-gnu/libnih.so.1 #7 0x7f00ff9ea513 in nih_command_parser () from /lib/x86_64-linux-gnu/libnih.so.1 #8 0x559a95990699 in ?? () #9 0x7f00ff1de3f1 in __libc_start_main (main=0x559a95990620, argc=3, argv=0x7fff0ace82d8, init=, fini=, rtld_fini=, stack_end=0x7fff0ace82c8) at ../csu/libc-start.c:291 #10 0x559a959906ea in ?? () stack trace w/ problem (appear to read something from FD 3 (a unix socket to upstart?) == (gdb) where #0 0x7f7750af142d in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #1 0x7f7750af5f41 in dbus_message_get_reply_serial () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7f7750aeb146 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7f7750aebc5c in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x557f7db2d2c9 in ?? () #5 0x7f7750f3eef0 in ?? () from /lib/x86_64-linux-gnu/libnih.so.1 #6 0x7f7750f3f513 in nih_command_parser () from /lib/x86_64-linux-gnu/libnih.so.1 #7 0x557f7db2a699 in ?? () #8 0x7f77507333f1 in __libc_start_main (main=0x557f7db2a620, argc=3, argv=0x7fff51adf6d8, init=, fini=, rtld_fini=, stack_end=0x7fff51adf6c8) at ../csu/libc-start.c:291 #9 0x557f7db2a6ea in ?? () -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1173915 Title: initctl continuously takes 100% of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1173915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)
Before trying the upstream kernel, I tried to replicate the issue. After noticing it was happening every time there are heavy file I/O. I was able to easily reproduce it at will by running apps that do lot of file I/O. I was also monitoring free memory every second to understand why kernel is invoking oom-killer to randomly killing applications. When oom-killer started to kill random applications, the memory looked like this. Every 1.0s: free -h gorilla: Sat Jan 14 09:52:01 2017 totalusedfree shared buff/cache available Mem: 5.9G755M127M 17M5.1G4.6G Swap: 2.0G 0B2.0G As you can see, there are lot of available memory (mostly in cache and I am very sure most of it are clean cache) but for some reason, it was not reclaimed by kernel (kswapd0?). So I decided to run "echo 3 > /proc/sys/vm/drop_caches" frequently to force dropping cache, and sure enough everything worked fine. Right now, I haven't seen this problem in the last 2+ days. root@gorilla:~# cat /var/log/syslog|egrep "NMI watchdog: BUG: soft lockup|oom-killer" root@gorilla:~# uptime 07:37:29 up 2 days, 19:34, 1 user, load average: 1.63, 0.77, 0.29 Now that I suspect this may be a possible bug in kswapd0, I did a search here for similar issues for kswapd0 and found one (see below) but I am not sure it is the same problem though the symptoms and workaround are same. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457 At the end of this report (comment #142) says, they have no problem in 4.4.0-45 kernel but Yakkety based 4.8+ kernel has this problem. Assuming this is the same issue, I can confirm the same as I have never had this problem before upgrading to Yakkety. I am wondering if the bug made its way back since this fix. Since I have a workaround, I am going to continue with it; it is not ideal but seem to hold it. The last note on the above report says the bug is fixed and any new problem should be opened as a new bug. Can this report be treated as new bug to address this problem? Thanks ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)
@jsalisbury, Thank you for the suggestions. I don't have the xenial kernel handy as I have the habit of running apt-get autoremove after upgrades. However, I will try the latest upstream kernel over this weekend and report the results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)
Kernel update to 4.8.0-34 did not make any difference. Help please. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)
Yesterday, I disabled NMI watch (a workaround discussed in another similar bug report) but it still crashed this morning. root@gorilla:~# sysctl -a|grep kernel.nmi_watchdog kernel.nmi_watchdog = 0 Today, I upgraded to 4.8.0-34 from 4.8.0-32 kernel to see if that makes any difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1655356/+attachment/4802627/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1655356/+attachment/4802623/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1655356/+attachment/4802624/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1655356/+attachment/4802626/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1655356/+attachment/4802622/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1655356/+attachment/4802625/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1655356/+attachment/4802619/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1655356/+attachment/4802620/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)
apport information ** Tags added: apport-collected ** Description changed: I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this problem started with errors, OOM and an eventual kernel panic. It can run fine for about 3-4 hours or so. I see the following errors on syslog (also attached w/ other logs and information I can gather). Jan 9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [kswapd0:50] Jan 9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [kswapd0:50] Jan 9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [kswapd0:50] Jan 9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kswapd0:50] Jan 9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kswapd0:50] Jan 8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0 Jan 9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0 Jan 9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long (2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 Jan 8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long (3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500 Jan 8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long (3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5 Jan 8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long (4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4 Jan 8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long (2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 Jan 8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long (3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500 Jan 9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long (3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500 Jan 9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long (4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500 Jan 9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long (6170 > 6165), lowering kernel.perf_event_max_sample_rate to 32250 Jan 9 07:36:53 gorilla kernel: [69325.386696] perf: interrupt took too long (7723 > 7712), lowering kernel.perf_event_max_sample_rate to 25750 Just to make sure if this is not memory related, I ran memtest for 12 passes over night and found no errors on memory. Removed the external backup drives to isolate the problem. Checked similar issues on lanchpad.net but most of them are related to video driver and power supply. Appreciate help. T
[Bug 1655356] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1655356/+attachment/4802621/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1655356/+attachment/4802618/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)
Attached files.tar containing cpuinfo.txt df.txt dmesg.txt initctl.txt lspci.txt lsusb.txt meminfo.txt swaps.txt uname.txt ** Attachment added: "files.tar" https://bugs.launchpad.net/ubuntu/+bug/1655356/+attachment/4802359/+files/files.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1655356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655356] [NEW] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)
Public bug reported: I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this problem started with errors, OOM and an eventual kernel panic. It can run fine for about 3-4 hours or so. I see the following errors on syslog (also attached w/ other logs and information I can gather). Jan 9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [kswapd0:50] Jan 9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [kswapd0:50] Jan 9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [kswapd0:50] Jan 9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kswapd0:50] Jan 9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kswapd0:50] Jan 8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0 Jan 9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0 Jan 9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long (2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 Jan 8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long (3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500 Jan 8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long (3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5 Jan 8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long (4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4 Jan 8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long (2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 Jan 8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long (3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500 Jan 9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long (3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500 Jan 9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long (4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500 Jan 9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long (6170 > 6165), lowering kernel.perf_event_max_sample_rate to 32250 Jan 9 07:36:53 gorilla kernel: [69325.386696] perf: interrupt took too long (7723 > 7712), lowering kernel.perf_event_max_sample_rate to 25750 Just to make sure if this is not memory related, I ran memtest for 12 passes over night and found no errors on memory. Removed the external backup drives to isolate the problem. Checked similar issues on lanchpad.net but most of them are related to video driver and power supply. Appreciate help. Thanks -Arul Attachments: syslog uname.txt swaps.txt dmesg.txt df.txt lspci.txt lsusb.txt meminfo.txt cpuinfo.txt ** Affects: ubu
[Bug 1173915] Re: initctl continuously takes 100% of CPU
Anyone found a fix or workaround for this problem? I have the same w/ Ubuntu 16.10 /sbin/initctl emit indicator-services-start The initctl spinning out of control. This was NOT the case with the previous version 16.04 and it only started to happen with 16.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1173915 Title: initctl continuously takes 100% of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1173915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251588] Re: ubuntu-release-upgrader crashed in save() with UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 103: ordinal not in range(128)
The same issue affects when i tried to upgrade to 16.04 from 15.10 UbuntuGnome -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251588 Title: ubuntu-release-upgrader crashed in save() with UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 103: ordinal not in range(128) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1251588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278280] Re: ubuntu-release-upgrader crashes with DistUpgrade/sourceslist.py", line 416, in save : UnicodeEncodeError: 'ascii' codec can't encode characters in position 97-114: ordinal not in ran
*** This bug is a duplicate of bug 1251588 *** https://bugs.launchpad.net/bugs/1251588 I have the same issue when i try to upgrade to 16.04 from 15.10 of UbuntuGNome -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278280 Title: ubuntu-release-upgrader crashes with DistUpgrade/sourceslist.py", line 416, in save : UnicodeEncodeError: 'ascii' codec can't encode characters in position 97-114: ordinal not in range(128) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1278280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309651] Re: MiniDLNA missing from Ubuntu 14.10
@Rory, are you sure minidlna is now available in Trusty? or you installed it from ppa:djart/minidlna ? Here is how mine looks... root@gorilla:~# apt-cache show minidlna N: Unable to locate package minidlna E: No packages found root@gorilla:~# apt-get install minidlna Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package minidlna -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309651 Title: MiniDLNA missing from Ubuntu 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/minidlna/+bug/1309651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1330123] Re: grive needs relink
I tried re-authorizing with 'grive -a' but the error is still not going away However, sync appear to be working just fine. Wonder what is 're-linking' mean -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1330123 Title: grive needs relink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grive/+bug/1330123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251939] Re: Chroot fails with Cannot chroot when not started as root error
I can confirm that Chroot is working in the proposed (2.4.6-2ubuntu2.1 ) Thank you for the fix. -Arul -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with Cannot chroot when not started as root error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1251939] Re: Chroot fails with Cannot chroot when not started as root error
I can confirm that Chroot is working in the proposed (2.4.6-2ubuntu2.1 ) Thank you for the fix. -Arul -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with Cannot chroot when not started as root error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251939] Re: Chroot fails with Cannot chroot when not started as root error
Any update on when can we get a fix for this? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with Cannot chroot when not started as root error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1251939] Re: Chroot fails with Cannot chroot when not started as root error
Any update on when can we get a fix for this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with Cannot chroot when not started as root error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251939] Re: Chroot fails with Cannot chroot when not started as root error
Thank you for reviewing this bug report and assigning the severity. While I agree with you on the assigned severity of Medium, I'd like to point out that though ChrootDir is not a default option, it relates to the security of apache server. I am not sure how many users simply use the server w/ default options, but I would guess many will do server hardening starting with chrooting. Would really appreciate if this fix is included soon. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with Cannot chroot when not started as root error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1251939] Re: Chroot fails with Cannot chroot when not started as root error
Thank you for reviewing this bug report and assigning the severity. While I agree with you on the assigned severity of Medium, I'd like to point out that though ChrootDir is not a default option, it relates to the security of apache server. I am not sure how many users simply use the server w/ default options, but I would guess many will do server hardening starting with chrooting. Would really appreciate if this fix is included soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with Cannot chroot when not started as root error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881164] Re: massive syslog entries (GHES: Failed ...) after upgrade to oneiric
** Changed in: ubuntu Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881164 Title: massive syslog entries (GHES: Failed ...) after upgrade to oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/881164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251939] [NEW] Chroot fails with Cannot chroot when not started as root error
Public bug reported: I have set my chroot directory as shown below. ChrootDir /var/www When started with the above chroot setting, apache2 exits with the following error [Sat Nov 16 13:52:40.621872 2013] [unixd:alert] [pid 3747] (34)Numerical result out of range: AH02158: Cannot chroot when not started as root NOTE: apache2 is started as 'root' user. This was reported as a bug in apache.org earlier (link below) where it was confirmed this is fixed in a trunk. https://issues.apache.org/bugzilla/show_bug.cgi?id=55787 Details of my Ubuntu server: - root@gorilla:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=13.10 DISTRIB_CODENAME=saucy DISTRIB_DESCRIPTION=Ubuntu 13.10 root@gorilla:~# apache2ctl -v Server version: Apache/2.4.6 (Ubuntu) Server built: Aug 9 2013 14:31:04 root@gorilla:~# apache2ctl -l -M Compiled in modules: core.c mod_so.c mod_watchdog.c http_core.c mod_log_config.c mod_logio.c mod_version.c mod_unixd.c mod_unixd.c ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: apache2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with Cannot chroot when not started as root error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1251939/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1251939] [NEW] Chroot fails with Cannot chroot when not started as root error
Public bug reported: I have set my chroot directory as shown below. ChrootDir /var/www When started with the above chroot setting, apache2 exits with the following error [Sat Nov 16 13:52:40.621872 2013] [unixd:alert] [pid 3747] (34)Numerical result out of range: AH02158: Cannot chroot when not started as root NOTE: apache2 is started as 'root' user. This was reported as a bug in apache.org earlier (link below) where it was confirmed this is fixed in a trunk. https://issues.apache.org/bugzilla/show_bug.cgi?id=55787 Details of my Ubuntu server: - root@gorilla:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=13.10 DISTRIB_CODENAME=saucy DISTRIB_DESCRIPTION=Ubuntu 13.10 root@gorilla:~# apache2ctl -v Server version: Apache/2.4.6 (Ubuntu) Server built: Aug 9 2013 14:31:04 root@gorilla:~# apache2ctl -l -M Compiled in modules: core.c mod_so.c mod_watchdog.c http_core.c mod_log_config.c mod_logio.c mod_version.c mod_unixd.c mod_unixd.c ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: apache2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with Cannot chroot when not started as root error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1251939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881164] Re: massive syslog entries (GHES: Failed ...) after upgrade to oneiric
Finally, this problem is fixed in quantal (Ubuntu 12.10) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881164 Title: massive syslog entries (GHES: Failed ...) after upgrade to oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/881164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1035932] Re: Chromium crashes very often on Ubuntu 12.04 with SIGSEGV in ??()
I moved to quantal (Ubuntu 12.10) and the problem is gone. Looks like it is fixed in the chromium version i.e. Version 22.0.1229.94 Ubuntu 12.10 (161065) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1035932 Title: Chromium crashes very often on Ubuntu 12.04 with SIGSEGV in ??() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1035932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1035932] Re: Chromium crashes very often on Ubuntu 12.04 with SIGSEGV in ??()
Same problem with my Ubuntu 12.04 as well. i.e. Chromium crashes very frequently. This is 'confirmed' as a bug back in Aug but no solution so far! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1035932 Title: Chromium crashes very often on Ubuntu 12.04 with SIGSEGV in ??() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1035932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019507] [NEW] Update manager issue
Public bug reported: Please help me on this. I cant update anything. It is showing the following error An unresolvable problem occurred while initializing the package information. Please report this bug against the 'update-manager' package and include the following error message: 'E:Encountered a section with no Package: header, E:Problem with MergeList /var/lib/apt/lists/ppa.launchpad.net_sun-java-community- team_sun-java6_ubuntu_dists_precise_main_binary-amd64_Packages, E:The package lists or status file could not be parsed or opened.' ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019507 Title: Update manager issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1019507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 937040] Re: Duplicate ufw rules installed by dovecot packages
Brian, thanks for the explanation, I had the same issue after upgrade to Precise and its all good now after removing the old/duplicate rules as per your suggestion! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/937040 Title: Duplicate ufw rules installed by dovecot packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/937040/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 937040] Re: Duplicate ufw rules installed by dovecot packages
Brian, thanks for the explanation, I had the same issue after upgrade to Precise and its all good now after removing the old/duplicate rules as per your suggestion! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/937040 Title: Duplicate ufw rules installed by dovecot packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/937040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 408051] [NEW] package update-manager 1:0.93.35 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1)
Public bug reported: Binary package hint: update-manager Traceback (most recent call last): File /usr/lib/python2.5/logging/_init_.py, line 753, in emit selt.flush() File /usr/lib/python2.5/logging/__init__.py, line 731, in flush self.stream.flush() IOError[Errno 9] Bad file descriptor ProblemType: Package Architecture: i386 DistroRelease: Ubuntu 8.10 ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) Package: update-manager 1:0.93.35 PackageArchitecture: all SourcePackage: update-manager Title: package update-manager 1:0.93.35 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) Uname: Linux 2.6.24-24-generic i686 ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package -- package update-manager 1:0.93.35 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) https://bugs.launchpad.net/bugs/408051 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 408051] Re: package update-manager 1:0.93.35 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1)
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/29802670/Dependencies.txt ** Attachment added: VarLogDistupgradeAptlog.gz http://launchpadlibrarian.net/29802671/VarLogDistupgradeAptlog.gz ** Attachment added: VarLogDistupgradeApttermlog.gz http://launchpadlibrarian.net/29802672/VarLogDistupgradeApttermlog.gz ** Attachment added: VarLogDistupgradeMainlog.gz http://launchpadlibrarian.net/29802673/VarLogDistupgradeMainlog.gz ** Attachment added: VarLogDistupgradeTermlog.gz http://launchpadlibrarian.net/29802674/VarLogDistupgradeTermlog.gz -- package update-manager 1:0.93.35 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) https://bugs.launchpad.net/bugs/408051 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
