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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
