The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Confirmed => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1334964 Title: [LENOVO IdeaPad U410] hibernate/resume failure Status in linux package in Ubuntu: Expired Bug description: Issue occurs on occasion when laptop goes into hibernation, it will sometimes not allow the OS to boot up properly and will require a hard reset. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-6-generic 3.15.0-6.11 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 Annotation: This occured during a previous hibernate and prevented it from resuming properly. ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: phantom 3313 F.... pulseaudio Date: Wed Jun 25 00:47:38 2014 DuplicateSignature: hibernate/resume:LENOVO IdeaPad U410:65CN89WW ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=6ef445f3-4ec3-401b-bbb5-8433beb033c3 InstallationDate: Installed on 2014-06-10 (16 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO IdeaPad U410 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic.efi.signed root=UUID=b81f86dc-0438-428d-9bdc-548699b3beed ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware 1.131 SourcePackage: linux StagingDrivers: keucr Title: [LENOVO IdeaPad U410] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/04/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 65CN89WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo dmi.board.vendor: LENOVO dmi.board.version: 31900003WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo U410 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr65CN89WW:bd09/04/2012:svnLENOVO:pnIdeaPadU410:pvrLenovoU410:rvnLENOVO:rnLenovo:rvr31900003WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoU410: dmi.product.name: IdeaPad U410 dmi.product.version: Lenovo U410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1334964/+subscriptions
суббота
[Bug 1635891] Re: Random hangs after upgrade to 4.4.0-45, possibly cgroup related
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Confirmed => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1635891 Title: Random hangs after upgrade to 4.4.0-45, possibly cgroup related Status in linux package in Ubuntu: Expired Bug description: Apologize in advance is anything is missing from this bug report. After upgrading to 4.4.0-45 we have started to experience random kernel lockups. I have attached a sample from the syslog which I managed to catch after one of these events. In other cases, nothing was written to the syslog. I notice that the cgroup system features here and there in the log, and the hanging server uses cgroups and namespaces heavily, so I suspect it is related. Sadly I don't know enough of the kernel to decipher the error I got further than that. Another unusual thing we do on this server, which may possibly be related, is that we regularly clear the caches ("echo 3 > /proc/sys/vm/drop_caches") /Pehr ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Oct 22 22:52 seq crw-rw---- 1 root audio 116, 33 Oct 22 22:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Oct 22 23:37:59 2016 HibernationDevice: RESUME=/dev/mapper/template--16--vg-swap_1 InstallationDate: Installed on 2016-04-22 (183 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic root=/dev/mapper/template--16--vg-root ro cgroup_enable=memory swapaccount=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware 1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1635891/+subscriptions
[Bug 1167065] Re: CVE-2013-1929
The task "linux-lts-saucy (Ubuntu Trusty)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Expired ** Tags added: kernel-autoclosed-eol -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1167065 Title: CVE-2013-1929 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Expired Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Expired Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Expired Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Won't Fix Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-backport-oneiric source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Expired Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux-lts-backport-oneiric source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Won't Fix Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid Status in linux-lts-backport-maverick source package in Vivid: Invalid Status in linux-lts-backport-natty source package in Vivid: Invalid Status in linux-lts-backport-oneiric source package in Vivid: Invalid Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Won't Fix Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-lts-wily source package in Vivid: Invalid Status in linux-lts-xenial source package in Vivid: Won't Fix Status in linux-mako source package in Vivid: Won't Fix Status in linux-manta source package in Vivid: Invalid Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-raspi2 source package in Vivid: Invalid Status in linux-snapdragon source package in Vivid: Won't Fix Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: Won't Fix Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: Invalid Status in linux-lts-backport-maverick source package in Wily: Invalid Status in linux-lts-backport-natty source package in Wily: Invalid Status in linux-lts-backport-oneiric source package in Wily: Invalid Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Won't Fix Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: Won't Fix Status in linux-manta source package in Wily: Invalid Status in linux-mvl-dove source package in Wily: Invalid Status in linux-raspi2 source package in Wily: Invalid Status in linux-snapdragon source package in Wily: Invalid Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Invalid Status in linux-armadaxp source package in Xenial: Invalid Status in linux-ec2 source package in Xenial: Invalid Status in linux-flo source package in Xenial: Expired Status in linux-fsl-imx51 source package in Xenial: Invalid Status in linux-goldfish source package in Xenial: Invalid Status in linux-lts-backport-maverick source package in Xenial: Invalid Status in linux-lts-backport-natty source package in Xenial: Invalid Status in linux-lts-backport-oneiric source package in Xenial: Invalid Status in linux-lts-quantal source package in Xenial: Invalid Status in linux-lts-raring source package in Xenial: Invalid Status in linux-lts-saucy source package in Xenial: Expired Status in linux-lts-trusty source package in Xenial: Invalid Status in linux-lts-utopic source package in Xenial: Invalid Status in linux-lts-vivid source package in Xenial: Invalid Status in linux-lts-wily source package in Xenial: Invalid Status in linux-lts-xenial source package in Xenial: Invalid Status in linux-mako source package in Xenial: Expired Status in linux-manta source package in Xenial: Invalid Status in linux-mvl-dove source package in Xenial: Invalid Status in linux-raspi2 source package in Xenial: Fix Committed Status in linux-snapdragon source package in Xenial: Invalid Status in linux-ti-omap4 source package in Xenial: Invalid Status in linux source package in Yakkety: Invalid Status in linux-armadaxp source package in Yakkety: Invalid Status in linux-ec2 source package in Yakkety: Invalid Status in linux-flo source package in Yakkety: Won't Fix Status in linux-fsl-imx51 source package in Yakkety: Invalid Status in linux-goldfish source package in Yakkety: Invalid Status in linux-lts-backport-maverick source package in Yakkety: Invalid Status in linux-lts-backport-natty source package in Yakkety: Invalid Status in linux-lts-backport-oneiric source package in Yakkety: Invalid Status in linux-lts-quantal source package in Yakkety: Invalid Status in linux-lts-raring source package in Yakkety: Invalid Status in linux-lts-saucy source package in Yakkety: Won't Fix Status in linux-lts-trusty source package in Yakkety: Invalid Status in linux-lts-utopic source package in Yakkety: Invalid Status in linux-lts-vivid source package in Yakkety: Invalid Status in linux-lts-wily source package in Yakkety: Invalid Status in linux-lts-xenial source package in Yakkety: Invalid Status in linux-mako source package in Yakkety: Won't Fix Status in linux-manta source package in Yakkety: Invalid Status in linux-mvl-dove source package in Yakkety: Invalid Status in linux-raspi2 source package in Yakkety: Fix Committed Status in linux-snapdragon source package in Yakkety: Invalid Status in linux-ti-omap4 source package in Yakkety: Invalid Bug description: Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data (VPD) data structure. Break-Fix: 184b89044fb6e2a74611dafa69b1dce0d98612c6 715230a44310a8cf66fbfb5a46f9a62a9b2de424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167065/+subscriptions
[Bug 1851447] Re: aufs-tools 4.14 FTBFS because of wrong SAUCE driver in the kernel
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Confirmed => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1851447 Title: aufs-tools 4.14 FTBFS because of wrong SAUCE driver in the kernel Status in linux package in Ubuntu: Expired Bug description: The latest aufs-tools package synced from Debian fails to build in Ubuntu (but not in Debian) because the Ubuntu kernel package has aufs sauce patches and they are not at a compatible version. [...] dh_auto_install install -d /<<BUILDDIR>>/aufs-tools-4.14\+20190211/debian/aufs-tools make -j4 install DESTDIR=/<<BUILDDIR>>/aufs-tools-4.14\+20190211/debian/aufs-tools AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" make[1]: Entering directory '/<<BUILDDIR>>/aufs-tools-4.14+20190211' cc -g -O2 -fdebug-prefix-map=/<<BUILDDIR>>/aufs-tools-4.14+20190211=. -fstack-protector-strong -Wformat -Werror=format-security -O -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I./libau -DAUFHSM_CMD=\"/usr/bin/aufhsm\" -DMOUNT_CMD=\"/bin/mount\" -DUMOUNT_CMD=\"/bin/umount\" -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now ver.c -o ver ./ver Wrong version! aufs-util for aufs4.14 20190211, but aufs is 4.x-rcN-20190805. See README in detail and try git branch -a. make[1]: *** [Makefile:120: ver_test] Error 255 rm ver [...] (https://launchpad.net/ubuntu/+source/aufs- tools/1:4.14+20190211-1/+build/17953990) Please either update the aufs patches in the kernel tree, or else drop them. (My understanding is that we probably don't want to drop them because docker may use aufs as a backend; and while this is deprecated, there is currently no upgrade story for users currently using it.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851447/+subscriptions
[Bug 1375514] Re: [Dell Inspiron 5547] Cursor jumps to trash or last icon on launch bar
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Triaged => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1375514 Title: [Dell Inspiron 5547] Cursor jumps to trash or last icon on launch bar Status in linux package in Ubuntu: Expired Bug description: When typing, frequently the cursor will jump to the last application icon in the launch bar. This is happening even though the touch pad is not touched. Also mouse settings have "disable touchpad when typing" enabled. sudo xinput [sudo] password for pme991: ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ DLL063E:00 06CB:2934 id=11 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Power Button id=8 [slave keyboard (3)] ↳ Sleep Button id=9 [slave keyboard (3)] ↳ Integrated_Webcam_HD id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)] ↳ Dell WMI hotkeys id=14 [slave keyboard (3)] lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 I appreciate any guidance or assistance. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: pme991 1862 F.... pulseaudio /dev/snd/controlC1: pme991 1862 F.... pulseaudio CurrentDesktop: Unity Date: Mon Sep 29 16:53:08 2014 HibernationDevice: RESUME=UUID=f38517c4-e36a-4946-9bea-30c050152453 InstallationDate: Installed on 2014-09-16 (13 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 5547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=af854011-dbd6-4233-843b-7a8178702c5b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.7 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0598GM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A04 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/09/2014:svnDellInc.:pnInspiron5547:pvrA04:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA04: dmi.product.name: Inspiron 5547 dmi.product.version: A04 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1375514/+subscriptions
[Bug 1288233] Re: Failed loading after update to 3.13.0-15 kernel. VmWare virt.
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Confirmed => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1288233 Title: Failed loading after update to 3.13.0-15 kernel. VmWare virt. Status in linux package in Ubuntu: Expired Bug description: Hello! Have a server under VMWare virtualisation in cloudatcost.com, Canada. After updating to last 3.13 kernel (previously i have updated raring to trusty) i have a bug: Root device dnt exist after loading initram - updating to linux-image-3.13.0-15-generic invoking that problem. I have now two kernels in system: 3.8 and 3.13.0-15. First 3.8 loading success, but 3.13.0-15 now have a problem with llvm and udev - root device do not exists and i have BusyBox shell such as: ALERT! /dev/disk/by-uuid/[MYUDIDNUMBER] does not exist. Dropping to a shell! BusyBox Before 3.13.0-15 i have also 3.13 kernel, but older and loading was succes without any warning or errors. Now i using 3.8 raring kernel on that server. 3.8 and 3.13 have a same grub config with same UDDID's, but 3.13.0-15 have the issue with this problem. --- AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Mar 4 17:15 seq crw-rw---- 1 root audio 116, 33 Mar 4 17:15 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=2c8e3542-e1c0-457b-a19d-6a76d750d0cb InstallationDate: Installed on 2013-10-14 (142 days ago) InstallationMedia: Ubuntu-Server 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.2) IwConfig: eth0 no wireless extensions. lo no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-29-generic root=UUID=638da42e-7b1b-48ac-8164-1dbefafea00b ro ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 RelatedPackageVersions: linux-restricted-modules-3.8.0-29-generic N/A linux-backports-modules-3.8.0-29-generic N/A linux-firmware 1.125 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-02-23 (9 days ago) UserGroups: cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/22/2012 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd06/22/2012:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1288233/+subscriptions
[Bug 1284342] Re: [REGRESSION Ubuntu 13.10] NumLock LED behavior on external USB keyboard screwed up
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Confirmed => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1284342 Title: [REGRESSION Ubuntu 13.10] NumLock LED behavior on external USB keyboard screwed up Status in linux package in Ubuntu: Expired Bug description: After upgrading from Ubuntu 13.04 to 13.10, issue #1250186 with the Caps Lock LED is fixed, and now NumLock, which used to work (almost) correctly, is srewed up, suffering from exactly the same issue as CapsLock used to. Steps to reproduce: - plug an external USB keyboard - turn on NumLock on that keyboard => the keyboard's NumLock LED turns on, and the numeric keys start working as numbers, as expected - now unplug the keyboard - replug the keyboard => Expected: the LED status must be consistent with the actual behavior. And it used to be!! It used to work in the best possible way: numlock status USED TO BE REMEMBERED, and the LED status was updated when replugging the keyboard, so after unplug/replug the behavior was as before and the displayed status was consistent with it. => Observed: the actual NumLock status is remembered, meaning the numeric keys keep working as number keys, as if num lock was ON, which is how it was prior to unplug/replug. But the LED is now off, so it is inconsistent with reality. The fact that the upgrade from 13.04 to 13.10 has fixed #1250186 and has screwed up NumLock behavior which was OK (on the same computer and same external keyboard), demonstrates that both are 100% software issues, i.e. Ubuntu issues, not hardware ones. And that correct behavior can be achieved. The only thing that was already wrong with NumLock, and remains wrong after the upgrade, is that the external keyboard's LED status is not updated when the NumLock status is changed from the laptop's builtin keyboard's NumLock key, while the behavior is always the same for both keyboards (leds behave as if keyboard were independent, but they are not). However, this provides a workaround for the bug, so it must NOT be changed before the bug is fixed. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-17-generic 3.11.0-17.31 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: teo 2186 F.... pulseaudio Date: Mon Feb 24 22:18:44 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-17-generic N/A linux-backports-modules-3.11.0-17-generic N/A linux-firmware 1.116.2 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284342/+subscriptions
[Bug 1401415] Re: [Dell Inspiron 2350] could not control brightness
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Confirmed => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1401415 Title: [Dell Inspiron 2350] could not control brightness Status in linux package in Ubuntu: Expired Bug description: Dell Inspiron 2350 (CID 201305-13669) with Ubuntu 14.04.1 Linux 201305-13669 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) Steps to reproduce this bug: 1. install Ubuntu 14.04.1 2. after installing, boot into desktop 3. dash --> brightness Expected result: There is an brightness slider on the brightness panel Actual result: There is no such slider. More information: /sys/class/backlight/ shows nothing ubuntu@201305-13669:~$ ls /sys/class/backlight/ ubuntu@201305-13669:~$ --------------------------------------------------------------- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1476 F.... pulseaudio /dev/snd/controlC1: ubuntu 1476 F.... pulseaudio CurrentDesktop: Unity CurrentDmesg: [ 15.148179] thinkpad_ec: no ThinkPad embedded controller! [ 17.013792] init: plymouth-upstart-bridge main process ended, respawning [ 17.021574] init: plymouth-upstart-bridge main process ended, respawning [ 17.969005] r8169 0000:03:00.0 eth0: link up [ 17.969013] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=a6237ffe-4fa9-4ab7-9253-55430263f86f InstallationDate: Installed on 2014-12-08 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 2350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=fe7cefb8-002c-4091-9a6e-6cab455727b5 ro rootdelay=60 quiet splash initcall_debug vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 08NG84 dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd09/02/2013:svnDellInc.:pnInspiron2350:pvr00:rvnDellInc.:rn08NG84:rvrX01:cvnDellInc.:ct13:cvr00: dmi.product.name: Inspiron 2350 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401415/+subscriptions
[Bug 1292509] Re: Missing statistics for `tx_bytes`, `tx_packets`, `rx_bytes` and `rx_packets` since Ubuntu 13.10
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Confirmed => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1292509 Title: Missing statistics for `tx_bytes`, `tx_packets`, `rx_bytes` and `rx_packets` since Ubuntu 13.10 Status in linux package in Ubuntu: Expired Status in linux package in Arch Linux: New Status in linux package in Fedora: New Bug description: I am using Ubuntu 13.10 and have an Ethernet connection to connect to the Internet. If I set my ISP username and password in router-cum-modem (ADSL) itself (i.e.; I get connected to internet automatically by just powering on my router); I don't get the information about `tx_bytes`, `tx_packets`, `rx_bytes` and `rx_packets` anymore. If I don't put the username and password in router; and instead use `sudo pppoeconf` to configure my connection by providing my ISP username and password; I get the information about `tx_bytes`, `tx_packets`, `rx_bytes` and `rx_packets` as expected. It is probably because of this bug, that Gnome System Monitor doesn't update Network History as reported earlier: https://bugs.launchpad.net/ubuntu/+source/gnome-system- monitor/+bug/1241894 =================================================================================== I have run the following commands on Ubuntu 13.10 installed on my system as per the answers given to this question: http://serverfault.com/questions/533513/how-to-get-tx-rx-bytes- without-ifconfig $ uname -a Linux aditya-desktop 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:13:28 UTC 2014 i686 athlon i686 GNU/Linux $ ifconfig eth0 Link encap:Ethernet HWaddr 94:de:80:34:47:7b inet addr:192.168.1.8 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::96de:80ff:fe34:477b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:18 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:49 errors:0 dropped:0 overruns:0 frame:0 TX packets:49 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4819 (4.8 KB) TX bytes:4819 (4.8 KB) $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0 $ cat /proc/net/dev Inter-| Receive | Transmit face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed lo: 190070 1601 0 0 0 0 0 0 190070 1601 0 0 0 0 0 0 eth0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 $ netstat -i Kernel Interface table Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg eth0 1500 0 0 0 0 0 0 0 0 0 BMRU lo 65536 0 1601 0 0 0 1601 0 0 0 LRU $ ip -s link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 RX: bytes packets errors dropped overrun mcast 190070 1601 0 0 0 0 TX: bytes packets errors dropped carrier collsns 190070 1601 0 0 0 0 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000 link/ether 94:de:80:34:47:7b brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 0 0 0 0 0 0 TX: bytes packets errors dropped carrier collsns 0 0 0 0 0 0 $ cat /sys/class/net/eth0/statistics/rx_bytes 0 $ cat /sys/class/net/eth0/statistics/rx_packets 0 $ cat /sys/class/net/eth0/statistics/tx_bytes 0 $ cat /sys/class/net/eth0/statistics/tx_packets 0 =================================================================================== It is working upto Ubuntu 12.04.3 and Ubuntu 13.04. I have run the following commands in Ubuntu 12.04.3 Live environment, which reports those statistics: $ uname -a Linux this 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 15:31:16 UTC 2013 i686 athlon i386 GNU/Linux $ ifconfig eth0 Link encap:Ethernet HWaddr 94:de:80:34:47:7b inet addr:192.168.1.8 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::96de:80ff:fe34:477b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:49 errors:0 dropped:0 overruns:0 frame:0 TX packets:109 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:26744 (26.7 KB) TX bytes:14380 (14.3 KB) Interrupt:18 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:25 errors:0 dropped:0 overruns:0 frame:0 TX packets:25 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2175 (2.1 KB) TX bytes:2175 (2.1 KB) $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0 =================================================================================== The bug was introduced in 13.10 and is still present in the development version of 14.04 as of today. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-18-generic 3.11.0-18.32 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: aditya 1390 F.... pulseaudio CurrentDmesg: [ 44.202948] systemd-hostnamed[1875]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! Date: Fri Mar 14 17:55:53 2014 HibernationDevice: RESUME=UUID=3d3ddc24-09de-4fd8-8d48-3fb947c0fc74 InstallationDate: Installed on 2014-03-06 (8 days ago) InstallationMedia: This IwConfig: lo no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2PT MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic root=UUID=b36eb8ca-34bb-41af-8b4f-c9514488396f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-18-generic N/A linux-backports-modules-3.11.0-18-generic N/A linux-firmware 1.116.2 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FC dmi.board.name: GA-78LMT-S2PT dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFC:bd11/05/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2PT:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2PT:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2PT dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1292509/+subscriptions
[Bug 1864147] Re: [bionic] Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Confirmed => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1864147 Title: [bionic] Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty Status in linux package in Ubuntu: Expired Status in linux source package in Bionic: Expired Bug description: [SRU Justification] [Impact] Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using HID's INT3511/INT3512. As a consequence, HW manufacturers have complete freedom to install any devices on-board as long as they can be accessed over serial tty interface. Once such device is Dell Edge 3002 IoT Gateway which sports ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively. Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver handles the enumeration for the slaves connected on these ports. Also, /dev/ttySx device nodes for these ports are no longer exposed to the userspace. [Fixes] This patchset allows the skipped virtual UART's with ACPI HID's mentioned above to be enumerated as ttyHSx port. [Regression Potential] Low. This driver binds only to Intel Atom E38XX (Baytrail-I) virtual serial ports on the Dell Edge 300x GW. These updates are being carried in the linux-oem (4.15.y) kernel for more than 2 years without any regressions. [Note] This driver has been submitted upstream and is under review. This issue has been identified as a regression in 4.15 and multiple solutions are being explored. Meanwhile, to support customer and maintain release schedule, this driver needs to be in Ubuntu 4.15 based kernels. More info: https://marc.info/?t=152455871600007&r=1&w=2 linux-oem buglink: http://bugs.launchpad.net/bugs/1690362 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864147/+subscriptions
[Bug 2147841] Re: Noble update: upstream stable patchset 2026-04-10
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2147841 Title: Noble update: upstream stable patchset 2026-04-10 Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2026-04-10 Ported from the following upstream stable releases: v6.6.124, v6.12.70 from git://git.kernel.org/ nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec x86/kfence: fix booting on 32bit non-PAE systems platform/x86: intel_telemetry: Fix swapped arrays in PSS output pmdomain: qcom: rpmpd: fix off-by-one error in clamping to the highest state pmdomain: imx8mp-blk-ctrl: Keep gpc power domain on for system wakeup pmdomain: imx: gpcv2: Fix the imx8mm gpu hang due to wrong adb400 reset pmdomain: imx8mp-blk-ctrl: Keep usb phy power domain on for system wakeup pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc->domains rbd: check for EOD after exclusive lock is ensured to be held ARM: 9468/1: fix memset64() on big-endian Revert "drm/amd: Check if ASPM is enabled from PCIe subsystem" KVM: Don't clobber irqfd routing type when deassigning irqfd netfilter: nft_set_pipapo: clamp maximum map bucket size to INT_MAX hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() binder: fix BR_FROZEN_REPLY error log binderfs: fix ida_alloc_max() upper bound KVM: selftests: Add -U_FORTIFY_SOURCE to avoid some unpredictable test failures gve: Fix stats report corruption on queue count change tracing: Fix ftrace event field alignments wifi: mac80211: ocb: skip rx_no_sta when interface is not joined wifi: wlcore: ensure skb headroom before skb_push net: usb: sr9700: support devices with virtual driver CD block,bfq: fix aux stat accumulation destination smb/server: call ksmbd_session_rpc_close() on error path in create_smb2_pipe() LoongArch: Set correct protection_map[] for VM_NONE/VM_SHARED LoongArch: Enable exception fixup for specific ADE subcode HID: intel-ish-hid: Update ishtp bus match to support device ID table HID: multitouch: add MT_QUIRK_STICKY_FINGERS to MT_CLS_VTL btrfs: fix reservation leak in some error paths when inserting inline extent HID: intel-ish-hid: Reset enum_devices_done before enumeration HID: playstation: Center initial joystick axes to prevent spurious events ALSA: hda/realtek: add HP Laptop 15s-eq1xxx mute LED quirk netfilter: replace -EEXIST with -EBUSY HID: quirks: Add another Chicony HP 5MP Cameras to hid_ignore_list HID: i2c-hid: fix potential buffer overflow in i2c_hid_get_report() HID: Apply quirk HID_QUIRK_ALWAYS_POLL to Edifier QR30 (2d99:a101) ring-buffer: Avoid softlockup in ring_buffer_resize() during memory free wifi: mac80211: collect station statistics earlier when disconnect ASoC: davinci-evm: Fix reference leak in davinci_evm_probe nvme-fc: release admin tagset if init fails nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready() ASoC: amd: yc: Fix microphone on ASUS M6500RE ASoC: tlv320adcx140: Propagate error codes during probe spi: hisi-kunpeng: Fixed the wrong debugfs node name in hisi_spi debugfs initialization regmap: maple: free entry on mas_store_gfp() failure wifi: cfg80211: Fix bitrate calculation overflow for HE rates scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() ALSA: hda/realtek: Fix headset mic for TongFang X6AR55xU scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() wifi: mac80211: correctly check if CSA is active wifi: mac80211: don't increment crypto_tx_tailroom_needed_cnt twice platform/x86: toshiba_haps: Fix memory leaks in add/remove routines platform/x86: intel_telemetry: Fix PSS event register mask platform/x86: hp-bioscfg: Skip empty attribute names smb/client: fix memory leak in smb2_open_file() net: add skb_header_pointer_careful() helper net/sched: cls_u32: use skb_header_pointer_careful() dpaa2-switch: prevent ZERO_SIZE_PTR dereference when num_ifs is zero net: liquidio: Initialize netdev pointer before queue setup net: liquidio: Fix off-by-one error in PF setup_nic_devices() cleanup net: liquidio: Fix off-by-one error in VF setup_nic_devices() cleanup dpaa2-switch: add bounds check for if_id in IRQ handler net: don't touch dev->stats in BPF redirect paths tipc: use kfree_sensitive() for session key material net: ethernet: adi: adin1110: Check return value of devm_gpiod_get_optional() in adin1110_check_spi() net: gro: fix outer network offset drm/mgag200: fix mgag200_bmc_stop_scanout() hwmon: (occ) Mark occ_init_attribute() as __printf ipv6: Fix ECMP sibling count mismatch when clearing RTF_ADDRCONF ASoC: amd: fix memory leak in acp3x pdm dma ops gve: Correct ethtool rx_dropped calculation spi: tegra210-quad: Return IRQ_HANDLED when timeout already processed transfer spi: tegra210-quad: Move curr_xfer read inside spinlock spi: tegra210-quad: Protect curr_xfer assignment in tegra_qspi_setup_transfer_one spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer spi: tegra210-quad: Protect curr_xfer clearing in tegra_qspi_non_combined_seq_xfer spi: tegra: Fix a memory leak in tegra_slink_probe() spi: tegra114: Preserve SPI mode bits in def_command1_reg ALSA: hda/realtek: Really fix headset mic for TongFang X6AR55xU. x86/vmware: Fix hypercall clobbers ALSA: aloop: Fix racy access at PCM trigger PCI/ERR: Ensure error recoverability at all times ublk: fix deadlock when reading partition table md: suspend array while updating raid_disks via sysfs ALSA: hda/realtek: Add quirk for Acer Nitro AN517-55 PCI: qcom: Remove ASPM L0s support for MSM8996 SoC drm/amd/pm: Disable MMIO access during SMU Mode 1 reset HID: logitech: add HID++ support for Logitech MX Anywhere 3S btrfs: reject new transactions if the fs is fully read-only ALSA: hda/realtek: ALC269 fixup for Lenovo Yoga Book 9i 13IRU8 audio net: phy: add phy_interface_weight() net: phy: add phy_interface_copy() net: sfp: pre-parse the module support net: sfp: enhance quirk for Fibrestore 2.5G copper SFP module net: sfp: convert sfp quirks to modify struct sfp_module_support net: sfp: Fix quirk for Ubiquiti U-Fiber Instant SFP module drm/amd/display: fix wrong color value mapping on MCM shaper LUT drm/xe/query: Fix topology query pointer advance ALSA: usb-audio: fix broken logic in snd_audigy2nx_led_update() gpiolib-acpi: Update file references in the Documentation and MAINTAINERS UBUNTU: Upstream stable to v6.6.124, v6.12.70 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147841/+subscriptions
пятница
[Bug 1435210] Re: Ubuntu 15.04: Bad MTRR memory management
** Tags added: kernel-autoclosed kernel-autoclosed-expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1435210 Title: Ubuntu 15.04: Bad MTRR memory management Status in linux package in Ubuntu: Confirmed Bug description: Hello, in order to contribute to quality improvement of the new Ubuntu 15.04, I'm reporting a problem I found in this "beta" version - related to MTRR memory management (mtrr_gran_size/mtrr_chunk_size stuff). If compared with Manjaro XFCE 0.9.0-pre4 edition (systemd, X.org server 1.17.1, kernel 1.19.1), it is quite obvious that there's definitely something wrong with the way how Ubuntu handles 16GB of RAM (inside BIOS, Intel graphics card is set to 256MB). Asus optimus notebook N750JVT-4069H (Intel® Core™ i7-4700HQ; RAM 16GB; Nvidia GeForce GT750M) Manjaro dmesg output: [ 0.000000] DMI: ASUSTeK COMPUTER INC. N750JV/N750JV, BIOS N750JV.210 04/11/2014 [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable [ 0.000000] AGP: No AGP bridge found [ 0.000000] e820: last_pfn = 0x42f200 max_arch_pfn = 0x400000000 [ 0.000000] MTRR default type: uncachable [ 0.000000] MTRR fixed ranges enabled: [ 0.000000] 00000-9FFFF write-back [ 0.000000] A0000-DFFFF uncachable [ 0.000000] E0000-FFFFF write-protect [ 0.000000] MTRR variable ranges enabled: [ 0.000000] 0 base 0000000000 mask 7C00000000 write-back [ 0.000000] 1 base 0400000000 mask 7FE0000000 write-back [ 0.000000] 2 base 0420000000 mask 7FF8000000 write-back [ 0.000000] 3 base 0428000000 mask 7FFC000000 write-back [ 0.000000] 4 base 042C000000 mask 7FFE000000 write-back [ 0.000000] 5 base 042E000000 mask 7FFF000000 write-back [ 0.000000] 6 base 042F000000 mask 7FFFE00000 write-back [ 0.000000] 7 base 00C0000000 mask 7FC0000000 uncachable [ 0.000000] 8 base 00BFC00000 mask 7FFFC00000 uncachable [ 0.000000] 9 disabled [ 0.000000] PAT configuration [0-7]: WB WC UC- UC WB WC UC- UC [ 0.000000] e820: update [mem 0xbfc00000-0xffffffff] usable ==> reserved [ 0.000000] e820: last_pfn = 0xbf000 max_arch_pfn = 0x400000000 [ 0.000000] Scanning 1 areas for low memory corruption Ubuntu dmesg output: [ 0.000000] DMI: ASUSTeK COMPUTER INC. N750JV/N750JV, BIOS N750JV.210 04/11/2014 [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable [ 0.000000] AGP: No AGP bridge found [ 0.000000] e820: last_pfn = 0x42f200 max_arch_pfn = 0x400000000 [ 0.000000] MTRR default type: uncachable [ 0.000000] MTRR fixed ranges enabled: [ 0.000000] 00000-9FFFF write-back [ 0.000000] A0000-DFFFF uncachable [ 0.000000] E0000-FFFFF write-protect [ 0.000000] MTRR variable ranges enabled: [ 0.000000] 0 base 0000000000 mask 7C00000000 write-back [ 0.000000] 1 base 0400000000 mask 7FE0000000 write-back [ 0.000000] 2 base 0420000000 mask 7FF8000000 write-back [ 0.000000] 3 base 0428000000 mask 7FFC000000 write-back [ 0.000000] 4 base 042C000000 mask 7FFE000000 write-back [ 0.000000] 5 base 042E000000 mask 7FFF000000 write-back [ 0.000000] 6 base 042F000000 mask 7FFFE00000 write-back [ 0.000000] 7 base 00C0000000 mask 7FC0000000 uncachable [ 0.000000] 8 base 00BFC00000 mask 7FFFC00000 uncachable [ 0.000000] 9 disabled [ 0.000000] PAT configuration [0-7]: WB WC UC- UC WB WC UC- UC [ 0.000000] original variable MTRRs [ 0.000000] reg 0, base: 0GB, range: 16GB, type WB [ 0.000000] reg 1, base: 16GB, range: 512MB, type WB [ 0.000000] reg 2, base: 16896MB, range: 128MB, type WB [ 0.000000] reg 3, base: 17024MB, range: 64MB, type WB [ 0.000000] reg 4, base: 17088MB, range: 32MB, type WB [ 0.000000] reg 5, base: 17120MB, range: 16MB, type WB [ 0.000000] reg 6, base: 17136MB, range: 2MB, type WB [ 0.000000] reg 7, base: 3GB, range: 1GB, type UC [ 0.000000] reg 8, base: 3068MB, range: 4MB, type UC [ 0.000000] total RAM covered: 16110M [ 0.000000] gran_size: 64K chunk_size: 64K num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 64K chunk_size: 128K num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 64K chunk_size: 256K num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 64K chunk_size: 512K num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 64K chunk_size: 1M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 64K chunk_size: 2M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 64K chunk_size: 4M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 64K chunk_size: 8M num_reg: 10 lose cover RAM: 2M [ 0.000000] gran_size: 64K chunk_size: 16M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 64K chunk_size: 64M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 64K chunk_size: 128M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 64K chunk_size: 256M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 64K chunk_size: 512M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 64K chunk_size: 1G num_reg: 10 lose cover RAM: 0G [ 0.000000] *BAD*gran_size: 64K chunk_size: 2G num_reg: 10 lose cover RAM: -1G [ 0.000000] gran_size: 128K chunk_size: 128K num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 128K chunk_size: 256K num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 128K chunk_size: 512K num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 128K chunk_size: 1M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 128K chunk_size: 2M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 128K chunk_size: 4M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 128K chunk_size: 8M num_reg: 10 lose cover RAM: 2M [ 0.000000] gran_size: 128K chunk_size: 16M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 128K chunk_size: 32M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 128K chunk_size: 64M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 128K chunk_size: 128M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 128K chunk_size: 256M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 128K chunk_size: 512M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 128K chunk_size: 1G num_reg: 10 lose cover RAM: 0G [ 0.000000] *BAD*gran_size: 128K chunk_size: 2G num_reg: 10 lose cover RAM: -1G [ 0.000000] gran_size: 256K chunk_size: 256K num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 256K chunk_size: 512K num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 256K chunk_size: 1M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 256K chunk_size: 2M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 256K chunk_size: 4M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 256K chunk_size: 8M num_reg: 10 lose cover RAM: 2M [ 0.000000] gran_size: 256K chunk_size: 16M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 256K chunk_size: 32M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 256K chunk_size: 64M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 256K chunk_size: 128M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 256K chunk_size: 256M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 256K chunk_size: 512M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 256K chunk_size: 1G num_reg: 10 lose cover RAM: 0G [ 0.000000] *BAD*gran_size: 256K chunk_size: 2G num_reg: 10 lose cover RAM: -1G [ 0.000000] gran_size: 512K chunk_size: 512K num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 512K chunk_size: 1M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 512K chunk_size: 2M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 512K chunk_size: 4M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 512K chunk_size: 8M num_reg: 10 lose cover RAM: 2M [ 0.000000] gran_size: 512K chunk_size: 16M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 512K chunk_size: 32M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 512K chunk_size: 64M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 512K chunk_size: 128M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 512K chunk_size: 256M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 512K chunk_size: 512M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 512K chunk_size: 1G num_reg: 10 lose cover RAM: 0G [ 0.000000] *BAD*gran_size: 512K chunk_size: 2G num_reg: 10 lose cover RAM: -1G [ 0.000000] gran_size: 1M chunk_size: 1M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 1M chunk_size: 2M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 1M chunk_size: 4M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 1M chunk_size: 8M num_reg: 10 lose cover RAM: 2M [ 0.000000] gran_size: 1M chunk_size: 16M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 1M chunk_size: 32M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 1M chunk_size: 64M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 1M chunk_size: 128M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 1M chunk_size: 256M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 1M chunk_size: 512M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 1M chunk_size: 1G num_reg: 10 lose cover RAM: 0G [ 0.000000] *BAD*gran_size: 1M chunk_size: 2G num_reg: 10 lose cover RAM: -1G [ 0.000000] gran_size: 2M chunk_size: 2M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 2M chunk_size: 4M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 2M chunk_size: 8M num_reg: 10 lose cover RAM: 2M [ 0.000000] gran_size: 2M chunk_size: 16M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 2M chunk_size: 32M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 2M chunk_size: 64M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 2M chunk_size: 128M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 2M chunk_size: 256M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 2M chunk_size: 512M num_reg: 10 lose cover RAM: 0G [ 0.000000] gran_size: 2M chunk_size: 1G num_reg: 10 lose cover RAM: 0G [ 0.000000] *BAD*gran_size: 2M chunk_size: 2G num_reg: 10 lose cover RAM: -1G [ 0.000000] gran_size: 4M chunk_size: 4M num_reg: 10 lose cover RAM: 8946M [ 0.000000] gran_size: 4M chunk_size: 8M num_reg: 10 lose cover RAM: 2M [ 0.000000] gran_size: 4M chunk_size: 16M num_reg: 10 lose cover RAM: 2M [ 0.000000] gran_size: 4M chunk_size: 32M num_reg: 8 lose cover RAM: 2M [ 0.000000] gran_size: 4M chunk_size: 64M num_reg: 8 lose cover RAM: 2M [ 0.000000] gran_size: 4M chunk_size: 128M num_reg: 8 lose cover RAM: 2M [ 0.000000] gran_size: 4M chunk_size: 256M num_reg: 8 lose cover RAM: 2M [ 0.000000] gran_size: 4M chunk_size: 512M num_reg: 8 lose cover RAM: 2M [ 0.000000] gran_size: 4M chunk_size: 1G num_reg: 8 lose cover RAM: 2M [ 0.000000] gran_size: 4M chunk_size: 2G num_reg: 9 lose cover RAM: 2M [ 0.000000] gran_size: 8M chunk_size: 8M num_reg: 10 lose cover RAM: 758M [ 0.000000] gran_size: 8M chunk_size: 16M num_reg: 10 lose cover RAM: 6M [ 0.000000] gran_size: 8M chunk_size: 32M num_reg: 8 lose cover RAM: 6M [ 0.000000] gran_size: 8M chunk_size: 64M num_reg: 8 lose cover RAM: 6M [ 0.000000] gran_size: 8M chunk_size: 128M num_reg: 8 lose cover RAM: 6M [ 0.000000] gran_size: 8M chunk_size: 256M num_reg: 8 lose cover RAM: 6M [ 0.000000] gran_size: 8M chunk_size: 512M num_reg: 8 lose cover RAM: 6M [ 0.000000] gran_size: 8M chunk_size: 1G num_reg: 8 lose cover RAM: 6M [ 0.000000] gran_size: 8M chunk_size: 2G num_reg: 9 lose cover RAM: 6M [ 0.000000] gran_size: 16M chunk_size: 16M num_reg: 10 lose cover RAM: 254M [ 0.000000] gran_size: 16M chunk_size: 32M num_reg: 8 lose cover RAM: 14M [ 0.000000] gran_size: 16M chunk_size: 64M num_reg: 8 lose cover RAM: 14M [ 0.000000] gran_size: 16M chunk_size: 128M num_reg: 8 lose cover RAM: 14M [ 0.000000] gran_size: 16M chunk_size: 256M num_reg: 8 lose cover RAM: 14M [ 0.000000] gran_size: 16M chunk_size: 512M num_reg: 8 lose cover RAM: 14M [ 0.000000] gran_size: 16M chunk_size: 1G num_reg: 8 lose cover RAM: 14M [ 0.000000] gran_size: 16M chunk_size: 2G num_reg: 9 lose cover RAM: 14M [ 0.000000] gran_size: 32M chunk_size: 32M num_reg: 10 lose cover RAM: 142M [ 0.000000] gran_size: 32M chunk_size: 64M num_reg: 8 lose cover RAM: 46M [ 0.000000] gran_size: 32M chunk_size: 128M num_reg: 8 lose cover RAM: 46M [ 0.000000] gran_size: 32M chunk_size: 256M num_reg: 8 lose cover RAM: 46M [ 0.000000] gran_size: 32M chunk_size: 512M num_reg: 8 lose cover RAM: 46M [ 0.000000] gran_size: 32M chunk_size: 1G num_reg: 8 lose cover RAM: 46M [ 0.000000] gran_size: 32M chunk_size: 2G num_reg: 9 lose cover RAM: 46M [ 0.000000] gran_size: 64M chunk_size: 64M num_reg: 10 lose cover RAM: 110M [ 0.000000] gran_size: 64M chunk_size: 128M num_reg: 8 lose cover RAM: 110M [ 0.000000] gran_size: 64M chunk_size: 256M num_reg: 8 lose cover RAM: 110M [ 0.000000] gran_size: 64M chunk_size: 512M num_reg: 8 lose cover RAM: 110M [ 0.000000] gran_size: 64M chunk_size: 1G num_reg: 8 lose cover RAM: 110M [ 0.000000] gran_size: 64M chunk_size: 2G num_reg: 9 lose cover RAM: 110M [ 0.000000] gran_size: 128M chunk_size: 128M num_reg: 8 lose cover RAM: 238M [ 0.000000] gran_size: 128M chunk_size: 256M num_reg: 8 lose cover RAM: 238M [ 0.000000] gran_size: 128M chunk_size: 512M num_reg: 8 lose cover RAM: 238M [ 0.000000] gran_size: 128M chunk_size: 1G num_reg: 8 lose cover RAM: 238M [ 0.000000] gran_size: 128M chunk_size: 2G num_reg: 9 lose cover RAM: 238M [ 0.000000] gran_size: 256M chunk_size: 256M num_reg: 6 lose cover RAM: 494M [ 0.000000] gran_size: 256M chunk_size: 512M num_reg: 6 lose cover RAM: 494M [ 0.000000] gran_size: 256M chunk_size: 1G num_reg: 7 lose cover RAM: 494M [ 0.000000] gran_size: 256M chunk_size: 2G num_reg: 8 lose cover RAM: 494M [ 0.000000] gran_size: 512M chunk_size: 512M num_reg: 5 lose cover RAM: 750M [ 0.000000] gran_size: 512M chunk_size: 1G num_reg: 7 lose cover RAM: 750M [ 0.000000] gran_size: 512M chunk_size: 2G num_reg: 8 lose cover RAM: 750M [ 0.000000] gran_size: 1G chunk_size: 1G num_reg: 3 lose cover RAM: 1774M [ 0.000000] gran_size: 1G chunk_size: 2G num_reg: 3 lose cover RAM: 1774M [ 0.000000] gran_size: 2G chunk_size: 2G num_reg: 3 lose cover RAM: 1774M [ 0.000000] mtrr_cleanup: can not find optimal value [ 0.000000] please specify mtrr_gran_size/mtrr_chunk_size [ 0.000000] e820: update [mem 0xbfc00000-0xffffffff] usable ==> reserved [ 0.000000] e820: last_pfn = 0xbf000 max_arch_pfn = 0x400000000 [ 0.000000] Scanning 1 areas for low memory corruption ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-9-generic 3.19.0-9.9 [modified: boot/vmlinuz-3.19.0-9-generic] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: aljosa 1824 F.... pulseaudio /dev/snd/controlC0: aljosa 1824 F.... pulseaudio CurrentDesktop: Unity Date: Mon Mar 23 09:52:24 2015 HibernationDevice: RESUME=UUID=df42f272-c519-4323-977d-bb1fe697e7f0 InstallationDate: Installed on 2015-03-19 (3 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150318) MachineType: ASUSTeK COMPUTER INC. N750JV ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic.efi.signed root=UUID=da571e57-f1af-49b1-95ba-206e95c86cec ro quiet splash ipv6.disable=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-9-generic N/A linux-backports-modules-3.19.0-9-generic N/A linux-firmware 1.143 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N750JV.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N750JV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN750JV.210:bd04/11/2014:svnASUSTeKCOMPUTERINC.:pnN750JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN750JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N750JV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1435210/+subscriptions
[Bug 1118447] Re: Race condition with network and NFS mounts causes boottime hang
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Confirmed => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1118447 Title: Race condition with network and NFS mounts causes boottime hang Status in linux package in Ubuntu: Expired Status in nfs-utils package in Ubuntu: Incomplete Bug description: I seem to experience a race condition during boot of my ubuntu 12.04 server: In approx. one of seven boots, the server hangs during bootup. This is what I see on the screen: After the line * Starting configure network device there is a short delay of about 1 second, then messages continue. I see * Starting Mount network filesystems [ OK ] * Starting set sysctls from /etc/sysctl.conf [ OK ] * Starting configure network device [ OK ] * Stopping Mount network filesystems [ OK ] * Stopping set sysctls from /etc/sysctl.conf [ OK ] * Starting Block the mounting event for NFS filesytems until statd is running [ OK ] * Stopping Block the mounting event for NFS filesytems until statd is running [ OK ] * Starting Block the mounting event for NFS filesytems until statd is running [ OK ] * Stopping Block the mounting event for NFS filesytems until statd is running [ OK ] The last messages repeats several times, and then the boot process hangs. In 6/7 of cases, I wait for a minute, and after that bootup continues. But in approx 1/7 cases, the system hangs at this point forever. The machine does not respond to CTRL-ALT-DEL, I have to reboot it using SysRq-Keys. WORKAROUND: Setting the NFS entries in fstab to "noauto" completely removes the problem: There is no timeout during boot, and no lockup any more. The machine boote smoothly with the NFS-shares unmounted. After the machine is up, we can manually mount the NFS-shares without a problem. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-37-generic 3.2.0-37.58 ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: aplay: device_list:252: keine Soundkarten gefunden ... ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: arecord: device_list:252: keine Soundkarten gefunden ... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 85.200104] lxcbr0: no IPv6 routers present Date: Thu Feb 7 15:50:40 2013 HibernationDevice: RESUME=UUID=6c172536-57cc-4deb-867a-0718d572f23e IwConfig: lo no wireless extensions. eth0 no wireless extensions. lxcbr0 no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. MarkForUpload: True ProcEnviron: LANGUAGE=de:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic root=/dev/mapper/lvmvg-root ro debug splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Es läuft kein PulseAudio-Dienst oder nicht als Sessiondienst. RelatedPackageVersions: linux-restricted-modules-3.2.0-37-generic N/A linux-backports-modules-3.2.0-37-generic N/A linux-firmware 1.79.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to precise on 2012-04-28 (285 days ago) dmi.bios.date: 07/04/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd07/04/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1118447/+subscriptions