Just had the same error in Ubuntu 14.04, but noticed that it only
occured AFTER I had updated from kernel 3.19.0-30-generic #33 to
3.19.0-30-generic #34 and especially after loading any new module.
Kernel 3.19.0-30-generic #33 and 3.19.0-30-generic #34 has the same path
so it makes sense that
In my case:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.3 LTS
Release:14.04
Codename: trusty
$ uname -rv
3.13.0-65-generic #105-Ubuntu SMP Mon Sep 21 18:50:58 UTC 2015
$ dmesg | grep -i glacier
[1.764257] Loaded X.509 cert
Hi Folks,
I have the same behavior:
3.19.0-30-generic #33-Ubuntu SMP Mon Sep 21 20:58:04 UTC 2015
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 15.04
Release:15.04
Codename: vivid
[mar. oct. 6 00:06:18 2015] Request for unknown module key
Why is this bug set to Fix released for Trusty? This is still
happening:
$ uname -rv
3.13.0-53-generic #88-Ubuntu SMP Wed May 13 18:10:29 UTC 2015
$ modprobe xfs
$ dmesg -T | tail -2
[Fri May 29 10:41:08 2015] Request for unknown module key 'Magrathea: Glacier
signing key:
Same issue
$ lsb_release -r
Release:14.04
$ uname -r
3.13.0-52-generic
May 10 00:40:40 kernel: [...] Request for unknown module key 'Magrathea:
Glacier signing key: 1981bc916ffc00599231ec5630e666e0256fd6f1' err -11
May 10 00:40:40 kernel: [...] ipt_REJECT: module verification failed:
This is also happening with the latest supported kernel on 14.04 LTS. We
are seeing various repeated messages of Request for unknown module key
'Magrathea: Glacier signing key:
6fca287c2573d09ca32c1980c0d763777a63d4f5' err -11 on some, but not all,
machines running this. I guess it relates to the
Sorry, this is on Trusty amd64, with linux-lowlatency-lts-utopic
3.16.0.31.24
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-raring in Ubuntu.
https://bugs.launchpad.net/bugs/1253155
Title:
Failure to validate module
I'm seeing this with linux-lowlatency-lts-utopic...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-raring in Ubuntu.
https://bugs.launchpad.net/bugs/1253155
Title:
Failure to validate module signature at boot time
Status in
3.19.1 clears the issue for me:
~$ uname -a
Linux g 3.19.1-031901-generic #201503080052 SMP Sun Mar 8 00:54:35 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
$ dmesg | grep Magrathea
[0.922583] Loaded X.509 cert 'Magrathea: Glacier signing key:
f6e44eefe0b3323a7a9c2576cad3252ee3ee7cfc'
Solved by installing the kernel from http://kernel.ubuntu.com/~kernel-
ppa/mainline/daily/2015-02-10-vivid/ leading to 3.19.0-999-generic
#201502092105
According to https://bugzilla.kernel.org/show_bug.cgi?id=92981 the
kernel on http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/ was
built
I installed the amd64 version of kernel 3.19 and have the same issue
reported by Sander Jonkers (jonkers).
dmesg | grep -i glacier
[4.179034] Loaded X.509 cert 'Magrathea: Glacier signing key:
7271576a09d86ef244371b0633e47abb75b89d'
[4.208578] Request for unknown module key 'Magrathea:
FWIW:
I also installed the lowlatency version of kernel 3.19, and that dmesg
doesn't show the lines Request for unknown module key 'Magrathea:
Glacier signing key:
sander@superstreamer:~$ uname -a
Linux superstreamer 3.19.0-031900-lowlatency #201502091451 SMP PREEMPT Mon Feb
9 14:58:45 UTC 2015
I just installed kernel 3.19 on vivid (source: http://kernel.ubuntu.com
/~kernel-ppa/mainline/v3.19-vivid/), and dmesg shows 129 lines with
Request for unknown module key 'Magrathea: Glacier signing key:
007271576a09d86ef244371b0633e47abb75b89d' err -11
So ... is this a regression bug? Or
This bug was fixed in the package linux-lts-raring -
3.8.0-38.56~precise1
---
linux-lts-raring (3.8.0-38.56~precise1) precise; urgency=low
[ Andy Whitcroft ]
* module signature does not use hash type in older releases
linux-lts-raring (3.8.0-38.55~precise1) precise; urgency=low
** Changed in: linux-lts-raring (Ubuntu Precise)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1253155
Title:
Failure to validate module
** Also affects: linux-lts-raring (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1253155
Title:
Failure to validate module signature
** Also affects: linux (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: linux-lts-raring (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects:
This support does not exist before v3.7 and therefore does not affect
quantal or precise.
** Changed in: linux (Ubuntu Quantal)
Status: New = Invalid
** Changed in: linux (Ubuntu Quantal)
Assignee: (unassigned) = Andy Whitcroft (apw)
** Changed in: linux (Ubuntu Precise)
** Changed in: linux-lts-raring (Ubuntu Precise)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1253155
Title:
Failure to validate module signature at
Patch for linux-lts-raring pushed to kernel-team@ for review for SRU.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1253155
Title:
Failure to validate module signature at boot time
This bug was fixed in the package linux - 3.11.0-15.23
---
linux (3.11.0-15.23) saucy; urgency=low
[Brad Figg]
* Release Tracking Bug
- LP: #1259259
[ Tim Gardner ]
* [Config] Build-in ohci-pci
- LP: #1244176
linux (3.11.0-15.22) saucy; urgency=low
[Brad Figg]
I'm so sorry. This operation is my mistake.
Status Fix Commited is right. But I can't rollback status.
Somebody, could you change status?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Saucy)
Status: Fix Released = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1253155
Title:
Failure to validate module signature at
** Tags removed: verification-needed-saucy
** Tags added: verification-done-saucy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1253155
Title:
Failure to validate module signature at
module video is not tainting the kernel anymore with this kernel
version from proposed
linux-3.11.0-15-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1253155
Title:
Failure to
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
saucy' to 'verification-done-saucy'.
If verification is not done by 5 working days from
** Branch linked: lp:ubuntu/precise-proposed/linux-lts-saucy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1253155
Title:
Failure to validate module signature at boot time
Status in
** Changed in: linux (Ubuntu Trusty)
Status: In Progress = Fix Committed
** Changed in: linux (Ubuntu Saucy)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Saucy)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1253155
Title:
Failure to validate module signature at boot time
This bug was fixed in the package linux - 3.12.0-4.12
---
linux (3.12.0-4.12) trusty; urgency=low
[ Andy Whitcroft ]
* [Config] switch build-depends to libiberty-dev
Fixes FTBS
* Release tracker
- LP: #1255322
-- Tim Gardner tim.gard...@canonical.com Tue, 26 Nov
This appears to be due to an objcopy that normally only happens on the
buildds when a gnu debug section is added to a module ELF, e.g.,
objcopy --add-gnu-debuglink=$(dbgpkgdir)/usr/lib/debug/$$module
$(pkgdir)/$$module
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Tim Gardner
** Also affects: linux (Ubuntu Trusty)
Importance: High
Assignee: Tim Gardner (timg-tpi)
Status: Confirmed
** Also affects: linux (Ubuntu Saucy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux (Ubuntu Saucy)
Status: New = In Progress
** Changed in: linux (Ubuntu Saucy)
Assignee: (unassigned) = Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed = In Progress
--
You received this bug notification because you are a
I get the module verification failed messages for libahci.ko. If the
module is signed, running:
hexdump -C /path/to/module | tail -n 5
should show the string ~Module signature appended~ at the end. I see
that with i915.ko for example, but with video.ko and libahci.ko I do
not. After a little
Attaching an older kernel log which contains the examples mentioned in
the report.
** Attachment added: kern.log.1
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1253155/+attachment/3913419/+files/kern.log.1
--
You received this bug notification because you are a member of Kernel
Similar bug reports:
bug 1237394
bug 1241251
** Changed in: linux (Ubuntu)
Status: New = Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Tags added: kernel-key
--
You received this bug notification because you are a member of Kernel
Packages, which is
36 matches
Mail list logo
