Your message dated Mon, 15 Sep 2014 15:56:42 +0200
with message-id <[email protected]>
and subject line Re: Bug#717480: udev: hang for about 30 seconds between
detecting sata disks and mounting filesystem
has caused the Debian Bug report #717480,
regarding udev: hang for about 30 seconds between detecting sata disks and
mounting filesystem
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
717480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717480
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: udev
Version: 204-1
Severity: important
Dear Maintainer,
I installed systemd from experimental yesterday and it booted just fine.
But I noticed I still had the old udev 175-7.2 running, so I upgraded
this one as well. After I upgraded udev there is an about 30 seconds
delay between detecting sata disks and mounting filesystems, excerpt
from dmesg:
[ 5.330804] sd 1:0:0:0: [sda] 586072368 512-byte logical blocks: (300 GB/279
GiB)
[ 5.330901] sd 1:0:0:0: [sda] Write Protect is off
[ 5.330903] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 5.330931] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[ 5.331479] sda: sda1 sda2 sda3 sda4
[ 5.331893] sd 1:0:0:0: [sda] Attached SCSI disk
[ 5.341220] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 5.342863] sr 2:0:0:0: Attached scsi CD-ROM sr0
[ 5.343261] sd 3:0:0:0: [sdb] 58626288 512-byte logical blocks: (30.0
GB/27.9 GiB)
[ 5.344983] sd 1:0:0:0: Attached scsi generic sg0 type 0
[ 5.345032] sd 3:0:0:0: [sdb] Write Protect is off
[ 5.345034] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 5.345074] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[ 5.349713] sr 2:0:0:0: Attached scsi generic sg1 type 5
[ 5.351233] sd 3:0:0:0: Attached scsi generic sg2 type 0
[ 5.352803] sdb: unknown partition table
[ 5.355058] sd 3:0:0:0: [sdb] Attached SCSI disk
[…]
[ 32.438547] device-mapper: uevent: version 1.0.3
[ 32.440484] device-mapper: ioctl: 4.25.0-ioctl (2013-06-26) initialised:
[email protected]
[ 32.539864] bio: create slab <bio-1> at 1
[ 32.628353] raid6: sse2x1 6488 MB/s
[ 32.646352] raid6: sse2x2 8554 MB/s
[ 32.664354] raid6: sse2x4 10839 MB/s
[ 32.665889] raid6: using algorithm sse2x4 (10839 MB/s)
[ 32.667338] raid6: using ssse3x2 recovery algorithm
[ 32.669122] xor: automatically using best checksumming function:
[ 32.680353] avx : 22600.000 MB/sec
[ 32.684784] bio: create slab <bio-2> at 2
[ 32.686708] Btrfs loaded
[ 32.708621] device label debian devid 1 transid 318468 /dev/dm-0
[ 32.713748] PM: Starting manual resume from disk
I first thought it wouldn´t but at all but it did.
Additionally to that today morning on resuming from hibernation there
was a delay of about 60 seconds between detecting sata disks and loading
hibernation image. Then I got a blank screen and neither did a key reveal
the KDE greeter nur did Ctrl-Alt-F1 or similar work. I shut down the
system hardly.
In journalctl I find:
-- Logs begin at Sa 2013-04-20 16:05:10 CEST, end at So 2013-07-21 11:50:48
CEST. --
Apr 20 16:05:10 merkaba systemd-journal[398]: Journal started
Apr 20 16:05:10 merkaba systemd-modules[385]: Inserted module 'ecryptfs'
Apr 20 16:05:10 merkaba systemd-modules[385]: Inserted module 'fuse'
Apr 20 16:05:10 merkaba systemd-modules[385]: Inserted module 'firewire_sbp2'
Apr 20 16:05:10 merkaba systemd-modules[385]: Inserted module 'loop'
Apr 20 16:05:10 merkaba systemd-modules[385]: Inserted module 'tp_smapi'
Apr 20 16:05:10 merkaba systemd-modules[385]: Inserted module 'hdaps'
Apr 20 16:05:10 merkaba systemd-modules[385]: could not find module by name='0'
Apr 20 16:05:10 merkaba systemd-modules[385]: Failed to insert 'acpiphp':
Function not implemented
Apr 20 16:05:10 merkaba systemd-modules[385]: Inserted module 'coretemp'
Apr 20 16:05:10 merkaba systemd-modules[385]: Inserted module 'sbs'
Apr 20 16:05:10 merkaba mdadm-raid[424]: Assembling MD arrays...done (disabled
in /etc/default/mdadm).
Apr 20 16:05:10 merkaba hdparm[422]: Setting parameters of disc: (none).
Apr 20 16:05:10 merkaba qemu-kvm[418]: Loading kvm module kvm_intel.
Apr 20 16:05:10 merkaba keyboard-setup[419]: Setting preliminary keymap...done.
Apr 20 16:05:10 merkaba mtp-probe[650]: checking bus 2, device 3:
"/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5"
Apr 20 16:05:10 merkaba mtp-probe[650]: bus: 2, device: 3 was not an MTP device
Apr 20 16:05:10 merkaba mtp-probe[660]: checking bus 1, device 4:
"/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3"
Apr 20 16:05:10 merkaba mtp-probe[660]: bus: 1, device: 4 was not an MTP device
Apr 20 16:05:10 merkaba mtp-probe[657]: checking bus 1, device 3:
"/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2"
Apr 20 16:05:10 merkaba mtp-probe[657]: bus: 1, device: 3 was not an MTP device
The "could not find" and "Failed to insert 'acpiphp'" messages are in read.
I already removed the module name from /etc/modules, with an earlier version
of udev and kernel I needed this one so that the Delock eSATA Expresscard
would be hotplugable.
I did not rebuild the initramfs after removing the module, I think thats
why I still get the message. I report back, once I did.
Anyhow, I think even if thats the reason for the delay, I wouldn´t have
it delay – as in, the module isn´t there, the user forgot, continue.
I will save a full copy of journalctl, syslog and dmesg in case you need
anything else from there.
This happened in a ThinkPad T520 with Intel SSD 320. systemd is all at 204:
libpam-systemd:amd64/experimental 204-1 uptodate
libsystemd-daemon0:amd64/experimental 204-1 uptodate
libsystemd-id128-0:amd64/experimental 204-1 uptodate
libsystemd-journal0:amd64/experimental 204-1 uptodate
libsystemd-login0:amd64/experimental 204-1 uptodate
systemd:amd64/experimental 204-1 uptodate
systemd-gui:all/sid 1:2-2 uptodate
systemd-ui:amd64/sid 2-2 uptodate
Thanks,
Martin
*** End of the template - remove these lines ***
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.11.0-rc1-tp520+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages udev depends on:
ii debconf [debconf-2.0] 1.5.50
ii libacl1 2.2.52-1
ii libblkid1 2.20.1-5.5
ii libc6 2.17-7
ii libkmod2 9-3
ii libselinux1 2.1.13-2
ii libudev1 204-1
ii lsb-base 4.1+Debian12
ii procps 1:3.3.8-2
ii sysv-rc 2.88dsf-43
ii util-linux 2.20.1-5.5
udev recommends no packages.
udev suggests no packages.
-- debconf information:
udev/new_kernel_needed: false
udev/title/upgrade:
udev/reboot_needed:
udev/sysfs_deprecated_incompatibility:
--- End Message ---
--- Begin Message ---
Version: 204-2
On Sat, 27 Jul 2013 13:57:25 +0200 Martin Steigerwald
<[email protected]> wrote:
> After I installed udev 204-2 alongside systemd 204-2 which was already
> installed I thought I good just change "init=/bin/systemd" once:
>
> Well issue is gone, boot is fast again.
>
> I am unsure as how to mark it fixed in 204-2, so I leave that to you.
Closing the bug as requested
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
