From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: 2.6.34-rc1: pci 0000:00:00.0: address space collision / spontaenous reboots [now 2.6.34-rc1]
Date: Sat, 13 Mar 2010 04:01:32 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.00.1003121859240.6929@p34.internal.lan> (raw)
In-Reply-To: <4B9AB7AE.7000002@kernel.org>
On Fri, 12 Mar 2010, Yinghai Lu wrote:
> On 03/12/2010 01:52 PM, Justin Piszcz wrote:
>>
>>
>> On Fri, 12 Mar 2010, Yinghai Lu wrote:
>>
>>> On 03/12/2010 01:30 PM, Justin Piszcz wrote:
>>>>
>>>>
>>>> On Fri, 12 Mar 2010, Justin Piszcz wrote:
>>>>
>>>>> On Fri, 12 Mar 2010, Justin Piszcz wrote:
>>>>>
>>>>
>>>> # Disable Bootmem code (NO_BOOTMEM) [Y/n/?] (NEW)
>>>>
> should be ok, just some warning.
Hi,
It stayed up for approximately 8-9 hours, then it crashed again.
It is either a DOA motherboard OR the memory mapping is causing problems..
$ cat /proc/interrupts
CPU0 CPU1
0: 127 8 IO-APIC-edge timer
1: 0 8 IO-APIC-edge i8042
8: 1 92 IO-APIC-edge rtc0
9: 0 0 IO-APIC-fasteoi acpi
14: 9 2353 IO-APIC-edge pata_atiixp
15: 2 39 IO-APIC-edge pata_atiixp
16: 0 0 IO-APIC-fasteoi ohci_hcd:usb3, ohci_hcd:usb4
17: 0 0 IO-APIC-fasteoi ehci_hcd:usb1
18: 0 68 IO-APIC-fasteoi ahci, ohci_hcd:usb5, ohci_hcd:usb6, ohci_hcd:usb7
19: 0 0 IO-APIC-fasteoi pata_jmicron, ehci_hcd:usb2
22: 1 85 IO-APIC-fasteoi ahci
27: 34 9902 PCI-MSI-edge eth1
28: 39 11356 PCI-MSI-edge eth0
NMI: 0 0 Non-maskable interrupts
LOC: 2278016 2277635 Local timer interrupts
SPU: 0 0 Spurious interrupts
PMI: 0 0 Performance monitoring interrupts
PND: 0 0 Performance pending work
RES: 3805 2872 Rescheduling interrupts
CAL: 23 138 Function call interrupts
TLB: 9 5 TLB shootdowns
THR: 0 0 Threshold APIC interrupts
MCE: 0 0 Machine check exceptions
MCP: 8 8 Machine check polls
ERR: 0
MIS: 0
Any other thoughts/ideas/things to try?
Justin.
next prev parent reply other threads:[~2010-03-13 9:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 10:25 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots Justin Piszcz
2010-03-12 10:49 ` Justin Piszcz
2010-03-12 10:57 ` Justin Piszcz
2010-03-12 12:44 ` Justin Piszcz
2010-03-12 12:56 ` Justin Piszcz
2010-03-12 13:10 ` 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots [full dmesg] Justin Piszcz
2010-03-12 20:01 ` Yinghai Lu
2010-03-12 20:02 ` Justin Piszcz
2010-03-12 20:27 ` Yinghai Lu
2010-03-12 20:34 ` Justin Piszcz
2010-03-12 20:39 ` Justin Piszcz
2010-03-12 21:30 ` 2.6.34-rc1: pci 0000:00:00.0: address space collision / spontaenous reboots [now 2.6.34-rc1] Justin Piszcz
2010-03-12 21:43 ` Yinghai Lu
2010-03-12 21:48 ` Justin Piszcz
2010-03-12 21:50 ` Yinghai Lu
2010-03-12 21:52 ` Justin Piszcz
2010-03-12 21:52 ` Yinghai Lu
2010-03-13 9:01 ` Justin Piszcz [this message]
2010-03-18 22:58 ` Bjorn Helgaas
2010-03-18 23:00 ` Justin Piszcz
2010-03-18 23:19 ` Bjorn Helgaas
2010-03-19 9:45 ` Justin Piszcz
2010-03-12 21:43 ` 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots [full dmesg] Yinghai Lu
2010-03-12 19:44 ` 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots Yinghai Lu
2010-03-12 20:32 ` Justin Piszcz
2010-03-12 21:10 ` Yinghai Lu
2010-03-12 21:59 ` Bjorn Helgaas
2010-03-12 22:07 ` Justin Piszcz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1003121859240.6929@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®