panic kernel when my laptop is being connected to a wifi network
Clash Royale CLAN TAG#URR8PPP up vote
1
down vote
favorite
My laptop has a rtl8723be wifi card. The trouble started when I tried to install the latest drivers wifi version.So, The spotted problem is that when my my laptop is being connected to a wifi network, a process(named systemd-journal) automatically starts running in the background creating huge log files like 60 GB. But,when I run (sudo modprobe -rv rtl8723be) both the wifi and the process turn off. I found the created files and deleted them but the question is, what can I do in order to use wifi without kernel panic. Currently I have turn off the wifi and I am using ethernet.
16.04
asked Mar 14 at 15:18
Nikolas Chrysanthidis
61
 |Â
show 5 more comments
up vote
1
down vote
favorite
My laptop has a rtl8723be wifi card. The trouble started when I tried to install the latest drivers wifi version.So, The spotted problem is that when my my laptop is being connected to a wifi network, a process(named systemd-journal) automatically starts running in the background creating huge log files like 60 GB. But,when I run (sudo modprobe -rv rtl8723be) both the wifi and the process turn off. I found the created files and deleted them but the question is, what can I do in order to use wifi without kernel panic. Currently I have turn off the wifi and I am using ethernet.
16.04
asked Mar 14 at 15:18
Nikolas Chrysanthidis
61
How did you install that latest WiFi drivers? Was it through the Ubuntu repositories or somewhere else?
– dsstorefile1
Mar 14 at 18:03
It was through repositories. I am writing the commands below.$ sudo add-apt-repository ppa:hanipouspilot/rtlwifi$ sudo apt-get update$ sudo apt-get install rtlwifi-new-dkms linux-firmware$ sudo reboot$ sudo apt-get install linux-headers-$(uname -r) gcc g++ build-essential dkms git$ cd rtlwifi_new-rock.new_btcoex$ make$ sudo make install$ sudo modprobe -rv rtl8723be` $ sudo modprobe -v rtl8723be ant_sel=2`$ echo "options rtl8723be ant_sel=2 fwlps=0" | sudo tee /etc/modprobe.d/rtl8723be.conf
– Nikolas Chrysanthidis
Mar 14 at 20:42
PPAs aren't official sources of software, so you have to be careful. What do the systemd-journal logs contain when the problem occurs? If it's a set of repeating messages, can you post a sample of them on a pastebin so someone can take a look at them?
– dsstorefile1
Mar 16 at 1:42
<Exactly as you described. This is just a small sample of the created log file. / Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472757] pcieport 0000:00:1d.3: device [8086:9d1b] error status/mask=00000001/00002000 Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472775] pcieport 0000:00:1d.3: [ 0] Receiver Error (First) Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472789] pcieport 0000:00:1d.3: AER: Corrected error received: id=00eb Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.473451] pcieport 0000:00:1d.3: can't find device of ID00eb>
– Nikolas Chrysanthidis
Mar 18 at 12:05
That looks familiar. Try rebooting withpci=nomsion the kernel command line and see if the error messages become less frequent.
– dsstorefile1
Mar 18 at 20:45
 |Â
show 5 more comments
up vote
1
down vote
favorite
up vote
1
down vote
favorite
My laptop has a rtl8723be wifi card. The trouble started when I tried to install the latest drivers wifi version.So, The spotted problem is that when my my laptop is being connected to a wifi network, a process(named systemd-journal) automatically starts running in the background creating huge log files like 60 GB. But,when I run (sudo modprobe -rv rtl8723be) both the wifi and the process turn off. I found the created files and deleted them but the question is, what can I do in order to use wifi without kernel panic. Currently I have turn off the wifi and I am using ethernet.
16.04
asked Mar 14 at 15:18
Nikolas Chrysanthidis
61
My laptop has a rtl8723be wifi card. The trouble started when I tried to install the latest drivers wifi version.So, The spotted problem is that when my my laptop is being connected to a wifi network, a process(named systemd-journal) automatically starts running in the background creating huge log files like 60 GB. But,when I run (sudo modprobe -rv rtl8723be) both the wifi and the process turn off. I found the created files and deleted them but the question is, what can I do in order to use wifi without kernel panic. Currently I have turn off the wifi and I am using ethernet.
16.04
16.04
asked Mar 14 at 15:18
Nikolas Chrysanthidis
61
asked Mar 14 at 15:18
Nikolas Chrysanthidis
61
asked Mar 14 at 15:18
Nikolas Chrysanthidis
61
asked Mar 14 at 15:18
Nikolas Chrysanthidis
61
asked Mar 14 at 15:18
Nikolas Chrysanthidis
61
61
How did you install that latest WiFi drivers? Was it through the Ubuntu repositories or somewhere else?
– dsstorefile1
Mar 14 at 18:03
It was through repositories. I am writing the commands below.$ sudo add-apt-repository ppa:hanipouspilot/rtlwifi$ sudo apt-get update$ sudo apt-get install rtlwifi-new-dkms linux-firmware$ sudo reboot$ sudo apt-get install linux-headers-$(uname -r) gcc g++ build-essential dkms git$ cd rtlwifi_new-rock.new_btcoex$ make$ sudo make install$ sudo modprobe -rv rtl8723be` $ sudo modprobe -v rtl8723be ant_sel=2`$ echo "options rtl8723be ant_sel=2 fwlps=0" | sudo tee /etc/modprobe.d/rtl8723be.conf
– Nikolas Chrysanthidis
Mar 14 at 20:42
PPAs aren't official sources of software, so you have to be careful. What do the systemd-journal logs contain when the problem occurs? If it's a set of repeating messages, can you post a sample of them on a pastebin so someone can take a look at them?
– dsstorefile1
Mar 16 at 1:42
<Exactly as you described. This is just a small sample of the created log file. / Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472757] pcieport 0000:00:1d.3: device [8086:9d1b] error status/mask=00000001/00002000 Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472775] pcieport 0000:00:1d.3: [ 0] Receiver Error (First) Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472789] pcieport 0000:00:1d.3: AER: Corrected error received: id=00eb Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.473451] pcieport 0000:00:1d.3: can't find device of ID00eb>
– Nikolas Chrysanthidis
Mar 18 at 12:05
That looks familiar. Try rebooting withpci=nomsion the kernel command line and see if the error messages become less frequent.
– dsstorefile1
Mar 18 at 20:45
 |Â
show 5 more comments
How did you install that latest WiFi drivers? Was it through the Ubuntu repositories or somewhere else?
– dsstorefile1
Mar 14 at 18:03
It was through repositories. I am writing the commands below.$ sudo add-apt-repository ppa:hanipouspilot/rtlwifi$ sudo apt-get update$ sudo apt-get install rtlwifi-new-dkms linux-firmware$ sudo reboot$ sudo apt-get install linux-headers-$(uname -r) gcc g++ build-essential dkms git$ cd rtlwifi_new-rock.new_btcoex$ make$ sudo make install$ sudo modprobe -rv rtl8723be` $ sudo modprobe -v rtl8723be ant_sel=2`$ echo "options rtl8723be ant_sel=2 fwlps=0" | sudo tee /etc/modprobe.d/rtl8723be.conf
– Nikolas Chrysanthidis
Mar 14 at 20:42
PPAs aren't official sources of software, so you have to be careful. What do the systemd-journal logs contain when the problem occurs? If it's a set of repeating messages, can you post a sample of them on a pastebin so someone can take a look at them?
– dsstorefile1
Mar 16 at 1:42
<Exactly as you described. This is just a small sample of the created log file. / Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472757] pcieport 0000:00:1d.3: device [8086:9d1b] error status/mask=00000001/00002000 Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472775] pcieport 0000:00:1d.3: [ 0] Receiver Error (First) Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472789] pcieport 0000:00:1d.3: AER: Corrected error received: id=00eb Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.473451] pcieport 0000:00:1d.3: can't find device of ID00eb>
– Nikolas Chrysanthidis
Mar 18 at 12:05
That looks familiar. Try rebooting withpci=nomsion the kernel command line and see if the error messages become less frequent.
– dsstorefile1
Mar 18 at 20:45
How did you install that latest WiFi drivers? Was it through the Ubuntu repositories or somewhere else?
– dsstorefile1
Mar 14 at 18:03
How did you install that latest WiFi drivers? Was it through the Ubuntu repositories or somewhere else?
– dsstorefile1
Mar 14 at 18:03
It was through repositories. I am writing the commands below.
$ sudo add-apt-repository ppa:hanipouspilot/rtlwifi $ sudo apt-get update $ sudo apt-get install rtlwifi-new-dkms linux-firmware $ sudo reboot $ sudo apt-get install linux-headers-$(uname -r) gcc g++ build-essential dkms git $ cd rtlwifi_new-rock.new_btcoex $ make $ sudo make install $ sudo modprobe -rv rtl8723be ` $ sudo modprobe -v rtl8723be ant_sel=2` $ echo "options rtl8723be ant_sel=2 fwlps=0" | sudo tee /etc/modprobe.d/rtl8723be.conf– Nikolas Chrysanthidis
Mar 14 at 20:42
It was through repositories. I am writing the commands below.
$ sudo add-apt-repository ppa:hanipouspilot/rtlwifi $ sudo apt-get update $ sudo apt-get install rtlwifi-new-dkms linux-firmware $ sudo reboot $ sudo apt-get install linux-headers-$(uname -r) gcc g++ build-essential dkms git $ cd rtlwifi_new-rock.new_btcoex $ make $ sudo make install $ sudo modprobe -rv rtl8723be ` $ sudo modprobe -v rtl8723be ant_sel=2` $ echo "options rtl8723be ant_sel=2 fwlps=0" | sudo tee /etc/modprobe.d/rtl8723be.conf– Nikolas Chrysanthidis
Mar 14 at 20:42
PPAs aren't official sources of software, so you have to be careful. What do the systemd-journal logs contain when the problem occurs? If it's a set of repeating messages, can you post a sample of them on a pastebin so someone can take a look at them?
– dsstorefile1
Mar 16 at 1:42
PPAs aren't official sources of software, so you have to be careful. What do the systemd-journal logs contain when the problem occurs? If it's a set of repeating messages, can you post a sample of them on a pastebin so someone can take a look at them?
– dsstorefile1
Mar 16 at 1:42
<Exactly as you described. This is just a small sample of the created log file. / Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472757] pcieport 0000:00:1d.3: device [8086:9d1b] error status/mask=00000001/00002000 Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472775] pcieport 0000:00:1d.3: [ 0] Receiver Error (First) Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472789] pcieport 0000:00:1d.3: AER: Corrected error received: id=00eb Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.473451] pcieport 0000:00:1d.3: can't find device of ID00eb>
– Nikolas Chrysanthidis
Mar 18 at 12:05
<Exactly as you described. This is just a small sample of the created log file. / Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472757] pcieport 0000:00:1d.3: device [8086:9d1b] error status/mask=00000001/00002000 Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472775] pcieport 0000:00:1d.3: [ 0] Receiver Error (First) Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472789] pcieport 0000:00:1d.3: AER: Corrected error received: id=00eb Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.473451] pcieport 0000:00:1d.3: can't find device of ID00eb>
– Nikolas Chrysanthidis
Mar 18 at 12:05
That looks familiar. Try rebooting with
pci=nomsi on the kernel command line and see if the error messages become less frequent.– dsstorefile1
Mar 18 at 20:45
That looks familiar. Try rebooting with
pci=nomsi on the kernel command line and see if the error messages become less frequent.– dsstorefile1
Mar 18 at 20:45
 |Â
show 5 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
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%2f1014914%2fpanic-kernel-when-my-laptop-is-being-connected-to-a-wifi-network%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
How did you install that latest WiFi drivers? Was it through the Ubuntu repositories or somewhere else?
– dsstorefile1
Mar 14 at 18:03
It was through repositories. I am writing the commands below.
$ sudo add-apt-repository ppa:hanipouspilot/rtlwifi$ sudo apt-get update$ sudo apt-get install rtlwifi-new-dkms linux-firmware$ sudo reboot$ sudo apt-get install linux-headers-$(uname -r) gcc g++ build-essential dkms git$ cd rtlwifi_new-rock.new_btcoex$ make$ sudo make install$ sudo modprobe -rv rtl8723be` $ sudo modprobe -v rtl8723be ant_sel=2`$ echo "options rtl8723be ant_sel=2 fwlps=0" | sudo tee /etc/modprobe.d/rtl8723be.conf– Nikolas Chrysanthidis
Mar 14 at 20:42
PPAs aren't official sources of software, so you have to be careful. What do the systemd-journal logs contain when the problem occurs? If it's a set of repeating messages, can you post a sample of them on a pastebin so someone can take a look at them?
– dsstorefile1
Mar 16 at 1:42
<Exactly as you described. This is just a small sample of the created log file. / Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472757] pcieport 0000:00:1d.3: device [8086:9d1b] error status/mask=00000001/00002000 Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472775] pcieport 0000:00:1d.3: [ 0] Receiver Error (First) Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.472789] pcieport 0000:00:1d.3: AER: Corrected error received: id=00eb Mar 17 09:21:18 nik-HP-Pavilion-Notebook kernel: [ 306.473451] pcieport 0000:00:1d.3: can't find device of ID00eb>
– Nikolas Chrysanthidis
Mar 18 at 12:05
That looks familiar. Try rebooting with
pci=nomsion the kernel command line and see if the error messages become less frequent.– dsstorefile1
Mar 18 at 20:45