[2769] in linux-scsi channel archive
Re: Diamond Fireport 40
daemon@ATHENA.MIT.EDU (Mike Simons)
Fri Nov 7 01:01:35 1997
From: Mike Simons <msimons@saic1.com>
In-Reply-To: <199711060539.XAA00397@rocket.cc.umr.edu> from Justin Miller at "Nov 5, 97 11:39:05 pm"
To: jhm@umr.edu (Justin Miller)
Date: Fri, 7 Nov 1997 00:57:53 -0500 (EST)
Cc: linux-scsi@vger.rutgers.edu
Sorry no good news in this post... just relaying similar problems
with a different SCSI controller.
> [...] I was writing a cdrom and
> decided it was time to play an mp3, I tried playing one and then boom,
> Kernel Panic!. unfortunately i couldn't save any of the info that it
> spat out when it gave up but i did see ncr8xx mentioned on a couple of
> lines. Since then I have burnt two cd's just fine, I was wondering if I
> had configured the driver incorrectly. [...]
> Attached devices:
> Host: scsi0 Channel: 00 Id: 04 Lun: 00
> Vendor: HP Model: CD-Writer 6020 Rev: 1.07
> Type: CD-ROM ANSI SCSI revision: 02
We have a dual-pentium machine with a BusLogic 948 SCSI controller,
and this cd-worm drive. _I_ am convinced that this cd-worm is misbehaving,
Since installing this drive 4 months ago, this machine has crashed
many times with what appeared to scsi bus locks. (*)
When using the cd-worm to play audio (via cdp or any other utility), I
can normally crash the machine just repeatedly changing which track is
being played. The cdrom that was here before never did that.
We have done several successful cd burning sessions, but there was one
horror... About 30 minutes into burning the 3rd copy of an image, someone
else decided to create a tar.gz file of their home directory.
I noticed what was going on and decided to go to their office and
mention the burning session (which they already knew about) to ask
them to suspend the tar. i got back to the machine to find it
locked hard (required power cycle for the drives to respond)... rebooted
to find massive filesystem corruption in *their* home directory, 30 mins
later fsck and I turned every file they owned into inode numbered files =).
It _could_ be the cdwrite program is to blame for that corruption (it has
burned onto the last 2/3rd's of a new cd after a ^C to stop a test burn,
then locked the bus after finishing the 'test burn'.
Does anyone want to try some of the things above on their HP 6020
to see what it does? I was hoping to test ours with some other scsi
controllers (not that any of the scsi cards/drivers work better than the
Buslogic one, just differently)
Now I use this worm drive _only_ when everyone else is at home and
_only_ to burn cd's that _must_ be burned. I have not used any other
worm drives, but I will bet this is not "normal" for worm drives in Linux
to crash the machine. ;)
I've been meaning to put this drive in a different machine that
I can bang away at it but haven't had the time. If anyone would like
to give suggestions/tests/advice to I'll file them away for when I do
get this drive in some other machine...
--
Later,
Mike Simons
Science Applications International Corporation
msimons@saic1.com 703-925-5674
*:
don't send any of the standard, 'check the scsi cable/termination/etc'
suggestions...
