From: Tim Okrongli <j6cubic@gmail.com>
To: Robert Hancock <hancockr@shaw.ca>, linux-kernel@vger.kernel.org
Subject: Re: Panics on AMD X2/NVidiaMCP55Ultra
Date: Fri, 08 Sep 2006 01:42:19 +0200 [thread overview]
Message-ID: <4500AE5B.1070808@gmail.com> (raw)
In-Reply-To: <4500A8B5.7040305@shaw.ca>
Robert Hancock wrote:
> With no symbols in the stack trace this is not very useful. Do you
> have CONFIG_KALLSYMS enabled?
>
Argh, forgot to cc my reply to someone else's question to the ML. The
problem could be traced to a faulty DIMM - by coincidence it was only
used while fscking; even during an attempted kernel rebuild no problems
arose (or rather: make ran into a different problem before it caused
RAM-related problems). That's why it took me so long (more than three
weeks and two mainboards, in fact) to figure out what it was.
For the sake of completeness, I found out when I finally resorted to
installing Windows so I could at least test the GPU and the setup CD
kept bluescreening.
Sorry to needlessly bother you.
next prev parent reply other threads:[~2006-09-07 23:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.5Ci7uSCK5S3sGLcqEDBk92xuBGc@ifi.uio.no>
2006-09-07 23:18 ` Panics on AMD X2/NVidiaMCP55Ultra Robert Hancock
2006-09-07 23:42 ` Tim Okrongli [this message]
2006-09-07 18:50 Tim Okrongli
2006-09-07 22:03 ` Prakash Punnoor
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=4500AE5B.1070808@gmail.com \
--to=j6cubic@gmail.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.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