This bug was fixed in the package linux - 3.0.0-19.33
---
linux (3.0.0-19.33) oneiric-proposed; urgency=low
[Luis Henriques]
* Release Tracking Bug
- LP: #985736
[ Luis Henriques ]
* SAUCE: ite-cir: postpone ISR registration
- LP: #984387
linux (3.0.0-19.32)
** Branch linked: lp:ubuntu/oneiric-proposed/linux-ti-omap4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications about this
We got confirmation from bug 973111, which is a duplicate on Oneiric,
that the patch for this bug solves the problem (reporter tested both a
kernel with only the patch plus tested the 3.0.0-19.3 release from
-proposed). Thus marking this as verification-done-oneiric. Also we got
confirmation in
Jim Leinweber, or anyone reporting this issue, could you please verify
that the latest kernel (3.0.0-19.32) actually fixes this problem? Thank
you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:ubuntu/lucid-proposed/linux-lts-backport-oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications
** Branch linked: lp:ubuntu/precise-proposed/linux-ti-omap4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications about this
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem ( 3.0.0-19.32). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
** Tags added: verification-needed-oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications about this bug go to:
I can confirm that both the ubuntu 12.04 precise kernel 3.2.0-21.34
and the upstream daily kernel 3.4.0-999.201204040406 boot for my Dell
E5420 laptop without the workaround. Hurrah!
Thanks everyone for the quick and successful work on this.
--
You received this bug notification because you
** Changed in: linux (Ubuntu Oneiric)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications
** Changed in: linux (Ubuntu Oneiric)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage
** Branch linked: lp:ubuntu/linux-armadaxp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications about this bug go to:
** Also affects: linux (Ubuntu Oneiric)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage
** Changed in: linux (Ubuntu Oneiric)
Status: New = In Progress
** Changed in: linux (Ubuntu Oneiric)
Assignee: (unassigned) = Tim Gardner (timg-tpi)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications about this
** Changed in: linux
Status: Unknown = Confirmed
** Changed in: linux
Importance: Critical = Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to
Photo DSC03081.JPG looks like we are jumping to
pcie_aspm_configure_common_clock + 0x25b which seems to be 0xd4b so I
suspect that is the BUG_ON(!pci_is_pcie(child)) statement below:
d4a: c3 retq
d4b: 0f 0b ud2a --
(pre-stable) ASPM: Fix pcie devices with non-pcie children
** Also affects: linux (Ubuntu Precise)
Importance: Critical
Status: Confirmed
** Changed in: linux (Ubuntu Precise)
Status: Confirmed = Fix Committed
** Changed in: linux (Ubuntu Precise)
Assignee: (unassigned) =
** Tags removed: rls-mgr-p-tracking
** Tags added: rls-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications about
We've been working with upstream and we've got a patch that should be
tested. I've put some new kernel .debs in:
http://zinc.canonical.com/~cking/lp-961482
Can you please try these out and see if it works without the
pcie_aspm=force workaround and let us know if it helps.
By the way, kudos to
Yes, that's work fine. Attached the dmeg of my system after logging into
ubuntu.
** Attachment added: dmeg_linux-headers-3.2.0-21.33-aspmfix1.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/961482/+attachment/2949040/+files/dmeg_linux-headers-3.2.0-21.33-aspmfix1.txt
--
You
Thanks for the speedy response Hatem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications about this bug go to:
This bug was fixed in the package linux - 3.2.0-20.33
---
linux (3.2.0-20.33) precise; urgency=low
[ Upstream Kernel Changes ]
* (pre-stable) ASPM: Fix pcie devices with non-pcie children
- LP: #961482
-- Leann Ogasawara leann.ogasaw...@canonical.com Tue, 27 Mar 2012
same on Asus P8Z68-V Gen3.
Ubuntu -20 Kernel and pcie_aspm=force fixed the problem. Details about
my system see 963128
Sorry can't really deep test the issue as the system is out of house and
I only have inexpierenced hands in situ.
--
You received this bug notification because you are a
OK - so to make any real progress with the underlying issue we really
need a full trace of the crash, so I've spun a kernel that will dump out
the stack trace with some delays inserted to allow us to take a few
photos of the stack trace.
The debug kernel .debs can be found in:
** Tags added: blocks-hwcert
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications about this bug go to:
Please find attached the requested picture when the kernel hangs. I hope
that can help
** Attachment added: Kernel Panic 3.2.0-20
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/961482/+attachment/2943353/+files/kernel-panic-3.2.0-20.tar.gz
--
You received this bug notification because
Same problem with 3.2.0-20 on a Gigabyte H61M-S2PV.
Workaround pcie_aspm=force works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To
same on a Gigabyte Z68XP-UD3, duplicate bug: #962510
I too confirm that pcie_aspm=force solves the issue. :D
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to
** Tags added: rls-mgr-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications about this bug go to:
Same problem on my Gigabyte GA-Z68X-UD3H-B3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications about this bug go to:
Same problem on my Gigabyte GA-Z68X-UD3H-B3
Kernel 3.2.0-20
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications about this
Same problem using Kernel 3.2.0-19 and kernel 3.2.0-20 amd64 on 12.04
LTS.
DELL Latitude E5520.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
The LKML discussion was along the lines I anticipated: evidently
different subsets of machines crash with and without the patch, leaving
the poor kernel maintainers with a dilemma. Clearly a more complex if
condition is called for, if only what it needs to be can be worked out.
I presume it's
A possible workaround is to boot with the kernel parameter:
pcie_aspm=force
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage
Yes, pcie_aspm=force let's me boot kernels such as 3.3.0 on that Dell
E5420 laptop. So I can confirm the workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel
Just tried the workaround on my ASUS P8Z68-V PRO and it works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications about this
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
The 3.2.0-20 kernel is out. Can you see if you have the same issue
booting this kernel?
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: linux (Ubuntu)
Importance: High = Critical
** Tags removed: needs-upstream-testing
--
You received this bug
It would be good to first identify which mainline kernel introduce the
regression. The 3.2.0-18.28 kernel was based off of upstream 3.2.9. The
3.2.0-19.31 kernel was rebased to 3.2.10, 3.2.11 and 3.2.12.
Could you test the mainline 3.2.11[0] kernel and see if the bug was
introduce in that
So to clarify the next steps:
1. First test the 3.2.0-20.32 kernel
2. Then test the mainline kernels posted in comment #10.
Thanks in advance!
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Wow, this bug is getting a lot of attention! Thanks, everyone.
Joseph Salisbury asked:
When the system hangs, can you see if you can access some of the other ttys?
Sorry, it hangs too early for VTY switching. Specifically, the last two
messages from around 1.47 seconds into boot are
The serial console may give you the same result if you already removed quiet
and splash keywords from grub, as mentioned in:
https://wiki.ubuntu.com/DebuggingKernelBoot
You may be able to use netconsole to capture additional debug info:
https://wiki.ubuntu.com/Kernel/Netconsole
--
You received
Jim,
Could you also test the following upstream kernels and see if they boot:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.9-precise/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.11-precise/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.12-precise/
Based on your results, I can
3.2.12 dies at 1.368s into boot after logging gs_change, similarly to 3.2.0-19
and 3.2.0-20
3.2.11 works
3.2.9 works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel
netconsole isn't going to be an option; it's dying well before getting any
NIC's up.
Let me know if I should hunt down a null modem cable or a digital camera.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the update, Jim.
So we now know the regression was introduced in the 3.2.12 mainline
kernel. I'll bisect between 3.2.11 and 3.2.11. I'll post a test kernel
shortly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Pic from latest upstream kernel
** Attachment added: photo.JPG
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/961482/+attachment/2917619/+files/photo.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Bug watch added: Linux Kernel Bug Tracker #42979
http://bugzilla.kernel.org/show_bug.cgi?id=42979
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=42979
Importance: Unknown
Status: Unknown
** Changed in: linux
Importance: Unknown = Critical
--
You
Typo, I'm biscecting between 3.2.11 and 3.2.12.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications about this bug go to:
Yes, I just tested t he latest mainline from today from
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ in response
to a request for me to do it in my orig bug report
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@GNAServicesInc
Did this panic happen with the v3.3 mainline kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications
gnaservicesinc's screenshot from his daily/current kernel try is pretty
much identical to what I get with the 3.3.0 mainline kernel from 3/18.
In case it wasn't obvious from the attachments, I'm using the 64-bit
amd64 kernels, not the 32-bit i386 kernels.
--
You received this bug notification
Hi All,
I created the first bisected test kernel, which is available at:
http://people.canonical.com/~jsalisbury/lp961482/
This test kernel is built up to commit:
cd3d5286e46aa60ff36a1f7431860d2e7e2fade2
Can folks affected by this bug try this test kernel and report back if
it boots or not?
On my Dell E5420 jsalisbury's lp961482 kernel exhibits the bug, so the
offending commit seems to be earlier than
cd3d5286e46aa60ff36a1f7431860d2e7e2fade2. This kernel also wedges
during boot at 1.36 seconds in, with last two tokens logged being
parse_early_options and gs_change.
--
You
Thanks for the update, Jim. I'll kick off the next kernel build. It will be
built up to commit:
989961646eaad60b22efb8e23090aea563514874
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
The next bisected kernel is available at:
http://people.canonical.com/~jsalisbury/lp961482/
It is built up to commit:
989961646eaad60b22efb8e23090aea563514874
This bug may be related to:
https://lkml.org/lkml/2012/3/19/232
I'll build a test kernel with commit
Failed to boot on http://people.canonical.com/~jsalisbury/lp961482/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications about
@GNAServiceInc,
Thanks for the update, I'll update the bisect that commit
989961646eaad60b22efb8e23090aea563514874 is bad.
Before I build the next bisected kernel, I'd like you have a test kernel
with commit 4949be16822e92a18ea0cc1616319926628092ee reverted. That
test kernel is available at:
Works now
** Attachment added: dmesg
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/961482/+attachment/2918394/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
Yes,
http://people.canonical.com/~jsalisbury/lp961482
/4949be16822e92a18ea0cc1616319926628092ee-reverted/
boots for me too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19
It boots!
http://people.canonical.com/~jsalisbury/lp961482
/4949be16822e92a18ea0cc1616319926628092ee-reverted/
works! yay!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19
The following commit appears to have caused the regression:
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
+++
I built an amd64 Precise test kernel with the previously mentioned commit
reverted. The test kernel is located at:
http://people.canonical.com/~jsalisbury/lp961482
Can you confirm that this test kernel still boots? If it does, that
would be the test kernel to run, until this bug is resolved.
Yes, the
Ubuntu 3.2.0-20.32~lp961482v1-generic 3.2.12
kernel build from
http://people.canonical.com/~jsalisbury/lp961482
boots and runs fine for me. I'm posting this comment using it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks for the update, Jim.
I would suggest using that test kernel(Or an earlier kernel that boots),
until this bug is resolved. The commit that caused this bug is
currently being discussed upstream on LKML:
https://lkml.org/lkml/2012/3/19/408
Thanks to everyone that helped out with this bug!
I think I may suffer from the same bug. Not sure,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/961823
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961482
Title:
3.2.0-19 kernel fails to boot (-18 OK)
To manage notifications about this bug go to:
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
When the system hangs, can you see if you can access some of the other
ttys? That can be done by pressing CTRL+ALT and F1.
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags added: kernel-da-key
--
You
Also, would it be possible for you to test the latest upstream kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v3.3 kernel[1] (Not a kernel in the daily directory). Once
you've tested the upstream kernel, please remove the 'needs-upstream-
testing' tag(Only
Can you also take a look at the following wiki page:
https://wiki.ubuntu.com/DebuggingKernelBoot
It provides some suggestions to get additional debug information during
the boot hang.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
One additional request, It would be great if we could run a kernel
bisect, to identify the commit that caused this bug. Would you be able
to test a few test kernels?
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
73 matches
Mail list logo
