[Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by local choice (Reaso
This affects me as well. I have trace information in the attached syslog. Below are the outputs from: * lsb_release -a * apt-cache policy network-manager * hwinfo --netcard - jss $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial $ apt-cache policy network-manager network-manager: Installed: 1.2.6-0ubuntu0.16.04.1 Candidate: 1.2.6-0ubuntu0.16.04.1 Version table: *** 1.2.6-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu0.16.04.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages $ hwinfo --netcard 24: PCI 200.0: 0200 Ethernet controller [Created at pci.366] Unique ID: rBUF.DLcddtZ5wl3 Parent ID: z8Q3.lhbiXmvIKtB SysFS ID: /devices/pci:00/:00:1c.0/:02:00.0 SysFS BusID: :02:00.0 Hardware Class: network Model: "Lenovo ThinkPad X60/X60s" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x109a "82573L Gigabit Ethernet Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x207e "ThinkPad X60/X60s" Driver: "e1000e" Driver Modules: "e1000e" Device File: eth0 Memory Range: 0xee00-0xee01 (rw,non-prefetchable) I/O Ports: 0x2000-0x201f (rw) IRQ: 28 (1760 events) HW Address: 00:16:d3:31:a0:90 Link detected: no Module Alias: "pci:v8086d109Asv17AAsd207Ebc02sc00i00" Driver Info #0: Driver Status: e1000e is active Driver Activation Cmd: "modprobe e1000e" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #10 (PCI bridge) 25: PCI 300.0: 0282 WLAN controller [Created at pci.366] Unique ID: y9sn.FZoxbnX_PE2 Parent ID: qTvu.nWUCVv8jNeC SysFS ID: /devices/pci:00/:00:1c.1/:03:00.0 SysFS BusID: :03:00.0 Hardware Class: network Model: "Intel PRO/Wireless 3945ABG [Golan] Network Connection" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x4227 "PRO/Wireless 3945ABG [Golan] Network Connection" SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x1010 Revision: 0x02 Driver: "iwl3945" Driver Modules: "iwl3945" Device File: wlan0 Features: WLAN Memory Range: 0xedf0-0xedf00fff (rw,non-prefetchable) IRQ: 31 (120102 events) HW Address: 00:18:de:66:4b:57 Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.745 5.765 5.785 5.805 5.825 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v8086d4227sv8086sd1010bc02sc80i00" Driver Info #0: Driver Status: iwl3945 is active Driver Activation Cmd: "modprobe iwl3945" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #11 (PCI bridge) ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1408963/+attachment/4944203/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1408963 Title: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 :03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING), To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1408963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] Re: utopic: Watchdog detected hard LOCKUP on cpu
** Tags added: kernel-unable-to-test-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] Re: utopic: Watchdog detected hard LOCKUP on cpu
** Package changed: 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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247161/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] Re: utopic: Watchdog detected hard LOCKUP on cpu
apport information ** Tags added: apport-collected utopic ** Description changed: After upgrading to Utopic, I have experienced two crashes (a few hours apart). I am unable to identify the trigger. Searching for similar bugs either apply to earlier releases of [K]Ubuntu or pertain to hardware that I do not have. I say my system crashes as I never wait long enough for the system to actually crash. I have had to reset the system both times in order to generate a response. In both instances, the mouse was still moving the cursor but no action by the mouse buttons or keyboard typing generated a response. Also, the machine would not respond to soft reset. A hard reset (prolonged depressing of the power button) was necessary to regain control. I have never experienced this issue before (on any hardware type) so I have limited information to offer (as I don't know where to look). I have attached the relevant syslog entries for the last crash. It is here that I determined the CPU lockups. First CPU 4 had a hard lockup, proceeded by a soft lockup on CPU 1. Please let me know what else to gather when this occurs again. - jss + --- + ApportVersion: 2.14.7-0ubuntu8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: jss5284 F pulseaudio + /dev/snd/controlC1: jss5284 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Ubuntu 14.10 + HibernationDevice: RESUME=UUID=c5ebf743-c96b-4f98-a04f-5f832e6661e4 + InstallationDate: Installed on 2013-03-31 (576 days ago) + InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) + MachineType: System manufacturer System Product Name + NonfreeKernelModules: wl + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic root=/dev/mapper/kubuntu-root ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 + ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 + RelatedPackageVersions: + linux-restricted-modules-3.16.0-23-generic N/A + linux-backports-modules-3.16.0-23-generic N/A + linux-firmware 1.138 + Tags: utopic + Uname: Linux 3.16.0-23-generic x86_64 + UpgradeStatus: Upgraded to utopic on 2014-10-27 (0 days ago) + UserGroups: adm cdrom dialout dip floppy libvirtd lpadmin plugdev sambashare scanner sudo syslog users vboxusers + _MarkForUpload: True + dmi.bios.date: 08/13/2013 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2104 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: P8Z77-V DELUXE + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.name: System Product Name + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247157/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247160/+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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247159/+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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247158/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247166/+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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247174/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247169/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247179/+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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247171/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247177/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247176/+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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247186/+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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247178/+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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247167/+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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247172/+files/WifiSyslog.txt ** Description changed: After upgrading to Utopic, I have experienced two crashes (a few hours apart). I am unable to identify the trigger. Searching for similar bugs either apply to earlier releases of [K]Ubuntu or pertain to hardware that I do not have. I say my system crashes as I never wait long enough for the system to actually crash. I have had to reset the system both times in order to generate a response. In both instances, the mouse was still moving the cursor but no action by the mouse buttons or keyboard typing generated a response. Also, the machine would not respond to soft reset. A hard reset (prolonged depressing of the power button) was necessary to regain control. I have never experienced this issue before (on any hardware type) so I have limited information to offer (as I don't know where to look). I have attached the relevant syslog entries for the last crash. It is here that I determined the CPU lockups. First CPU 4 had a hard lockup, proceeded by a soft lockup on CPU 1. Please let me know what else to gather when this occurs again. - jss --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jss5284 F pulseaudio /dev/snd/controlC1: jss5284 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c5ebf743-c96b-4f98-a04f-5f832e6661e4 InstallationDate: Installed on 2013-03-31 (576 days ago) InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic root=/dev/mapper/kubuntu-root ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-23-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (0 days ago) UserGroups: adm cdrom dialout dip floppy libvirtd lpadmin plugdev sambashare scanner sudo syslog users vboxusers _MarkForUpload: True dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer + --- + ApportVersion: 2.14.7-0ubuntu8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: jss5284 F pulseaudio + /dev/snd/controlC1: jss5284 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Ubuntu 14.10 + HibernationDevice: RESUME=UUID=c5ebf743-c96b-4f98-a04f-5f832e6661e4 + InstallationDate: Installed on 2013-03-31 (576 days ago) + InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) + MachineType: System manufacturer System Product Name + NonfreeKernelModules: wl + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic root=/dev/mapper/kubuntu-root ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 + ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 + RelatedPackageVersions: + linux-restricted-modules-3.16.0-23-generic N/A + linux-backports-modules-3.16.0-23-generic N/A + linux-firmware 1.138 + Tags: utopic + Uname: Linux 3.16.0-23-generic x86_64 + UpgradeStatus: Upgraded to utopic on 2014-10-27 (0 days ago) + UserGroups: adm cdrom dialout dip floppy libvirtd lpadmin plugdev sambashare scanner sudo syslog users vboxusers + _MarkForUpload: True + dmi.bios.date: 08/13/2013 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2104 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: P8Z77-V DELUXE + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture +
[Bug 1386518] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247180/+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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247183/+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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247182/+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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247165/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247175/+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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247162/+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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247170/+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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247181/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247168/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247185/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] AlsaInfo.txt
apport information ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247173/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247164/+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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247163/+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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247187/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247184/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1386518/+attachment/4247188/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] Re: utopic: Watchdog detected hard LOCKUP on cpu
Installed linux-image-3.18-rc2-generic-amd64. Also installed corresponding headers. bcmwl did not compile do to alloc_netdev() now taking 4 arguments. See make.log attached. ** Attachment added: make.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+attachment/4247624/+files/make.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1386518] Re: utopic: Watchdog detected hard LOCKUP on cpu
I need to generate an initramfs as I run encrypted multidisks that host LVM2. I am trying to find again the documentation on how to do this. - jss On Tue, Oct 28, 2014 at 7:23 PM, Jon Stumpf 1386...@bugs.launchpad.net wrote: Installed linux-image-3.18-rc2-generic-amd64. Also installed corresponding headers. bcmwl did not compile do to alloc_netdev() now taking 4 arguments. See make.log attached. ** Attachment added: make.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+attachment/4247624/+files/make.log -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- - jss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1386518] Re: utopic: Watchdog detected hard LOCKUP on cpu
I am willing to run the newer kernel but I need a refresher on how to create the initramfs to support my setup. The kernel is having an issue discovering the MD raid arrays I have configured. The boot disk is on a standard volume on an SSD. The remaining filesystems are all LVMs on the encrypted MD volumes. I just need to know the steps. I can figure out the details. Otherwise, I will tag this as I cannot test. - jss On Tue, Oct 28, 2014 at 7:54 PM, Jon Stumpf jon.stu...@gmail.com wrote: I need to generate an initramfs as I run encrypted multidisks that host LVM2. I am trying to find again the documentation on how to do this. - jss On Tue, Oct 28, 2014 at 7:23 PM, Jon Stumpf 1386...@bugs.launchpad.net wrote: Installed linux-image-3.18-rc2-generic-amd64. Also installed corresponding headers. bcmwl did not compile do to alloc_netdev() now taking 4 arguments. See make.log attached. ** Attachment added: make.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+attachment/4247624/+files/make.log -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- - jss -- - jss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] Re: utopic: Watchdog detected hard LOCKUP on cpu
** Attachment added: syslog.lockup https://bugs.launchpad.net/ubuntu/+bug/1386518/+attachment/4246758/+files/syslog.lockup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386518] [NEW] utopic: Watchdog detected hard LOCKUP on cpu
Public bug reported: After upgrading to Utopic, I have experienced two crashes (a few hours apart). I am unable to identify the trigger. Searching for similar bugs either apply to earlier releases of [K]Ubuntu or pertain to hardware that I do not have. I say my system crashes as I never wait long enough for the system to actually crash. I have had to reset the system both times in order to generate a response. In both instances, the mouse was still moving the cursor but no action by the mouse buttons or keyboard typing generated a response. Also, the machine would not respond to soft reset. A hard reset (prolonged depressing of the power button) was necessary to regain control. I have never experienced this issue before (on any hardware type) so I have limited information to offer (as I don't know where to look). I have attached the relevant syslog entries for the last crash. It is here that I determined the CPU lockups. First CPU 4 had a hard lockup, proceeded by a soft lockup on CPU 1. Please let me know what else to gather when this occurs again. - jss ** Affects: 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/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1386518] Re: utopic: Watchdog detected hard LOCKUP on cpu
My machine is slow on some tasks but not very busy as per ksysguard. Using top, I noticed that one of my RAID drives is resync-ing and bootchart-collector is consuming 10% of the CPU many minutes after the reboot. I am not sure if the MD resync was before or after the system crashes. On Tue, Oct 28, 2014 at 12:42 AM, Jon Stumpf 1386...@bugs.launchpad.net wrote: ** Attachment added: syslog.lockup https://bugs.launchpad.net/ubuntu/+bug/1386518/+attachment/4246758/+files/syslog.lockup -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1386518/+subscriptions -- - jss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386518 Title: utopic: Watchdog detected hard LOCKUP on cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1386518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1354193] [NEW] Variables in /etc/default/tomcat7 overridden in /etc/init.d/tomcat7
Public bug reported: Many variables defined in /etc/default/tomcat7 are overridden in /etc/init.d/tomcat7. In short, they cannot be set in /etc/default/tomcat7. These are: TOMCAT7_USER, TOMCAT7_GROUP, TOMCAT7_SECURITY, JVM_TMP, and JAVA_HOME. If empty, JVM_TMP was set to /etc/tomcat7-$NAME-tmp. With NAME=tomcat7, this was redundant and I fixed it to match what is documented in /etc/default/tomcat7. In the (temporary) logic to set JAVA_HOME, there was an error in enumerating the java-7-openjdk's. The error caused the enumerated list to only be the last directory discovered. I fixed the error to match the logic for the java-6-openjdk's. Lastly, the auto-generate message for the policies is hardcoded. I added logic to list both the logical path and, if different, the physical path to the policy.d directory. ** Affects: tomcat7 (Ubuntu) Importance: Undecided Status: New ** Patch added: tomcat7.diff https://bugs.launchpad.net/bugs/1354193/+attachment/4172311/+files/tomcat7.diff ** Description changed: - Many variables defined in /etc/default/tomcat7 are overridden + Many variables defined in /etc/default/tomcat7 are overridden in /etc/init.d/tomcat7. In short, they cannot be set in /etc/default/tomcat7. These are: TOMCAT7_USER, TOMCAT7_GROUP, TOMCAT7_SECURITY, JVM_TMP, and JAVA_HOME. If empty, JVM_TMP was set to /etc/tomcat7-$NAME-tmp. With NAME=tomcat7, this was redundant and I fixed it to match what is documented in /etc/default/tomcat7. In the (temporary) logic to set JAVA_HOME, there was an error in enumerating the java-7-openjdk's. The error caused the enumerated list to only be the last directory discovered. I fixed the error to match the logic for the java-6-openjdk's. + + Lastly, the auto-generate message for the policies is hardcoded. I + added logic to list both the logical path and, if different, the + physical path to the policy.d directory. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat7 in Ubuntu. https://bugs.launchpad.net/bugs/1354193 Title: Variables in /etc/default/tomcat7 overridden in /etc/init.d/tomcat7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1354193/+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 1354203] [NEW] /etc/cron.daily/tomcat7 overrides variables defined in /etc/default/tomcat7
Public bug reported: LOGFILE_DAYS and LOGFILE_COMPRESS are overridden. ** Affects: tomcat7 (Ubuntu) Importance: Undecided Status: New ** Patch added: cron.tomcat7.diff https://bugs.launchpad.net/bugs/1354203/+attachment/4172325/+files/cron.tomcat7.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat7 in Ubuntu. https://bugs.launchpad.net/bugs/1354203 Title: /etc/cron.daily/tomcat7 overrides variables defined in /etc/default/tomcat7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1354203/+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 1354193] [NEW] Variables in /etc/default/tomcat7 overridden in /etc/init.d/tomcat7
Public bug reported: Many variables defined in /etc/default/tomcat7 are overridden in /etc/init.d/tomcat7. In short, they cannot be set in /etc/default/tomcat7. These are: TOMCAT7_USER, TOMCAT7_GROUP, TOMCAT7_SECURITY, JVM_TMP, and JAVA_HOME. If empty, JVM_TMP was set to /etc/tomcat7-$NAME-tmp. With NAME=tomcat7, this was redundant and I fixed it to match what is documented in /etc/default/tomcat7. In the (temporary) logic to set JAVA_HOME, there was an error in enumerating the java-7-openjdk's. The error caused the enumerated list to only be the last directory discovered. I fixed the error to match the logic for the java-6-openjdk's. Lastly, the auto-generate message for the policies is hardcoded. I added logic to list both the logical path and, if different, the physical path to the policy.d directory. ** Affects: tomcat7 (Ubuntu) Importance: Undecided Status: New ** Patch added: tomcat7.diff https://bugs.launchpad.net/bugs/1354193/+attachment/4172311/+files/tomcat7.diff ** Description changed: - Many variables defined in /etc/default/tomcat7 are overridden + Many variables defined in /etc/default/tomcat7 are overridden in /etc/init.d/tomcat7. In short, they cannot be set in /etc/default/tomcat7. These are: TOMCAT7_USER, TOMCAT7_GROUP, TOMCAT7_SECURITY, JVM_TMP, and JAVA_HOME. If empty, JVM_TMP was set to /etc/tomcat7-$NAME-tmp. With NAME=tomcat7, this was redundant and I fixed it to match what is documented in /etc/default/tomcat7. In the (temporary) logic to set JAVA_HOME, there was an error in enumerating the java-7-openjdk's. The error caused the enumerated list to only be the last directory discovered. I fixed the error to match the logic for the java-6-openjdk's. + + Lastly, the auto-generate message for the policies is hardcoded. I + added logic to list both the logical path and, if different, the + physical path to the policy.d directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1354193 Title: Variables in /etc/default/tomcat7 overridden in /etc/init.d/tomcat7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1354193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1354203] [NEW] /etc/cron.daily/tomcat7 overrides variables defined in /etc/default/tomcat7
Public bug reported: LOGFILE_DAYS and LOGFILE_COMPRESS are overridden. ** Affects: tomcat7 (Ubuntu) Importance: Undecided Status: New ** Patch added: cron.tomcat7.diff https://bugs.launchpad.net/bugs/1354203/+attachment/4172325/+files/cron.tomcat7.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1354203 Title: /etc/cron.daily/tomcat7 overrides variables defined in /etc/default/tomcat7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1354203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1270686] [NEW] rsnapshot LVM backup fails at line 3720
Public bug reported:
This error is received for each LVM listed in the rsnapshot.conf file:
Use of uninitialized value $linux_lvm_oldpwd in concatenation (.) or
string at /usr/bin/rsnapshot line 3720.
chdir()
Use of uninitialized value $linux_lvm_oldpwd in chdir at
/usr/bin/rsnapshot line 3722.
Use of chdir('') or chdir(undef) as chdir() is deprecated at
/usr/bin/rsnapshot line 3722.
The error actually occurs at the assignment of $linux_lvm_oldpwd on line 3543.
$linux_lvm_oldpwd = $ENV{PWD};
$ENV{PWD} returns nothing. This was not the case in December and this
started failing for me sometime around Jan 10th, 2014. I am not a Perl
programmer but the documentation I found states that the proper way to
get the current working directory is to call cwd() and NOT use
$ENV{PWD}.
I replaced the offending line with the following:
$linux_lvm_oldpwd = cwd();
I no longer experience the issue.
- jss
** Affects: rsnapshot (Ubuntu)
Importance: Undecided
Status: New
** Patch added: rsnapshot.patch
https://bugs.launchpad.net/bugs/1270686/+attachment/3952433/+files/rsnapshot.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270686
Title:
rsnapshot LVM backup fails at line 3720
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsnapshot/+bug/1270686/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1270686] Re: rsnapshot LVM backup fails at line 3720
$ dpkg --status perl Package: perl Status: install ok installed Priority: standard Section: perl Installed-Size: 17115 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Architecture: amd64 Version: 5.14.2-21build1 ... lines deleted ... $ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1270686 Title: rsnapshot LVM backup fails at line 3720 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsnapshot/+bug/1270686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1216470] Re: ntfs-3g Raring package does not indicate it replaces ntfsprogs
I had already created the dummy package to avoid the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1216470 Title: ntfs-3g Raring package does not indicate it replaces ntfsprogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1216470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1216470] [NEW] ntfs-3g Raring package does not indicate it replaces ntfsprogs
Public bug reported: When installing third-party packages that depend on ntfsprogs and support multiple Ubuntu versions, the dependency check fails on Raring Ringtail since the ntfs-3g package does not indicate it replaces ntfsprogs (source: aptitude show ntfs-3g). I suspect this was overlooked in Raring as ntfsprogs was dropped (not provided) in Raring. Unfortunately, some third-party packages will still address ntfsprogs for sometime and it would be helpful if ntfs-3g would satisfy the dependency. I have filed a bug with the third-party provider as well. ** Affects: ntfs-3g (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/1216470 Title: ntfs-3g Raring package does not indicate it replaces ntfsprogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1216470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 872093] Re: SD Card not being recognized
I have the same history/problem with my Dell Vostro 2510. - jss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/872093 Title: SD Card not being recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/872093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292010] Re: opengl error with i830_vtbl.c:465: i830_emit_state: Assertion `0' failed.
Is there a workaround for this (e.g., disable desktop effects)? Is there a timeframe to fix this issue? -- opengl error with i830_vtbl.c:465: i830_emit_state: Assertion `0' failed. https://bugs.launchpad.net/bugs/292010 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 550104] Re: Plymouth seems to kill all tty's on my native resolution
All, After reading numerous posts on the ugly purple screen, my fix was the following. 1) purge all existing nvidia packages (sudo apt-get purge 'nvidia*') 2) blacklist the free and old proprietary drivers (http://forums.nvidia.com/index.php?showtopic=167422) 3) install the proprietary driver from the nvidia website (ppa repository didn't have nvidia-glx-195) 4) Edit /etc/default/grub a) Add/update GRUB_GFXMODE to the physical screen resolution, GRUB_GFXMODE=1440x900 b) Add GRUB_GFXPAYLOAD_LINUX=1440x900 5) sudo update-grub2 6) echo FRAMEBUFFER=y | sudo tee 6) sudo update-initramfs -u 4b was the crucial step. Once I added this to /etc/default/grub, default.plymouth worked. Most of my answers were found in http://ubuntuforums.org/showthread.php?t=1469475. -- Plymouth seems to kill all tty's on my native resolution https://bugs.launchpad.net/bugs/550104 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 550104] Re: Plymouth seems to kill all tty's on my native resolution
Correction 6) sudo gedit /etc/initramfs-tools/conf.d/splash and add FRAMEBUFFER=y 7) sudo update-initramfs -u -- Plymouth seems to kill all tty's on my native resolution https://bugs.launchpad.net/bugs/550104 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 303807] Re: X server 1.5.2 aborts in __glxContextDestroy, within 15 minutes after login
Bryce, Following the Backtracing instructions, I added the debugger symbols and attempted to recreate the problem while Xorg was attached to gdb. I have been unsuccessful in duplicating the problem as of yet. The machine has not experienced the problem since it was rebooted: 21:23:08 up 2 days, 39 min. What I have been able to do capture backtraces after Xorg receives SIGPIPE signals from what appears some failure between the screensaver and the Xorg server. The keuphoria.kss seems to hang after 30 seconds or so. I kill it with SIGHUP as SIGTERM does not work - I suspect by design. I have attached 3 output files for your inspection. I will continue to attempt to recreate the problem. One difference (beyond the debugging symbols and gdb) is I didn't have the laptop in it's docking station. I will attempt that over the next couple of days. - jss - jss ** Attachment added: gdb-Xorg.tbz http://launchpadlibrarian.net/24553647/gdb-Xorg.tbz -- X server 1.5.2 aborts in __glxContextDestroy, within 15 minutes after login https://bugs.launchpad.net/bugs/303807 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 303807] Re: X server 1.5.2 aborts, signal 11, within 15 minutes after login
Note that I am using Kubuntu so I do not have a /var/log/gdm directory. That said, I have attached all the available kdm logs which have the both planes enabled error and a backtrace. Let me know if this is sufficient. ** Attachment added: kdm.tar http://launchpadlibrarian.net/23594908/kdm.tar -- X server 1.5.2 aborts, signal 11, within 15 minutes after login https://bugs.launchpad.net/bugs/303807 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 303807] Re: X server 1.5.2 aborts, signal 11, within 15 minutes after login
** Attachment added: lspci-vvnn.out http://launchpadlibrarian.net/21584494/lspci-vvnn.out -- X server 1.5.2 aborts, signal 11, within 15 minutes after login https://bugs.launchpad.net/bugs/303807 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 303807] Re: X server 1.5.2 aborts, signal 11, within 15 minutes after login
** Attachment added: xorg.conf http://launchpadlibrarian.net/21457901/xorg.conf -- X server 1.5.2 aborts, signal 11, within 15 minutes after login https://bugs.launchpad.net/bugs/303807 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 303807] Re: X server 1.5.2 aborts, signal 11, within 15 minutes after login
** Attachment added: Xorg.0.log immediately following a crash http://launchpadlibrarian.net/21457919/Xorg.0.log-saved -- X server 1.5.2 aborts, signal 11, within 15 minutes after login https://bugs.launchpad.net/bugs/303807 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 303807] Re: X server 1.5.2 aborts, signal 11, within 15 minutes after login
** Attachment added: Xorg.0.log without xorg.conf http://launchpadlibrarian.net/21458038/Xorg.0.log-no-xorg.conf -- X server 1.5.2 aborts, signal 11, within 15 minutes after login https://bugs.launchpad.net/bugs/303807 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 303807] Re: X server 1.5.2 aborts, signal 11, within 15 minutes after login
Dan, Thanks for getting back to me. The last crash was yesterday while it was idle. I have attached the information as you requested: xorg.conf Xorg.0.log (using the existing xorg.conf) Xorg.0.log (w/o xorg.conf) - jss -- X server 1.5.2 aborts, signal 11, within 15 minutes after login https://bugs.launchpad.net/bugs/303807 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 303807] Re: X server 1.5.2 aborts, signal 11, within 15 minutes after login
Dan, One additional point that may be related. During a session, I sometimes get a dialog box saying something to the effect that a monitor configuration change has been detected and it asks me if I would like to reconfigure or ignore. I have ignore and reconfigured - both with no obvious effect. Next time it happens, I will record the message. The last time happened during the session when the xorg.conf was not used. - jss -- X server 1.5.2 aborts, signal 11, within 15 minutes after login https://bugs.launchpad.net/bugs/303807 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
