public inbox for kernelnewbies@kernelnewbies.org
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Ozgur Karatas <ozgurk@ieee.org>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: System does not start with kernel from staging-testing pulled 3hours ago
Date: Fri, 15 Apr 2022 14:47:36 +0200	[thread overview]
Message-ID: <0a063a91-7bf5-4154-3afa-db3b38b1b8d7@gmail.com> (raw)
In-Reply-To: <CAADfD8wa=cMsM=Qkjq_8-2nrtuY3Pnx9=h6V-rjFSAVbhRqJJA@mail.gmail.com>

On 4/15/22 13:02, Ozgur Karatas wrote:
> 
> 
> On Fri, Apr 15, 2022 at 2:23 PM Philipp Hortmann 
> <philipp.g.hortmann@gmail.com <mailto:philipp.g.hortmann@gmail.com>> wrote:
> 
>     Hi,
> 
>     i have switched this morning from 5.18.0-rc1 to 5.18.0-rc2
> 
>     But with 5.18.0-rc2 (Pulled today 15.04.2022) my computer does not
>     start
>     anymore
>     It stops approxemately at 1.7 seconds
> 
>     here the last log captured on the screen:
>     ...
>     Begin: Waiting for suspend/resume device ... Begin: Running
>     /scripts/local-block ... done
>     done.
>     Gave up waiting for suspend/resume device
>     done.
>     Begin: Waiting for root file system ... Begin: Running
>     /scripts/local-block ... done
>     Gave up waiting for root file system device. Common problems:
>     - Boot args (cat /proc/cmdline)
>              - Check rootdelay= (did the system wait long enough?)
>     - Missing modules (cat /proc/modules: is /dev)
>     ALERT! UUID= .... does not exist. Dropping to a shell!
> 
> 
>     BusyBox v1.30.1 (Ubuntu ........
>     (initramfs)
> 
>     here the version that works:
>     Linux matrix-ESPRIMO-P710 5.18.0-rc1+ #1 SMP PREEMPT_DYNAMIC Sat Apr 9
>     09:13:53 CEST 2022 x86_64 x86_64 x86_64 GNU/Linux
> 
>     I am on branch staging-testing
> 
>     Do I have to change my settings? Or is this caused by a kernel bug?
> 
> 
> Hello,
> 
> I dont think this is a kernel bug. it seems related to VFS structure and 
> filesystem so which filesystem were you using?
> Are your mount points correct? Please check your /etc/fstab file while 
> on busybox maybe you can see the volumes for which you know the UUID by 
> mounting a test.
> 
> Filesystem is use UUID identify and blkid command show all UUID.
> 
> Regards
> 
>     Thanks for your support.
> 
>     Bye Philipp
> 
>     _______________________________________________
>     Kernelnewbies mailing list
>     Kernelnewbies@kernelnewbies.org <mailto:Kernelnewbies@kernelnewbies.org>
>     https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>     <https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies>
> 

Hi,

thanks for your response.

Here some more information dumped on 5.18.0-rc1:

In the dump above the UUID was missing so here is the missing line:
ALERT! UUID= e575c8fb-4c2a-47ec-973e-4a52cdd2ebdf does not exist. 
Dropping to a shell!

cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdb2 during installation
UUID=e575c8fb-4c2a-47ec-973e-4a52cdd2ebdf /               ext4 
errors=remount-ro 0       1
# /boot/efi was on /dev/sdb1 during installation
UUID=727C-04B3  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/sdb3 during installation
UUID=f30ab35a-fffd-4531-a4d5-7d780bb8ea9a none            swap    sw 
           0       0


lsblk -o UUID,FSTYPE,PATH,MOUNTPOINT
UUID                                 FSTYPE   PATH        MOUNTPOINT
                                               /dev/sda
a7179471-fdfc-4da6-a7ba-cfbeec5e6e6b ext4     /dev/sda1
                                               /dev/sdb
727C-04B3                            vfat     /dev/sdb1   /boot/efi
e575c8fb-4c2a-47ec-973e-4a52cdd2ebdf ext4     /dev/sdb2   /
f30ab35a-fffd-4531-a4d5-7d780bb8ea9a swap     /dev/sdb3   [SWAP]
                                               /dev/sdc
DC9D-F7B4                            vfat     /dev/sdc1
                                               /dev/sdc2
60909EF2909ECE42                     ntfs     /dev/sdc3
BA665B75665B317D                     ntfs     /dev/sdc4
                                               /dev/sr0

But the question remains. What has changed from rc1 to rc2 that cause 
the hang?

Thanks

Bye Philipp



_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2022-04-15 12:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15 10:22 System does not start with kernel from staging-testing pulled 3hours ago Philipp Hortmann
2022-04-15 11:02 ` Ozgur Karatas
2022-04-15 12:47   ` Philipp Hortmann [this message]
2022-04-15 19:12     ` Philipp Hortmann
2022-04-15 19:43       ` Ozgur Karatas
2022-04-15 21:34         ` Philipp Hortmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0a063a91-7bf5-4154-3afa-db3b38b1b8d7@gmail.com \
    --to=philipp.g.hortmann@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=ozgurk@ieee.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox