[Kernel-packages] [Bug 1244176] Re: Server 13.10 Install Fails with USB Keyboard (Appears to Hang)
As said in comment #13, I think this is related to the ohci-pci module. All other usb hcd drivers are built-in but this one was missed after upstream split it off the ohci_hcd driver. Initramfs-tools cannot help there for the installer at least. ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Stefan Bader (smb) ** Changed in: linux (Ubuntu) Status: Confirmed = In Progress ** Changed in: initramfs-tools (Ubuntu) Status: New = Invalid ** Also affects: initramfs-tools (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Saucy) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu Saucy) Status: New = Invalid -- 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/1244176 Title: Server 13.10 Install Fails with USB Keyboard (Appears to Hang) Status in “initramfs-tools” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: In Progress Status in “initramfs-tools” source package in Saucy: Invalid Status in “linux” source package in Saucy: New Bug description: A fresh install of Server 13.10 on old hardware fails when a USB keyboard is present. The installation succeeds when a PS/2 keyboard is installed. The installation appears to hang at the third screen, which is Select Language. The screen does not respond to keyboard or mouse events. The issue was experienced independently on HP/Compag dc5850 with Athlon X2 2.3 GHz dual core, 4GB RAM; and DELL Optiplex 755. See Server 13.10 Install Hangs, http://askubuntu.com/questions/364945/server-13-10-install- hangs/364949. The issue was not present on Server 12.04.3 LTS or 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1244176/+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 1244176] Re: Server 13.10 Install Fails with USB Keyboard (Appears to Hang)
Proposing to build the driver into the kernel (again). Though for Saucy this would only help the installation when the image would get re-spun with the new kernel. This is normally not done. But we will have to see. ** Changed in: linux (Ubuntu) Status: In Progress = Fix Committed ** Changed in: linux (Ubuntu Saucy) Status: New = In Progress ** Changed in: linux (Ubuntu Saucy) Importance: Undecided = High -- 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/1244176 Title: Server 13.10 Install Fails with USB Keyboard (Appears to Hang) Status in “initramfs-tools” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Fix Committed Status in “initramfs-tools” source package in Saucy: Invalid Status in “linux” source package in Saucy: In Progress Bug description: A fresh install of Server 13.10 on old hardware fails when a USB keyboard is present. The installation succeeds when a PS/2 keyboard is installed. The installation appears to hang at the third screen, which is Select Language. The screen does not respond to keyboard or mouse events. The issue was experienced independently on HP/Compag dc5850 with Athlon X2 2.3 GHz dual core, 4GB RAM; and DELL Optiplex 755. See Server 13.10 Install Hangs, http://askubuntu.com/questions/364945/server-13-10-install- hangs/364949. The issue was not present on Server 12.04.3 LTS or 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1244176/+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 1244176] Re: Server 13.10 Install Fails with USB Keyboard (Appears to Hang)
Fix committed does not mean its available. It just means it was added to the git repo. If a kernel gets available there should be an automatic release notice and the status changing to 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/1244176 Title: Server 13.10 Install Fails with USB Keyboard (Appears to Hang) Status in “initramfs-tools” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Fix Committed Status in “initramfs-tools” source package in Saucy: Invalid Status in “linux” source package in Saucy: In Progress Status in “initramfs-tools” source package in Trusty: Invalid Status in “linux” source package in Trusty: Fix Committed Bug description: A fresh install of Server 13.10 on old hardware fails when a USB keyboard is present. The installation succeeds when a PS/2 keyboard is installed. The installation appears to hang at the third screen, which is Select Language. The screen does not respond to keyboard or mouse events. The issue was experienced independently on HP/Compag dc5850 with Athlon X2 2.3 GHz dual core, 4GB RAM; and DELL Optiplex 755. See Server 13.10 Install Hangs, http://askubuntu.com/questions/364945/server-13-10-install- hangs/364949. The issue was not present on Server 12.04.3 LTS or 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1244176/+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 1258631] Re: instances fails to register GPT partition entries on virtio devices
Funny enough the boot dmesg contains some indication about the problem, while the serial output does now (or so it seems): [0.627017] GPT:Primary header thinks Alt. header is not at the end of the disk. [0.628500] GPT:4194303 != 20971519 [0.629167] GPT:Alternate GPT header not at the end of the disk. [0.630291] GPT:4194303 != 20971519 [0.630951] GPT: Use GNU Parted to correct GPT errors. [0.632002] vda: vda1 I have to get the image to check locally. Would be interesting to look at the reported values and whether breaking into pre-mount allows to reread the partition table (check whether its a race). -- 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/1258631 Title: instances fails to register GPT partition entries on virtio devices Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Raring: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: When booting via KVM and using the VirtIO interface, GPT partition entries are not shown properly. ubuntu@gpt-test-4:~$ sudo parted /dev/vda -s -- print Model: Virtio Block Device (virtblk) Disk /dev/vda: 10.7GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start EndSize File system Name Flags 127 1049kB 2097kB 1049kB BIOS boot partition bios_grub 128 2097kB 89.1MB 87.0MB fat32 EFI System boot 1 89.1MB 10.7GB 10.6GB ext4 Linux filesystem Booting with -hda disk.img [2.612975] sr 1:0:0:0: Attached scsi generic sg1 type 5 [2.617252] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [2.644685] sda: sda1 sda127 sda128 [2.664314] sd 0:0:0:0: [sda] Attached SCSI disk Booting with -drive if=virtio,file=disk.img or -drive if=scsi,file=disk.img: [2.411933] brd: module loaded [2.422616] loop: module loaded [2.442178] vda: vda1 [2.49] scsi0 : ata_piix [2.456868] scsi1 : ata_piix ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu6 ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 Uname: Linux 3.12.0-5-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 Date: Fri Dec 6 18:49:57 2013 Ec2AMI: ami-0632 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0548 Ec2Ramdisk: ari-0548 Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-5-generic root=LABEL=cloudimg-rootfs console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.3:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.1.3 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258631/+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 1258631] Re: instances fails to register GPT partition entries on virtio devices
** Changed in: linux (Ubuntu Trusty) Status: Confirmed = In Progress ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) = Stefan Bader (smb) -- 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/1258631 Title: instances fails to register GPT partition entries on virtio devices Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Raring: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “linux” source package in Trusty: In Progress Bug description: When booting via KVM and using the VirtIO interface, GPT partition entries are not shown properly. ubuntu@gpt-test-4:~$ sudo parted /dev/vda -s -- print Model: Virtio Block Device (virtblk) Disk /dev/vda: 10.7GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start EndSize File system Name Flags 127 1049kB 2097kB 1049kB BIOS boot partition bios_grub 128 2097kB 89.1MB 87.0MB fat32 EFI System boot 1 89.1MB 10.7GB 10.6GB ext4 Linux filesystem Booting with -hda disk.img [2.612975] sr 1:0:0:0: Attached scsi generic sg1 type 5 [2.617252] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [2.644685] sda: sda1 sda127 sda128 [2.664314] sd 0:0:0:0: [sda] Attached SCSI disk Booting with -drive if=virtio,file=disk.img or -drive if=scsi,file=disk.img: [2.411933] brd: module loaded [2.422616] loop: module loaded [2.442178] vda: vda1 [2.49] scsi0 : ata_piix [2.456868] scsi1 : ata_piix ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu6 ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 Uname: Linux 3.12.0-5-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 Date: Fri Dec 6 18:49:57 2013 Ec2AMI: ami-0632 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0548 Ec2Ramdisk: ari-0548 Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-5-generic root=LABEL=cloudimg-rootfs console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.3:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.1.3 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258631/+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 1258631] Re: instances fails to register GPT partition entries on virtio devices
Oh dear, the answer is so simple after one finally realizes what is going on... The problem here is that the virtio_blk driver has not been changed to support more than 15 partitions per device. The partition scanning is looking at the GPT partition table but only at the first 15 elements. Since the other two partitions are 127 and 128, they never get added if the device is a virtio disk. So this isn't exactly a bug but a limitation in virtio right now. I am not sure whether the images could use number 14 and 15 for those two partitions. Then they should be visible for emulated and virtual devices... Otherwise this would be some development work which one had to discuss upstream. -- 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/1258631 Title: instances fails to register GPT partition entries on virtio devices Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Raring: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “linux” source package in Trusty: In Progress Bug description: When booting via KVM and using the VirtIO interface, GPT partition entries are not shown properly. ubuntu@gpt-test-4:~$ sudo parted /dev/vda -s -- print Model: Virtio Block Device (virtblk) Disk /dev/vda: 10.7GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start EndSize File system Name Flags 127 1049kB 2097kB 1049kB BIOS boot partition bios_grub 128 2097kB 89.1MB 87.0MB fat32 EFI System boot 1 89.1MB 10.7GB 10.6GB ext4 Linux filesystem Booting with -hda disk.img [2.612975] sr 1:0:0:0: Attached scsi generic sg1 type 5 [2.617252] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [2.644685] sda: sda1 sda127 sda128 [2.664314] sd 0:0:0:0: [sda] Attached SCSI disk Booting with -drive if=virtio,file=disk.img or -drive if=scsi,file=disk.img: [2.411933] brd: module loaded [2.422616] loop: module loaded [2.442178] vda: vda1 [2.49] scsi0 : ata_piix [2.456868] scsi1 : ata_piix ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu6 ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 Uname: Linux 3.12.0-5-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 Date: Fri Dec 6 18:49:57 2013 Ec2AMI: ami-0632 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0548 Ec2Ramdisk: ari-0548 Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-5-generic root=LABEL=cloudimg-rootfs console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.3:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.1.3 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258631/+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 1258631] Re: instances fails to register GPT partition entries on virtio devices
Won't fix sounds harsh but as this is not really a bug but a limitation of the driver, this would be an enhancement and no fix of a bug. Which means this would have to be done (and the need for it accepted) upstream. ** Changed in: linux (Ubuntu Trusty) Status: In Progress = Won't Fix ** Changed in: linux (Ubuntu Trusty) Assignee: Stefan Bader (smb) = (unassigned) ** Changed in: linux (Ubuntu Saucy) Status: Confirmed = Won't Fix ** Changed in: linux (Ubuntu Raring) Status: Confirmed = Won't Fix ** Changed in: linux (Ubuntu) Status: In Progress = Won't Fix -- 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/1258631 Title: instances fails to register GPT partition entries on virtio devices Status in “linux” package in Ubuntu: Won't Fix Status in “linux” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Won't Fix Status in “linux” source package in Trusty: Won't Fix Bug description: When booting via KVM and using the VirtIO interface, GPT partition entries are not shown properly. ubuntu@gpt-test-4:~$ sudo parted /dev/vda -s -- print Model: Virtio Block Device (virtblk) Disk /dev/vda: 10.7GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start EndSize File system Name Flags 127 1049kB 2097kB 1049kB BIOS boot partition bios_grub 128 2097kB 89.1MB 87.0MB fat32 EFI System boot 1 89.1MB 10.7GB 10.6GB ext4 Linux filesystem Booting with -hda disk.img [2.612975] sr 1:0:0:0: Attached scsi generic sg1 type 5 [2.617252] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [2.644685] sda: sda1 sda127 sda128 [2.664314] sd 0:0:0:0: [sda] Attached SCSI disk Booting with -drive if=virtio,file=disk.img or -drive if=scsi,file=disk.img: [2.411933] brd: module loaded [2.422616] loop: module loaded [2.442178] vda: vda1 [2.49] scsi0 : ata_piix [2.456868] scsi1 : ata_piix ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu6 ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 Uname: Linux 3.12.0-5-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 Date: Fri Dec 6 18:49:57 2013 Ec2AMI: ami-0632 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0548 Ec2Ramdisk: ari-0548 Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-5-generic root=LABEL=cloudimg-rootfs console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.3:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.1.3 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258631/+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 1244176] Re: Server 13.10 Install Fails with USB Keyboard (Appears to Hang)
** Tags removed: verification-needed-saucy ** Tags added: verification-done-saucy -- 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/1244176 Title: Server 13.10 Install Fails with USB Keyboard (Appears to Hang) Status in “initramfs-tools” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Fix Released Status in “initramfs-tools” source package in Saucy: Invalid Status in “linux” source package in Saucy: Fix Committed Status in “initramfs-tools” source package in Trusty: Invalid Status in “linux” source package in Trusty: Fix Released Bug description: A fresh install of Server 13.10 on old hardware fails when a USB keyboard is present. The installation succeeds when a PS/2 keyboard is installed. The installation appears to hang at the third screen, which is Select Language. The screen does not respond to keyboard or mouse events. The issue was experienced independently on HP/Compag dc5850 with Athlon X2 2.3 GHz dual core, 4GB RAM; and DELL Optiplex 755. See Server 13.10 Install Hangs, http://askubuntu.com/questions/364945/server-13-10-install- hangs/364949. The issue was not present on Server 12.04.3 LTS or 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1244176/+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 1244176] Re: Server 13.10 Install Fails with USB Keyboard (Appears to Hang)
I set the saucy confirmation to done because a real verification is hard there. ISO images are usually not re-created after release and even less likely with a kernel still in proposed. So I just checked that the deb packages for 3.11.0-15.23 contain no ohci-pci module and the contained config has CONFIG_USB_OHCI_HCD_PCI. -- 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/1244176 Title: Server 13.10 Install Fails with USB Keyboard (Appears to Hang) Status in “initramfs-tools” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Fix Released Status in “initramfs-tools” source package in Saucy: Invalid Status in “linux” source package in Saucy: Fix Committed Status in “initramfs-tools” source package in Trusty: Invalid Status in “linux” source package in Trusty: Fix Released Bug description: A fresh install of Server 13.10 on old hardware fails when a USB keyboard is present. The installation succeeds when a PS/2 keyboard is installed. The installation appears to hang at the third screen, which is Select Language. The screen does not respond to keyboard or mouse events. The issue was experienced independently on HP/Compag dc5850 with Athlon X2 2.3 GHz dual core, 4GB RAM; and DELL Optiplex 755. See Server 13.10 Install Hangs, http://askubuntu.com/questions/364945/server-13-10-install- hangs/364949. The issue was not present on Server 12.04.3 LTS or 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1244176/+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 1244176] Re: Server 13.10 Install Fails with USB Keyboard (Appears to Hang)
... has CONFIG_USB_OHCI_HCD_PCI=y was what I tried to write... -- 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/1244176 Title: Server 13.10 Install Fails with USB Keyboard (Appears to Hang) Status in “initramfs-tools” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Fix Released Status in “initramfs-tools” source package in Saucy: Invalid Status in “linux” source package in Saucy: Fix Committed Status in “initramfs-tools” source package in Trusty: Invalid Status in “linux” source package in Trusty: Fix Released Bug description: A fresh install of Server 13.10 on old hardware fails when a USB keyboard is present. The installation succeeds when a PS/2 keyboard is installed. The installation appears to hang at the third screen, which is Select Language. The screen does not respond to keyboard or mouse events. The issue was experienced independently on HP/Compag dc5850 with Athlon X2 2.3 GHz dual core, 4GB RAM; and DELL Optiplex 755. See Server 13.10 Install Hangs, http://askubuntu.com/questions/364945/server-13-10-install- hangs/364949. The issue was not present on Server 12.04.3 LTS or 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1244176/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
Before running prepare-testbed: - create a directory in /mnt that user ubuntu can write to (say /mnt/adt) - echo BASEDIR=/mnt/adt ~/.adtrc autopkgtest should then use /mnt which has lots of space on medium guests. -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM Status in “linux” package in Ubuntu: In Progress Status in “qemu-kvm” package in Ubuntu: New Status in “linux” source package in Saucy: In Progress Status in “qemu-kvm” source package in Saucy: New Bug description: Attempting to run apt-get in a nested vm hosted in OpenStack results in a general protection fault in the kernel in the nested VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
I saw a similar crash when running the prepare script with a Saucy64 host, a Saucy32 1rst and Saucy32 2nd level guest. The 1rst level guest cpu set to core2duo and I also had to replace the qemu-system-x86_64 by qemu (which maps to the same arch). Otherwise the 2nd level guest was not started at all. That would on one run give a double-fault as you had, but the second attempt did succeed. Though both runs had a lot of NMI (reason 21 and 31) messages in them. -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM Status in “linux” package in Ubuntu: In Progress Status in “qemu-kvm” package in Ubuntu: New Status in “linux” source package in Saucy: In Progress Status in “qemu-kvm” source package in Saucy: New Bug description: Attempting to run apt-get in a nested vm hosted in OpenStack results in a general protection fault in the kernel in the nested VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
Using a 64bit 1rst level guest seemed better on manual runs but running in loops seemed to have locked up on the third run. Though completely without any messages. I have to look into that next week. I need to run again with qmp enabled. At least this allows to check for the instruction pointer of the cpus. But unfortunately I don't know yet how to get any better data from the 2nd level guest. -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM Status in “linux” package in Ubuntu: In Progress Status in “qemu-kvm” package in Ubuntu: New Status in “linux” source package in Saucy: In Progress Status in “qemu-kvm” source package in Saucy: New Bug description: Attempting to run apt-get in a nested vm hosted in OpenStack results in a general protection fault in the kernel in the nested VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
So host Q and 1rst 32 completed 35 runs and 1rst 64 completed 40. -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM Status in “linux” package in Ubuntu: In Progress Status in “qemu-kvm” package in Ubuntu: New Status in “linux” source package in Saucy: In Progress Status in “qemu-kvm” source package in Saucy: New Bug description: Attempting to run apt-get in a nested vm hosted in OpenStack results in a general protection fault in the kernel in the nested VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
They can be even together. The -nographic removes any emulated graphics card. I am not sure in detail how the cloud images work, but I believe serial line as a console is always on. Depending on which release (in that case I think it is the qemu user-space) the used setup would not work even. Because -monitor stdio redicrects the monitor to stdio and the default of serial was stdio, too. So they did clash (might depend on -nographic as well). So when playing without -nogrphics, and crashes persist, you might play with -vga std which would give a std vga card instead of cirrus. -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM Status in “linux” package in Ubuntu: In Progress Status in “qemu-kvm” package in Ubuntu: New Status in “linux” source package in Saucy: In Progress Status in “qemu-kvm” source package in Saucy: New Bug description: Attempting to run apt-get in a nested vm hosted in OpenStack results in a general protection fault in the kernel in the nested VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
** Changed in: linux (Ubuntu) Assignee: Stefan Bader (smb) = (unassigned) ** Changed in: linux (Ubuntu Saucy) Assignee: Stefan Bader (smb) = (unassigned) ** Changed in: qemu-kvm (Ubuntu) Assignee: Stefan Bader (smb) = (unassigned) ** Changed in: qemu-kvm (Ubuntu Saucy) Assignee: Stefan Bader (smb) = (unassigned) -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM Status in “linux” package in Ubuntu: In Progress Status in “qemu-kvm” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: In Progress Status in “qemu-kvm” source package in Saucy: Confirmed Bug description: Attempting to run apt-get in a nested vm hosted in OpenStack results in a general protection fault in the kernel in the nested VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1233075] Re: resizefs failure with raring
So as of IRC feedback this seems to work on a current Quantal kernel.
Which means the next steps should be to verify on one side whether for
example the originally released Raring kernel (3.8.0-19.29) already
showed that problem and on the other side whether a current Saucy
(3.11.0-9.16) kernel still has the same issue.
** 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/1233075
Title:
resizefs failure with raring
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Deploying a raring cloud image with a 2.7G filesystem to 2TB hard disk
crashes in resizefs
[ 143.673885] 0800 880bd4b87f60 880bca8b7d00
8125b
e47
[ 143.673945] Call Trace:
[ 143.673970] [8125be47] ext4_flex_group_add+0x1317/0x1490
[ 143.674001] [8125d00a] ext4_resize_fs+0x74a/0xdc0
[ 143.674030] [8123ae31] ext4_ioctl+0x971/0xb60
[ 143.674060] [811a4091] ? do_filp_open+0x41/0xa0
[ 143.674089] [811a61a9] do_vfs_ioctl+0x99/0x570
[ 143.674119] [8117d00f] ? kmem_cache_free+0x2f/0x130
[ 143.674148] [811a36b2] ? final_putname+0x22/0x50
[ 143.674177] [811a38b9] ? putname+0x29/0x40
[ 143.674204] [811a6711] sys_ioctl+0x91/0xb0
[ 143.674233] [816d59dd] system_call_fastpath+0x1a/0x1f
[ 143.674261] Code: 0f 85 f2 fe ff ff 31 c0 48 83 c4 28 5b 41 5c 41 5d 41 5e
41
5f 5d c3 48 83 c4 28 b8 f4 ff ff ff 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b
90
66 66 66 66 90 55 48 89 e5 48 83 ec 18 4c 89 65 f0 49
[ 143.674584] RIP [8125a5cd] set_flexbg_block_bitmap+0x17d/0x180
[ 143.674618] RSP 880bca8b7bb0
[ 143.674643] ---[ end trace 5fa931e218cd3ae5 ]---
2013-09-30 10:07:44,273 - util.py[WARNING]: Failed to resize filesystem
(cmd=('r
esize2fs', '/dev/disk/by-uuid/420927c3-abd7-4b7d-972c-a8b6969d7d53'))
2013-09-30 10:07:44,293 - util.py[WARNING]: Running resizefs (module
'cloudinit
.config.cc_resizefs' from
'/usr/lib/python2.7/dist-packages/cloudinit/config/cc_
resizefs.pyc') failed
Is all the diagnostics I have so far.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233075/+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 1209423] Re: [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at boot
Lucid server is supported until 2015 and I would tend to see this as a server issue. So since this can be reduced to md problems, the fact that /proc/mdstat is empty would lead to assume that something during the assembly failed completely. Despite the weird output of mdadm --examine (sounds really like some tool failure back in lucid) does looking at the other mirror half produce the same/similar output (assume that would be on sdc)? Maybe also remove the quiet command line option in grub before booting (if that still hides too much output, experiment with removing splash as well, though I think to remember that may cause the question about skipping or manual recovery not to appear on screen on some older releases (thoug not remembering which one)). -- 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/1209423 Title: [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at boot Status in “linux” package in Ubuntu: Incomplete Bug description: After update from 2.6.32-46 to 2.6.32-47 one of the md arrays does not start anymore at boot time. The RAID 1 md0 now causes message Continue to wait; or Press S to skip mounting or M for manual recovery at boot. I used S to create this report as requested in a similar bug report (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1190295) by user penalvch Booting back into 2.6.32-46 the md devices are correctly set up and the system boots normally. See the linked bug for further details, such as: The array that does not start anymore has the following config: level=raid1 metadata=1.2 num-devices=2 While a second array with metadata=1.0 seems to be recognized and started correctly. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-50-generic 2.6.32-50.112 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-50.112-generic 2.6.32.61+drm33.26 Uname: Linux 2.6.32-50-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1991 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf622 irq 22' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,80860034,00100202' Controls : 28 Simple ctrls : 16 Date: Thu Aug 8 02:01:09 2013 HibernationDevice: RESUME=UUID=b1649a13-fffd-4e98-b42b-a5e9ea98f9fc InstallationMedia: Ubuntu 10.04.4 LTS Lucid Lynx - Release amd64 (20120214.2) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-50-generic root=UUID=e69dddfa-14a0-499f-9267-edca27fbd7a4 ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34.14 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8192s_usb Title: [STAGING] dmi.bios.date: 04/19/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: WBIBX10J.86A.0293.2010.0419.1819 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WB dmi.board.vendor: Intel Corporation dmi.board.version: AAE64798-207 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0293.2010.0419.1819:bd04/19/2010:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-207:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209423/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
Serge mentioned today on IRC that this may be also a glibc issue, but I am not sure what exactly he was looking at and why he thinks so. Apparently ftracing (I guess the qemu process) and some partially inlining clone function (those with .isra extention) were involved. -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM Status in “linux” package in Ubuntu: Incomplete Status in “qemu-kvm” package in Ubuntu: New Bug description: Attempting to run apt-get in a nested vm hosted in OpenStack results in a general protection fault in the kernel in the nested VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1209423] Re: [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at boot
Yes, could be related but also is a slightly more complicated setup as the imsm container is used (fakeRAID with some support in the BIOS from Intel). Tried to reproduce in a VM but without success, yet. Though one interesting note is that mdadm --misc --scan --detail would somehow report a metadata version of 01.02 (instead of 1.2) which when added to /etc/mdadm/mdadm.conf causes mdadm to complain about an unknown format (though the array still gets assembled). Can we get the output of mdadm --misc --scan --detail for the working and non-working kernel and the contents of /etc/mdadm/mdadm.conf? -- 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/1209423 Title: [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at boot Status in “linux” package in Ubuntu: Incomplete Bug description: After update from 2.6.32-46 to 2.6.32-47 one of the md arrays does not start anymore at boot time. The RAID 1 md0 now causes message Continue to wait; or Press S to skip mounting or M for manual recovery at boot. I used S to create this report as requested in a similar bug report (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1190295) by user penalvch Booting back into 2.6.32-46 the md devices are correctly set up and the system boots normally. See the linked bug for further details, such as: The array that does not start anymore has the following config: level=raid1 metadata=1.2 num-devices=2 While a second array with metadata=1.0 seems to be recognized and started correctly. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-50-generic 2.6.32-50.112 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-50.112-generic 2.6.32.61+drm33.26 Uname: Linux 2.6.32-50-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1991 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf622 irq 22' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,80860034,00100202' Controls : 28 Simple ctrls : 16 Date: Thu Aug 8 02:01:09 2013 HibernationDevice: RESUME=UUID=b1649a13-fffd-4e98-b42b-a5e9ea98f9fc InstallationMedia: Ubuntu 10.04.4 LTS Lucid Lynx - Release amd64 (20120214.2) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-50-generic root=UUID=e69dddfa-14a0-499f-9267-edca27fbd7a4 ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34.14 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8192s_usb Title: [STAGING] dmi.bios.date: 04/19/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: WBIBX10J.86A.0293.2010.0419.1819 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WB dmi.board.vendor: Intel Corporation dmi.board.version: AAE64798-207 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0293.2010.0419.1819:bd04/19/2010:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-207:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209423/+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 1209423] Re: [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at boot
Looks like the --scan command might be useless as it seems only to work properly when the array is defined correctly in mdadm.conf. All my devices can be examined with --examine and do not show those odd failed lines. While not being able to reproduce the exact issue, removing the array definition from mdadm.conf gets me into a similar problem and mdadm seems not to work right at that point. But that happens with the old -46 and newer -50 kernels. -- 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/1209423 Title: [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at boot Status in “linux” package in Ubuntu: Incomplete Bug description: After update from 2.6.32-46 to 2.6.32-47 one of the md arrays does not start anymore at boot time. The RAID 1 md0 now causes message Continue to wait; or Press S to skip mounting or M for manual recovery at boot. I used S to create this report as requested in a similar bug report (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1190295) by user penalvch Booting back into 2.6.32-46 the md devices are correctly set up and the system boots normally. See the linked bug for further details, such as: The array that does not start anymore has the following config: level=raid1 metadata=1.2 num-devices=2 While a second array with metadata=1.0 seems to be recognized and started correctly. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-50-generic 2.6.32-50.112 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-50.112-generic 2.6.32.61+drm33.26 Uname: Linux 2.6.32-50-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1991 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf622 irq 22' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,80860034,00100202' Controls : 28 Simple ctrls : 16 Date: Thu Aug 8 02:01:09 2013 HibernationDevice: RESUME=UUID=b1649a13-fffd-4e98-b42b-a5e9ea98f9fc InstallationMedia: Ubuntu 10.04.4 LTS Lucid Lynx - Release amd64 (20120214.2) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-50-generic root=UUID=e69dddfa-14a0-499f-9267-edca27fbd7a4 ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34.14 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8192s_usb Title: [STAGING] dmi.bios.date: 04/19/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: WBIBX10J.86A.0293.2010.0419.1819 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WB dmi.board.vendor: Intel Corporation dmi.board.version: AAE64798-207 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0293.2010.0419.1819:bd04/19/2010:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-207:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209423/+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 1242210] Re: Failed to install linux kernel
It looks a bit like the primary failure is something during the post- install of linux-image is trying to call update-nvidia which does not exist and then causes the complete post-install to fail. And that in turn makes those other packages fail because they depend on linux-image. Maybe worth checking whether some script in /etc/kernel/postinst.d calls out to update-nvidia and to comment out that line. Then sudo apt-get install -f should complete the install. -- 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/1242210 Title: Failed to install linux kernel Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from 13.04 to 13.10. I get the following error: E: linux-image-3.11.0-12-generic: subprocess installed post-installation script returned error exit status 2 E: linux-image-extra-3.11.0-12-generic: dependency problems - leaving unconfigured E: linux-image-generic: dependency problems - leaving unconfigured E: linux-generic: dependency problems - leaving unconfigured E: linux: dependency problems - leaving unconfigured E: linux-image: dependency problems - leaving unconfigured Additional info here: http://askubuntu.com/questions/360593/after- upgrade-to-13-10-unable-to-update-kernel Description: Ubuntu 13.10 64bit Release: 13.10 --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2012-05-15 (523 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True NonfreeKernelModules: nvidia Package: linux 3.11.0.12.13 PackageArchitecture: amd64 Tags: saucy Uname: Linux 3.11.6-031106-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to saucy on 2013-10-17 (2 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pst007x3426 F pulseaudio /dev/snd/controlC0: pst007x3426 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=ed7653b8-c185-4b7d-a8e4-6dc07f73d3f1 InstallationDate: Installed on 2012-05-15 (523 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: System76, Inc. Serval Professional MarkForUpload: True NonfreeKernelModules: nvidia Package: linux 3.11.0.12.13 PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=bb2235bf-3a84-4901-ab95-2ee3634533f8 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: zram Tags: saucy staging Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (2 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video dmi.bios.date: 08/09/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: Not Applicable dmi.board.name: Serval Professional dmi.board.vendor: System76, Inc. dmi.board.version: serp7 dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: serp7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7: dmi.product.name: Serval Professional dmi.product.version: serp7 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242210/+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 1242210] Re: Failed to install linux kernel
As the script seems to be present at least, could you check (ls -la /etc/kernel/postinst.d) whether it is executable? -- 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/1242210 Title: Failed to install linux kernel Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from 13.04 to 13.10. I get the following error: E: linux-image-3.11.0-12-generic: subprocess installed post-installation script returned error exit status 2 E: linux-image-extra-3.11.0-12-generic: dependency problems - leaving unconfigured E: linux-image-generic: dependency problems - leaving unconfigured E: linux-generic: dependency problems - leaving unconfigured E: linux: dependency problems - leaving unconfigured E: linux-image: dependency problems - leaving unconfigured Additional info here: http://askubuntu.com/questions/360593/after- upgrade-to-13-10-unable-to-update-kernel Description: Ubuntu 13.10 64bit Release: 13.10 --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2012-05-15 (523 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True NonfreeKernelModules: nvidia Package: linux 3.11.0.12.13 PackageArchitecture: amd64 Tags: saucy Uname: Linux 3.11.6-031106-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to saucy on 2013-10-17 (2 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pst007x3426 F pulseaudio /dev/snd/controlC0: pst007x3426 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=ed7653b8-c185-4b7d-a8e4-6dc07f73d3f1 InstallationDate: Installed on 2012-05-15 (523 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: System76, Inc. Serval Professional MarkForUpload: True NonfreeKernelModules: nvidia Package: linux 3.11.0.12.13 PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=bb2235bf-3a84-4901-ab95-2ee3634533f8 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: zram Tags: saucy staging Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (2 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video dmi.bios.date: 08/09/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: Not Applicable dmi.board.name: Serval Professional dmi.board.vendor: System76, Inc. dmi.board.version: serp7 dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: serp7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7: dmi.product.name: Serval Professional dmi.product.version: serp7 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242210/+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 1242210] Re: Failed to install linux kernel
Unfortunately you did a whole lot of things by now. So it is hard to tell in what state your system is now. If you run sudo apt-get install -f does this still complain about the kernel packages? This would be something to solve first as the nvidia binary module requires those to compile a driver module. One thing to make it simpler for the moment to change boot arguments or which kernel to boot is to run sudo vi /etc/default/grub and add '#' to the beginning of those two lines GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true Then run sudo update-grub that should give you an automatic grub selection screen at boot with a 10s countdown. Under advanced option would be any older kernels left on the system. Does booting back into an older one give you some high-res graphics again? Does pressing ctrl-alt-f1 give you a text console? -- 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/1242210 Title: Failed to install linux kernel Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from 13.04 to 13.10. I get the following error: E: linux-image-3.11.0-12-generic: subprocess installed post-installation script returned error exit status 2 E: linux-image-extra-3.11.0-12-generic: dependency problems - leaving unconfigured E: linux-image-generic: dependency problems - leaving unconfigured E: linux-generic: dependency problems - leaving unconfigured E: linux: dependency problems - leaving unconfigured E: linux-image: dependency problems - leaving unconfigured Additional info here: http://askubuntu.com/questions/360593/after- upgrade-to-13-10-unable-to-update-kernel Description: Ubuntu 13.10 64bit Release: 13.10 --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2012-05-15 (523 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True NonfreeKernelModules: nvidia Package: linux 3.11.0.12.13 PackageArchitecture: amd64 Tags: saucy Uname: Linux 3.11.6-031106-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to saucy on 2013-10-17 (2 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pst007x3426 F pulseaudio /dev/snd/controlC0: pst007x3426 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=ed7653b8-c185-4b7d-a8e4-6dc07f73d3f1 InstallationDate: Installed on 2012-05-15 (523 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: System76, Inc. Serval Professional MarkForUpload: True NonfreeKernelModules: nvidia Package: linux 3.11.0.12.13 PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=bb2235bf-3a84-4901-ab95-2ee3634533f8 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: zram Tags: saucy staging Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (2 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video dmi.bios.date: 08/09/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: Not Applicable dmi.board.name: Serval Professional dmi.board.vendor: System76, Inc. dmi.board.version: serp7 dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: serp7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7: dmi.product.name: Serval Professional dmi.product.version: serp7 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242210/+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 1242210] Re: Failed to install linux kernel
Could you attach /var/log/syslog and /var/log/Xorg.0.log from your system, please. -- 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/1242210 Title: Failed to install linux kernel Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from 13.04 to 13.10. I get the following error: E: linux-image-3.11.0-12-generic: subprocess installed post-installation script returned error exit status 2 E: linux-image-extra-3.11.0-12-generic: dependency problems - leaving unconfigured E: linux-image-generic: dependency problems - leaving unconfigured E: linux-generic: dependency problems - leaving unconfigured E: linux: dependency problems - leaving unconfigured E: linux-image: dependency problems - leaving unconfigured Additional info here: http://askubuntu.com/questions/360593/after- upgrade-to-13-10-unable-to-update-kernel Description: Ubuntu 13.10 64bit Release: 13.10 --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2012-05-15 (523 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True NonfreeKernelModules: nvidia Package: linux 3.11.0.12.13 PackageArchitecture: amd64 Tags: saucy Uname: Linux 3.11.6-031106-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to saucy on 2013-10-17 (2 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pst007x3426 F pulseaudio /dev/snd/controlC0: pst007x3426 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=ed7653b8-c185-4b7d-a8e4-6dc07f73d3f1 InstallationDate: Installed on 2012-05-15 (523 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: System76, Inc. Serval Professional MarkForUpload: True NonfreeKernelModules: nvidia Package: linux 3.11.0.12.13 PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=bb2235bf-3a84-4901-ab95-2ee3634533f8 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: zram Tags: saucy staging Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (2 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video dmi.bios.date: 08/09/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: Not Applicable dmi.board.name: Serval Professional dmi.board.vendor: System76, Inc. dmi.board.version: serp7 dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: serp7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7: dmi.product.name: Serval Professional dmi.product.version: serp7 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242210/+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 1242210] Re: Failed to install linux kernel
Maybe also the output of dkms status as it sound like the binary driver is intended to be used. -- 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/1242210 Title: Failed to install linux kernel Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from 13.04 to 13.10. I get the following error: E: linux-image-3.11.0-12-generic: subprocess installed post-installation script returned error exit status 2 E: linux-image-extra-3.11.0-12-generic: dependency problems - leaving unconfigured E: linux-image-generic: dependency problems - leaving unconfigured E: linux-generic: dependency problems - leaving unconfigured E: linux: dependency problems - leaving unconfigured E: linux-image: dependency problems - leaving unconfigured Additional info here: http://askubuntu.com/questions/360593/after- upgrade-to-13-10-unable-to-update-kernel Description: Ubuntu 13.10 64bit Release: 13.10 --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2012-05-15 (523 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True NonfreeKernelModules: nvidia Package: linux 3.11.0.12.13 PackageArchitecture: amd64 Tags: saucy Uname: Linux 3.11.6-031106-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to saucy on 2013-10-17 (2 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pst007x3426 F pulseaudio /dev/snd/controlC0: pst007x3426 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=ed7653b8-c185-4b7d-a8e4-6dc07f73d3f1 InstallationDate: Installed on 2012-05-15 (523 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: System76, Inc. Serval Professional MarkForUpload: True NonfreeKernelModules: nvidia Package: linux 3.11.0.12.13 PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=bb2235bf-3a84-4901-ab95-2ee3634533f8 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: zram Tags: saucy staging Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (2 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video dmi.bios.date: 08/09/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: Not Applicable dmi.board.name: Serval Professional dmi.board.vendor: System76, Inc. dmi.board.version: serp7 dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: serp7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7: dmi.product.name: Serval Professional dmi.product.version: serp7 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242210/+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 1242210] Re: Failed to install linux kernel
You are not really making it simpler by doing a lot of things you were not asked to and not doing things you were asked to. Just saying... I guess your system is in a state where the nvidia binary driver module is not correctly compiled but the package is installed up to a point where it prevents the nouveau driver to load. The package in question would be called nvidia-somethin. Probabaly dpkg -l|grep nvidia helps). Uninstalling jockey does not help because that is just the helper that shows you the drivers, not the driver itself. So maybe purging the nvidia package gets you into a state that uses nouvau and from there the binary driver could be re-installed... -- 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/1242210 Title: Failed to install linux kernel Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from 13.04 to 13.10. I get the following error: E: linux-image-3.11.0-12-generic: subprocess installed post-installation script returned error exit status 2 E: linux-image-extra-3.11.0-12-generic: dependency problems - leaving unconfigured E: linux-image-generic: dependency problems - leaving unconfigured E: linux-generic: dependency problems - leaving unconfigured E: linux: dependency problems - leaving unconfigured E: linux-image: dependency problems - leaving unconfigured Additional info here: http://askubuntu.com/questions/360593/after- upgrade-to-13-10-unable-to-update-kernel Description: Ubuntu 13.10 64bit Release: 13.10 --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2012-05-15 (523 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True NonfreeKernelModules: nvidia Package: linux 3.11.0.12.13 PackageArchitecture: amd64 Tags: saucy Uname: Linux 3.11.6-031106-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to saucy on 2013-10-17 (2 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pst007x3426 F pulseaudio /dev/snd/controlC0: pst007x3426 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=ed7653b8-c185-4b7d-a8e4-6dc07f73d3f1 InstallationDate: Installed on 2012-05-15 (523 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: System76, Inc. Serval Professional MarkForUpload: True NonfreeKernelModules: nvidia Package: linux 3.11.0.12.13 PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=bb2235bf-3a84-4901-ab95-2ee3634533f8 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: zram Tags: saucy staging Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (2 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video dmi.bios.date: 08/09/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: Not Applicable dmi.board.name: Serval Professional dmi.board.vendor: System76, Inc. dmi.board.version: serp7 dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: serp7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7: dmi.product.name: Serval Professional dmi.product.version: serp7 dmi.sys.vendor: System76, Inc. --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pst007x4871 F pulseaudio /dev/snd/controlC0: pst007x4871 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=ed7653b8-c185-4b7d-a8e4-6dc07f73d3f1 InstallationDate: Installed on 2012-05-15 (525 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: System76, Inc. Serval Professional MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no
[Kernel-packages] [Bug 1242210] Re: Failed to install linux kernel
Cannot speak for Kubuntu but its probably the same, but in Ubuntu it relates to jockey. But then jockey is a front end to manage certain packages for binary drivers. I have no machine up with an nvidia card right now, so I cannot look what package name it is exactly. And I am by now a bit confused what exactly you have installed (but maybe it is ubuntu and additionally the kubuntu desktop to switch between the two). Two things you may be able to try are jockey-text -l (if that has errors) or try sudo apt-get install ubuntu-desktop^ (the ^ and the end means its not a single package but a list). This should basically try to install all packages that are required for an ubuntu install. In case something is missing there. -- 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/1242210 Title: Failed to install linux kernel Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading from 13.04 to 13.10. I get the following error: E: linux-image-3.11.0-12-generic: subprocess installed post-installation script returned error exit status 2 E: linux-image-extra-3.11.0-12-generic: dependency problems - leaving unconfigured E: linux-image-generic: dependency problems - leaving unconfigured E: linux-generic: dependency problems - leaving unconfigured E: linux: dependency problems - leaving unconfigured E: linux-image: dependency problems - leaving unconfigured Additional info here: http://askubuntu.com/questions/360593/after- upgrade-to-13-10-unable-to-update-kernel Description: Ubuntu 13.10 64bit Release: 13.10 --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2012-05-15 (523 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True NonfreeKernelModules: nvidia Package: linux 3.11.0.12.13 PackageArchitecture: amd64 Tags: saucy Uname: Linux 3.11.6-031106-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to saucy on 2013-10-17 (2 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pst007x3426 F pulseaudio /dev/snd/controlC0: pst007x3426 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=ed7653b8-c185-4b7d-a8e4-6dc07f73d3f1 InstallationDate: Installed on 2012-05-15 (523 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: System76, Inc. Serval Professional MarkForUpload: True NonfreeKernelModules: nvidia Package: linux 3.11.0.12.13 PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=bb2235bf-3a84-4901-ab95-2ee3634533f8 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: zram Tags: saucy staging Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (2 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video dmi.bios.date: 08/09/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: Not Applicable dmi.board.name: Serval Professional dmi.board.vendor: System76, Inc. dmi.board.version: serp7 dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: serp7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7: dmi.product.name: Serval Professional dmi.product.version: serp7 dmi.sys.vendor: System76, Inc. --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pst007x4871 F pulseaudio /dev/snd/controlC0: pst007x4871 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=ed7653b8-c185-4b7d-a8e4-6dc07f73d3f1 InstallationDate: Installed on 2012-05-15 (525 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: System76, Inc. Serval Professional MarkForUpload: True Package: linux (not installed)
[Kernel-packages] [Bug 1196295] Re: lxc-start enters uninterruptible sleep
This looks to be the third case we hit with the same symptom (and likely for yet another reason). The complicating issue is that lxc containers make use of net namespaces and if those are released, references to I think the netdevice structures, are temporarily moved over to the loopback device. So anything going wrong with respect of references will show up like what you see (to add non mental note: bug 1021471 and bug 1065434). Since you say it takes 10-15hrs to hit it feels like this could again be a case of something rarely going on when the container is shut down which then causes a reference to not being dropped. Right now the range between 3.5.0-27 (maybe?) and 3.8.0-25 is quite vast. And at least up to 3.10 we can assume it has not been detected/fixed. So unlikely something that will be easy to spot. I know it is a lot of effort, but it would be really important to narrow down the version delta. If possible, I would suggest to use the mainline kernels to start of a rough manual bisection. http://kernel.ubuntu.com/~kernel-ppa/mainline/ -- 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/1196295 Title: lxc-start enters uninterruptible sleep Status in The Linux Kernel: Confirmed Status in “linux” package in Ubuntu: Confirmed Status in “lxc” package in Ubuntu: Confirmed Bug description: After running and terminating around 6000 containers overnight, something happened on my box that is affecting every new LXC container I try to start. The DEBUG log file looks like: lxc-start 1372615570.399 WARN lxc_start - inherited fd 9 lxc-start 1372615570.399 INFO lxc_apparmor - aa_enabled set to 1 lxc-start 1372615570.399 DEBUGlxc_conf - allocated pty '/dev/pts/302' (5/6) lxc-start 1372615570.399 DEBUGlxc_conf - allocated pty '/dev/pts/303' (7/8) lxc-start 1372615570.399 DEBUGlxc_conf - allocated pty '/dev/pts/304' (10/11) lxc-start 1372615570.399 DEBUGlxc_conf - allocated pty '/dev/pts/305' (12/13) lxc-start 1372615570.399 DEBUGlxc_conf - allocated pty '/dev/pts/306' (14/15) lxc-start 1372615570.399 DEBUGlxc_conf - allocated pty '/dev/pts/307' (16/17) lxc-start 1372615570.399 DEBUGlxc_conf - allocated pty '/dev/pts/308' (18/19) lxc-start 1372615570.399 DEBUGlxc_conf - allocated pty '/dev/pts/309' (20/21) lxc-start 1372615570.399 INFO lxc_conf - tty's configured lxc-start 1372615570.399 DEBUGlxc_start - sigchild handler set lxc-start 1372615570.399 INFO lxc_start - 'vm-59' is initialized lxc-start 1372615570.404 DEBUGlxc_start - Not dropping cap_sys_boot or watching utmp lxc-start 1372615570.404 INFO lxc_start - stored saved_nic #0 idx 12392 name vethP59 lxc-start 1372615570.404 INFO lxc_conf - opened /home/x/vm/vm-59.hold as fd 25 It stops there. In 'ps faux', it looks like: root 31621 0.0 0.0 25572 1272 ?D14:06 0:00 \_ lxc-start -n vm-59 -f /tmp/tmp.fG6T6ERZpS -l DEBUG -o /home/x/lxcdebug/vm-59.txt -- /usr/sbin/dropbear -F -E -m On a successful LXC run (prior to the server getting into this state), this hangs just before: lxc-start 1372394092.208 DEBUGlxc_cgroup - checking '/' (rootfs) lxc-start 1372394092.208 DEBUGlxc_cgroup - checking '/sys' (sysfs) lxc-start 1372394092.208 DEBUGlxc_cgroup - checking '/proc' (proc) lxc-start 1372394092.208 DEBUGlxc_cgroup - checking '/dev' (devtmpfs) lxc-start 1372394092.208 DEBUGlxc_cgroup - checking '/dev/pts' (devpts) lxc-start 1372394092.208 DEBUGlxc_cgroup - checking '/run' (tmpfs) lxc-start 1372394092.208 DEBUGlxc_cgroup - checking '/' (btrfs) lxc-start 1372394092.208 DEBUGlxc_cgroup - checking '/sys/fs/cgroup' (tmpfs) lxc-start 1372394092.208 DEBUGlxc_cgroup - checking '/sys/fs/cgroup/cpuset' (cgroup) lxc-start 1372394092.208 INFO lxc_cgroup - [1] found cgroup mounted at '/sys/fs/cgroup/cpuset',opts='rw,relatime,cpuset,clone_children' lxc-start 1372394092.208 DEBUGlxc_cgroup - get_init_cgroup: found init cgroup for subsys (null) at / It looks like a resource leak, but I'm not yet sure of what that would be. If it matters, I SIGKILL my lxc-start processes instead of using lxc- stop. Could that have any negative implications? Oh, and cgroups had almost 6000 entries for VMs that are long dead (I'm guessing it's due to my SIGKILL). I've run cgclear and my /sys/fs/cgroup/*/ dirs are now totally empty, but the new containers still hang. --- Architecture: amd64 DistroRelease: Ubuntu 13.04 MarkForUpload: True Package: lxc 0.9.0-0ubuntu3.3 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8
[Kernel-packages] [Bug 1178707] Re: Kernel Panics - ec2
I am sorry, I unfortunately got distracted by trying to finish some feature for the next release. And I must admit right now I have no good idea how to proceed. The pages that got dumped at least to me show no pattern that points to a certain process. You might be in a better position there since you know better what those instances are doing. The only vague suspect might be something that does asynchronous I/O (just because that would to a certain degree use anonymous pages which seem to be ending up on free lists incorrectly). If there was to be certain processes you would know to use aio and if that would be configurable, it would be worth trying to turn that off and see whether the instance survives. Or if there are independent tasks that cause some of the load and could be turned off and on, maybe it would become more obvious which direction to look. Though I doubt this is possible. -- 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/1178707 Title: Kernel Panics - ec2 Status in “linux” package in Ubuntu: Confirmed Bug description: Kernel Versions affected: 2.6.32-346-ec2 #51-Ubuntu 2.6.32-309-ec2 #18-Ubuntu SMP 3.0.0-32-virtual #51~lucid1-Ubuntu SMP 2.6.32-351-ec2 #64-Ubuntu SMP Description: Ubuntu 10.04.4 LTS Release: 10.04 We're seeing Kernel Panics across a variety of different instance types on AWS all running 10.04 on the following AMIs ami-da0cf8b3 ami-3fe54d56 We've tested with Various Kernels and still have had the issue. I've attached the console output from a few of the servers where the panics occur as well as the --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 10.04 Frequency: Once every few days. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: Package: linux (not installed) ProcCmdLine: root=LABEL=cloudimg-rootfs ro xencons=hvc0 console=hvc0 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcModules: acpiphp 23989 0 - Live 0xa000 ProcVersionSignature: Ubuntu 3.0.0-32.51~lucid1-virtual 3.0.69 Regression: No Reproducible: No Tags: lucid kconfig needs-upstream-testing Uname: Linux 3.0.0-32-virtual x86_64 UserGroups: --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 10.04 Frequency: Once every few days. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: Package: linux (not installed) ProcCmdLine: root=/dev/sda1 ro 4 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcModules: ipv6 293511 12 - Live 0xa000 ProcVersionSignature: Ubuntu 2.6.32-309.18-ec2 2.6.32.21+drm33.7 Regression: No Reproducible: No Tags: lucid kconfig needs-upstream-testing Uname: Linux 2.6.32-309-ec2 x86_64 UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178707/+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 1223920] Re: Documentation build error
** Also affects: linux (Ubuntu Precise) Importance: Undecided 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/1223920 Title: Documentation build error Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: New Bug description: Building documentation results in the following error: Error(/build/buildd/linux-3.5.0//include/linux/wait.h:621): cannot understand prototype:'wait_event_interruptible_lock_irq_timeout(wq, condition, lock, \ ' It looks like prototypes are expected to be defined in a single line. The following commit should fix this issue: commit 654784284430bf2739985914b65e09c7c35a7273 Author: Daniel Santos daniel.san...@pobox.com Date: Thu Oct 4 17:15:05 2012 -0700 kernel-doc: bugfix - multi-line macros Prior to this patch the following code breaks: /** * multiline_example - this breaks kernel-doc */ #define multiline_example( \ myparam) Producing this error: Error(somefile.h:983): cannot understand prototype: 'multiline_example( \ ' This patch fixes the issue by appending all lines ending in a blackslash (optionally followed by whitespace), removing the backslash and any whitespace after it prior to appending (just like the C pre-processor would). This fixes a break in kerel-doc introduced by the additions to rbtree.h. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-34-generic 3.5.0-34.55 ProcVersionSignature: Ubuntu 3.5.0-34.55-generic 3.5.7.13 Uname: Linux 3.5.0-34-generic x86_64 ApportVersion: 2.6.1-0ubuntu12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ubuntu 1681 F pulseaudio /dev/snd/controlC1: ubuntu 1681 F pulseaudio /dev/snd/controlC0: ubuntu 1681 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 15.377267] show_signal_msg: 57 callbacks suppressed [ 15.377272] colord-sane[1462]: segfault at 0 ip 7f0904e1d5d4 sp 7fffef3c7950 error 4 in libc-2.15.so[7f0904d62000+1b5000] [ 15.628049] end_request: I/O error, dev fd0, sector 0 [ 15.648073] end_request: I/O error, dev fd0, sector 0 [ 64.737929] gdbus[1675]: segfault at 20006 ip 7f9690b527d3 sp 7f96871cad80 error 4 in libglib-2.0.so.0.3400.1[7f9690b0b000+f5000] Date: Wed Sep 11 15:54:49 2013 HibernationDevice: RESUME=UUID=38974120-e8e1-4057-a8ba-999df156bb26 InstallationDate: Installed on 2012-12-19 (266 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Bochs Bochs MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-34-generic root=UUID=89a7e0f5-d420-4ddd-8958-c23dafbc8746 ro console=ttyS0 RelatedPackageVersions: linux-restricted-modules-3.5.0-34-generic N/A linux-backports-modules-3.5.0-34-generic N/A linux-firmware1.95.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223920/+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 1197451] Re: Ubuntu fails to properly boot on Macbook Air 2013 6, 1 6, 2
** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Triaged -- 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/1197451 Title: Ubuntu fails to properly boot on Macbook Air 2013 6,1 6,2 Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Precise: Triaged Status in “linux” source package in Quantal: Triaged Status in “linux” source package in Raring: Triaged Status in “linux” source package in Saucy: Triaged Bug description: Ubuntu fails to properly boot on Macbook Air 2013 6,1 Ubuntu fails to boot the 13.10 live image from usb without specifying acpi-off as a boot parameter. After installation is complete the boot process hangs at a purple screen. Booting into recovery mode shows that the process stops at the following: smpboot: Booting Node 0, #1 I've tried 12.04.2, 13.04, and 13.10. I've also tried booting with kernel ver 3.9.8-030908-generic and the result is the same. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.10.0-2-generic 3.10.0-2.9 ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2885 F pulseaudio /dev/snd/controlC0: ubuntu 2885 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.335 Date: Wed Jul 3 15:31:42 2013 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 13.10 Saucy Salamander - Alpha amd64+mac (20130703) MachineType: Apple Inc. MacBookAir6,1 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed boot=casper quiet splash acpi=off BOOT_IMAGE=/casper/vmlinuz RelatedPackageVersions: linux-restricted-modules-3.10.0-2-generic N/A linux-backports-modules-3.10.0-2-generic N/A linux-firmware1.110 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0099.B00.1305241529 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-35C1E88140C3E6CF dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-35C1E88140C3E6CF dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B00.1305241529:bd05/24/2013:svnAppleInc.:pnMacBookAir6,1:pvr1.0:rvnAppleInc.:rnMac-35C1E88140C3E6CF:rvrMacBookAir6,1:cvnAppleInc.:ct10:cvrMac-35C1E88140C3E6CF: dmi.product.name: MacBookAir6,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1197451/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
As it seemed that starting a 64bit hypervisor (qemu-system-x86_64) from a 32bit user-space running on another 64bit hypervisor has different issues which seem to go back even further, I concentrated on bisecting the case of host running 64bit user-space on a 64bit CPU and the first level guest running 64bit user-space under a 64bit hypervisor. The second level guest is started with a 64bit hypervisor but a 32bit userspace. All host and guests are Saucy and started with the same kernel. Then for bisecting I only replaced the host kernel with kernels between v3.9 and v3.10. Then started a guest and ran the prepare-testbed repeatedly. The first change that broke things was: commit 5f3d5799974b89100268ba813cec8db7bd0693fb KVM: nVMX: Rework event injection and recovery However at that point starting a 2nd level guest is completely broken until: commit 5a2892ce72e010e3cb96b438d7cdddce0c88e0e6 KVM: nVMX: Skip PF interception check when queuing during nested run So potentially the rework patch broke things and the current issue is remaining after fixing the major issues. Though it could be introduced by one of the patches in between but it cannot be bisected. -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM Status in “linux” package in Ubuntu: In Progress Status in “qemu-kvm” package in Ubuntu: New Status in “linux” source package in Saucy: In Progress Status in “qemu-kvm” source package in Saucy: New Bug description: Attempting to run apt-get in a nested vm hosted in OpenStack results in a general protection fault in the kernel in the nested VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
Btw, James, this means there is a simple but not very helpful work- around for Saucy: use AMD CPU based hosts. Did not check for 32bit user- space on 1rst level but with 64bit and had no issues. Not very surprising as the regression seems to be in the nested VMX code. But also not very useful when working in the cloud... -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM Status in “linux” package in Ubuntu: In Progress Status in “qemu-kvm” package in Ubuntu: New Status in “linux” source package in Saucy: In Progress Status in “qemu-kvm” source package in Saucy: New Bug description: Attempting to run apt-get in a nested vm hosted in OpenStack results in a general protection fault in the kernel in the nested VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New = Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: vsftpd (Ubuntu) Status: Confirmed = Invalid -- 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/1313450 Title: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration Status in “linux” package in Ubuntu: Confirmed Status in “vsftpd” package in Ubuntu: Invalid Bug description: The configuration submitted was modified during testing, but this also failed with the default configuration. The only solution I have found so far was to delete the configuration, this would allow the service to start, but obviously not work as intended. If I try to start the service manually using vsftpd or sudo vsftpd I receive the following error message: 500 OOPS: munmap I also tried the default commands /etc/init.d/vsftpd or service vsftpd start ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: vsftpd 3.0.2-1ubuntu2 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 27 21:23:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: t1.micro Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vsftpd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.vsftpd.conf: [modified] mtime.conffile..etc.vsftpd.conf: 2014-04-27T21:16:28.222467 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: t1.micro Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable Package: vsftpd 3.0.2-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Tags: trusty ec2-images Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True modified.conffile..etc.vsftpd.conf: [modified] mtime.conffile..etc.vsftpd.conf: 2014-04-29T19:03:28.834467 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313450/+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 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration
As far as I can see from the upstream discussion this is indeed a kernel issue. Initially it was intended to be fixed by Author: Mel Gorman mgor...@suse.de xen: properly account for _PAGE_NUMA during xen pte translations ... Steven Noonan forwarded a users report where they had a problem starting vsftpd on a Xen paravirtualized guest, with this in dmesg: BUG: Bad page map in process vsftpd pte:800493b88165 pmd:e9cc01067 ... However the patch got reverted later (which also made it back into 14.04 via stable because it caused regressions on migration. With v3.15-rc2 there was a new change to address this: commit 29c7787075c92ca8af353acd5301481e6f37082f Author: Mel Gorman mgor...@suse.de mm: use paravirt friendly ops for NUMA hinting ptes It looks that change (while tagged for stable) has not yet been picked up for 3.13. -- 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/1313450 Title: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration Status in “linux” package in Ubuntu: Confirmed Status in “vsftpd” package in Ubuntu: Invalid Bug description: The configuration submitted was modified during testing, but this also failed with the default configuration. The only solution I have found so far was to delete the configuration, this would allow the service to start, but obviously not work as intended. If I try to start the service manually using vsftpd or sudo vsftpd I receive the following error message: 500 OOPS: munmap I also tried the default commands /etc/init.d/vsftpd or service vsftpd start ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: vsftpd 3.0.2-1ubuntu2 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 27 21:23:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: t1.micro Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vsftpd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.vsftpd.conf: [modified] mtime.conffile..etc.vsftpd.conf: 2014-04-27T21:16:28.222467 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: t1.micro Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable Package: vsftpd 3.0.2-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Tags: trusty ec2-images Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True modified.conffile..etc.vsftpd.conf: [modified] mtime.conffile..etc.vsftpd.conf: 2014-04-29T19:03:28.834467 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313450/+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 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration
** Also affects: vsftpd (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Importance: Undecided = High ** Changed in: linux (Ubuntu Trusty) Status: New = Confirmed ** Changed in: vsftpd (Ubuntu Trusty) Status: New = Invalid -- 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/1313450 Title: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration Status in “linux” package in Ubuntu: Confirmed Status in “vsftpd” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Confirmed Status in “vsftpd” source package in Trusty: Invalid Bug description: The configuration submitted was modified during testing, but this also failed with the default configuration. The only solution I have found so far was to delete the configuration, this would allow the service to start, but obviously not work as intended. If I try to start the service manually using vsftpd or sudo vsftpd I receive the following error message: 500 OOPS: munmap I also tried the default commands /etc/init.d/vsftpd or service vsftpd start ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: vsftpd 3.0.2-1ubuntu2 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 27 21:23:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: t1.micro Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vsftpd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.vsftpd.conf: [modified] mtime.conffile..etc.vsftpd.conf: 2014-04-27T21:16:28.222467 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: t1.micro Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable Package: vsftpd 3.0.2-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Tags: trusty ec2-images Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True modified.conffile..etc.vsftpd.conf: [modified] mtime.conffile..etc.vsftpd.conf: 2014-04-29T19:03:28.834467 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313450/+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 1317811] Re: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots
Could be interesting to find out whether on a m1.small the issue does not occur (although that still could be resulting from other differences in the setup than mtu). Not sure how AWS manages to cause the instance to come up with a different mtu either. In my experiments I had a normal bridge on the host set to 9000 and the guest still had 1500. Though I do not know how the network is set up in EC2 in detail (could be openvswitch). Generally the issue is that something seems to cause packets with a large data buffer. One slot in the xen-net driver is a 4k page. The limit is 18 slots. Anything above that causes the observed message and the packet to be dropped. The host side would have another limit of (usually) 20 slots on which it would assume a malicious guest and disrupts the connection. But since the guest drops at 17 or above the host should never see that number. Unfortunately I am not that deeply understanding the network code, so I will have to ask upstream. As far as I understand a socket buffer can consist of of multiple fragments (kind of a scatter gather list). There is a definition in the code that sets a limit to the number of fragments based on a maximum frame size of 64K. This results in 17 frags (for 4K pages that is 16 + 1 to handle data not starting at page boundary). The Xen driver counts the length of the memory area in all frags (if data in a frag starts at an offset that is added, the code does that for every frag, the question would be whether in theory each frag would be allowed to have an offset because that might add up to more than one page). To the number of pages needed for the frags, the driver then adds the number of pages (can that be more than one?) needed for the header. If that is bigger than 18 (17 for frag + 1 for header?) the rides the rocket error happens. This leaves a few question marks for me: the memory associated with a frag can be a compound page, so I would think that the length might be greater than 4K. I have no clue, yet, how compound pages exactly come into play. Is the 64K limit still enforced by a limit of the number of frags? Can each frag data begin at some offset (and end with more than one page of overall overhead)? Apparently the header can start at some offset, too. So worst case (assuming header length to be less than 4K), if the offset is quite big, that could end up requiring 2 pages. Then if the frag data happens to use up its 17 pages limit, we just would end up hitting the 19 pages failure size. -- 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/1317811 Title: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots Status in “linux” package in Ubuntu: Confirmed Bug description: Running Ubuntu 14.04 LTS on EC2, we see a lot of the following in the kernel log: xen_netfront: xennet: skb rides the rocket: 19 slots Each of these messages corresponds to a dropped TX packet, and eventually causes our application's connections to break and timeout. The problem appears when network load increases. We have Node.js processes doing pubsub with a Redis server, and these are most visibly affected, showing frequent connection loss. The processes talk to each other using the private addresses EC2 allocates to the machines. Notably, the default MTU on the network interface seems to have gone up from 1500 on 13.10, to 9000 in 14.04 LTS. Reducing the MTU back to 1500 seems to drastically reduce dropped packets. (Can't say for certain if it completely eliminates the problem.) The machines we run are started from ami-896c96fe. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:01 seq crw-rw 1 root audio 116, 33 May 9 09:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 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: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri May 9 09:11:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A
[Kernel-packages] [Bug 1317811] Re: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots
Thinking about this, I could build a debug kernel to which I add code to print out the layout of the socket buffer when the size check fails. Stéphan, would you be able to run that on a setup that shows the failures? -- 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/1317811 Title: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots Status in “linux” package in Ubuntu: Confirmed Bug description: Running Ubuntu 14.04 LTS on EC2, we see a lot of the following in the kernel log: xen_netfront: xennet: skb rides the rocket: 19 slots Each of these messages corresponds to a dropped TX packet, and eventually causes our application's connections to break and timeout. The problem appears when network load increases. We have Node.js processes doing pubsub with a Redis server, and these are most visibly affected, showing frequent connection loss. The processes talk to each other using the private addresses EC2 allocates to the machines. Notably, the default MTU on the network interface seems to have gone up from 1500 on 13.10, to 9000 in 14.04 LTS. Reducing the MTU back to 1500 seems to drastically reduce dropped packets. (Can't say for certain if it completely eliminates the problem.) The machines we run are started from ami-896c96fe. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:01 seq crw-rw 1 root audio 116, 33 May 9 09:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 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: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri May 9 09:11:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:54 seq crw-rw 1 root audio 116, 33 May 9 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 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: [Errno 2] No such file or directory CurrentDmesg: [ 24.724129] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317811/+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 1317811] Re: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots
Thanks for the additional info. Definitely the relation to MTU size sounds quite plausible. The checking is on traffic from the guest out and that I would expect to be affected by MTU together with GSO support. And yes, preferably we find a reproducer that does not require a production system to suffer. And ideally for me if I could do so on a local test system to understand the host side. I will try to figure out more details from a stock c3.large if that is possible and maybe whether something like iperf can trigger it there. -- 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/1317811 Title: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots Status in “linux” package in Ubuntu: Confirmed Bug description: Running Ubuntu 14.04 LTS on EC2, we see a lot of the following in the kernel log: xen_netfront: xennet: skb rides the rocket: 19 slots Each of these messages corresponds to a dropped TX packet, and eventually causes our application's connections to break and timeout. The problem appears when network load increases. We have Node.js processes doing pubsub with a Redis server, and these are most visibly affected, showing frequent connection loss. The processes talk to each other using the private addresses EC2 allocates to the machines. Notably, the default MTU on the network interface seems to have gone up from 1500 on 13.10, to 9000 in 14.04 LTS. Reducing the MTU back to 1500 seems to drastically reduce dropped packets. (Can't say for certain if it completely eliminates the problem.) The machines we run are started from ami-896c96fe. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:01 seq crw-rw 1 root audio 116, 33 May 9 09:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 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: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri May 9 09:11:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:54 seq crw-rw 1 root audio 116, 33 May 9 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 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: [Errno 2] No such file or directory CurrentDmesg: [ 24.724129] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317811/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1317811] Re: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots
Yes, the kernel would be a set of dpkg files to be installed via 'dpkg -i'. Of course I still have to code that up. If I can reproduce it with your instructions locally then even better (would cut down turnaround times). Otherwise I can start up some EC2 instances, too. Good to have a simple way to trigger it. Not like some other issues that only happen under production conditions. -- 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/1317811 Title: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots Status in “linux” package in Ubuntu: Confirmed Bug description: Running Ubuntu 14.04 LTS on EC2, we see a lot of the following in the kernel log: xen_netfront: xennet: skb rides the rocket: 19 slots Each of these messages corresponds to a dropped TX packet, and eventually causes our application's connections to break and timeout. The problem appears when network load increases. We have Node.js processes doing pubsub with a Redis server, and these are most visibly affected, showing frequent connection loss. The processes talk to each other using the private addresses EC2 allocates to the machines. Notably, the default MTU on the network interface seems to have gone up from 1500 on 13.10, to 9000 in 14.04 LTS. Reducing the MTU back to 1500 seems to drastically reduce dropped packets. (Can't say for certain if it completely eliminates the problem.) The machines we run are started from ami-896c96fe. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:01 seq crw-rw 1 root audio 116, 33 May 9 09:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 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: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri May 9 09:11:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:54 seq crw-rw 1 root audio 116, 33 May 9 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 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: [Errno 2] No such file or directory CurrentDmesg: [ 24.724129] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1317811] Re: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots
Good news, the reproducer works on my local system, too. Thanks. :) -- 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/1317811 Title: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots Status in “linux” package in Ubuntu: Confirmed Bug description: Running Ubuntu 14.04 LTS on EC2, we see a lot of the following in the kernel log: xen_netfront: xennet: skb rides the rocket: 19 slots Each of these messages corresponds to a dropped TX packet, and eventually causes our application's connections to break and timeout. The problem appears when network load increases. We have Node.js processes doing pubsub with a Redis server, and these are most visibly affected, showing frequent connection loss. The processes talk to each other using the private addresses EC2 allocates to the machines. Notably, the default MTU on the network interface seems to have gone up from 1500 on 13.10, to 9000 in 14.04 LTS. Reducing the MTU back to 1500 seems to drastically reduce dropped packets. (Can't say for certain if it completely eliminates the problem.) The machines we run are started from ami-896c96fe. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:01 seq crw-rw 1 root audio 116, 33 May 9 09:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 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: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri May 9 09:11:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:54 seq crw-rw 1 root audio 116, 33 May 9 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 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: [Errno 2] No such file or directory CurrentDmesg: [ 24.724129] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317811/+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 1317811] Re: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots
** Changed in: linux (Ubuntu) Status: Confirmed = In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Stefan Bader (smb) -- 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/1317811 Title: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots Status in “linux” package in Ubuntu: In Progress Bug description: Running Ubuntu 14.04 LTS on EC2, we see a lot of the following in the kernel log: xen_netfront: xennet: skb rides the rocket: 19 slots Each of these messages corresponds to a dropped TX packet, and eventually causes our application's connections to break and timeout. The problem appears when network load increases. We have Node.js processes doing pubsub with a Redis server, and these are most visibly affected, showing frequent connection loss. The processes talk to each other using the private addresses EC2 allocates to the machines. Notably, the default MTU on the network interface seems to have gone up from 1500 on 13.10, to 9000 in 14.04 LTS. Reducing the MTU back to 1500 seems to drastically reduce dropped packets. (Can't say for certain if it completely eliminates the problem.) The machines we run are started from ami-896c96fe. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:01 seq crw-rw 1 root audio 116, 33 May 9 09:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 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: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri May 9 09:11:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:54 seq crw-rw 1 root audio 116, 33 May 9 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 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: [Errno 2] No such file or directory CurrentDmesg: [ 24.724129] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317811/+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 1317811] Re: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots
So with the added debugging and running the reproducer with the outside bridge (and so the vifs) and the PV guests eth0 set to 9001 (as seen on EC2), I get the following (format is length@offset): [ 698.108119] xen_netfront: xennet: skb rides the rocket: 19 slots [ 698.108134] header 1490@238 - 1 slots [ 698.108139] frag #0 1614@2164 - + 1 pages [ 698.108143] frag #1 3038@1296 - + 2 pages [ 698.108147] frag #2 6076@1852 - + 2 pages [ 698.108151] frag #3 6076@292 - + 2 pages [ 698.108156] frag #4 6076@2828 - + 3 pages [ 698.108160] frag #5 3038@1268 - + 2 pages [ 698.108164] frag #6 2272@1824 - + 1 pages [ 698.108168] frag #7 3804@0 - + 1 pages [ 698.108172] frag #8 6076@264 - + 2 pages [ 698.108177] frag #9 3946@2800 - + 2 pages [ 698.108180] frags adding 18 slots So multiple frags can point to a compound page and also start at an offset. Which makes either the assumption about the size required to handle N frags is wrong or whatever creates that buffer... -- 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/1317811 Title: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots Status in “linux” package in Ubuntu: In Progress Bug description: Running Ubuntu 14.04 LTS on EC2, we see a lot of the following in the kernel log: xen_netfront: xennet: skb rides the rocket: 19 slots Each of these messages corresponds to a dropped TX packet, and eventually causes our application's connections to break and timeout. The problem appears when network load increases. We have Node.js processes doing pubsub with a Redis server, and these are most visibly affected, showing frequent connection loss. The processes talk to each other using the private addresses EC2 allocates to the machines. Notably, the default MTU on the network interface seems to have gone up from 1500 on 13.10, to 9000 in 14.04 LTS. Reducing the MTU back to 1500 seems to drastically reduce dropped packets. (Can't say for certain if it completely eliminates the problem.) The machines we run are started from ami-896c96fe. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:01 seq crw-rw 1 root audio 116, 33 May 9 09:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 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: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri May 9 09:11:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:54 seq crw-rw 1 root audio 116, 33 May 9 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 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: [Errno 2] No such file or directory CurrentDmesg: [ 24.724129] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill:
[Kernel-packages] [Bug 1319244] Re: iostat: Cannot open /proc/stat: Cannot allocate memory
It looks like two things at play: 1. Something in the way the system is set up seems to the DMA/DMA32 pool under higher pressure 2. Reading /proc/stat ends up requesting a 64kB memory area (order-4) in the DMA32 pool on node0 While there are still two elements in the 64kB slot, they both are emergency reserve, which open_stat did not ask for. So while there is not much that can easily be done about the memory pressure in general, it looks like open_stat could very well be more conservative about its memory requirement. First the calculation reserves 128 bytes for each possible cpu, while the actual output only produces one line of overall stats, plus one for each online cpu. So it seems to make sense to use the number of online cpus for the allocation. Second the upper limit for the buffer is set to the maximum that kmalloc can do. However it is known that anything beyond order-3 allocations (32kB) are costly and prone to fail due to memory pressure. And having a smaller buffer is not world ending for the stat output either. Since the proc file uses the seq_file functions it only would cause more read calls instead of filling all stats into one single buffer. ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Stefan Bader (smb) -- 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/1319244 Title: iostat: Cannot open /proc/stat: Cannot allocate memory Status in “linux” package in Ubuntu: Confirmed Bug description: Intermitently I get errors stating that various programs cannot allocate memory when reading /proc/stat I have 2 servers that are affected by the issue. Probably a duplicate of 1226172 [1764593.455329] top: page allocation failure: order:4, mode:0x1040d0 [1764593.455335] CPU: 3 PID: 10323 Comm: top Tainted: GF O 3.11.0-18-generic #32-Ubuntu [1764593.455338] Hardware name: Intel Corporation S2400SC/S2400SC, BIOS SE5C600.86B.02.02.0002.122320131210 12/23/2013 [1764593.455340] 88042670b9d0 816e8571 001040d0 [1764593.455345] 88042670ba58 81144ae0 880a3fffcb48 [1764593.455348] 000e 88042670ba28 0040 0007 [1764593.455351] Call Trace: [1764593.455361] [816e8571] dump_stack+0x45/0x56 [1764593.455367] [81144ae0] warn_alloc_failed+0xf0/0x140 [1764593.455371] [81148a15] __alloc_pages_nodemask+0x725/0x920 [1764593.455376] [81184589] alloc_pages_current+0xa9/0x160 [1764593.455379] [81143bfe] __get_free_pages+0xe/0x50 [1764593.455384] [8118d75e] kmalloc_order_trace+0x2e/0xa0 [1764593.455388] [811c9960] ? single_open+0xb0/0xb0 [1764593.455391] [8118ee19] __kmalloc+0x159/0x180 [1764593.455393] [811c9960] ? single_open+0xb0/0xb0 [1764593.455398] [81213c10] stat_open+0x50/0xc0 [1764593.455401] [8120a700] proc_reg_open+0x70/0x110 [1764593.455405] [811a5d4b] do_dentry_open+0x1eb/0x280 [1764593.455408] [8120a690] ? proc_reg_release+0x70/0x70 [1764593.455411] [811a5e69] vfs_open+0x49/0x50 [1764593.455415] [811b5e13] do_last+0x1c3/0xe50 [1764593.455418] [8118e5d8] ? kmem_cache_alloc_trace+0x108/0x130 [1764593.455421] [811b6b61] path_openat+0xc1/0x630 [1764593.455426] [811689d9] ? handle_mm_fault+0x299/0x670 [1764593.455429] [811b7eda] do_filp_open+0x3a/0x90 [1764593.455433] [816ef78e] ? _raw_spin_lock+0xe/0x20 [1764593.455437] [811c4847] ? __alloc_fd+0xa7/0x130 [1764593.455440] [811a704c] do_sys_open+0x12c/0x270 [1764593.455445] [81074989] ? __set_current_blocked+0x49/0x60 [1764593.455448] [811a71ae] SyS_open+0x1e/0x20 [1764593.455452] [816f841d] system_call_fastpath+0x1a/0x1f [1764593.455454] Mem-Info: [1764593.455455] Node 0 DMA per-cpu: [1764593.455458] CPU0: hi:0, btch: 1 usd: 0 [1764593.455459] CPU1: hi:0, btch: 1 usd: 0 [1764593.455461] CPU2: hi:0, btch: 1 usd: 0 [1764593.455462] CPU3: hi:0, btch: 1 usd: 0 [1764593.455463] CPU4: hi:0, btch: 1 usd: 0 [1764593.455465] CPU5: hi:0, btch: 1 usd: 0 [1764593.455466] CPU6: hi:0, btch: 1 usd: 0 [1764593.455468] CPU7: hi:0, btch: 1 usd: 0 [1764593.455469] Node 0 DMA32 per-cpu: [1764593.455471] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455472] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455474] CPU2: hi: 186, btch: 31 usd: 0 [1764593.455475] CPU3: hi: 186, btch: 31 usd: 0 [1764593.455477] CPU4: hi: 186, btch: 31 usd: 0 [1764593.455478] CPU5: hi: 186, btch: 31 usd: 0 [1764593.455480] CPU6: hi: 186
[Kernel-packages] [Bug 1319244] Re: iostat: Cannot open /proc/stat: Cannot allocate memory
This would be the proposed way of fixing the issue. I took a current 3.11 kernel version with the patch applied and prepared packages which can be found at http://people.canonical.com/~smb/lp1319244/ Please could you try how this works on your system and report back here with the results? Thanks. ** Patch added: Proposed fix https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1319244/+attachment/4112313/+files/0001-UBUNTU-SAUCE-fs-stat-Reduce-memory-requirements-for-.patch -- 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/1319244 Title: iostat: Cannot open /proc/stat: Cannot allocate memory Status in “linux” package in Ubuntu: Confirmed Bug description: Intermitently I get errors stating that various programs cannot allocate memory when reading /proc/stat I have 2 servers that are affected by the issue. Probably a duplicate of 1226172 [1764593.455329] top: page allocation failure: order:4, mode:0x1040d0 [1764593.455335] CPU: 3 PID: 10323 Comm: top Tainted: GF O 3.11.0-18-generic #32-Ubuntu [1764593.455338] Hardware name: Intel Corporation S2400SC/S2400SC, BIOS SE5C600.86B.02.02.0002.122320131210 12/23/2013 [1764593.455340] 88042670b9d0 816e8571 001040d0 [1764593.455345] 88042670ba58 81144ae0 880a3fffcb48 [1764593.455348] 000e 88042670ba28 0040 0007 [1764593.455351] Call Trace: [1764593.455361] [816e8571] dump_stack+0x45/0x56 [1764593.455367] [81144ae0] warn_alloc_failed+0xf0/0x140 [1764593.455371] [81148a15] __alloc_pages_nodemask+0x725/0x920 [1764593.455376] [81184589] alloc_pages_current+0xa9/0x160 [1764593.455379] [81143bfe] __get_free_pages+0xe/0x50 [1764593.455384] [8118d75e] kmalloc_order_trace+0x2e/0xa0 [1764593.455388] [811c9960] ? single_open+0xb0/0xb0 [1764593.455391] [8118ee19] __kmalloc+0x159/0x180 [1764593.455393] [811c9960] ? single_open+0xb0/0xb0 [1764593.455398] [81213c10] stat_open+0x50/0xc0 [1764593.455401] [8120a700] proc_reg_open+0x70/0x110 [1764593.455405] [811a5d4b] do_dentry_open+0x1eb/0x280 [1764593.455408] [8120a690] ? proc_reg_release+0x70/0x70 [1764593.455411] [811a5e69] vfs_open+0x49/0x50 [1764593.455415] [811b5e13] do_last+0x1c3/0xe50 [1764593.455418] [8118e5d8] ? kmem_cache_alloc_trace+0x108/0x130 [1764593.455421] [811b6b61] path_openat+0xc1/0x630 [1764593.455426] [811689d9] ? handle_mm_fault+0x299/0x670 [1764593.455429] [811b7eda] do_filp_open+0x3a/0x90 [1764593.455433] [816ef78e] ? _raw_spin_lock+0xe/0x20 [1764593.455437] [811c4847] ? __alloc_fd+0xa7/0x130 [1764593.455440] [811a704c] do_sys_open+0x12c/0x270 [1764593.455445] [81074989] ? __set_current_blocked+0x49/0x60 [1764593.455448] [811a71ae] SyS_open+0x1e/0x20 [1764593.455452] [816f841d] system_call_fastpath+0x1a/0x1f [1764593.455454] Mem-Info: [1764593.455455] Node 0 DMA per-cpu: [1764593.455458] CPU0: hi:0, btch: 1 usd: 0 [1764593.455459] CPU1: hi:0, btch: 1 usd: 0 [1764593.455461] CPU2: hi:0, btch: 1 usd: 0 [1764593.455462] CPU3: hi:0, btch: 1 usd: 0 [1764593.455463] CPU4: hi:0, btch: 1 usd: 0 [1764593.455465] CPU5: hi:0, btch: 1 usd: 0 [1764593.455466] CPU6: hi:0, btch: 1 usd: 0 [1764593.455468] CPU7: hi:0, btch: 1 usd: 0 [1764593.455469] Node 0 DMA32 per-cpu: [1764593.455471] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455472] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455474] CPU2: hi: 186, btch: 31 usd: 0 [1764593.455475] CPU3: hi: 186, btch: 31 usd: 0 [1764593.455477] CPU4: hi: 186, btch: 31 usd: 0 [1764593.455478] CPU5: hi: 186, btch: 31 usd: 0 [1764593.455480] CPU6: hi: 186, btch: 31 usd: 0 [1764593.455481] CPU7: hi: 186, btch: 31 usd: 0 [1764593.455482] Node 0 Normal per-cpu: [1764593.455484] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455485] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455487] CPU2: hi: 186, btch: 31 usd: 0 [1764593.455488] CPU3: hi: 186, btch: 31 usd: 0 [1764593.455490] CPU4: hi: 186, btch: 31 usd: 0 [1764593.455491] CPU5: hi: 186, btch: 31 usd: 0 [1764593.455492] CPU6: hi: 186, btch: 31 usd: 0 [1764593.455494] CPU7: hi: 186, btch: 31 usd: 0 [1764593.455495] Node 1 Normal per-cpu: [1764593.455497] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455498] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455500] CPU2: hi: 186, btch: 31 usd: 0 [1764593.455501] CPU3: hi: 186,
[Kernel-packages] [Bug 1317811] Re: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots
Playing around with this, I actually found an even simpler way to trigger the issue: PV guest #1: Install redis-server (and enable eth0 ip in config) PV guest #2: Install redis-tools and run 'redis-benchmark -q -h PV guest #1 IP -d 1000' The MTU size turns out to be irrelevant, this even happens with 1500 during the batch request tests. What does make a difference is to prevent scatter gather as it was reported in another bug about this (on any host that sees the rides the rocket message: sudo ethtool -K eth0 sg off I discussed the issue upstream and the driver should handle this case without dropping the request. It might be a bit complicated so I cannot give an ETA on the fix right 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/1317811 Title: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots Status in “linux” package in Ubuntu: In Progress Bug description: Running Ubuntu 14.04 LTS on EC2, we see a lot of the following in the kernel log: xen_netfront: xennet: skb rides the rocket: 19 slots Each of these messages corresponds to a dropped TX packet, and eventually causes our application's connections to break and timeout. The problem appears when network load increases. We have Node.js processes doing pubsub with a Redis server, and these are most visibly affected, showing frequent connection loss. The processes talk to each other using the private addresses EC2 allocates to the machines. Notably, the default MTU on the network interface seems to have gone up from 1500 on 13.10, to 9000 in 14.04 LTS. Reducing the MTU back to 1500 seems to drastically reduce dropped packets. (Can't say for certain if it completely eliminates the problem.) The machines we run are started from ami-896c96fe. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:01 seq crw-rw 1 root audio 116, 33 May 9 09:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 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: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri May 9 09:11:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:54 seq crw-rw 1 root audio 116, 33 May 9 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 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: [Errno 2] No such file or directory CurrentDmesg: [ 24.724129] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True To manage
[Kernel-packages] [Bug 1317811] Re: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots
Oh, ok. It does work quite well on my local guests that come up with 1500 MTU. Maybe the EC2 guests would need a bigger data size value than 1000. But yeah, as long as I have some way to verify whatever comes up to fix this, it is ok. Yes, the loss of jumbo frames was expected. As long as high throughput is not critical it is at least good enough as a work-around. About a upstream discussion: http://www.spinics.net/lists/netdev/msg282340.html Basically it looks like the problem was kind of known but probably did not happens often enough. Or actually complicated to fix. It appears that other drivers will not have that issue as long as the limit is in the actual transfer size and not in the number of pages required to accommodate the frags/scatter gather list. Unfortunately Xen has a limit there that guests have to impose because otherwise the host side driver would shut down the connection completely. -- 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/1317811 Title: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots Status in “linux” package in Ubuntu: In Progress Bug description: Running Ubuntu 14.04 LTS on EC2, we see a lot of the following in the kernel log: xen_netfront: xennet: skb rides the rocket: 19 slots Each of these messages corresponds to a dropped TX packet, and eventually causes our application's connections to break and timeout. The problem appears when network load increases. We have Node.js processes doing pubsub with a Redis server, and these are most visibly affected, showing frequent connection loss. The processes talk to each other using the private addresses EC2 allocates to the machines. Notably, the default MTU on the network interface seems to have gone up from 1500 on 13.10, to 9000 in 14.04 LTS. Reducing the MTU back to 1500 seems to drastically reduce dropped packets. (Can't say for certain if it completely eliminates the problem.) The machines we run are started from ami-896c96fe. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:01 seq crw-rw 1 root audio 116, 33 May 9 09:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 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: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri May 9 09:11:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:54 seq crw-rw 1 root audio 116, 33 May 9 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 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: [Errno 2] No such file or directory CurrentDmesg: [ 24.724129] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images
[Kernel-packages] [Bug 1218959] Re: KVM virbr# no longer forwards multicast traffic by default (U12.04)
Serge, looks like we need to be careful with those two. At least one of them: bridge: only expire the mdb entry when query is received was reverted with 3.12. The commit message looks a bit like they might have packed several reverts into one. And it references bridge: disable snooping if there is no querier as the one making the reverted stuff obsolete. -- 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/1218959 Title: KVM virbr# no longer forwards multicast traffic by default (U12.04) Status in “libvirt” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Incomplete Status in “libvirt” source package in Precise: Confirmed Status in “linux” source package in Precise: Incomplete Bug description: A recent kernel update (Apr 2013) has made it's way to U12.04.2 LTS (approx June-Aug 2013) and has stopped the (default) behaviour of automatically forwarding multicast traffic over virbr#. Some updates the bridge subsystem now, by default, disable multicast traffic without IGMP Querier being enabled on that bridge. The corresponding Fedora/RHEL bug tracks the progress/updates of this specific change in relation to Fedora. https://bugzilla.redhat.com/show_bug.cgi?id=880035 (I have yet to find a similar bug report in Ubuntu so I have created this bug to help the Ubuntu community identify multicast issues that may arise since April 2013 in U12.04 LTS and presumably other Ubuntu releases as backports are made and break regression testing.) Using the latest patches in U12.04.2 LTS this following addition, with some modifications, can be made to the udev rules will enable multicast on virbr# bridge: https://bugzilla.redhat.com/show_bug.cgi?id=880035#c38 While this is an improvement/correction to KVM bridge networking it has broken existing functionality in U12.04.2 LTS and broke regressed functionality that once worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1218959/+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 1244176] Re: Server 13.10 Install Fails with USB Keyboard (Appears to Hang)
But the Trusty kernel has the CONFIG_USB_OHCI_HCD_PCI=y set (which was the problem reported here) and I just checked the iso with the virtual keyboard/monitor over lan which was failing before. And that is reacting on the keyboard. Michael, from the little info in your comment its unclear whether there was a kernel panic and a resulting hang or just the usb keyboard had an issue. But since things seem to work here, it is very likely a different issue to this. Could you file a new bug (ubuntu-bug linux from the live iso, then you can manually update the report with the details of the server install). Subscribe me to the new report, then I will see it. And add more details on how this happens (always the same place, a certain menu or when). Thanks. -- 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/1244176 Title: Server 13.10 Install Fails with USB Keyboard (Appears to Hang) Status in “initramfs-tools” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Fix Released Status in “initramfs-tools” source package in Saucy: Invalid Status in “linux” source package in Saucy: Fix Released Status in “initramfs-tools” source package in Trusty: Invalid Status in “linux” source package in Trusty: Fix Released Bug description: A fresh install of Server 13.10 on old hardware fails when a USB keyboard is present. The installation succeeds when a PS/2 keyboard is installed. The installation appears to hang at the third screen, which is Select Language. The screen does not respond to keyboard or mouse events. The issue was experienced independently on HP/Compag dc5850 with Athlon X2 2.3 GHz dual core, 4GB RAM; and DELL Optiplex 755. See Server 13.10 Install Hangs, http://askubuntu.com/questions/364945/server-13-10-install- hangs/364949. The issue was not present on Server 12.04.3 LTS or 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1244176/+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 1304001] Re: xen:balloon errors in 14.04 beta
I would think Boris is after memory related special settings on the host and guest (if you can reveal those). Could be you are hinting that at least for the host the config was not modified. I assume still using the xm/xend stack. The other info there would be the number assigned to mem of guest type like the one we have the dmesg of. Boris, do you think it would help you to get the dyndbg enabled output? -- 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/1304001 Title: xen:balloon errors in 14.04 beta Status in “linux” package in Ubuntu: Confirmed Bug description: Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: -- pirq=16 - irq=8 (gsi=8) [0.562622] xen: -- pirq=17 - irq=12 (gsi=12) [0.562649] xen: -- pirq=18 - irq=1 (gsi=1) [0.562673] xen: -- pirq=19 - irq=6 (gsi=6) [0.562705] xen: -- pirq=20 - irq=4 (gsi=4) [0.920527] xen: -- pirq=21 - irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+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 1304001] Re: xen:balloon errors in 14.04 beta
Hi Andrew, sorry about the dyndbg. It all lokked like it would be tied to that but right now I am not sure it is. I need to check the code again. If anything else fails we can do a special kernel. I have the same issue as Boris in that I am not able to cause the same problem on HVM guests locally. I am using an Ubuntu base install (Xen-4.2.2 + dom kernel 3.8). xend-config is set to allow ballooning. Now the question is how memory for a guest is configured on the host. I can see the issue on a c3.large instance but we have no way of knowing anything outside the guest. One note, too. There is one other memory related message in the guests dmesg: [0.00] NUMA: Warning: invalid memblk node 0 [mem 0x1-0x0fff] I vaguely remember NUMA related problems at some point. But I cannot remember whether this was something that needed fixes in the hypervisor, the dom0 kernel or the guest kernel. Or combinations of that. -- 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/1304001 Title: xen:balloon errors in 14.04 beta Status in “linux” package in Ubuntu: Confirmed Bug description: Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: -- pirq=16 - irq=8 (gsi=8) [0.562622] xen: -- pirq=17 - irq=12 (gsi=12) [0.562649] xen: -- pirq=18 - irq=1 (gsi=1) [0.562673] xen: -- pirq=19 - irq=6 (gsi=6) [0.562705] xen: -- pirq=20 - irq=4 (gsi=4) [0.920527] xen: -- pirq=21 - irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+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 1270656] Re: Ubuntu 14.04 boots to blank console
As far as I remember we changed CONFIG_DRM_VMWGFX_FBCON to 'y ' now. Generally
it is getting more complicated nowadays. Grub2 initializes some framebuffer
graphics mode (unless console mode is enforced in /etc/default/grub), hands
this fb over to plymouth and that hands things over to X. And somewhere between
grub and plymouth starting, the kernel may start a gfx device specific modeset
driver which may have its own fb driver. Many opportunities for things to go
wrong. Btw, I think I mentioned it before but the vga= argument may be becoming
more a problem than helping. Grub sets a gfx mode already and that is kept if
no modeset driver is not changing it. And all newer modeset drivers use video=
for specifying the preferred resolution. (like video=1280x800@32). But in
theory that should not be necessary at all when the gfx mode is set ok by grub.
Anyway, I tend to declare this bug as fixed and have people with other gfx
cards/drivers open individual bug reports. Mixing things in one single report
will only cause confusion.
--
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/1270656
Title:
Ubuntu 14.04 boots to blank console
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux” package in Debian:
New
Status in “linux” package in Fedora:
New
Bug description:
Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console.
Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but ps axf shows
/sbin/getty running on tty{1..6}:
# ps axf | grep tty
880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4
885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5
890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2
891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3
893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6
4290 pts/1S+ 0:00 \_ grep --color=auto tty
1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1
Removing deprecated vga=768 from kernel commandline = doesn't boot into
800x600, keeps 640x480
Settings
GRUB_GFXMODE=800x600
GRUB_GFXPAYLOAD=800x600
are ignored.
Grub boots up with 800x600, switches back to 640x480 (setting
GRUB_GFXPAYLOAD to keep it is the same) kernel doesn't switch back
to 800x600.
Adding deprecated vga=768 back in:
Grub boots up with 800x600, switches back to 640x480, kernel switches back to
800x600, but doesn't use this console. No output at all. Keys are accepted (you
can login, but you'll have to guess what is going on on the screen).
Exactly the same error is found with debian. Switching to a self
compiled kernel solves this error. Looks a lot like some necessary
stuff for console resolution switching is missing in the debian
-/ubuntu-kernels.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: util-linux 2.20.1-5.1ubuntu13
ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
Uname: Linux 3.13.0-4-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
Date: Mon Jan 20 00:20:36 2014
InstallationDate: Installed on 2012-12-12 (403 days ago)
InstallationMedia: Ubuntu-Server 12.04.1 LTS Precise Pangolin - Release
amd64 (20120817.3)
ProcEnviron:
TERM=screen-bce
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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
Re: [Kernel-packages] [Bug 1313497] Re: USB keyboard unresponsive on fresh install
Hi Stuart, On 29.04.2014 05:23, Stuart Longland wrote: Did the linux-3.13.0-24-generic package miss out a few files or are they in a separate package the installer forgot to install? That could be and depends on you seed. For bare-metal you should have seleced linux-server for d-i base-installer/kernel/image. In general the linux-image should not be picked directly as we indeed split up the modules into the minimum for virtual machines and a rest. linux-server, linux-generic, and linux-virtual are all meta-package which will install the right set of packages and also make sure you see kernel updates. server and generic nowadays is actually the same. So you could have installed without those and now miss the linux-image-extra package. -- 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/1313497 Title: USB keyboard unresponsive on fresh install Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I just did a fresh install of Ubuntu 14.04 LTS onto a machine here. During the installation (which is pre-seeded) and in the BIOS, my keyboard works flawlessly. However, the moment I boot the machine up, I note the keyboard is not operational. Naturally, I discover this *after* buggering up my networking settings. The offending package is linux-image-3.13.0-24-generic version 3.13.0-24.46. At one point I noticed an irq 16: nobody cared error message. Due to there being no network connectivity, I was unable to capture the message displayed. The output from `dmesg` (see attachment dmesg.txt) suggests it does see USB and the keyboard, but plugging the keyboard into any of the available ports and pressing keys has no effect on the console. The machine is a rack-mounted server, intended to run headless. The motherboard is an Intel DQ77MK. No peripheral cards are installed. root@host:~# cat /proc/version_signature Ubuntu 3.13.0-24.46-generic 3.13.9 root@host:~# lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller [8086:0150] (rev 09) Subsystem: Intel Corporation Device [8086:2035] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: [e0] Vendor Specific Information: Len=0c ? 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2035] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: Memory at f780 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at e000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at f000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Address: Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI]) Subsystem: Intel Corporation Device [8086:2035] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 40 Region 0: Memory at f7e2 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Address: fee0a00c Data: 4181 Kernel driver in use: xhci_hcd 00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) Subsystem: Intel Corporation Device [8086:2035] Control:
[Kernel-packages] [Bug 1317811] Re: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots
Right, unfortunately a real fix without the need to disable scatter gather will unlikely happen soon. None of the approaches discussed until now seem to find the agreement of everybody as they all would not be perfect. -- 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/1317811 Title: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots Status in “linux” package in Ubuntu: In Progress Bug description: Running Ubuntu 14.04 LTS on EC2, we see a lot of the following in the kernel log: xen_netfront: xennet: skb rides the rocket: 19 slots Each of these messages corresponds to a dropped TX packet, and eventually causes our application's connections to break and timeout. The problem appears when network load increases. We have Node.js processes doing pubsub with a Redis server, and these are most visibly affected, showing frequent connection loss. The processes talk to each other using the private addresses EC2 allocates to the machines. Notably, the default MTU on the network interface seems to have gone up from 1500 on 13.10, to 9000 in 14.04 LTS. Reducing the MTU back to 1500 seems to drastically reduce dropped packets. (Can't say for certain if it completely eliminates the problem.) The machines we run are started from ami-896c96fe. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:01 seq crw-rw 1 root audio 116, 33 May 9 09:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 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: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri May 9 09:11:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:54 seq crw-rw 1 root audio 116, 33 May 9 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 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: [Errno 2] No such file or directory CurrentDmesg: [ 24.724129] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317811/+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 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration
The changes are in 3.15, so Utopic/development branch should be fixed already. ** Changed in: linux (Ubuntu) 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/1313450 Title: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration Status in “linux” package in Ubuntu: Fix Released Status in “vsftpd” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Fix Released Status in “vsftpd” source package in Trusty: Invalid Bug description: The configuration submitted was modified during testing, but this also failed with the default configuration. The only solution I have found so far was to delete the configuration, this would allow the service to start, but obviously not work as intended. If I try to start the service manually using vsftpd or sudo vsftpd I receive the following error message: 500 OOPS: munmap I also tried the default commands /etc/init.d/vsftpd or service vsftpd start ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: vsftpd 3.0.2-1ubuntu2 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 27 21:23:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: t1.micro Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vsftpd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.vsftpd.conf: [modified] mtime.conffile..etc.vsftpd.conf: 2014-04-27T21:16:28.222467 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: t1.micro Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable Package: vsftpd 3.0.2-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Tags: trusty ec2-images Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True modified.conffile..etc.vsftpd.conf: [modified] mtime.conffile..etc.vsftpd.conf: 2014-04-29T19:03:28.834467 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313450/+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 1319244] Re: iostat: Cannot open /proc/stat: Cannot allocate memory
** Description changed: + break-fix: 59a32e2ce5eb809967cac4e718bc527beca83c59 f74373a5cc7a0155d232c4e999648c7a95435bb2 + break-fix: 59a32e2ce5eb809967cac4e718bc527beca83c59 058504edd02667eef8fac9be27ab3ea74332e9b4 + Intermitently I get errors stating that various programs cannot allocate memory when reading /proc/stat I have 2 servers that are affected by the issue. Probably a duplicate of 1226172 [1764593.455329] top: page allocation failure: order:4, mode:0x1040d0 [1764593.455335] CPU: 3 PID: 10323 Comm: top Tainted: GF O 3.11.0-18-generic #32-Ubuntu [1764593.455338] Hardware name: Intel Corporation S2400SC/S2400SC, BIOS SE5C600.86B.02.02.0002.122320131210 12/23/2013 [1764593.455340] 88042670b9d0 816e8571 001040d0 [1764593.455345] 88042670ba58 81144ae0 880a3fffcb48 [1764593.455348] 000e 88042670ba28 0040 0007 [1764593.455351] Call Trace: [1764593.455361] [816e8571] dump_stack+0x45/0x56 [1764593.455367] [81144ae0] warn_alloc_failed+0xf0/0x140 [1764593.455371] [81148a15] __alloc_pages_nodemask+0x725/0x920 [1764593.455376] [81184589] alloc_pages_current+0xa9/0x160 [1764593.455379] [81143bfe] __get_free_pages+0xe/0x50 [1764593.455384] [8118d75e] kmalloc_order_trace+0x2e/0xa0 [1764593.455388] [811c9960] ? single_open+0xb0/0xb0 [1764593.455391] [8118ee19] __kmalloc+0x159/0x180 [1764593.455393] [811c9960] ? single_open+0xb0/0xb0 [1764593.455398] [81213c10] stat_open+0x50/0xc0 [1764593.455401] [8120a700] proc_reg_open+0x70/0x110 [1764593.455405] [811a5d4b] do_dentry_open+0x1eb/0x280 [1764593.455408] [8120a690] ? proc_reg_release+0x70/0x70 [1764593.455411] [811a5e69] vfs_open+0x49/0x50 [1764593.455415] [811b5e13] do_last+0x1c3/0xe50 [1764593.455418] [8118e5d8] ? kmem_cache_alloc_trace+0x108/0x130 [1764593.455421] [811b6b61] path_openat+0xc1/0x630 [1764593.455426] [811689d9] ? handle_mm_fault+0x299/0x670 [1764593.455429] [811b7eda] do_filp_open+0x3a/0x90 [1764593.455433] [816ef78e] ? _raw_spin_lock+0xe/0x20 [1764593.455437] [811c4847] ? __alloc_fd+0xa7/0x130 [1764593.455440] [811a704c] do_sys_open+0x12c/0x270 [1764593.455445] [81074989] ? __set_current_blocked+0x49/0x60 [1764593.455448] [811a71ae] SyS_open+0x1e/0x20 [1764593.455452] [816f841d] system_call_fastpath+0x1a/0x1f [1764593.455454] Mem-Info: [1764593.455455] Node 0 DMA per-cpu: [1764593.455458] CPU0: hi:0, btch: 1 usd: 0 [1764593.455459] CPU1: hi:0, btch: 1 usd: 0 [1764593.455461] CPU2: hi:0, btch: 1 usd: 0 [1764593.455462] CPU3: hi:0, btch: 1 usd: 0 [1764593.455463] CPU4: hi:0, btch: 1 usd: 0 [1764593.455465] CPU5: hi:0, btch: 1 usd: 0 [1764593.455466] CPU6: hi:0, btch: 1 usd: 0 [1764593.455468] CPU7: hi:0, btch: 1 usd: 0 [1764593.455469] Node 0 DMA32 per-cpu: [1764593.455471] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455472] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455474] CPU2: hi: 186, btch: 31 usd: 0 [1764593.455475] CPU3: hi: 186, btch: 31 usd: 0 [1764593.455477] CPU4: hi: 186, btch: 31 usd: 0 [1764593.455478] CPU5: hi: 186, btch: 31 usd: 0 [1764593.455480] CPU6: hi: 186, btch: 31 usd: 0 [1764593.455481] CPU7: hi: 186, btch: 31 usd: 0 [1764593.455482] Node 0 Normal per-cpu: [1764593.455484] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455485] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455487] CPU2: hi: 186, btch: 31 usd: 0 [1764593.455488] CPU3: hi: 186, btch: 31 usd: 0 [1764593.455490] CPU4: hi: 186, btch: 31 usd: 0 [1764593.455491] CPU5: hi: 186, btch: 31 usd: 0 [1764593.455492] CPU6: hi: 186, btch: 31 usd: 0 [1764593.455494] CPU7: hi: 186, btch: 31 usd: 0 [1764593.455495] Node 1 Normal per-cpu: [1764593.455497] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455498] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455500] CPU2: hi: 186, btch: 31 usd: 0 [1764593.455501] CPU3: hi: 186, btch: 31 usd: 0 [1764593.455503] CPU4: hi: 186, btch: 31 usd: 0 [1764593.455504] CPU5: hi: 186, btch: 31 usd: 30 [1764593.455505] CPU6: hi: 186, btch: 31 usd: 0 [1764593.455507] CPU7: hi: 186, btch: 31 usd: 0 [1764593.455511] active_anon:4739030 inactive_anon:2482840 isolated_anon:0 [1764593.455511] active_file:6228818 inactive_file:5945293 isolated_file:0 [1764593.455511] unevictable:1459 dirty:61 writeback:0 unstable:0 [1764593.455511] free:318692 slab_reclaimable:462577 slab_unreclaimable:149699
[Kernel-packages] [Bug 1319244] Re: iostat: Cannot open /proc/stat: Cannot allocate memory
I would doubt Saucy by now since it is almost EOL due to the reduced support of non-LTS releases. Trusty should get it through the normal upstream-stable path. -- 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/1319244 Title: iostat: Cannot open /proc/stat: Cannot allocate memory Status in “linux” package in Ubuntu: Fix Released Bug description: break-fix: 59a32e2ce5eb809967cac4e718bc527beca83c59 f74373a5cc7a0155d232c4e999648c7a95435bb2 break-fix: 59a32e2ce5eb809967cac4e718bc527beca83c59 058504edd02667eef8fac9be27ab3ea74332e9b4 Intermitently I get errors stating that various programs cannot allocate memory when reading /proc/stat I have 2 servers that are affected by the issue. Probably a duplicate of 1226172 [1764593.455329] top: page allocation failure: order:4, mode:0x1040d0 [1764593.455335] CPU: 3 PID: 10323 Comm: top Tainted: GF O 3.11.0-18-generic #32-Ubuntu [1764593.455338] Hardware name: Intel Corporation S2400SC/S2400SC, BIOS SE5C600.86B.02.02.0002.122320131210 12/23/2013 [1764593.455340] 88042670b9d0 816e8571 001040d0 [1764593.455345] 88042670ba58 81144ae0 880a3fffcb48 [1764593.455348] 000e 88042670ba28 0040 0007 [1764593.455351] Call Trace: [1764593.455361] [816e8571] dump_stack+0x45/0x56 [1764593.455367] [81144ae0] warn_alloc_failed+0xf0/0x140 [1764593.455371] [81148a15] __alloc_pages_nodemask+0x725/0x920 [1764593.455376] [81184589] alloc_pages_current+0xa9/0x160 [1764593.455379] [81143bfe] __get_free_pages+0xe/0x50 [1764593.455384] [8118d75e] kmalloc_order_trace+0x2e/0xa0 [1764593.455388] [811c9960] ? single_open+0xb0/0xb0 [1764593.455391] [8118ee19] __kmalloc+0x159/0x180 [1764593.455393] [811c9960] ? single_open+0xb0/0xb0 [1764593.455398] [81213c10] stat_open+0x50/0xc0 [1764593.455401] [8120a700] proc_reg_open+0x70/0x110 [1764593.455405] [811a5d4b] do_dentry_open+0x1eb/0x280 [1764593.455408] [8120a690] ? proc_reg_release+0x70/0x70 [1764593.455411] [811a5e69] vfs_open+0x49/0x50 [1764593.455415] [811b5e13] do_last+0x1c3/0xe50 [1764593.455418] [8118e5d8] ? kmem_cache_alloc_trace+0x108/0x130 [1764593.455421] [811b6b61] path_openat+0xc1/0x630 [1764593.455426] [811689d9] ? handle_mm_fault+0x299/0x670 [1764593.455429] [811b7eda] do_filp_open+0x3a/0x90 [1764593.455433] [816ef78e] ? _raw_spin_lock+0xe/0x20 [1764593.455437] [811c4847] ? __alloc_fd+0xa7/0x130 [1764593.455440] [811a704c] do_sys_open+0x12c/0x270 [1764593.455445] [81074989] ? __set_current_blocked+0x49/0x60 [1764593.455448] [811a71ae] SyS_open+0x1e/0x20 [1764593.455452] [816f841d] system_call_fastpath+0x1a/0x1f [1764593.455454] Mem-Info: [1764593.455455] Node 0 DMA per-cpu: [1764593.455458] CPU0: hi:0, btch: 1 usd: 0 [1764593.455459] CPU1: hi:0, btch: 1 usd: 0 [1764593.455461] CPU2: hi:0, btch: 1 usd: 0 [1764593.455462] CPU3: hi:0, btch: 1 usd: 0 [1764593.455463] CPU4: hi:0, btch: 1 usd: 0 [1764593.455465] CPU5: hi:0, btch: 1 usd: 0 [1764593.455466] CPU6: hi:0, btch: 1 usd: 0 [1764593.455468] CPU7: hi:0, btch: 1 usd: 0 [1764593.455469] Node 0 DMA32 per-cpu: [1764593.455471] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455472] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455474] CPU2: hi: 186, btch: 31 usd: 0 [1764593.455475] CPU3: hi: 186, btch: 31 usd: 0 [1764593.455477] CPU4: hi: 186, btch: 31 usd: 0 [1764593.455478] CPU5: hi: 186, btch: 31 usd: 0 [1764593.455480] CPU6: hi: 186, btch: 31 usd: 0 [1764593.455481] CPU7: hi: 186, btch: 31 usd: 0 [1764593.455482] Node 0 Normal per-cpu: [1764593.455484] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455485] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455487] CPU2: hi: 186, btch: 31 usd: 0 [1764593.455488] CPU3: hi: 186, btch: 31 usd: 0 [1764593.455490] CPU4: hi: 186, btch: 31 usd: 0 [1764593.455491] CPU5: hi: 186, btch: 31 usd: 0 [1764593.455492] CPU6: hi: 186, btch: 31 usd: 0 [1764593.455494] CPU7: hi: 186, btch: 31 usd: 0 [1764593.455495] Node 1 Normal per-cpu: [1764593.455497] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455498] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455500] CPU2: hi: 186, btch: 31 usd: 0 [1764593.455501] CPU3: hi: 186, btch: 31 usd: 0 [1764593.455503] CPU4: hi: 186, btch: 31 usd: 0 [1764593.455504] CPU5: hi: 186, btch: 31 usd:
[Kernel-packages] [Bug 1319244] Re: iostat: Cannot open /proc/stat: Cannot allocate memory
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: linux (Ubuntu Trusty) Status: New = Triaged ** Tags added: kernel-bug-break-fix -- 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/1319244 Title: iostat: Cannot open /proc/stat: Cannot allocate memory Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Triaged Bug description: break-fix: 59a32e2ce5eb809967cac4e718bc527beca83c59 f74373a5cc7a0155d232c4e999648c7a95435bb2 break-fix: 59a32e2ce5eb809967cac4e718bc527beca83c59 058504edd02667eef8fac9be27ab3ea74332e9b4 Intermitently I get errors stating that various programs cannot allocate memory when reading /proc/stat I have 2 servers that are affected by the issue. Probably a duplicate of 1226172 [1764593.455329] top: page allocation failure: order:4, mode:0x1040d0 [1764593.455335] CPU: 3 PID: 10323 Comm: top Tainted: GF O 3.11.0-18-generic #32-Ubuntu [1764593.455338] Hardware name: Intel Corporation S2400SC/S2400SC, BIOS SE5C600.86B.02.02.0002.122320131210 12/23/2013 [1764593.455340] 88042670b9d0 816e8571 001040d0 [1764593.455345] 88042670ba58 81144ae0 880a3fffcb48 [1764593.455348] 000e 88042670ba28 0040 0007 [1764593.455351] Call Trace: [1764593.455361] [816e8571] dump_stack+0x45/0x56 [1764593.455367] [81144ae0] warn_alloc_failed+0xf0/0x140 [1764593.455371] [81148a15] __alloc_pages_nodemask+0x725/0x920 [1764593.455376] [81184589] alloc_pages_current+0xa9/0x160 [1764593.455379] [81143bfe] __get_free_pages+0xe/0x50 [1764593.455384] [8118d75e] kmalloc_order_trace+0x2e/0xa0 [1764593.455388] [811c9960] ? single_open+0xb0/0xb0 [1764593.455391] [8118ee19] __kmalloc+0x159/0x180 [1764593.455393] [811c9960] ? single_open+0xb0/0xb0 [1764593.455398] [81213c10] stat_open+0x50/0xc0 [1764593.455401] [8120a700] proc_reg_open+0x70/0x110 [1764593.455405] [811a5d4b] do_dentry_open+0x1eb/0x280 [1764593.455408] [8120a690] ? proc_reg_release+0x70/0x70 [1764593.455411] [811a5e69] vfs_open+0x49/0x50 [1764593.455415] [811b5e13] do_last+0x1c3/0xe50 [1764593.455418] [8118e5d8] ? kmem_cache_alloc_trace+0x108/0x130 [1764593.455421] [811b6b61] path_openat+0xc1/0x630 [1764593.455426] [811689d9] ? handle_mm_fault+0x299/0x670 [1764593.455429] [811b7eda] do_filp_open+0x3a/0x90 [1764593.455433] [816ef78e] ? _raw_spin_lock+0xe/0x20 [1764593.455437] [811c4847] ? __alloc_fd+0xa7/0x130 [1764593.455440] [811a704c] do_sys_open+0x12c/0x270 [1764593.455445] [81074989] ? __set_current_blocked+0x49/0x60 [1764593.455448] [811a71ae] SyS_open+0x1e/0x20 [1764593.455452] [816f841d] system_call_fastpath+0x1a/0x1f [1764593.455454] Mem-Info: [1764593.455455] Node 0 DMA per-cpu: [1764593.455458] CPU0: hi:0, btch: 1 usd: 0 [1764593.455459] CPU1: hi:0, btch: 1 usd: 0 [1764593.455461] CPU2: hi:0, btch: 1 usd: 0 [1764593.455462] CPU3: hi:0, btch: 1 usd: 0 [1764593.455463] CPU4: hi:0, btch: 1 usd: 0 [1764593.455465] CPU5: hi:0, btch: 1 usd: 0 [1764593.455466] CPU6: hi:0, btch: 1 usd: 0 [1764593.455468] CPU7: hi:0, btch: 1 usd: 0 [1764593.455469] Node 0 DMA32 per-cpu: [1764593.455471] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455472] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455474] CPU2: hi: 186, btch: 31 usd: 0 [1764593.455475] CPU3: hi: 186, btch: 31 usd: 0 [1764593.455477] CPU4: hi: 186, btch: 31 usd: 0 [1764593.455478] CPU5: hi: 186, btch: 31 usd: 0 [1764593.455480] CPU6: hi: 186, btch: 31 usd: 0 [1764593.455481] CPU7: hi: 186, btch: 31 usd: 0 [1764593.455482] Node 0 Normal per-cpu: [1764593.455484] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455485] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455487] CPU2: hi: 186, btch: 31 usd: 0 [1764593.455488] CPU3: hi: 186, btch: 31 usd: 0 [1764593.455490] CPU4: hi: 186, btch: 31 usd: 0 [1764593.455491] CPU5: hi: 186, btch: 31 usd: 0 [1764593.455492] CPU6: hi: 186, btch: 31 usd: 0 [1764593.455494] CPU7: hi: 186, btch: 31 usd: 0 [1764593.455495] Node 1 Normal per-cpu: [1764593.455497] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455498] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455500] CPU2: hi: 186, btch: 31 usd: 0
[Kernel-packages] [Bug 1327563] Re: Long delay when mounting NFS shares
To add a bit of debugging I did (using two VMs): - There server side kernel version does not matter (tested trusty and utopic) - A client with a 3.13 kernel will have the delay, while the 3.16 kernel is ok Enabling NFS debugging on both clients (as root echo 32767 /proc/sys/sunrpc/nfs_debug) shows an interesting fact: 3.13 client: 7581.776148] NFS: nfs4_discover_server_trunking: testing 'lam-utopic6401' 7581.776154] NFS call setclientid auth=RPCSEC_GSS, 'Linux NFSv4.0 192.168.2.19 7596.776086] RPC: AUTH_GSS upcall timed out. 7596.776086] Please check user daemon is running. 7596.776110] NFS reply setclientid: -13 7596.776121] NFS call setclientid auth=RPCSEC_GSS, 'Linux NFSv4.0 192.168.2.19 7597.024109] NFS reply setclientid: -13 7597.024766] NFS call setclientid auth=UNIX, 'Linux NFSv4.0 192.168.2.192/192. 7597.025506] NFS reply setclientid: 0 7597.025512] NFS call setclientid_confirm auth=UNIX, (client ID fb69c65304 7597.026068] NFS reply setclientid_confirm: 0 3.16 client: 2137.866775] NFS: nfs4_discover_server_trunking: testing 'lam-utopic6401' 2137.866783] NFS call setclientid auth=UNIX, 'Linux NFSv4.0 192.168.2.120/192. 2137.867420] NFS reply setclientid: 0 2137.867426] NFS call setclientid_confirm auth=UNIX, (client ID fb69c65305 2137.867727] NFS reply setclientid_confirm: 0 So the newer kernel seems to skip the other authentication methods. And of those two AUTH_GSS is causing the delay because it times out. Unfortunately I did not spot any commits in between 3.13 and now that would immediately sound like a good candidate for fixing this. -- 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/1327563 Title: Long delay when mounting NFS shares Status in “linux” package in Ubuntu: Confirmed Bug description: Summary: After upgrading the kernel on Ubuntu 14.04 to 3.13.0-29-generic I found that it can take a considerably longer amount of time to mount NFS shares. How to reproduce: 1. Install Ubuntu 14.04 on two machines. A minimal server install should be fine. One will act as a server, the other as a client. 2. Upgrade the kernel on the client machine to at least 3.13.0-27-generic. 3. Install the nfs-kernel-server package on the server. 4. Add a directory to /etc/exports and run service nfs-kernel-server start. 5. Install the nfs-common package on the client. 6. Attempt to mount the shared directory on the client. Expected result: The shared directory should be mounted on the client more or less immediately. Actual result: The mount command hangs and eventually completes. In this test case it takes 16 seconds consistently. On a production machine where the problem was first discovered the time is considerably longer and essentially makes it impossible to mount NFS shares. Regression: I have been able to reproduce the problem on clients running Linux 3.13.0-27-generic and later. The problem is not reproducible on clients running Linux 3.13.0-24-generic. The problem is reproducible no matter which kernel version is used on the server. Tested client kernel versions: Linux 3.13.0-29-generic #53-Ubuntu FAIL Linux 3.13.0-27-generic #50-Ubuntu FAIL Linux 3.13.0-24-generic #47-Ubuntu OK Tested server kernel versions: Linux 3.13.0-29-generic #53-Ubuntu OK Linux 3.13.0-27-generic #50-Ubuntu OK Linux 3.13.0-24-generic #47-Ubuntu OK lsb_release -rd: Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy linux-image-generic: linux-image-generic: Installed: (none) Candidate: 3.13.0.29.35 Version table: 3.13.0.29.35 0 500 http://se.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 3.13.0.24.28 0 500 http://se.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 7 16:26 seq crw-rw 1 root audio 116, 33 Jun 7 16:26 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sat Jun 7 16:30:02 2014 HibernationDevice: RESUME=UUID=9c13108b-d40a-4881-b563-c477ed2e6804 InstallationDate: Installed on 2014-06-07 (0 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Kernel-packages] [Bug 1344430] Re: 10-15% iowait on kvm instances on Ubuntu 14.04
Some things (like the hardware of the host) we get through apport-collect. It would be good to get a better understanding of the guest usage. Like how many guests, how much memory they get, how many vcpus. virtio disks and network and how are the guests connected to the network (NAT bridge, transparent bridge, openvswitch?). Are vdisk using raw images or qcov2, image files or partitions or logical volumes. Maybe then we can also replicate the issue in a test environment. Up to now I am not sure I ever was able to see the same issue or not. Oh and was there a specific stat or combination of stats that hints this is happening. Laggy terminal is hard to test for in some scripted way. -- 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/1344430 Title: 10-15% iowait on kvm instances on Ubuntu 14.04 Status in “linux” package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 12.04 to Ubuntu 14.04 we began seeing 10-15% iowait on kvm guests. The guests had little to no load and yet the shell was laggy and commands took forever to respond (assuming you could even type them) # uname -a Linux kvm-andromeda 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux # kvm --version QEMU emulator version 2.0.0 (Debian 2.0.0+dfsg-2ubuntu1.1), Copyright (c) 2003-2008 Fabrice Bellard I posted to Ubuntu Server and they suggested that I upgrade my kernel version. Relevant Mailing List discussion: https://lists.ubuntu.com/archives/ubuntu-server/2014-July/006925.html After installing a 3.14 kernel the performance returned to normal. kvm-andromeda:~# uname -a Linux kvm-andromeda 3.14.1-031401-generic #201404141220 SMP Mon Apr 14 16:21:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 DistroRelease: Ubuntu 14.04 Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Tags: trusty Uname: Linux 3.14.1-031401-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: root _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1344430/+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 1322129] Re: Raw Food Diet - Health Benefits of Raw Vegetables
** Changed in: linux (Ubuntu) Status: Incomplete = Invalid -- 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/1322129 Title: Raw Food Diet - Health Benefits of Raw Vegetables Status in “linux” package in Ubuntu: Invalid Bug description: Most of us harmonize that a raw rootlike fasting strength better us regress unit, turn our eudaemonia, and hike our levels of push. So, time we are sensible of all the impressive advantages, how rise we ofttimes fail to add these actor foods to our regular fast programs? Is it because we judge vegetables are drab, tastes bad or fuck too bimestrial to read? Do we consider that the sassy foods fast could be very pricey? Or, do our occupied touch schedules tidy firm substance options the easier superior? Doctors, nutritionists, and yet our mothers, materialize to be forceful us for life that feeding a sort of veggies give learning for our upbeat. It has been drilled into our heads, we live that it's honorable, and most of us requisite to do what is human for our embody. Considerably, there is morality interest. We can abandonment all our excuses and misconceptions, since the feminist is that adding statesman uncooked vegetables to our diet does not feature to be complicated, deadening, or costly. With today's profession, it comes with an copiousness of fun and interesting recipes parcel at our fingertips. Meet your local repository or shop, or but reverse on your pc and explore the fascinating grouping of raw veggie cooking. There a grouping of options, several using ingredients readily gettable at most supermarkets for commonsensible prices. Enquiry, try new things, or add your real own flair and you give shortly actualise that consumption raw vegetables module not exclusive entity you to see turn, they can secernment major too!The key intellect why Eat Raw? One of the most popular motivators in dynamic your fast is understanding why the mind is eminent. Raw vegetables are an superior communicator of vitamins, nutrients, and antioxidants, and are packed with invaluable phytochemicals, that really provide protect the embody and amend its elemental potentiality to improve itself. Additionally they comprise serious enzymes that service in straitlaced digestion and assisted in the absorption of nutrients. The fact is that, cookery can unmake or decrease all these necessary properties. Raw healthy or extant foods tend to be unfinished, low in metal, and also screw all the enzymes, vitamins, and minerals plant uninjured so your embody is competent to use the nutrients much efficiently. For peak eudaimonia benefits, active 75% of matter should be ingested raw. So, sicken out those new recipes, pucker together a laughter ingredient, and educate to flavour all the advantages veggies can supply. What are the Advantages of a Raw Vegetal Fasting? Adding vegetables for your regular consumption drawing can render lots of affirmatory benefits that instrument turn your animal and emotional well-being. In a shortly abstraction, you present remark a material push assist, accumulated energy, and poised moods. You present kip advisable, suppose clearer, and achieve a intelligent unit. From outdo digestion into a lowly venture of disease and reinforced immunity, consuming raw veggies is among the person things you instrument e'er do for your embody wellbeing. http://garciniaultramaxtry.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322129/+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 1322211] Re: linux-image-3.13.0-24-generic kernel doesn't boot on Xen 3.0 from CentOS5
I see that this was agreed to be an upstream change that is considered stable material. The patch looks reasonable from the discussion, but I would like to see it at least reaching upstream linux or linux-next at least. -- 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/1322211 Title: linux-image-3.13.0-24-generic kernel doesn't boot on Xen 3.0 from CentOS5 Status in “linux” package in Ubuntu: Confirmed Bug description: linux-image-3.13.0-24-generic does not boot on Xen 3.0. Tested on CentOS 5.10. Boot crashes before any output from kernel. Output from xm dmesg: (XEN) event_channel.c:181:d0 EVTCHNOP failure: domain 0, error -22, line 181 (XEN) event_channel.c:181:d0 EVTCHNOP failure: domain 0, error -22, line 181 (XEN) traps.c:1912:d2004 Domain attempted WRMSR 008b from 0015: to :. (XEN) traps.c:405:d2004 Unhandled invalid opcode fault/trap [#6] in domain 2004 on VCPU 0 [ec=] (XEN) domain_crash_sync called from entry.S (XEN) Domain 2004 (vcpu#0) crashed on cpu#14: (XEN) [ Xen-3.1.2-308.8.2.el5 x86_64 debug=n Not tainted ] (XEN) CPU:14 (XEN) RIP:e033:[81004c38] (XEN) RFLAGS: 0282 CONTEXT: guest (XEN) rax: ffea rbx: 023ff000 rcx: 0002 (XEN) rdx: 0001 rsi: 81c01e48 rdi: (XEN) rbp: 81c01e58 rsp: 81c01e08 r8: (XEN) r9: 81c01dc8 r10: 7ff0 r11: (XEN) r12: 81dd6900 r13: r14: (XEN) r15: cr0: 80050033 cr4: 26b0 (XEN) cr3: 001dde584000 cr2: (XEN) ds: es: fs: gs: ss: e02b cs: e033 (XEN) Guest stack trace from rsp=81c01e08: (XEN)0002 81004c38 0001e030 (XEN)00010082 81c01e48 e02b 81004c32 (XEN)00010004 8171e4a0 81c01e78 81d38f1d (XEN)00010001 81727ed0 81c01ef0 81d3c58b (XEN) 81c01ef0 81c01f08 (XEN)0010 81c01f00 81c01ec0 81ebc632 (XEN) 81dd6900 (XEN) 81c01f30 81d34c07 0018 (XEN)356a4e4bd08da87b 81c01f60 f3df (XEN) 81c01f40 81d345ee 81c01ff8 (XEN)81d384a7 000206c2 000133200800 0f898371 (XEN) (XEN) (XEN) (XEN) (XEN) 0f0060c0c748 (XEN)c305 (XEN) (XEN) (XEN) Appears to be a known bug that has not been patched in mainline kernel yet: http://lists.xen.org/archives/html/xen-devel/2014-05/msg01474.html Tested recompiling from kernel at git://kernel.ubuntu.com/ubuntu /ubuntu-trusty.git with patch from above thread. # lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 # apt-cache policy linux-image-3.13.0-24-generic linux-image-3.13.0-24-generic: Installed: 3.13.0-24.46 Candidate: 3.13.0-24.46 Version table: *** 3.13.0-24.46 0 100 /var/lib/dpkg/status --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 15:10 seq crw-rw 1 root audio 116, 33 May 22 15:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 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: [Errno 2] No such file or directory CurrentDmesg: [ 20.010048] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine:
[Kernel-packages] [Bug 1322407] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
Can you be more specific about the configuration of the server (/etc/exports,/etc/defaul/nfs-*) and what kind of client you use. I just tried this on two VMs and saw not issues (at least with a basic NFSv4 setup). -- 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/1322407 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly Status in “linux” package in Ubuntu: Confirmed Bug description: This concerns the server edition of 14.04. I have set up a NFS server. Once I attach at least one client, one kworker process starts to use 100% CPU. The runaway kworker returns to idle when I reset the NFS server daemon with service nfs-kernel-server stop followed by service nfs-kernel-server start. With the nfs kernel server stopped, the CPU remains idle. With the nfs kernel server running, as soon as one client requests a connection, the kworker process jumps to 100% CPU again. After some random time, the nfs kernel server no longer accepts requests from clients. Restarting the service allows clients to reconnect. The syslog shows no relevant information. This problem has never appeared on a very similar server setup with 12.04. Configration: The svcgssd is not running. I played with various configurations (enabling/disabling NFSv3 and NFSv4), but it makes no difference. I tried to enable event debugging: # echo workqueue:workqueue_queue_work /sys/kernel/debug/tracing/set_event # cat /sys/kernel/debug/tracing/trace_pipe /var/tmp/kerntrace.txt and found the following kernel trace in a tight loop: [...] kworker/2:1-86[002] d... 161940.910668: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910674: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910675: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910681: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910682: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910688: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910689: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910695: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910696: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910702: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 [...] At present, I have to consider NFS fubar. Thanks, Mark ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/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: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Thu May 22 22:48:48 2014 HibernationDevice: RESUME=UUID=adcdeef5-9b46-4ea4-b9f4-b6e642ea91e8 InstallationDate: Installed on 2014-05-12 (10 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3
[Kernel-packages] [Bug 1322407] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
Probably the relevant part I missed initially is that probably this involves connections going on and succeeding for a bit and fail at some point. Where it is unclear how many connections have been going on and so on. The function tracing you did does show that there is some kind of loop going on but does not allow to figure out any real details. I wonder whether you could try to enable some of the nfs debugging from /proc/sys/sunrpc/*_debug. Which allows to enable various pieces of internal debugging. #define RPCDBG_XPRT 0x0001 #define RPCDBG_CALL 0x0002 #define RPCDBG_DEBUG0x0004 #define RPCDBG_NFS 0x0008 #define RPCDBG_AUTH 0x0010 #define RPCDBG_BIND 0x0020 #define RPCDBG_SCHED0x0040 #define RPCDBG_TRANS0x0080 #define RPCDBG_SVCXPRT 0x0100 #define RPCDBG_SVCDSP 0x0200 #define RPCDBG_MISC 0x0400 #define RPCDBG_CACHE0x0800 #define RPCDBG_ALL 0x7fff So echoing 524287 into the various /proc interfaces should enable all debugging. Not sure which if them maybe starting with nfsd_debug and/or rpc_debug. Maybe this allows to narrow down what goes wrong in a better way. -- 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/1322407 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly Status in “linux” package in Ubuntu: Confirmed Bug description: This concerns the server edition of 14.04. I have set up a NFS server. Once I attach at least one client, one kworker process starts to use 100% CPU. The runaway kworker returns to idle when I reset the NFS server daemon with service nfs-kernel-server stop followed by service nfs-kernel-server start. With the nfs kernel server stopped, the CPU remains idle. With the nfs kernel server running, as soon as one client requests a connection, the kworker process jumps to 100% CPU again. After some random time, the nfs kernel server no longer accepts requests from clients. Restarting the service allows clients to reconnect. The syslog shows no relevant information. This problem has never appeared on a very similar server setup with 12.04. Configration: The svcgssd is not running. I played with various configurations (enabling/disabling NFSv3 and NFSv4), but it makes no difference. I tried to enable event debugging: # echo workqueue:workqueue_queue_work /sys/kernel/debug/tracing/set_event # cat /sys/kernel/debug/tracing/trace_pipe /var/tmp/kerntrace.txt and found the following kernel trace in a tight loop: [...] kworker/2:1-86[002] d... 161940.910668: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910674: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910675: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910681: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910682: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910688: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910689: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910695: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910696: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910702: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 [...] At present, I have to consider NFS fubar. Thanks, Mark ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No
[Kernel-packages] [Bug 1319244] Re: iostat: Cannot open /proc/stat: Cannot allocate memory
Any news about how the test kernels did fare? -- 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/1319244 Title: iostat: Cannot open /proc/stat: Cannot allocate memory Status in “linux” package in Ubuntu: Confirmed Bug description: Intermitently I get errors stating that various programs cannot allocate memory when reading /proc/stat I have 2 servers that are affected by the issue. Probably a duplicate of 1226172 [1764593.455329] top: page allocation failure: order:4, mode:0x1040d0 [1764593.455335] CPU: 3 PID: 10323 Comm: top Tainted: GF O 3.11.0-18-generic #32-Ubuntu [1764593.455338] Hardware name: Intel Corporation S2400SC/S2400SC, BIOS SE5C600.86B.02.02.0002.122320131210 12/23/2013 [1764593.455340] 88042670b9d0 816e8571 001040d0 [1764593.455345] 88042670ba58 81144ae0 880a3fffcb48 [1764593.455348] 000e 88042670ba28 0040 0007 [1764593.455351] Call Trace: [1764593.455361] [816e8571] dump_stack+0x45/0x56 [1764593.455367] [81144ae0] warn_alloc_failed+0xf0/0x140 [1764593.455371] [81148a15] __alloc_pages_nodemask+0x725/0x920 [1764593.455376] [81184589] alloc_pages_current+0xa9/0x160 [1764593.455379] [81143bfe] __get_free_pages+0xe/0x50 [1764593.455384] [8118d75e] kmalloc_order_trace+0x2e/0xa0 [1764593.455388] [811c9960] ? single_open+0xb0/0xb0 [1764593.455391] [8118ee19] __kmalloc+0x159/0x180 [1764593.455393] [811c9960] ? single_open+0xb0/0xb0 [1764593.455398] [81213c10] stat_open+0x50/0xc0 [1764593.455401] [8120a700] proc_reg_open+0x70/0x110 [1764593.455405] [811a5d4b] do_dentry_open+0x1eb/0x280 [1764593.455408] [8120a690] ? proc_reg_release+0x70/0x70 [1764593.455411] [811a5e69] vfs_open+0x49/0x50 [1764593.455415] [811b5e13] do_last+0x1c3/0xe50 [1764593.455418] [8118e5d8] ? kmem_cache_alloc_trace+0x108/0x130 [1764593.455421] [811b6b61] path_openat+0xc1/0x630 [1764593.455426] [811689d9] ? handle_mm_fault+0x299/0x670 [1764593.455429] [811b7eda] do_filp_open+0x3a/0x90 [1764593.455433] [816ef78e] ? _raw_spin_lock+0xe/0x20 [1764593.455437] [811c4847] ? __alloc_fd+0xa7/0x130 [1764593.455440] [811a704c] do_sys_open+0x12c/0x270 [1764593.455445] [81074989] ? __set_current_blocked+0x49/0x60 [1764593.455448] [811a71ae] SyS_open+0x1e/0x20 [1764593.455452] [816f841d] system_call_fastpath+0x1a/0x1f [1764593.455454] Mem-Info: [1764593.455455] Node 0 DMA per-cpu: [1764593.455458] CPU0: hi:0, btch: 1 usd: 0 [1764593.455459] CPU1: hi:0, btch: 1 usd: 0 [1764593.455461] CPU2: hi:0, btch: 1 usd: 0 [1764593.455462] CPU3: hi:0, btch: 1 usd: 0 [1764593.455463] CPU4: hi:0, btch: 1 usd: 0 [1764593.455465] CPU5: hi:0, btch: 1 usd: 0 [1764593.455466] CPU6: hi:0, btch: 1 usd: 0 [1764593.455468] CPU7: hi:0, btch: 1 usd: 0 [1764593.455469] Node 0 DMA32 per-cpu: [1764593.455471] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455472] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455474] CPU2: hi: 186, btch: 31 usd: 0 [1764593.455475] CPU3: hi: 186, btch: 31 usd: 0 [1764593.455477] CPU4: hi: 186, btch: 31 usd: 0 [1764593.455478] CPU5: hi: 186, btch: 31 usd: 0 [1764593.455480] CPU6: hi: 186, btch: 31 usd: 0 [1764593.455481] CPU7: hi: 186, btch: 31 usd: 0 [1764593.455482] Node 0 Normal per-cpu: [1764593.455484] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455485] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455487] CPU2: hi: 186, btch: 31 usd: 0 [1764593.455488] CPU3: hi: 186, btch: 31 usd: 0 [1764593.455490] CPU4: hi: 186, btch: 31 usd: 0 [1764593.455491] CPU5: hi: 186, btch: 31 usd: 0 [1764593.455492] CPU6: hi: 186, btch: 31 usd: 0 [1764593.455494] CPU7: hi: 186, btch: 31 usd: 0 [1764593.455495] Node 1 Normal per-cpu: [1764593.455497] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455498] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455500] CPU2: hi: 186, btch: 31 usd: 0 [1764593.455501] CPU3: hi: 186, btch: 31 usd: 0 [1764593.455503] CPU4: hi: 186, btch: 31 usd: 0 [1764593.455504] CPU5: hi: 186, btch: 31 usd: 30 [1764593.455505] CPU6: hi: 186, btch: 31 usd: 0 [1764593.455507] CPU7: hi: 186, btch: 31 usd: 0 [1764593.455511] active_anon:4739030 inactive_anon:2482840 isolated_anon:0 [1764593.455511] active_file:6228818 inactive_file:5945293 isolated_file:0 [1764593.455511]
[Kernel-packages] [Bug 1322407] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
Oh, sorry, actually it was just me hitting too many Fs. So 32767 (0x7fff) should be enough. I guess the other value is ok, too just sets too many bits in the mask. Yes, the messages should end up in syslog. With all debugging turned on there will be quite a bit of logging going on. Hope this does not change timing in a way that the problem does not show up anymore. -- 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/1322407 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly Status in “linux” package in Ubuntu: Confirmed Bug description: This concerns the server edition of 14.04. I have set up a NFS server. Once I attach at least one client, one kworker process starts to use 100% CPU. The runaway kworker returns to idle when I reset the NFS server daemon with service nfs-kernel-server stop followed by service nfs-kernel-server start. With the nfs kernel server stopped, the CPU remains idle. With the nfs kernel server running, as soon as one client requests a connection, the kworker process jumps to 100% CPU again. After some random time, the nfs kernel server no longer accepts requests from clients. Restarting the service allows clients to reconnect. The syslog shows no relevant information. This problem has never appeared on a very similar server setup with 12.04. Configration: The svcgssd is not running. I played with various configurations (enabling/disabling NFSv3 and NFSv4), but it makes no difference. I tried to enable event debugging: # echo workqueue:workqueue_queue_work /sys/kernel/debug/tracing/set_event # cat /sys/kernel/debug/tracing/trace_pipe /var/tmp/kerntrace.txt and found the following kernel trace in a tight loop: [...] kworker/2:1-86[002] d... 161940.910668: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910674: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910675: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910681: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910682: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910688: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910689: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910695: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910696: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910702: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 [...] At present, I have to consider NFS fubar. Thanks, Mark ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/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: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Thu May 22 22:48:48 2014 HibernationDevice: RESUME=UUID=adcdeef5-9b46-4ea4-b9f4-b6e642ea91e8 InstallationDate: Installed on 2014-05-12 (10 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2)
[Kernel-packages] [Bug 1322407] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
If /proc/mounts shows nvsvers=4 I would assume as well that nfsv4 is used. Formally I had the feeling that the examples looked like for really using nfsv4 one would need to have one entry in /etc/exports declaring a fsid=0 (iow the root) and then clients would ask for paths relative to that root. On one hand I *think* that I remember someone asking on irc and having issues when not following that. Which was another thing that seemed to have worked before. For the debugging, I think it does give me a rough idea, just need to match that up against some code. Which will probably take a bit. But somehow it appears to try to connect but then to think the socket needs to be released for some reason. And possibly it either is failing to release it with some unexpected condition or incorrectly assumes it is still connected and repeats this forever. Cannot really think of a reason why this is related (or not) to another server running (at least yet). -- 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/1322407 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly Status in “linux” package in Ubuntu: Confirmed Bug description: This concerns the server edition of 14.04. I have set up a NFS server. Once I attach at least one client, one kworker process starts to use 100% CPU. The runaway kworker returns to idle when I reset the NFS server daemon with service nfs-kernel-server stop followed by service nfs-kernel-server start. With the nfs kernel server stopped, the CPU remains idle. With the nfs kernel server running, as soon as one client requests a connection, the kworker process jumps to 100% CPU again. After some random time, the nfs kernel server no longer accepts requests from clients. Restarting the service allows clients to reconnect. The syslog shows no relevant information. This problem has never appeared on a very similar server setup with 12.04. Configration: The svcgssd is not running. I played with various configurations (enabling/disabling NFSv3 and NFSv4), but it makes no difference. I tried to enable event debugging: # echo workqueue:workqueue_queue_work /sys/kernel/debug/tracing/set_event # cat /sys/kernel/debug/tracing/trace_pipe /var/tmp/kerntrace.txt and found the following kernel trace in a tight loop: [...] kworker/2:1-86[002] d... 161940.910668: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910674: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910675: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910681: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910682: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910688: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910689: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910695: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910696: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910702: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 [...] At present, I have to consider NFS fubar. Thanks, Mark ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0',
[Kernel-packages] [Bug 1322407] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
Now this also explains why I had a hard time (iow was not being able to) reproducing this here. Since this indeed is a rather unusual corner case, I can put it a little lower on the list. Still I would try to understand the debug output enough to have some better idea about how that windows app is getting NFS into such a mess. Maybe there is some way to at least weaken the effects. About the fsid=0 exports. Yeah, it seems like a bit of a twisted way of setting things up. That face that I have to mount server:/ for the export defined as fsid=0 I can grasp. But then how other mounts are matched to be below this and to be NFSv4 is not really that obvious. -- 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/1322407 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly Status in “linux” package in Ubuntu: Confirmed Bug description: This concerns the server edition of 14.04. I have set up a NFS server. Once I attach at least one client, one kworker process starts to use 100% CPU. The runaway kworker returns to idle when I reset the NFS server daemon with service nfs-kernel-server stop followed by service nfs-kernel-server start. With the nfs kernel server stopped, the CPU remains idle. With the nfs kernel server running, as soon as one client requests a connection, the kworker process jumps to 100% CPU again. After some random time, the nfs kernel server no longer accepts requests from clients. Restarting the service allows clients to reconnect. The syslog shows no relevant information. This problem has never appeared on a very similar server setup with 12.04. Configration: The svcgssd is not running. I played with various configurations (enabling/disabling NFSv3 and NFSv4), but it makes no difference. I tried to enable event debugging: # echo workqueue:workqueue_queue_work /sys/kernel/debug/tracing/set_event # cat /sys/kernel/debug/tracing/trace_pipe /var/tmp/kerntrace.txt and found the following kernel trace in a tight loop: [...] kworker/2:1-86[002] d... 161940.910668: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910674: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910675: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910681: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910682: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910688: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910689: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910695: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910696: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910702: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 [...] At present, I have to consider NFS fubar. Thanks, Mark ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/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: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error:
[Kernel-packages] [Bug 1322407] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
Deeper inspection of the logs looks like the problem is some connection attempt when xprt is not connected. Part of that procedure is to re-use the connection which forces the xprt to disconnect (so the socket can be re-used). This triggers a state change (TCP_CLOSE) and wakes up the task waiting for the connection. But the connection state then in INPROGRESS which somehow gets translated into EGAIN and that triggers call_bind which repeats the re-use of socket process. With that lead, I found two commits upstream referring to this commit that introduces that behaviour: * 561ec1603171 (SUNRPC: call_connect_status should recheck bind..) The two fixes related to that are: * 1fa3e2e SUNRPC: Ensure call_connect_status() deals correctly with SOFTCONN tasks * 485f225 SUNRPC: Ensure that call_connect times out correctly The latter would at least cause timeouts to be re-adjusted before looping back into call_bind. So it might be worth trying those. I build a trusty kernel with those two patches added. The debs are at http://people.canonical.com/~smb/lp1322407/ Could you install those on the server side and see whether this helps with the problem? -- 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/1322407 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly Status in “linux” package in Ubuntu: Confirmed Bug description: This concerns the server edition of 14.04. I have set up a NFS server. Once I attach at least one client, one kworker process starts to use 100% CPU. The runaway kworker returns to idle when I reset the NFS server daemon with service nfs-kernel-server stop followed by service nfs-kernel-server start. With the nfs kernel server stopped, the CPU remains idle. With the nfs kernel server running, as soon as one client requests a connection, the kworker process jumps to 100% CPU again. After some random time, the nfs kernel server no longer accepts requests from clients. Restarting the service allows clients to reconnect. The syslog shows no relevant information. This problem has never appeared on a very similar server setup with 12.04. Configration: The svcgssd is not running. I played with various configurations (enabling/disabling NFSv3 and NFSv4), but it makes no difference. I tried to enable event debugging: # echo workqueue:workqueue_queue_work /sys/kernel/debug/tracing/set_event # cat /sys/kernel/debug/tracing/trace_pipe /var/tmp/kerntrace.txt and found the following kernel trace in a tight loop: [...] kworker/2:1-86[002] d... 161940.910668: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910674: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910675: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910681: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910682: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910688: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910689: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910695: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910696: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910702: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 [...] At present, I have to consider NFS fubar. Thanks, Mark ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.1
[Kernel-packages] [Bug 1322407] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
Thanks Mark. I will propose those for 14.04 (Trusty) then. ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Importance: Undecided = High ** Changed in: linux (Ubuntu Trusty) Status: New = In Progress ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) = Stefan Bader (smb) ** Changed in: linux (Ubuntu) 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/1322407 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: In Progress Bug description: This concerns the server edition of 14.04. I have set up a NFS server. Once I attach at least one client, one kworker process starts to use 100% CPU. The runaway kworker returns to idle when I reset the NFS server daemon with service nfs-kernel-server stop followed by service nfs-kernel-server start. With the nfs kernel server stopped, the CPU remains idle. With the nfs kernel server running, as soon as one client requests a connection, the kworker process jumps to 100% CPU again. After some random time, the nfs kernel server no longer accepts requests from clients. Restarting the service allows clients to reconnect. The syslog shows no relevant information. This problem has never appeared on a very similar server setup with 12.04. Configration: The svcgssd is not running. I played with various configurations (enabling/disabling NFSv3 and NFSv4), but it makes no difference. I tried to enable event debugging: # echo workqueue:workqueue_queue_work /sys/kernel/debug/tracing/set_event # cat /sys/kernel/debug/tracing/trace_pipe /var/tmp/kerntrace.txt and found the following kernel trace in a tight loop: [...] kworker/2:1-86[002] d... 161940.910668: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910674: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910675: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910681: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910682: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910688: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910689: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910695: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910696: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910702: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 [...] At present, I have to consider NFS fubar. Thanks, Mark ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/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: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Thu May 22 22:48:48 2014 HibernationDevice: RESUME=UUID=adcdeef5-9b46-4ea4-b9f4-b6e642ea91e8
[Kernel-packages] [Bug 1322407] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
The fix-released for the development kernel is based on both patches being in the 3.14.4 upstream stable tree. -- 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/1322407 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: In Progress Bug description: This concerns the server edition of 14.04. I have set up a NFS server. Once I attach at least one client, one kworker process starts to use 100% CPU. The runaway kworker returns to idle when I reset the NFS server daemon with service nfs-kernel-server stop followed by service nfs-kernel-server start. With the nfs kernel server stopped, the CPU remains idle. With the nfs kernel server running, as soon as one client requests a connection, the kworker process jumps to 100% CPU again. After some random time, the nfs kernel server no longer accepts requests from clients. Restarting the service allows clients to reconnect. The syslog shows no relevant information. This problem has never appeared on a very similar server setup with 12.04. Configration: The svcgssd is not running. I played with various configurations (enabling/disabling NFSv3 and NFSv4), but it makes no difference. I tried to enable event debugging: # echo workqueue:workqueue_queue_work /sys/kernel/debug/tracing/set_event # cat /sys/kernel/debug/tracing/trace_pipe /var/tmp/kerntrace.txt and found the following kernel trace in a tight loop: [...] kworker/2:1-86[002] d... 161940.910668: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910674: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910675: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910681: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910682: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910688: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910689: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910695: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910696: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910702: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 [...] At present, I have to consider NFS fubar. Thanks, Mark ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/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: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Thu May 22 22:48:48 2014 HibernationDevice: RESUME=UUID=adcdeef5-9b46-4ea4-b9f4-b6e642ea91e8 InstallationDate: Installed on 2014-05-12 (10 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcEnviron: TERM=xterm PATH=(custom, no
[Kernel-packages] [Bug 1319244] Re: iostat: Cannot open /proc/stat: Cannot allocate memory
It turns out we (you) were not the first ones running into it. The IBM mainframe guys (obviously) have the same need to potentially allow many CPUs. The upstream discussion is here: https://lkml.org/lkml/2014/5/21/251 So, while the change I made does work in this case, it can cause issues. Firstly /proc/stat uses a open_single interface. That means the proc file is not seekable and has no iterator. So all output has to be done in one go. And that means the buffer _has_ to be big enough to hold all output. Which means the part that limits the maximum size to order-3 allocations can cause issue on systems that really have a lot of CPUs. The other part of changing the buffer from holding x*possible number of CPUs to x*online CPUs was also thought of in the upstream thread. The problem there is that between open (buffer gets allocated) and show (buffer is filled) it is possible than a bunch of CPUs are set online. So one needs to be extra careful what would happen then. Sounds like the most likely outcome could be to have a vmalloc fallback option. But the discussion does not seem to be finished, yet. -- 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/1319244 Title: iostat: Cannot open /proc/stat: Cannot allocate memory Status in “linux” package in Ubuntu: Confirmed Bug description: Intermitently I get errors stating that various programs cannot allocate memory when reading /proc/stat I have 2 servers that are affected by the issue. Probably a duplicate of 1226172 [1764593.455329] top: page allocation failure: order:4, mode:0x1040d0 [1764593.455335] CPU: 3 PID: 10323 Comm: top Tainted: GF O 3.11.0-18-generic #32-Ubuntu [1764593.455338] Hardware name: Intel Corporation S2400SC/S2400SC, BIOS SE5C600.86B.02.02.0002.122320131210 12/23/2013 [1764593.455340] 88042670b9d0 816e8571 001040d0 [1764593.455345] 88042670ba58 81144ae0 880a3fffcb48 [1764593.455348] 000e 88042670ba28 0040 0007 [1764593.455351] Call Trace: [1764593.455361] [816e8571] dump_stack+0x45/0x56 [1764593.455367] [81144ae0] warn_alloc_failed+0xf0/0x140 [1764593.455371] [81148a15] __alloc_pages_nodemask+0x725/0x920 [1764593.455376] [81184589] alloc_pages_current+0xa9/0x160 [1764593.455379] [81143bfe] __get_free_pages+0xe/0x50 [1764593.455384] [8118d75e] kmalloc_order_trace+0x2e/0xa0 [1764593.455388] [811c9960] ? single_open+0xb0/0xb0 [1764593.455391] [8118ee19] __kmalloc+0x159/0x180 [1764593.455393] [811c9960] ? single_open+0xb0/0xb0 [1764593.455398] [81213c10] stat_open+0x50/0xc0 [1764593.455401] [8120a700] proc_reg_open+0x70/0x110 [1764593.455405] [811a5d4b] do_dentry_open+0x1eb/0x280 [1764593.455408] [8120a690] ? proc_reg_release+0x70/0x70 [1764593.455411] [811a5e69] vfs_open+0x49/0x50 [1764593.455415] [811b5e13] do_last+0x1c3/0xe50 [1764593.455418] [8118e5d8] ? kmem_cache_alloc_trace+0x108/0x130 [1764593.455421] [811b6b61] path_openat+0xc1/0x630 [1764593.455426] [811689d9] ? handle_mm_fault+0x299/0x670 [1764593.455429] [811b7eda] do_filp_open+0x3a/0x90 [1764593.455433] [816ef78e] ? _raw_spin_lock+0xe/0x20 [1764593.455437] [811c4847] ? __alloc_fd+0xa7/0x130 [1764593.455440] [811a704c] do_sys_open+0x12c/0x270 [1764593.455445] [81074989] ? __set_current_blocked+0x49/0x60 [1764593.455448] [811a71ae] SyS_open+0x1e/0x20 [1764593.455452] [816f841d] system_call_fastpath+0x1a/0x1f [1764593.455454] Mem-Info: [1764593.455455] Node 0 DMA per-cpu: [1764593.455458] CPU0: hi:0, btch: 1 usd: 0 [1764593.455459] CPU1: hi:0, btch: 1 usd: 0 [1764593.455461] CPU2: hi:0, btch: 1 usd: 0 [1764593.455462] CPU3: hi:0, btch: 1 usd: 0 [1764593.455463] CPU4: hi:0, btch: 1 usd: 0 [1764593.455465] CPU5: hi:0, btch: 1 usd: 0 [1764593.455466] CPU6: hi:0, btch: 1 usd: 0 [1764593.455468] CPU7: hi:0, btch: 1 usd: 0 [1764593.455469] Node 0 DMA32 per-cpu: [1764593.455471] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455472] CPU1: hi: 186, btch: 31 usd: 0 [1764593.455474] CPU2: hi: 186, btch: 31 usd: 0 [1764593.455475] CPU3: hi: 186, btch: 31 usd: 0 [1764593.455477] CPU4: hi: 186, btch: 31 usd: 0 [1764593.455478] CPU5: hi: 186, btch: 31 usd: 0 [1764593.455480] CPU6: hi: 186, btch: 31 usd: 0 [1764593.455481] CPU7: hi: 186, btch: 31 usd: 0 [1764593.455482] Node 0 Normal per-cpu: [1764593.455484] CPU0: hi: 186, btch: 31 usd: 0 [1764593.455485] CPU
[Kernel-packages] [Bug 1244176] Re: Server 13.10 Install Fails with USB Keyboard (Appears to Hang)
Really you should file a new bug report (like anybody else still running into keyboard issues). Like I said in comment #35 the symptoms may be the same but the missing module of _this_ bug report is included in 14.04. Make sure to describe the environment with as much detail as possible (keyboard locally attached or a (v)KVM, locally attached at usb2 or 3 port (usually black or blue sockets). Post the new bug number here to make the report easily findable. Thanks. -- 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/1244176 Title: Server 13.10 Install Fails with USB Keyboard (Appears to Hang) Status in “initramfs-tools” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Fix Released Status in “initramfs-tools” source package in Saucy: Invalid Status in “linux” source package in Saucy: Fix Released Status in “initramfs-tools” source package in Trusty: Invalid Status in “linux” source package in Trusty: Fix Released Bug description: A fresh install of Server 13.10 on old hardware fails when a USB keyboard is present. The installation succeeds when a PS/2 keyboard is installed. The installation appears to hang at the third screen, which is Select Language. The screen does not respond to keyboard or mouse events. The issue was experienced independently on HP/Compag dc5850 with Athlon X2 2.3 GHz dual core, 4GB RAM; and DELL Optiplex 755. See Server 13.10 Install Hangs, http://askubuntu.com/questions/364945/server-13-10-install- hangs/364949. The issue was not present on Server 12.04.3 LTS or 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1244176/+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 1322407] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
It might be a bit unclear but the main task is fix released because Utopic (14.10 and current trunk) is based on 3.15 right now (will move to 3.16 before release). So Utopic is ok. For Trusty this is still in the mill. The patches have references to this report. So you should see an automatic post here when a kernel with the fixes hits proposed. Since I found both patches in the git repo/branch used to prepare the next update, I mark the Trusty task as fix committed. That still does not mean there is a kernel to test officially. Just that it is in the repository. ** Changed in: linux (Ubuntu Trusty) Status: In Progress = Fix Committed -- 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/1322407 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Bug description: This concerns the server edition of 14.04. I have set up a NFS server. Once I attach at least one client, one kworker process starts to use 100% CPU. The runaway kworker returns to idle when I reset the NFS server daemon with service nfs-kernel-server stop followed by service nfs-kernel-server start. With the nfs kernel server stopped, the CPU remains idle. With the nfs kernel server running, as soon as one client requests a connection, the kworker process jumps to 100% CPU again. After some random time, the nfs kernel server no longer accepts requests from clients. Restarting the service allows clients to reconnect. The syslog shows no relevant information. This problem has never appeared on a very similar server setup with 12.04. Configration: The svcgssd is not running. I played with various configurations (enabling/disabling NFSv3 and NFSv4), but it makes no difference. I tried to enable event debugging: # echo workqueue:workqueue_queue_work /sys/kernel/debug/tracing/set_event # cat /sys/kernel/debug/tracing/trace_pipe /var/tmp/kerntrace.txt and found the following kernel trace in a tight loop: [...] kworker/2:1-86[002] d... 161940.910668: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910674: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910675: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910681: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910682: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910688: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910689: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910695: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910696: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910702: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 [...] At present, I have to consider NFS fubar. Thanks, Mark ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/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: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such
[Kernel-packages] [Bug 1244176] Re: Server 13.10 Install Fails with USB Keyboard (Appears to Hang)
Pragmatically I would just go for a 14.04 (LTS) install. It is pretty stable already and following updates you would end up with a long-term supported install. If it has to be 13.10 then its either a netinstall with a preseed (so no interaction is required), but that is slightly complicated. Or use a 13.04 install media and upgrade from there. A bit tedious. -- 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/1244176 Title: Server 13.10 Install Fails with USB Keyboard (Appears to Hang) Status in “initramfs-tools” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Fix Released Status in “initramfs-tools” source package in Saucy: Invalid Status in “linux” source package in Saucy: Fix Released Status in “initramfs-tools” source package in Trusty: Invalid Status in “linux” source package in Trusty: Fix Released Bug description: A fresh install of Server 13.10 on old hardware fails when a USB keyboard is present. The installation succeeds when a PS/2 keyboard is installed. The installation appears to hang at the third screen, which is Select Language. The screen does not respond to keyboard or mouse events. The issue was experienced independently on HP/Compag dc5850 with Athlon X2 2.3 GHz dual core, 4GB RAM; and DELL Optiplex 755. See Server 13.10 Install Hangs, http://askubuntu.com/questions/364945/server-13-10-install- hangs/364949. The issue was not present on Server 12.04.3 LTS or 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1244176/+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 1268906] Re: cpu soft lockup running kvm
** Also affects: linux (Ubuntu Trusty) Importance: Medium Assignee: Stefan Bader (smb) Status: Confirmed ** Also affects: qemu-kvm (Ubuntu Trusty) Importance: Medium Status: Confirmed ** Changed in: qemu-kvm (Ubuntu Trusty) Status: Confirmed = Invalid -- 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/1268906 Title: cpu soft lockup running kvm Status in “linux” package in Ubuntu: Confirmed Status in “qemu-kvm” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Confirmed Status in “qemu-kvm” source package in Trusty: Invalid Bug description: Ran twice - first time running kvm killed my system. The second time, I just got lots of kernel oops messages in dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3250 F pulseaudio /dev/snd/controlC0: james 3250 F pulseaudio /dev/snd/pcmC0D0p: james 3250 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 10:29:20 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
** Changed in: linux (Ubuntu Trusty) Status: In Progress = Fix Committed -- 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/1268906 Title: cpu soft lockup running kvm Status in “linux” package in Ubuntu: Fix Committed Status in “qemu-kvm” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Fix Committed Status in “qemu-kvm” source package in Trusty: Invalid Bug description: Ran twice - first time running kvm killed my system. The second time, I just got lots of kernel oops messages in dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3250 F pulseaudio /dev/snd/controlC0: james 3250 F pulseaudio /dev/snd/pcmC0D0p: james 3250 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 10:29:20 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1269086] Re: RAID1 installations fail to complete on trusty server images with 3.13
I just did a manual expert install of the current server daily (3.13.0-3-generic #18 kernel) and that did complete with raid getting synced. Guest was configured with 1VCPU and 1G of memory. I used 2 LVs of 8G size to have two virtio disks. -- 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/1269086 Title: RAID1 installations fail to complete on trusty server images with 3.13 Status in “linux” package in Ubuntu: Incomplete Bug description: Starting from 20140109, with 3.13.0-1-generic kernel onwards trusty- server installations with RAID1 configuration fail to complete the installations. This occurs with both amd64 and i386 images. The following stack trace is found in the installer syslog: Jan 14 10:08:20 net/hw-detect.hotplug: Detected hotpluggable network interface lo Jan 14 10:11:52 kernel: [ 1680.528225] INFO: task md0_resync:16918 blocked for more than 120 seconds. Jan 14 10:11:52 kernel: [ 1680.528236] Tainted: GF 3.13.0-2-generic #17-Ubuntu Jan 14 10:11:52 kernel: [ 1680.528239] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Jan 14 10:11:52 kernel: [ 1680.528242] md0_resync D 88001f414440 0 16918 2 0x Jan 14 10:11:52 kernel: [ 1680.528251] 880013b23bf8 0006 880013559800 880013b23fd8 Jan 14 10:11:52 kernel: [ 1680.528257] 00014440 00014440 880013559800 88000ce5ce80 Jan 14 10:11:52 kernel: [ 1680.528262] 88001351deb8 880013b23c70 88001351dea0 88001351de40 Jan 14 10:11:52 kernel: [ 1680.528267] Call Trace: Jan 14 10:11:52 kernel: [ 1680.528287] [81709379] schedule+0x29/0x70 Jan 14 10:11:52 kernel: [ 1680.528297] [a0142457] sync_request+0x227/0xb30 [raid1] Jan 14 10:11:52 kernel: [ 1680.528310] [810a8a20] ? prepare_to_wait_event+0x100/0x100 Jan 14 10:11:52 kernel: [ 1680.528320] [815942a3] md_do_sync+0x993/0xdc0 Jan 14 10:11:52 kernel: [ 1680.528330] [8104f3ff] ? kvm_clock_read+0x1f/0x30 Jan 14 10:11:52 kernel: [ 1680.528340] [8101b809] ? sched_clock+0x9/0x10 Jan 14 10:11:52 kernel: [ 1680.528348] [8109a40d] ? sched_clock_local+0x1d/0x80 Jan 14 10:11:52 kernel: [ 1680.528355] [81590e48] md_thread+0x118/0x130 Jan 14 10:11:52 kernel: [ 1680.528360] [81590d30] ? mddev_unlock+0xe0/0xe0 Jan 14 10:11:52 kernel: [ 1680.528367] [81088212] kthread+0xd2/0xf0 Jan 14 10:11:52 kernel: [ 1680.528372] [81088140] ? kthread_create_on_node+0x190/0x190 Jan 14 10:11:52 kernel: [ 1680.528382] [8171587c] ret_from_fork+0x7c/0xb0 Jan 14 10:11:52 kernel: [ 1680.528387] [81088140] ? kthread_create_on_node+0x190/0x190 Jan 14 10:11:52 kernel: [ 1680.528393] INFO: task jbd2/md0-8:20260 blocked for more than 120 seconds. Jan 14 10:11:52 kernel: [ 1680.528396] Tainted: GF 3.13.0-2-generic #17-Ubuntu Jan 14 10:11:52 kernel: [ 1680.528398] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Jan 14 10:11:52 kernel: [ 1680.528400] jbd2/md0-8 D 88001f414440 0 20260 2 0x Jan 14 10:11:52 kernel: [ 1680.528406] 88001fbf5888 0002 88001c053000 88001fbf5fd8 Jan 14 10:11:52 kernel: [ 1680.528411] 00014440 00014440 88001c053000 88001351de40 Jan 14 10:11:52 kernel: [ 1680.528415] 88001351deb8 88001351dea0 88001c053000 88001c22f180 Jan 14 10:11:52 kernel: [ 1680.528420] Call Trace: Jan 14 10:11:52 kernel: [ 1680.528426] [81709379] schedule+0x29/0x70 Jan 14 10:11:52 kernel: [ 1680.528432] [a014076c] wait_barrier+0x13c/0x2a0 [raid1] Jan 14 10:11:52 kernel: [ 1680.528438] [810a8a20] ? prepare_to_wait_event+0x100/0x100 Jan 14 10:11:52 kernel: [ 1680.528444] [a014158f] make_request+0x7f/0xd20 [raid1] Jan 14 10:11:52 kernel: [ 1680.528456] [814155d8] ? virtqueue_add_sgs+0x458/0x590 Jan 14 10:11:52 kernel: [ 1680.528467] [8114e3a5] ? mempool_alloc_slab+0x15/0x20 Jan 14 10:11:52 kernel: [ 1680.528473] [8158dd25] md_make_request+0xd5/0x220 Jan 14 10:11:52 kernel: [ 1680.528481] [8132c062] generic_make_request+0xc2/0x110 Jan 14 10:11:52 kernel: [ 1680.528486] [8132c121] submit_bio+0x71/0x150 Jan 14 10:11:52 kernel: [ 1680.528495] [8124099e] ? ext4_bio_write_page+0x12e/0x2d0 Jan 14 10:11:52 kernel: [ 1680.528500] [81240815] ext4_io_submit+0x25/0x50 Jan 14 10:11:52 kernel: [ 1680.528506] [8123bd83] ext4_writepage+0xc3/0x440 Jan 14 10:11:52 kernel: [ 1680.528511] [8114c151] ? find_get_pages_tag+0xd1/0x180 Jan 14 10:11:52 kernel: [ 1680.528517] [811553e3] __writepage+0x13/0x40 Jan 14 10:11:52 kernel: [ 1680.528522]
[Kernel-packages] [Bug 1269086] Re: RAID1 installations fail to complete on trusty server images with 3.13
Could we confirm whether the automatic test runs still fail with the latest images? ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- 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/1269086 Title: RAID1 installations fail to complete on trusty server images with 3.13 Status in “linux” package in Ubuntu: Incomplete Bug description: Starting from 20140109, with 3.13.0-1-generic kernel onwards trusty- server installations with RAID1 configuration fail to complete the installations. This occurs with both amd64 and i386 images. The following stack trace is found in the installer syslog: Jan 14 10:08:20 net/hw-detect.hotplug: Detected hotpluggable network interface lo Jan 14 10:11:52 kernel: [ 1680.528225] INFO: task md0_resync:16918 blocked for more than 120 seconds. Jan 14 10:11:52 kernel: [ 1680.528236] Tainted: GF 3.13.0-2-generic #17-Ubuntu Jan 14 10:11:52 kernel: [ 1680.528239] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Jan 14 10:11:52 kernel: [ 1680.528242] md0_resync D 88001f414440 0 16918 2 0x Jan 14 10:11:52 kernel: [ 1680.528251] 880013b23bf8 0006 880013559800 880013b23fd8 Jan 14 10:11:52 kernel: [ 1680.528257] 00014440 00014440 880013559800 88000ce5ce80 Jan 14 10:11:52 kernel: [ 1680.528262] 88001351deb8 880013b23c70 88001351dea0 88001351de40 Jan 14 10:11:52 kernel: [ 1680.528267] Call Trace: Jan 14 10:11:52 kernel: [ 1680.528287] [81709379] schedule+0x29/0x70 Jan 14 10:11:52 kernel: [ 1680.528297] [a0142457] sync_request+0x227/0xb30 [raid1] Jan 14 10:11:52 kernel: [ 1680.528310] [810a8a20] ? prepare_to_wait_event+0x100/0x100 Jan 14 10:11:52 kernel: [ 1680.528320] [815942a3] md_do_sync+0x993/0xdc0 Jan 14 10:11:52 kernel: [ 1680.528330] [8104f3ff] ? kvm_clock_read+0x1f/0x30 Jan 14 10:11:52 kernel: [ 1680.528340] [8101b809] ? sched_clock+0x9/0x10 Jan 14 10:11:52 kernel: [ 1680.528348] [8109a40d] ? sched_clock_local+0x1d/0x80 Jan 14 10:11:52 kernel: [ 1680.528355] [81590e48] md_thread+0x118/0x130 Jan 14 10:11:52 kernel: [ 1680.528360] [81590d30] ? mddev_unlock+0xe0/0xe0 Jan 14 10:11:52 kernel: [ 1680.528367] [81088212] kthread+0xd2/0xf0 Jan 14 10:11:52 kernel: [ 1680.528372] [81088140] ? kthread_create_on_node+0x190/0x190 Jan 14 10:11:52 kernel: [ 1680.528382] [8171587c] ret_from_fork+0x7c/0xb0 Jan 14 10:11:52 kernel: [ 1680.528387] [81088140] ? kthread_create_on_node+0x190/0x190 Jan 14 10:11:52 kernel: [ 1680.528393] INFO: task jbd2/md0-8:20260 blocked for more than 120 seconds. Jan 14 10:11:52 kernel: [ 1680.528396] Tainted: GF 3.13.0-2-generic #17-Ubuntu Jan 14 10:11:52 kernel: [ 1680.528398] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Jan 14 10:11:52 kernel: [ 1680.528400] jbd2/md0-8 D 88001f414440 0 20260 2 0x Jan 14 10:11:52 kernel: [ 1680.528406] 88001fbf5888 0002 88001c053000 88001fbf5fd8 Jan 14 10:11:52 kernel: [ 1680.528411] 00014440 00014440 88001c053000 88001351de40 Jan 14 10:11:52 kernel: [ 1680.528415] 88001351deb8 88001351dea0 88001c053000 88001c22f180 Jan 14 10:11:52 kernel: [ 1680.528420] Call Trace: Jan 14 10:11:52 kernel: [ 1680.528426] [81709379] schedule+0x29/0x70 Jan 14 10:11:52 kernel: [ 1680.528432] [a014076c] wait_barrier+0x13c/0x2a0 [raid1] Jan 14 10:11:52 kernel: [ 1680.528438] [810a8a20] ? prepare_to_wait_event+0x100/0x100 Jan 14 10:11:52 kernel: [ 1680.528444] [a014158f] make_request+0x7f/0xd20 [raid1] Jan 14 10:11:52 kernel: [ 1680.528456] [814155d8] ? virtqueue_add_sgs+0x458/0x590 Jan 14 10:11:52 kernel: [ 1680.528467] [8114e3a5] ? mempool_alloc_slab+0x15/0x20 Jan 14 10:11:52 kernel: [ 1680.528473] [8158dd25] md_make_request+0xd5/0x220 Jan 14 10:11:52 kernel: [ 1680.528481] [8132c062] generic_make_request+0xc2/0x110 Jan 14 10:11:52 kernel: [ 1680.528486] [8132c121] submit_bio+0x71/0x150 Jan 14 10:11:52 kernel: [ 1680.528495] [8124099e] ? ext4_bio_write_page+0x12e/0x2d0 Jan 14 10:11:52 kernel: [ 1680.528500] [81240815] ext4_io_submit+0x25/0x50 Jan 14 10:11:52 kernel: [ 1680.528506] [8123bd83] ext4_writepage+0xc3/0x440 Jan 14 10:11:52 kernel: [ 1680.528511] [8114c151] ? find_get_pages_tag+0xd1/0x180 Jan 14 10:11:52 kernel: [ 1680.528517] [811553e3] __writepage+0x13/0x40 Jan 14 10:11:52 kernel: [ 1680.528522] [81155d5d] write_cache_pages+0x23d/0x4b0 Jan 14 10:11:52 kernel: [
[Kernel-packages] [Bug 1269086] Re: RAID1 installations fail to complete on trusty server images with 3.13
** Changed in: linux (Ubuntu) Assignee: (unassigned) = Stefan Bader (smb) -- 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/1269086 Title: RAID1 installations fail to complete on trusty server images with 3.13 Status in “linux” package in Ubuntu: Incomplete Bug description: Starting from 20140109, with 3.13.0-1-generic kernel onwards trusty- server installations with RAID1 configuration fail to complete the installations. This occurs with both amd64 and i386 images. The following stack trace is found in the installer syslog: Jan 14 10:08:20 net/hw-detect.hotplug: Detected hotpluggable network interface lo Jan 14 10:11:52 kernel: [ 1680.528225] INFO: task md0_resync:16918 blocked for more than 120 seconds. Jan 14 10:11:52 kernel: [ 1680.528236] Tainted: GF 3.13.0-2-generic #17-Ubuntu Jan 14 10:11:52 kernel: [ 1680.528239] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Jan 14 10:11:52 kernel: [ 1680.528242] md0_resync D 88001f414440 0 16918 2 0x Jan 14 10:11:52 kernel: [ 1680.528251] 880013b23bf8 0006 880013559800 880013b23fd8 Jan 14 10:11:52 kernel: [ 1680.528257] 00014440 00014440 880013559800 88000ce5ce80 Jan 14 10:11:52 kernel: [ 1680.528262] 88001351deb8 880013b23c70 88001351dea0 88001351de40 Jan 14 10:11:52 kernel: [ 1680.528267] Call Trace: Jan 14 10:11:52 kernel: [ 1680.528287] [81709379] schedule+0x29/0x70 Jan 14 10:11:52 kernel: [ 1680.528297] [a0142457] sync_request+0x227/0xb30 [raid1] Jan 14 10:11:52 kernel: [ 1680.528310] [810a8a20] ? prepare_to_wait_event+0x100/0x100 Jan 14 10:11:52 kernel: [ 1680.528320] [815942a3] md_do_sync+0x993/0xdc0 Jan 14 10:11:52 kernel: [ 1680.528330] [8104f3ff] ? kvm_clock_read+0x1f/0x30 Jan 14 10:11:52 kernel: [ 1680.528340] [8101b809] ? sched_clock+0x9/0x10 Jan 14 10:11:52 kernel: [ 1680.528348] [8109a40d] ? sched_clock_local+0x1d/0x80 Jan 14 10:11:52 kernel: [ 1680.528355] [81590e48] md_thread+0x118/0x130 Jan 14 10:11:52 kernel: [ 1680.528360] [81590d30] ? mddev_unlock+0xe0/0xe0 Jan 14 10:11:52 kernel: [ 1680.528367] [81088212] kthread+0xd2/0xf0 Jan 14 10:11:52 kernel: [ 1680.528372] [81088140] ? kthread_create_on_node+0x190/0x190 Jan 14 10:11:52 kernel: [ 1680.528382] [8171587c] ret_from_fork+0x7c/0xb0 Jan 14 10:11:52 kernel: [ 1680.528387] [81088140] ? kthread_create_on_node+0x190/0x190 Jan 14 10:11:52 kernel: [ 1680.528393] INFO: task jbd2/md0-8:20260 blocked for more than 120 seconds. Jan 14 10:11:52 kernel: [ 1680.528396] Tainted: GF 3.13.0-2-generic #17-Ubuntu Jan 14 10:11:52 kernel: [ 1680.528398] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Jan 14 10:11:52 kernel: [ 1680.528400] jbd2/md0-8 D 88001f414440 0 20260 2 0x Jan 14 10:11:52 kernel: [ 1680.528406] 88001fbf5888 0002 88001c053000 88001fbf5fd8 Jan 14 10:11:52 kernel: [ 1680.528411] 00014440 00014440 88001c053000 88001351de40 Jan 14 10:11:52 kernel: [ 1680.528415] 88001351deb8 88001351dea0 88001c053000 88001c22f180 Jan 14 10:11:52 kernel: [ 1680.528420] Call Trace: Jan 14 10:11:52 kernel: [ 1680.528426] [81709379] schedule+0x29/0x70 Jan 14 10:11:52 kernel: [ 1680.528432] [a014076c] wait_barrier+0x13c/0x2a0 [raid1] Jan 14 10:11:52 kernel: [ 1680.528438] [810a8a20] ? prepare_to_wait_event+0x100/0x100 Jan 14 10:11:52 kernel: [ 1680.528444] [a014158f] make_request+0x7f/0xd20 [raid1] Jan 14 10:11:52 kernel: [ 1680.528456] [814155d8] ? virtqueue_add_sgs+0x458/0x590 Jan 14 10:11:52 kernel: [ 1680.528467] [8114e3a5] ? mempool_alloc_slab+0x15/0x20 Jan 14 10:11:52 kernel: [ 1680.528473] [8158dd25] md_make_request+0xd5/0x220 Jan 14 10:11:52 kernel: [ 1680.528481] [8132c062] generic_make_request+0xc2/0x110 Jan 14 10:11:52 kernel: [ 1680.528486] [8132c121] submit_bio+0x71/0x150 Jan 14 10:11:52 kernel: [ 1680.528495] [8124099e] ? ext4_bio_write_page+0x12e/0x2d0 Jan 14 10:11:52 kernel: [ 1680.528500] [81240815] ext4_io_submit+0x25/0x50 Jan 14 10:11:52 kernel: [ 1680.528506] [8123bd83] ext4_writepage+0xc3/0x440 Jan 14 10:11:52 kernel: [ 1680.528511] [8114c151] ? find_get_pages_tag+0xd1/0x180 Jan 14 10:11:52 kernel: [ 1680.528517] [811553e3] __writepage+0x13/0x40 Jan 14 10:11:52 kernel: [ 1680.528522] [81155d5d] write_cache_pages+0x23d/0x4b0 Jan 14 10:11:52 kernel: [ 1680.528527] [811553d0] ? global_dirtyable_memory+0x40/0x40 Jan 14 10:11
[Kernel-packages] [Bug 1269401] Re: [Trusty] Switching framebuffers fails on VMs using cirrus
** Attachment added: dmesg.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269401/+attachment/3949420/+files/dmesg.log ** Tags added: trusty -- 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/1269401 Title: [Trusty] Switching framebuffers fails on VMs using cirrus Status in “linux” package in Ubuntu: Confirmed Bug description: Trusty Server (daily image 2014-01-15) Kernel: 3.13.0-3.18-generic 64bit Booting a VM which is set to use cirrus graphics there seems to (still) be a problem with the framebuffers. The kernel has a special KMS module which also has a framebuffer interface. During boot plymouth likely keeps the fb open which the kernel tries to replace the generic FB with the special one (and fails). Symptom is a system which seems to hang on boot when looking at the graphical console. [7.140598] checking generic (fc00 16) vs hw (fc00 200) [7.140603] fb: conflicting fb hw usage cirrusdrmfb vs simple - removing generic driver [7.140650] Console: switching to colour dummy device 80x25 [7.144410] [drm:cirrus_vram_init] *ERROR* can't reserve VRAM [7.144422] cirrus :00:02.0: Fatal error during GPU init: -6 [7.144426] Trying to free nonexistent resource febf4000-febf4fff [7.144431] Trying to free nonexistent resource fc00-fc3f [8.254229] systemd-udevd[302]: Failed to apply ACL on /dev/dri/card0: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269401/+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 1269401] [NEW] [Trusty] Switching framebuffers fails on VMs using cirrus
Public bug reported: Trusty Server (daily image 2014-01-15) Kernel: 3.13.0-3.18-generic 64bit Booting a VM which is set to use cirrus graphics there seems to (still) be a problem with the framebuffers. The kernel has a special KMS module which also has a framebuffer interface. During boot plymouth likely keeps the fb open which the kernel tries to replace the generic FB with the special one (and fails). Symptom is a system which seems to hang on boot when looking at the graphical console. [7.140598] checking generic (fc00 16) vs hw (fc00 200) [7.140603] fb: conflicting fb hw usage cirrusdrmfb vs simple - removing generic driver [7.140650] Console: switching to colour dummy device 80x25 [7.144410] [drm:cirrus_vram_init] *ERROR* can't reserve VRAM [7.144422] cirrus :00:02.0: Fatal error during GPU init: -6 [7.144426] Trying to free nonexistent resource febf4000-febf4fff [7.144431] Trying to free nonexistent resource fc00-fc3f [8.254229] systemd-udevd[302]: Failed to apply ACL on /dev/dri/card0: No such file or directory ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Tags: trusty ** Changed in: linux (Ubuntu) Status: New = 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/1269401 Title: [Trusty] Switching framebuffers fails on VMs using cirrus Status in “linux” package in Ubuntu: Confirmed Bug description: Trusty Server (daily image 2014-01-15) Kernel: 3.13.0-3.18-generic 64bit Booting a VM which is set to use cirrus graphics there seems to (still) be a problem with the framebuffers. The kernel has a special KMS module which also has a framebuffer interface. During boot plymouth likely keeps the fb open which the kernel tries to replace the generic FB with the special one (and fails). Symptom is a system which seems to hang on boot when looking at the graphical console. [7.140598] checking generic (fc00 16) vs hw (fc00 200) [7.140603] fb: conflicting fb hw usage cirrusdrmfb vs simple - removing generic driver [7.140650] Console: switching to colour dummy device 80x25 [7.144410] [drm:cirrus_vram_init] *ERROR* can't reserve VRAM [7.144422] cirrus :00:02.0: Fatal error during GPU init: -6 [7.144426] Trying to free nonexistent resource febf4000-febf4fff [7.144431] Trying to free nonexistent resource fc00-fc3f [8.254229] systemd-udevd[302]: Failed to apply ACL on /dev/dri/card0: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269401/+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 1269401] Re: [Trusty] Switching framebuffers fails on VMs using cirrus
** Attachment added: udev.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269401/+attachment/3949421/+files/udev.log ** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- 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/1269401 Title: [Trusty] Switching framebuffers fails on VMs using cirrus Status in “linux” package in Ubuntu: Confirmed Bug description: Trusty Server (daily image 2014-01-15) Kernel: 3.13.0-3.18-generic 64bit Booting a VM which is set to use cirrus graphics there seems to (still) be a problem with the framebuffers. The kernel has a special KMS module which also has a framebuffer interface. During boot plymouth likely keeps the fb open which the kernel tries to replace the generic FB with the special one (and fails). Symptom is a system which seems to hang on boot when looking at the graphical console. [7.140598] checking generic (fc00 16) vs hw (fc00 200) [7.140603] fb: conflicting fb hw usage cirrusdrmfb vs simple - removing generic driver [7.140650] Console: switching to colour dummy device 80x25 [7.144410] [drm:cirrus_vram_init] *ERROR* can't reserve VRAM [7.144422] cirrus :00:02.0: Fatal error during GPU init: -6 [7.144426] Trying to free nonexistent resource febf4000-febf4fff [7.144431] Trying to free nonexistent resource fc00-fc3f [8.254229] systemd-udevd[302]: Failed to apply ACL on /dev/dri/card0: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269401/+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 1270656] Re: Ubuntu 14.04 boots to blank console
The apport data from comment #11 shows a virtual machine on VMWare.
Looking at the first dmesg log, there seems to be some kind of resource
conflict between the simple-framebuffer driver and vmwgfx. For testing
you could probably try to create a file like /etc/modprobe.d/blacklist-
testing.conf with a line blacklist vmwgfx in it. That should give some
console (maybe not the most performant).
[0.782125] simple-framebuffer simple-framebuffer.0: framebuffer at
0xe800, 0x1d5000 bytes, mapped to 0xc9000838
[0.782128] simple-framebuffer simple-framebuffer.0: format=a8r8g8b8,
mode=800x600x32, linelength=3200
[0.784093] Console: switching to colour frame buffer device 100x37
[0.785022] simple-framebuffer simple-framebuffer.0: fb0: simplefb
registered!
...
[ 21.258191] vmwgfx :00:0f.0: BAR 1: can't reserve [mem
0xe800-0xefff pref]
[ 21.258193] [drm] It appears like vesafb is loaded. Ignore above error if
any.
[ 21.258469] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 21.258471] [drm] No driver support for vblank timestamp query.
[ 21.259320] [drm] Screen objects system initialized
[ 21.259325] [drm] Initialized vmwgfx 2.4.0 20120209 for :00:0f.0 on
minor 0
--
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/1270656
Title:
Ubuntu 14.04 boots to blank console
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console.
Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but ps axf shows
/sbin/getty running on tty{1..6}:
# ps axf | grep tty
880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4
885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5
890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2
891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3
893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6
4290 pts/1S+ 0:00 \_ grep --color=auto tty
1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1
Removing deprecated vga=768 from kernel commandline = doesn't boot into
800x600, keeps 640x480
Settings
GRUB_GFXMODE=800x600
GRUB_GFXPAYLOAD=800x600
are ignored.
Grub boots up with 800x600, switches back to 640x480 (setting
GRUB_GFXPAYLOAD to keep it is the same) kernel doesn't switch back
to 800x600.
Adding deprecated vga=768 back in:
Grub boots up with 800x600, switches back to 640x480, kernel switches back to
800x600, but doesn't use this console. No output at all. Keys are accepted (you
can login, but you'll have to guess what is going on on the screen).
Exactly the same error is found with debian. Switching to a self
compiled kernel solves this error. Looks a lot like some necessary
stuff for console resolution switching is missing in the debian
-/ubuntu-kernels.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: util-linux 2.20.1-5.1ubuntu13
ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
Uname: Linux 3.13.0-4-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
Date: Mon Jan 20 00:20:36 2014
InstallationDate: Installed on 2012-12-12 (403 days ago)
InstallationMedia: Ubuntu-Server 12.04.1 LTS Precise Pangolin - Release
amd64 (20120817.3)
ProcEnviron:
TERM=screen-bce
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270603] Re: trusty kernel panicking multiple times a day
Part of v3.13 final. We should get that patch with the next rebase. Marc, that screenshot counts as physical assault (or whatever the appropriate charge for making ones eyes bleed is). ;) -- 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/1270603 Title: trusty kernel panicking multiple times a day Status in “linux” package in Ubuntu: Confirmed Bug description: Just upgraded from Saucy to Trusty, and trusty kernel is now panicking multiple times a day. Harware is Asus UX32VD with a gigabit USB dongle. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-4-generic 3.13.0-4.19 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mdeslaur 2570 F pulseaudio CurrentDesktop: Unity Date: Sun Jan 19 11:23:21 2014 HibernationDevice: RESUME=UUID=d629bf89-9bbe-4485-84ac-66a484464fae InstallationDate: Installed on 2013-11-26 (53 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-4-generic.efi.signed root=UUID=daa96c43-a895-4b0f-9a8a-470cf54d2f06 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-4-generic N/A linux-backports-modules-3.13.0-4-generic N/A linux-firmware1.121 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2014-01-17 (1 days ago) dmi.bios.date: 09/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD 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.:bvrUX32VD.212:bd09/17/2012:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD 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/1270603/+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 1270228] Re: Loading partman-xfs failed for unknown reasons. Aborting error in trusty server installations
** Changed in: linux (Ubuntu) Assignee: (unassigned) = Stefan Bader (smb) -- 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/1270228 Title: Loading partman-xfs failed for unknown reasons. Aborting error in trusty server installations Status in “linux” package in Ubuntu: Confirmed Bug description: With 20140117 (containing kernel 3.13.0-4-generic) trusty server images the above error message dialog appears during the installation and the following could be seen in the install syslog: Jan 17 16:49:28 anna[8497]: DEBUG: retrieving partman-target 83ubuntu1 Jan 17 16:49:28 debconf: -- SUBST anna/progress_step_retr PACKAGE partman-target Jan 17 16:49:28 debconf: Adding [PACKAGE] - [partman-target] Jan 17 16:49:28 debconf: -- 0 Jan 17 16:49:28 debconf: -- PROGRESS INFO anna/progress_step_retr Jan 17 16:49:28 debconf: -- 0 OK Jan 17 16:49:28 anna[8497]: corrupted status flag!!: 0 Jan 17 16:49:28 anna[8497]: (process:10536): tar: write error: No space left on device Jan 17 16:49:28 anna[8497]: (process:10536): tar: write error: No space left on device Jan 17 16:49:28 debconf: -- PROGRESS STEP 1 Jan 17 16:49:28 debconf: -- 0 OK Jan 17 16:49:28 anna[8497]: DEBUG: retrieving partman-xfs 53 Jan 17 16:49:28 debconf: -- SUBST anna/progress_step_retr PACKAGE partman-xfs Jan 17 16:49:28 debconf: Adding [PACKAGE] - [partman-xfs] Jan 17 16:49:28 debconf: -- 0 Jan 17 16:49:28 debconf: -- PROGRESS INFO anna/progress_step_retr Jan 17 16:49:28 debconf: -- 0 OK Jan 17 16:49:28 debconf: -- PROGRESS STOP Jan 17 16:49:28 debconf: -- 0 OK Jan 17 16:49:28 debconf: -- SUBST anna/install_failed PACKAGE partman-xfs Jan 17 16:49:28 debconf: Adding [PACKAGE] - [partman-xfs] Jan 17 16:49:28 debconf: -- 0 Jan 17 16:49:28 debconf: -- INPUT critical anna/install_failed Jan 17 16:49:28 debconf: -- 0 question will be asked Jan 17 16:49:28 debconf: -- GO Jan 17 16:56:07 debconf: -- 0 ok Jan 17 16:56:07 main-menu[2943]: WARNING **: Configuring 'load-cdrom' failed with error code 8 Jan 17 16:56:07 debconf: -- GET debconf/priority Jan 17 16:56:07 debconf: -- 0 critical Jan 17 16:56:07 main-menu[2943]: WARNING **: Menu item 'load-cdrom' failed. Jan 17 16:56:07 debconf: -- SETTITLE debian-installer/load-cdrom/title Jan 17 16:56:07 debconf: -- 0 OK Jan 17 16:56:07 debconf: -- CAPB Jan 17 16:56:07 debconf: -- 0 multiselect backup progresscancel align escape plugin-terminal plugin-detect-keyboard Jan 17 16:56:07 debconf: -- METAGET debian-installer/load-cdrom/title Description Jan 17 16:56:07 debconf: -- 0 Load installer components from CD Jan 17 16:56:07 debconf: -- SUBST debian-installer/main-menu/item-failure ITEM Load installer components from CD Jan 17 16:56:07 debconf: Adding [ITEM] - [Load installer components from CD] Jan 17 16:56:07 debconf: -- 0 Jan 17 16:56:07 debconf: -- INPUT critical debian-installer/main-menu/item-failure Jan 17 16:56:07 debconf: -- 0 question will be asked = The steps to reproduce: Install ubuntu server from the the ISO image of 20140117 Impacted jobs are: http://ci.ubuntu.com/smokeng/trusty/server/i386/20140117/6131/default/ and http://ci.ubuntu.com/smokeng/trusty/server/amd64/20140117/6130/default/ The installer syslog is attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270228/+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 1270228] Re: Loading partman-xfs failed for unknown reasons. Aborting error in trusty server installations
There is one commit that is not yet in 3.13.0-4 but has a very suspicious comment in the commit: commit d1969a84dd6a44d375aa82bba7d6c38713a429c3 Author: Hugh Dickins hu...@google.com Date: Thu Jan 16 15:26:48 2014 -0800 percpu_counter: unbreak __percpu_counter_add() Commit 74e72f894d56 (lib/percpu_counter.c: fix __percpu_counter_add()) looked very plausible, but its arithmetic was badly wrong: obvious once you see the fix, but maddening to get there from the weird tmpfs ENOSPCs That would explain why there is ENOSPC reported without du agreeing when counting the usage. -- 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/1270228 Title: Loading partman-xfs failed for unknown reasons. Aborting error in trusty server installations Status in “linux” package in Ubuntu: Confirmed Bug description: With 20140117 (containing kernel 3.13.0-4-generic) trusty server images the above error message dialog appears during the installation and the following could be seen in the install syslog: Jan 17 16:49:28 anna[8497]: DEBUG: retrieving partman-target 83ubuntu1 Jan 17 16:49:28 debconf: -- SUBST anna/progress_step_retr PACKAGE partman-target Jan 17 16:49:28 debconf: Adding [PACKAGE] - [partman-target] Jan 17 16:49:28 debconf: -- 0 Jan 17 16:49:28 debconf: -- PROGRESS INFO anna/progress_step_retr Jan 17 16:49:28 debconf: -- 0 OK Jan 17 16:49:28 anna[8497]: corrupted status flag!!: 0 Jan 17 16:49:28 anna[8497]: (process:10536): tar: write error: No space left on device Jan 17 16:49:28 anna[8497]: (process:10536): tar: write error: No space left on device Jan 17 16:49:28 debconf: -- PROGRESS STEP 1 Jan 17 16:49:28 debconf: -- 0 OK Jan 17 16:49:28 anna[8497]: DEBUG: retrieving partman-xfs 53 Jan 17 16:49:28 debconf: -- SUBST anna/progress_step_retr PACKAGE partman-xfs Jan 17 16:49:28 debconf: Adding [PACKAGE] - [partman-xfs] Jan 17 16:49:28 debconf: -- 0 Jan 17 16:49:28 debconf: -- PROGRESS INFO anna/progress_step_retr Jan 17 16:49:28 debconf: -- 0 OK Jan 17 16:49:28 debconf: -- PROGRESS STOP Jan 17 16:49:28 debconf: -- 0 OK Jan 17 16:49:28 debconf: -- SUBST anna/install_failed PACKAGE partman-xfs Jan 17 16:49:28 debconf: Adding [PACKAGE] - [partman-xfs] Jan 17 16:49:28 debconf: -- 0 Jan 17 16:49:28 debconf: -- INPUT critical anna/install_failed Jan 17 16:49:28 debconf: -- 0 question will be asked Jan 17 16:49:28 debconf: -- GO Jan 17 16:56:07 debconf: -- 0 ok Jan 17 16:56:07 main-menu[2943]: WARNING **: Configuring 'load-cdrom' failed with error code 8 Jan 17 16:56:07 debconf: -- GET debconf/priority Jan 17 16:56:07 debconf: -- 0 critical Jan 17 16:56:07 main-menu[2943]: WARNING **: Menu item 'load-cdrom' failed. Jan 17 16:56:07 debconf: -- SETTITLE debian-installer/load-cdrom/title Jan 17 16:56:07 debconf: -- 0 OK Jan 17 16:56:07 debconf: -- CAPB Jan 17 16:56:07 debconf: -- 0 multiselect backup progresscancel align escape plugin-terminal plugin-detect-keyboard Jan 17 16:56:07 debconf: -- METAGET debian-installer/load-cdrom/title Description Jan 17 16:56:07 debconf: -- 0 Load installer components from CD Jan 17 16:56:07 debconf: -- SUBST debian-installer/main-menu/item-failure ITEM Load installer components from CD Jan 17 16:56:07 debconf: Adding [ITEM] - [Load installer components from CD] Jan 17 16:56:07 debconf: -- 0 Jan 17 16:56:07 debconf: -- INPUT critical debian-installer/main-menu/item-failure Jan 17 16:56:07 debconf: -- 0 question will be asked = The steps to reproduce: Install ubuntu server from the the ISO image of 20140117 Impacted jobs are: http://ci.ubuntu.com/smokeng/trusty/server/i386/20140117/6131/default/ and http://ci.ubuntu.com/smokeng/trusty/server/amd64/20140117/6130/default/ The installer syslog is attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270228/+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 1233075] Re: resizefs failure with raring
This appears to be fixed actually (reference in other bug)
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Released = Invalid
--
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/1233075
Title:
resizefs failure with raring
Status in “linux” package in Ubuntu:
Invalid
Bug description:
Deploying a raring cloud image with a 2.7G filesystem to 2TB hard disk
crashes in resizefs
[ 143.673885] 0800 880bd4b87f60 880bca8b7d00
8125b
e47
[ 143.673945] Call Trace:
[ 143.673970] [8125be47] ext4_flex_group_add+0x1317/0x1490
[ 143.674001] [8125d00a] ext4_resize_fs+0x74a/0xdc0
[ 143.674030] [8123ae31] ext4_ioctl+0x971/0xb60
[ 143.674060] [811a4091] ? do_filp_open+0x41/0xa0
[ 143.674089] [811a61a9] do_vfs_ioctl+0x99/0x570
[ 143.674119] [8117d00f] ? kmem_cache_free+0x2f/0x130
[ 143.674148] [811a36b2] ? final_putname+0x22/0x50
[ 143.674177] [811a38b9] ? putname+0x29/0x40
[ 143.674204] [811a6711] sys_ioctl+0x91/0xb0
[ 143.674233] [816d59dd] system_call_fastpath+0x1a/0x1f
[ 143.674261] Code: 0f 85 f2 fe ff ff 31 c0 48 83 c4 28 5b 41 5c 41 5d 41 5e
41
5f 5d c3 48 83 c4 28 b8 f4 ff ff ff 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b
90
66 66 66 66 90 55 48 89 e5 48 83 ec 18 4c 89 65 f0 49
[ 143.674584] RIP [8125a5cd] set_flexbg_block_bitmap+0x17d/0x180
[ 143.674618] RSP 880bca8b7bb0
[ 143.674643] ---[ end trace 5fa931e218cd3ae5 ]---
2013-09-30 10:07:44,273 - util.py[WARNING]: Failed to resize filesystem
(cmd=('r
esize2fs', '/dev/disk/by-uuid/420927c3-abd7-4b7d-972c-a8b6969d7d53'))
2013-09-30 10:07:44,293 - util.py[WARNING]: Running resizefs (module
'cloudinit
.config.cc_resizefs' from
'/usr/lib/python2.7/dist-packages/cloudinit/config/cc_
resizefs.pyc') failed
Is all the diagnostics I have so far.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233075/+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 1233075] Re: resizefs failure with raring
Correct status is a bit hard to say as the problem was the journal which
was defined too small given the image size on creation. There may or may
not be a better way to detect this and bail early.
--
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/1233075
Title:
resizefs failure with raring
Status in “linux” package in Ubuntu:
Invalid
Bug description:
Deploying a raring cloud image with a 2.7G filesystem to 2TB hard disk
crashes in resizefs
[ 143.673885] 0800 880bd4b87f60 880bca8b7d00
8125b
e47
[ 143.673945] Call Trace:
[ 143.673970] [8125be47] ext4_flex_group_add+0x1317/0x1490
[ 143.674001] [8125d00a] ext4_resize_fs+0x74a/0xdc0
[ 143.674030] [8123ae31] ext4_ioctl+0x971/0xb60
[ 143.674060] [811a4091] ? do_filp_open+0x41/0xa0
[ 143.674089] [811a61a9] do_vfs_ioctl+0x99/0x570
[ 143.674119] [8117d00f] ? kmem_cache_free+0x2f/0x130
[ 143.674148] [811a36b2] ? final_putname+0x22/0x50
[ 143.674177] [811a38b9] ? putname+0x29/0x40
[ 143.674204] [811a6711] sys_ioctl+0x91/0xb0
[ 143.674233] [816d59dd] system_call_fastpath+0x1a/0x1f
[ 143.674261] Code: 0f 85 f2 fe ff ff 31 c0 48 83 c4 28 5b 41 5c 41 5d 41 5e
41
5f 5d c3 48 83 c4 28 b8 f4 ff ff ff 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b
90
66 66 66 66 90 55 48 89 e5 48 83 ec 18 4c 89 65 f0 49
[ 143.674584] RIP [8125a5cd] set_flexbg_block_bitmap+0x17d/0x180
[ 143.674618] RSP 880bca8b7bb0
[ 143.674643] ---[ end trace 5fa931e218cd3ae5 ]---
2013-09-30 10:07:44,273 - util.py[WARNING]: Failed to resize filesystem
(cmd=('r
esize2fs', '/dev/disk/by-uuid/420927c3-abd7-4b7d-972c-a8b6969d7d53'))
2013-09-30 10:07:44,293 - util.py[WARNING]: Running resizefs (module
'cloudinit
.config.cc_resizefs' from
'/usr/lib/python2.7/dist-packages/cloudinit/config/cc_
resizefs.pyc') failed
Is all the diagnostics I have so far.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233075/+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 1270656] Re: Ubuntu 14.04 boots to blank console
Blacklisting simple-framebuffer for the Ubuntu kernel will have no
effect because it is built-in. But I am interested in the two dmesg's
without any blacklisting to compare the output. Somehow those labelled
as own kernel seem to be from a boot with the normal Ubuntu kernel, too.
Just the wrong dmesg or where were the different kernels installed?
--
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/1270656
Title:
Ubuntu 14.04 boots to blank console
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux” package in Debian:
New
Status in “linux” package in Fedora:
New
Bug description:
Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console.
Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but ps axf shows
/sbin/getty running on tty{1..6}:
# ps axf | grep tty
880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4
885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5
890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2
891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3
893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6
4290 pts/1S+ 0:00 \_ grep --color=auto tty
1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1
Removing deprecated vga=768 from kernel commandline = doesn't boot into
800x600, keeps 640x480
Settings
GRUB_GFXMODE=800x600
GRUB_GFXPAYLOAD=800x600
are ignored.
Grub boots up with 800x600, switches back to 640x480 (setting
GRUB_GFXPAYLOAD to keep it is the same) kernel doesn't switch back
to 800x600.
Adding deprecated vga=768 back in:
Grub boots up with 800x600, switches back to 640x480, kernel switches back to
800x600, but doesn't use this console. No output at all. Keys are accepted (you
can login, but you'll have to guess what is going on on the screen).
Exactly the same error is found with debian. Switching to a self
compiled kernel solves this error. Looks a lot like some necessary
stuff for console resolution switching is missing in the debian
-/ubuntu-kernels.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: util-linux 2.20.1-5.1ubuntu13
ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
Uname: Linux 3.13.0-4-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
Date: Mon Jan 20 00:20:36 2014
InstallationDate: Installed on 2012-12-12 (403 days ago)
InstallationMedia: Ubuntu-Server 12.04.1 LTS Precise Pangolin - Release
amd64 (20120817.3)
ProcEnviron:
TERM=screen-bce
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1271669] Re: move drivers/misc/vmw_vmci/vmw_vmci.ko from linux-image-extra to linux-image-virtual
** Changed in: linux (Ubuntu) Status: Confirmed = In Progress -- 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/1271669 Title: move drivers/misc/vmw_vmci/vmw_vmci.ko from linux-image-extra to linux-image-virtual Status in “linux” package in Ubuntu: In Progress Bug description: drivers/misc/vmw_vmci/vmw_vmci.ko is currently in linux-image-extra. Due to a sync of open-vm-tools and an open MIR on open-vm-tools, this module is needed in the regular kernel Bug #1220950 open-vm-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1271669/+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 1271669] Re: move drivers/misc/vmw_vmci/vmw_vmci.ko from linux-image-extra to linux-image-virtual
** Package changed: ubuntu = linux (Ubuntu) -- 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/1271669 Title: move drivers/misc/vmw_vmci/vmw_vmci.ko from linux-image-extra to linux-image-virtual Status in “linux” package in Ubuntu: In Progress Bug description: drivers/misc/vmw_vmci/vmw_vmci.ko is currently in linux-image-extra. Due to a sync of open-vm-tools and an open MIR on open-vm-tools, this module is needed in the regular kernel Bug #1220950 open-vm-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1271669/+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 1271669] Re: Move vmware related modules from extras into main kernel package
Modified the title so this could include multiple modules. vmxnet3 is already in the main package, but vsock.ko and vmw_vsock_vmci_transport.ko are not but likely should. There is a vmwgfx driver, too but the target is probably more server type which does not need accelerated gfx. Also right now there is no other drm driver in the main package. ** Summary changed: - move vmware modules (vmci, vsock, vxnet3) from linux-image-extra to linux-image-virtual + Move vmware related modules from extras into main kernel package -- 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/1271669 Title: Move vmware related modules from extras into main kernel package Status in “linux” package in Ubuntu: In Progress Bug description: drivers/misc/vmw_vmci/vmw_vmci.ko, net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko are currently in linux-image-extra. Due to a sync of open-vm-tools and an open MIR on open-vm-tools, these modules are needed in the regular kernel. Bug #1220950 open-vm-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1271669/+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 1271669] Re: Move vmware related modules from extras into main kernel package
Came up with the same change mostly. just generically including everything in net/vmw_vsock/*. -- 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/1271669 Title: Move vmware related modules from extras into main kernel package Status in “linux” package in Ubuntu: In Progress Bug description: drivers/misc/vmw_vmci/vmw_vmci.ko, net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko are currently in linux-image-extra. Due to a sync of open-vm-tools and an open MIR on open-vm-tools, these modules are needed in the regular kernel. Bug #1220950 open-vm-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1271669/+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 1271669] Re: Move vmware related modules from extras into main kernel package
Test packages in people.cc/~smb/vmcitest. -- 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/1271669 Title: Move vmware related modules from extras into main kernel package Status in “linux” package in Ubuntu: In Progress Status in “open-vm-tools” package in Ubuntu: In Progress Bug description: drivers/misc/vmw_vmci/vmw_vmci.ko, net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko are currently in linux-image-extra. Due to a sync of open-vm-tools and an open MIR on open-vm-tools, these modules are needed in the regular kernel. Bug #1220950 open-vm-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1271669/+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 1270656] Re: Ubuntu 14.04 boots to blank console
Ok so with those there seems to be some resolution lines which get
repeated three times with the Ubuntu kernel (which is odd) and compared
to the self-compiled kernel there seems to be no action to replace the
framebuffer.
Could you try to boot the Ubuntu kernel with vmwgfx.enable_fbdev=1
added to the kernel command-line in grub and report back whether that
changes behaviour (also adding the dmesg from that run)?
--
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/1270656
Title:
Ubuntu 14.04 boots to blank console
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux” package in Debian:
New
Status in “linux” package in Fedora:
New
Bug description:
Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console.
Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but ps axf shows
/sbin/getty running on tty{1..6}:
# ps axf | grep tty
880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4
885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5
890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2
891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3
893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6
4290 pts/1S+ 0:00 \_ grep --color=auto tty
1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1
Removing deprecated vga=768 from kernel commandline = doesn't boot into
800x600, keeps 640x480
Settings
GRUB_GFXMODE=800x600
GRUB_GFXPAYLOAD=800x600
are ignored.
Grub boots up with 800x600, switches back to 640x480 (setting
GRUB_GFXPAYLOAD to keep it is the same) kernel doesn't switch back
to 800x600.
Adding deprecated vga=768 back in:
Grub boots up with 800x600, switches back to 640x480, kernel switches back to
800x600, but doesn't use this console. No output at all. Keys are accepted (you
can login, but you'll have to guess what is going on on the screen).
Exactly the same error is found with debian. Switching to a self
compiled kernel solves this error. Looks a lot like some necessary
stuff for console resolution switching is missing in the debian
-/ubuntu-kernels.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: util-linux 2.20.1-5.1ubuntu13
ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
Uname: Linux 3.13.0-4-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
Date: Mon Jan 20 00:20:36 2014
InstallationDate: Installed on 2012-12-12 (403 days ago)
InstallationMedia: Ubuntu-Server 12.04.1 LTS Precise Pangolin - Release
amd64 (20120817.3)
ProcEnviron:
TERM=screen-bce
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1270656] Re: Ubuntu 14.04 boots to blank console
Not sure which errors are gone now. The line related to drm and vmwgfx are like
the previous no blacklisting and no setting fbdev dmesg to me. Again repeating
the resolution and FIFO line and not replacing the framebuffer.
How the user-space tools would influence the kernel boot I cannot explain. The
dkms package that goes with it does not seem to replace anything gfx related.
So loosing a few lines while switching framebuffers is something I would not
worry too much about. Though that should be the same with the Ubuntu and your
own kernel... We probably should make the default enabled here.
Aside that, something else to try: most newer framebuffer drivers (especially
those related to drm drivers) will understand something like video=800x600
instead of vga=789 (maybe video=simplefb:800x600 but according to dmesg it is
already using that resolution). The resolution would be set by GRUB_GFXMODE,
GRUB_GFXPAYLOAD is not used when generating the real grub config file.
--
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/1270656
Title:
Ubuntu 14.04 boots to blank console
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux” package in Debian:
New
Status in “linux” package in Fedora:
New
Bug description:
Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console.
Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but ps axf shows
/sbin/getty running on tty{1..6}:
# ps axf | grep tty
880 tty4 Ss+0:00 /sbin/getty -8 38400 tty4
885 tty5 Ss+0:00 /sbin/getty -8 38400 tty5
890 tty2 Ss+0:00 /sbin/getty -8 38400 tty2
891 tty3 Ss+0:00 /sbin/getty -8 38400 tty3
893 tty6 Ss+0:00 /sbin/getty -8 38400 tty6
4290 pts/1S+ 0:00 \_ grep --color=auto tty
1093 tty1 Ss+0:00 /sbin/getty -8 38400 tty1
Removing deprecated vga=768 from kernel commandline = doesn't boot into
800x600, keeps 640x480
Settings
GRUB_GFXMODE=800x600
GRUB_GFXPAYLOAD=800x600
are ignored.
Grub boots up with 800x600, switches back to 640x480 (setting
GRUB_GFXPAYLOAD to keep it is the same) kernel doesn't switch back
to 800x600.
Adding deprecated vga=768 back in:
Grub boots up with 800x600, switches back to 640x480, kernel switches back to
800x600, but doesn't use this console. No output at all. Keys are accepted (you
can login, but you'll have to guess what is going on on the screen).
Exactly the same error is found with debian. Switching to a self
compiled kernel solves this error. Looks a lot like some necessary
stuff for console resolution switching is missing in the debian
-/ubuntu-kernels.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: util-linux 2.20.1-5.1ubuntu13
ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
Uname: Linux 3.13.0-4-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
Date: Mon Jan 20 00:20:36 2014
InstallationDate: Installed on 2012-12-12 (403 days ago)
InstallationMedia: Ubuntu-Server 12.04.1 LTS Precise Pangolin - Release
amd64 (20120817.3)
ProcEnviron:
TERM=screen-bce
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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 1273386] Re: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel
Did you find out whether this actually was a regression compared to the previous kernel? Also, since the problem seems to be something submitting a bufferhead that is not mapped (anymore?) on releasing the mount namespace, maybe the content of /proc/pid/mount* of the process about to be killed. -- 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/1273386 Title: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): New Status in “linux” package in Ubuntu: Incomplete Bug description: In the past 9 days we have been seeing very frequent occurences of this kernel crash: http://paste.openstack.org/show/61869/ Even if the particular crash pasted here is triggered by dnsmasq, in almost all cases the crash is actually triggered by the neutron metada proxy. This also affects nova badly since this issue, which appears namespace related, results in a hang while mounting the ndb device for key injection. logstash query: http://logstash.openstack.org/#eyJzZWFyY2giOiJcImtlcm5lbCBCVUcgYXQgL2J1aWxkL2J1aWxkZC9saW51eC0zLjIuMC9mcy9idWZmZXIuYzoyOTE3XCIgYW5kIGZpbGVuYW1lOnN5c2xvZy50eHQiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImN1c3RvbSIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJmcm9tIjoiMjAxNC0wMS0xNlQxODo1MDo0OCswMDowMCIsInRvIjoiMjAxNC0wMS0yN1QxOToxNjoxMSswMDowMCIsInVzZXJfaW50ZXJ2YWwiOiIwIn0sInN0YW1wIjoxMzkwODUwMzI2ODY0fQ== We have seen about 398 hits since the bug started to manifest. Decreased hit rate in the past few days is due to less neutron patches being pushed. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1273386/+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 1273386] Re: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel
Hi Salvatore, so that old crash really looks quite similar. One interesting difference is that this process did simply exit and was not killed. Which sounds, like you did suspect as well, that this is not a regression in a recent kernel but something in the way things are executed changed and makes it just happen more often now. I hear from James Page that right now some changes in OpenStack will cause more things happen in parallel. That maybe causes some races to get triggered which haven't been observed (that often) before. To get a better understanding what the exact state of things is when this happens, would it be possible to enable crashdump on one of the development machines experiencing the issue and set it to panic on the oops? A description how to set up crashdump you would find at https://wiki.ubuntu.com/Kernel/CrashdumpRecipe. To cause the oops to become a panic you would have to echo 1 into /proc/sys/kernel/panic_on_oops after boot. -- 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/1273386 Title: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): New Status in “linux” package in Ubuntu: Incomplete Bug description: In the past 9 days we have been seeing very frequent occurences of this kernel crash: http://paste.openstack.org/show/61869/ Even if the particular crash pasted here is triggered by dnsmasq, in almost all cases the crash is actually triggered by the neutron metada proxy. This also affects nova badly since this issue, which appears namespace related, results in a hang while mounting the ndb device for key injection. logstash query: http://logstash.openstack.org/#eyJzZWFyY2giOiJcImtlcm5lbCBCVUcgYXQgL2J1aWxkL2J1aWxkZC9saW51eC0zLjIuMC9mcy9idWZmZXIuYzoyOTE3XCIgYW5kIGZpbGVuYW1lOnN5c2xvZy50eHQiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImN1c3RvbSIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJmcm9tIjoiMjAxNC0wMS0xNlQxODo1MDo0OCswMDowMCIsInRvIjoiMjAxNC0wMS0yN1QxOToxNjoxMSswMDowMCIsInVzZXJfaW50ZXJ2YWwiOiIwIn0sInN0YW1wIjoxMzkwODUwMzI2ODY0fQ== We have seen about 398 hits since the bug started to manifest. Decreased hit rate in the past few days is due to less neutron patches being pushed. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1273386/+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
