MODSIGN: Couldn't get UEFI db list

Asked by corrado venturini on 2017-10-06

at each boot I see 3 messages:
10:39:07 kernel: Couldn't get size: 0x800000000000000e
10:39:07 kernel: MODSIGN: Couldn't get UEFI db list
10:39:07 kernel: Couldn't get size: 0x800000000000000e

the problem is already known in bugzilla:
should i open the problem on launchpad too? Or being a kernel problem i must just sit on the river and wait?

Question information

English Edit question
Ubuntu Edit question
No assignee Edit question
Last query:
Last reply:

Is this an issue in RedHat?

Manfred Hampl (m-hampl) said : #2

This may be related to Kernel v 4.12.* (or 4.13)

also reported on other distros, e.g.

Does it prevent the system from starting?

The issue is on Ubuntu 17.10
corrado@corrado-p5-0930:~$ uname -a
Linux corrado-p5-0930 4.13.0-12-generic #13-Ubuntu SMP Sat Sep 23 03:40:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

it does not prevent system from starting

so open bug or sit and wait?

Then I suggest you report a bug. Artful is not ready and not stable

Manfred Hampl (m-hampl) said : #5

There is already Bug #1719191 created by you.
In my opinion this should be enough.
Maybe a task for the kernel could be added.

a task? you mean a tag?

Manfred Hampl (m-hampl) said : #7

What I meant is "Also affects distribution/package" and select Distribution: Ubuntu - Source package name: linux

Antonis (aaantonis) said : #8

My system is a 17.10 server kernel 4.13 with xubuntu desktop. I had the same problem since last night after a power failure. I was seeing the xubuntu splash screen and after a few seconds I would get into the above mentioned messages. I have two single disk Raid0 s on my system.
Alt-tabing while on the splash screen showed me that it was trying to find the dependencies on the second hard drive.
I edited the fstab and removed the dependency leading to that second drive and booted normally.
Hope it helps someone.

Can you help with this problem?

Provide an answer of your own, or ask corrado venturini for more information if necessary.

To post a message you must log in.