linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Christian <evilninja@gmx.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: CONFIG_ALPHA_SRM not compiling on 2.5
Date: Sat, 8 Mar 2003 17:53:01 +0300	[thread overview]
Message-ID: <20030308175301.A736@localhost.park.msu.ru> (raw)
In-Reply-To: <3E692DEB.2030207@gmx.net>; from evilninja@gmx.net on Sat, Mar 08, 2003 at 12:40:27AM +0100

On Sat, Mar 08, 2003 at 12:40:27AM +0100, Christian wrote:
> Linux version 2.5.63 #7 Wed Mar 05 [...]
> 
> halt code = 7
> machine check while inPAL mode
> PC = 14a0c
> >>>

This has been fixed in 2.5.64.

Ivan.

  reply	other threads:[~2003-03-08 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-04 23:38 CONFIG_ALPHA_SRM not compiling on 2.5 Christian
2003-03-05  0:53 ` Jan-Benedict Glaw
2003-03-07 23:40   ` Christian
2003-03-08 14:53     ` Ivan Kokshaysky [this message]
2003-03-08 17:36       ` Christian

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=20030308175301.A736@localhost.park.msu.ru \
    --to=ink@jurassic.park.msu.ru \
    --cc=evilninja@gmx.net \
    --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;
as well as URLs for NNTP newsgroup(s).