[SOLVED] Unable to boot after upgrade to kernel 3.2.12

Lampus · 2012-03-23 17:05:52

Now I can see very strange behavior: kernel 3.2.12 boots fine without any additional kernel parameters like pcie_aspm=force.
And now I have no any idea how to reproduce this bug.
It's very strange...

Leonid.I · 2012-03-23 20:54:09

Does disabling aspm (pcie_aspm=off) help as well?

gr2mx · 2012-03-24 10:22:11

Leonid.I wrote:

Does disabling aspm (pcie_aspm=off) help as well?

It did the trick for me.

Last edited by gr2mx (2012-03-24 11:32:45)

akspecs · 2012-03-25 06:42:39

Having the same problem. My system freezes at loading ramdisk. Running on a Z68X-UD3H-B3 motherboard. I'll try these parameters mentioned previously and post back with my results.

Ecrelinf · 2012-03-25 07:42:11

pcie_aspm=off
dont works for me, boot hanged
pcie_aspm=force
Boot Ok

akspecs · 2012-03-25 09:32:43

Ecrelinf wrote:

pcie_aspm=off
dont works for me, boot hanged
pcie_aspm=force
Boot Ok

I can say the same. The same is true on the recent LTS kernel update as well. I wish I had searched for this thread prior to doing a reinstall

niqingliang2003 · 2012-03-25 10:08:05

same problem with ASUS's P8H67 / i5-2300 / dataland 6870.

I have downgraded the linux to 3.2.6.

gabriel9 · 2012-03-25 13:10:06

Same problem was on my machine, and one member pointed me to this thread. This is bad to say but i am glad to see that i am not alone in this. Thanks for workaround.

pepedopolous · 2012-03-25 15:21:02

I've tried the workaround pcie_aspm=force and I still can't boot if I use any kernel above 3.2.1-1 on ARCH or indeed 3.2.0-17 on my Ubuntu partition. Suppose I could try pcie_aspm=off?

I'm using a Dell Studio XPS 13 laptop. Strange, had high hopes for the workaround which seems to work for everyone else who's reported..

Finest Bug · 2012-03-25 19:52:23

Hello,

I have this issue, too. I've noticed by upgrading to linux 3.2.12.
No problem, I thought, and booted linux-lts 3.0.24.
But then after the update I made stupidly to linux-lts 3.0.25 the problem appears with the lts kernel, too.

I downgraded to linux 3.2.11 for now.

Your Finest Bug

cookiecaper · 2012-03-26 00:12:44

FYI this manifested a bit differently for me. I didn't get a visible kernel panic/backtrace (probably because of my GRUB2 VGA settings) and I had assumed the problem was related to the recent GRUB2 updates I saw happen. The boot process would proceed past the menu and then I would just sit on a completely blank black screen. No input from the keyboard was accepted (though I didn't try sysrq). So I spent some time trying to rebuild my GRUB2 conf and reinstall it to no avail.

Then I found this thread and tried pcie_aspm=force which allowed me to boot successfully. At first I thought it wasn't applicable since someone said the problem didn't affect newer boards -- I have a P67A-UD7-B3.

moscar · 2012-03-26 02:23:53

I have a GA-Z68AP-D3 and tried to boot with both BIOS version F6 and F7 neither worked. pcie_aspm=force worked in both cases and I downgraded to 3.2.11 for now.

Lenry · 2012-03-26 09:28:36

anybody upgraded to 3.2.13? does it solve the problem?

krigun · 2012-03-26 10:48:30

Lenry wrote:

anybody upgraded to 3.2.13? does it solve the problem?

I ran into the same problem with 3.3 as well, so I doubt it works in 3.2.13.. Could not find anything about this in the changelog either

Last edited by krigun (2012-03-26 10:50:16)

krigun · 2012-03-26 11:12:38

Again, HERE is the official kernel bug report. Supposedly the supplied patch fixes this issue. Unverified by me, but you could attempt to recompile the arch kernel with the supplied patch.

EDIT: Noticed that the bug report does not contain any patch, but describes the commit that caused the problem. Basically you need to revert this:

f043ddb60c84ea64a23b755004572afe922e653c PCI: ignore pre-1.1 ASPM
quirking when ASPM is disabled
diff --git a/drivers/pci/pcie/aspm.c b/drivers/pci/pcie/aspm.c
index 1cfbf22..24f049e 100644
--- a/drivers/pci/pcie/aspm.c
+++ b/drivers/pci/pcie/aspm.c
@@ -500,6 +500,9 @@ static int pcie_aspm_sanity_check(struct pci_dev *pdev)
        int pos;
        u32 reg32;

+ if (aspm_disabled)
+ return 0;
+

Last edited by krigun (2012-03-26 11:16:03)

TripleSpeeder · 2012-03-26 17:25:13

cookiecaper wrote:

FYI this manifested a bit differently for me. I didn't get a visible kernel panic/backtrace (probably because of my GRUB2 VGA settings) and I had assumed the problem was related to the recent GRUB2 updates I saw happen. The boot process would proceed past the menu and then I would just sit on a completely blank black screen. No input from the keyboard was accepted (though I didn't try sysrq). So I spent some time trying to rebuild my GRUB2 conf and reinstall it to no avail.
Then I found this thread and tried pcie_aspm=force which allowed me to boot successfully. At first I thought it wasn't applicable since someone said the problem didn't affect newer boards -- I have a P67A-UD7-B3.

Exactly the same behaviour here, with an Asus P8P67 Board. pcie_aspm=force allowed me to boot again.

krigun · 2012-03-26 17:52:10

cookiecaper wrote:

FYI this manifested a bit differently for me. I didn't get a visible kernel panic/backtrace (probably because of my GRUB2 VGA settings) and I had assumed the problem was related to the recent GRUB2 updates I saw happen. The boot process would proceed past the menu and then I would just sit on a completely blank black screen.

Perhaps you are using loglevel=0 kernel parameter? I bet you see the kernel panic if you use loglevel=7

I know this because I tried loglevel=0, and the screen was just blank

Last edited by krigun (2012-03-26 17:54:14)

fire_dragon · 2012-03-27 11:04:55

pepedopolous wrote:

I've tried the workaround pcie_aspm=force and I still can't boot if I use any kernel above 3.2.1-1 on ARCH or indeed 3.2.0-17 on my Ubuntu partition. Suppose I could try pcie_aspm=off?
I'm using a Dell Studio XPS 13 laptop. Strange, had high hopes for the workaround which seems to work for everyone else who's reported..

If anybody should wonder what the pcie_aspm parameter controls, read this article.
As i read it, enabling or disabling pcie_aspm(whatever's rigth for your machine), shuold in worst case result in a higher power comsumption.
I wouldn't upgrade a production-server, though...

Last edited by fire_dragon (2012-03-27 11:05:18)

Lenry · 2012-03-27 11:14:59

fire_dragon wrote:

...
I wouldn't upgrade a production-server, though...

I did... -_-
Fortunately it's only being restarted once in a week (turned off for the weekend), and during the last week I upgraded my home PC, and find this bug. From that time I don't dare to restart the server at the office, as it is a Sandy Bridge based machine, and forbade everybody else to do such thing...

fire_dragon · 2012-03-27 11:31:27

Lenry wrote:

fire_dragon wrote:
...
I wouldn't upgrade a production-server, though...
I did... -_-
Fortunately it's only being restarted once in a week (turned off for the weekend), and during the last week I upgraded my home PC, and find this bug. From that time I don't dare to restart the server at the office, as it is a Sandy Bridge based machine, and forbade everybody else to do such thing...

Hmmm...
I would set pcie_aspm=force in the bootloader.
There's a fair chance your server will get back online, just in case someone or something boots your server.

Lenry · 2012-03-27 11:36:11

fire_dragon wrote:

Lenry wrote:
fire_dragon wrote:
...
I wouldn't upgrade a production-server, though...
I did... -_-
Fortunately it's only being restarted once in a week (turned off for the weekend), and during the last week I upgraded my home PC, and find this bug. From that time I don't dare to restart the server at the office, as it is a Sandy Bridge based machine, and forbade everybody else to do such thing...
Hmmm...
I would set pcie_aspm=force in the bootloader.
There's a fair chance your server will get back online, just in case someone or something boots your server.

I know, and if something happens, that will be the first thing to try, as it worked at home, but that doesn't work in every occasion, as we can see the example of pepedopolous.

fire_dragon · 2012-03-27 12:00:46

According to the previus link, If you use pcie_aspm=force on a system that don't support it, the system will stop responding.
That could explain the different behavior.
But your are right... I wouldn't trust it blindly either.

akspecs · 2012-03-27 12:36:49

I'm assuming that linux 3.2.13 isn't going to work either considering 3.3 didn't work.

moscar · 2012-03-27 22:02:14

akspecs wrote:

I'm assuming that linux 3.2.13 isn't going to work either considering 3.3 didn't work.

Tried it, did not work..

jac · 2012-03-28 14:17:15

Just reporting in that I, too, have the same issue. The force option is a workaround here. I'm on a Gigabyte P67A-UD7-B3. Looking through this thread, two things have been linked with patches:
a patch to pcie_clear_aspm in drivers/pci/pcie/aspm.c
and a patch to pcie_aspm_sanity_check in the same file

Have either of these been tested/proven to work for anyone?

Arch Linux

#26 2012-03-23 17:05:52

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#27 2012-03-23 20:54:09

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#28 2012-03-24 10:22:11

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#29 2012-03-25 06:42:39

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#30 2012-03-25 07:42:11

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#31 2012-03-25 09:32:43

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#32 2012-03-25 10:08:05

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#33 2012-03-25 13:10:06

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#34 2012-03-25 15:21:02

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#35 2012-03-25 19:52:23

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#36 2012-03-26 00:12:44

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#37 2012-03-26 02:23:53

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#38 2012-03-26 09:28:36

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#39 2012-03-26 10:48:30

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#40 2012-03-26 11:12:38

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#41 2012-03-26 17:25:13

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#42 2012-03-26 17:52:10

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#43 2012-03-27 11:04:55

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#44 2012-03-27 11:14:59

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#45 2012-03-27 11:31:27

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#46 2012-03-27 11:36:11

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#47 2012-03-27 12:00:46

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#48 2012-03-27 12:36:49

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#49 2012-03-27 22:02:14

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

#50 2012-03-28 14:17:15

Re: [SOLVED] Unable to boot after upgrade to kernel 3.2.12

Board footer