[Kernel-packages] [Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
** Changed in: linux-raspi2 (Ubuntu) Assignee: Ryan Finnie (fo0bar) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: This issue was reported in this mailing list thread first https://lists.ubuntu.com/archives/snapcraft/2016-December/002138.html Hardware: RPi3 Image: http://www.finnie.org/software/raspberrypi/ubuntu-rpi3/ubuntu-16.04-preinstalled-server-armhf+raspi3.img.xz [Steps to Reproduce] 1. Install the image in an SD card. Use it to boot into the system. 2. Issue the command "sudo apt-get update; sudo apt-get install linux-image-4.4.0-1038-raspi2 linux-headers-4.4.0-1038-raspi2 linux-raspi2-headers-4.4.0-1038 -y" 3. Reboot [Expected Result] Boot into the system with kernel 4.4.0-1038-raspi2 [Actual Result] The system stop at the booting session with the message 'Starting kernel...' and never goes to the login session. [Additional Info] 4.4.0-1029-raspi2 and 4.4.0-1034-raspi2 were used as the forementioned apt installation steps. They work well. They could go to the login session and ready for use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
With the regression fix tested, I've gone ahead and fixed the core
problem on my system, switching the backing device to 4k. Documented
below and worked for me, but PLEASE don't take it at face value, since
part of it is literally destroying the bcache header area of the backing
disk.
# WARNING! Loss of data, life, liberty, etc. Do not blindly copy/paste!
# You need to unmount and make sure the bcache device is not being used,
# and specifically wait for the cache state to go from dirty to clean
# if using writeback.
DEV_BACKING=/dev/sdx1 # /dev/md0 for me
DEV_CACHE=/dev/sdy1 # /dev/sdb1 for me
DEV_BCACHE=bcache0
OFFSET="$(bcache-super-show ${DEV_BACKING?} | awk '$1=="dev.data.first_sector"
{print $2}')"
CSET_UUID="$(bcache-super-show ${DEV_CACHE?} | awk '$1=="cset.uuid" {print
$2}')"
file -s ${DEV_CACHE?}
file -s ${DEV_BACKING?}
dd if=${DEV_BACKING?} bs=512 skip=${OFFSET?} count=8 | file -
# Remove and wipe cache device
echo ${CSET_UUID?} >/sys/block/${DEV_BCACHE?}/bcache/detach
cat /sys/block/${DEV_BCACHE?}/bcache/state
echo 1 >/sys/fs/bcache/${CSET_UUID?}/stop
while [ -e /sys/fs/bcache/${CSET_UUID?}/stop ]; do sleep 1; done
wipefs -a ${DEV_CACHE?}
# Stop bcache0, wipe and recreate bcache portion of backing device
echo 1 >/sys/block/${DEV_BCACHE?}/bcache/stop
while [ -e /sys/block/${DEV_BCACHE?}/bcache/stop ]; do sleep 1; done
# Removes bcache magic bytes from beginning and (hopefully) leaves all data from
# ${OFFSET?} onward (the actual data). But don't trust me here.
wipefs -a ${DEV_BACKING?}
dd if=/dev/zero of=${DEV_BACKING?} bs=512 count=${OFFSET?}
make-bcache --block 4k --bucket 2M --data-offset ${OFFSET?} -B ${DEV_BACKING?}
while [ ! -e /sys/block/${DEV_BCACHE?}/bcache/attach ]; do sleep 1; done
file -s /dev/${DEV_BCACHE?}
# Safe to remount and use bcache device now
# Recreate and attach cache
make-bcache --block 4k --bucket 2M -C ${DEV_CACHE?}
CSET_UUID="$(bcache-super-show ${DEV_CACHE?} | awk '$1=="cset.uuid" {print
$2}')"
echo ${CSET_UUID?} >/sys/block/${DEV_BCACHE?}/bcache/attach
echo writeback >/sys/block/${DEV_BCACHE?}/bcache/cache_mode
cat /sys/block/${DEV_BCACHE?}/bcache/state
--
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/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Eoan:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Users of bcache who manually specified a block size
greater than the page size when creating the device
with 'make-bcache' started to hit a kernel BUG/oops
after kernel upgrades. (This is not widely used.)
* The issue has been exposed with commit ad6bf88a6c19
("block: fix an integer overflow in logical block size")
because it increased the range of values accepted as
logical block size, which used to overflow to zero,
and thus receive a default of 512 via block layer.
* The issue existed previously, but with fewer values
exposed (e.g. 8k, 16k, 32k); the regression reports
happened with larger values (512k) for RAID stripes.
[Fix]
* The upstream commit dcacbc1242c7 ("bcache: check and
adjust logical block size for backing devices") checks
the block size and adjusts it if needed, to the value
of the underlying device's logical block size.
* It is merged as of v5.8-rcN, and sent to v5.7 stable.
[Test Case]
* Run make-bcache with block size greater than page size.
$ sudo make-bcache --bdev $DEV --block 8k
* Expected results: bcache device registered; no BUG/oops.
* Details steps on comment #43.
[Regression Potential]
* Restricted to users who specify a bcache block size
greater than page size.
* Regressions could theoretically manifest on bcache
device probe/register, if the underlying device's
logical block size for whatever triggers issues not
seen previously with the overflow/default 512 bytes.
[Other Info]
* Unstable has the patch on both master/master-5.7.
* Groovy should get it on rebase.
[Original Bug Description]
After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does
not boot any longer. It always crashes during boot with a kernel panic.
I suspect that this crash might be related to Bcache because this is
the only one of our systems where we use Bcache and the kernel panic
appears right after Bcache initialization.
I already checked that this bug still exists in the 4.15.0-92.93
kernel from proposed.
Unfortunately, I cannot do a bisect because this is a critical
production system and we do not have any
[Kernel-packages] [Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Works on focal, thank you
--
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/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Eoan:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Users of bcache who manually specified a block size
greater than the page size when creating the device
with 'make-bcache' started to hit a kernel BUG/oops
after kernel upgrades. (This is not widely used.)
* The issue has been exposed with commit ad6bf88a6c19
("block: fix an integer overflow in logical block size")
because it increased the range of values accepted as
logical block size, which used to overflow to zero,
and thus receive a default of 512 via block layer.
* The issue existed previously, but with fewer values
exposed (e.g. 8k, 16k, 32k); the regression reports
happened with larger values (512k) for RAID stripes.
[Fix]
* The upstream commit dcacbc1242c7 ("bcache: check and
adjust logical block size for backing devices") checks
the block size and adjusts it if needed, to the value
of the underlying device's logical block size.
* It is merged as of v5.8-rcN, and sent to v5.7 stable.
[Test Case]
* Run make-bcache with block size greater than page size.
$ sudo make-bcache --bdev $DEV --block 8k
* Expected results: bcache device registered; no BUG/oops.
* Details steps on comment #43.
[Regression Potential]
* Restricted to users who specify a bcache block size
greater than page size.
* Regressions could theoretically manifest on bcache
device probe/register, if the underlying device's
logical block size for whatever triggers issues not
seen previously with the overflow/default 512 bytes.
[Other Info]
* Unstable has the patch on both master/master-5.7.
* Groovy should get it on rebase.
[Original Bug Description]
After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does
not boot any longer. It always crashes during boot with a kernel panic.
I suspect that this crash might be related to Bcache because this is
the only one of our systems where we use Bcache and the kernel panic
appears right after Bcache initialization.
I already checked that this bug still exists in the 4.15.0-92.93
kernel from proposed.
Unfortunately, I cannot do a bisect because this is a critical
production system and we do not have any other system with a similar
configuration.
I attached a screenshot with the trace of the kernel panic.
The last message that appears before the kernel panic (or rather the
last one that I can see - there is a rather long pause between that
message and the panic and I cannot scroll up far enough to ensure that
there are no other messages in between) is:
bcache: register_bcache() error /dev/dm-0: device already registered
When booting with kernel 4.15.0-88 that does not have this problem,
the next message is
bcache: register_bcache() error /dev/dm-12: device already registered
(emitting change event)
After that the next message is:
Begin: Loading essential drivers ... done
This message also appears after the kernel panic, but the boot process
stalls and the system can only be recovered by doing a hardware reset.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-88-generic 4.15.0-88.88
ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
Uname: Linux 4.15.0-88-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Mar 17 21:08 seq
crw-rw 1 root audio 116, 33 Mar 17 21:08 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Mar 18 12:55:18 2020
HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a
InstallationDate: Installed on 2013-07-02 (2450 days ago)
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release
amd64 (20130214)
MachineType: HP ProLiant DL160 G6
PciMultimedia:
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic
root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw
RelatedPackageVersions:
Re: [Kernel-packages] [Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
On 6/2/20 10:19 AM, Mauricio Faria de Oliveira wrote: > Do you remember specifying a block size of 512 kB for 'make-bcache' when > creating it? > > e.g., make-bcache --bdev|-B /dev/mdN --block|-w 512k # or similarly. My set was created by hand, and it's entirely possible I specified "--block 512k" instead of "--block 512" (though the backing device is 4096, so it should have actually been 4k). -- 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/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in Linux: Confirmed Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Works on focal! Linux nibbler 5.4.0-34-generic #38+lp1867916b1 SMP Sun May 31 21:41:06 -03 2020 x86_64 x86_64 x86_64 GNU/Linux Thanks! I'm curious to see the patch; I tried root causing it myself and suspected it had to do with something like an overflow in an unanticipated block size, but never got anywhere on that. Also keep in mind I filed an upstream bug (https://bugzilla.kernel.org/show_bug.cgi?id=207811), so please make sure to reference that when submitting the fix upstream. Again, thank you Mauricio! -- 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/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Sure, done. -- 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/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
** Attachment added: "lp1867916-lsblk" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5378817/+files/lp1867916-lsblk -- 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/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Done, please see attached. (The sd* devices do tend to move around; the bcache backing device is currently at sdb1.) -- 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/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
** Attachment added: "lp1867916-bcache-super-show.sd" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5378589/+files/lp1867916-bcache-super-show.sd -- 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/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
** Attachment added: "lp1867916-bcache-super-show.md" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5378590/+files/lp1867916-bcache-super-show.md -- 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/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
** Attachment added: "lp1867916-queue_block_size" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5378588/+files/lp1867916-queue_block_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/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Here's a crashdump from the working kernel, with everything enabled: https://www.finnie.org/stuff/lp1867916-crashdump-20200528.tar.xz -- 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/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
The bcache device is raid+bcache, with luks below it (and then lvm), so it's not directly mountable. Do you just want the stack set up and functional like normal? -- 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/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Mike: Sorry, that is not related. I'd suggest filing a new bug. Mauricio: Any update on this? This also affects the 5.4 line, so after upgrading to focal I needed to remain on 4.15.0-88. -- 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/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
I've bisected the problem down to commit
c35a4a858d0616e7817026d88f377c7201ad449a ("block: fix an integer
overflow in logical block size", upstream
ad6bf88a6c19a39fb3b0045d78ea880325dfcf15).
I don't know what the exact problem is with the commit, but seems to be
in the area of fs/block_dev.c set_init_blocksize() calling
bdev_logical_block_size() which the offending commit touches.
# bad: [a78d21bd8bb58c158f73108eb7d7402619fcae3d] UBUNTU: Ubuntu-4.15.0-91.92
# good: [d5b8ff45eabff3cb2232a2eea38a862edc647ab8] UBUNTU: Ubuntu-4.15.0-88.88
git bisect start 'Ubuntu-4.15.0-91.92' 'Ubuntu-4.15.0-88.88'
# bad: [c04c6d87ca3a7e2c8019e0a2349fcf1175ffcce0] KVM: PPC: Release all
hardware TCE tables attached to a group
git bisect bad c04c6d87ca3a7e2c8019e0a2349fcf1175ffcce0
# good: [9a6b3cea5792f94f03f579c668a60eb4ddd209f0] dt-bindings: reset: meson8b:
fix duplicate reset IDs
git bisect good 9a6b3cea5792f94f03f579c668a60eb4ddd209f0
# bad: [6783f1bf22bb55bcd2628d7cabeacc9c720971e6] ALSA: usb-audio: update quirk
for B PX to remove microphone
git bisect bad 6783f1bf22bb55bcd2628d7cabeacc9c720971e6
# skip: [c4099e7e88621e82a5b3a5b0a2e3d6d8eee4e8e0] ptp: free ptp device pin
descriptors properly
git bisect skip c4099e7e88621e82a5b3a5b0a2e3d6d8eee4e8e0
# bad: [3222d8b5d803ed733dba2da03b595cf90c871fe6] drm/nouveau/mmu: qualify vmm
during dtor
git bisect bad 3222d8b5d803ed733dba2da03b595cf90c871fe6
# skip: [3db4efba8dea644e54e339ac2e46b497aea93638] NFC: pn533: fix bulk-message
timeout
git bisect skip 3db4efba8dea644e54e339ac2e46b497aea93638
# skip: [211ff6ef5f2f19d86d35dcbb94d4b09ab7de00fc] batman-adv: Fix DAT
candidate selection on little endian systems
git bisect skip 211ff6ef5f2f19d86d35dcbb94d4b09ab7de00fc
# skip: [3cb4cbc154b57c2fb842fbacc6ea4bd625ce680f] perf hists: Fix variable
name's inconsistency in hists__for_each() macro
git bisect skip 3cb4cbc154b57c2fb842fbacc6ea4bd625ce680f
# good: [1d9d2aae71b2d1c18d7d69c4850ca57ebd1e6fc1] clk: Don't try to enable
critical clocks if prepare failed
git bisect good 1d9d2aae71b2d1c18d7d69c4850ca57ebd1e6fc1
# skip: [37f1c7c4bf8eaf03f0e07152f55e0dda97bd52e8] cfg80211: check for
set_wiphy_params
git bisect skip 37f1c7c4bf8eaf03f0e07152f55e0dda97bd52e8
# good: [43cdcecf3a1bd5fdf9cbce0f3908cdde789c7ffd] ALSA: seq: Fix racy access
for queue timer in proc read
git bisect good 43cdcecf3a1bd5fdf9cbce0f3908cdde789c7ffd
# bad: [7a10b28e6122e12323da46732fc345d476a21829] ARM: dts: am571x-idk: Fix
gpios property to have the correct gpio number
git bisect bad 7a10b28e6122e12323da46732fc345d476a21829
# good: [31e3c075719a3afe5ffd2b9b8e1f18e07255bd96] Fix built-in early-load
Intel microcode alignment
git bisect good 31e3c075719a3afe5ffd2b9b8e1f18e07255bd96
# bad: [c35a4a858d0616e7817026d88f377c7201ad449a] block: fix an integer
overflow in logical block size
git bisect bad c35a4a858d0616e7817026d88f377c7201ad449a
# first bad commit: [c35a4a858d0616e7817026d88f377c7201ad449a] block: fix an
integer overflow in logical block 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/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Status in linux package in Ubuntu:
In Progress
Bug description:
After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems
does not boot any longer. It always crashes during boot with a kernel
panic.
I suspect that this crash might be related to Bcache because this is
the only one of our systems where we use Bcache and the kernel panic
appears right after Bcache initialization.
I already checked that this bug still exists in the 4.15.0-92.93
kernel from proposed.
Unfortunately, I cannot do a bisect because this is a critical
production system and we do not have any other system with a similar
configuration.
I attached a screenshot with the trace of the kernel panic.
The last message that appears before the kernel panic (or rather the
last one that I can see - there is a rather long pause between that
message and the panic and I cannot scroll up far enough to ensure that
there are no other messages in between) is:
bcache: register_bcache() error /dev/dm-0: device already registered
When booting with kernel 4.15.0-88 that does not have this problem,
the next message is
bcache: register_bcache() error /dev/dm-12: device already registered
(emitting change event)
After that the next message is:
Begin: Loading essential drivers ... done
This message also appears after the kernel panic, but the boot process
stalls and the system can only be recovered by doing a hardware reset.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-88-generic 4.15.0-88.88
ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
Uname: Linux 4.15.0-88-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Mar 17 21:08 seq
[Kernel-packages] [Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
BTW, for future searchers, I've uploaded dmesg.202004081903 separately, and pasted the crash here: [ 194.36] bcache: bch_journal_replay() journal replay done, 3 keys in 6 entries, seq 23285862 [ 194.444622] bcache: register_cache() registered cache device sdb1 [ 194.448381] bcache: register_bdev() registered backing device md0 [ 194.602075] BUG: unable to handle kernel NULL pointer dereference at 0008 [ 194.602100] IP: create_empty_buffers+0x29/0xf0 [ 194.602110] PGD 0 P4D 0 [ 194.602121] Oops: [#1] SMP NOPTI [ 194.602137] Modules linked in: bcache ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter pps_ldisc aufs overlay cmac bnep bonding bridge stp llc arc4 snd_hda_codec_hdmi nls_iso8859_1 edac_mce_amd kvm_amd kvm irqbypass rtl8xxxu mac80211 btusb btrtl btbcm snd_hda_intel btintel snd_hda_codec bluetooth cfg80211 eeepc_wmi snd_hda_core asus_wmi joydev sparse_keymap snd_hwdep wmi_bmof input_leds snd_pcm ecdh_generic snd_timer snd soundcore ccp k10temp shpchp mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp libiscsi_tcp auth_rpcgss libiscsi nfs_acl scsi_transport_iscsi lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid1 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx [ 194.602323] xor raid6_pq libcrc32c hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nouveau crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc mxm_wmi video ttm drm_kms_helper aesni_intel syscopyarea sysfillrect igb sysimgblt aes_x86_64 fb_sys_fops crypto_simd glue_helper dca cryptd i2c_algo_bit drm i2c_piix4 ptp ahci nvme pps_core libahci nvme_core gpio_amdpt wmi gpio_generic [ 194.602406] CPU: 1 PID: 4403 Comm: bcache-register Not tainted 4.15.0-91-generic #92-Ubuntu [ 194.602425] Hardware name: System manufacturer System Product Name/PRIME X370-PRO, BIOS 4207 12/08/2018 [ 194.602447] RIP: 0010:create_empty_buffers+0x29/0xf0 [ 194.602459] RSP: 0018:a833cc37f7a8 EFLAGS: 00010246 [ 194.602471] RAX: RBX: f6227c3f4c00 RCX: 0013 [ 194.602487] RDX: RSI: 0008 RDI: f6227c3f4c00 [ 194.602503] RBP: a833cc37f7c0 R08: 0001 R09: dead00ff [ 194.602519] R10: 8976ca4f7aa0 R11: R12: [ 194.602535] R13: R14: R15: 0200 [ 194.602551] FS: 7f51c3bb2500() GS:89771ec4() knlGS: [ 194.602569] CS: 0010 DS: ES: CR0: 80050033 [ 194.602582] CR2: 0008 CR3: 000f24aea000 CR4: 003406e0 [ 194.602598] Call Trace: [ 194.602606] create_page_buffers+0x51/0x60 [ 194.602616] block_read_full_page+0x4e/0x370 [ 194.602626] ? set_init_blocksize+0x80/0x80 [ 194.602636] blkdev_readpage+0x18/0x20 [ 194.602646] do_read_cache_page+0x2a2/0x580 [ 194.602656] ? blkdev_writepages+0x40/0x40 [ 194.602667] ? update_load_avg+0x57f/0x6e0 [ 194.602676] read_cache_page+0x15/0x20 [ 194.602687] read_dev_sector+0x2d/0xd0 [ 194.602696] read_lba+0x130/0x220 [ 194.602704] ? efi_partition+0x11a/0x790 [ 194.602713] efi_partition+0x138/0x790 [ 194.602723] ? string+0x60/0x90 [ 194.602731] ? vsnprintf+0xfb/0x510 [ 194.602740] ? snprintf+0x45/0x70 [ 194.602748] ? is_gpt_valid.part.6+0x420/0x420 [ 194.602760] check_partition+0x130/0x230 [ 194.603304] ? check_partition+0x130/0x230 [ 194.603837] rescan_partitions+0xaa/0x350 [ 194.604372] bdev_disk_changed+0x53/0x60 [ 194.604895] __blkdev_get+0x34a/0x510 [ 194.605413] blkdev_get+0x129/0x320 [ 194.605930] ? wake_up_bit+0x42/0x50 [ 194.606445] ? unlock_new_inode+0x4c/0x80 [ 194.606947] ? bdget+0x108/0x120 [ 194.607432] device_add_disk+0x38b/0x490 [ 194.607909] ? bcache_dev_sectors_dirty_add+0xb0/0xb0 [bcache] [ 194.608373] bch_cached_dev_run.part.28+0x42/0x1a0 [bcache] [ 194.608821] ? wait_woken+0x80/0x80 [ 194.609258] bch_cached_dev_attach+0x3b5/0x4f0 [bcache] [ 194.609681] ? vprintk_func+0x47/0xc0 [ 194.610088] ? printk+0x52/0x6e [ 194.610479] register_bcache+0x864/0x1110 [bcache] [ 194.610861] ? register_bcache+0x864/0x1110 [bcache] [ 194.611227] kobj_attr_store+0x12/0x20 [ 194.611580] ? kobj_attr_store+0x12/0x20 [ 194.611925] sysfs_kf_write+0x3c/0x50 [ 194.612259] kernfs_fop_write+0x125/0x1a0 [ 194.612595] __vfs_write+0x1b/0x40 [ 194.612921] vfs_write+0xb1/0x1a0 [ 194.613245] SyS_write+0x5c/0xe0 [ 194.613565] do_syscall_64+0x73/0x130 [ 194.613886] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 194.614212] RIP: 0033:0x7f51c36b8154 [ 194.614530] RSP: 002b:7ffd27009a58 EFLAGS: 0246 ORIG_RAX: 0001 [ 194.614858] RAX: ffda RBX: 0009 RCX: 7f51c36b8154 [ 194.615183] RDX: 0009 RSI: 560160a77260 RDI: 0003 [ 194.615506] RBP:
[Kernel-packages] [Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Here you go: https://www.finnie.org/stuff/lp1867916-crashdump.tar.xz (138MB) Some notes on the process: - Also blacklisted it87 (DKMS) so the running kernel wasn't "tainted" - Also disabled the relevant crypttab entry for this group - 768M produced "crashkernel reservation failed - No suitable area found" in dmesg, used 512M instead - Had to disable secure boot (https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869672 which you also appear to be working on, heh) -- 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/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
I can confirm going from 4.15.0-88 to 4.15.0-91 on my bcache system
panics in the same way. Here's my layout:
-> sd{c,d,f,g,h}: each 4TB gpt, sd{c,d,f,g,h}1: each type linux_raid_member
--> md0: raid6, sd{c,d,f,g,h}1
--> sda: 512GB gpt, sda1: type bcache
---> bcache0: md0 + sda1
> whatadisk_crypt: LUKS on bcache0
-> LVM VG whatadisk: whatadisk_crypt
--> multiple LVs
There are also a handful of other disks (for example, nvme0n1 is the
encrypted boot disk), but the layout above is the only part which bcache
touches.
Happy to help with additional info or testing, please let me know.
--
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/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Status in linux package in Ubuntu:
In Progress
Bug description:
After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems
does not boot any longer. It always crashes during boot with a kernel
panic.
I suspect that this crash might be related to Bcache because this is
the only one of our systems where we use Bcache and the kernel panic
appears right after Bcache initialization.
I already checked that this bug still exists in the 4.15.0-92.93
kernel from proposed.
Unfortunately, I cannot do a bisect because this is a critical
production system and we do not have any other system with a similar
configuration.
I attached a screenshot with the trace of the kernel panic.
The last message that appears before the kernel panic (or rather the
last one that I can see - there is a rather long pause between that
message and the panic and I cannot scroll up far enough to ensure that
there are no other messages in between) is:
bcache: register_bcache() error /dev/dm-0: device already registered
When booting with kernel 4.15.0-88 that does not have this problem,
the next message is
bcache: register_bcache() error /dev/dm-12: device already registered
(emitting change event)
After that the next message is:
Begin: Loading essential drivers ... done
This message also appears after the kernel panic, but the boot process
stalls and the system can only be recovered by doing a hardware reset.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-88-generic 4.15.0-88.88
ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
Uname: Linux 4.15.0-88-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Mar 17 21:08 seq
crw-rw 1 root audio 116, 33 Mar 17 21:08 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Mar 18 12:55:18 2020
HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a
InstallationDate: Installed on 2013-07-02 (2450 days ago)
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release
amd64 (20130214)
MachineType: HP ProLiant DL160 G6
PciMultimedia:
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic
root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw
RelatedPackageVersions:
linux-restricted-modules-4.15.0-88-generic N/A
linux-backports-modules-4.15.0-88-generic N/A
linux-firmware 1.173.16
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago)
dmi.bios.date: 11/06/2009
dmi.bios.vendor: HP
dmi.bios.version: O33
dmi.chassis.asset.tag: 0191525
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr:
dmi.product.name: ProLiant DL160 G6
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+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 1771467] Re: Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0
The fix was bikeshedded a tiny bit on LKML, but is now accepted upstream
and AIUI will be in linux-next soon:
https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git/commit/?id=0d98ba8d70b0070ac117452ea0b663e26bbf46bf
This change is tested as backwards compatible with Ubuntu 4.15, and
would be appreciated for SRU.
--
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/1771467
Title:
Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
Verified on multiple DL360 Gen9 servers with up to date firmware.
Just before reboot or shutdown, there is the following panic:
[ 289.093083] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 289.093085] {1}[Hardware Error]: event severity: fatal
[ 289.093087] {1}[Hardware Error]: Error 0, type: fatal
[ 289.093088] {1}[Hardware Error]: section_type: PCIe error
[ 289.093090] {1}[Hardware Error]: port_type: 4, root port
[ 289.093091] {1}[Hardware Error]: version: 1.16
[ 289.093093] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093094] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093095] {1}[Hardware Error]: slot: 0
[ 289.093096] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093097] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093098] {1}[Hardware Error]: class_code: 040600
[ 289.093378] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093380] {1}[Hardware Error]: Error 1, type: fatal
[ 289.093381] {1}[Hardware Error]: section_type: PCIe error
[ 289.093382] {1}[Hardware Error]: port_type: 4, root port
[ 289.093383] {1}[Hardware Error]: version: 1.16
[ 289.093384] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093386] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093386] {1}[Hardware Error]: slot: 0
[ 289.093387] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093388] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093674] {1}[Hardware Error]: class_code: 040600
[ 289.093676] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093678] Kernel panic - not syncing: Fatal hardware error!
[ 289.093745] Kernel Offset: 0x1cc0 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 289.105835] ERST: [Firmware Warn]: Firmware does not respond in time.
It does eventually restart after this. Then during the subsequent
POST, the following warning appears:
Embedded RAID 1 : Smart Array P440ar Controller - (2048 MB, V6.30) 7 Logical
Drive(s) - Operation Failed
- 1719-Slot 0 Drive Array - A controller failure event occurred prior
to this power-up. (Previous lock up code = 0x13) Action: Install the
latest controller firmware. If the problem persists, replace the
controller.
The latter's symptoms are described in
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04805565
but the running storage controller firmware is much newer than the
doc's resolution.
Neither of these problems occur during shutdown/reboot on the xenial
kernel.
FWIW, when running on old P89 (1.50 (07/20/2015) vs 2.56
(01/22/2018)), the shutdown failure mode was a loop like so:
[529151.035267] NMI: IOCK error (debug interrupt?) for reason 75 on CPU 0.
[529153.222883] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.222884] Do you have a strange power saving mode enabled?
[529153.222884] Dazed and confused, but trying to continue
[529153.554447] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554448] Do you have a strange power saving mode enabled?
[529153.554449] Dazed and confused, but trying to continue
[529153.554450] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554451] Do you have a strange power saving mode enabled?
[529153.554452] Dazed and confused, but trying to continue
[529153.554452] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554453] Do you have a strange power saving mode enabled?
[529153.554454] Dazed and confused, but trying to continue
[529153.554454] Uhhuh. NMI received for unknown reason 35 on CPU 0.
[529153.554455] Do you have a strange power saving mode enabled?
[529153.554456] Dazed and confused, but trying to continue
[529153.554457] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554458] Do you have a strange power saving mode enabled?
[529153.554458] Dazed and confused, but trying to continue
[529153.554459] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554460] Do you have a strange power saving mode enabled?
[529153.554460] Dazed and
[Kernel-packages] [Bug 1775732] [NEW] arm64 soft lock crashes on nova-compute charm running
Public bug reported: Discovered on bionic, arm64 (Moonshot, verified on multiple swirlix cartridges), 4.15.0-22-generic. After deploying the nova-compute Juju charm, on subsequent reboots, within a few seconds after complete boot, everything will freeze and eventually display on the serial console (just these, no traces): [ 188.010510] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [juju-log:2272] [ 216.010292] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [juju-log:2272] (From here on, "lock up" refers to that sequence: boot a kernel, it completes boot to login prompt, then everything freezes a few seconds later, then BUGs.) It's usually but not always juju-log, sometimes a relation-ids or similar. I was able to briefly notice that it was in its startup config-changed hook. I've separated out and tested nearly everything it does during its startup config-changed (sets up bridging, writes some config files, restarts libvirtd/nova-compute/etc) without being able to trigger the bug, but I suspect proximity to boot is a factor. If I disable jujud- unit-nova-compute startup, boot, log in, re-enable and start (by which time over a minute or so has elapsed from boot finish), it will not lock up. Similarly, if I wrap the jujud startup in a `strace -Ff -o /var/log/strace.log` (which slows it down massively), it will not lock up. Watched pot syndrome. I've tried kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/ . I noticed most of the recent arm64 mainline kernels had failed builds, notified the kernel team channel and apw fixed the issue and started some rebuilds. What I've discovered (after many dead ends and a futile bisection) is that mainline builds before the rebuilds lock up, but fixed mainline builds initiated by apw DO NOT lock up. e.g. 4.16.3-041603.201804190730 locks up, but 4.16.6-041606.201806042022 does not lock up. (4.16.4 and 4.16.5 appear to have never been rebuilt and don't have arm64 debs, and that period is what I tried to bisect after figuring a fix must be in there.) But when I try to compile any of these recent kernels myself, they lock up when booted. Same kernel configs, tried on both bionic and in a cosmic chroot, tried both native arm64 compile and cross-compile from amd64. e.g. 4.16.6-041606.201806042022 from k.u.c does not lock up, but when I build it myself, it does. TBC, I've verified lock ups on the following kernels (all assume kernel configs from their respective Ubuntu or k.u.c mainline builds): - 4.15.0-22-generic from bionic (both Ubuntu-provided and my own recompile) - v4.16 (and all point releases) - v4.17 As I write this, my compiled v4.10 DOES NOT appear to lock up. I will attempt to bisect at a macro level from 4.10..4.15 and dig deeper. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 2 04:22 seq crw-rw 1 root audio 116, 33 Jun 2 04:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Jun 8 00:13:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug arm64 bionic uec-images -- 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/1775732 Title: arm64 soft lock crashes on nova-compute charm running Status in linux package in Ubuntu: Confirmed Bug description: Discovered on bionic, arm64 (Moonshot, verified on multiple swirlix cartridges), 4.15.0-22-generic. After deploying the nova-compute Juju charm, on subsequent reboots, within a few seconds after complete boot, everything will freeze and eventually display on the serial console (just these, no traces): [ 188.010510] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [juju-log:2272] [ 216.010292] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [juju-log:2272] (From here on, "lock up" refers to that
[Kernel-packages] [Bug 1771467] Re: Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0
A patch has been submitted to linux-pci, and I've confirmed this fix
works: https://lkml.org/lkml/2018/5/22/817
--
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/1771467
Title:
Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
Verified on multiple DL360 Gen9 servers with up to date firmware.
Just before reboot or shutdown, there is the following panic:
[ 289.093083] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 289.093085] {1}[Hardware Error]: event severity: fatal
[ 289.093087] {1}[Hardware Error]: Error 0, type: fatal
[ 289.093088] {1}[Hardware Error]: section_type: PCIe error
[ 289.093090] {1}[Hardware Error]: port_type: 4, root port
[ 289.093091] {1}[Hardware Error]: version: 1.16
[ 289.093093] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093094] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093095] {1}[Hardware Error]: slot: 0
[ 289.093096] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093097] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093098] {1}[Hardware Error]: class_code: 040600
[ 289.093378] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093380] {1}[Hardware Error]: Error 1, type: fatal
[ 289.093381] {1}[Hardware Error]: section_type: PCIe error
[ 289.093382] {1}[Hardware Error]: port_type: 4, root port
[ 289.093383] {1}[Hardware Error]: version: 1.16
[ 289.093384] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093386] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093386] {1}[Hardware Error]: slot: 0
[ 289.093387] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093388] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093674] {1}[Hardware Error]: class_code: 040600
[ 289.093676] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093678] Kernel panic - not syncing: Fatal hardware error!
[ 289.093745] Kernel Offset: 0x1cc0 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 289.105835] ERST: [Firmware Warn]: Firmware does not respond in time.
It does eventually restart after this. Then during the subsequent
POST, the following warning appears:
Embedded RAID 1 : Smart Array P440ar Controller - (2048 MB, V6.30) 7 Logical
Drive(s) - Operation Failed
- 1719-Slot 0 Drive Array - A controller failure event occurred prior
to this power-up. (Previous lock up code = 0x13) Action: Install the
latest controller firmware. If the problem persists, replace the
controller.
The latter's symptoms are described in
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04805565
but the running storage controller firmware is much newer than the
doc's resolution.
Neither of these problems occur during shutdown/reboot on the xenial
kernel.
FWIW, when running on old P89 (1.50 (07/20/2015) vs 2.56
(01/22/2018)), the shutdown failure mode was a loop like so:
[529151.035267] NMI: IOCK error (debug interrupt?) for reason 75 on CPU 0.
[529153.222883] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.222884] Do you have a strange power saving mode enabled?
[529153.222884] Dazed and confused, but trying to continue
[529153.554447] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554448] Do you have a strange power saving mode enabled?
[529153.554449] Dazed and confused, but trying to continue
[529153.554450] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554451] Do you have a strange power saving mode enabled?
[529153.554452] Dazed and confused, but trying to continue
[529153.554452] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554453] Do you have a strange power saving mode enabled?
[529153.554454] Dazed and confused, but trying to continue
[529153.554454] Uhhuh. NMI received for unknown reason 35 on CPU 0.
[529153.554455] Do you have a strange power saving mode enabled?
[529153.554456] Dazed and confused, but trying to continue
[529153.554457] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554458] Do you have a strange power saving mode enabled?
[529153.554458] Dazed and confused, but trying to continue
[529153.554459] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554460] Do you have a strange power saving mode enabled?
[529153.554460] Dazed and confused, but trying to continue
[529154.953916] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529154.953917] Do you have a strange power saving mode enabled?
[529154.953918] Dazed and confused, but trying
[Kernel-packages] [Bug 1771467] Re: Reboot/shutdown kernel panic on HP DL360 Gen9 w/ bionic 4.15.0
I tracked it down to https://patchwork.kernel.org/patch/10027157/ just
before 4.15-rc1. This appears to affect all DL360/DL380 Gen9 I've
encountered so far. Opened
https://bugzilla.kernel.org/show_bug.cgi?id=199779 and currently working
with Sinan Kaya to disagnose.
** Tags added: kernel-bug-exists-upstream
** Bug watch added: Linux Kernel Bug Tracker #199779
https://bugzilla.kernel.org/show_bug.cgi?id=199779
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Confirmed
** Summary changed:
- Reboot/shutdown kernel panic on HP DL360 Gen9 w/ bionic 4.15.0
+ Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.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/1771467
Title:
Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
Verified on multiple DL360 Gen9 servers with up to date firmware.
Just before reboot or shutdown, there is the following panic:
[ 289.093083] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 289.093085] {1}[Hardware Error]: event severity: fatal
[ 289.093087] {1}[Hardware Error]: Error 0, type: fatal
[ 289.093088] {1}[Hardware Error]: section_type: PCIe error
[ 289.093090] {1}[Hardware Error]: port_type: 4, root port
[ 289.093091] {1}[Hardware Error]: version: 1.16
[ 289.093093] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093094] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093095] {1}[Hardware Error]: slot: 0
[ 289.093096] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093097] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093098] {1}[Hardware Error]: class_code: 040600
[ 289.093378] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093380] {1}[Hardware Error]: Error 1, type: fatal
[ 289.093381] {1}[Hardware Error]: section_type: PCIe error
[ 289.093382] {1}[Hardware Error]: port_type: 4, root port
[ 289.093383] {1}[Hardware Error]: version: 1.16
[ 289.093384] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093386] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093386] {1}[Hardware Error]: slot: 0
[ 289.093387] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093388] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093674] {1}[Hardware Error]: class_code: 040600
[ 289.093676] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093678] Kernel panic - not syncing: Fatal hardware error!
[ 289.093745] Kernel Offset: 0x1cc0 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 289.105835] ERST: [Firmware Warn]: Firmware does not respond in time.
It does eventually restart after this. Then during the subsequent
POST, the following warning appears:
Embedded RAID 1 : Smart Array P440ar Controller - (2048 MB, V6.30) 7 Logical
Drive(s) - Operation Failed
- 1719-Slot 0 Drive Array - A controller failure event occurred prior
to this power-up. (Previous lock up code = 0x13) Action: Install the
latest controller firmware. If the problem persists, replace the
controller.
The latter's symptoms are described in
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04805565
but the running storage controller firmware is much newer than the
doc's resolution.
Neither of these problems occur during shutdown/reboot on the xenial
kernel.
FWIW, when running on old P89 (1.50 (07/20/2015) vs 2.56
(01/22/2018)), the shutdown failure mode was a loop like so:
[529151.035267] NMI: IOCK error (debug interrupt?) for reason 75 on CPU 0.
[529153.222883] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.222884] Do you have a strange power saving mode enabled?
[529153.222884] Dazed and confused, but trying to continue
[529153.554447] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554448] Do you have a strange power saving mode enabled?
[529153.554449] Dazed and confused, but trying to continue
[529153.554450] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554451] Do you have a strange power saving mode enabled?
[529153.554452] Dazed and confused, but trying to continue
[529153.554452] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554453] Do you have a strange power saving mode enabled?
[529153.554454] Dazed and confused, but trying to continue
[529153.554454] Uhhuh. NMI received for unknown reason 35 on CPU 0.
[529153.554455] Do you have a strange power saving mode enabled?
[529153.554456] Dazed and confused, but trying to
[Kernel-packages] [Bug 1771467] [NEW] Reboot/shutdown kernel panic on HP DL360 Gen9 w/ bionic 4.15.0
Public bug reported:
Verified on multiple DL360 Gen9 servers with up to date firmware. Just
before reboot or shutdown, there is the following panic:
[ 289.093083] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 289.093085] {1}[Hardware Error]: event severity: fatal
[ 289.093087] {1}[Hardware Error]: Error 0, type: fatal
[ 289.093088] {1}[Hardware Error]: section_type: PCIe error
[ 289.093090] {1}[Hardware Error]: port_type: 4, root port
[ 289.093091] {1}[Hardware Error]: version: 1.16
[ 289.093093] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093094] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093095] {1}[Hardware Error]: slot: 0
[ 289.093096] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093097] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093098] {1}[Hardware Error]: class_code: 040600
[ 289.093378] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093380] {1}[Hardware Error]: Error 1, type: fatal
[ 289.093381] {1}[Hardware Error]: section_type: PCIe error
[ 289.093382] {1}[Hardware Error]: port_type: 4, root port
[ 289.093383] {1}[Hardware Error]: version: 1.16
[ 289.093384] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093386] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093386] {1}[Hardware Error]: slot: 0
[ 289.093387] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093388] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093674] {1}[Hardware Error]: class_code: 040600
[ 289.093676] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093678] Kernel panic - not syncing: Fatal hardware error!
[ 289.093745] Kernel Offset: 0x1cc0 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 289.105835] ERST: [Firmware Warn]: Firmware does not respond in time.
It does eventually restart after this. Then during the subsequent POST,
the following warning appears:
Embedded RAID 1 : Smart Array P440ar Controller - (2048 MB, V6.30) 7 Logical
Drive(s) - Operation Failed
- 1719-Slot 0 Drive Array - A controller failure event occurred prior
to this power-up. (Previous lock up code = 0x13) Action: Install the
latest controller firmware. If the problem persists, replace the
controller.
The latter's symptoms are described in
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04805565
but the running storage controller firmware is much newer than the doc's
resolution.
Neither of these problems occur during shutdown/reboot on the xenial
kernel.
FWIW, when running on old P89 (1.50 (07/20/2015) vs 2.56 (01/22/2018)),
the shutdown failure mode was a loop like so:
[529151.035267] NMI: IOCK error (debug interrupt?) for reason 75 on CPU 0.
[529153.222883] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.222884] Do you have a strange power saving mode enabled?
[529153.222884] Dazed and confused, but trying to continue
[529153.554447] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554448] Do you have a strange power saving mode enabled?
[529153.554449] Dazed and confused, but trying to continue
[529153.554450] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554451] Do you have a strange power saving mode enabled?
[529153.554452] Dazed and confused, but trying to continue
[529153.554452] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554453] Do you have a strange power saving mode enabled?
[529153.554454] Dazed and confused, but trying to continue
[529153.554454] Uhhuh. NMI received for unknown reason 35 on CPU 0.
[529153.554455] Do you have a strange power saving mode enabled?
[529153.554456] Dazed and confused, but trying to continue
[529153.554457] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554458] Do you have a strange power saving mode enabled?
[529153.554458] Dazed and confused, but trying to continue
[529153.554459] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554460] Do you have a strange power saving mode enabled?
[529153.554460] Dazed and confused, but trying to continue
[529154.953916] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529154.953917] Do you have a strange power saving mode enabled?
[529154.953918] Dazed and confused, but trying to continue
But upgrading to 2.56 changes that to a kernel panic.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-signed-image-generic 4.15.0.21.22
ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
Uname: Linux 4.15.0-21-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 15 23:11 seq
crw-rw 1 root audio 116, 33 May 15 23:11 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error:
[Kernel-packages] [Bug 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
I'm not even remotely sure about things here, so some raw notes:
* Current bisect effort ("oh man, this will take forever"):
# bad: [69973b830859bc6529a7a0468ba0d80ee5117826] Linux 4.9
# good: [c8d2bc9bc39ebea8437fd974fdbc21847bb897a3] Linux 4.8
git bisect start 'v4.9' 'v4.8'
# good: [a5af7e1fc69a46f29b977fd4b570e0ac414c2338] rxrpc: Fix loss of PING
RESPONSE ACK production due to PING ACKs
git bisect good a5af7e1fc69a46f29b977fd4b570e0ac414c2338
# bad: [a379f71a30dddbd2e7393624e455ce53c87965d1] Merge branch 'akpm' (patches
from Andrew)
git bisect bad a379f71a30dddbd2e7393624e455ce53c87965d1
* Found ppc_tm=off, tried it on 4.15.0 generic, works!
* Might be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1664622 - might be a
qemu issue
* 4.15.0 does work on scalingstack bos02 POWER8 KVM xenial xenial hosts
(-machine pseries-xenial,accel=kvm,usb=off -cpu host), but I figured
that had already been tested and would have been noticed by now. (If I
hadn't mentioned before, the host running the ppc64el fullvirt VM at
home is a xenial host.)
* See also http://lists.gnu.org/archive/html/qemu-
ppc/2018-01/msg00021.html - might be mitigated with pseries-2.12 with a
bionic host qemu setup, but I don't have an easy way to test with a
bionic host + qemu at the moment.
--
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/1761626
Title:
[regression] bionic 4.15.0-13-generic panics on qemu ppc64el
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Artful:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel
panics before initrd. Going back to xenial 4.4.0 works correctly.
linux-image-4.15.0-13-generic:
Installed: 4.15.0-13.14
Candidate: 4.15.0-13.14
Version table:
*** 4.15.0-13.14 500
500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main
ppc64el Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic ppc64le
.var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform'
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Apr 5 16:11 seq
crw-rw 1 root audio 116, 33 Apr 5 16:11 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Thu Apr 5 16:13:28 2018
HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic
root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro
ProcLoadAvg: 3.04 2.18 0.92 3/119 1643
ProcLocks:
1: POSIX ADVISORY WRITE 1225 00:12:470 0 EOF
2: POSIX ADVISORY WRITE 841 00:12:459 0 EOF
3: FLOCK ADVISORY WRITE 832 00:12:449 0 EOF
4: POSIX ADVISORY WRITE 802 00:12:432 0 EOF
5: POSIX ADVISORY WRITE 350 00:12:294 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/dev/vda3 partition1408960 0 -1
ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP
Mon Apr 2 16:08:02 UTC 2018
RelatedPackageVersions:
linux-restricted-modules-4.4.0-119-generic N/A
linux-backports-modules-4.4.0-119-generic N/A
linux-firmware 1.173
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago)
cpu_cores: Number of cores present = 1
cpu_coreson: Number of cores online = 1
cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255:
Machine is not SMT capable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+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 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
4.8.0 works, 4.9.0 panics. I'll see about bisecting. -- 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/1761626 Title: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Triaged Bug description: When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel panics before initrd. Going back to xenial 4.4.0 works correctly. linux-image-4.15.0-13-generic: Installed: 4.15.0-13.14 Candidate: 4.15.0-13.14 Version table: *** 4.15.0-13.14 500 500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main ppc64el Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic ppc64le .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform' AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 16:11 seq crw-rw 1 root audio 116, 33 Apr 5 16:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Apr 5 16:13:28 2018 HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro ProcLoadAvg: 3.04 2.18 0.92 3/119 1643 ProcLocks: 1: POSIX ADVISORY WRITE 1225 00:12:470 0 EOF 2: POSIX ADVISORY WRITE 841 00:12:459 0 EOF 3: FLOCK ADVISORY WRITE 832 00:12:449 0 EOF 4: POSIX ADVISORY WRITE 802 00:12:432 0 EOF 5: POSIX ADVISORY WRITE 350 00:12:294 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/vda3 partition1408960 0 -1 ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP Mon Apr 2 16:08:02 UTC 2018 RelatedPackageVersions: linux-restricted-modules-4.4.0-119-generic N/A linux-backports-modules-4.4.0-119-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago) cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+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 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
I can test earlier mainlines, but keep in mind that ppc64el is very slow on my home qemu setup (note "only" "very slow"; ppc64 is "amazingly slow", presumably due to endian swapping). Does Kernel have a POWER8 playground machine, if it comes to bisect compiling? -- 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/1761626 Title: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Triaged Bug description: When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel panics before initrd. Going back to xenial 4.4.0 works correctly. linux-image-4.15.0-13-generic: Installed: 4.15.0-13.14 Candidate: 4.15.0-13.14 Version table: *** 4.15.0-13.14 500 500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main ppc64el Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic ppc64le .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform' AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 16:11 seq crw-rw 1 root audio 116, 33 Apr 5 16:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Apr 5 16:13:28 2018 HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro ProcLoadAvg: 3.04 2.18 0.92 3/119 1643 ProcLocks: 1: POSIX ADVISORY WRITE 1225 00:12:470 0 EOF 2: POSIX ADVISORY WRITE 841 00:12:459 0 EOF 3: FLOCK ADVISORY WRITE 832 00:12:449 0 EOF 4: POSIX ADVISORY WRITE 802 00:12:432 0 EOF 5: POSIX ADVISORY WRITE 350 00:12:294 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/vda3 partition1408960 0 -1 ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP Mon Apr 2 16:08:02 UTC 2018 RelatedPackageVersions: linux-restricted-modules-4.4.0-119-generic N/A linux-backports-modules-4.4.0-119-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago) cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+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 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
Same result with 4.16.0-041600-generic and 4.13.0-38-generic -- 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/1761626 Title: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el Status in linux package in Ubuntu: Confirmed Bug description: When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel panics before initrd. Going back to xenial 4.4.0 works correctly. linux-image-4.15.0-13-generic: Installed: 4.15.0-13.14 Candidate: 4.15.0-13.14 Version table: *** 4.15.0-13.14 500 500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main ppc64el Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic ppc64le .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform' AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 16:11 seq crw-rw 1 root audio 116, 33 Apr 5 16:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Apr 5 16:13:28 2018 HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro ProcLoadAvg: 3.04 2.18 0.92 3/119 1643 ProcLocks: 1: POSIX ADVISORY WRITE 1225 00:12:470 0 EOF 2: POSIX ADVISORY WRITE 841 00:12:459 0 EOF 3: FLOCK ADVISORY WRITE 832 00:12:449 0 EOF 4: POSIX ADVISORY WRITE 802 00:12:432 0 EOF 5: POSIX ADVISORY WRITE 350 00:12:294 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/vda3 partition1408960 0 -1 ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP Mon Apr 2 16:08:02 UTC 2018 RelatedPackageVersions: linux-restricted-modules-4.4.0-119-generic N/A linux-backports-modules-4.4.0-119-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago) cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+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 1761626] [NEW] [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
Public bug reported: When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel panics before initrd. Going back to xenial 4.4.0 works correctly. linux-image-4.15.0-13-generic: Installed: 4.15.0-13.14 Candidate: 4.15.0-13.14 Version table: *** 4.15.0-13.14 500 500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main ppc64el Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic ppc64le .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform' AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 16:11 seq crw-rw 1 root audio 116, 33 Apr 5 16:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Apr 5 16:13:28 2018 HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro ProcLoadAvg: 3.04 2.18 0.92 3/119 1643 ProcLocks: 1: POSIX ADVISORY WRITE 1225 00:12:470 0 EOF 2: POSIX ADVISORY WRITE 841 00:12:459 0 EOF 3: FLOCK ADVISORY WRITE 832 00:12:449 0 EOF 4: POSIX ADVISORY WRITE 802 00:12:432 0 EOF 5: POSIX ADVISORY WRITE 350 00:12:294 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/vda3 partition 1408960 0 -1 ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP Mon Apr 2 16:08:02 UTC 2018 RelatedPackageVersions: linux-restricted-modules-4.4.0-119-generic N/A linux-backports-modules-4.4.0-119-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago) cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug bionic ppc64el -- 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/1761626 Title: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el Status in linux package in Ubuntu: Confirmed Bug description: When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel panics before initrd. Going back to xenial 4.4.0 works correctly. linux-image-4.15.0-13-generic: Installed: 4.15.0-13.14 Candidate: 4.15.0-13.14 Version table: *** 4.15.0-13.14 500 500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main ppc64el Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic ppc64le .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform' AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 16:11 seq crw-rw 1 root audio 116, 33 Apr 5 16:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Apr 5 16:13:28 2018 HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro ProcLoadAvg: 3.04 2.18 0.92 3/119 1643 ProcLocks: 1: POSIX ADVISORY WRITE 1225 00:12:470 0 EOF 2: POSIX ADVISORY WRITE 841
[Kernel-packages] [Bug 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
** Attachment added: "Kernel boot log for 4.15.0-13-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+attachment/5103357/+files/1761626-4.15.0-13-generic.boot.log -- 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/1761626 Title: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el Status in linux package in Ubuntu: Confirmed Bug description: When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel panics before initrd. Going back to xenial 4.4.0 works correctly. linux-image-4.15.0-13-generic: Installed: 4.15.0-13.14 Candidate: 4.15.0-13.14 Version table: *** 4.15.0-13.14 500 500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main ppc64el Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic ppc64le .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform' AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 16:11 seq crw-rw 1 root audio 116, 33 Apr 5 16:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Apr 5 16:13:28 2018 HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro ProcLoadAvg: 3.04 2.18 0.92 3/119 1643 ProcLocks: 1: POSIX ADVISORY WRITE 1225 00:12:470 0 EOF 2: POSIX ADVISORY WRITE 841 00:12:459 0 EOF 3: FLOCK ADVISORY WRITE 832 00:12:449 0 EOF 4: POSIX ADVISORY WRITE 802 00:12:432 0 EOF 5: POSIX ADVISORY WRITE 350 00:12:294 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/vda3 partition1408960 0 -1 ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP Mon Apr 2 16:08:02 UTC 2018 RelatedPackageVersions: linux-restricted-modules-4.4.0-119-generic N/A linux-backports-modules-4.4.0-119-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago) cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+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 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
** Attachment added: "libvirt XML file for instance" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+attachment/5103368/+files/1761626-libvirt.xml -- 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/1761626 Title: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el Status in linux package in Ubuntu: Confirmed Bug description: When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel panics before initrd. Going back to xenial 4.4.0 works correctly. linux-image-4.15.0-13-generic: Installed: 4.15.0-13.14 Candidate: 4.15.0-13.14 Version table: *** 4.15.0-13.14 500 500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main ppc64el Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic ppc64le .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform' AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 16:11 seq crw-rw 1 root audio 116, 33 Apr 5 16:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Apr 5 16:13:28 2018 HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro ProcLoadAvg: 3.04 2.18 0.92 3/119 1643 ProcLocks: 1: POSIX ADVISORY WRITE 1225 00:12:470 0 EOF 2: POSIX ADVISORY WRITE 841 00:12:459 0 EOF 3: FLOCK ADVISORY WRITE 832 00:12:449 0 EOF 4: POSIX ADVISORY WRITE 802 00:12:432 0 EOF 5: POSIX ADVISORY WRITE 350 00:12:294 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/vda3 partition1408960 0 -1 ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP Mon Apr 2 16:08:02 UTC 2018 RelatedPackageVersions: linux-restricted-modules-4.4.0-119-generic N/A linux-backports-modules-4.4.0-119-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago) cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+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 1284093] Re: Please update regulations to support VHT
This is one of the major contributing factors to LP: #1437913. I have rebased 2013.02.13-1ubuntu1 on top of Debian 2014.11.18-1, please see: https://launchpad.net/~fo0bar/+archive/ubuntu/ppa/+build/7325504 Could I get a sponsor upload? Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1284093 Title: Please update regulations to support VHT Status in wireless-regdb package in Ubuntu: Confirmed Bug description: Only very recent versions of wireless-regdb have support for VHT (80mhz channels); in addition, all current kernels have a bug that will cause your card to fail to associate with a VHT ap when your local regdb didn't allow VHT: https://bugzilla.kernel.org/show_bug.cgi?id=70881 I have updated the existing Debian bug requesting this too: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729089 Well, more precisely I have emailed the update but it hasn't gone through yet. :) I would recommend updating to 2013.11.27 (current upstream) as it includes other regulatory fixes. I would also recommend applying this to at least Precise and Trusty, possibly Saucy since it is still supported. Here is the update that should post to the Debian bug soon: I would much appreciate this, especially you make the jump to 2013.11.27. The new regdb will also solve issues with 802.11ac; the referenced version appears to be the first with support for 80mhz channels. Without the new regdb (or a patch the kernel that masks the symptoms, below), when you connect to an AP that supports 80mhz channels, you are disconnected with a nearly useless error. Link to the ticket, with details and the symptom-masking patch that will be in future kernels: https://bugzilla.kernel.org/show_bug.cgi?id=70881 It would be great if we could get the new regdb upstream into Debian asap; in the meantime I will try to get an updated version into a ppa for Ubuntu users at least. ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1284093/+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 1437913] Re: Wifi unstable on vivid with Intel 7265 (Thinkpad X250)
The problem is still being diagnosed on kernel bugzilla, but for the moment, iw reg set US seems to be a workaround. -- 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/1437913 Title: Wifi unstable on vivid with Intel 7265 (Thinkpad X250) Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Triaged Bug description: After upgrading from utopic to vivid beta, wifi on the Intel 7265 on my Thinkpad X250 has become unstable (linux-image 3.19.0-10.10, linux- firmware 1.143). I'm seeing two primary problems: * On 5GHz 802.11ac, I'll get DEAUTH_LEAVING almost exactly every minute, followed by an immediate reconnect. * On both 2.4GHz and 5GHz, all network activity will cease after 10-20 minutes. A manual reconnect will temporarily fix network activity. This is complicated by the fact that the newer firmware requires kernel 3.19 and kernel 3.19 requires the iwlwifi-7265D*.ucode firmware instead of the old iwlwifi-7265*.ucode firmware, so it's not possible to mix/match older/newer kernel/firmware combinations, nor do a kernel bisect. FAOD, the latest utopic kernel/firmware combination (linux-image 3.16.0-33.44, linux-firmware 1.138.1) works fine, which I can use in vivid if I manually install them. I have tested ~kernel-ppa/mainline 3.19.3-031903.201503261036 and 4.0.0-04rc5.201503230035, which exhibit the same problems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-10-generic 3.19.0-10.10 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1862 F pulseaudio /dev/snd/controlC1: ryan 1862 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 29 11:42:13 2015 HibernationDevice: RESUME=UUID=c21a0227-27e2-4c4f-8bd9-30793932acbc InstallationDate: Installed on 2015-03-07 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20CMCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux acpi_backlight=vendor psmouse.proto=imps quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-10-generic N/A linux-backports-modules-3.19.0-10-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET28W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CMCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET28W(1.05):bd01/23/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CMCTO1WW dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1437913/+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 1437913] Re: Wifi unstable on vivid with Intel 7265 (Thinkpad X250)
http://marc.info/?l=linux-wirelessm=142778129512570w=2 -- 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/1437913 Title: Wifi unstable on vivid with Intel 7265 (Thinkpad X250) Status in linux package in Ubuntu: Triaged Bug description: After upgrading from utopic to vivid beta, wifi on the Intel 7265 on my Thinkpad X250 has become unstable (linux-image 3.19.0-10.10, linux- firmware 1.143). I'm seeing two primary problems: * On 5GHz 802.11ac, I'll get DEAUTH_LEAVING almost exactly every minute, followed by an immediate reconnect. * On both 2.4GHz and 5GHz, all network activity will cease after 10-20 minutes. A manual reconnect will temporarily fix network activity. This is complicated by the fact that the newer firmware requires kernel 3.19 and kernel 3.19 requires the iwlwifi-7265D*.ucode firmware instead of the old iwlwifi-7265*.ucode firmware, so it's not possible to mix/match older/newer kernel/firmware combinations, nor do a kernel bisect. FAOD, the latest utopic kernel/firmware combination (linux-image 3.16.0-33.44, linux-firmware 1.138.1) works fine, which I can use in vivid if I manually install them. I have tested ~kernel-ppa/mainline 3.19.3-031903.201503261036 and 4.0.0-04rc5.201503230035, which exhibit the same problems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-10-generic 3.19.0-10.10 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1862 F pulseaudio /dev/snd/controlC1: ryan 1862 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 29 11:42:13 2015 HibernationDevice: RESUME=UUID=c21a0227-27e2-4c4f-8bd9-30793932acbc InstallationDate: Installed on 2015-03-07 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20CMCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux acpi_backlight=vendor psmouse.proto=imps quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-10-generic N/A linux-backports-modules-3.19.0-10-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET28W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CMCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET28W(1.05):bd01/23/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CMCTO1WW dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437913/+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 1437913] Re: Wifi unstable on vivid with Intel 7265 (Thinkpad X250)
** Bug watch added: Linux Kernel Bug Tracker #95901 http://bugzilla.kernel.org/show_bug.cgi?id=95901 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=95901 Importance: Unknown Status: Unknown -- 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/1437913 Title: Wifi unstable on vivid with Intel 7265 (Thinkpad X250) Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Triaged Bug description: After upgrading from utopic to vivid beta, wifi on the Intel 7265 on my Thinkpad X250 has become unstable (linux-image 3.19.0-10.10, linux- firmware 1.143). I'm seeing two primary problems: * On 5GHz 802.11ac, I'll get DEAUTH_LEAVING almost exactly every minute, followed by an immediate reconnect. * On both 2.4GHz and 5GHz, all network activity will cease after 10-20 minutes. A manual reconnect will temporarily fix network activity. This is complicated by the fact that the newer firmware requires kernel 3.19 and kernel 3.19 requires the iwlwifi-7265D*.ucode firmware instead of the old iwlwifi-7265*.ucode firmware, so it's not possible to mix/match older/newer kernel/firmware combinations, nor do a kernel bisect. FAOD, the latest utopic kernel/firmware combination (linux-image 3.16.0-33.44, linux-firmware 1.138.1) works fine, which I can use in vivid if I manually install them. I have tested ~kernel-ppa/mainline 3.19.3-031903.201503261036 and 4.0.0-04rc5.201503230035, which exhibit the same problems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-10-generic 3.19.0-10.10 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1862 F pulseaudio /dev/snd/controlC1: ryan 1862 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 29 11:42:13 2015 HibernationDevice: RESUME=UUID=c21a0227-27e2-4c4f-8bd9-30793932acbc InstallationDate: Installed on 2015-03-07 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20CMCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux acpi_backlight=vendor psmouse.proto=imps quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-10-generic N/A linux-backports-modules-3.19.0-10-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET28W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CMCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET28W(1.05):bd01/23/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CMCTO1WW dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1437913/+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 1437913] Re: Wifi unstable on vivid with Intel 7265 (Thinkpad X250)
BIOS updated to 1.07, no change in behavior. N10ET30W (1.07 ) 03/05/2015 ** 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/1437913 Title: Wifi unstable on vivid with Intel 7265 (Thinkpad X250) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from utopic to vivid beta, wifi on the Intel 7265 on my Thinkpad X250 has become unstable (linux-image 3.19.0-10.10, linux- firmware 1.143). I'm seeing two primary problems: * On 5GHz 802.11ac, I'll get DEAUTH_LEAVING almost exactly every minute, followed by an immediate reconnect. * On both 2.4GHz and 5GHz, all network activity will cease after 10-20 minutes. A manual reconnect will temporarily fix network activity. This is complicated by the fact that the newer firmware requires kernel 3.19 and kernel 3.19 requires the iwlwifi-7265D*.ucode firmware instead of the old iwlwifi-7265*.ucode firmware, so it's not possible to mix/match older/newer kernel/firmware combinations, nor do a kernel bisect. FAOD, the latest utopic kernel/firmware combination (linux-image 3.16.0-33.44, linux-firmware 1.138.1) works fine, which I can use in vivid if I manually install them. I have tested ~kernel-ppa/mainline 3.19.3-031903.201503261036 and 4.0.0-04rc5.201503230035, which exhibit the same problems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-10-generic 3.19.0-10.10 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1862 F pulseaudio /dev/snd/controlC1: ryan 1862 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 29 11:42:13 2015 HibernationDevice: RESUME=UUID=c21a0227-27e2-4c4f-8bd9-30793932acbc InstallationDate: Installed on 2015-03-07 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20CMCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux acpi_backlight=vendor psmouse.proto=imps quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-10-generic N/A linux-backports-modules-3.19.0-10-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET28W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CMCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET28W(1.05):bd01/23/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CMCTO1WW dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437913/+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 1437913] Re: Wifi unstable on vivid with Intel 7265 (Thinkpad X250)
No change with 4.0.0-04rc6.201503291935. ** 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/1437913 Title: Wifi unstable on vivid with Intel 7265 (Thinkpad X250) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from utopic to vivid beta, wifi on the Intel 7265 on my Thinkpad X250 has become unstable (linux-image 3.19.0-10.10, linux- firmware 1.143). I'm seeing two primary problems: * On 5GHz 802.11ac, I'll get DEAUTH_LEAVING almost exactly every minute, followed by an immediate reconnect. * On both 2.4GHz and 5GHz, all network activity will cease after 10-20 minutes. A manual reconnect will temporarily fix network activity. This is complicated by the fact that the newer firmware requires kernel 3.19 and kernel 3.19 requires the iwlwifi-7265D*.ucode firmware instead of the old iwlwifi-7265*.ucode firmware, so it's not possible to mix/match older/newer kernel/firmware combinations, nor do a kernel bisect. FAOD, the latest utopic kernel/firmware combination (linux-image 3.16.0-33.44, linux-firmware 1.138.1) works fine, which I can use in vivid if I manually install them. I have tested ~kernel-ppa/mainline 3.19.3-031903.201503261036 and 4.0.0-04rc5.201503230035, which exhibit the same problems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-10-generic 3.19.0-10.10 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1862 F pulseaudio /dev/snd/controlC1: ryan 1862 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 29 11:42:13 2015 HibernationDevice: RESUME=UUID=c21a0227-27e2-4c4f-8bd9-30793932acbc InstallationDate: Installed on 2015-03-07 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20CMCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux acpi_backlight=vendor psmouse.proto=imps quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-10-generic N/A linux-backports-modules-3.19.0-10-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET28W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CMCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET28W(1.05):bd01/23/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CMCTO1WW dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437913/+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 1437913] Re: Wifi unstable on vivid with Intel 7265 (Thinkpad X250)
ASUS RT-AC87R (retail version of the RT-AC87U, same hardware), firmware 3.0.0.4.378_4608-g7e6c1e5 (latest), in WAP-only mode. ** 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/1437913 Title: Wifi unstable on vivid with Intel 7265 (Thinkpad X250) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from utopic to vivid beta, wifi on the Intel 7265 on my Thinkpad X250 has become unstable (linux-image 3.19.0-10.10, linux- firmware 1.143). I'm seeing two primary problems: * On 5GHz 802.11ac, I'll get DEAUTH_LEAVING almost exactly every minute, followed by an immediate reconnect. * On both 2.4GHz and 5GHz, all network activity will cease after 10-20 minutes. A manual reconnect will temporarily fix network activity. This is complicated by the fact that the newer firmware requires kernel 3.19 and kernel 3.19 requires the iwlwifi-7265D*.ucode firmware instead of the old iwlwifi-7265*.ucode firmware, so it's not possible to mix/match older/newer kernel/firmware combinations, nor do a kernel bisect. FAOD, the latest utopic kernel/firmware combination (linux-image 3.16.0-33.44, linux-firmware 1.138.1) works fine, which I can use in vivid if I manually install them. I have tested ~kernel-ppa/mainline 3.19.3-031903.201503261036 and 4.0.0-04rc5.201503230035, which exhibit the same problems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-10-generic 3.19.0-10.10 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1862 F pulseaudio /dev/snd/controlC1: ryan 1862 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 29 11:42:13 2015 HibernationDevice: RESUME=UUID=c21a0227-27e2-4c4f-8bd9-30793932acbc InstallationDate: Installed on 2015-03-07 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20CMCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux acpi_backlight=vendor psmouse.proto=imps quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-10-generic N/A linux-backports-modules-3.19.0-10-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET28W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CMCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET28W(1.05):bd01/23/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CMCTO1WW dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437913/+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 1437913] [NEW] Wifi unstable on vivid with Intel 7265 (Thinkpad X250)
Public bug reported: After upgrading from utopic to vivid beta, wifi on the Intel 7265 on my Thinkpad X250 has become unstable (linux-image 3.19.0-10.10, linux- firmware 1.143). I'm seeing two primary problems: * On 5GHz 802.11ac, I'll get DEAUTH_LEAVING almost exactly every minute, followed by an immediate reconnect. * On both 2.4GHz and 5GHz, all network activity will cease after 10-20 minutes. A manual reconnect will temporarily fix network activity. This is complicated by the fact that the newer firmware requires kernel 3.19 and kernel 3.19 requires the iwlwifi-7265D*.ucode firmware instead of the old iwlwifi-7265*.ucode firmware, so it's not possible to mix/match older/newer kernel/firmware combinations, nor do a kernel bisect. FAOD, the latest utopic kernel/firmware combination (linux-image 3.16.0-33.44, linux-firmware 1.138.1) works fine, which I can use in vivid if I manually install them. I have tested ~kernel-ppa/mainline 3.19.3-031903.201503261036 and 4.0.0-04rc5.201503230035, which exhibit the same problems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-10-generic 3.19.0-10.10 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1862 F pulseaudio /dev/snd/controlC1: ryan 1862 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 29 11:42:13 2015 HibernationDevice: RESUME=UUID=c21a0227-27e2-4c4f-8bd9-30793932acbc InstallationDate: Installed on 2015-03-07 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20CMCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux acpi_backlight=vendor psmouse.proto=imps quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-10-generic N/A linux-backports-modules-3.19.0-10-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET28W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CMCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET28W(1.05):bd01/23/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CMCTO1WW dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1437913 Title: Wifi unstable on vivid with Intel 7265 (Thinkpad X250) Status in linux package in Ubuntu: New Bug description: After upgrading from utopic to vivid beta, wifi on the Intel 7265 on my Thinkpad X250 has become unstable (linux-image 3.19.0-10.10, linux- firmware 1.143). I'm seeing two primary problems: * On 5GHz 802.11ac, I'll get DEAUTH_LEAVING almost exactly every minute, followed by an immediate reconnect. * On both 2.4GHz and 5GHz, all network activity will cease after 10-20 minutes. A manual reconnect will temporarily fix network activity. This is complicated by the fact that the newer firmware requires kernel 3.19 and kernel 3.19 requires the iwlwifi-7265D*.ucode firmware instead of the old iwlwifi-7265*.ucode firmware, so it's not possible to mix/match older/newer kernel/firmware combinations, nor do a kernel bisect. FAOD, the latest utopic kernel/firmware combination (linux-image 3.16.0-33.44, linux-firmware 1.138.1) works fine, which I can use in vivid if I manually install them. I have tested ~kernel-ppa/mainline 3.19.3-031903.201503261036 and 4.0.0-04rc5.201503230035, which exhibit the same problems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-10-generic 3.19.0-10.10 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1862 F pulseaudio /dev/snd/controlC1: ryan 1862 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 29 11:42:13 2015 HibernationDevice: RESUME=UUID=c21a0227-27e2-4c4f-8bd9-30793932acbc InstallationDate: Installed on 2015-03-07 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20CMCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1348832] Re: e1000e Detected Hardware Unit Hang
Tested linux- image-3.16.0-031600rc7-generic_3.16.0-031600rc7.201407271635_amd64.deb for a week, was not able to replicate. ** Tags added: kernel-fixed-upstream-3.16-rc7 ** 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/1348832 Title: e1000e Detected Hardware Unit Hang Status in “linux” package in Ubuntu: Confirmed Bug description: e1000e device on a trusty router/server/etc, up for a few weeks, stopped responding and went into a Detected Hardware Unit Hang loop. At the time, the interface was under moderate load, about 60mbps inbound. [1871400.121801] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: [1871400.121801] TDH 92 [1871400.121801] TDT cf [1871400.121801] next_to_use cf [1871400.121801] next_to_clean90 [1871400.121801] buffer_info[next_to_clean]: [1871400.121801] time_stamp 11be7959f [1871400.121801] next_to_watch92 [1871400.121801] jiffies 11be79797 [1871400.121801] next_to_watch.status 0 [1871400.121801] MAC Status 80083 [1871400.121801] PHY Status 796d [1871400.121801] PHY 1000BASE-T Status 7800 [1871400.121801] PHY Extended Status3000 [1871400.121801] PCI Status 10 [1871402.120130] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: [1871402.120130] TDH 92 [1871402.120130] TDT cf [1871402.120130] next_to_use cf [1871402.120130] next_to_clean90 [1871402.120130] buffer_info[next_to_clean]: [1871402.120130] time_stamp 11be7959f [1871402.120130] next_to_watch92 [1871402.120130] jiffies 11be7998b [1871402.120130] next_to_watch.status 0 [1871402.120130] MAC Status 80083 [1871402.120130] PHY Status 796d [1871402.120130] PHY 1000BASE-T Status 7800 [1871402.120130] PHY Extended Status3000 [1871402.120130] PCI Status 10 [1871404.118513] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: [1871404.118513] TDH 92 [1871404.118513] TDT cf [1871404.118513] next_to_use cf [1871404.118513] next_to_clean90 [1871404.118513] buffer_info[next_to_clean]: [1871404.118513] time_stamp 11be7959f [1871404.118513] next_to_watch92 [1871404.118513] jiffies 11be79b7f [1871404.118513] next_to_watch.status 0 [1871404.118513] MAC Status 80083 [1871404.118513] PHY Status 796d [1871404.118513] PHY 1000BASE-T Status 7800 [1871404.118513] PHY Extended Status3000 [1871404.118513] PCI Status 10 [1871405.129366] [ cut here ] [1871405.129374] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.13.0/net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280() [1871405.129375] NETDEV WATCHDOG: eth1 (e1000e): transmit queue 0 timed out [1871405.129376] Modules linked in: ksplice_vijajns4_vmlinux_new(OF) ksplice_vijajns4(OF) ksplice_ax32i68r_vmlinux_new(OF) ksplice_ax32i68r(OF) ksplice_n4y5yx0j_vmlinux_new(OF) ksplice_n4y5yx0j(OF) nct6775(F) hwmon_vid(F) xt_nat vhost_net vhost macvtap macvlan ip6t_REJECT ipt_REJECT xt_LOG ipt_MASQUERADE xt_TCPMSS iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack xt_tcpudp ip6table_filter ip6_tables iptable_filter ip_tables x_tables sit tunnel4 ip_tunnel bridge stp llc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache jfs dm_multipath scsi_dh x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm ftdi_sio joydev usbserial parport_pc mei_me mei serio_raw ppdev acpi_pad mac_hid coretemp lp parport dm_crypt raid456 async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear hid_generic raid10 usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 i915 lrw e1000e gf128mul glue_helper ablk_helper i2c_algo_bit cryptd psmouse ahci drm_kms_helper ptp libahci pps_core video drm [last unloaded: ksplice_vijajns4_vmlinux_old] [1871405.129434] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GF O 3.13.0-30-generic #54-Ubuntu [1871405.129435] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z97 Pro3, BIOS P1.40 05/23/2014 [1871405.129436] 0009 88081fa03d98 8171a324 88081fa03de0 [1871405.129440] 88081fa03dd0 810676bd 8807eeb94000 [1871405.129441] 8807ee867c80 0001 88081fa03e30 [1871405.129444] Call Trace: [1871405.129445] IRQ [8171a324] dump_stack+0x45/0x56 [1871405.129453] [810676bd]
[Kernel-packages] [Bug 1348832] [NEW] e1000e Detected Hardware Unit Hang
Public bug reported: e1000e device on a trusty router/server/etc, up for a few weeks, stopped responding and went into a Detected Hardware Unit Hang loop. At the time, the interface was under moderate load, about 60mbps inbound. [1871400.121801] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: [1871400.121801] TDH 92 [1871400.121801] TDT cf [1871400.121801] next_to_use cf [1871400.121801] next_to_clean90 [1871400.121801] buffer_info[next_to_clean]: [1871400.121801] time_stamp 11be7959f [1871400.121801] next_to_watch92 [1871400.121801] jiffies 11be79797 [1871400.121801] next_to_watch.status 0 [1871400.121801] MAC Status 80083 [1871400.121801] PHY Status 796d [1871400.121801] PHY 1000BASE-T Status 7800 [1871400.121801] PHY Extended Status3000 [1871400.121801] PCI Status 10 [1871402.120130] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: [1871402.120130] TDH 92 [1871402.120130] TDT cf [1871402.120130] next_to_use cf [1871402.120130] next_to_clean90 [1871402.120130] buffer_info[next_to_clean]: [1871402.120130] time_stamp 11be7959f [1871402.120130] next_to_watch92 [1871402.120130] jiffies 11be7998b [1871402.120130] next_to_watch.status 0 [1871402.120130] MAC Status 80083 [1871402.120130] PHY Status 796d [1871402.120130] PHY 1000BASE-T Status 7800 [1871402.120130] PHY Extended Status3000 [1871402.120130] PCI Status 10 [1871404.118513] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: [1871404.118513] TDH 92 [1871404.118513] TDT cf [1871404.118513] next_to_use cf [1871404.118513] next_to_clean90 [1871404.118513] buffer_info[next_to_clean]: [1871404.118513] time_stamp 11be7959f [1871404.118513] next_to_watch92 [1871404.118513] jiffies 11be79b7f [1871404.118513] next_to_watch.status 0 [1871404.118513] MAC Status 80083 [1871404.118513] PHY Status 796d [1871404.118513] PHY 1000BASE-T Status 7800 [1871404.118513] PHY Extended Status3000 [1871404.118513] PCI Status 10 [1871405.129366] [ cut here ] [1871405.129374] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.13.0/net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280() [1871405.129375] NETDEV WATCHDOG: eth1 (e1000e): transmit queue 0 timed out [1871405.129376] Modules linked in: ksplice_vijajns4_vmlinux_new(OF) ksplice_vijajns4(OF) ksplice_ax32i68r_vmlinux_new(OF) ksplice_ax32i68r(OF) ksplice_n4y5yx0j_vmlinux_new(OF) ksplice_n4y5yx0j(OF) nct6775(F) hwmon_vid(F) xt_nat vhost_net vhost macvtap macvlan ip6t_REJECT ipt_REJECT xt_LOG ipt_MASQUERADE xt_TCPMSS iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack xt_tcpudp ip6table_filter ip6_tables iptable_filter ip_tables x_tables sit tunnel4 ip_tunnel bridge stp llc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache jfs dm_multipath scsi_dh x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm ftdi_sio joydev usbserial parport_pc mei_me mei serio_raw ppdev acpi_pad mac_hid coretemp lp parport dm_crypt raid456 async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear hid_generic raid10 usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 i915 lrw e1000e gf128mul glue_helper ablk_helper i2c_algo_bit cryptd psmouse ahci drm_kms_helper ptp libahci pps_core video drm [last unloaded: ksplice_vijajns4_vmlinux_old] [1871405.129434] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GF O 3.13.0-30-generic #54-Ubuntu [1871405.129435] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z97 Pro3, BIOS P1.40 05/23/2014 [1871405.129436] 0009 88081fa03d98 8171a324 88081fa03de0 [1871405.129440] 88081fa03dd0 810676bd 8807eeb94000 [1871405.129441] 8807ee867c80 0001 88081fa03e30 [1871405.129444] Call Trace: [1871405.129445] IRQ [8171a324] dump_stack+0x45/0x56 [1871405.129453] [810676bd] warn_slowpath_common+0x7d/0xa0 [1871405.129455] [8106772c] warn_slowpath_fmt+0x4c/0x50 [1871405.129459] [8163f096] dev_watchdog+0x276/0x280 [1871405.129461] [8163ee20] ? dev_graft_qdisc+0x80/0x80 [1871405.129464] [81074226] call_timer_fn+0x36/0x100 [1871405.129467] [8163ee20] ? dev_graft_qdisc+0x80/0x80 [1871405.129468] [810751bf] run_timer_softirq+0x1ef/0x2f0 [1871405.129471] [8106caec] __do_softirq+0xec/0x2c0 [1871405.129475] [8106d035] irq_exit+0x105/0x110 [1871405.129478] [8172d0c5] smp_apic_timer_interrupt+0x45/0x60 [1871405.129482]
[Kernel-packages] [Bug 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration
I can confirm that 29c7787075c92ca8af353acd5301481e6f37082f applies cleanly again the latest trusty tree (3.13.0-27.50), and does indeed fix the vsftpd problem without apparent side effects. -- 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 1303657] Re: Cannot boot trusty kernel on qemu-system-arm
linux-image-3.13.0-24-generic_3.13.0-24.46~hvcdcc_armhf.deb verified as working, both directly and via u-boot, thank you. And thanks for including the DTB in the package now. I was using vexpress-v2p-ca9.dtb, but IIRC I compiled it from vanilla sometime last year. -- 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/1303657 Title: Cannot boot trusty kernel on qemu-system-arm Status in “linux” package in Ubuntu: Confirmed Bug description: == SRU Justification == Upon d-r-u of a qemu ARM guest from saucy to trusty, the kernel no longer boots: == Fix == Build the correct dtb for this board and disable the console-over-jtag or Apply the attached patches, recompile and install. == Impact == Kernel hangs at boot. == Test Case == Try booting your installation with and without those fixes. === U-Boot 2013.10 (Nov 23 2013 - 04:30:10) DRAM: 1 GiB WARNING: Caches not enabled Flash: 256 MiB MMC: MMC: 0 In:serial Out: serial Err: serial Net: smc911x-0 Hit any key to stop autoboot: 0 reading boot.scr 352 bytes read in 28 ms (11.7 KiB/s) ## Executing script at 6000 reading vmlinuz 5474584 bytes read in 958 ms (5.4 MiB/s) reading initrd.img 17883834 bytes read in 3013 ms (5.7 MiB/s) reading board.dtb 11863 bytes read in 6 ms (1.9 MiB/s) Kernel image @ 0x60008000 [ 0x00 - 0x538918 ] ## Flattened Device Tree blob at 62008000 Booting using the fdt blob at 0x62008000 Using Device Tree in place at 62008000, end 6200de56 Starting kernel ... === At this point, the host CPU just spins. The previous kernel from saucy (3.11.0-19-generic) boots correctly into the trusty environment. The VM is being launched as so: export QEMU_AUDIO_DRV=none exec qemu-system-arm -display none -M vexpress-a9 -kernel /srv/arm-dev/u-boot -m 1024 \ -serial stdio -net nic,model=lan9118,macaddr=52:54:00:68:90:14 \ -net tap,ifname=arm-dev,script=no,downscript=no -sd /dev/mapper/host-arm_dev \ -pflash /srv/arm-dev/pflash1.img -pflash /srv/arm-dev/pflash2.img -smp 1 The flash images are unused; the scr points to the SD: fatload mmc 0:1 0x60008000 vmlinuz fatload mmc 0:1 0x61008000 initrd.img fatload mmc 0:1 0x62008000 board.dtb setenv bootargs console=ttyAMA0,38400 root=/dev/mmcblk0p2 nosmp setenv fdt_high 0x setenv initrd_high 0x bootz 0x60008000 0x61008000:0x100 0x62008000 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic armv7l AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-19-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu1 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/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' CurrentDmesg: [ 113.007517] init: plymouth-upstart-bridge main process ended, respawning Date: Mon Apr 7 01:23:13 2014 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: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyAMA0,38400 root=/dev/mmcblk0p2 nosmp RelatedPackageVersions: linux-restricted-modules-3.11.0-19-generic N/A linux-backports-modules-3.11.0-19-generic N/A linux-firmware 1.127 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1303657/+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 1303657] [NEW] Cannot boot 3.13.0-23-generic from u-boot on qemu-system-arm
Public bug reported: Upon d-r-u of a qemu ARM guest from saucy to trusty, the kernel no longer boots: === U-Boot 2013.10 (Nov 23 2013 - 04:30:10) DRAM: 1 GiB WARNING: Caches not enabled Flash: 256 MiB MMC: MMC: 0 In:serial Out: serial Err: serial Net: smc911x-0 Hit any key to stop autoboot: 0 reading boot.scr 352 bytes read in 28 ms (11.7 KiB/s) ## Executing script at 6000 reading vmlinuz 5474584 bytes read in 958 ms (5.4 MiB/s) reading initrd.img 17883834 bytes read in 3013 ms (5.7 MiB/s) reading board.dtb 11863 bytes read in 6 ms (1.9 MiB/s) Kernel image @ 0x60008000 [ 0x00 - 0x538918 ] ## Flattened Device Tree blob at 62008000 Booting using the fdt blob at 0x62008000 Using Device Tree in place at 62008000, end 6200de56 Starting kernel ... === At this point, the host CPU just spins. The previous kernel from saucy (3.11.0-19-generic) boots correctly into the trusty environment. The VM is being launched as so: export QEMU_AUDIO_DRV=none exec qemu-system-arm -display none -M vexpress-a9 -kernel /srv/arm-dev/u-boot -m 1024 \ -serial stdio -net nic,model=lan9118,macaddr=52:54:00:68:90:14 \ -net tap,ifname=arm-dev,script=no,downscript=no -sd /dev/mapper/host-arm_dev \ -pflash /srv/arm-dev/pflash1.img -pflash /srv/arm-dev/pflash2.img -smp 1 The flash images are unused; the scr points to the SD: fatload mmc 0:1 0x60008000 vmlinuz fatload mmc 0:1 0x61008000 initrd.img fatload mmc 0:1 0x62008000 board.dtb setenv bootargs console=ttyAMA0,38400 root=/dev/mmcblk0p2 nosmp setenv fdt_high 0x setenv initrd_high 0x bootz 0x60008000 0x61008000:0x100 0x62008000 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic armv7l AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-19-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu1 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/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' CurrentDmesg: [ 113.007517] init: plymouth-upstart-bridge main process ended, respawning Date: Mon Apr 7 01:23:13 2014 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: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyAMA0,38400 root=/dev/mmcblk0p2 nosmp RelatedPackageVersions: linux-restricted-modules-3.11.0-19-generic N/A linux-backports-modules-3.11.0-19-generic N/A linux-firmware 1.127 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-07 (0 days ago) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf 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/1303657 Title: Cannot boot 3.13.0-23-generic from u-boot on qemu-system-arm Status in “linux” package in Ubuntu: New Bug description: Upon d-r-u of a qemu ARM guest from saucy to trusty, the kernel no longer boots: === U-Boot 2013.10 (Nov 23 2013 - 04:30:10) DRAM: 1 GiB WARNING: Caches not enabled Flash: 256 MiB MMC: MMC: 0 In:serial Out: serial Err: serial Net: smc911x-0 Hit any key to stop autoboot: 0 reading boot.scr 352 bytes read in 28 ms (11.7 KiB/s) ## Executing script at 6000 reading vmlinuz 5474584 bytes read in 958 ms (5.4 MiB/s) reading initrd.img 17883834 bytes read in 3013 ms (5.7 MiB/s) reading board.dtb 11863 bytes read in 6 ms (1.9 MiB/s) Kernel image @ 0x60008000 [ 0x00 - 0x538918 ] ## Flattened Device Tree blob at 62008000 Booting using the fdt blob at 0x62008000 Using Device Tree in place at 62008000, end 6200de56 Starting kernel ... === At this point, the host CPU just spins. The previous kernel from saucy (3.11.0-19-generic) boots correctly into the trusty environment. The VM is being launched as so: export QEMU_AUDIO_DRV=none exec qemu-system-arm -display none -M vexpress-a9 -kernel /srv/arm-dev/u-boot -m 1024 \ -serial stdio -net nic,model=lan9118,macaddr=52:54:00:68:90:14 \ -net tap,ifname=arm-dev,script=no,downscript=no -sd /dev/mapper/host-arm_dev \
[Kernel-packages] [Bug 1303657] Re: Cannot boot 3.13.0-23-generic on qemu-system-arm
Looks like the lp helper script got confused; logs were already attached from apport-bug. Overriding. BTW, I removed u-boot from the situation and tried booting 3.13.0-23-generic directly from qemu-system-arm, same result. I have not yet been able to get 3.13.0-23-generic to boot. ** Summary changed: - Cannot boot 3.13.0-23-generic from u-boot on qemu-system-arm + Cannot boot 3.13.0-23-generic on qemu-system-arm ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Tags removed: 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/1303657 Title: Cannot boot 3.13.0-23-generic on qemu-system-arm Status in “linux” package in Ubuntu: Confirmed Bug description: Upon d-r-u of a qemu ARM guest from saucy to trusty, the kernel no longer boots: === U-Boot 2013.10 (Nov 23 2013 - 04:30:10) DRAM: 1 GiB WARNING: Caches not enabled Flash: 256 MiB MMC: MMC: 0 In:serial Out: serial Err: serial Net: smc911x-0 Hit any key to stop autoboot: 0 reading boot.scr 352 bytes read in 28 ms (11.7 KiB/s) ## Executing script at 6000 reading vmlinuz 5474584 bytes read in 958 ms (5.4 MiB/s) reading initrd.img 17883834 bytes read in 3013 ms (5.7 MiB/s) reading board.dtb 11863 bytes read in 6 ms (1.9 MiB/s) Kernel image @ 0x60008000 [ 0x00 - 0x538918 ] ## Flattened Device Tree blob at 62008000 Booting using the fdt blob at 0x62008000 Using Device Tree in place at 62008000, end 6200de56 Starting kernel ... === At this point, the host CPU just spins. The previous kernel from saucy (3.11.0-19-generic) boots correctly into the trusty environment. The VM is being launched as so: export QEMU_AUDIO_DRV=none exec qemu-system-arm -display none -M vexpress-a9 -kernel /srv/arm-dev/u-boot -m 1024 \ -serial stdio -net nic,model=lan9118,macaddr=52:54:00:68:90:14 \ -net tap,ifname=arm-dev,script=no,downscript=no -sd /dev/mapper/host-arm_dev \ -pflash /srv/arm-dev/pflash1.img -pflash /srv/arm-dev/pflash2.img -smp 1 The flash images are unused; the scr points to the SD: fatload mmc 0:1 0x60008000 vmlinuz fatload mmc 0:1 0x61008000 initrd.img fatload mmc 0:1 0x62008000 board.dtb setenv bootargs console=ttyAMA0,38400 root=/dev/mmcblk0p2 nosmp setenv fdt_high 0x setenv initrd_high 0x bootz 0x60008000 0x61008000:0x100 0x62008000 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic armv7l AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-19-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu1 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/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' CurrentDmesg: [ 113.007517] init: plymouth-upstart-bridge main process ended, respawning Date: Mon Apr 7 01:23:13 2014 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: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyAMA0,38400 root=/dev/mmcblk0p2 nosmp RelatedPackageVersions: linux-restricted-modules-3.11.0-19-generic N/A linux-backports-modules-3.11.0-19-generic N/A linux-firmware 1.127 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1303657/+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 1303657] Re: Cannot boot 3.13.0-23-generic on qemu-system-arm
The only option on https://wiki.ubuntu.com/DebuggingKernelBoot of relevance to booting an ARM kernel in QEMU is the debug flag, which doesn't change anything. The u-boot output is in the original report; when booting through u-boot, it CPU spins after Starting kernel When booting the kernel directly from qemu-system-arm, there is literally no output. I don't have access to 3.13.0-22, it was a d-r-u from saucy to trusty this weekend. I was referring to the difference between the saucy kernel line (3.11) and the trusty kernel line (3.13). I'm compiling an armhf kernel from http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.14-trusty/ to test vanilla, but this is going to take a very long time. ** Summary changed: - Cannot boot 3.13.0-23-generic on qemu-system-arm + Cannot boot trusty kernel on qemu-system-arm -- 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/1303657 Title: Cannot boot trusty kernel on qemu-system-arm Status in “linux” package in Ubuntu: Confirmed Bug description: Upon d-r-u of a qemu ARM guest from saucy to trusty, the kernel no longer boots: === U-Boot 2013.10 (Nov 23 2013 - 04:30:10) DRAM: 1 GiB WARNING: Caches not enabled Flash: 256 MiB MMC: MMC: 0 In:serial Out: serial Err: serial Net: smc911x-0 Hit any key to stop autoboot: 0 reading boot.scr 352 bytes read in 28 ms (11.7 KiB/s) ## Executing script at 6000 reading vmlinuz 5474584 bytes read in 958 ms (5.4 MiB/s) reading initrd.img 17883834 bytes read in 3013 ms (5.7 MiB/s) reading board.dtb 11863 bytes read in 6 ms (1.9 MiB/s) Kernel image @ 0x60008000 [ 0x00 - 0x538918 ] ## Flattened Device Tree blob at 62008000 Booting using the fdt blob at 0x62008000 Using Device Tree in place at 62008000, end 6200de56 Starting kernel ... === At this point, the host CPU just spins. The previous kernel from saucy (3.11.0-19-generic) boots correctly into the trusty environment. The VM is being launched as so: export QEMU_AUDIO_DRV=none exec qemu-system-arm -display none -M vexpress-a9 -kernel /srv/arm-dev/u-boot -m 1024 \ -serial stdio -net nic,model=lan9118,macaddr=52:54:00:68:90:14 \ -net tap,ifname=arm-dev,script=no,downscript=no -sd /dev/mapper/host-arm_dev \ -pflash /srv/arm-dev/pflash1.img -pflash /srv/arm-dev/pflash2.img -smp 1 The flash images are unused; the scr points to the SD: fatload mmc 0:1 0x60008000 vmlinuz fatload mmc 0:1 0x61008000 initrd.img fatload mmc 0:1 0x62008000 board.dtb setenv bootargs console=ttyAMA0,38400 root=/dev/mmcblk0p2 nosmp setenv fdt_high 0x setenv initrd_high 0x bootz 0x60008000 0x61008000:0x100 0x62008000 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic armv7l AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-19-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu1 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/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' CurrentDmesg: [ 113.007517] init: plymouth-upstart-bridge main process ended, respawning Date: Mon Apr 7 01:23:13 2014 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: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyAMA0,38400 root=/dev/mmcblk0p2 nosmp RelatedPackageVersions: linux-restricted-modules-3.11.0-19-generic N/A linux-backports-modules-3.11.0-19-generic N/A linux-firmware 1.127 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1303657/+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 1303657] Re: Cannot boot trusty kernel on qemu-system-arm
FWIW, I was not able to compile the armhf package from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/: CC [M] drivers/gpu/drm/msm/msm_drv.o CC [M] drivers/gpu/drm/msm/msm_fb.o CC [M] drivers/gpu/drm/msm/msm_gem.o CC [M] drivers/gpu/drm/msm/msm_gem_prime.o CC [M] drivers/gpu/drm/msm/msm_gem_submit.o CC [M] drivers/gpu/drm/msm/msm_gpu.o CC [M] drivers/gpu/drm/msm/msm_iommu.o CC [M] drivers/gpu/drm/msm/msm_ringbuffer.o CC [M] drivers/gpu/drm/msm/msm_fbdev.o LD [M] drivers/gpu/drm/msm/msm.o drivers/gpu/drm/msm/hdmi/hdmi.o: In function `.LANCHOR2': hdmi.c:(.rodata+0x10): multiple definition of `__mod_of_device_table' drivers/gpu/drm/msm/adreno/a3xx_gpu.o:a3xx_gpu.c:(.rodata+0x4e8): first defined here drivers/gpu/drm/msm/msm_drv.o: In function `.LANCHOR0': msm_drv.c:(.rodata+0x20c): multiple definition of `__mod_of_device_table' drivers/gpu/drm/msm/adreno/a3xx_gpu.o:a3xx_gpu.c:(.rodata+0x4e8): first defined here make[6]: *** [drivers/gpu/drm/msm/msm.o] Error 1 make[5]: *** [drivers/gpu/drm/msm] Error 2 make[4]: *** [drivers/gpu/drm] Error 2 make[3]: *** [drivers/gpu] Error 2 make[2]: *** [drivers] Error 2 make[1]: *** [sub-make] Error 2 make[1]: Leaving directory `/home/ryan/v3.14-trusty/linux-3.14' make: *** [/home/ryan/v3.14-trusty/linux-3.14/debian/stamps/stamp-build-generic] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 debuild: fatal error at line 1364: dpkg-buildpackage -rfakeroot -D -us -uc failed real447m6.844s user385m56.960s sys 36m20.700s -- 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/1303657 Title: Cannot boot trusty kernel on qemu-system-arm Status in “linux” package in Ubuntu: Confirmed Bug description: Upon d-r-u of a qemu ARM guest from saucy to trusty, the kernel no longer boots: === U-Boot 2013.10 (Nov 23 2013 - 04:30:10) DRAM: 1 GiB WARNING: Caches not enabled Flash: 256 MiB MMC: MMC: 0 In:serial Out: serial Err: serial Net: smc911x-0 Hit any key to stop autoboot: 0 reading boot.scr 352 bytes read in 28 ms (11.7 KiB/s) ## Executing script at 6000 reading vmlinuz 5474584 bytes read in 958 ms (5.4 MiB/s) reading initrd.img 17883834 bytes read in 3013 ms (5.7 MiB/s) reading board.dtb 11863 bytes read in 6 ms (1.9 MiB/s) Kernel image @ 0x60008000 [ 0x00 - 0x538918 ] ## Flattened Device Tree blob at 62008000 Booting using the fdt blob at 0x62008000 Using Device Tree in place at 62008000, end 6200de56 Starting kernel ... === At this point, the host CPU just spins. The previous kernel from saucy (3.11.0-19-generic) boots correctly into the trusty environment. The VM is being launched as so: export QEMU_AUDIO_DRV=none exec qemu-system-arm -display none -M vexpress-a9 -kernel /srv/arm-dev/u-boot -m 1024 \ -serial stdio -net nic,model=lan9118,macaddr=52:54:00:68:90:14 \ -net tap,ifname=arm-dev,script=no,downscript=no -sd /dev/mapper/host-arm_dev \ -pflash /srv/arm-dev/pflash1.img -pflash /srv/arm-dev/pflash2.img -smp 1 The flash images are unused; the scr points to the SD: fatload mmc 0:1 0x60008000 vmlinuz fatload mmc 0:1 0x61008000 initrd.img fatload mmc 0:1 0x62008000 board.dtb setenv bootargs console=ttyAMA0,38400 root=/dev/mmcblk0p2 nosmp setenv fdt_high 0x setenv initrd_high 0x bootz 0x60008000 0x61008000:0x100 0x62008000 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic armv7l AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-19-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu1 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/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' CurrentDmesg: [ 113.007517] init: plymouth-upstart-bridge main process ended, respawning Date: Mon Apr 7 01:23:13 2014 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: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyAMA0,38400 root=/dev/mmcblk0p2 nosmp RelatedPackageVersions:
