mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartek Krajnik <bartek@sm.pl>
To: linux-kernel@vger.kernel.org
Subject: alpha with 2.4.1
Date: Wed, 7 Feb 2001 17:21:53 +0100	[thread overview]
Message-ID: <20010207172153.A7333@lama.supermedia.pl> (raw)

My console after panic:
_____________________________________________________________________________
Code: b26901cc stl a3,460(s0)

 a0300000	ldl t0,0(a0)
 482010c1	extbl t0,0,t0
 402075a2	cmpeq t0,3,t1
 e4400003	blt t1,.+16
 d3400045	bsr ra,.+280
*b0090218	stl v0,536(s0)
 c3e00002	br .+12

Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
_____________________________________________________________________________

My cpuinfo:
______________________________________________________________________________
cpu                     : Alpha
cpu model               : EV56
cpu variation           : 7
cpu revision            : 0
cpu serial number       :
system type             : Noritake
system variation        : 0
system revision         : 0
system serial number    : AY90560615
cycle frequency [Hz]    : 500000000
timer frequency [Hz]    : 1024.00
page size [bytes]       : 8192
phys. address bits      : 40
max. addr. space #      : 127
BogoMIPS                : 994.44
kernel unaligned acc    : 318104 (pc=fffffc00003cec04,va=fffffc000e1c25e6)
user unaligned acc      : 0 (pc=0,va=0)
platform string         : AlphaServer 800 5/500
cpus detected           : 1
______________________________________________________________________________

With kernel 2.2.* I haven't any problems... (expect files >2GB).
I use reiserfs(ext2: problem with inodes numbers) for /var/spool_news/.

-- 
	BARTEK
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

                 reply	other threads:[~2001-02-07 16:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010207172153.A7333@lama.supermedia.pl \
    --to=bartek@sm.pl \
    --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®