Unexpected Shutdowns

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
User avatar
SMG
Level 5
Level 5
Posts: 713
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Unexpected Shutdowns

Post by SMG »

Maybe you need to use a "Novo" button to change boot order on UEFI? Change boot order/boot from usb ideapad 320s ,insideh20 ver 5,options greyed out.

I do not know enough about your model laptop to know if "Novo" applies.
LM20.0 Cinnamon
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

My notebook does not have a "Novo" Button - I think.

I don't know too much about UEFI/Legacy but doesn't the boot order apply to both modes?
1000
Level 3
Level 3
Posts: 128
Joined: Wed Jul 29, 2020 2:14 am

Re: Unexpected Shutdowns

Post by 1000 »

For me working something like this

Code: Select all

sudo dd if=/home/user/Download/FD12FULL/FD12FULL.img of=/dev/sdd
dd copied .img file to my sdd pendrive.
And now I have Fat16 partition on pendrive.
There is not enough space on this partition. :(
I need resize or create next partition for Bios.

After reboot I see info about install Freedos, YES / NO
I write NO and I see black screen with DOS.
Something similar

Code: Select all

C\:>_
Has anyone seen any tutorial on how to run Bios install from FreeDOS / DOS ?
User avatar
SMG
Level 5
Level 5
Posts: 713
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Unexpected Shutdowns

Post by SMG »

omg_me wrote:
Sat Sep 12, 2020 2:36 pm
My notebook does not have a "Novo" Button - I think.
This link Factory reset a Lenovo V330-15lbk model 81AX using NOVA button indicates it is a button on the side?
omg_me wrote:
Sat Sep 12, 2020 2:36 pm
I don't know too much about UEFI/Legacy but doesn't the boot order apply to both modes?
I have a computer that came out in the very early stages of UEFI and it's UEFI is listed as "experimental", so I've never really used it. However, in my BIOS, the boot order for legacy is separate from the boot order for UEFI.
LM20.0 Cinnamon
User avatar
SMG
Level 5
Level 5
Posts: 713
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Unexpected Shutdowns

Post by SMG »

Here's some more details on the Novo button. Introduction to NOVO button - ideapad. Apparently it can be something different on different models?
LM20.0 Cinnamon
User avatar
SMG
Level 5
Level 5
Posts: 713
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Unexpected Shutdowns

Post by SMG »

1000 wrote:
Sat Sep 12, 2020 2:36 pm
Has anyone seen any tutorial on how to run Bios install from FreeDOS / DOS ?
The first post in this thread How to upgrade your system BIOS using FreeDOS links to this webpage How to upgrade your system BIOS using FreeDOS.

Edited to add: The first comment from Nikos on this page 5 Tools to Easily Install FreeDOS or MS-DOS onto USB for BIOS Flashing indicates "On UEFI motherboards, to boot into FreeDOS, you need to activate the Compatibility Support Module (CSM), which enabled BIOS features in UEFI. Also, in Secure Boot options, select “Other OS”.

If you installed Windows while in UEFI mode, don’t forget to revert the aforementioned UEFI settings back, before you reboot into Windows, to prevent unpredictable problems."
Last edited by SMG on Sat Sep 12, 2020 3:06 pm, edited 1 time in total.
LM20.0 Cinnamon
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

You are right, sorry. I never took a closer look at my notebook. I had to turn on some lights, but indeed, there is a button I could press with a pencil or so.

Funny enough,
1000 wrote:
Sat Sep 12, 2020 2:36 pm
For me working something like this

Code: Select all

sudo dd if=/home/user/Download/FD12FULL/FD12FULL.img of=/dev/sdd
dd copied .img file to my sdd pendrive.
And now I have Fat16 partition on pendrive.
There is not enough space on this partition. :(
I need resize or create next partition for Bios.

After reboot I see info about install Freedos, YES / NO
I write NO and I see black screen with DOS.
Something similar

Code: Select all

C\:>_
Has anyone seen any tutorial on how to run Bios install from FreeDOS / DOS ?
that worked for me as well. I was able to boot into FreeDos with a USB prepared like that. But I'm not sure what I did differently this time compared to what was mentioned here:
asinoro wrote:
Sat Sep 12, 2020 5:20 am
Use the whole usb and write it with the command:

Code: Select all

sudo  dd status=progress  bs=4096 if=/location of your iso/linuxmint.iso  of= /dev/sdx ; sync  
Where sdx the location of your usb.
I think I can add the BIOS update onto the drive and then run it from within the FreeDOS, correct?
1000
Level 3
Level 3
Posts: 128
Joined: Wed Jul 29, 2020 2:14 am

Re: Unexpected Shutdowns

Post by 1000 »

My notebook does not have a "Novo" Button - I think.
It is very possible that you are right. Especially if you have GRUB installed.
I don't remember exactly, but I installed a system a long time ago. New system overwritten something.
I did not find on the manufacturer's website how to restore the original bootloader.
I want to say that if you are talking about a special button on the keyboard, it is somehow related to a hidden partition on the disk.
And if something is gone it won't work.
This happens after the installation of the system, other than from the recovery partition.
Certain manufacturers allow you to back up your original system on some models.
But this copy is clean and can also break the button.
My English is not perfect, but maybe someone understood something. :D
Edit.
Other way , you can check with legacy or uefi mode.
1000
Level 3
Level 3
Posts: 128
Joined: Wed Jul 29, 2020 2:14 am

Re: Unexpected Shutdowns

Post by 1000 »

I think I can add the BIOS update onto the drive and then run it from within the FreeDOS, correct?
Yes, if if it fits on a pendrive.
You need have .exe file unpacked there.

Command inside DOS

Code: Select all

dir
Will show files and folders.
Probably you need write name_of_file.exe and click Enter.
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

Dead end... (unless someone objects)

Tried to run the .exe, but FreeDOS says "This program must be run under Win32".

Will have another look at the possible options tomorrow...
User avatar
SMG
Level 5
Level 5
Posts: 713
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Unexpected Shutdowns

Post by SMG »

Always good to take breaks.

Here is a possible idea for your next venture into BIOS updating Flash your Lenovo Ideapad laptop BIOS from Linux using UEFI capsule updates.
LM20.0 Cinnamon
1000
Level 3
Level 3
Posts: 128
Joined: Wed Jul 29, 2020 2:14 am

Re: Unexpected Shutdowns

Post by 1000 »

I had problem write correct name, so I changed file name in Linux Mint.
I tried again.
Bios update works for me. But I have hardware from other manufacturer.

I have also other hardware also other manufacturer and there I need only copy file to Fat partition on pendrive.
From Bios settings I can choose file and update Bios.

In your case, I don't see much of a choice.
This is your README file to update Bios https://download.lenovo.com/consumer/mo ... cn51ww.txt
And this is a separate guide of the manufacturer https://support.lenovo.com/us/en/soluti ... 00008#Auto

I saw on the internet also suggestions Bios update from hirensbootcd.
But I have to warn you.
- Convenient, but I don't know if it will works.
- Additional software inside may be legal, but the system W. 10 PE not necessarily.
Depending on the license, the manufacturer could forbid system modification and distribution.
- And also I do not know how safe this such a system is.

A long time ago I saw a program to modify an ISO file and to add your own programs, but I don't know if it still exists.
But external program this is also some risk of installing a malicious virus.

SMG tip above looks a little safer because innoextract is open source and exist in Linux Mint repository.

Edit.
For other people and maybe for yourself.
You can write a request to the manufacturer about support Bios update from USB because you use Linux. :D
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

SMG wrote:
Sat Sep 12, 2020 5:35 pm
Always good to take breaks.

Here is a possible idea for your next venture into BIOS updating Flash your Lenovo Ideapad laptop BIOS from Linux using UEFI capsule updates.
Wow, that is a really nice guide. Thank you.

So, i followed the guide until Step 3, and

Code: Select all

sudo fwupdate -a {e20bafd3-9914-4f4f-9537-3129e090eb3c} ./6SCN51WW.CAP
Works without error, but the followed validation step worries me, as I don't get a clean "pending update".

Code: Select all

$sudo fwupdate -iv
(fwupdate:3468): FuDevice-DEBUG: 08:56:17.537: using 4be1d82544d8b1332b6189d4368d1e5a03e4883c for UEFI-e20bafd3-9914-4f4f-9537-3129e090eb3c-dev0
(fwupdate:3468): GLib-GIO-DEBUG: 08:56:17.538: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
failed: Error opening file /sys/firmware/efi/efivars/fwupd-e20bafd3-9914-4f4f-9537-3129e090eb3c-0-0abba7dc-e516-4167-bbf5-4d9d1c739416: No such file or directory
Should I try to continue or is this the time to abort? :roll:

EDIT:
Ok, i had a look at the /sys/firmware/efi/efivars/ and there was a file fwupd-{e20bafd3-9914-4f4f-9537-3129e090eb3c}-0-0abba7dc-e516-4167-bbf5-4d9d1c739416. So I rerun with

Code: Select all

sudo fwupdate -a e20bafd3-9914-4f4f-9537-3129e090eb3c ./6SCN51WW.CAP
and now sudo fwupdate -i looks better:

Code: Select all

Information for the update status entry 0:
  Information Version: 7
  Firmware GUID: {e20bafd3-9914-4f4f-9537-3129e090eb3c}
  Capsule Flags: 0x00000000x
  Hardware Instance: 0
  Update Status: attempt-update
  Capsule File Path: /EFI/ubuntu/fw/fwupd-e20bafd3-9914-4f4f-9537-3129e090eb3c.cap
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

Worked nicely (although the BIOS beeps were a little bit worrying :P).

Thank you all for your extensive help! I hope with the BIOS update the unexpected shutdowns will stop to occur (although during the last two days none occurred anyway - let's hope it will stay that way).
1000
Level 3
Level 3
Posts: 128
Joined: Wed Jul 29, 2020 2:14 am

Re: Unexpected Shutdowns

Post by 1000 »

Check logs again for example like this.

Code: Select all

dmesg -l emerg,alert,crit,err

Code: Select all

journalctl -b0 | grep -Ei "error|fail"
These commands will not show the whole log, only fragments.
There will also be spam in the output.

For example.

Code: Select all

$ journalctl -b0 | grep -Ei "error|fail" | nl
     1	wrz 13 10:13:46 user kernel: RAS: Correctable Errors collector initialized.
     2	wrz 13 10:13:46 user kernel: EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
     3	wrz 13 10:13:47 user kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
     4	wrz 13 10:13:50 user systemd[1]: Starting GRUB failed boot detection...
     5	wrz 13 10:13:50 user systemd[1]: Finished GRUB failed boot detection.
     6	wrz 13 10:13:50 user smartd[958]: Device: /dev/sda [SAT], no SMART Error Log, ignoring -l error (override with -T permissive)
     7	wrz 13 10:13:53 user smartd[958]: Device: /dev/sdc [SAT], SMART Prefailure Attribute: 3 Spin_Up_Time changed from 174 to 175
Command nl will add number of line in this way :D
- Lines 1, 2 , 4, 5, 7 this is only information for me.
Edit: Maybe on line 7 I have to be careful, because it shows that the disk is slowly wearing out.
- Line 3 it doesn't matter for me, because I am using " legacy mode " instead UEFI in Bios.
- Line 6 is about smartmontools app (this is smartd). After opening the whole log, I saw more details there.
Smartmontools not support my /dev/sda hard drive because " not found in smartd database "
User avatar
SMG
Level 5
Level 5
Posts: 713
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Unexpected Shutdowns

Post by SMG »

omg_me wrote:
Sun Sep 13, 2020 3:35 am
Worked nicely (although the BIOS beeps were a little bit worrying :P).

Thank you all for your extensive help! I hope with the BIOS update the unexpected shutdowns will stop to occur (although during the last two days none occurred anyway - let's hope it will stay that way).
There was this special step in the process, "Hold your breath during the actual flashing procedure." :lol:
I think we all breathe a little easier when the computer boots up successfully after a BIOS update.

Glad it worked and hopefully that will address the issue.
LM20.0 Cinnamon
1000
Level 3
Level 3
Posts: 128
Joined: Wed Jul 29, 2020 2:14 am

Re: Unexpected Shutdowns

Post by 1000 »

You can also test command

Code: Select all

journalctl -xb0 -p emerg..err
In man journalctl is hard to see, viewtopic.php?p=1877514#p1877514
but two dots are the range in this case,
so " journalctl -xb0 -p emerg..debug "will show entire log.
( But it's colorful and it's easier to find a error :D )
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

Although it looked good until now, I just had another shutdown.

Any ideas what to look at next?
User avatar
SMG
Level 5
Level 5
Posts: 713
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Unexpected Shutdowns

Post by SMG »

What do the errors in syslog prior to the shutdown look like for this time?
LM20.0 Cinnamon
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

Pretty much the same, except that my temp logging is put there as well, unless I missed something:

Code: Select all

Sep 16 13:29:59 gam0r-PC kernel: [13509.019862] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:29:59 gam0r-PC kernel: [13509.019876] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:29:59 gam0r-PC kernel: [13509.019886] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:29:59 gam0r-PC kernel: [13509.019892] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:29:59 gam0r-PC kernel: [13509.021286] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:29:59 gam0r-PC kernel: [13509.021298] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:29:59 gam0r-PC kernel: [13509.021307] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:29:59 gam0r-PC kernel: [13509.021313] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:00 gam0r-PC kernel: [13509.870546] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:00 gam0r-PC kernel: [13509.870552] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:00 gam0r-PC kernel: [13509.870555] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:00 gam0r-PC kernel: [13509.870557] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:01 gam0r-PC CRON[21408]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Sep 16 13:30:01 gam0r-PC CRON[21409]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 16 13:30:01 gam0r-PC kernel: [13511.034501] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:01 gam0r-PC kernel: [13511.034507] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:01 gam0r-PC kernel: [13511.034510] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:01 gam0r-PC kernel: [13511.034512] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:02 gam0r-PC kernel: [13511.873942] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:02 gam0r-PC kernel: [13511.873947] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:02 gam0r-PC kernel: [13511.873950] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:02 gam0r-PC kernel: [13511.873952] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:05 gam0r-PC kernel: [13514.592706] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:05 gam0r-PC kernel: [13514.592720] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:05 gam0r-PC kernel: [13514.592730] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:05 gam0r-PC kernel: [13514.592736] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:05 gam0r-PC kernel: [13515.019558] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:05 gam0r-PC kernel: [13515.019571] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:05 gam0r-PC kernel: [13515.019581] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:05 gam0r-PC kernel: [13515.019587] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:07 gam0r-PC kernel: [13516.939173] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:07 gam0r-PC kernel: [13516.939179] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:07 gam0r-PC kernel: [13516.939182] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:07 gam0r-PC kernel: [13516.939185] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:08 gam0r-PC kernel: [13517.882028] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:08 gam0r-PC kernel: [13517.882033] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:08 gam0r-PC kernel: [13517.882037] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:08 gam0r-PC kernel: [13517.882038] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:10 gam0r-PC kernel: [13519.885237] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:10 gam0r-PC kernel: [13519.885242] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:10 gam0r-PC kernel: [13519.885245] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:10 gam0r-PC kernel: [13519.885247] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:11 gam0r-PC kernel: [13521.020327] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:11 gam0r-PC kernel: [13521.020340] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:11 gam0r-PC kernel: [13521.020350] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:11 gam0r-PC kernel: [13521.020357] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:12 gam0r-PC kernel: [13521.891835] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:12 gam0r-PC kernel: [13521.891847] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:12 gam0r-PC kernel: [13521.891857] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:12 gam0r-PC kernel: [13521.891863] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:15 gam0r-PC kernel: [13524.576931] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:15 gam0r-PC kernel: [13524.576945] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:15 gam0r-PC kernel: [13524.576955] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:15 gam0r-PC kernel: [13524.576961] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:16 gam0r-PC kernel: [13525.893029] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:16 gam0r-PC kernel: [13525.893035] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:16 gam0r-PC kernel: [13525.893038] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:16 gam0r-PC kernel: [13525.893040] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:17 gam0r-PC kernel: [13527.017056] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:17 gam0r-PC kernel: [13527.017070] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:17 gam0r-PC kernel: [13527.017081] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:17 gam0r-PC kernel: [13527.017088] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:17 gam0r-PC kernel: [13527.018161] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:17 gam0r-PC kernel: [13527.018175] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:17 gam0r-PC kernel: [13527.018186] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:17 gam0r-PC kernel: [13527.018193] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:18 gam0r-PC kernel: [13527.441893] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:18 gam0r-PC kernel: [13527.441912] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:18 gam0r-PC kernel: [13527.441926] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:18 gam0r-PC kernel: [13527.441936] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:18 gam0r-PC kernel: [13527.895242] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:18 gam0r-PC kernel: [13527.895248] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:18 gam0r-PC kernel: [13527.895252] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:18 gam0r-PC kernel: [13527.895254] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:23 gam0r-PC kernel: [13533.019633] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:23 gam0r-PC kernel: [13533.019646] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:23 gam0r-PC kernel: [13533.019656] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:23 gam0r-PC kernel: [13533.019662] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:24 gam0r-PC kernel: [13533.903241] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:24 gam0r-PC kernel: [13533.903247] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Sep 16 13:30:24 gam0r-PC kernel: [13533.903252] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000040/00002000
Sep 16 13:30:24 gam0r-PC kernel: [13533.903254] pcieport 0000:00:1c.4: AER:    [ 6] BadTLP                
Sep 16 13:30:26 gam0r-PC kernel: [13535.905434] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:26 gam0r-PC kernel: [13535.905440] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:26 gam0r-PC kernel: [13535.905443] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:26 gam0r-PC kernel: [13535.905445] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:28 gam0r-PC kernel: [13537.908316] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:28 gam0r-PC kernel: [13537.908321] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:28 gam0r-PC kernel: [13537.908324] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:28 gam0r-PC kernel: [13537.908326] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:30 gam0r-PC kernel: [13539.424888] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:30 gam0r-PC kernel: [13539.424902] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:30 gam0r-PC kernel: [13539.424912] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:30 gam0r-PC kernel: [13539.424918] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:32 gam0r-PC kernel: [13541.914234] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:32 gam0r-PC kernel: [13541.914240] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:32 gam0r-PC kernel: [13541.914244] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:32 gam0r-PC kernel: [13541.914247] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:35 gam0r-PC kernel: [13545.018662] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:35 gam0r-PC kernel: [13545.018675] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:35 gam0r-PC kernel: [13545.018685] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:35 gam0r-PC kernel: [13545.018691] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:36 gam0r-PC kernel: [13545.632911] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:36 gam0r-PC kernel: [13545.632924] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:36 gam0r-PC kernel: [13545.632934] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:36 gam0r-PC kernel: [13545.632940] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:38 gam0r-PC kernel: [13547.921627] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:38 gam0r-PC kernel: [13547.921632] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:38 gam0r-PC kernel: [13547.921635] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:38 gam0r-PC kernel: [13547.921637] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:40 gam0r-PC kernel: [13549.665079] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:40 gam0r-PC kernel: [13549.665092] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:40 gam0r-PC kernel: [13549.665102] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:40 gam0r-PC kernel: [13549.665108] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:40 gam0r-PC kernel: [13549.920596] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:40 gam0r-PC kernel: [13549.920609] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:40 gam0r-PC kernel: [13549.920619] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:40 gam0r-PC kernel: [13549.920625] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:42 gam0r-PC kernel: [13551.926878] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:42 gam0r-PC kernel: [13551.926883] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:42 gam0r-PC kernel: [13551.926887] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:42 gam0r-PC kernel: [13551.926889] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:42 gam0r-PC rtkit-daemon[1083]: Supervising 6 threads of 4 processes of 1 users.
Sep 16 13:30:42 gam0r-PC rtkit-daemon[1083]: Successfully made thread 21420 of process 1242 owned by '1000' RT at priority 5.
Sep 16 13:30:42 gam0r-PC rtkit-daemon[1083]: Supervising 7 threads of 4 processes of 1 users.
Sep 16 13:30:42 gam0r-PC rtkit-daemon[1083]: Supervising 6 threads of 4 processes of 1 users.
Sep 16 13:30:42 gam0r-PC rtkit-daemon[1083]: Successfully made thread 21421 of process 1242 owned by '1000' RT at priority 5.
Sep 16 13:30:42 gam0r-PC rtkit-daemon[1083]: Supervising 7 threads of 4 processes of 1 users.
Sep 16 13:30:47 gam0r-PC kernel: [13557.019432] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:47 gam0r-PC kernel: [13557.019445] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:47 gam0r-PC kernel: [13557.019455] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:47 gam0r-PC kernel: [13557.019461] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:47 gam0r-PC kernel: [13557.020375] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:47 gam0r-PC kernel: [13557.020387] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:47 gam0r-PC kernel: [13557.020397] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:47 gam0r-PC kernel: [13557.020402] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:48 gam0r-PC kernel: [13557.934868] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:48 gam0r-PC kernel: [13557.934874] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:48 gam0r-PC kernel: [13557.934877] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:48 gam0r-PC kernel: [13557.934879] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 13:30:50 gam0r-PC kernel: [13559.937706] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Sep 16 13:30:50 gam0r-PC kernel: [13559.937711] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 13:30:50 gam0r-PC kernel: [13559.937715] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Sep 16 13:30:50 gam0r-PC kernel: [13559.937717] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Sep 16 14:12:36 gam0r-PC systemd-modules-load[530]: Inserted module 'lp'
Post Reply

Return to “Newbie Questions”