From: David Mosberger <davidm@napali.hpl.hp.com>
To: Balazs Scheidler <bazsi@balabit.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel oops on ia64 (2.6.6 + 0521 ia64 patch)
Date: Wed, 16 Jun 2004 18:03:08 -0700 [thread overview]
Message-ID: <16592.60876.886257.165633@napali.hpl.hp.com> (raw)
In-Reply-To: <1087420973.4345.19.camel@bzorp.balabit>
Balazs> I'm encountering more-or-less reproducible oopses on a 2.6.6
Balazs> kernel with 0521 ia64 patch, compiled with gcc 3.3.3 on
Balazs> Debian sarge.
Balazs> The box is a HP rx2600 with a single processor, kernel is
Balazs> compiled in UP mode. Here is the backtrace (saved off froma
Balazs> terminal session on the network console, thus the
Balazs> formatting, but the info should be correct).
Does the oops go away with an SMP kernel?
--david
next prev parent reply other threads:[~2004-06-17 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 21:22 Balazs Scheidler
2004-06-17 1:03 ` David Mosberger [this message]
2004-06-17 16:28 ` Balazs Scheidler
2004-06-17 19:37 ` David Mosberger
2004-06-22 9:34 ` KOVACS Krisztian
2004-06-30 0:19 ` David Mosberger
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=16592.60876.886257.165633@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=bazsi@balabit.hu \
--cc=davidm@hpl.hp.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
all inboxes | Powered by JetHome®