From: grundler@dsl2.external.hp.com (Grant Grundler)
To: Nahkola Mikko <mnahkola@trinms01.ntc.nokia.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Yet another tar-triggered problem?
Date: Tue, 4 Feb 2003 11:06:47 -0700 [thread overview]
Message-ID: <20030204180647.GC15904@dsl2.external.hp.com> (raw)
In-Reply-To: <20030204085502.GQ7503@aurinko.ntc.nokia.com>
On Tue, Feb 04, 2003 at 10:55:02AM +0200, Nahkola Mikko wrote:
> 1024a2d0 seems much more readable here... but then again the stuff is
> much further apart.
>
> 1024a2ac t dino_in32
yeah, dino_in32 just means we detected the existing error condition
when reading from IO space. Something else caused the bus error before.
> Indeed, and on HP-UX I've seen occasional HPMCs with slightly-broken
> disks, for example...
Like this problem with the tape though, that's most likely a driver bug.
grant
next prev parent reply other threads:[~2003-02-04 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 15:44 [parisc-linux] Yet another tar-triggered problem? Nahkola Mikko
2003-02-03 17:30 ` Grant Grundler
2003-02-04 8:55 ` Nahkola Mikko
2003-02-04 18:06 ` Grant Grundler [this message]
2003-02-06 10:11 ` Nahkola Mikko
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=20030204180647.GC15904@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=mnahkola@trinms01.ntc.nokia.com \
--cc=parisc-linux@lists.parisc-linux.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