You are not logged in.

#1 2018-05-01 00:34:14

seadiem
Member
Registered: 2018-04-30
Posts: 6

Arch box won't boot: PCIe Bus Error: severity=Corrected

So I recently updated my arch install, and I think me forgetting to update grub caused the following problem. Whenever I turn my computer on (i.e. I have no access to its command line or anything), it boots straight to the following error message:

starting version 238
[0.569493] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4(Reciever ID)
[0.570235] pcieport 0000:00:1c.4: device [8086:a294] error status/mask=00002041/00002000
[0.570841] pcieport 0000:00:1c.4: [0] Reciever Error (First)
[0.571330] pcieport 0000:00:1c.4: [6] Bad TLP
/dev/sda2: clean, 317587/13172736 files, 3411899/52660782 blocks


Any help would be greatly appreciated. I've been banging my head against a wall for a while now. Oh, and I do have access to the GRUB bash-like command line, however I have no interaction with my Arch install whatsoever. It would be spectacular if I don't have to reinstall my system. A lot of work went into it.

Offline

#2 2018-05-01 03:22:42

circleface
Member
Registered: 2012-05-26
Posts: 639

Re: Arch box won't boot: PCIe Bus Error: severity=Corrected

Grub is already loaded by that point, so I doubt that is the cause.  On the other hand, what do you mean you "forgot" to update grub?  Grub should be automatically updated when you run a full system upgrade.

More on topic, did you install the microcode updates (if you have an intel processor).

Offline

#3 2018-05-01 03:23:55

seadiem
Member
Registered: 2018-04-30
Posts: 6

Re: Arch box won't boot: PCIe Bus Error: severity=Corrected

Ah. Yeah I didn't realize that I needed to install those. Is there any way to without having an actual command line?

Offline

#4 2018-05-01 03:56:48

circleface
Member
Registered: 2012-05-26
Posts: 639

Re: Arch box won't boot: PCIe Bus Error: severity=Corrected

You can always boot the live media you used to install Arch and chroot in to your system, the same way you did when installing.  Don't do the whole install, just mount the filesystems properly and then arch-chroot.  From there, you will be at a command line inside your installed system.  Make sure you install 'intel-ucode' and then configure it like the wiki says.  Of course, this may not solve your problem, but it may solve future problems.

Offline

#5 2018-05-01 04:12:32

seadiem
Member
Registered: 2018-04-30
Posts: 6

Re: Arch box won't boot: PCIe Bus Error: severity=Corrected

I managed to get into the command line and update intel ucode and the grub config, and nothing. sad

Offline

#6 2018-05-01 04:46:40

seadiem
Member
Registered: 2018-04-30
Posts: 6

Re: Arch box won't boot: PCIe Bus Error: severity=Corrected

SOLVED! It turns out that I must have accidentally updated with pacman -Syu, instead of pacman -Syy, which update my kernel to a version that wasn't compatible with my PCIe ports. After reverting to a previous one with this article [https://wiki.archlinux.org/index.php/Do … g_packages], it worked. Feels freaking great.

Offline

#7 2018-05-01 06:04:40

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,849

Re: Arch box won't boot: PCIe Bus Error: severity=Corrected

Please mark your solved threads by editing your inital posts subject.

For the record: "severity=Corrected" is not a fatal error and not the cause of the failing boot and while the kernel is the most self-contained package, at some point you might run into trouble by stalling it, so I'd suggest to figure the actual problem asap.

Offline

#8 2018-05-01 09:09:57

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,435

Re: Arch box won't boot: PCIe Bus Error: severity=Corrected

I'm also worried about the implications of that statement "accidentally updated with pacman -Syu, instead of pacman -Syy". This is no accident, that's what you should be doing. "Updating" with pacman -Syy and selectively installing packages is guaranteed to lead into issues. Hold back the kernel if you must, it's one of the few packages with little repercussions to do so, but thinking that updating with -Syu is an "accident" is absolutely wrong, get rid of that mindset.

Offline

Board footer

Powered by FluxBB