[Kernel-packages] [Bug 1822797] Re: ZFS module is installed for wrong kernel on arm64-raspi3 systems (19.04 beta)
I have had good experience with running ZFS on rpi3 using other distros. Of course it would be a complete craziness to use zfs in a desktop setup with just 1Gb of RAM. For what rpi is actually meant, 1Gb is plenty enough to run ZFS especially if the ARC size is set to a smaller value. This is why I hope this problem would get fixed, so I am able to use Ubuntu on all platforms. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1822797 Title: ZFS module is installed for wrong kernel on arm64-raspi3 systems (19.04 beta) Status in linux-raspi2 package in Ubuntu: Triaged Bug description: Platform: Raspberry Pi 3 running ubuntu-19.04-beta-preinstalled- server-arm64+raspi3.img Kernel: Default (Linux ubuntu 4.18.0-1010-raspi2 #12-Ubuntu SMP PREEMPT Tue Feb 12 12:17:11 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux) Problem: The ZFS module is installed for a kernel that can not be used. apt-get install zfs-initramfs Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvpair1linux libuutil1linux libzfs2linux libzpool2linux linux-image-unsigned-5.0.0-8-snapdragon linux-modules-5.0.0-8-snapdragon zfs-zed zfsutils-linux Suggested packages: fdutils linux-doc-5.0.0 | linux-source-5.0.0 linux-tools linux-headers-5.0.0-8-snapdragon nfs-kernel-server samba-common-bin The following NEW packages will be installed: libnvpair1linux libuutil1linux libzfs2linux libzpool2linux linux-image-unsigned-5.0.0-8-snapdragon linux-modules-5.0.0-8-snapdragon zfs-initramfs zfs-zed zfsutils-linux 0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 55.7 MB of archives. After this operation, 305 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 linux-modules-5.0.0-8-snapdragon arm64 5.0.0-8.9 [47.5 MB] Get:2 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 linux-image-unsigned-5.0.0-8-snapdragon arm64 5.0.0-8.9 [7169 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libnvpair1linux arm64 0.7.12-1ubuntu5 [42.8 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libuutil1linux arm64 0.7.12-1ubuntu5 [50.7 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libzpool2linux arm64 0.7.12-1ubuntu5 [498 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libzfs2linux arm64 0.7.12-1ubuntu5 [121 kB] Get:7 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfsutils-linux arm64 0.7.12-1ubuntu5 [267 kB] Get:8 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfs-initramfs arm64 0.7.12-1ubuntu5 [22.2 kB] Get:9 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfs-zed arm64 0.7.12-1ubuntu5 [57.5 kB] Fetched 55.7 MB in 37s (1486 kB/s) Selecting previously unselected package linux-modules-5.0.0-8-snapdragon. (Reading database ... 61671 files and directories currently installed.) Preparing to unpack .../0-linux-modules-5.0.0-8-snapdragon_5.0.0-8.9_arm64.deb ... Unpacking linux-modules-5.0.0-8-snapdragon (5.0.0-8.9) ... Selecting previously unselected package linux-image-unsigned-5.0.0-8-snapdragon. Preparing to unpack .../1-linux-image-unsigned-5.0.0-8-snapdragon_5.0.0-8.9_arm64.deb ... Unpacking linux-image-unsigned-5.0.0-8-snapdragon (5.0.0-8.9) ... Selecting previously unselected package libnvpair1linux. Preparing to unpack .../2-libnvpair1linux_0.7.12-1ubuntu5_arm64.deb ... Unpacking libnvpair1linux (0.7.12-1ubuntu5) ... Selecting previously unselected package libuutil1linux. Preparing to unpack .../3-libuutil1linux_0.7.12-1ubuntu5_arm64.deb ... Unpacking libuutil1linux (0.7.12-1ubuntu5) ... Selecting previously unselected package libzpool2linux. Preparing to unpack .../4-libzpool2linux_0.7.12-1ubuntu5_arm64.deb ... Unpacking libzpool2linux (0.7.12-1ubuntu5) ... Selecting previously unselected package libzfs2linux. Preparing to unpack .../5-libzfs2linux_0.7.12-1ubuntu5_arm64.deb ... Unpacking libzfs2linux (0.7.12-1ubuntu5) ... Selecting previously unselected package zfsutils-linux. Preparing to unpack .../6-zfsutils-linux_0.7.12-1ubuntu5_arm64.deb ... Unpacking zfsutils-linux (0.7.12-1ubuntu5) ... Selecting previously unselected package zfs-initramfs. Preparing to unpack .../7-zfs-initramfs_0.7.12-1ubuntu5_arm64.deb ... Unpacking zfs-initramfs (0.7.12-1ubuntu5) ... Selecting previously unselected package zfs-zed. Preparing to unpack .../8-zfs-zed_0.7.12-1ubuntu5_arm64.deb ... Unpacking zfs-zed (0.7.12-1ubuntu5) ... Setting up libuutil1linux (0.7.12-1ubuntu5) ... Setting up linux-modules-5.0.0-8-snapdragon (5.0.0-8.9) ... Setting up
[Kernel-packages] [Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
No, I do not have the possibility to test this as the server is in production now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hardware: HPE ProLiant DL360 gen9 Ubuntu Version: 18.04 Problem: When rebooting the server, everything goes well (shutting down services, unmounting etc) until the last step where it reads "Starting Reboot". At this point the system is getting stuck and nothing else can can be done than holding the power button in for a long enough time to turn it off. At the same time as the system get stuck, a red error light is lightening up on the server. This light is green until it reaches this "Starting Reboot" stage. The same happens if the server is shutdown, with the difference that the last message is "Starting Power-Off" instead of "Starting Reboot". The server is installed with a new clean 18.04 installation. This server was rebooting/shutting down without a problem with all releases between 16.04 and 17.10. This problem is serious as it prevents remote reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 13 11:16 seq crw-rw 1 root audio 116, 33 Jun 13 11:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/21/2018 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
I have this problem with Intel Xeon CPU E5-2620 v4. I do not think it is CPU related. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hardware: HPE ProLiant DL360 gen9 Ubuntu Version: 18.04 Problem: When rebooting the server, everything goes well (shutting down services, unmounting etc) until the last step where it reads "Starting Reboot". At this point the system is getting stuck and nothing else can can be done than holding the power button in for a long enough time to turn it off. At the same time as the system get stuck, a red error light is lightening up on the server. This light is green until it reaches this "Starting Reboot" stage. The same happens if the server is shutdown, with the difference that the last message is "Starting Power-Off" instead of "Starting Reboot". The server is installed with a new clean 18.04 installation. This server was rebooting/shutting down without a problem with all releases between 16.04 and 17.10. This problem is serious as it prevents remote reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 13 11:16 seq crw-rw 1 root audio 116, 33 Jun 13 11:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/21/2018 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
This installation is running from a ZFS root. Would upgrading the kernel to mainline cause the zfs module to not work? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Hardware: HPE ProLiant DL360 gen9 Ubuntu Version: 18.04 Problem: When rebooting the server, everything goes well (shutting down services, unmounting etc) until the last step where it reads "Starting Reboot". At this point the system is getting stuck and nothing else can can be done than holding the power button in for a long enough time to turn it off. At the same time as the system get stuck, a red error light is lightening up on the server. This light is green until it reaches this "Starting Reboot" stage. The same happens if the server is shutdown, with the difference that the last message is "Starting Power-Off" instead of "Starting Reboot". The server is installed with a new clean 18.04 installation. This server was rebooting/shutting down without a problem with all releases between 16.04 and 17.10. This problem is serious as it prevents remote reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 13 11:16 seq crw-rw 1 root audio 116, 33 Jun 13 11:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/21/2018 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
** Tags added: apport-collected ** Description changed: Hardware: HPE ProLiant DL360 gen9 Ubuntu Version: 18.04 Problem: When rebooting the server, everything goes well (shutting down services, unmounting etc) until the last step where it reads "Starting Reboot". At this point the system is getting stuck and nothing else can can be done than holding the power button in for a long enough time to turn it off. At the same time as the system get stuck, a red error light is lightening up on the server. This light is green until it reaches this "Starting Reboot" stage. The same happens if the server is shutdown, with the difference that the last message is "Starting Power- Off" instead of "Starting Reboot". The server is installed with a new clean 18.04 installation. This server was rebooting/shutting down without a problem with all releases between 16.04 and 17.10. This problem is serious as it prevents remote reboot. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jun 13 11:16 seq + crw-rw 1 root audio 116, 33 Jun 13 11:16 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=none + MachineType: HP ProLiant DL360 Gen9 + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 mgadrmfb + ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro + ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-23-generic N/A + linux-backports-modules-4.15.0-23-generic N/A + linux-firmware 1.173.1 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic + Uname: Linux 4.15.0-23-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 05/21/2018 + dmi.bios.vendor: HP + dmi.bios.version: P89 + dmi.board.name: ProLiant DL360 Gen9 + dmi.board.vendor: HP + dmi.chassis.type: 23 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: + dmi.product.family: ProLiant + dmi.product.name: ProLiant DL360 Gen9 + dmi.sys.vendor: HP ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" Status in linux package in Ubuntu: Confirmed Bug description: Hardware: HPE ProLiant DL360 gen9 Ubuntu Version: 18.04 Problem: When rebooting the server, everything goes well (shutting down services, unmounting etc) until the last step where it reads "Starting Reboot". At this point the system is getting stuck and nothing else can can be done than holding the power button in for a long enough time to turn it off. At the same time as the system get stuck, a red error light is lightening up on the server. This light is green until it reaches this "Starting Reboot" stage. The same happens if the server is shutdown, with the difference that the last message is "Starting Power-Off" instead of "Starting Reboot". The server is installed with a new clean 18.04 installation. This server was rebooting/shutting down without a problem with all releases between 16.04 and 17.10. This problem is serious as it prevents remote reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 13 11:16 seq crw-rw 1 root audio 116, 33 Jun 13 11:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic
[Kernel-packages] [Bug 1765048] Re: bionic: LINUX_VERSION_CODE incorrect?
I see. Thank you for replying. ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765048 Title: bionic: LINUX_VERSION_CODE incorrect? Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: In linux/version.h there is a LINUX_VERSION_CODE define. Issue: According to the Keepalived developer(s), the define set in version 4.15.0-15.16, encoded value 265999, is incorrect. Instead of 4.15.0, it reflects 4.15.15. Seen on bionic. See https://github.com/acassen/keepalived/issues/838 , their comments copied here: "Converting 265999 to hex gives 0x40F0F, which means kernel version 4.15.15. This looks like linux/version.h is being incorrectly constructed, or there is a mismatch between the running kernel and the kernel header files." and "The #define LINUX_VERSION_CODE 265999 statement says that the headers are for Linux version 4.15.15, so keepalived is correctly reporting what is in linux/version.h header file. This issue probably needs to be reported to Ubuntu since it looks like the header file they are distributing is incorrect." root@hostname:~/keepalived# dpkg -l | grep linux-headers ii linux-headers-4.13.0-364.13.0-36.40 all Header files related to Linux kernel version 4.13.0 ii linux-headers-4.13.0-36-generic4.13.0-36.40 amd64Linux kernel headers for version 4.13.0 on 64 bit x86 SMP ii linux-headers-4.13.0-384.13.0-38.43 all Header files related to Linux kernel version 4.13.0 ii linux-headers-4.13.0-38-generic4.13.0-38.43 amd64Linux kernel headers for version 4.13.0 on 64 bit x86 SMP ii linux-headers-4.15.0-154.15.0-15.16 all Header files related to Linux kernel version 4.15.0 ii linux-headers-4.15.0-15-generic4.15.0-15.16 amd64Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-generic 4.15.0.15.16 amd64Generic Linux kernel headers root@hostname:~/keepalived# root@hostname:~/keepalived# dpkg -S /usr/include/linux/version.h linux-libc-dev:amd64: /usr/include/linux/version.h root@hostname:~/keepalived# dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 4.15.0-15.16 root@hostname:~# grep LINUX_VERSION_CODE /usr/include/linux/version.h #define LINUX_VERSION_CODE 265999 # uname -a Linux hostname 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Can you please advise if this is the case? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765048] Re: bionic: LINUX_VERSION_CODE incorrect?
No apport because not a crash bug. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765048 Title: bionic: LINUX_VERSION_CODE incorrect? Status in linux package in Ubuntu: Confirmed Bug description: In linux/version.h there is a LINUX_VERSION_CODE define. Issue: According to the Keepalived developer(s), the define set in version 4.15.0-15.16, encoded value 265999, is incorrect. Instead of 4.15.0, it reflects 4.15.15. Seen on bionic. See https://github.com/acassen/keepalived/issues/838 , their comments copied here: "Converting 265999 to hex gives 0x40F0F, which means kernel version 4.15.15. This looks like linux/version.h is being incorrectly constructed, or there is a mismatch between the running kernel and the kernel header files." and "The #define LINUX_VERSION_CODE 265999 statement says that the headers are for Linux version 4.15.15, so keepalived is correctly reporting what is in linux/version.h header file. This issue probably needs to be reported to Ubuntu since it looks like the header file they are distributing is incorrect." root@hostname:~/keepalived# dpkg -l | grep linux-headers ii linux-headers-4.13.0-364.13.0-36.40 all Header files related to Linux kernel version 4.13.0 ii linux-headers-4.13.0-36-generic4.13.0-36.40 amd64Linux kernel headers for version 4.13.0 on 64 bit x86 SMP ii linux-headers-4.13.0-384.13.0-38.43 all Header files related to Linux kernel version 4.13.0 ii linux-headers-4.13.0-38-generic4.13.0-38.43 amd64Linux kernel headers for version 4.13.0 on 64 bit x86 SMP ii linux-headers-4.15.0-154.15.0-15.16 all Header files related to Linux kernel version 4.15.0 ii linux-headers-4.15.0-15-generic4.15.0-15.16 amd64Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-generic 4.15.0.15.16 amd64Generic Linux kernel headers root@hostname:~/keepalived# root@hostname:~/keepalived# dpkg -S /usr/include/linux/version.h linux-libc-dev:amd64: /usr/include/linux/version.h root@hostname:~/keepalived# dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 4.15.0-15.16 root@hostname:~# grep LINUX_VERSION_CODE /usr/include/linux/version.h #define LINUX_VERSION_CODE 265999 # uname -a Linux hostname 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Can you please advise if this is the case? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765048] [NEW] bionic: LINUX_VERSION_CODE incorrect?
Public bug reported: In linux/version.h there is a LINUX_VERSION_CODE define. Issue: According to the Keepalived developer(s), the define set in version 4.15.0-15.16, encoded value 265999, is incorrect. Instead of 4.15.0, it reflects 4.15.15. Seen on bionic. See https://github.com/acassen/keepalived/issues/838 , their comments copied here: "Converting 265999 to hex gives 0x40F0F, which means kernel version 4.15.15. This looks like linux/version.h is being incorrectly constructed, or there is a mismatch between the running kernel and the kernel header files." and "The #define LINUX_VERSION_CODE 265999 statement says that the headers are for Linux version 4.15.15, so keepalived is correctly reporting what is in linux/version.h header file. This issue probably needs to be reported to Ubuntu since it looks like the header file they are distributing is incorrect." root@hostname:~/keepalived# dpkg -l | grep linux-headers ii linux-headers-4.13.0-364.13.0-36.40 all Header files related to Linux kernel version 4.13.0 ii linux-headers-4.13.0-36-generic4.13.0-36.40 amd64Linux kernel headers for version 4.13.0 on 64 bit x86 SMP ii linux-headers-4.13.0-384.13.0-38.43 all Header files related to Linux kernel version 4.13.0 ii linux-headers-4.13.0-38-generic4.13.0-38.43 amd64Linux kernel headers for version 4.13.0 on 64 bit x86 SMP ii linux-headers-4.15.0-154.15.0-15.16 all Header files related to Linux kernel version 4.15.0 ii linux-headers-4.15.0-15-generic4.15.0-15.16 amd64Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-generic 4.15.0.15.16 amd64Generic Linux kernel headers root@hostname:~/keepalived# root@hostname:~/keepalived# dpkg -S /usr/include/linux/version.h linux-libc-dev:amd64: /usr/include/linux/version.h root@hostname:~/keepalived# dpkg -l | grep linux-libc-dev ii linux-libc-dev:amd64 4.15.0-15.16 root@hostname:~# grep LINUX_VERSION_CODE /usr/include/linux/version.h #define LINUX_VERSION_CODE 265999 # uname -a Linux hostname 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Can you please advise if this is the case? Thanks in advance. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: artful ** Description changed: In linux/version.h there is a LINUX_VERSION_CODE define. Issue: According to the Keepalived developer(s), the define set in version 4.15.0-15.16, encoded value 265999, is incorrect. Instead of - 4.15.0, it reflects 4.15.15. + 4.15.0, it reflects 4.15.15. Seen on bionic. See https://github.com/acassen/keepalived/issues/838 , their comments copied here: "Converting 265999 to hex gives 0x40F0F, which means kernel version 4.15.15. This looks like linux/version.h is being incorrectly constructed, or there is a mismatch between the running kernel and the kernel header files." and "The #define LINUX_VERSION_CODE 265999 statement says that the headers are for Linux version 4.15.15, so keepalived is correctly reporting what is in linux/version.h header file. This issue probably needs to be reported to Ubuntu since it looks like the header file they are distributing is incorrect." - root@hostname:~/keepalived# dpkg -l | grep linux-headers ii linux-headers-4.13.0-364.13.0-36.40 all Header files related to Linux kernel version 4.13.0 ii linux-headers-4.13.0-36-generic4.13.0-36.40 amd64Linux kernel headers for version 4.13.0 on 64 bit x86 SMP ii linux-headers-4.13.0-384.13.0-38.43 all Header files related to Linux kernel version 4.13.0 ii linux-headers-4.13.0-38-generic4.13.0-38.43 amd64Linux kernel headers for version 4.13.0 on 64 bit x86 SMP ii linux-headers-4.15.0-154.15.0-15.16 all Header files related to Linux kernel version 4.15.0 ii linux-headers-4.15.0-15-generic4.15.0-15.16 amd64Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-generic 4.15.0.15.16 amd64Generic Linux kernel headers root@hostname:~/keepalived# root@hostname:~/keepalived# dpkg -S /usr/include/linux/version.h linux-libc-dev:amd64: /usr/include/linux/version.h
[Kernel-packages] [Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d
FWIW, m3.large is also affected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573231 Title: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do- release-upgrade -d Status in linux package in Ubuntu: Confirmed Bug description: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=8ea401db-b84b-4cd6-a628-d72f30bbf1e5 ro console=tty1 console=ttyS0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers' [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] x86/fpu: Using 'eager' FPU context switches. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xefff] usable [0.00] BIOS-e820: [mem 0xfc00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x0001efff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.4 present. [0.00] Hypervisor detected: Xen [0.00] Xen version 4.2. [0.00] Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs. [0.00] Blkfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated disks. [0.00] You might have to change the root device [0.00] from /dev/hd[a-d] to /dev/xvd[a-d] [0.00] in your root= kernel command line option [0.00] e820: last_pfn = 0x1f max_arch_pfn = 0x4 [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT [0.00] e820: last_pfn = 0xf max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000fbba0-0x000fbbaf] mapped at [880fbba0] [0.00] Scanning 1 areas for low memory corruption [0.00] RAMDISK: [mem 0x3407e000-0x36036fff] [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen ) [0.00] ACPI: XSDT 0xFC00F5A0 54 (v01 XenHVM HVML ) [0.00] ACPI: FACP 0xFC00F260 F4 (v04 XenHVM HVML ) [0.00] ACPI: DSDT 0xFC0035E0 00BBF6 (v02 XenHVM INTL 20090123) [0.00] ACPI: FACS 0xFC0035A0 40 [0.00] ACPI: FACS 0xFC0035A0 40 [0.00] ACPI: APIC 0xFC00F360 D8 (v02 XenHVM HVML ) [0.00] ACPI: HPET 0xFC00F4B0 38 (v01 XenHVM HVML ) [0.00] ACPI: WAET 0xFC00F4F0 28 (v01 XenHVM HVML ) [0.00] ACPI: SSDT 0xFC00F520 31 (v02 XenHVM INTL 20090123) [0.00] ACPI: SSDT 0xFC00F560 31 (v02 XenHVM INTL 20090123) [0.00] No NUMA configuration found [0.00] Faking a node at [mem 0x-0x0001efff] [0.00] NODE_DATA(0) allocated [mem 0x1efff7000-0x1efffbfff] [0.00] Zone ranges: [0.00] DMA [mem 0x1000-0x00ff] [0.00] DMA32[mem 0x0100-0x] [0.00] Normal [mem 0x0001-0x0001efff] [0.00] Device empty [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x1000-0x0009dfff] [0.00] node 0: [mem 0x0010-0xefff] [0.00] node 0: [mem 0x0001-0x0001efff] [0.00] Initmem setup node 0 [mem 0x1000-0x0001efff] [0.00] ACPI: PM-Timer IO Port: 0xb008 [
[Kernel-packages] [Bug 1233110] Re: Black screen with blinking cursor and moveable mouse cursor after latest kernel upgrade
I tested the mainline kernel as requested and the bug still exists. ** Tags added: kernel-bug-exists-upstream ** Description changed: - I updated ubuntu sep 30. + I updated ubuntu sep 30. Among other updates was kernel 3.8.0-31.46 After updating and rebooting I get grub, select ubuntu as always, then instead of going to the unity-greeter login screen I just get a black screen with a blinking cursor in the top left and a mouse cursor i can move around. If I press CTRL-ALT-F1 and login i can write “sudo service lightdm --full-restart and then I get login screen and everything is normal. If I use the previous kernel 3.8.0-30 everything works like normal. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-30-generic 3.8.0-30.44 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: laeb 2134 F pulseaudio - /dev/snd/controlC1: laeb 2134 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: laeb 2134 F pulseaudio + /dev/snd/controlC1: laeb 2134 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 30 13:16:19 2013 HibernationDevice: RESUME=UUID=e9e3c42a-9205-4ad8-b97f-fd890621a694 InstallationDate: Installed on 2013-08-29 (31 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IwConfig: - eth0 no wireless extensions. - - lono wireless extensions. + eth0 no wireless extensions. + + lono wireless extensions. MachineType: Dell Inc. OptiPlex 9010 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic root=UUID=10c2ca64-ed49-4e2d-9e2f-e6fd226b23f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.8.0-30-generic N/A - linux-backports-modules-3.8.0-30-generic N/A - linux-firmware1.106 + linux-restricted-modules-3.8.0-30-generic N/A + linux-backports-modules-3.8.0-30-generic N/A + linux-firmware1.106 RfKill: - + SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 00F82W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd06/11/2013:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn00F82W:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1233110 Title: Black screen with blinking cursor and moveable mouse cursor after latest kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I updated ubuntu sep 30. Among other updates was kernel 3.8.0-31.46 After updating and rebooting I get grub, select ubuntu as always, then instead of going to the unity-greeter login screen I just get a black screen with a blinking cursor in the top left and a mouse cursor i can move around. If I press CTRL-ALT-F1 and login i can write “sudo service lightdm --full-restart and then I get login screen and everything is normal. If I use the previous kernel 3.8.0-30 everything works like normal. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-30-generic 3.8.0-30.44 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laeb 2134 F pulseaudio /dev/snd/controlC1: laeb 2134 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 30 13:16:19 2013 HibernationDevice: RESUME=UUID=e9e3c42a-9205-4ad8-b97f-fd890621a694 InstallationDate: Installed on 2013-08-29 (31 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 9010 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic root=UUID=10c2ca64-ed49-4e2d-9e2f-e6fd226b23f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-30-generic N/A linux-backports-modules-3.8.0-30-generic N/A linux-firmware1.106 RfKill:
[Kernel-packages] [Bug 1233110] [NEW] Black screen with blinking cursor and moveable mouse cursor after latest kernel upgrade
Public bug reported: I updated ubuntu sep 30. Among other updates was kernel 3.8.0-31.46 After updating and rebooting I get grub, select ubuntu as always, then instead of going to the unity-greeter login screen I just get a black screen with a blinking cursor in the top left and a mouse cursor i can move around. If I press CTRL-ALT-F1 and login i can write “sudo service lightdm --full-restart and then I get login screen and everything is normal. If I use the previous kernel 3.8.0-30 everything works like normal. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-30-generic 3.8.0-30.44 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laeb 2134 F pulseaudio /dev/snd/controlC1: laeb 2134 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 30 13:16:19 2013 HibernationDevice: RESUME=UUID=e9e3c42a-9205-4ad8-b97f-fd890621a694 InstallationDate: Installed on 2013-08-29 (31 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 9010 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic root=UUID=10c2ca64-ed49-4e2d-9e2f-e6fd226b23f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-30-generic N/A linux-backports-modules-3.8.0-30-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 00F82W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd06/11/2013:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn00F82W:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1233110 Title: Black screen with blinking cursor and moveable mouse cursor after latest kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I updated ubuntu sep 30. Among other updates was kernel 3.8.0-31.46 After updating and rebooting I get grub, select ubuntu as always, then instead of going to the unity-greeter login screen I just get a black screen with a blinking cursor in the top left and a mouse cursor i can move around. If I press CTRL-ALT-F1 and login i can write “sudo service lightdm --full-restart and then I get login screen and everything is normal. If I use the previous kernel 3.8.0-30 everything works like normal. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-30-generic 3.8.0-30.44 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laeb 2134 F pulseaudio /dev/snd/controlC1: laeb 2134 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 30 13:16:19 2013 HibernationDevice: RESUME=UUID=e9e3c42a-9205-4ad8-b97f-fd890621a694 InstallationDate: Installed on 2013-08-29 (31 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 9010 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic root=UUID=10c2ca64-ed49-4e2d-9e2f-e6fd226b23f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-30-generic N/A linux-backports-modules-3.8.0-30-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 00F82W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd06/11/2013:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn00F82W:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this
