after last OS uptate system will not boot normaly.

[Brian Baugus]

will not boot to, Ubuntu, with Linux 6.5.0-34 generic but will boot into Linux 6.5.0-28 generic if forced. I have never had an issue before with OS updates.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: brian 5016 F.... pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-12-30 (499 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
IwConfig:
 lo no wireless extensions.

 eno1 no wireless extensions.

 pan1 no wireless extensions.
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic root=UUID=b7f11165-0646-439f-a6b3-878c0626a8c0 ro quiet splash
ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-28-generic N/A
 linux-backports-modules-6.5.0-28-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.31
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: wayland-session jammy
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/07/2013
dmi.bios.release: 4.6
dmi.bios.vendor: Intel Corp.
dmi.bios.version: ENB7510H.86A.0045.2013.0307.1509
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DB75EN
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG39650-400
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrENB7510H.86A.0045.2013.0307.1509:bd03/07/2013:br4.6:svn:pn:pvr:rvnIntelCorporation:rnDB75EN:rvrAAG39650-400:cvn:ct3:cvr:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.sku: To be filled by O.E.M.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: brian 5016 F.... pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-12-30 (499 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
IwConfig:
 lo no wireless extensions.

 eno1 no wireless extensions.

 pan1 no wireless extensions.
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic root=UUID=b7f11165-0646-439f-a6b3-878c0626a8c0 ro quiet splash
ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-28-generic N/A
 linux-backports-modules-6.5.0-28-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.31
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: wayland-session jammy
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/07/2013
dmi.bios.release: 4.6
dmi.bios.vendor: Intel Corp.
dmi.bios.version: ENB7510H.86A.0045.2013.0307.1509
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DB75EN
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG39650-400
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrENB7510H.86A.0045.2013.0307.1509:bd03/07/2013:br4.6:svn:pn:pvr:rvnIntelCorporation:rnDB75EN:rvrAAG39650-400:cvn:ct3:cvr:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.sku: To be filled by O.E.M.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2063893/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[lotuspsychje (lotuspsychje)]

Thank you for filing this bug and make Ubuntu better!

In order to pull in your logs and system info

please execute; apport-collect 2063893 from a terminal

so the developers can debug your bug a better way.

In the future please use ubuntu-bug linux (kernel in this case) from a terminal to file a bug

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sni (sni.)]

Hello, I have the same or similar problem, after a dist-upgrade and subsequent reboot, my server ran into a kernel panic (sync init). I have the problem with the linux-6.5.0-34-generic kernel, the linux-6.5.0-28-generic and all previous ones work fine.

Since the kernel does not seem to mount the root volume, there are no logs.

[Brian Baugus (baugus80)]

Sounds exactly the same as I am haveing.

On Sat, Apr 27, 2024 at 11:45 AM Sni <email address hidden> wrote:

> Hello, I have the same or similar problem, after a dist-upgrade and
> subsequent reboot, my server ran into a kernel panic (sync init). I have
> the problem with the linux-6.5.0-34-generic kernel, the
> linux-6.5.0-28-generic and all previous ones work fine.
>
> Since the kernel does not seem to mount the root volume, there are no
> logs.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2063893
>
> Title:
> after last OS uptate system will not boot normaly.
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> will not boot to, Ubuntu, with Linux 6.5.0-34 generic but will boot
> into Linux 6.5.0-28 generic if forced. I have never had an issue
> before with OS updates.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063893/+subscriptions
>
>

[Brian Baugus (baugus80)]

Is there a resolve for this issue as yet? If so please let me know, it's a
pain at restarts and i'm fearful of doing more updates.

On Wed, May 1, 2024 at 5:35 AM Brian Baugus <email address hidden> wrote:

> Sounds exactly the same as I am haveing.
>
> On Sat, Apr 27, 2024 at 11:45 AM Sni <email address hidden> wrote:
>
>> Hello, I have the same or similar problem, after a dist-upgrade and
>> subsequent reboot, my server ran into a kernel panic (sync init). I have
>> the problem with the linux-6.5.0-34-generic kernel, the
>> linux-6.5.0-28-generic and all previous ones work fine.
>>
>> Since the kernel does not seem to mount the root volume, there are no
>> logs.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/2063893
>>
>> Title:
>> after last OS uptate system will not boot normaly.
>>
>> Status in linux package in Ubuntu:
>> Confirmed
>>
>> Bug description:
>> will not boot to, Ubuntu, with Linux 6.5.0-34 generic but will boot
>> into Linux 6.5.0-28 generic if forced. I have never had an issue
>> before with OS updates.
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063893/+subscriptions
>>
>>

[Werner Habel (werner-habel)]

when will this at least be assigned?
It is a severe issue that cold break future distribution upgrades for affected users.

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Brian Baugus (baugus80)]

apport information

[Hartmut Manz (hartmut-manz)]

with the new kernel update 6.5.0-35 this problem is fixed for me.

[Sni (sni.)]

seems that it was also fixed for me with the new version (linux-6.5.0-35-generic).