[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#360893: marked as done (udev takes too long to create /dev/hda... and system drops to a shell)

Your message dated Sun, 7 May 2006 23:04:40 +0200
with message-id <20060507210440.GA6143@nancy>
and subject line Bug#360893: udev takes too long to create /dev/hda... and system drops to a shell
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: udev
Version: 0.088-2
Severity: normal

*** Please type your report below this line ***
Hi,
        after a regular upgrade to the present version of udev a new
problem occurs: udev claims it discovers the hardware correctly and in
particular gives out some messages about my Maxtor, about calling it hda,
hda1, hda2 etc.
Then, after hanging there for a while, the initialization scripts say they
cannot find /dev/hda1 (which is supposed to be mounted as root) and drop to
a shell.  Indeed from there ls /dev/hd* gives nothing for a couple of
minutes. After that, a message udevd-event about find_free_number: %e is deprecated... , such as reported in #359978 #357741, pops up. Only now the 
correct /dev/hd... are created.
After this, if I do nothing and exit from the shell, the system completes
its normal boot.

I read Marco's initial message and was doubtful about the appropriateness
of this bug report, but eventually I thought that I was running udev before
on the same machine with no problem, and never changed any setup manually.
So there is likely some real bug in either udev or in its interaction with
the boot scripts.

Let me know if more hardware/configuration details are needed.

Ciao,
        Nick


-- Package-specific info:
-- /etc/udev/rules.d/:
/etc/udev/rules.d/:
total 0
lrwxrwxrwx 1 root root 20 Apr 19 2005 020_permissions.rules -> ../permissions.rules 
lrwxrwxrwx  1 root root 19 Nov  4 14:00 025_libgphoto2.rules -> ../libgphoto2.rules
lrwxrwxrwx  1 root root 15 Feb 16 10:46 85-pcmcia.rules -> ../pcmcia.rules
lrwxrwxrwx  1 root root 19 Mar 14  2005 cd-aliases.rules -> ../cd-aliases.rules
lrwxrwxrwx  1 root root 13 Mar 14  2005 udev.rules -> ../udev.rules
lrwxrwxrwx 1 root root 25 Apr 5 08:51 z20_persistent-input.rules -> ../persistent-input.rules 
lrwxrwxrwx  1 root root 19 Aug 29  2005 z20_persistent.rules -> ../persistent.rules
lrwxrwxrwx  1 root root 12 Aug 29  2005 z50_run.rules -> ../run.rules
lrwxrwxrwx  1 root root 16 Nov  4 13:49 z55_hotplug.rules -> ../hotplug.rules
lrwxrwxrwx  1 root root 19 Aug 29  2005 z60_alsa-utils.rules -> ../alsa-utils.rules
lrwxrwxrwx  1 root root 17 Aug 29  2005 z70_hotplugd.rules -> ../hotplugd.rules

-- /sys/:
/sys/block/fd0/dev
/sys/block/hda/dev
/sys/block/hda/hda1/dev
/sys/block/hda/hda2/dev
/sys/block/hda/hda3/dev
/sys/block/hdc/dev
/sys/block/hdd/dev
/sys/block/ram0/dev
/sys/block/ram1/dev
/sys/block/ram10/dev
/sys/block/ram11/dev
/sys/block/ram12/dev
/sys/block/ram13/dev
/sys/block/ram14/dev
/sys/block/ram15/dev
/sys/block/ram2/dev
/sys/block/ram3/dev
/sys/block/ram4/dev
/sys/block/ram5/dev
/sys/block/ram6/dev
/sys/block/ram7/dev
/sys/block/ram8/dev
/sys/block/ram9/dev
/sys/class/input/input0/event0/dev
/sys/class/input/input1/event1/dev
/sys/class/input/input2/event2/dev
/sys/class/input/input2/mouse0/dev
/sys/class/input/mice/dev
/sys/class/misc/agpgart/dev
/sys/class/misc/hpet/dev
/sys/class/misc/psaux/dev
/sys/class/misc/rtc/dev
/sys/class/sound/adsp/dev
/sys/class/sound/audio/dev
/sys/class/sound/controlC0/dev
/sys/class/sound/dsp/dev
/sys/class/sound/mixer/dev
/sys/class/sound/pcmC0D0c/dev
/sys/class/sound/pcmC0D0p/dev
/sys/class/sound/pcmC0D1c/dev
/sys/class/sound/pcmC0D1p/dev
/sys/class/sound/timer/dev
/sys/class/usb_device/usbdev1.1/dev
/sys/class/usb_device/usbdev2.1/dev
/sys/class/usb_device/usbdev3.1/dev
/sys/class/usb_device/usbdev4.1/dev
/sys/class/usb_device/usbdev5.1/dev

-- Kernel configuration:


-- System Information:
Debian Release: stable/testing/unstable
  APT prefers stable
  APT policy: (700, 'stable'), (100, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages udev depends on:
ii  initscripts                  2.86.ds1-13 Scripts for initializing and shutt
ii  libc6                        2.3.6-3     GNU C Library: Shared libraries an
ii  libselinux1                  1.30-1      SELinux shared libraries
ii  lsb-base                     3.0-16      Linux Standard Base 3.0 init scrip
ii  makedev                      2.3.1-80    creates device files in /dev
ii  sed                          4.1.2-8     The GNU sed stream editor

udev recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Tue, 02 May 2006, Nicola Manini wrote:

> >could you try out linux-image-2.6-$flavour from unstable
> >if that works for you.
> 
> Yes, I installed linux-image-2.6.16-1.686
> and this one boots fine, no prob.

ok cool that's good news.
 
> >hmm did you check from the shell if udevd is running with ps aux?
> 
> Yes, back when I booted 2.6.15 within the shell, from ps aux | grep udev
> I got the following:
> 837 0                 656 S < udevd --daemon
> 
> >try to regnerate your initramfs with latest:
> >update-initramfs -u 
> 
> I did: no change, even with initramfs-tool 0.60

well that will only update newest kernel so to update the 2.6.15,
that would have to be specified with -k version aka
update-initramfs -u -k 2.6.15-1-686
 
> >thanks for your bug report, unfortunately i can pinpoint from the
> >give info the cause.
> 
> Eventually, it seems this one is a 2.6.15 kernel bug rather than 
> initramfs-tool's.
> 
> Right now, I feel very happy with my new 2.6.16-1.686
> As long as it proves itself stable...
> 
> Thank you for your help Maks, all the best,
> 						Nick

thanks for the feedback, closing bug report.

best regards
-- 
maks

--- End Message ---
Reply to: