From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
chris.mesterharm@gmail.com
Subject: Re: 2.6.34-rc1: pci 0000:00:00.0: address space collision / spontaenous reboots [now 2.6.34-rc1]
Date: Fri, 19 Mar 2010 05:45:44 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1003190543140.31166@p34.internal.lan> (raw)
In-Reply-To: <201003181719.55238.bjorn.helgaas@hp.com>
On Thu, 18 Mar 2010, Bjorn Helgaas wrote:
> On Thursday 18 March 2010 05:00:02 pm Justin Piszcz wrote:
>> On Thu, 18 Mar 2010, Bjorn Helgaas wrote:
>>
>>> On Saturday 13 March 2010 02:01:32 am Justin Piszcz wrote:
>>>> 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..
>>>
>>> Did you ever make any more progress on this? I don't have any ideas;
>>> just wondering whether you learned anything.
>
>> I swapped the motherboard with the ASUS and all problems have disappeared.
>> Someone else e-mailed me with a similar issue (freeze/hang/etc) with a
>> similar motherboard (but UDP3 instead of 5 I believe) and they could not
>> find a solution either, they were trying to install Fedora.
>
> Huh. You started with a Gigabyte board, IIRC, and replaced it with
> an ASUS, so we can't tell if you just had a defective Gigabyte board,
> or if there's something we need to fix in Linux.
>
> The other poster with a similar board and similar symptoms sounds
> interesting, though. You don't have a pointer to a bugzilla or
> email discussion, do you?
>
> Bjorn
>
Hi,
I have cc'd him on this thread.
His board = GA-770TA-UD3
My board = GA-MA790FXT-UD5P
The discussion:
On Wed, 17 Mar 2010, Chris Mesterharm wrote:
> Hello,
>
> Did you ever fix that Gigabyte board with the address space collision? I'm
> have a similar problem with a GA-770TA-UD3 board using Fedora 12. (It kept
> hanging on install, and after install it randomly locks up after a few
> hours.) Currently I'm rerunning hardware tests. If it passes, I'm going to
> try an older kernel and then Ubuntu. If it fails that I'm going to send the
> board back to Newegg.
>
> Thanks,
> Chris
Hi,
Got rid of that board, I spent ~7-14 days on it, doing everything
imaginable, I have been using linux since ~1996 on my own hardware, ran
out of ideas, got a new ASUS board, no more problems.
Intel Gigabyte boards seem to be OK.
AMD ones, of this type, not so sure.
Please let me know when you end up finding!
You should run:
1. memtest first (make sure it passes, grab the system rescue cd)
2. run stress on it, etc
Justin.
next prev parent reply other threads:[~2010-03-19 9:45 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
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 [this message]
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.1003190543140.31166@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=bjorn.helgaas@hp.com \
--cc=chris.mesterharm@gmail.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®