From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Jochen Friedrich <jochen@scram.de>,
Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: 2.3.39 LLC on Alpha broken?
Date: 01 Oct 2002 18:05:15 +0200 [thread overview]
Message-ID: <87heg6ta9w.fsf@student.uni-tuebingen.de> (raw)
In-Reply-To: <20021001184627.B3726@jurassic.park.msu.ru>
Ivan Kokshaysky <ink@jurassic.park.msu.ru> writes:
> On Mon, Sep 30, 2002 at 11:04:17PM +0200, Jochen Friedrich wrote:
> > - After shutting down the Alpha with a "reboot" command, the last message
> > on the console was "Rebooting...". After that... nothing. Not even a
> > power-off - power-on helped, anymore. I just get 4 beeps from my Alpha
> > now, indicating an invalid firmware checksum... So 2.5.39 seems to be an
> > alpha2brick release :-(
>
> Strange. It works fine for me on sx164 and nautilus. I could guess
> either a) some driver bug that accidentally hit the flash-ROM area
> or b) just a terrible coincidence.
Hmm, shutting down didn't work on my Nautilus with 2.5.39+Ivan's
Nautilus patches, either. It did not nuke the firmware, though...
--
Falk
next prev parent reply other threads:[~2002-10-01 15:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 7:46 2.3.39 compile errors on Alpha Jochen Friedrich
2002-09-30 7:59 ` Jochen Friedrich
2002-09-30 11:08 ` Adrian Bunk
2002-09-30 12:35 ` Alan Cox
2002-09-30 12:25 ` David S. Miller
2002-09-30 13:15 ` Alan Cox
2002-09-30 13:20 ` 2.5.39 XConfig Processor Detection Adam Voigt
2002-09-30 13:30 ` Dave Jones
2002-09-30 13:48 ` Adam Voigt
2002-09-30 20:39 ` 2.3.39 compile errors on Alpha David S. Miller
2002-09-30 17:58 ` 2.3.39 LLC on Alpha broken? Jochen Friedrich
2002-09-30 18:07 ` Arnaldo Carvalho de Melo
2002-09-30 8:04 ` Jochen Friedrich
2002-09-30 21:04 ` Jochen Friedrich
2002-10-01 14:46 ` Ivan Kokshaysky
2002-10-01 16:05 ` Falk Hueffner [this message]
2002-09-30 20:59 ` David S. Miller
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=87heg6ta9w.fsf@student.uni-tuebingen.de \
--to=falk.hueffner@student.uni-tuebingen.de \
--cc=acme@conectiva.com.br \
--cc=ink@jurassic.park.msu.ru \
--cc=jochen@scram.de \
--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).