public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Floppy constantly accessed in 2.6.31-rc2
Date: Tue, 14 Jul 2009 01:06:51 +0200	[thread overview]
Message-ID: <1247526411.5220.5.camel@localhost.localdomain> (raw)
In-Reply-To: <h3ehgd$mti$1@ger.gmane.org>

On Sun, 2009-07-12 at 23:44 -0600, Robert Hancock wrote:
> On 2.6.31-rc2 (actually current git as of today) the floppy drive is 
> constantly being accessed with these messages being reported:
> 
> Platform driver 'floppy' needs updating - please use dev_pm_ops
> Floppy drive(s): fd0 is 1.44M
> FDC 0 is a post-1991 82077
> end_request: I/O error, dev fd0, sector 0
> end_request: I/O error, dev fd0, sector 0
> end_request: I/O error, dev fd0, sector 0
> end_request: I/O error, dev fd0, sector 0
> end_request: I/O error, dev fd0, sector 0
> end_request: I/O error, dev fd0, sector 0
> end_request: I/O error, dev fd0, sector 0
> 
> lsof reports no process with /dev/fd0 open so it is not clear what is 
> causing this activity. It looks like the access starts when I log in to 
> X, but doesn't stop when I log out. I'm guessing HAL or something checks 
> the floppy drive and then the kernel somehow gets stuck in a loop 
> retrying the request..

That does look a bit like
https://bugzilla.redhat.com/show_bug.cgi?id=489083 (and its duplicate
https://bugzilla.redhat.com/show_bug.cgi?id=496586 ).

Regards,


Paul Bolle


  parent reply	other threads:[~2009-07-13 23:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13  5:44 Floppy constantly accessed in 2.6.31-rc2 Robert Hancock
2009-07-13 22:43 ` Andrew Morton
2009-07-13 23:06 ` Paul Bolle [this message]
2009-07-13 23:36   ` Robert Hancock

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=1247526411.5220.5.camel@localhost.localdomain \
    --to=pebolle@tiscali.nl \
    --cc=hancockrwd@gmail.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