Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #79761 > unrolled thread

Bug#1042068: linux-image-6.4.0-1-amd64 boot kernel panic

Started byTerrance Hendrik <terrance.hendrik@gmail.com>
First post2023-07-26 05:10 +0200
Last post2023-07-26 17:20 +0200
Articles 4 — 3 participants

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1042068: linux-image-6.4.0-1-amd64 boot kernel panic Terrance Hendrik <terrance.hendrik@gmail.com> - 2023-07-26 05:10 +0200
    Bug#1042068: linux-image-6.4.0-1-amd64 boot kernel panic Ben Hutchings <ben@decadent.org.uk> - 2023-07-26 17:20 +0200
      Bug#1042068: linux-image-6.4.0-1-amd64 boot kernel panic Terrance Hendrik <terrance.hendrik@gmail.com> - 2023-07-28 04:40 +0200
    Processed: Re: Bug#1042068: linux-image-6.4.0-1-amd64 boot kernel  panic "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-07-26 17:20 +0200

#79761 — Bug#1042068: linux-image-6.4.0-1-amd64 boot kernel panic

FromTerrance Hendrik <terrance.hendrik@gmail.com>
Date2023-07-26 05:10 +0200
SubjectBug#1042068: linux-image-6.4.0-1-amd64 boot kernel panic
Message-ID<GVD4t-2On4-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Package: linux-image-6.4.0-1-amd64
Version: 6.4.4-1
system info:

```
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux trixie/sid
Release:        n/a
Codename:       trixie
$ lscpu
Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         39 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  20
  On-line CPU(s) list:   0-19
Vendor ID:               GenuineIntel
  Model name:            12th Gen Intel(R) Core(TM) i7-12700H
...
```

Root FS is **btrfs**


Boot log (photo OCR, unable to save log, might have some errors)

```

[0.625362] Key type .fscrypt registered

[0.625379] Key type fscrypt-provisioning registered

[9.626122] Key type encrypted registered

[0.626142] AppArmor: AppArmor shal policy hashing enabled

[0.626493] integrity: Loading X.509 certificate: UEFI:b

[0.626527] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA
2011: 13adb43096d82709cBcd54f316ed522988a1bd4'

[0.626571] integrity: Loading X.509 certificate: UEF1: db

[0.626602] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA
2011: a92902398e16c4977Bcd90 f99e4f9ae17c55af53'

[0.627200] ima: Allocated hash algorithm: sha256

[0.646056] ima: No architecture policies found[

[0.647855] evm: Initialising EVM extended attributes:

[0.649888] evm: security. selinux

[0.651351] evm: security. SMACK64 (disabled)

[0.652752] evm: security. SMACK64EXEC (disabled)

[0.653931] evm: security. SMACK64TRANSMUTE (disabled)

[0.655031] evm: security. SMACK64MMAP (disabled)

[0.656067] evm: security. apparmor

[0.657873] evm: security. ima

[0.658026] evm: security.capability

[0.658966] evm: HMAC attrs: Bx1

[0.703120] clk: Disabling unused clocks

[0.704503] List of all partitions:

[0.705638] No filesystem could mount root, tried:

[8.705639]

[0.707504] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)

[0.708458] CPU: 6 PID: 1 Comm: swapper/0 Not tainted 6.4.0-1-amd64 #1
Debian 6.4.4-1

[8.709396] Harduare name: MECHREVO WUJIE16 Pro/WUJIE16 Pro. BIOS Q3ANWJ.16
12/09/2022

[0.710369] Call Trace:

[0.711305] <TASK>

[0.712215] dump_stack_1v1+0×47/0×60

[0.713148] panic+0x17f/0×330

[0.714067] mount_block_root+0×21f/0x2b@

[0.714981] prepare_namespace+Oxf0/0×170

[8.715888] kernel_init_freeable+Bx417/8×470

[0.716782] ?__pfx_kernel_init+B×10/B×10

[0.717637] kernel_init+Bxla/Bx1cl

[0.718583] ret_from_fork+Bx29/0×50

[0.719387] </TASK>

[0.720391] Kernel Offset: Bx37000000 from Oxffffffff81000000 (relocation
range: Bxffffffff80000000-0xffffffffbfffffff)

[0.721331]---[ end Kernel panic - not syncing: FS: Unable to mount root fs
on unknown-black(0,0) ]--

```

Thanks!

[toc] | [next] | [standalone]

#79767

FromBen Hutchings <ben@decadent.org.uk>
Date2023-07-26 17:20 +0200
Message-ID<GVOsV-2VHO-9@gated-at.bofh.it>
In reply to#79761

[Multipart message — attachments visible in raw view] — view raw

Control: reassign -1 src:linux 6.4.4-1
Control: tag -1 moreinfo

On Wed, 2023-07-26 at 10:59 +0800, Terrance Hendrik wrote:
> Package: linux-image-6.4.0-1-amd64
> Version: 6.4.4-1
> system info:
> 
> ```
> $ lsb_release -a
> No LSB modules are available.
> Distributor ID: Debian
> Description:    Debian GNU/Linux trixie/sid
> Release:        n/a
> Codename:       trixie
> $ lscpu
> Architecture:            x86_64
>   CPU op-mode(s):        32-bit, 64-bit
>   Address sizes:         39 bits physical, 48 bits virtual
>   Byte Order:            Little Endian
> CPU(s):                  20
>   On-line CPU(s) list:   0-19
> Vendor ID:               GenuineIntel
>   Model name:            12th Gen Intel(R) Core(TM) i7-12700H
> ...
> ```
> 
> Root FS is **btrfs**
> 
> 
> Boot log (photo OCR, unable to save log, might have some errors)
[...]
> [0.704503] List of all partitions:
> 
> [0.705638] No filesystem could mount root, tried:
[...]

It seems that your boot loader tried to boot this kernel without an
initramfs.

- Which boot loader are you using?
- Does /boot/initrd.img-6.4.0-1-amd64 exist?
- Does "dpkg --configure -a" do anything or show any errors?

Ben.

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug

[toc] | [prev] | [next] | [standalone]

#79788

FromTerrance Hendrik <terrance.hendrik@gmail.com>
Date2023-07-28 04:40 +0200
Message-ID<GWlyx-3gVZ-3@gated-at.bofh.it>
In reply to#79767

[Multipart message — attachments visible in raw view] — view raw

- Which boot loader are you using?

grub-common                                    2.06-13
         amd64
grub-efi                                       2.06-13
         amd64
grub-efi-amd64                                 2.06-13
         amd64
grub-efi-amd64-bin                             2.06-13
         amd64
grub-efi-amd64-signed                          1+2.06+13
         amd64

- Does /boot/initrd.img-6.4.0-1-amd64 exist?

file not found

- Does "dpkg --configure -a" do anything or show any errors?

```
Failed to process /etc/kernel/header_postinst.d at
/var/lib/dpkg/info/linux-headers-6.4.0-1-amd64.postinst line 11.
dpkg: error processing package linux-headers-6.4.0-1-amd64 (--configure):
 installed linux-headers-6.4.0-1-amd64 package post-installation script
subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-headers-amd64:
 linux-headers-amd64 depends on linux-headers-6.4.0-1-amd64 (= 6.4.4-1);
however:
  Package linux-headers-6.4.0-1-amd64 is not configured yet.

dpkg: error processing package linux-headers-amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-image-amd64:
 linux-image-amd64 depends on linux-image-6.4.0-1-amd64 (= 6.4.4-1);
however:
  Package linux-image-6.4.0-1-amd64 is not configured yet.

dpkg: error processing package linux-image-amd64 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-6.4.0-1-amd64
 linux-headers-6.4.0-1-amd64
 linux-headers-amd64
 linux-image-amd64
root@<hostname> ~ # apt install linux-headers-amd64
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
linux-headers-amd64 is already the newest version (6.4.4-1).
0 upgraded, 0 newly installed, 0 to remove and 35 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
```

error configuring linux-headers-6.4.0-1-amd64

```
root@<hostname> ~ # dpkg-reconfigure --force linux-headers-6.4.0-1-amd64
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.4.0-1-amd64.
Sign command: /lib/modules/6.4.0-1-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area...
make -j20 KERNELRELEASE=6.4.0-1-amd64 -C /lib/modules/6.4.0-1-amd64/build
M=/var/lib/dkms/tp_smapi/0.43/build HDAPS=1...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.4.0-1-amd64 (x86_64)
Consult /var/lib/dkms/tp_smapi/0.43/build/make.log for more information.
Sign command: /lib/modules/6.4.0-1-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area...
make -j20 KERNELRELEASE=6.4.0-1-amd64 -C /lib/modules/6.4.0-1-amd64/build
M=/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build...(bad exit
status: 2)
Error! Bad return status for module build on kernel: 6.4.0-1-amd64 (x86_64)
Consult /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/make.log for
more information.
dkms autoinstall on 6.4.0-1-amd64/x86_64 succeeded for bbswitch
nvidia-current virtualbox
dkms autoinstall on 6.4.0-1-amd64/x86_64 failed for tp_smapi(10) xtrx(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.4.0-1-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at
/var/lib/dpkg/info/linux-headers-6.4.0-1-amd64.postinst line 11.
```

/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/make.log

```
DKMS make.log for xtrx-0.0.1+git20190320.5ae3a3e-3.3 for kernel
6.4.0-1-amd64 (x86_64)
Fri Jul 28 10:03:44 AM HKT 2023
make: Entering directory '/usr/src/linux-headers-6.4.0-1-amd64'
  CC [M]  /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/xtrx.o
In file included from
/usr/src/linux-headers-6.4.0-1-common/include/linux/linkage.h:7,
                 from
/usr/src/linux-headers-6.4.0-1-common/arch/x86/include/asm/cache.h:5,
                 from
/usr/src/linux-headers-6.4.0-1-common/include/linux/cache.h:6,
                 from
/usr/src/linux-headers-6.4.0-1-common/include/linux/time.h:5,
                 from
/usr/src/linux-headers-6.4.0-1-common/include/linux/stat.h:19,
                 from
/usr/src/linux-headers-6.4.0-1-common/include/linux/module.h:13,
                 from
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/xtrx.c:22:
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/xtrx.c: In function
‘xtrx_init’:
/usr/src/linux-headers-6.4.0-1-common/include/linux/export.h:27:22: error:
passing argument 1 of ‘class_create’ from incompatible pointer type
[-Werror=incompatible-pointer-types]
   27 | #define THIS_MODULE (&__this_module)
      |                     ~^~~~~~~~~~~~~~~
      |                      |
      |                      struct module *
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/xtrx.c:1535:35:
note: in expansion of macro ‘THIS_MODULE’
 1535 |         xtrx_class = class_create(THIS_MODULE, CLASS_NAME);
      |                                   ^~~~~~~~~~~
In file included from
/usr/src/linux-headers-6.4.0-1-common/include/linux/device.h:31,
                 from
/usr/src/linux-headers-6.4.0-1-common/include/linux/pci.h:37,
                 from
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/xtrx.c:25:
/usr/src/linux-headers-6.4.0-1-common/include/linux/device/class.h:230:54:
note: expected ‘const char *’ but argument is of type ‘struct module *’
  230 | struct class * __must_check class_create(const char *name);
      |                                          ~~~~~~~~~~~~^~~~
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/xtrx.c:1535:22:
error: too many arguments to function ‘class_create’
 1535 |         xtrx_class = class_create(THIS_MODULE, CLASS_NAME);
      |                      ^~~~~~~~~~~~
/usr/src/linux-headers-6.4.0-1-common/include/linux/device/class.h:230:29:
note: declared here
  230 | struct class * __must_check class_create(const char *name);
      |                             ^~~~~~~~~~~~
cc1: some warnings being treated as errors
make[1]: ***
[/usr/src/linux-headers-6.4.0-1-common/scripts/Makefile.build:257:
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build/xtrx.o] Error 1
make: *** [/usr/src/linux-headers-6.4.0-1-common/Makefile:2051:
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.3/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.4.0-1-amd64'
```

2 dkms modules failed to built,
xtrx/0.0.1+git20190320.5ae3a3e-3.3
tp_smapi/0.43

quick & dirty fix xtrx
1535     xtrx_class = class_create(THIS_MODULE, CLASS_NAME);
1535     xtrx_class = class_create(/*THIS_MODULE*/, CLASS_NAME);

too many errors from tp-smapi-dkms, and I dont't remember using it , so
`apt purge tp-smapi-dkms`

now /boot/initrd.img-6.4.0-1-amd64 can be built


On Wed, Jul 26, 2023 at 11:14 PM Ben Hutchings <ben@decadent.org.uk> wrote:

> Control: reassign -1 src:linux 6.4.4-1
> Control: tag -1 moreinfo
>
> On Wed, 2023-07-26 at 10:59 +0800, Terrance Hendrik wrote:
> > Package: linux-image-6.4.0-1-amd64
> > Version: 6.4.4-1
> > system info:
> >
> > ```
> > $ lsb_release -a
> > No LSB modules are available.
> > Distributor ID: Debian
> > Description:    Debian GNU/Linux trixie/sid
> > Release:        n/a
> > Codename:       trixie
> > $ lscpu
> > Architecture:            x86_64
> >   CPU op-mode(s):        32-bit, 64-bit
> >   Address sizes:         39 bits physical, 48 bits virtual
> >   Byte Order:            Little Endian
> > CPU(s):                  20
> >   On-line CPU(s) list:   0-19
> > Vendor ID:               GenuineIntel
> >   Model name:            12th Gen Intel(R) Core(TM) i7-12700H
> > ...
> > ```
> >
> > Root FS is **btrfs**
> >
> >
> > Boot log (photo OCR, unable to save log, might have some errors)
> [...]
> > [0.704503] List of all partitions:
> >
> > [0.705638] No filesystem could mount root, tried:
> [...]
>
> It seems that your boot loader tried to boot this kernel without an
> initramfs.
>
> - Which boot loader are you using?
> - Does /boot/initrd.img-6.4.0-1-amd64 exist?
> - Does "dpkg --configure -a" do anything or show any errors?
>
> Ben.
>
> --
> Ben Hutchings
> Every program is either trivial or else contains at least one bug
>
>

[toc] | [prev] | [next] | [standalone]

#79768 — Processed: Re: Bug#1042068: linux-image-6.4.0-1-amd64 boot kernel panic

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2023-07-26 17:20 +0200
SubjectProcessed: Re: Bug#1042068: linux-image-6.4.0-1-amd64 boot kernel panic
Message-ID<GVOsV-2VHO-11@gated-at.bofh.it>
In reply to#79761
Processing control commands:

> reassign -1 src:linux 6.4.4-1
Bug #1042068 [linux-image-6.4.0-1-amd64] linux-image-6.4.0-1-amd64 boot kernel panic
Bug reassigned from package 'linux-image-6.4.0-1-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/6.4.4+1.
Ignoring request to alter fixed versions of bug #1042068 to the same values previously set
Bug #1042068 [src:linux] linux-image-6.4.0-1-amd64 boot kernel panic
Marked as found in versions linux/6.4.4-1.
> tag -1 moreinfo
Bug #1042068 [src:linux] linux-image-6.4.0-1-amd64 boot kernel panic
Added tag(s) moreinfo.

-- 
1042068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042068
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web