Newer Kernels cause problems for my SSD, how can I fix?
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
When I decided to install linux, I was plagued with battery life problems, and most annoyingly, every reboot my system would fail to detect my SSD.
After much research I have found the source to one of my problems.
In kernel version 4.11 they added a NVMe controller that saves power. After the kernel version 4.11.0rc7 they added in this patch:
static const struct nvme_core_quirk_entry core_quirks = {
/*
* Seen on a Samsung "SM951 NVMe SAMSUNG 256GB": using APST causes
* the controller to go out to lunch. It dies when the watchdog
* timer reads CSTS and gets 0xffffffff.
*/
.vid = 0x144d,
.fr = "BXW75D0Q",
.quirks = NVME_QUIRK_NO_APST,
,
Apparently this causes problems with my SSD when rebooting, making it so it is not detected. I can only use kernel version 4.11.0rc7 any below to avoid the rebooting problem AND have the power changing patch in my kernel.
Now, my only question is: Is it possible to disable this in newer kernels? I wouldn't really know how to go about this at all. I'd hope it's as simple as adding a boot parameter.
boot kernel ssd xps
edited Jan 28 at 15:57
Thomas
3,31481326
asked Jan 28 at 15:12
Cristian Velasquez Ramos
62
add a comment |Â
up vote
0
down vote
favorite
When I decided to install linux, I was plagued with battery life problems, and most annoyingly, every reboot my system would fail to detect my SSD.
After much research I have found the source to one of my problems.
In kernel version 4.11 they added a NVMe controller that saves power. After the kernel version 4.11.0rc7 they added in this patch:
static const struct nvme_core_quirk_entry core_quirks = {
/*
* Seen on a Samsung "SM951 NVMe SAMSUNG 256GB": using APST causes
* the controller to go out to lunch. It dies when the watchdog
* timer reads CSTS and gets 0xffffffff.
*/
.vid = 0x144d,
.fr = "BXW75D0Q",
.quirks = NVME_QUIRK_NO_APST,
,
Apparently this causes problems with my SSD when rebooting, making it so it is not detected. I can only use kernel version 4.11.0rc7 any below to avoid the rebooting problem AND have the power changing patch in my kernel.
Now, my only question is: Is it possible to disable this in newer kernels? I wouldn't really know how to go about this at all. I'd hope it's as simple as adding a boot parameter.
boot kernel ssd xps
edited Jan 28 at 15:57
Thomas
3,31481326
asked Jan 28 at 15:12
Cristian Velasquez Ramos
62
You should report bug upstream or to launchpad, but not here.
– N0rbert
Jan 28 at 16:04
This question has information that might be helpful: askubuntu.com/questions/998471/…
– WinEunuuchs2Unix
Jan 28 at 16:42
I was hoping I would be able to disable this patch myself, but I suppose no one knows how? Thank you for the link
– Cristian Velasquez Ramos
Jan 28 at 18:08
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
When I decided to install linux, I was plagued with battery life problems, and most annoyingly, every reboot my system would fail to detect my SSD.
After much research I have found the source to one of my problems.
In kernel version 4.11 they added a NVMe controller that saves power. After the kernel version 4.11.0rc7 they added in this patch:
static const struct nvme_core_quirk_entry core_quirks = {
/*
* Seen on a Samsung "SM951 NVMe SAMSUNG 256GB": using APST causes
* the controller to go out to lunch. It dies when the watchdog
* timer reads CSTS and gets 0xffffffff.
*/
.vid = 0x144d,
.fr = "BXW75D0Q",
.quirks = NVME_QUIRK_NO_APST,
,
Apparently this causes problems with my SSD when rebooting, making it so it is not detected. I can only use kernel version 4.11.0rc7 any below to avoid the rebooting problem AND have the power changing patch in my kernel.
Now, my only question is: Is it possible to disable this in newer kernels? I wouldn't really know how to go about this at all. I'd hope it's as simple as adding a boot parameter.
boot kernel ssd xps
edited Jan 28 at 15:57
Thomas
3,31481326
asked Jan 28 at 15:12
Cristian Velasquez Ramos
62
When I decided to install linux, I was plagued with battery life problems, and most annoyingly, every reboot my system would fail to detect my SSD.
After much research I have found the source to one of my problems.
In kernel version 4.11 they added a NVMe controller that saves power. After the kernel version 4.11.0rc7 they added in this patch:
static const struct nvme_core_quirk_entry core_quirks = {
/*
* Seen on a Samsung "SM951 NVMe SAMSUNG 256GB": using APST causes
* the controller to go out to lunch. It dies when the watchdog
* timer reads CSTS and gets 0xffffffff.
*/
.vid = 0x144d,
.fr = "BXW75D0Q",
.quirks = NVME_QUIRK_NO_APST,
,
Apparently this causes problems with my SSD when rebooting, making it so it is not detected. I can only use kernel version 4.11.0rc7 any below to avoid the rebooting problem AND have the power changing patch in my kernel.
Now, my only question is: Is it possible to disable this in newer kernels? I wouldn't really know how to go about this at all. I'd hope it's as simple as adding a boot parameter.
boot kernel ssd xps
boot kernel ssd xps
edited Jan 28 at 15:57
Thomas
3,31481326
asked Jan 28 at 15:12
Cristian Velasquez Ramos
62
edited Jan 28 at 15:57
Thomas
3,31481326
asked Jan 28 at 15:12
Cristian Velasquez Ramos
62
edited Jan 28 at 15:57
Thomas
3,31481326
edited Jan 28 at 15:57
Thomas
3,31481326
edited Jan 28 at 15:57
Thomas
3,31481326
3,31481326
asked Jan 28 at 15:12
Cristian Velasquez Ramos
62
asked Jan 28 at 15:12
Cristian Velasquez Ramos
62
asked Jan 28 at 15:12
Cristian Velasquez Ramos
62
62
You should report bug upstream or to launchpad, but not here.
– N0rbert
Jan 28 at 16:04
This question has information that might be helpful: askubuntu.com/questions/998471/…
– WinEunuuchs2Unix
Jan 28 at 16:42
I was hoping I would be able to disable this patch myself, but I suppose no one knows how? Thank you for the link
– Cristian Velasquez Ramos
Jan 28 at 18:08
add a comment |Â
You should report bug upstream or to launchpad, but not here.
– N0rbert
Jan 28 at 16:04
This question has information that might be helpful: askubuntu.com/questions/998471/…
– WinEunuuchs2Unix
Jan 28 at 16:42
I was hoping I would be able to disable this patch myself, but I suppose no one knows how? Thank you for the link
– Cristian Velasquez Ramos
Jan 28 at 18:08
You should report bug upstream or to launchpad, but not here.
– N0rbert
Jan 28 at 16:04
You should report bug upstream or to launchpad, but not here.
– N0rbert
Jan 28 at 16:04
This question has information that might be helpful: askubuntu.com/questions/998471/…
– WinEunuuchs2Unix
Jan 28 at 16:42
This question has information that might be helpful: askubuntu.com/questions/998471/…
– WinEunuuchs2Unix
Jan 28 at 16:42
I was hoping I would be able to disable this patch myself, but I suppose no one knows how? Thank you for the link
– Cristian Velasquez Ramos
Jan 28 at 18:08
I was hoping I would be able to disable this patch myself, but I suppose no one knows how? Thank you for the link
– Cristian Velasquez Ramos
Jan 28 at 18:08
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
You may have already fixed this by now, but I thought I'd post here as well as the original thread.
TLDR: Try booting with kernel parameter nvme_core.force_apst=1
answered Jun 13 at 23:59
tuxxi
1012
1
Hi! Thanks for the response. I found a perfect tuning to allow my SSD to take advantage of the internal optimization while not having it stall on reboot. in the kernel parameters just place this parameter:nvme_core.default_ps_max_latency_us=4950
– Cristian Velasquez Ramos
Jun 17 at 14:38
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You may have already fixed this by now, but I thought I'd post here as well as the original thread.
TLDR: Try booting with kernel parameter nvme_core.force_apst=1
answered Jun 13 at 23:59
tuxxi
1012
1
Hi! Thanks for the response. I found a perfect tuning to allow my SSD to take advantage of the internal optimization while not having it stall on reboot. in the kernel parameters just place this parameter:nvme_core.default_ps_max_latency_us=4950
– Cristian Velasquez Ramos
Jun 17 at 14:38
add a comment |Â
up vote
0
down vote
You may have already fixed this by now, but I thought I'd post here as well as the original thread.
TLDR: Try booting with kernel parameter nvme_core.force_apst=1
answered Jun 13 at 23:59
tuxxi
1012
1
Hi! Thanks for the response. I found a perfect tuning to allow my SSD to take advantage of the internal optimization while not having it stall on reboot. in the kernel parameters just place this parameter:nvme_core.default_ps_max_latency_us=4950
– Cristian Velasquez Ramos
Jun 17 at 14:38
add a comment |Â
up vote
0
down vote
up vote
0
down vote
You may have already fixed this by now, but I thought I'd post here as well as the original thread.
TLDR: Try booting with kernel parameter nvme_core.force_apst=1
answered Jun 13 at 23:59
tuxxi
1012
You may have already fixed this by now, but I thought I'd post here as well as the original thread.
TLDR: Try booting with kernel parameter nvme_core.force_apst=1
answered Jun 13 at 23:59
tuxxi
1012
answered Jun 13 at 23:59
tuxxi
1012
answered Jun 13 at 23:59
tuxxi
1012
answered Jun 13 at 23:59
tuxxi
1012
1012
1
Hi! Thanks for the response. I found a perfect tuning to allow my SSD to take advantage of the internal optimization while not having it stall on reboot. in the kernel parameters just place this parameter:nvme_core.default_ps_max_latency_us=4950
– Cristian Velasquez Ramos
Jun 17 at 14:38
add a comment |Â
1
Hi! Thanks for the response. I found a perfect tuning to allow my SSD to take advantage of the internal optimization while not having it stall on reboot. in the kernel parameters just place this parameter:nvme_core.default_ps_max_latency_us=4950
– Cristian Velasquez Ramos
Jun 17 at 14:38
1
1
Hi! Thanks for the response. I found a perfect tuning to allow my SSD to take advantage of the internal optimization while not having it stall on reboot. in the kernel parameters just place this parameter:
nvme_core.default_ps_max_latency_us=4950– Cristian Velasquez Ramos
Jun 17 at 14:38
Hi! Thanks for the response. I found a perfect tuning to allow my SSD to take advantage of the internal optimization while not having it stall on reboot. in the kernel parameters just place this parameter:
nvme_core.default_ps_max_latency_us=4950– Cristian Velasquez Ramos
Jun 17 at 14:38
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1000681%2fnewer-kernels-cause-problems-for-my-ssd-how-can-i-fix%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
You should report bug upstream or to launchpad, but not here.
– N0rbert
Jan 28 at 16:04
This question has information that might be helpful: askubuntu.com/questions/998471/…
– WinEunuuchs2Unix
Jan 28 at 16:42
I was hoping I would be able to disable this patch myself, but I suppose no one knows how? Thank you for the link
– Cristian Velasquez Ramos
Jan 28 at 18:08