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

Bug#647011: marked as done (udev randomly stuck on boot while running udevadm settle)

Your message dated Sat, 16 Oct 2021 01:37:15 -0700 (PDT)
with message-id <616a8f3b.1c69fb81.ec7ff.2874@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #647011,
regarding udev randomly stuck on boot while running udevadm settle
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 owner@bugs.debian.org
immediately.)


-- 
647011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647011
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: udev
Version: 172-1
Severity: important
Tags: upstream



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
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.40  
ii  libc6                  2.13-21 
ii  libselinux1            2.1.0-1 
ii  libudev0               172-1   
ii  lsb-base               3.2-28  
ii  util-linux             2.19.1-5

Versions of packages udev recommends:
ii  pciutils  1:3.1.7-12
ii  usbutils  1:004-2   

udev suggests no packages.

-- debconf information excluded

Guess there's some kind of racecondition at boottime. Could be relied to nouveau as that seem's to get loaded during this time (inserted dmesg command in initscript right above the settle command). I just switched from Arch Linux to Debian Testing. Didn't recognize this on Arch (udev 174). Maybe there is already an upstream fix for this problem. I'm on a lenovo w520 (quadro 2000m graphics card, optimus disabled via bios-setting, set to dedicated graphics card). Running udevadm settle command with --timeout=10 does not fix this... there is no timeout. Guess it's deadlocked.

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: