From: Steffen Persvold <sp@scali.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Strange behaviour
Date: Fri, 26 Apr 2002 02:40:23 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905530@msgid-missing> (raw)
Hi all,
In our lab we have two B2-stepping BigSur (that is the codename for
the 2-cpu ones isn't it ?) machines running slightly modified RH7.1 2.4.3
kernel with SMP support (Yes I know, it's unsupported hardware, but
they've worked fine so far). When I do a rather long DMA transfer with a
Dolphin SCI card the machine prints this to the serial console and stops :
gSelFlashStartAddr : ffe4ffb0
gSelLogLength : ffaf
gSelNextEntry : 5386
gSelEntryCount : 9
gSelNewEntriesCount : 1
gSelLastLogRead : 0
gSelCurMaxRecordSize: 13b0
gSelFlags : 28
gSelFullFlag : 0
gSelValidFlag : 1
gSelClearFlag : 0
gSelControl : 0
gFlashExists : 1
gSelFlashStartAddr : ffe4ffb0
gSelLogLength : ffaf
gSelNextEntry : 673c
gSelEntryCount : a
gSelNewEntriesCount : 2
gSelLastLogRead : 0
gSelCurMaxRecordSize: 13b0
gSelFlags : 28
gSelFullFlag : 0
gSelValidFlag : 1
gSelClearFlag : 0
gSelControl : 0
gFlashExists : 1
No kernel oops, no kdb, no nothing. Only solution is to power the server
off and then on again.
I'm curious to what this is, it seems to come from the machine firmware or
something ? Is this related to the beta HW I have, Linux kernel version or
is it something else ?
Thanks in advance,
--
Steffen Persvold | Scalable Linux Systems | Try out the world's best
mailto:sp@scali.com | http://www.scali.com | performing MPI implementation:
Tel: (+47) 2262 8950 | Olaf Helsets vei 6 | - ScaMPI 1.13.8 -
Fax: (+47) 2262 8951 | N0621 Oslo, NORWAY | >320MBytes/s and <4uS latency
next reply other threads:[~2002-04-26 2:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 2:40 Steffen Persvold [this message]
2002-04-30 3:11 ` [Linux-ia64] Strange behaviour 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=marc-linux-ia64-105590701905530@msgid-missing \
--to=sp@scali.com \
--cc=linux-ia64@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