[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: kernel errors



sorry, replied to wrong list.

On Fri, 03 Feb 2023 16:55:18 -0500,
John Covici wrote:
> 
> For instance I just got a post from Freedom Scientific which had the
> announcement in the Email and also link to the post.
> On Fri, 03 Feb 2023 15:28:55 -0500,
> David Wright wrote:
> > 
> > On Fri 03 Feb 2023 at 13:12:05 (+0000), Richmond wrote:
> > > David Wright <deblis@lionunicorn.co.uk> writes:
> > > > On Thu 02 Feb 2023 at 21:58:54 (+0000), Richmond wrote:
> > > >> "Thomas Schmitt" <scdbackup@gmx.net> writes:
> > > >> >
> > > >> > (If not there, then in the /scripts/local-block directory of the initrd ?)
> > > >> 
> > > >> I don't know how I would look in that. Is it in RAM at boot time?
> > > >
> > > >        Choose your kernel ↓↓↓↓↓↓↓↓↓↓    Pick any name ↓↓↓↓↓↓↓↓
> > > >
> > > > $ unmkinitramfs /boot/initrd.img-5.10.0-21-amd64 /tmp/initrd21
> > > > cpio: etc/console-setup/null: Cannot mknod: Operation not permitted
> > > > $ ls -GlgR /tmp/initrd21/main/scripts/
> > > > /tmp/initrd21/main/scripts/:
> > > > total 48
> > > > -rw-r--r-- 1 11152 Jan 14  2021 functions
> > > > drwxr-xr-x 2  4096 Feb  2 18:45 init-bottom
> > > > drwxr-xr-x 2  4096 Feb  2 18:45 init-top
> > > > -rw-r--r-- 1  5303 Jan 14  2021 local
> > > > drwxr-xr-x 2  4096 Feb  2 18:45 local-block
> > > > drwxr-xr-x 2  4096 Feb  2 18:45 local-bottom
> > > > drwxr-xr-x 2  4096 Feb  2 18:45 local-premount
> > > > drwxr-xr-x 2  4096 Feb  2 18:45 local-top
> > > > -rw-r--r-- 1  3093 Jan 14  2021 nfs
> > > >
> > > > /tmp/initrd21/main/scripts/init-bottom:
> > > > total 8
> > > > -rw-r--r-- 1  77 Jan 23 21:46 ORDER
> > > > -rwxr-xr-x 1 611 Aug  7 08:25 udev
> > > >
> > > > /tmp/initrd21/main/scripts/init-top:
> > > > total 20
> > > > -rw-r--r-- 1 314 Jan 23 21:46 ORDER
> > > > -rwxr-xr-x 1 384 Jan 14  2021 all_generic_ide
> > > > -rwxr-xr-x 1 296 Jan 14  2021 blacklist
> > > > -rwxr-xr-x 1 167 Jan 14  2021 keymap
> > > > -rwxr-xr-x 1 568 Aug  7 08:25 udev
> > > >
> > > > /tmp/initrd21/main/scripts/local-block:
> > > > total 8
> > > > -rw-r--r-- 1  82 Jan 23 21:46 ORDER
> > > > -rwxr-xr-x 1 246 Feb  1  2022 cryptroot
> > > >
> > > > /tmp/initrd21/main/scripts/local-bottom:
> > > > total 20
> > > > -rw-r--r-- 1 336 Jan 23 21:46 ORDER
> > > > -rwxr-xr-x 1 253 Feb  1  2022 cryptgnupg-sc
> > > > -rwxr-xr-x 1 449 Feb  1  2022 cryptopensc
> > > > -rwxr-xr-x 1 307 Feb  1  2022 cryptroot
> > > > -rwxr-xr-x 1 345 Nov  2 16:46 ntfs_3g
> > > >
> > > > /tmp/initrd21/main/scripts/local-premount:
> > > > total 12
> > > > -rw-r--r-- 1 165 Jan 23 21:46 ORDER
> > > > -rwxr-xr-x 1 226 Nov  2 16:46 ntfs_3g
> > > > -rwxr-xr-x 1 863 Jan 14  2021 resume
> > > >
> > > > /tmp/initrd21/main/scripts/local-top:
> > > > total 20
> > > > -rw-r--r-- 1  162 Jan 23 21:46 ORDER
> > > > -rwxr-xr-x 1  757 Feb  1  2022 cryptopensc
> > > > -rwxr-xr-x 1 8630 Feb  1  2022 cryptroot
> > > > $ 
> > > >
> > > > This is a desktop with random-key swap, so no resume.
> > > > There are encrypted partitions present. YMMV.
> > > >
> > > > Cheers,
> > > > David.
> > > 
> > > ~$ unmkinitramfs /boot/initrd.img-5.10.0-21-amd64 /tmp/initrd21
> > > ~$ find /tmp/initrd21/ -print|grep "local-block"
> > > ~$ find /tmp/initrd21/ -print|grep "local"
> > > 
> > > /tmp/initrd21/usr/local
> > > /tmp/initrd21/usr/local/share
> > > /tmp/initrd21/usr/local/share/fonts
> > > /tmp/initrd21/usr/local/share/fonts/.uuid
> > > /tmp/initrd21/scripts/local-bottom
> > > /tmp/initrd21/scripts/local-bottom/ntfs_3g
> > > /tmp/initrd21/scripts/local-bottom/ORDER
> > > /tmp/initrd21/scripts/local
> > > /tmp/initrd21/scripts/local-premount
> > > /tmp/initrd21/scripts/local-premount/ntfs_3g
> > > /tmp/initrd21/scripts/local-premount/ORDER
> > > /tmp/initrd21/scripts/local-premount/resume
> > > 
> > > No local block. :-?
> > > 
> > > find /tmp/initrd21/ -print|grep local|grep block
> > > 
> > > No output here.
> > 
> > Well, no, but there is a resume sitting there in local-premount,
> > which suggests to me¹ that you perhaps have something in
> > /etc/initramfs-tools/conf.d/resume. Has that been reported?
> > 
> > I'd also be interested to see the output from:
> > 
> > $ ls -lR /dev/disk | grep sr
> > 
> > and
> > 
> > $ grep -e sr -e sw /etc/fstab
> > 
> > The intent of that last pattern is to see the swap lines that you
> > have been commenting out.
> > 
> > Of course, we might not see anything unusual anywhere while the
> > machines are in their "fixed" state (whatever that means).
> > 
> > ¹ This is a guess, based on the fact that I also have that file in
> >   initrd, and I have RESUME=none in /etc/initramfs-tools/conf.d/resume,
> >   and something somewhere has to read the word "none".
> > 
> > Cheers,
> > David.
> > 
> 
> -- 
> Your life is like a penny.  You're going to lose it.  The question is:
> How do
> you spend it?
> 
>          John Covici wb2una
>          covici@ccs.covici.com
> 

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici wb2una
         covici@ccs.covici.com

Reply to: