public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Padraig Brady <padraig@antefacto.com>
To: Owen Taylor <otaylor@redhat.com>
Cc: andersen@codepoet.org,
	Matthias Andree <matthias.andree@stud.uni-dortmund.de>,
	Linux-Kernel mailing list <linux-kernel@vger.kernel.org>,
	sopwith@redhat.com
Subject: Re: Need help tracing regular write activity in 5 s interval
Date: Wed, 05 Jun 2002 17:43:55 +0100	[thread overview]
Message-ID: <3CFE3FCB.9040109@antefacto.com> (raw)
In-Reply-To: <20020602135501.GA2548@merlin.emma.line.org>	<3CFCA2B0.4060501@antefacto.com> <20020604120434.GA1386@codepoet.org>	<3CFE1B78.9010406@antefacto.com> <20020605155017.251EC2423B5@fresnel.labs.redhat.com>

Owen Taylor wrote:
> Padraig Brady <padraig@antefacto.com> writes:
> 
>>I'm sure it will :-)
>>
>>However this it just masking the "problem"
> 
> Well, the question is, "what is the problem"? 
> 
> Your problem is that a debug message is being output by the kernel and
> filling your logs. If the debug message doesn't do anybody any good
> (and it doesn't) then removing the debug message is a fine way of
> solving the problem.

True. But I thought there might be (future) side affects of
cdrom_media_changed() always returning true. Why is it there at all?

> I looked at _why_ the debug message was being generated in this
> particular case a long time ago, and it seemed to essentially be a bug
> in the IDE code

Yes that's my guess, and I may have time to look at it.

, but other than generating the debug message,
> basically a harmless one, and there was no interest in fixing it among
> the kernel people I talked to at the time.
> 
> (I don't remember details any more; it was several years ago.)
> 
> 
>>, and I don't
>>think it's "buggy CDROM drives" as I've tried 3 different
>>machines with the following drives:
>>
>>SAMSUNG DVD-ROM SD-612
>>TOSHIBA DVD-ROM SD-C2402
>>CREATIVE CD5233E
>>
>>and they all show the same problem. I.E. logs filling with
>>"VFS: Disk change detected on device ide1(22,0)".
> 
> *This* problem is certainly not a buggy CD-ROM. There are other
> (rarer) problems with logs filling with magicdev that do have to do
> with buggy CD-ROM drives; so that is perhaps what you heard about.
> 
> (Most common one is that some Yamaha CD-RW's apparently report media
> in the drive when they don't have any media in the drive.  magicdev
> tries to mount it, and that failure generates an error message.)
> 
> [...] 
> 
>>Also related, why does the LED flash on every ATA command?
>>Is this controlled by the drive or ide controller?
>>Are you telling me that windows would flash the LED every so often
>>to automount CDs?
> 
> Are you sure that the LED flashing isn't the debug messages being
> written to your hard drive?

Yep. Good point though.

thanks,
Padraig.


  reply	other threads:[~2002-06-05 16:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-02 13:55 Need help tracing regular write activity in 5 s interval Matthias Andree
2002-06-04 11:21 ` Padraig Brady
2002-06-04 11:41   ` Muli Ben-Yehuda
2002-06-04 11:43   ` Xavier Bestel
2002-06-04 12:04   ` Erik Andersen
2002-06-05 14:08     ` Padraig Brady
2002-06-05 15:13       ` Padraig Brady
2002-06-05 15:50       ` Owen Taylor
2002-06-05 16:43         ` Padraig Brady [this message]
2002-06-05 22:22           ` Padraig Brady
  -- strict thread matches above, loose matches on Subject: below --
2002-06-02 15:25 Thunder from the hill
2002-06-02 15:41 ` Kevin Krieser
2002-06-02 16:12 ` Kenneth Johansson
2002-06-02 20:19 ` Matthias Andree

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=3CFE3FCB.9040109@antefacto.com \
    --to=padraig@antefacto.com \
    --cc=andersen@codepoet.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@stud.uni-dortmund.de \
    --cc=otaylor@redhat.com \
    --cc=sopwith@redhat.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