[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
** Changed in: linux (Ubuntu) Target: None = ubuntu-8.04.2 -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
** Changed in: linux Bugwatch: Linux Kernel Bug Tracker #10396 = Linux Kernel Bug Tracker #10124 Status: Invalid = Unknown -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
Hi TJ, Thanks for the clarification. This latest patch you pointed me to also seems to already be in the Hardy and Intrepid trees: [EMAIL PROTECTED]:~/ubuntu-hardy$ git log b87e81e5c6e64ae0eae3b4f61bf07bfeec856184 commit b87e81e5c6e64ae0eae3b4f61bf07bfeec856184 Author: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Tue Apr 15 14:34:49 2008 -0700 acpi: unneccessary to scan the PCI bus already scanned http://bugzilla.kernel.org/show_bug.cgi?id=10124 [EMAIL PROTECTED]:~/ubuntu-intrepid$ git log b87e81e5c6e64ae0eae3b4f61bf07bfeec856184 commit b87e81e5c6e64ae0eae3b4f61bf07bfeec856184 Author: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Tue Apr 15 14:34:49 2008 -0700 acpi: unneccessary to scan the PCI bus already scanned http://bugzilla.kernel.org/show_bug.cgi?id=10124 Brett, I know you confirmed you still have an issue, but glancing at your lspci output it seems you have different hardware than what TJ originally reported. Even though you experience the same symptom that's reported here you might need to open a different bug report. But I'd like to hear from TJ first if this is actually fixed or not. Thanks. -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
Whoa, there is something wacky going on with my git tree I think. Obviously from the git log output I pasted it looks like the patch is already applied to Hardy, but further examining the actual file(s) I'm not seeing the patch applied. I even re-cloned my git tree (git clone git://kernel.ubuntu.com/ubuntu/ubuntu-hardy.git) and see the same odditiy. So please disregard my comment that this is already in Hardy. -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
On Fri, 2008-08-15 at 07:54 +, Leann Ogasawara wrote: Hi TJ, Thanks for the clarification. This latest patch you pointed me to also seems to already be in the Hardy and Intrepid trees: [EMAIL PROTECTED]:~/ubuntu-hardy$ git log b87e81e5c6e64ae0eae3b4f61bf07bfeec856184 commit b87e81e5c6e64ae0eae3b4f61bf07bfeec856184 Author: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Tue Apr 15 14:34:49 2008 -0700 Leann, are you sure that is from ubuntu-hardy master branch? What I mean is, I think it is from the mainline/master remote tracking branch if you have one. If I check the commits in master against one of the files touched the commit b87e81e5 doesn't show up: ubuntu-hardy$ git-status # On branch master nothing to commit (working directory clean) ubuntu-hardy$ git-log -1 --pretty=oneline b180a9b27d1875b970df1bcd74114300e0f7707a UBUNTU: if_arp: add a WiMax pseudo header ubuntu-hardy$ git-log --pretty=format:%h %ci %s -- arch/x86/pci/pci.c | grep b87e81e5 ubuntu-hardy$ If I check the most recent tag prior to that commit I get: ubuntu-hardy$ git-describe b87e81e5 v2.6.25-rc9-67-gb87e81e ubuntu-hardy$ git-describe --contains b87e81e5 v2.6.25~6 which comes from my remote mainline tracking branch: ubuntu-hardy$ git-remote show mainline * remote mainline URL: /home/all/SourceCode/linux/linux-2.6/.git Tracked remote branches fix-bugzilla-10396 master pci-2.6 pci-iomem pci-resource-allocation-debug -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
*** This bug is a duplicate of bug 258143 *** https://bugs.launchpad.net/bugs/258143 ** This bug has been marked a duplicate of bug 258143 Hardy: acpi: unneccessary to scan the PCI bus already scanned -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
*** This bug is a duplicate of bug 258143 *** https://bugs.launchpad.net/bugs/258143 ** Changed in: linux Status: Unknown = Fix Released -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
Hi TJ, The patch you referenced in an eariler comment ( https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/214814/comments/3 ) seems to already be in both Hardy Heron 8.04 and the upcoming Intepid Ibex 8.10 kernel already. Can you confirm this is now resolved for you for both Hardy and the upcoming Intrepid releases? Thanks in advance. [EMAIL PROTECTED]:~/ubuntu-hardy$ git log 08f1c192c3c32797068bfe97738babb3295bbf42 commit 08f1c192c3c32797068bfe97738babb3295bbf42 Author: Muli Ben-Yehuda [EMAIL PROTECTED] Date: Sun Jul 22 00:23:39 2007 +0300 x86-64: introduce struct pci_sysdata to facilitate sharing of -sysdata [EMAIL PROTECTED]:~/ubuntu-intrepid$ git log 08f1c192c3c32797068bfe97738babb3295bbf42 commit 08f1c192c3c32797068bfe97738babb3295bbf42 Author: Muli Ben-Yehuda [EMAIL PROTECTED] Date: Sun Jul 22 00:23:39 2007 +0300 x86-64: introduce struct pci_sysdata to facilitate sharing of -sysdata -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
Leann, the patch you reference is the one that introduced the problem. The fix can be cherry-picked from: commit b87e81e5c6e64ae0eae3b4f61bf07bfeec856184 Author: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Tue Apr 15 14:34:49 2008 -0700 acpi: unneccessary to scan the PCI bus already scanned -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
My HP Pavillion a200n with an Intel Celeron 2.4GHz processor has this problem. It happened in a fresh install of 8.04 and even updated to 8.04.1. This never happened in 7.10 Hope that helps! -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
There doesn't seem to have been much progress on getting this bugfix into the archive. I'm nominating this bug for hardy SRU, but dropping the milestone since it doesn't appear to be on track for inclusion in 8.04.1. ** Changed in: linux (Ubuntu) Target: ubuntu-8.04.1 = None ** Changed in: linux (Ubuntu Hardy) Importance: Undecided = High Status: New = Triaged -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
I get this on an older HP Pavilion a200n running as a server. It previously had 7.10 on it and worked - as far as I know - flawlessly. _ERROR_: BUG: soft lockup - CPU#0 stuck for 11s! [kacpi_notify:45] _PROBLEM_: Computer locks up for $x amount of seconds _TRIED_: Disable acpi by adding 'acpi=off' to '/boot/grub/menu.lst' -- didn't work I will now attach: $ lspci -vv lspci.txt $ cat /proc/cpuinfo cpuinfo.txt $ cat /proc/meminfo meminfo.txt How can I apply this patch? Or how can I compile the latest kernel? ** Attachment added: lspci -vv lspci.txt http://launchpadlibrarian.net/14580789/lspci.txt -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
Noticed you used a program called acpidump. Attaching. ** Attachment added: sudo acpidump acpidump.txt http://launchpadlibrarian.net/14580910/acpidump.txt -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
** Attachment added: cat /proc/meminfo meminfo.txt http://launchpadlibrarian.net/14580812/meminfo.txt -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
** Attachment added: cat /proc/cpuinfo cpuinfo.txt http://launchpadlibrarian.net/14580790/cpuinfo.txt -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
** Changed in: linux (Ubuntu) Target: ubuntu-8.04 = ubuntu-8.04.1 -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
A simpler fix was provided by Matthew Wilcox on linux-pci mailing list. It is cleaner and simpler than my DMI-based patches. Matthew's suggested patch then came to the attention of Zhao Yakui on linux-acpi who reported a patch is already in the -mm tree that solves a similar report at buzilla: Intel SC450NX system stops working with kernels later than 2.6.22.x http://bugzilla.kernel.org/show_bug.cgi?id=10124 That patch has been tested and confirmed working. The patch is found at: http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc8/2.6.25-rc8-mm2 /broken-out/acpi-unneccessary-to-scan-the-pci-bus-already-scanned.patch -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
** Changed in: linux Status: In Progress = Invalid -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
** Changed in: linux Status: Incomplete = In Progress -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
** Attachment added: Hardy i450NX Dell PowerEdge 6300 fix http://launchpadlibrarian.net/13298574/ubuntu-hardy-pci-i450nx-no-secondary-bus-scan-poweredge-6300.diff -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
** Attachment added: Gutsy i450NX Dell PowerEdge 6300 fix http://launchpadlibrarian.net/13298582/ubuntu-gutsy-pci-i450nx-no-secondary-bus-scan-poweredge-6300.diff ** Changed in: linux (Ubuntu) Importance: Undecided = High Assignee: (unassigned) = TJ (intuitivenipple) Status: New = In Progress Target: None = ubuntu-8.04 ** Bug watch added: Linux Kernel Bug Tracker #10396 http://bugzilla.kernel.org/show_bug.cgi?id=10396 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=10396 Importance: Unknown Status: Unknown ** Description changed: See also upstream bug: http://bugzilla.kernel.org/show_bug.cgi?id=10396 Systems based on the Intel 450NX chipset may experience issues where devices aren't recognised that lead to drivers failing, unhandled IRQs, and other serious boot failures. The issue is caused because this chipset has 3 PCI root buses. When it was first released some operating systems (read: Windows NT) didn't always correctly discover the 2nd and 3rd PCI buses. As a result the PCI BIOS tables were 'hacked' to have a fake bridge device on PCI bus 0 that points to the same bus number as the 1st bus so they would be scanned correctly by the OS. $ lspci 00:0a.0 PCI bridge: Intel Corporation 21154 PCI-to-PCI Bridge 00:10.0 Host bridge: Intel Corporation 450NX - 82451NX Memory I/O Controller (rev 03) 00:12.0 Host bridge: Intel Corporation 450NX - 82454NX/84460GX PCI Expander Bridge (rev 04) 00:13.0 Host bridge: Intel Corporation 450NX - 82454NX/84460GX PCI Expander Bridge (rev 04) 00:14.0 Host bridge: Intel Corporation 450NX - 82454NX/84460GX PCI Expander Bridge (rev 04) As a result, in a well-behaved OS the 2nd and 3rd PCI buses would be scanned twice. Once as secondaries of the 1st bus, and then as root buses in their own right. This caused problems with devices being discovered twice. A fix-up for all i450N chipsets was introduced in arch/i386/pci/fixups.c::pci_fixup_i450nx(). Note: arch/i386 was refactored to arch/x86/ subsequently. The fix-up checks the PCI config for the subsidiary buses and if it finds them scans them. This adds them to the root_pci_bus list. Later in the boot process the ACPI/PCI code reads the ACPI DSDT table, finds the PCI bus entries (PNP0A03) and tries to scan them. It fails when scanning the 2nd and 3rd buses with: [0.910906] ACPI: PCI Root Bridge [PX0B] (:02) [0.912085] ACPI: Bus :02 not present in PCI namespace [0.917111] ACPI: PCI Root Bridge [PX1A] (:03) [0.920085] ACPI: Bus :03 not present in PCI namespace Unfortunately, the report is misleading since the reason is that the bus is found to be already registered and therefore ignored. The situation can be worked around by booting with pci=noacpi. The solution is to make the pci_fixup_i450nx() code selected based on the DMI of the system. I've introduced a patch that does this. Initially the only DMI it will match is Dell PowerEdge 6300 but if other systems are found to be affected the output of sudo dmidecode should be captured and reported. Additional DMI_MATCH entries can then be added to the patch. I found this reference to the issue in AKM's 2.6.0 mm tree and the linux-scsi mailing list archive: I can tell you what's going on here. This is a 450NX based motherboard. The 450NX chipset from Intel was the first chipset to have peer PCI busses. For backwards compatibility, some machine makers hacked their PCI BIOS to have a fake bridge device on PCI bus 0 that points to the same bus number as the peer bus. This way if the OS didn't know about the peer bus registers it would still find the devices by scanning behind the bridge. In this case we are scanning behind this fake bridge and then also scanning based upon the peer bus registers in the chipset, and as a result we are finding the device twice. In order to fix this problem you need to change the peer bus quirk code for the 450NX chipset to scan the list of bus 0 devices looking for a bridge that has the same config as the peer bus registers and if so delete the bridge from the list. That will avoid double scanning and will avoid having the PCI code try and configure sub busses via a fake bridge when it should do all configurations via the 450NX peer bus registers. -- Doug Ledford [EMAIL PROTECTED] http://marc.info/?l=linux-scsim=106839680416899w=2 In this particular case a Dell PowerEdge 6300 with a PERC 2 RAID array - controller (aacraid) fails to boot on any kernel after v.2.6.20 - (Feisty). Reports show: + controller (aacraid) fails to boot on any kernel after v2.6.20 (Feisty). + Reports show: [ 0.00] Linux version 2.6.24-15-generic ([EMAIL PROTECTED]) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #1 SMP Fri Apr 4 09:18:39 BST 2008 (Ubuntu 2.6.24-15.26-generic) [ 436.079664] Adaptec
[Bug 214814] Re: BUG: soft lockup - CPU#0 stuck for 61s!
** Changed in: linux Status: Unknown = Incomplete -- BUG: soft lockup - CPU#0 stuck for 61s! https://bugs.launchpad.net/bugs/214814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
