Ubuntu 16.04 LTS on Alienware Aurora R7, Kernel panic on shutdown
Clash Royale CLAN TAG#URR8PPP up vote
-1
down vote
favorite
I just installed 16.04 LTS on my new desktop, Dell Alienware Aurora R7, with i7-8700K, 32GB RAM, SSD(SM961 NVMe SSD) and 1080TI.
So far, everything works ok except I get a kernel panic when I try to shutdown (reboot works ok).
How can I avoid that?
kernel shutdown alienware
edited Apr 10 at 12:39
Zanna
48.2k13120228
asked Feb 22 at 12:10
John B. Kim
12
add a comment |Â
up vote
-1
down vote
favorite
I just installed 16.04 LTS on my new desktop, Dell Alienware Aurora R7, with i7-8700K, 32GB RAM, SSD(SM961 NVMe SSD) and 1080TI.
So far, everything works ok except I get a kernel panic when I try to shutdown (reboot works ok).
How can I avoid that?
kernel shutdown alienware
edited Apr 10 at 12:39
Zanna
48.2k13120228
asked Feb 22 at 12:10
John B. Kim
12
What kernel are you running (useuname -ato determine)? You may want to move to a different kernel. That said, since the issue is on shutdown, I wouldn't be too concerned (that's just me).
– richbl
Feb 22 at 14:56
4.13.0-36-generic #40~16.04.1-Ubuntu.
– John B. Kim
Feb 23 at 13:38
Have you tried to disable(blacklist) i2c module noted in this link: helloworldproject.blogspot.com/2016/11/…
– Art
Feb 27 at 20:45
1
I faced the same issue myself and found a solution. See my answer here for the instructions: unix.stackexchange.com/a/446913/52937
– yttrium
May 30 at 13:34
This answer will help you askubuntu.com/a/1047057/486406
– ASIL
Jun 16 at 8:59
add a comment |Â
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I just installed 16.04 LTS on my new desktop, Dell Alienware Aurora R7, with i7-8700K, 32GB RAM, SSD(SM961 NVMe SSD) and 1080TI.
So far, everything works ok except I get a kernel panic when I try to shutdown (reboot works ok).
How can I avoid that?
kernel shutdown alienware
edited Apr 10 at 12:39
Zanna
48.2k13120228
asked Feb 22 at 12:10
John B. Kim
12
I just installed 16.04 LTS on my new desktop, Dell Alienware Aurora R7, with i7-8700K, 32GB RAM, SSD(SM961 NVMe SSD) and 1080TI.
So far, everything works ok except I get a kernel panic when I try to shutdown (reboot works ok).
How can I avoid that?
kernel shutdown alienware
kernel shutdown alienware
edited Apr 10 at 12:39
Zanna
48.2k13120228
asked Feb 22 at 12:10
John B. Kim
12
edited Apr 10 at 12:39
Zanna
48.2k13120228
asked Feb 22 at 12:10
John B. Kim
12
edited Apr 10 at 12:39
Zanna
48.2k13120228
edited Apr 10 at 12:39
Zanna
48.2k13120228
edited Apr 10 at 12:39
Zanna
48.2k13120228
48.2k13120228
asked Feb 22 at 12:10
John B. Kim
12
asked Feb 22 at 12:10
John B. Kim
12
asked Feb 22 at 12:10
John B. Kim
12
12
What kernel are you running (useuname -ato determine)? You may want to move to a different kernel. That said, since the issue is on shutdown, I wouldn't be too concerned (that's just me).
– richbl
Feb 22 at 14:56
4.13.0-36-generic #40~16.04.1-Ubuntu.
– John B. Kim
Feb 23 at 13:38
Have you tried to disable(blacklist) i2c module noted in this link: helloworldproject.blogspot.com/2016/11/…
– Art
Feb 27 at 20:45
1
I faced the same issue myself and found a solution. See my answer here for the instructions: unix.stackexchange.com/a/446913/52937
– yttrium
May 30 at 13:34
This answer will help you askubuntu.com/a/1047057/486406
– ASIL
Jun 16 at 8:59
add a comment |Â
What kernel are you running (useuname -ato determine)? You may want to move to a different kernel. That said, since the issue is on shutdown, I wouldn't be too concerned (that's just me).
– richbl
Feb 22 at 14:56
4.13.0-36-generic #40~16.04.1-Ubuntu.
– John B. Kim
Feb 23 at 13:38
Have you tried to disable(blacklist) i2c module noted in this link: helloworldproject.blogspot.com/2016/11/…
– Art
Feb 27 at 20:45
1
I faced the same issue myself and found a solution. See my answer here for the instructions: unix.stackexchange.com/a/446913/52937
– yttrium
May 30 at 13:34
This answer will help you askubuntu.com/a/1047057/486406
– ASIL
Jun 16 at 8:59
What kernel are you running (use
uname -a to determine)? You may want to move to a different kernel. That said, since the issue is on shutdown, I wouldn't be too concerned (that's just me).– richbl
Feb 22 at 14:56
What kernel are you running (use
uname -a to determine)? You may want to move to a different kernel. That said, since the issue is on shutdown, I wouldn't be too concerned (that's just me).– richbl
Feb 22 at 14:56
4.13.0-36-generic #40~16.04.1-Ubuntu.– John B. Kim
Feb 23 at 13:38
4.13.0-36-generic #40~16.04.1-Ubuntu.– John B. Kim
Feb 23 at 13:38
Have you tried to disable(blacklist) i2c module noted in this link: helloworldproject.blogspot.com/2016/11/…
– Art
Feb 27 at 20:45
Have you tried to disable(blacklist) i2c module noted in this link: helloworldproject.blogspot.com/2016/11/…
– Art
Feb 27 at 20:45
1
1
I faced the same issue myself and found a solution. See my answer here for the instructions: unix.stackexchange.com/a/446913/52937
– yttrium
May 30 at 13:34
I faced the same issue myself and found a solution. See my answer here for the instructions: unix.stackexchange.com/a/446913/52937
– yttrium
May 30 at 13:34
This answer will help you askubuntu.com/a/1047057/486406
– ASIL
Jun 16 at 8:59
This answer will help you askubuntu.com/a/1047057/486406
– ASIL
Jun 16 at 8:59
add a comment |Â
4 Answers
4
active
oldest
votes
up vote
0
down vote
I was actually looking into this due to the fact that I might get the same system.
There was a previous question for this situation for which an answer mentioned choosing a previous kernel version. That might solve it:
Ubuntu 16.04 LTS IRQ kernel panic at shutdown - Alienware R7 desktop
BTW did you try the system with the latest non-LTS version of Ubuntu? That could also work.
answered Feb 22 at 13:29
Newres
62
Thanks for your answer. I tried but it doesn't work.
– John B. Kim
Feb 23 at 13:49
add a comment |Â
up vote
0
down vote
I have an Alienware Aurora R7/0VDT73, BIOS 1.0.11. The system crashed on shutdown because of IRQ issues on a built-in-module (i2c-designware-core).
I solved this by editing the file /etc/default/grub and adding the kernel option noapic, to this line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet noapic splash"
After that you should also launch the command:
sudo update-grub
Now my system shuts down without any problem.
edited Jun 16 at 8:52
Martin Thornton
2,43441730
answered Jun 16 at 8:25
Garfield
11
add a comment |Â
up vote
0
down vote
How I solved this issue!
Add initcall_blacklist=dw_i2c_init_driver to the kernel command line. This works for me on kernel 4.15.0+.
For anyone else who'll find this answer. You can do it by editing /etc/default/grub:
Run in the terminal: sudo -H gedit /etc/default/grub.
(if you don't have gedit installed use your favorite text editor or
"sudo apt install gedit" without quotes)
Append blacklist string to the GRUB_CMDLINE_LINUX_DEFAULT: GRUB_CMDLINE_LINUX_DEFAULT="quiet initcall_blacklist=dw_i2c_init_driver".
Save the file, close the editor.
Run in the terminal: sudo update-grub.
Reboot and test!
Credit goes to this post: https://unix.stackexchange.com/questions/423797/how-do-i-disable-i2c-designware-support-when-its-not-built-as-a-module/446913#446913
These are my specs for this rig.
Alienware Aurora R5
Nvidia GTX 1070/8GBvram
8GB ram
i7 Intel core processor(8core)"Skylake"
answered Jun 27 at 0:56
Jeff Linux Turner
11
It seems that this is the actual answer " How I solved this issue was installing Manjaro and using their built in kernel installer,and switched to a "Real Time" kernel. " I suggest editing your answer to make this stand out more.
– Organic Marble
Jun 27 at 1:32
add a comment |Â
up vote
0
down vote
On my Dell Alienware 17R3 with Samsung Pro 960 NVMe SSD I had a problem suspending/resuming lockup fixed by editing /etc/default/grub and adding the parameter acpiphp.disable=1 to the line containing:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Afterwards it looks like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpiphp.disable=1"
Save the file. Next update /boot/grub.cfg and generate a new initrd.img with the command:
sudo update-grub
Finally reboot and test.
I don't have the PM961, but rather the 960 Pro so haven't experienced your issue. If none of the other answers or comments help one last thing you could try is:
nvme_core.default_ps_max_latency_us=5500
parameter in /etc/default/grub LINUX kernel argument list. I just found this in Arch Linux. There are other steps you may wish to investigate in the link.
answered Mar 3 at 19:42
WinEunuuchs2Unix
36.3k759136
add a comment |Â
protected by WinEunuuchs2Unix Jun 27 at 2:42
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I was actually looking into this due to the fact that I might get the same system.
There was a previous question for this situation for which an answer mentioned choosing a previous kernel version. That might solve it:
Ubuntu 16.04 LTS IRQ kernel panic at shutdown - Alienware R7 desktop
BTW did you try the system with the latest non-LTS version of Ubuntu? That could also work.
answered Feb 22 at 13:29
Newres
62
Thanks for your answer. I tried but it doesn't work.
– John B. Kim
Feb 23 at 13:49
add a comment |Â
up vote
0
down vote
I was actually looking into this due to the fact that I might get the same system.
There was a previous question for this situation for which an answer mentioned choosing a previous kernel version. That might solve it:
Ubuntu 16.04 LTS IRQ kernel panic at shutdown - Alienware R7 desktop
BTW did you try the system with the latest non-LTS version of Ubuntu? That could also work.
answered Feb 22 at 13:29
Newres
62
Thanks for your answer. I tried but it doesn't work.
– John B. Kim
Feb 23 at 13:49
add a comment |Â
up vote
0
down vote
up vote
0
down vote
I was actually looking into this due to the fact that I might get the same system.
There was a previous question for this situation for which an answer mentioned choosing a previous kernel version. That might solve it:
Ubuntu 16.04 LTS IRQ kernel panic at shutdown - Alienware R7 desktop
BTW did you try the system with the latest non-LTS version of Ubuntu? That could also work.
answered Feb 22 at 13:29
Newres
62
I was actually looking into this due to the fact that I might get the same system.
There was a previous question for this situation for which an answer mentioned choosing a previous kernel version. That might solve it:
Ubuntu 16.04 LTS IRQ kernel panic at shutdown - Alienware R7 desktop
BTW did you try the system with the latest non-LTS version of Ubuntu? That could also work.
answered Feb 22 at 13:29
Newres
62
answered Feb 22 at 13:29
Newres
62
answered Feb 22 at 13:29
Newres
62
answered Feb 22 at 13:29
Newres
62
62
Thanks for your answer. I tried but it doesn't work.
– John B. Kim
Feb 23 at 13:49
add a comment |Â
Thanks for your answer. I tried but it doesn't work.
– John B. Kim
Feb 23 at 13:49
Thanks for your answer. I tried but it doesn't work.
– John B. Kim
Feb 23 at 13:49
Thanks for your answer. I tried but it doesn't work.
– John B. Kim
Feb 23 at 13:49
add a comment |Â
up vote
0
down vote
I have an Alienware Aurora R7/0VDT73, BIOS 1.0.11. The system crashed on shutdown because of IRQ issues on a built-in-module (i2c-designware-core).
I solved this by editing the file /etc/default/grub and adding the kernel option noapic, to this line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet noapic splash"
After that you should also launch the command:
sudo update-grub
Now my system shuts down without any problem.
edited Jun 16 at 8:52
Martin Thornton
2,43441730
answered Jun 16 at 8:25
Garfield
11
add a comment |Â
up vote
0
down vote
I have an Alienware Aurora R7/0VDT73, BIOS 1.0.11. The system crashed on shutdown because of IRQ issues on a built-in-module (i2c-designware-core).
I solved this by editing the file /etc/default/grub and adding the kernel option noapic, to this line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet noapic splash"
After that you should also launch the command:
sudo update-grub
Now my system shuts down without any problem.
edited Jun 16 at 8:52
Martin Thornton
2,43441730
answered Jun 16 at 8:25
Garfield
11
add a comment |Â
up vote
0
down vote
up vote
0
down vote
I have an Alienware Aurora R7/0VDT73, BIOS 1.0.11. The system crashed on shutdown because of IRQ issues on a built-in-module (i2c-designware-core).
I solved this by editing the file /etc/default/grub and adding the kernel option noapic, to this line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet noapic splash"
After that you should also launch the command:
sudo update-grub
Now my system shuts down without any problem.
edited Jun 16 at 8:52
Martin Thornton
2,43441730
answered Jun 16 at 8:25
Garfield
11
I have an Alienware Aurora R7/0VDT73, BIOS 1.0.11. The system crashed on shutdown because of IRQ issues on a built-in-module (i2c-designware-core).
I solved this by editing the file /etc/default/grub and adding the kernel option noapic, to this line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet noapic splash"
After that you should also launch the command:
sudo update-grub
Now my system shuts down without any problem.
edited Jun 16 at 8:52
Martin Thornton
2,43441730
answered Jun 16 at 8:25
Garfield
11
edited Jun 16 at 8:52
Martin Thornton
2,43441730
edited Jun 16 at 8:52
Martin Thornton
2,43441730
edited Jun 16 at 8:52
Martin Thornton
2,43441730
2,43441730
answered Jun 16 at 8:25
Garfield
11
answered Jun 16 at 8:25
Garfield
11
answered Jun 16 at 8:25
Garfield
11
11
add a comment |Â
add a comment |Â
up vote
0
down vote
How I solved this issue!
Add initcall_blacklist=dw_i2c_init_driver to the kernel command line. This works for me on kernel 4.15.0+.
For anyone else who'll find this answer. You can do it by editing /etc/default/grub:
Run in the terminal: sudo -H gedit /etc/default/grub.
(if you don't have gedit installed use your favorite text editor or
"sudo apt install gedit" without quotes)
Append blacklist string to the GRUB_CMDLINE_LINUX_DEFAULT: GRUB_CMDLINE_LINUX_DEFAULT="quiet initcall_blacklist=dw_i2c_init_driver".
Save the file, close the editor.
Run in the terminal: sudo update-grub.
Reboot and test!
Credit goes to this post: https://unix.stackexchange.com/questions/423797/how-do-i-disable-i2c-designware-support-when-its-not-built-as-a-module/446913#446913
These are my specs for this rig.
Alienware Aurora R5
Nvidia GTX 1070/8GBvram
8GB ram
i7 Intel core processor(8core)"Skylake"
answered Jun 27 at 0:56
Jeff Linux Turner
11
It seems that this is the actual answer " How I solved this issue was installing Manjaro and using their built in kernel installer,and switched to a "Real Time" kernel. " I suggest editing your answer to make this stand out more.
– Organic Marble
Jun 27 at 1:32
add a comment |Â
up vote
0
down vote
How I solved this issue!
Add initcall_blacklist=dw_i2c_init_driver to the kernel command line. This works for me on kernel 4.15.0+.
For anyone else who'll find this answer. You can do it by editing /etc/default/grub:
Run in the terminal: sudo -H gedit /etc/default/grub.
(if you don't have gedit installed use your favorite text editor or
"sudo apt install gedit" without quotes)
Append blacklist string to the GRUB_CMDLINE_LINUX_DEFAULT: GRUB_CMDLINE_LINUX_DEFAULT="quiet initcall_blacklist=dw_i2c_init_driver".
Save the file, close the editor.
Run in the terminal: sudo update-grub.
Reboot and test!
Credit goes to this post: https://unix.stackexchange.com/questions/423797/how-do-i-disable-i2c-designware-support-when-its-not-built-as-a-module/446913#446913
These are my specs for this rig.
Alienware Aurora R5
Nvidia GTX 1070/8GBvram
8GB ram
i7 Intel core processor(8core)"Skylake"
answered Jun 27 at 0:56
Jeff Linux Turner
11
It seems that this is the actual answer " How I solved this issue was installing Manjaro and using their built in kernel installer,and switched to a "Real Time" kernel. " I suggest editing your answer to make this stand out more.
– Organic Marble
Jun 27 at 1:32
add a comment |Â
up vote
0
down vote
up vote
0
down vote
How I solved this issue!
Add initcall_blacklist=dw_i2c_init_driver to the kernel command line. This works for me on kernel 4.15.0+.
For anyone else who'll find this answer. You can do it by editing /etc/default/grub:
Run in the terminal: sudo -H gedit /etc/default/grub.
(if you don't have gedit installed use your favorite text editor or
"sudo apt install gedit" without quotes)
Append blacklist string to the GRUB_CMDLINE_LINUX_DEFAULT: GRUB_CMDLINE_LINUX_DEFAULT="quiet initcall_blacklist=dw_i2c_init_driver".
Save the file, close the editor.
Run in the terminal: sudo update-grub.
Reboot and test!
Credit goes to this post: https://unix.stackexchange.com/questions/423797/how-do-i-disable-i2c-designware-support-when-its-not-built-as-a-module/446913#446913
These are my specs for this rig.
Alienware Aurora R5
Nvidia GTX 1070/8GBvram
8GB ram
i7 Intel core processor(8core)"Skylake"
answered Jun 27 at 0:56
Jeff Linux Turner
11
How I solved this issue!
Add initcall_blacklist=dw_i2c_init_driver to the kernel command line. This works for me on kernel 4.15.0+.
For anyone else who'll find this answer. You can do it by editing /etc/default/grub:
Run in the terminal: sudo -H gedit /etc/default/grub.
(if you don't have gedit installed use your favorite text editor or
"sudo apt install gedit" without quotes)
Append blacklist string to the GRUB_CMDLINE_LINUX_DEFAULT: GRUB_CMDLINE_LINUX_DEFAULT="quiet initcall_blacklist=dw_i2c_init_driver".
Save the file, close the editor.
Run in the terminal: sudo update-grub.
Reboot and test!
Credit goes to this post: https://unix.stackexchange.com/questions/423797/how-do-i-disable-i2c-designware-support-when-its-not-built-as-a-module/446913#446913
These are my specs for this rig.
Alienware Aurora R5
Nvidia GTX 1070/8GBvram
8GB ram
i7 Intel core processor(8core)"Skylake"
answered Jun 27 at 0:56
Jeff Linux Turner
11
edited Jun 27 at 2:44
answered Jun 27 at 0:56
Jeff Linux Turner
11
answered Jun 27 at 0:56
Jeff Linux Turner
11
answered Jun 27 at 0:56
Jeff Linux Turner
11
11
It seems that this is the actual answer " How I solved this issue was installing Manjaro and using their built in kernel installer,and switched to a "Real Time" kernel. " I suggest editing your answer to make this stand out more.
– Organic Marble
Jun 27 at 1:32
add a comment |Â
It seems that this is the actual answer " How I solved this issue was installing Manjaro and using their built in kernel installer,and switched to a "Real Time" kernel. " I suggest editing your answer to make this stand out more.
– Organic Marble
Jun 27 at 1:32
It seems that this is the actual answer " How I solved this issue was installing Manjaro and using their built in kernel installer,and switched to a "Real Time" kernel. " I suggest editing your answer to make this stand out more.
– Organic Marble
Jun 27 at 1:32
It seems that this is the actual answer " How I solved this issue was installing Manjaro and using their built in kernel installer,and switched to a "Real Time" kernel. " I suggest editing your answer to make this stand out more.
– Organic Marble
Jun 27 at 1:32
add a comment |Â
up vote
0
down vote
On my Dell Alienware 17R3 with Samsung Pro 960 NVMe SSD I had a problem suspending/resuming lockup fixed by editing /etc/default/grub and adding the parameter acpiphp.disable=1 to the line containing:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Afterwards it looks like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpiphp.disable=1"
Save the file. Next update /boot/grub.cfg and generate a new initrd.img with the command:
sudo update-grub
Finally reboot and test.
I don't have the PM961, but rather the 960 Pro so haven't experienced your issue. If none of the other answers or comments help one last thing you could try is:
nvme_core.default_ps_max_latency_us=5500
parameter in /etc/default/grub LINUX kernel argument list. I just found this in Arch Linux. There are other steps you may wish to investigate in the link.
answered Mar 3 at 19:42
WinEunuuchs2Unix
36.3k759136
add a comment |Â
up vote
0
down vote
On my Dell Alienware 17R3 with Samsung Pro 960 NVMe SSD I had a problem suspending/resuming lockup fixed by editing /etc/default/grub and adding the parameter acpiphp.disable=1 to the line containing:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Afterwards it looks like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpiphp.disable=1"
Save the file. Next update /boot/grub.cfg and generate a new initrd.img with the command:
sudo update-grub
Finally reboot and test.
I don't have the PM961, but rather the 960 Pro so haven't experienced your issue. If none of the other answers or comments help one last thing you could try is:
nvme_core.default_ps_max_latency_us=5500
parameter in /etc/default/grub LINUX kernel argument list. I just found this in Arch Linux. There are other steps you may wish to investigate in the link.
answered Mar 3 at 19:42
WinEunuuchs2Unix
36.3k759136
add a comment |Â
up vote
0
down vote
up vote
0
down vote
On my Dell Alienware 17R3 with Samsung Pro 960 NVMe SSD I had a problem suspending/resuming lockup fixed by editing /etc/default/grub and adding the parameter acpiphp.disable=1 to the line containing:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Afterwards it looks like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpiphp.disable=1"
Save the file. Next update /boot/grub.cfg and generate a new initrd.img with the command:
sudo update-grub
Finally reboot and test.
I don't have the PM961, but rather the 960 Pro so haven't experienced your issue. If none of the other answers or comments help one last thing you could try is:
nvme_core.default_ps_max_latency_us=5500
parameter in /etc/default/grub LINUX kernel argument list. I just found this in Arch Linux. There are other steps you may wish to investigate in the link.
answered Mar 3 at 19:42
WinEunuuchs2Unix
36.3k759136
On my Dell Alienware 17R3 with Samsung Pro 960 NVMe SSD I had a problem suspending/resuming lockup fixed by editing /etc/default/grub and adding the parameter acpiphp.disable=1 to the line containing:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Afterwards it looks like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpiphp.disable=1"
Save the file. Next update /boot/grub.cfg and generate a new initrd.img with the command:
sudo update-grub
Finally reboot and test.
I don't have the PM961, but rather the 960 Pro so haven't experienced your issue. If none of the other answers or comments help one last thing you could try is:
nvme_core.default_ps_max_latency_us=5500
parameter in /etc/default/grub LINUX kernel argument list. I just found this in Arch Linux. There are other steps you may wish to investigate in the link.
answered Mar 3 at 19:42
WinEunuuchs2Unix
36.3k759136
edited Jun 27 at 2:51
answered Mar 3 at 19:42
WinEunuuchs2Unix
36.3k759136
answered Mar 3 at 19:42
WinEunuuchs2Unix
36.3k759136
answered Mar 3 at 19:42
WinEunuuchs2Unix
36.3k759136
36.3k759136
add a comment |Â
add a comment |Â
protected by WinEunuuchs2Unix Jun 27 at 2:42
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
What kernel are you running (use
uname -ato determine)? You may want to move to a different kernel. That said, since the issue is on shutdown, I wouldn't be too concerned (that's just me).– richbl
Feb 22 at 14:56
4.13.0-36-generic #40~16.04.1-Ubuntu.– John B. Kim
Feb 23 at 13:38
Have you tried to disable(blacklist) i2c module noted in this link: helloworldproject.blogspot.com/2016/11/…
– Art
Feb 27 at 20:45
1
I faced the same issue myself and found a solution. See my answer here for the instructions: unix.stackexchange.com/a/446913/52937
– yttrium
May 30 at 13:34
This answer will help you askubuntu.com/a/1047057/486406
– ASIL
Jun 16 at 8:59