From: reflex <reflex-2000@gmx.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: hal daemon and ide-floppy
Date: Mon, 02 Feb 2004 07:35:04 +0000 [thread overview]
Message-ID: <1075707299.714.0.camel@lapis> (raw)
In-Reply-To: <20040201225224.GA4001@werewolf.able.es>
Am Mon, den 02.02.2004 schrieb Greg KH um 04:16:
> > Feb 1 23:50:15 werewolf kernel: ide-floppy: hdd: I/O error, pc = 0, key = 2, asc = 3a, ascq = 0
> > Feb 1 23:50:15 werewolf kernel: ide-floppy: hdd: I/O error, pc = 1b, key = 2, asc = 3a, ascq = 0
> > Feb 1 23:50:15 werewolf kernel: hdd: No disk in drive
> >
> > every 2 seconds, both in messages and syslog.
> > They can grow very large after some uptime ;)
>
> Why not ask the hal authors about why they are doing this?
I have had the same problem with the volume daemon. The main probelm is
that such messages are not from the polling program but from the driver.
Either patch the ide-floppy driver or find another way to poll withouht
errors :-)
You will get similar messages if you poll for usb memory sticks after
plugging in and plugging out (because then, the driver is still loaded),
or polling for normal floppy disks.
If anyone finds/knows a solution for this it would be of great interest
to me.
Regards
Clemens
--
Clemens Wacha wacha@gmx.ch ICQ:12620942
proudly running Debian/GNU Linux. See http://www.debian.org
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-02-02 7:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 21:50 [ANNOUNCE] udev 015 release Greg KH
2004-01-26 23:56 ` Greg KH
2004-01-27 5:52 ` Chris Friesen
2004-01-27 22:22 ` Greg KH
[not found] ` <1075351964.7680.12.camel@nosferatu.lan>
2004-01-29 21:54 ` Greg KH
[not found] ` <1075395125.7680.21.camel@nosferatu.lan>
2004-01-29 21:55 ` Greg KH
2004-01-31 3:17 ` Kay Sievers
[not found] ` <1075571697.7232.11.camel@nosferatu.lan>
2004-01-31 18:15 ` Kay Sievers
[not found] ` <1075573621.7232.14.camel@nosferatu.lan>
2004-01-31 18:39 ` Kay Sievers
2004-01-30 16:45 ` Prakash K. Cheemplavam
2004-01-30 17:23 ` Greg KH
2004-01-30 17:44 ` Prakash K. Cheemplavam
2004-01-30 17:49 ` Greg KH
2004-01-30 18:17 ` Prakash K. Cheemplavam
[not found] ` <1075649046.24826.8.camel@nosferatu.lan>
2004-02-02 8:46 ` Prakash K. Cheemplavam
2004-02-01 22:52 ` hal daemon and ide-floppy J.A. Magallon
2004-02-02 3:16 ` Greg KH
2004-02-02 7:35 ` reflex [this message]
2004-02-02 22:32 ` udev depends on /usr J.A. Magallon
2004-02-02 22:44 ` Greg KH
2004-02-02 23:01 ` J.A. Magallon
2004-02-02 23:08 ` [ANNOUNCE] udev 015 release Prakash K. Cheemplavam
2004-02-02 23:11 ` Greg KH
[not found] ` <1075401020.7680.25.camel@nosferatu.lan>
2004-02-02 23:32 ` Greg KH
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=1075707299.714.0.camel@lapis \
--to=reflex-2000@gmx.net \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).