Activity log for bug #1867916

Date Who What changed Old value New value Message
2020-03-18 12:08:02 Sebastian Marsching bug added bug
2020-03-18 12:08:02 Sebastian Marsching attachment added Screenshot of the kernel panic https://bugs.launchpad.net/bugs/1867916/+attachment/5338345/+files/IMG_3762.JPG
2020-03-18 12:30:12 Ubuntu Kernel Bot linux (Ubuntu): status New Confirmed
2020-03-30 14:21:43 Mauricio Faria de Oliveira bug added subscriber Mauricio Faria de Oliveira
2020-04-06 14:19:39 Sebastian Marsching attachment added block device hierarchy https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5347771/+files/lp1867916.1.out
2020-04-07 14:17:11 Mauricio Faria de Oliveira linux (Ubuntu): assignee Mauricio Faria de Oliveira (mfo)
2020-04-07 14:17:14 Mauricio Faria de Oliveira linux (Ubuntu): importance Undecided Medium
2020-04-07 14:17:24 Mauricio Faria de Oliveira linux (Ubuntu): status Confirmed In Progress
2020-04-08 04:21:12 Ryan Finnie bug added subscriber Ryan Finnie
2020-04-08 19:46:20 Ryan Finnie attachment added dmesg.202004081903 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5349895/+files/dmesg.202004081903
2020-04-09 11:32:09 Dr. Jens Harbott bug added subscriber Dr. Jens Harbott
2020-04-09 23:21:25 Mauricio Faria de Oliveira tags amd64 apport-bug bionic amd64 apport-bug bionic seg
2020-04-12 20:39:32 Michael Dundas bug added subscriber Michael Dundas
2020-05-21 02:33:31 Ryan Finnie bug watch added https://bugzilla.kernel.org/show_bug.cgi?id=207811
2020-05-21 02:33:31 Ryan Finnie bug task added linux
2020-05-29 22:35:30 Ryan Finnie attachment added lp1867916-queue_block_size https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5378588/+files/lp1867916-queue_block_size
2020-05-29 22:35:49 Ryan Finnie attachment added lp1867916-bcache-super-show.sd https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5378589/+files/lp1867916-bcache-super-show.sd
2020-05-29 22:36:08 Ryan Finnie attachment added lp1867916-bcache-super-show.md https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5378590/+files/lp1867916-bcache-super-show.md
2020-05-30 18:44:53 Ryan Finnie attachment added lp1867916-lsblk https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5378817/+files/lp1867916-lsblk
2020-06-02 12:10:22 Bug Watch Updater linux: status Unknown Confirmed
2020-06-02 12:10:22 Bug Watch Updater linux: importance Unknown Medium
2020-06-02 16:56:20 Sebastian Marsching attachment added lp1867916-queue_block_size.seb https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5379837/+files/lp1867916-queue_block_size.seb
2020-07-07 15:24:14 Mauricio Faria de Oliveira nominated for series Ubuntu Focal
2020-07-07 15:24:14 Mauricio Faria de Oliveira bug task added linux (Ubuntu Focal)
2020-07-07 15:24:14 Mauricio Faria de Oliveira nominated for series Ubuntu Bionic
2020-07-07 15:24:14 Mauricio Faria de Oliveira bug task added linux (Ubuntu Bionic)
2020-07-07 15:24:14 Mauricio Faria de Oliveira nominated for series Ubuntu Xenial
2020-07-07 15:24:14 Mauricio Faria de Oliveira bug task added linux (Ubuntu Xenial)
2020-07-07 15:24:14 Mauricio Faria de Oliveira nominated for series Ubuntu Groovy
2020-07-07 15:24:14 Mauricio Faria de Oliveira bug task added linux (Ubuntu Groovy)
2020-07-07 15:24:14 Mauricio Faria de Oliveira nominated for series Ubuntu Eoan
2020-07-07 15:24:14 Mauricio Faria de Oliveira bug task added linux (Ubuntu Eoan)
2020-07-07 15:24:23 Mauricio Faria de Oliveira linux (Ubuntu Xenial): status New In Progress
2020-07-07 15:24:29 Mauricio Faria de Oliveira linux (Ubuntu Xenial): importance Undecided Medium
2020-07-07 15:24:32 Mauricio Faria de Oliveira linux (Ubuntu Xenial): assignee Mauricio Faria de Oliveira (mfo)
2020-07-07 15:24:37 Mauricio Faria de Oliveira linux (Ubuntu Bionic): status New In Progress
2020-07-07 15:24:39 Mauricio Faria de Oliveira linux (Ubuntu Bionic): importance Undecided Medium
2020-07-07 15:24:42 Mauricio Faria de Oliveira linux (Ubuntu Bionic): assignee Mauricio Faria de Oliveira (mfo)
2020-07-07 15:25:06 Mauricio Faria de Oliveira linux (Ubuntu Eoan): status New In Progress
2020-07-07 15:25:09 Mauricio Faria de Oliveira linux (Ubuntu Eoan): importance Undecided Medium
2020-07-07 15:25:12 Mauricio Faria de Oliveira linux (Ubuntu Eoan): assignee Mauricio Faria de Oliveira (mfo)
2020-07-07 15:25:14 Mauricio Faria de Oliveira linux (Ubuntu Focal): status New In Progress
2020-07-07 15:25:17 Mauricio Faria de Oliveira linux (Ubuntu Focal): importance Undecided Medium
2020-07-07 15:25:22 Mauricio Faria de Oliveira linux (Ubuntu Focal): assignee Mauricio Faria de Oliveira (mfo)
2020-07-07 15:25:29 Mauricio Faria de Oliveira linux (Ubuntu Groovy): status In Progress Won't Fix
2020-07-07 15:25:33 Mauricio Faria de Oliveira linux (Ubuntu Groovy): importance Medium Undecided
2020-07-07 15:25:36 Mauricio Faria de Oliveira linux (Ubuntu Groovy): assignee Mauricio Faria de Oliveira (mfo)
2020-07-07 15:25:52 Mauricio Faria de Oliveira linux (Ubuntu): status In Progress Fix Committed
2020-07-07 15:26:22 Mauricio Faria de Oliveira 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 [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 #. [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:  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
2020-07-07 15:27:58 Mauricio Faria de Oliveira 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 #. [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:  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 [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:  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
2020-07-22 07:01:38 Kelsey Steele linux (Ubuntu Eoan): status In Progress Fix Committed
2020-07-22 07:01:56 Kelsey Steele linux (Ubuntu Xenial): status In Progress Fix Committed
2020-07-22 11:32:15 Ubuntu Kernel Bot tags amd64 apport-bug bionic seg amd64 apport-bug bionic seg verification-needed-xenial
2020-07-29 16:32:02 Mauricio Faria de Oliveira tags amd64 apport-bug bionic seg verification-needed-xenial amd64 apport-bug bionic seg verification-done-xenial
2020-08-01 18:41:50 Ubuntu Kernel Bot tags amd64 apport-bug bionic seg verification-done-xenial amd64 apport-bug bionic seg verification-done-xenial verification-needed-bionic
2020-08-03 20:17:54 Kelsey Steele linux (Ubuntu Bionic): status In Progress Fix Committed
2020-08-03 20:17:57 Kelsey Steele linux (Ubuntu Focal): status In Progress Fix Committed
2020-08-10 14:17:12 Ubuntu Kernel Bot tags amd64 apport-bug bionic seg verification-done-xenial verification-needed-bionic amd64 apport-bug bionic seg verification-done-xenial verification-needed-bionic verification-needed-focal
2020-08-12 08:04:28 Mauricio Faria de Oliveira tags amd64 apport-bug bionic seg verification-done-xenial verification-needed-bionic verification-needed-focal amd64 apport-bug bionic seg verification-done-bionic verification-done-xenial verification-needed-focal
2020-08-12 08:16:26 Mauricio Faria de Oliveira tags amd64 apport-bug bionic seg verification-done-bionic verification-done-xenial verification-needed-focal amd64 apport-bug bionic seg verification-done-bionic verification-done-focal verification-done-xenial
2020-08-13 20:23:41 Launchpad Janitor linux (Ubuntu Xenial): status Fix Committed Fix Released
2020-08-18 16:59:47 Brian Murray linux (Ubuntu Eoan): status Fix Committed Won't Fix
2020-08-31 13:57:07 Launchpad Janitor linux (Ubuntu Focal): status Fix Committed Fix Released
2020-09-01 10:15:06 Launchpad Janitor linux (Ubuntu Bionic): status Fix Committed Fix Released
2020-09-01 12:42:45 Mauricio Faria de Oliveira linux (Ubuntu): status Fix Committed Fix Released
2020-09-01 12:43:06 Mauricio Faria de Oliveira linux (Ubuntu Groovy): status Won't Fix Fix Released
2021-11-19 18:43:16 Ryan Finnie removed subscriber Ryan Finnie