[Kernel-packages] [Bug 1542957] Re: SCSI failed | boot failed | APCI complained
I refuse to use Apport until it offers an option for fully anonymized reporting. That means full anonymization of all filenames, including directories, usernames, strings from filesystem content, addresses, device names and whatever else. I'm boycotting Apport. -- 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/1542957 Title: SCSI failed | boot failed | APCI complained Status in linux package in Ubuntu: Incomplete Bug description: SCSI stopped working. Machine locks on boot. It was fine before. What should happen: machine boosts, scsi interface enabled What does happen: machine fails to boot, acpi reports problems Boot messages [edited]: ACPI PCC Probe Failed Starting Version 219 Worker[139] /devices/pci000:00 ... etc SCSI timing out command, waited 82s ... devices/pci timeout kill it ... seq 987 /devices/pci killed ... INFO: task systemd-udevd:139 blocked for more than 120 seconds module len 27812 truncated INFO: task sh blocked for more than 120 seconds INFO: task alsactl:468 blocked for more than 120 seconds INFO: task apparmor: 474 blocked for more than 120 seconds and so on. Here's what looks like a relevant section from kern.log: Feb 7 22:08:58 zammo kernel: [ 10.846041] scsi host4: Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 Feb 7 22:08:58 zammo kernel: [ 10.846041] Feb 7 22:08:58 zammo kernel: [ 10.846041] aic7850: Single Channel A, SCSI Id=7, 3/253 SCBs Feb 7 22:08:58 zammo kernel: [ 10.846041] Feb 7 22:08:58 zammo kernel: [ 60.535354] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) Feb 7 22:08:58 zammo kernel: [ 64.555112] lp: driver loaded but no devices found Feb 7 22:08:58 zammo kernel: [ 64.638863] ppdev: user-space parallel port driver Feb 7 22:08:58 zammo kernel: [ 64.724900] parport_pc 00:03: reported by Plug and Play ACPI Feb 7 22:08:58 zammo kernel: [ 64.724948] parport0: PC-style at 0x378 (0x778), irq 7, using FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP] Feb 7 22:08:58 zammo kernel: [ 64.807286] lp0: using parport0 (interrupt-driven). Feb 7 22:08:58 zammo kernel: [ 70.374056] intel_rng: Firmware space is locked read-only. If you can't or Feb 7 22:08:58 zammo kernel: [ 70.374056] intel_rng: don't want to disable this in firmware setup, and if Feb 7 22:08:58 zammo kernel: [ 70.374056] intel_rng: you are certain that your system has a functional Feb 7 22:08:58 zammo kernel: [ 70.374056] intel_rng: RNG, try using the 'no_fwh_detect' option. Feb 7 22:08:58 zammo kernel: [ 70.387710] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Feb 7 22:08:58 zammo kernel: [ 70.505366] ACPI Warning: SystemIO range 0x0828-0x082f conflicts with OpRegion 0x082a-0x082a (\GIC3) (20141107/utaddress-258) Feb 7 22:08:58 zammo kernel: [ 70.505380] ACPI Warning: SystemIO range 0x0828-0x082f conflicts with OpRegion 0x082b-0x082b (\GIC2) (20141107/utaddress-258) Feb 7 22:08:58 zammo kernel: [ 70.505389] ACPI Warning: SystemIO range 0x0828-0x082f conflicts with OpRegion 0x0828-0x082d (\GLBC) (20141107/utaddress-258) Feb 7 22:08:58 zammo kernel: [ 70.505398] ACPI Warning: SystemIO range 0x0828-0x082f conflicts with OpRegion 0x082a-0x082a (\SACT) (20141107/utaddress-258) Feb 7 22:08:58 zammo kernel: [ 70.505405] ACPI Warning: SystemIO range 0x0828-0x082f conflicts with OpRegion 0x0828-0x0828 (\SSTS) (20141107/utaddress-258) Feb 7 22:08:58 zammo kernel: [ 70.505413] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Feb 7 22:08:58 zammo kernel: [ 70.505419] ACPI Warning: SystemIO range 0x08b0-0x08bf conflicts with OpRegion 0x08b8-0x08b8 (\GHI0) (20141107/utaddress-258) Feb 7 22:08:58 zammo kernel: [ 70.505427] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Feb 7 22:08:58 zammo kernel: [ 70.505432] ACPI Warning: SystemIO range 0x0880-0x08af conflicts with OpRegion 0x088e-0x088e (\GIC1) (20141107/utaddress-258) Feb 7 22:08:58 zammo kernel: [ 70.505441] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Feb 7 22:08:58 zammo kernel: [ 70.505445] lpc_ich: Resource conflict(s) found affecting gpio_ich -- Description: Ubuntu 15.04 Release: 15.04 -- To manage notifications about this bug
[Kernel-packages] [Bug 1542957] [NEW] SCSI failed | boot failed | APCI complained
Public bug reported: SCSI stopped working. Machine locks on boot. It was fine before. What should happen: machine boosts, scsi interface enabled What does happen: machine fails to boot, acpi reports problems Boot messages [edited]: ACPI PCC Probe Failed Starting Version 219 Worker[139] /devices/pci000:00 ... etc SCSI timing out command, waited 82s ... devices/pci timeout kill it ... seq 987 /devices/pci killed ... INFO: task systemd-udevd:139 blocked for more than 120 seconds module len 27812 truncated INFO: task sh blocked for more than 120 seconds INFO: task alsactl:468 blocked for more than 120 seconds INFO: task apparmor: 474 blocked for more than 120 seconds and so on. Here's what looks like a relevant section from kern.log: Feb 7 22:08:58 zammo kernel: [ 10.846041] scsi host4: Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 Feb 7 22:08:58 zammo kernel: [ 10.846041] Feb 7 22:08:58 zammo kernel: [ 10.846041] aic7850: Single Channel A, SCSI Id=7, 3/253 SCBs Feb 7 22:08:58 zammo kernel: [ 10.846041] Feb 7 22:08:58 zammo kernel: [ 60.535354] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) Feb 7 22:08:58 zammo kernel: [ 64.555112] lp: driver loaded but no devices found Feb 7 22:08:58 zammo kernel: [ 64.638863] ppdev: user-space parallel port driver Feb 7 22:08:58 zammo kernel: [ 64.724900] parport_pc 00:03: reported by Plug and Play ACPI Feb 7 22:08:58 zammo kernel: [ 64.724948] parport0: PC-style at 0x378 (0x778), irq 7, using FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP] Feb 7 22:08:58 zammo kernel: [ 64.807286] lp0: using parport0 (interrupt-driven). Feb 7 22:08:58 zammo kernel: [ 70.374056] intel_rng: Firmware space is locked read-only. If you can't or Feb 7 22:08:58 zammo kernel: [ 70.374056] intel_rng: don't want to disable this in firmware setup, and if Feb 7 22:08:58 zammo kernel: [ 70.374056] intel_rng: you are certain that your system has a functional Feb 7 22:08:58 zammo kernel: [ 70.374056] intel_rng: RNG, try using the 'no_fwh_detect' option. Feb 7 22:08:58 zammo kernel: [ 70.387710] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Feb 7 22:08:58 zammo kernel: [ 70.505366] ACPI Warning: SystemIO range 0x0828-0x082f conflicts with OpRegion 0x082a-0x082a (\GIC3) (20141107/utaddress-258) Feb 7 22:08:58 zammo kernel: [ 70.505380] ACPI Warning: SystemIO range 0x0828-0x082f conflicts with OpRegion 0x082b-0x082b (\GIC2) (20141107/utaddress-258) Feb 7 22:08:58 zammo kernel: [ 70.505389] ACPI Warning: SystemIO range 0x0828-0x082f conflicts with OpRegion 0x0828-0x082d (\GLBC) (20141107/utaddress-258) Feb 7 22:08:58 zammo kernel: [ 70.505398] ACPI Warning: SystemIO range 0x0828-0x082f conflicts with OpRegion 0x082a-0x082a (\SACT) (20141107/utaddress-258) Feb 7 22:08:58 zammo kernel: [ 70.505405] ACPI Warning: SystemIO range 0x0828-0x082f conflicts with OpRegion 0x0828-0x0828 (\SSTS) (20141107/utaddress-258) Feb 7 22:08:58 zammo kernel: [ 70.505413] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Feb 7 22:08:58 zammo kernel: [ 70.505419] ACPI Warning: SystemIO range 0x08b0-0x08bf conflicts with OpRegion 0x08b8-0x08b8 (\GHI0) (20141107/utaddress-258) Feb 7 22:08:58 zammo kernel: [ 70.505427] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Feb 7 22:08:58 zammo kernel: [ 70.505432] ACPI Warning: SystemIO range 0x0880-0x08af conflicts with OpRegion 0x088e-0x088e (\GIC1) (20141107/utaddress-258) Feb 7 22:08:58 zammo kernel: [ 70.505441] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Feb 7 22:08:58 zammo kernel: [ 70.505445] lpc_ich: Resource conflict(s) found affecting gpio_ich -- Description:Ubuntu 15.04 Release:15.04 -- ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: acpi boot pci scsi systemio -- 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/1542957 Title: SCSI failed | boot failed | APCI complained Status in linux package in Ubuntu: New Bug description: SCSI stopped working. Machine locks on boot. It was fine before. What should happen: machine boosts, scsi interface enabled What does happen: machine fails to boot, acpi reports problems Boot messages [edited]: ACPI PCC Probe Failed Starting
[Kernel-packages] [Bug 1276739] Re: partman-crypto uses xts by default, yet xts.ko kernel module is not present in 3.2 (original-point-zero stack) crypto-modules-udeb
This bug appears to be a problem with Xubuntu AMD64 12.04.4 Alternate. I have been prevented using this disk to rescue an encrypted LVM system because, it says, reload ioctl failed...failed to setup dm-crypt key mapping for device... check that kernel supports aes-xts-plain64 cipher. The system was setup using default Xubuntu installer options for encrypted LVM (can't remember which version but it was recent and it worked). The rescue has become necessary because kernel -29 update failed due to /root partition becoming full. Kernel update failure consisted of a disk full error before the kernel extras image could be installed. USB Keyboard therefore fails when system asks for encryption password. The problem would be resolved for common users if the system detected its problem and provided a 'Dummy's' option to resize the partition, with an intelligent guess proffered as the new size. Rescue of this situation is like venturing into a foggy swamp. Before you even get to attempt the resize operation, the Xubuntu rescue disk is not loaded with the same cipher that it had originally used to setup the encrypted volume. The DebianLive AMD64 7.5.0 Rescue CD failed as well. It seems to be incapable of recognizing a non-US keyboard, which makes entering an encryption password setup on an English keyboard quite unlikely (unless its a Mickey Mouse password that uses only standard numbers and letters). It is very unlikely a common user will detect this fact from using the live CD. The experience of attempting this operation will therefore be deeply frustrating and ultimately unsuccessful. The solution now appears to be to keep downloading rescue disks until one works. -- 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/1276739 Title: partman-crypto uses xts by default, yet xts.ko kernel module is not present in 3.2 (original-point-zero stack) crypto-modules-udeb Status in “debian-installer” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Invalid Status in “partman-crypto” package in Ubuntu: Invalid Status in “debian-installer” source package in Precise: Fix Released Status in “linux” source package in Precise: Fix Released Status in “partman-crypto” source package in Precise: Invalid Bug description: [Impact] * Performing automatic encrypted LVM installation using Kubuntu and Xubuntu 12.04.4 alternate installer images results in a failure to configure encrypted volumes. Please either use manual partitioning to create encrypted volumes with any non-default IV algorithm setting or use 12.04.3 media to complete the installation. [Error Message] Configuration of encrypted volumes failed. An error occurred while configuring encrypted volumes. The configuration has been aborted. [Cause of the bug] * xts.ko kernel module is missing from 3.2 crypto-modules-udeb [Working (older) media] * Kubuntu http://cdimages.ubuntu.com/kubuntu/releases/12.04.3/release/ * Xubuntu http://cdimages.ubuntu.com/xubuntu/releases/12.04.3/release/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1276739/+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 1276739] Re: partman-crypto uses xts by default, yet xts.ko kernel module is not present in 3.2 (original-point-zero stack) crypto-modules-udeb
GParted Live CD doesn't appear to be able to help either - no facility to work on encrypted partitions: http://gparted.org/features.php -- 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/1276739 Title: partman-crypto uses xts by default, yet xts.ko kernel module is not present in 3.2 (original-point-zero stack) crypto-modules-udeb Status in “debian-installer” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Invalid Status in “partman-crypto” package in Ubuntu: Invalid Status in “debian-installer” source package in Precise: Fix Released Status in “linux” source package in Precise: Fix Released Status in “partman-crypto” source package in Precise: Invalid Bug description: [Impact] * Performing automatic encrypted LVM installation using Kubuntu and Xubuntu 12.04.4 alternate installer images results in a failure to configure encrypted volumes. Please either use manual partitioning to create encrypted volumes with any non-default IV algorithm setting or use 12.04.3 media to complete the installation. [Error Message] Configuration of encrypted volumes failed. An error occurred while configuring encrypted volumes. The configuration has been aborted. [Cause of the bug] * xts.ko kernel module is missing from 3.2 crypto-modules-udeb [Working (older) media] * Kubuntu http://cdimages.ubuntu.com/kubuntu/releases/12.04.3/release/ * Xubuntu http://cdimages.ubuntu.com/xubuntu/releases/12.04.3/release/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1276739/+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
