[mpt3sas, UBSAN] 6.5-rc won't boot

Koba Ko koba.ko at canonical.com
Thu Jul 27 08:06:29 UTC 2023


Hi Sune
You could use a bootable kernel then journalctl to dump the dmesg

# dump last  dmesg
#sudo journalctl -k -b -1

On Thu, Jul 27, 2023, 3:52 PM Sune Mølgaard <sune at molgaard.org> wrote:

> Hi Koba,
>
> Thank you for looking into this!
>
> I just filed
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028830, but with a
> photo of the screen, since I don't know of any way to get dmesg output
> of a non-booting system.
>
> After grub, that photo is what happens, and the boot process doesn't
> progress except for repetitions of the statement that udev couldn't start.
>
> /sune
>
> On 27/07/2023 03.49, Koba Ko wrote:
> > hi Sune,
> > Could you file a bug on launchpad? and upload the dmesg with ubsan
> complaints.
> > I will discuss it with author and find a solution.
> >
> > Thanks
> > Koba Ko
> >
> > On Thu, Jul 27, 2023 at 12:07 AM Sune Mølgaard <sune at molgaard.org>
> wrote:
> >> Hi Koba,
> >>
> >> Thank you for clarifying.
> >>
> >> It now only reports the MPI2_SAS_IO_UNIT0_PHY_DATA [1] parts, i.e. the
> >> MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1] are no longer displayed.
> >>
> >> The MPI2_SAS_IO_UNIT0_PHY_DATA [1] parts displayed are the same as
> >> before, displayed in the exact same way.
> >>
> >> /sune
> >>
> >> On 26/07/2023 13.37, Koba Ko wrote:
> >>> Hi Sune,
> >>> I applied the old config but it's latest vanilla kernel, 6.5rc3
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/kernel-team/attachments/20230727/df00e0f1/attachment.html>


More information about the kernel-team mailing list