From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-mips@linux-mips.org
Subject: Re: MC Bus Error / tcp_ack_saw_tstamp Was: IP28 Installation Success report
Date: Thu, 27 Dec 2007 16:10:31 +0100 [thread overview]
Message-ID: <20071227151031.GA7516@alpha.franken.de> (raw)
In-Reply-To: <20071227090401.GA3393@paradigm.rfc822.org>
On Thu, Dec 27, 2007 at 10:04:01AM +0100, Florian Lohoff wrote:
> On Sun, Dec 23, 2007 at 08:54:42PM +0100, Florian Lohoff wrote:
> > I thought an installation success report is sometimes nice to have:
>
> Linux ip28 2.6.24-rc5-g8b3ba06b-dirty #21 Tue Dec 18 12:48:29 CET 2007 mips64 GNU/Linux
>
> After ~10 days uptime and multiple gcc builds. Logging in via ssh
> and issueing an "ls" in the build directory:
>
> MC Bus Error
looks like
/* GIO errors are fatal */
if (gio_err_stat & GIO_ERRMASK)
goto mips_be_fatal;
in ip28_be_interrupt is too strict. Load speculations to addresses
in the GIO address range where no device responds, will probably always
produce bus timeout. It might be worth to use
check_addr_in_insn(cpu_err_addr, regs)) before killing the machine.
So
if ((gio_err_stat & GIO_ERRMASK) &&
check_addr_in_insn(gio_err_addr, regs))
goto mips_be_fatal;
might be better.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2007-12-27 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 9:04 MC Bus Error / tcp_ack_saw_tstamp Was: IP28 Installation Success report Florian Lohoff
2007-12-27 13:28 ` Ralf Baechle
2007-12-27 15:10 ` Thomas Bogendoerfer [this message]
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=20071227151031.GA7516@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=flo@rfc822.org \
--cc=linux-mips@linux-mips.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