From: Prasanna P Subash <psubash@turbolinux.com>
To: linux-kernel@vger.kernel.org
Subject: Verbose debug messages when accessing /dev/fd0
Date: Wed, 28 Feb 2001 15:37:09 -0800 [thread overview]
Message-ID: <20010228153709.C10049@turbolinux.com> (raw)
Hi lkml.
when i do a
fd = open( "/dev/fd0", O_WRONLY );
in 2.4.2 series kernels, i get these messages on the console:
psubash kernel: floppy0: reschedule timeout lock fdc
psubash kernel: floppy0: reschedule timeout redo fd request
psubash kernel: floppy0: reschedule timeout redo fd request
psubash kernel: floppy0: checking disk change line for drive 0
psubash kernel: floppy0: jiffies=34789296
psubash kernel: floppy0: disk change line=80
psubash kernel: floppy0: flags=2
psubash kernel: queue fd request dtime=2
psubash kernel: floppy0: reschedule timeout floppy start
psubash kernel: floppy0: setting NEWCHANGE in floppy_start
psubash kernel: floppy0: calling disk change from floppy_ready
psubash kernel: floppy0: checking disk change line for drive 0
psubash kernel: floppy0: jiffies=34789296
psubash kernel: floppy0: disk change line=80
psubash kernel: floppy0: flags=6
psubash kernel: floppy0: calling disk change from seek
psubash kernel: recalibrate floppy: dtime=2
psubash kernel: recal interrupt: dtime=2
psubash kernel: floppy0: calling disk change from floppy_ready
psubash kernel: floppy0: checking disk change line for drive 0
psubash kernel: floppy0: jiffies=34789296
psubash kernel: floppy0: disk change line=80
psubash kernel: floppy0: flags=6
psubash kernel: floppy0: calling disk change from seek
psubash kernel: seek command: dtime=2
psubash kernel: seek interrupt: dtime=3
psubash kernel: floppy0: clearing NEWCHANGE flag because of effective seek=
psubash kernel: floppy0: jiffies=34789297
psubash kernel: floppy0: calling disk change from floppy_ready
psubash kernel: floppy0: checking disk change line for drive 0
psubash kernel: floppy0: jiffies=34789299
psubash kernel: floppy0: disk change line=80
psubash kernel: floppy0: flags=2
psubash kernel: floppy0: calling disk change from seek
psubash kernel: floppy0: checking disk change line for drive 0
psubash kernel: floppy0: jiffies=34789299
psubash kernel: floppy0: disk change line=80
psubash kernel: floppy0: flags=2
psubash kernel: floppy0: reschedule timeout request done 0
psubash kernel: end_request: I/O error, dev 02:00 (floppy), sector 0
psubash kernel: floppy0: calling disk change from set_dor
psubash kernel: floppy0: checking disk change line for drive 0
psubash kernel: floppy0: jiffies=34789590
psubash kernel: floppy0: disk change line=80
psubash kernel: floppy0: flags=12
the last 4 lines showup after 2-3 seconds as I guess they are from the bottom halves.
To prevent this from writing all over my text based app I have to flank the open() with syslog()'s.
On a 2.2 kernel I get 2 debug lines instead (from end_request).
Are the log levels correct for these debug messages ?
Thanks,
--
Prasanna Subash --- psubash@turbolinux.com --- TurboLinux, INC
------------------------------------------------------------------------
Linux, the choice | Your heart is pure, and your mind clear,
of a GNU generation -o) | and your soul devout.
Kernel 2.4.2-ac3 /\\ |
on a i686 _\\_v |
|
------------------------------------------------------------------------
reply other threads:[~2001-02-28 23:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010228153709.C10049@turbolinux.com \
--to=psubash@turbolinux.com \
--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
all inboxes | Powered by JetHome®