From: Guillaume Chazarain <guichaz@yahoo.fr>
To: linux-hotplug@vger.kernel.org
Subject: Re: Infinite loop with hal
Date: Fri, 20 Aug 2004 12:41:12 +0000 [thread overview]
Message-ID: <4125F168.8080500@yahoo.fr> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1409 bytes --]
David Zeuthen wrote:
>On Wed, 2004-08-18 at 10:41 +0200, Guillaume Chazarain wrote:
>
>
>>[Follow-up to http://marc.theaimsgroup.com/?t=109239500600001&r=1&w=2]
>>
>>
>>
>
>Thanks a lot for following up; sorry for the lag, I had to moderate the
>message to get through and I only just saw the message
>
>
>
I am not very fast either ;)
>>Unfortunately, the problem did not disappear with the upgrade :(
>>As soon as I access my ZIP, even with "head -c1 /dev/hdd", the
>>infinite loop is back, using 100% of my little PentiumIII 450.
>>
>>
>
>Does this happen even while hald is not running? I guess it really will
>happen even though hald is not running, because of this message from the
>syslog
>
>Aug 17 22:25:40 localhost udev[23814]: configured rule in '/etc/udev/rules.d/51-udev-persistent.rules' at line 3 applied, 'hdd4' becomes '%k'
>
>Try moving that file out of the way and see if it happens again.
>
>
>
Right, it happens also when hald is not running and hiding the file
causes the infinite loop to
go away. I attached the file for information, it's a vanilla fedora/udev
one.
>>The only way to stop the loop is to mount the ZIP or to eject it.
>>In the latter case hald will crash.
>>
>>
>>
>
>Ugh, that's bad, care to send a backtrace?
>
>
>
Sorry, forgot to download the source while at work. It will be for
tomorrow it seems :(
Thanks for your help.
--
Guillaume
[-- Attachment #1.2: Type: text/html, Size: 2363 bytes --]
[-- Attachment #2: 51-udev-persistent.rules --]
[-- Type: text/plain, Size: 1129 bytes --]
BUS="scsi", PROGRAM="/sbin/udev.get_persistent_device_name.sh", NAME="%k" SYMLINK="%c{1+}"
BUS="usb", PROGRAM="/sbin/udev.get_persistent_device_name.sh", NAME="%k" SYMLINK="%c{1+}"
BUS="ide", PROGRAM="/sbin/udev.get_persistent_device_name.sh", NAME="%k" SYMLINK="%c{1+}"
# S/390 zfcp, full disk
BUS="ccw", PROGRAM="/sbin/scsi_id" SYSFS{cutype}="1731/03" SYSFS{devtype}="1732/03" KERNEL="sd*[!0-9]", NAME="%k" SYMLINK="disk/by-path/ccw-%s{hba_id}-fcp-%s{wwpn}:%s{fcp_lun} disk/by-serial/fcp-%c{1}%c{2}-%c{3}"
# S/390 zfcp, disk partition
BUS="ccw", PROGRAM="/sbin/scsi_id" SYSFS{cutype}="1731/03" SYSFS{devtype}="1732/03" KERNEL="sd*[0-9]", NAME="%k" SYMLINK="disk/by-path/ccw-%s{hba_id}-fcp-%s{wwpn}:%s{fcp_lun}-part%n disk/by-serial/fcp-%c{1}%c{2}-%c{3}-part%n"
# S/390 DASD, full disk
BUS="ccw", SYSFS_discipline="ECKD" KERNEL="dasd*[!0-9]", NAME="%k" SYMLINK="disk/by-path/ccw-%b"
# S/390 DASD, disk partition
BUS="ccw", SYSFS_discipline="ECKD" KERNEL="dasd*[0-9]", NAME="%k" SYMLINK="disk/by-path/ccw-%b-part%n"
# KERNEL="ntibm*[0-9]", SYMLINK="tape/%b/non-rewinding"
# KERNEL="rtibm*[0-9]", SYMLINK="tape/%b/rewinding"
reply other threads:[~2004-08-20 12:41 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=4125F168.8080500@yahoo.fr \
--to=guichaz@yahoo.fr \
--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).