[Kernel-packages] [Bug 1860659] Re: 4.15.0-1053 contains fatal nilfs2 kernel bug

2020-01-24 Thread Paul R.
** Attachment added: "linux-raspi2 4.15.0-1054 (bionic-proposed) boot log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1860659/+attachment/5322709/+files/linux-raspi2%204.15.0-1054%20%28bionic-proposed%29%20boot%20log.txt

-- 
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/1860659

Title:
  4.15.0-1053 contains fatal nilfs2 kernel bug

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Bionic:
  New

Bug description:
  The Bionic 4.15.0-1053 kernel package contains this nilfs2 bug:
  https://marc.info/?t=15741385112

  and it specifically concerns this nilfs2 commit for 5.3 which was apparently 
backported:
  https://marc.info/?l=linux-nilfs&m=157423529924889&w=2

  My RPi 2B boots fine from nilfs2 on kernel 4.15.0-1052, but kernel
  -1053 oopses consistently and reproducibly, with exactly the same
  "nilfs_segctor_do_construct" pattern as in the above bug report.

  Reverting to -1052 results in a working, bootable system again.

  The -1053 changelog mentions:
  "Bionic update: upstream stable patchset 2019-11-21 (LP: #1853519)"
  which I suspect is the cause.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1860659/+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 1860659] Re: 4.15.0-1053 contains fatal nilfs2 kernel bug

2020-01-24 Thread Paul R.
Hi. Yes, I get the same crash with the 4.15.0-1054.58 proposed kernel.
Log attached.

-- 
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/1860659

Title:
  4.15.0-1053 contains fatal nilfs2 kernel bug

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Bionic:
  New

Bug description:
  The Bionic 4.15.0-1053 kernel package contains this nilfs2 bug:
  https://marc.info/?t=15741385112

  and it specifically concerns this nilfs2 commit for 5.3 which was apparently 
backported:
  https://marc.info/?l=linux-nilfs&m=157423529924889&w=2

  My RPi 2B boots fine from nilfs2 on kernel 4.15.0-1052, but kernel
  -1053 oopses consistently and reproducibly, with exactly the same
  "nilfs_segctor_do_construct" pattern as in the above bug report.

  Reverting to -1052 results in a working, bootable system again.

  The -1053 changelog mentions:
  "Bionic update: upstream stable patchset 2019-11-21 (LP: #1853519)"
  which I suspect is the cause.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1860659/+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 1860659] [NEW] 4.15.0-1053 contains fatal nilfs2 kernel bug

2020-01-23 Thread Paul R.
Public bug reported:

The Bionic 4.15.0-1053 kernel package contains this nilfs2 bug:
https://marc.info/?t=15741385112

and it specifically concerns this nilfs2 commit for 5.3 which was apparently 
backported:
https://marc.info/?l=linux-nilfs&m=157423529924889&w=2

My RPi 2B boots fine from nilfs2 on kernel 4.15.0-1052, but kernel -1053
oopses consistently and reproducibly, with exactly the same
"nilfs_segctor_do_construct" pattern as in the above bug report.

Reverting to -1052 results in a working, bootable system again.

The -1053 changelog mentions:
"Bionic update: upstream stable patchset 2019-11-21 (LP: #1853519)"
which I suspect is the cause.

** Affects: linux-raspi2 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1860659

Title:
  4.15.0-1053 contains fatal nilfs2 kernel bug

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  The Bionic 4.15.0-1053 kernel package contains this nilfs2 bug:
  https://marc.info/?t=15741385112

  and it specifically concerns this nilfs2 commit for 5.3 which was apparently 
backported:
  https://marc.info/?l=linux-nilfs&m=157423529924889&w=2

  My RPi 2B boots fine from nilfs2 on kernel 4.15.0-1052, but kernel
  -1053 oopses consistently and reproducibly, with exactly the same
  "nilfs_segctor_do_construct" pattern as in the above bug report.

  Reverting to -1052 results in a working, bootable system again.

  The -1053 changelog mentions:
  "Bionic update: upstream stable patchset 2019-11-21 (LP: #1853519)"
  which I suspect is the cause.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1860659/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


Re: [Kernel-packages] [Bug 1745694] Re: System will not start after the upgrade of the kernel

2018-02-20 Thread Paul R
Yes.

On Thu, Feb 8, 2018 at 9:04 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> Does this bug go away if you boot back into the prior kernel version?
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => High
>
> ** Tags added: kernel-da-key
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1745694
>
> Title:
>   System will not start after the upgrade of the kernel
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Ubuntu 16.04 LTS (32 bit kernel)
>
>   After software updates the system will not boot with the new kernel.
>
>   Expected the system to start with the new kernel, end up with a purple
>   screen with nothing on it.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: ubuntu-release-upgrader-core 1:16.04.23
>   ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
>   Uname: Linux 4.10.0-28-generic i686
>   NonfreeKernelModules: wl
>   ApportVersion: 2.20.1-0ubuntu2.15
>   Architecture: i386
>   CrashDB: ubuntu
>   CurrentDesktop: Unity
>   Date: Fri Jan 26 15:00:52 2018
>   InstallationDate: Installed on 2018-01-26 (0 days ago)
>   InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386
> (20170801)
>   PackageArchitecture: all
>   SourcePackage: ubuntu-release-upgrader
>   Symptom: dist-upgrade
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1745694/+subscriptions
>

-- 
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/1745694

Title:
  System will not start after the upgrade of the kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 LTS (32 bit kernel)

  After software updates the system will not boot with the new kernel.

  Expected the system to start with the new kernel, end up with a purple
  screen with nothing on it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Fri Jan 26 15:00:52 2018
  InstallationDate: Installed on 2018-01-26 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745694/+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