From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-mm1 - locks solid when starting KDE (EDAC errors)
Date: Fri, 06 Jan 2006 13:46:46 +0000 [thread overview]
Message-ID: <1136555206.30498.10.camel@localhost.localdomain> (raw)
In-Reply-To: <9a8748490601051552x4c8315e7n3c61860283a95716@mail.gmail.com>
On Gwe, 2006-01-06 at 00:52 +0100, Jesper Juhl wrote:
> Unfortunately not much makes it to the logs. The only things I can
> find is this :
>
> Jan 6 00:18:39 dragon kernel: [ 19.479000] Write protecting the
> kernel read-only data: 333k
> Jan 6 00:18:57 dragon kernel: [ 46.416000] EDAC PCI- Signaled
> System Error on 0000:00:18.2
> Jan 6 00:18:57 dragon kernel: [ 46.416000] EDAC PCI- Master Data
> Parity Error on 0000:00:18.2
> Jan 6 00:18:57 dragon kernel: [ 46.416000] EDAC PCI- Detected
> Parity Error on 0000:00:18.2
> <<<here I power off the system since it's locked solid>>>
If those occur just at boot then they may be noise from the bios setup.
Can you build without EDAC and check if that stops the crash. It
shouldn't stop it crashing but if it does then its important to know
next prev parent reply other threads:[~2006-01-06 13:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 23:52 Jesper Juhl
2006-01-05 23:56 ` Jesper Juhl
2006-01-06 0:27 ` Andrew Morton
2006-01-06 0:40 ` Jesper Juhl
2006-01-06 0:59 ` Andrew Morton
2006-01-06 1:04 ` Jesper Juhl
2006-01-07 0:25 ` Jesper Juhl
2006-01-07 0:28 ` Dave Jones
2006-01-07 0:40 ` Andrew Morton
2006-01-07 0:57 ` Dave Jones
2006-01-07 1:20 ` Jesper Juhl
2006-01-07 1:28 ` Jesper Juhl
2006-01-07 1:53 ` Grant Coady
2006-01-07 2:51 ` Jesper Juhl
2006-01-07 3:13 ` Andrew Morton
2006-01-07 3:19 ` Jesper Juhl
2006-01-07 3:53 ` Dave Jones
2006-01-06 13:46 ` Alan Cox [this message]
2006-01-07 1:12 ` Jesper Juhl
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=1136555206.30498.10.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=jesper.juhl@gmail.com \
--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
Powered by JetHome