You are not logged in.

Pages: 1 2 3

#51 2012-03-28 15:36:12

FreeTheBee
Member
Registered: 2011-01-02
Posts: 125

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

I just ran into this problem with a Gigabyte Z68-UD3H-B3 and kernel 3.2.13. The pice_aspm=force workaround, does its job for me.

Finding this thread was a great relieve, I hadn't updated my system in 2 months (no internet for a while), so I expected to have some problems finding a solution since I just updated 450 packages smile I didn't expect to have it fixed in less than 30 minutes.

Offline

#52 2012-03-28 16:02:32

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,643
Website

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

Someone should update the wiki with this solution.

CPU-optimized Linux-ck packages @ Repo-ck  • AUR packages • Zsh and other configs

Offline

#53 2012-03-28 16:27:50

serg36
Member
Registered: 2012-03-28
Posts: 1

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

Same problem on Gigabyte GA-P67A-UD4-B3, BIOS F7
pcie_aspm=force solve the problem for me too.

Offline

#54 2012-03-29 21:18:58

pepedopolous
Member
Registered: 2012-02-12
Posts: 86

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

Hmm...

Ubuntu claim that their latest kernel contains a fix (3.2.20-13)

However, I still have the same kernel panic whether I use pcie_aspm=force or not.

Arch is OK if I hold the kernel at 3.2.1-1.

Maybe I have a different problem? Any idea how to get any useful information from kernel panics?

Offline

#55 2012-03-30 12:15:14

krigun
Member
From: Norway
Registered: 2005-06-06
Posts: 122
Website

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

pepedopolous wrote:

Maybe I have a different problem? Any idea how to get any useful information from kernel panics?

There are several ways of doing this, none of which are very simple, but if you have the required equipment (such as a serial port OR USB serial dongle, some cables, extra PC, etc), then you probably get the full kernel panic message using a serial console. Its relatively simple to set up once you have all the required hardware (which I don't). See: https://wiki.ubuntu.com/Kernel/KernelDe … al_Console

Not sure if the archlinux kernel has these enabled or not:

CONFIG_USB_SERIAL_CONSOLE
CONFIG_USB_SERIAL
CONFIG_USB_SERIAL_PL2303

Given that we are all on newer motherboards, you definately need at least the USB serial dongle. If you have an old laptop or something that has a serial port, then you should be good to go.

Last edited by krigun (2012-03-30 12:24:09)

Offline

#56 2012-04-01 16:44:33

krigun
Member
From: Norway
Registered: 2005-06-06
Posts: 122
Website

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

FYI - The kernel bug report regarding this issue was just closed as fixed.

Offline

#57 2012-04-01 20:18:15

Lenry
Member
From: Szeged, Hungary
Registered: 2010-03-27
Posts: 64
Website

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

krigun wrote:

FYI - The kernel bug report regarding this issue was just closed as fixed.

great. I hope it will be included in the next release

Offline

#58 2012-04-02 03:08:52

Fixo
Member
Registered: 2012-04-01
Posts: 5

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

Gigabyte Z68XP-UD3 here too. Same problem.

Offline

#59 2012-04-02 09:11:20

Lenry
Member
From: Szeged, Hungary
Registered: 2010-03-27
Posts: 64
Website

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

Fixo wrote:

Gigabyte Z68XP-UD3 here too. Same problem.

did the workaround worked for you?

Offline

#60 2012-04-02 15:52:32

Fixo
Member
Registered: 2012-04-01
Posts: 5

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

yes! worked, thank you. But once the problem is fixed, we must erase it, right?

Offline

#61 2012-04-02 19:00:03

akspecs
Member
Registered: 2012-02-11
Posts: 179

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

Fixo wrote:

yes! worked, thank you. But once the problem is fixed, we must erase it, right?

Assuming the patch for the fix is included with the mainline kernel, yes.  If not, you either keep that parameter or patch the kernel and compile it yourself (if you want to remove that parameter).

Offline

#62 2012-04-03 20:28:52

krigun
Member
From: Norway
Registered: 2005-06-06
Posts: 122
Website

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

That was fast - merged into 3.2.14 and 3.3.1 - http://www.kernel.org/pub/linux/kernel/ … Log-3.2.14

So it should work now.

    Linux 3.2.14

commit e277a09f64ac659407582c2182b245afa66dcebc
Author: Matthew Garrett <mjg@redhat.com>
Date:   Tue Mar 27 10:17:41 2012 -0400

    ASPM: Fix pcie devices with non-pcie children
    
    commit c9651e70ad0aa499814817cbf3cc1d0b806ed3a1 upstream.
    
    Since 3.2.12 and 3.3, some systems are failing to boot with a BUG_ON.
    Some other systems using the pata_jmicron driver fail to boot because no
    disks are detected.  Passing pcie_aspm=force on the kernel command line
    works around it.
    
    The cause: commit 4949be16822e ("PCI: ignore pre-1.1 ASPM quirking when
    ASPM is disabled") changed the behaviour of pcie_aspm_sanity_check() to
    always return 0 if aspm is disabled, in order to avoid cases where we
    changed ASPM state on pre-PCIe 1.1 devices.
    
    This skipped the secondary function of pcie_aspm_sanity_check which was
    to avoid us enabling ASPM on devices that had non-PCIe children, causing
    trouble later on.  Move the aspm_disabled check so we continue to honour
    that scenario.
    
    Addresses https://bugzilla.kernel.org/show_bug.cgi?id=42979 and
              http://bugs.debian.org/665420
    
    Reported-by: Romain Francoise <romain@orebokech.com> # kernel panic
    Reported-by: Chris Holland <bandidoirlandes@gmail.com> # disk detection trouble
    Signed-off-by: Matthew Garrett <mjg@redhat.com>
    Tested-by: Hatem Masmoudi <hatem.masmoudi@gmail.com> # Dell Latitude E5520
    Tested-by: janek <jan0x6c@gmail.com> # pata_jmicron with JMB362/JMB363
    [jn: with more symptoms in log message]
    Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

and

Linux 3.3.1

commit bc67f4a645796ad57ccd10f2814d0cb5ddd8fb4b
Author: Matthew Garrett <mjg@redhat.com>
Date:   Tue Mar 27 10:17:41 2012 -0400

    ASPM: Fix pcie devices with non-pcie children

Last edited by krigun (2012-04-03 20:32:26)

Offline

#63 2012-04-04 04:46:09

akspecs
Member
Registered: 2012-02-11
Posts: 179

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

krigun wrote:

That was fast - merged into 3.2.14 and 3.3.1 - http://www.kernel.org/pub/linux/kernel/ … Log-3.2.14

So it should work now.

    Linux 3.2.14

commit e277a09f64ac659407582c2182b245afa66dcebc
Author: Matthew Garrett <mjg@redhat.com>
Date:   Tue Mar 27 10:17:41 2012 -0400

    ASPM: Fix pcie devices with non-pcie children
    
    commit c9651e70ad0aa499814817cbf3cc1d0b806ed3a1 upstream.
    
    Since 3.2.12 and 3.3, some systems are failing to boot with a BUG_ON.
    Some other systems using the pata_jmicron driver fail to boot because no
    disks are detected.  Passing pcie_aspm=force on the kernel command line
    works around it.
    
    The cause: commit 4949be16822e ("PCI: ignore pre-1.1 ASPM quirking when
    ASPM is disabled") changed the behaviour of pcie_aspm_sanity_check() to
    always return 0 if aspm is disabled, in order to avoid cases where we
    changed ASPM state on pre-PCIe 1.1 devices.
    
    This skipped the secondary function of pcie_aspm_sanity_check which was
    to avoid us enabling ASPM on devices that had non-PCIe children, causing
    trouble later on.  Move the aspm_disabled check so we continue to honour
    that scenario.
    
    Addresses https://bugzilla.kernel.org/show_bug.cgi?id=42979 and
              http://bugs.debian.org/665420
    
    Reported-by: Romain Francoise <romain@orebokech.com> # kernel panic
    Reported-by: Chris Holland <bandidoirlandes@gmail.com> # disk detection trouble
    Signed-off-by: Matthew Garrett <mjg@redhat.com>
    Tested-by: Hatem Masmoudi <hatem.masmoudi@gmail.com> # Dell Latitude E5520
    Tested-by: janek <jan0x6c@gmail.com> # pata_jmicron with JMB362/JMB363
    [jn: with more symptoms in log message]
    Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

and

Linux 3.3.1

commit bc67f4a645796ad57ccd10f2814d0cb5ddd8fb4b
Author: Matthew Garrett <mjg@redhat.com>
Date:   Tue Mar 27 10:17:41 2012 -0400

    ASPM: Fix pcie devices with non-pcie children

I can confirm that it works (currently running 3.2.14).  This is an example of the beauty of kernel.org and it's open source success.

Last edited by akspecs (2012-04-04 04:47:05)

Offline

#64 2012-04-04 08:21:58

krigun
Member
From: Norway
Registered: 2005-06-06
Posts: 122
Website

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

akspecs wrote:

I can confirm that it works (currently running 3.2.14).  This is an example of the beauty of kernel.org and it's open source success.

Excellent! Great work from the kernel devs - again. So ultimately this issue is limited to kernel versions 3.2.12, 3.2.13, and 3.3.0.

Offline

Pages: 1 2 3

Board footer

Powered by FluxBB