Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - linux-nvme

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: linux-nvme 4.9.7-1

Git Clone URL: https://aur-dev.archlinux.org/linux-nvme.git (read-only)
Package Base: linux-nvme
Description: The Linux kernel with patches made by Andy Lutomirski
Upstream URL: http://www.kernel.org/
Licenses: GPL2
Submitter: damige
Maintainer: damige
Last Packager: damige
Votes: 14
Popularity: 3.164561
First Submitted: 2016-09-04 01:20
Last Updated: 2017-02-01 19:29

Latest Comments

1 2 3 4 5 Next › Last »

damige commented on 2017-01-23 22:15

@MartB After some more testing i only seem to get this problem if the laptop has been in standby(close lid) since boot. Avoiding standby seems to avoid the issue for me.

damige commented on 2017-01-09 14:18

@MartB thanks, please let us know if you find something interesting or for example if i need to change the patches.

MartB commented on 2017-01-09 14:14

@damige now thats really unfortunate because its such a commonly used nvme device :/

Thanks for posting that patch i will try to find more information about that specific issue. I really hope this can be ironed out too.

damige commented on 2017-01-09 14:08


I have seen this before myself too (just once) i'm currently under the assumption its this:

The creator of the APST patchset: Andy Lutomirski, created this patch to disable APST for the SM951 as there were issues reported with it while running APST. I have not included this patch that disables APST as i use the SM951 myself.

I hope this (occasional) issue with the SM951 can be ironed out, though i have no idea if its a bug that can be worked around within the software patches or if its a hardware/controller bug.

MartB commented on 2017-01-09 09:18

I just ran into another filesystem crash on this kernel while compiling the new version.

If someone can walk me through the process to provide better debugging information go ahead.

To be clear this happened twice only on linux-nvme nowhere else (not even on mainline 4.9 or 4.10)

Samsung PM-951 on a dell xps 15.

Kind regards

damige commented on 2017-01-07 22:54

@edh @mindstormer
Thanks for the feedback i have re-included the sign files in the pkgbuild.

mindstormer commented on 2017-01-07 22:42

Sorry, I just glimpsed at previous comments and thought there were issues regarding keys so when I couldn't builds the newer one, I assumed I had the same issue. You're right.

edh commented on 2017-01-07 15:00

Would you please consider adding the signature files back again :(
One user misinterpreting an error message should not be a sufficient reason to simply remove them. The package is way more trustworthy if it uses gpg signatures and it probably is not a burden for most users.

Everything you need to know should be explained or referenced in makepkg's ArchWiki entry [1]. In your case the gpg keys for verifying the kernel are simply missing in your keyring.

[1] https://wiki.archlinux.org/index.php/makepkg#Signature_checking

damige commented on 2017-01-06 21:57

@mindstormer: please try again
If it doesnt work try:
"gpg --recv-keys 'ABAF11C65A2970B130ABE3C479BE3E4300411886' '647F28654894E3BD457199BE38DBBDC86092693E'"

mindstormer commented on 2017-01-06 21:47

Signature error for latest as of this post:

Verifying source file signatures with gpg...
linux-4.9.tar ... FAILED (unknown public key 79BE3E4300411886)
patch-4.9.1 ... FAILED (unknown public key 38DBBDC86092693E)
==> ERROR: One or more PGP signatures could not be verified!