public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: logs full of chatty IDE cdrom
Date: Sun, 11 May 2003 00:58:25 +0100	[thread overview]
Message-ID: <20030510235825.GG662@gallifrey> (raw)
In-Reply-To: <1052605114.19350.9.camel@dhcp22.swansea.linux.org.uk>

* Alan Cox (alan@lxorguk.ukuu.org.uk) wrote:

> That is interesting. Someone sent a SCSI command the it really didn't
> like. This isn't a dell 8100 or similar laptop is it btw ?

Nope, thats just a standard DVD; its plugged into one channel of a
Promise Ultra100 TX2; an Iomega Zip 100 is a slave on the same channel.
Everything works fine - the only problem is the log messages from audio
playing. /proc/ide/hde/settings is:

name                    value           min             max
mode
----                    -----           ---             --- ----
current_speed           0               0               70 rw
dsc_overlap             1               0               1 rw
ide-scsi                0               0               1 rw
init_speed              0               0               70 rw
io_32bit                0               0               3 rw
keepsettings            0               0               1 rw
nice1                   1               0               1 rw
number                  0               0               3 rw
pio_mode                write-only      0               255 w
slow                    0               0               1 rw
unmaskirq               0               0               1 rw
using_dma               0               0               1 rw

My full set of IDE stuff is:

On board AMD 766 ViperPlus IDE:
   hda - IBM Deathstar 60GB
   hdc - Memorex CD-RW with ide-scsi

Promise Ultra100 TX2
   hde - the offending DVD ROM
   hdf - Iomega ZIP 100 ATAPI
   hdg - IBM Deathstar 60GB

> I guess people with raw drive access should learn to program as well. You
> could play with drive->quiet I guess (I think its drive->quiet) but right
> now the IDE layer has no notion of how severe an error is although it has
> some idea who caused it. For 2.5.x passing quiet/loud in the taskfile is
> a viable extension for 2.4 its not so clear how you would do it nicely.

I guess I was really after a /proc/ide/hd?/verbosity to shut the drive
up independent of what application was trying to talk to it.

Dave
 ---------------- Have a happy GNU millennium! ----------------------   
/ Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

  reply	other threads:[~2003-05-10 23:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-10 20:17 logs full of chatty IDE cdrom Dr. David Alan Gilbert
2003-05-10 20:41 ` Alan Cox
2003-05-10 22:47   ` Dr. David Alan Gilbert
2003-05-10 22:18     ` Alan Cox
2003-05-10 23:58       ` Dr. David Alan Gilbert [this message]
2003-05-12 10:43   ` Martin Schlemmer
2003-05-14  8:16 ` Jens Axboe

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=20030510235825.GG662@gallifrey \
    --to=gilbertd@treblig.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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