2.6.34-rc1: pci 0000:00:00.0: address space collision / spontaenous reboots [now 2.6.34-rc1]
in [Kernel]
|
Prev: 2.6.34-rc1: pci 0000:00:00.0: address space collision / spontaenous reboots [now 2.6.34-rc1]
Next: 2.6.33 GP fault only when built with tracing
From: Justin Piszcz on 18 Mar 2010 19:10 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.. > > Hi Justin, > > Did you ever make any more progress on this? I don't have any ideas; > just wondering whether you learned anything. > > Bjorn > Hello, 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. Justin. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Justin Piszcz on 19 Mar 2010 05:50
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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |