From: Giuliano Pochini <pochini@denise.shiny.it>
To: Nelson Abramson <pogtal@erols.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: bG3+damaged CD=crash
Date: Sat, 08 Jul 2000 17:26:04 -0400 [thread overview]
Message-ID: <39679C6C.CC794B77@denise.shiny.it> (raw)
In-Reply-To: 396499F3.491EA41@erols.com
> > My blue-G3 hangs completely when I try to read a CDROM with some
> > errors. The whole system freezes and the only cure is reboot (no
> > logs, no errors, no panics, no oops). My older 7300 simply told
> > it couldn't read the disk. Is it a known bug ?
>
> Maybe it's a bad CD?
Yes, it IS bad.
> Chances are if it crashes one machine and another
> won't read it, that the CD-ROM itself is bad, not the reader....
> If you
> purchased the CD (as opposed to burning it yourself), get in contact with
> the LinuxPPC people and ask for an exchange...
Ehmm, no. This CDROM is a backup copy of all junk I d/l from the net. It's
content is not important. What I mean is thet if I try to read a file Linux
creashes.
cp /mnt/cdrom/foobar.tgz /home/pochini/ ---> Linux hangs completely
Doing the same on the old 7300 w/ SCSI CD reader if tells me it can't read the
disk and continues working happily.
> > Perhaps I'll buy a SCSI CD, I hate IDE junk.
>
> Your 7300 (I think, and AppleSpec backs me up) has a SCSI CD-ROM, so it's
> probably not the drives.
The problem is the pmac IDE software driver. Trying to read the same CDROM om
my PC gives an error and does not crash.
Bye.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-08 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000705125107.63985.qmail@hotmail.com>
2000-07-06 7:24 ` bG3+damaged CD=crash Giuliano Pochini
2000-07-06 14:38 ` Nelson Abramson
2000-07-08 21:26 ` Giuliano Pochini [this message]
2000-07-06 7:30 ` USB related panics Giuliano Pochini
2000-07-06 8:46 ` Benjamin Herrenschmidt
2000-07-06 10:51 ` Giuliano Pochini
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=39679C6C.CC794B77@denise.shiny.it \
--to=pochini@denise.shiny.it \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=pogtal@erols.com \
/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).