[Kernel-packages] [Bug 1911360] Re: Nvidia-Graphics-Drivers-460 Causes System To Not Boot
** Project changed: maas-deployer => maas -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1911360 Title: Nvidia-Graphics-Drivers-460 Causes System To Not Boot Status in MAAS: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: After installing version 460, my 18.04 laptop stopping booting. Error reported: hdaudio hdaudioC0D2: Unable to bind codec. If I boot to grub, press 'e' and remove nomodeset, the systems boots normally. sudo lshw -C display *-display UNCLAIMED description: VGA compatible controller product: GM107GLM [Quadro M1000M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller cap_list configuration: latency=0 resources: memory:dc00-dcff memory:b000-bfff memory:c000-c1ff ioport:e000(size=128) memory:dd00-dd07 *-display UNCLAIMED description: VGA compatible controller product: HD Graphics P530 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list configuration: latency=0 resources: memory:db00-dbff memory:7000-7fff ioport:f000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1911360/+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 1479031] [NEW] attached block devices not showing up
Public bug reported: I have Ubuntu Precise guests running in kvm to which I attach volumes immediately after boot. Sometimes I notice that the devices do not show up in the guest e.g. they are not visible in /proc/partitions and dmesg boot log shows no sign of then being noticed. Qemu itself shows that the devices are attached and if I do a rescan within the guest the devices appear. A reboot also cause the devices to appear. So, it feels like there is enough evidence to suggest that the devices were properly attached by qemu/seabios but they just didn't get noticed by the guest. This issue is reproducible with Precise running 3.2, 3.5 (lts-quantal) and 3.8 (lts-raring) kernels but not as of 3.11 (lts-saucy) so it would appear that something changed between 3.8 and 3.11 that resolved this issue and if we can identify it we should backport to 3.2. I am able to reproduce this issue using Openstack to spin up vms and attach volumes using the following script: http://pastebin.ubuntu.com/11954253/ I hit this issue with 1/2 instances. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Precise) Importance: Undecided Assignee: Chris J Arges (arges) Status: New -- 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/1479031 Title: attached block devices not showing up Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: New Bug description: I have Ubuntu Precise guests running in kvm to which I attach volumes immediately after boot. Sometimes I notice that the devices do not show up in the guest e.g. they are not visible in /proc/partitions and dmesg boot log shows no sign of then being noticed. Qemu itself shows that the devices are attached and if I do a rescan within the guest the devices appear. A reboot also cause the devices to appear. So, it feels like there is enough evidence to suggest that the devices were properly attached by qemu/seabios but they just didn't get noticed by the guest. This issue is reproducible with Precise running 3.2, 3.5 (lts-quantal) and 3.8 (lts-raring) kernels but not as of 3.11 (lts-saucy) so it would appear that something changed between 3.8 and 3.11 that resolved this issue and if we can identify it we should backport to 3.2. I am able to reproduce this issue using Openstack to spin up vms and attach volumes using the following script: http://pastebin.ubuntu.com/11954253/ I hit this issue with 1/2 instances. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479031/+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 1479031] Re: attached block devices not showing up
** Description changed: I have Ubuntu Precise guests running in kvm to which I attach volumes immediately after boot. Sometimes I notice that the devices do not show up in the guest e.g. they are not visible in /proc/partitions and dmesg boot log shows no sign of then being noticed. Qemu itself shows that the devices are attached and if I do a rescan within the guest the devices appear. A reboot also cause the devices to appear. So, it feels like there is enough evidence to suggest that the devices were properly attached by qemu/seabios but they just didn't get noticed by the guest. This issue is reproducible with Precise running 3.2, 3.5 (lts-quantal) and 3.8 (lts-raring) kernels but not as of 3.11 (lts-saucy) so it would appear that something changed between 3.8 and 3.11 that resolved this issue and if we can identify it we should backport to 3.2. - I am currently able to reproduce this issue using openstack to spin up - vms and attach volumes using the following script: + I am able to reproduce this issue using Openstack to spin up vms and + attach volumes using the following script: http://pastebin.ubuntu.com/11954253/ - I currently hit this issue with 1/2 instrances. + I hit this issue with 1/2 instances. -- 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/1479031 Title: attached block devices not showing up Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: New Bug description: I have Ubuntu Precise guests running in kvm to which I attach volumes immediately after boot. Sometimes I notice that the devices do not show up in the guest e.g. they are not visible in /proc/partitions and dmesg boot log shows no sign of then being noticed. Qemu itself shows that the devices are attached and if I do a rescan within the guest the devices appear. A reboot also cause the devices to appear. So, it feels like there is enough evidence to suggest that the devices were properly attached by qemu/seabios but they just didn't get noticed by the guest. This issue is reproducible with Precise running 3.2, 3.5 (lts-quantal) and 3.8 (lts-raring) kernels but not as of 3.11 (lts-saucy) so it would appear that something changed between 3.8 and 3.11 that resolved this issue and if we can identify it we should backport to 3.2. I am able to reproduce this issue using Openstack to spin up vms and attach volumes using the following script: http://pastebin.ubuntu.com/11954253/ I hit this issue with 1/2 instances. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479031/+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
