From: Alexander Nyberg <alexn@telia.com>
To: vandep01@student.ucr.edu
Cc: linux-kernel@vger.kernel.org, ruschein@infomine.ucr.edu
Subject: Re: Kernel Bug Report
Date: Thu, 14 Jul 2005 19:30:11 +0200 [thread overview]
Message-ID: <1121362211.2043.3.camel@localhost.localdomain> (raw)
In-Reply-To: <30a258ac.1bd5021b.81be400@smh.ucr.edu>
tor 2005-07-14 klockan 10:10 -0700 skrev Paul Vander Griend:
> System:
> Motherboard = Tyan K8WE
> Processor = 2x Opteron 250
> Memory = 8GB ECC Registered
>
> On all of the recent release candidates except for
> 2.6.13-rc2-git2 the kernel panics while booting. These
> versions include 2.6.13-rc2-git* (* != 2 ) and 2.6.13-rc3.
>
> I also want to mention that I am using gcc 3.3.5 on debian and
> that during compilation there are 3 messages at the end that
> say an assertion has failed IE (LD: assertion failed).
Those are harmless
> It looks like it panics during a mem_cpy but I know its
> difficult to tell just by the output.
>
> I get a code: f3 a4 c3 66 66 66 90 66 66 66 90 66 66 66 90 66
>
> The problem appears very reproducable so I can provide more
> information upon request.
What does the rest of the panic say? There should be text above this
that tells where the panic occured and why. Can you please send that
here?
next prev parent reply other threads:[~2005-07-14 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 17:10 Kernel Bug Report Paul Vander Griend
2005-07-14 17:30 ` Alexander Nyberg [this message]
2005-07-19 9:32 ` Alexander Nyberg
-- strict thread matches above, loose matches on Subject: below --
2005-07-15 19:04 Lee
2005-07-15 19:19 ` Lee Revell
2005-07-15 19:24 ` Lee
2005-07-15 19:38 ` Lee Revell
2005-07-15 19:41 ` Lee
2004-06-19 19:34 David Michael Leo Brown Jr.
2004-06-20 8:50 ` Arjan van de Ven
2002-04-19 0:53 vinny.k
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=1121362211.2043.3.camel@localhost.localdomain \
--to=alexn@telia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ruschein@infomine.ucr.edu \
--cc=vandep01@student.ucr.edu \
/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