All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. Nagy Elemér Károl y" <eknagy@omikk.bme.hu>
To: sparclinux@vger.kernel.org
Subject: Sun V210 Cheetah error trap (kernel problem?)
Date: Sun, 13 Apr 2014 18:33:02 +0000	[thread overview]
Message-ID: <20140413182920.M36664@omikk.bme.hu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

Dear SPARC Kernel Gurus!

I am SysAdming a Sun V210 iptables firewall and I have a kernel problem (?) on it.

Sometimes the console (both virtual via SSH and serial console via ILOM) dies, syslog to disk is stopping, but iptables
keeps filtering the packages. There is a "Cheetah error trap" on the console and in the attached syslog snippet.

Kernel version is 3.2.0-4-sparc64-smp (Debian 3.2.54-2 sparc64) (previous Debian 7 kernel versions behaved similarly).

The error happens sporadically, sometimes once in three months, sometimes once a week. There is no obvious way to
trigger it, IRQ seems to be the best suspect at the moment (iptraf and apt-get upgrade seems to trigger it more often than
idling).

I can apply patches, recompile kernel and do such stuff but I have no idea how to decode this error.

I can experiment with different patches and settings on the weekends as long as they do not endanger the 12 hour
mission-critical weekday filtering.

If I can not resolve this issue the machine will be replaced with an inferior performance X86 machine, so I hope you can
help me - I already tried the Debian Sparc, so you are my last hope.

Thank you:
Elmar K. Nagy


[-- Attachment #2: syslog --]
[-- Type: application/octet-stream, Size: 2981 bytes --]

------%<------%<------%<------%<------%<------%<------%<------%<------%<------
Apr 11 23:17:01 sun1 /USR/SBIN/CRON[8435]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Apr 12 00:15:03 sun1 kernel: [265113.199013] ERROR(1): Cheetah error trap taken afsr[0010100000000000] afar[0000000040000000] TL1(0)
Apr 12 00:15:03 sun1 kernel: [265113.319198] ERROR(1): TPC[407bb0] TNPC[407bb4] O7[448fdc] TSTATE[480e01606]
Apr 12 00:15:03 sun1 kernel: [265113.411823] ERROR(1): TPC<copy_tsb+0x30/0x80>
Apr 12 00:15:03 sun1 kernel: [265113.470153] ERROR(1): M_SYND(0),  E_SYND(0), Privileged
Apr 12 00:15:03 sun1 kernel: [265113.539926] ERROR(1): Highest priority error (0000100000000000) "Unmapped error from system bus"
Apr 12 00:15:03 sun1 kernel: [265113.656601] ERROR(1): D-cache idx[0] tag[0000000000000000] utag[0000000000000000] stag[0000000000000000]
Apr 12 00:15:03 sun1 kernel: [265113.782414] ERROR(1): D-cache data0[0000000000000000] data1[0000000000000000] data2[0000000000000000] data3[0000000000000000]
Apr 12 00:15:03 sun1 kernel: [265113.932249] ERROR(1): I-cache idx[0] tag[0000000000000000] utag[0000000000000000] stag[0000000000000000] u[0000000000000000] l[0000000000000000]
Apr 12 00:15:03 sun1 kernel: [265114.103812] ERROR(1): I-cache INSN0[0000000000000000] INSN1[0000000000000000] INSN2[0000000000000000] INSN3[0000000000000000]
Apr 12 00:15:03 sun1 kernel: [265114.253643] ERROR(1): I-cache INSN4[0000000000000000] INSN5[0000000000000000] INSN6[0000000000000000] INSN7[0000000000000000]
Apr 12 00:15:03 sun1 kernel: [265114.403472] ERROR(1): E-cache idx[40000000] tag[000000001a000fee]
Apr 12 00:15:03 sun1 kernel: [265114.484672] ERROR(1): E-cache data0[804600003fa90012] data1[804080003fa90010] data2[800000103dd1c012] data3[800000103dd06012]
Apr 12 00:15:03 sun1 kernel: [265114.634513] Kernel panic - not syncing: Irrecoverable deferred error trap.
Apr 12 00:15:03 sun1 kernel: [265114.634518] 
Apr 12 00:15:03 sun1 kernel: [265114.746585] Call Trace:
Apr 12 00:15:03 sun1 kernel: [265114.779762]  [0000000000428e28] cheetah_deferred_handler+0x32c/0x364
Apr 12 00:15:03 sun1 kernel: [265114.864404]  [0000000000405e50] c_deferred+0x18/0x24
Apr 12 00:15:03 sun1 kernel: [265114.930735]  [0000000000407bb0] copy_tsb+0x30/0x80
Apr 12 00:15:03 sun1 kernel: [265114.994790]  [0000000000783504] do_sparc64_fault+0x5b4/0x7a4
Apr 12 00:15:03 sun1 kernel: [265115.070275]  [00000000004079a8] sparc64_realfault_common+0x10/0x20
Apr 12 00:15:03 sun1 kernel: [265115.152631]  [000000000045d1f0] schedule_tail+0x78/0x88
Apr 12 00:15:03 sun1 kernel: [265115.222395]  [0000000000406050] ret_from_syscall+0x8/0x18
Apr 12 00:15:03 sun1 kernel: [265115.294457] Press Stop-A (L1-A) to return to the boot prom
Apr 12 00:17:01 sun1 /USR/SBIN/CRON[8605]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Apr 13 11:40:12 sun1 kernel: imklog 5.8.11, log source = /proc/kmsg started.
------%<------%<------%<------%<------%<------%<------%<------%<------%<------

                 reply	other threads:[~2014-04-13 18:33 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=20140413182920.M36664@omikk.bme.hu \
    --to=eknagy@omikk.bme.hu \
    --cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.