From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: st corruption
Date: Tue, 27 Mar 2001 20:26:08 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.05.10103272015180.494-100000@callisto.of.borg> (raw)
In-Reply-To: <200103252008.OAA17663@lists.linuxppc.org>
Status update:
- When I connect my DDS1 to the MESH, I see no corruption (as long as I get
no `lost arbitration' messages from the MESH driver. I never get those with
the disk BTW). So the tape drive seems to be fine.
- I wanted to try different tape drives, but all retired DDS drives I found
at work seem to be in a non-functional state. I tried 3 of them, without
any luck.
- I wanted to try a 2.2.x kernel, but linuxppc_2_2 (2.2.19-pre3) just says
`illegal instruction' and returns me to the OF prompt.
My next steps:
- Try to understand the sym53c8xx and st drivers.
- Look for missing sync()s and cache flushes in PCI and SCSI busmastering
code.
Anyone else with a clue?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-03-27 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 19:41 st corruption Geert Uytterhoeven
2001-03-22 23:14 ` Tony Mantler
2001-03-23 7:20 ` Geert Uytterhoeven
2001-03-23 13:22 ` Tony Mantler
2001-03-25 15:08 ` Guillaume Laures
2001-03-25 19:21 ` Geert Uytterhoeven
2001-03-25 20:08 ` Guillaume Laures
2001-03-27 18:26 ` Geert Uytterhoeven [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=Pine.LNX.4.05.10103272015180.494-100000@callisto.of.borg \
--to=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).