INFO: task systemd-udevd:326 blocked for more than 120 seconds.

Bug #1688920 reported by Cristian Aravena Romero
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
systemd
Fix Released
Unknown
linux (Ubuntu)
Invalid
Medium
Unassigned
usb-creator (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

dmesg:
[ 605.178422] INFO: task systemd-udevd:326 blocked for more than 120 seconds.
[ 605.178434] Not tainted 4.11.0-041100rc8-generic #201704232131
[ 605.178437] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 605.178442] systemd-udevd D 0 326 1 0x00000104
[ 605.178449] Call Trace:
[ 605.178467] __schedule+0x3c6/0x8c0
[ 605.178474] schedule+0x36/0x80
[ 605.178479] schedule_preempt_disabled+0xe/0x10
[ 605.178484] __mutex_lock.isra.5+0x26d/0x4e0
[ 605.178492] __mutex_lock_slowpath+0x13/0x20
[ 605.178497] ? __mutex_lock_slowpath+0x13/0x20
[ 605.178501] mutex_lock+0x2f/0x40
[ 605.178508] __blkdev_get+0x121/0x440
[ 605.178513] blkdev_get+0x12a/0x330
[ 605.178519] blkdev_open+0x5b/0x70
[ 605.178523] do_dentry_open+0x20a/0x310
[ 605.178528] ? bd_acquire+0xd0/0xd0
[ 605.178533] vfs_open+0x4e/0x80
[ 605.178540] path_openat+0x623/0x1500
[ 605.178546] ? kernfs_seq_stop_active+0x2b/0x30
[ 605.178552] do_filp_open+0x99/0x110
[ 605.178558] ? _crng_backtrack_protect+0x62/0x80
[ 605.178562] ? __check_object_size+0x100/0x19d
[ 605.178567] do_sys_open+0x130/0x220
[ 605.178571] ? do_sys_open+0x130/0x220
[ 605.178576] SyS_open+0x1e/0x20
[ 605.178582] do_syscall_64+0x5b/0xc0
[ 605.178586] entry_SYSCALL64_slow_path+0x25/0x25
[ 605.178590] RIP: 0033:0x7f4a8b59bd70
[ 605.178593] RSP: 002b:00007fff0a24e0b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
[ 605.178598] RAX: ffffffffffffffda RBX: 00007fff0a24e150 RCX: 00007f4a8b59bd70
[ 605.178600] RDX: 0000561d1157fd23 RSI: 00000000000a0800 RDI: 0000561d12af1c10
[ 605.178603] RBP: 00007fff0a24e600 R08: 0000561d1157f400 R09: 0000000000000000
[ 605.178605] R10: 0000561d12ab4e40 R11: 0000000000000246 R12: 00007fff0a24e260
[ 605.178607] R13: 0000561d12aa2010 R14: 0000561d12aaa0e0 R15: 00007fff0a24e130

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: systemd 232-21ubuntu3
Uname: Linux 4.11.0-041100-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat May 6 17:13:05 2017
InstallationDate: Installed on 2015-07-26 (650 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-041100-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Changed in systemd:
status: Unknown → New
Changed in systemd:
status: New → Fix Released
affects: systemd (Ubuntu) → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Andreas Fritiofson (andreas-fritiofson) wrote :

I got the same dmesg output when using Startup Disk Creator to write an (L)ubuntu ISO image to a USB stick. After a very long time, and three such messages in the log, the disk creator finally claimed that it was complete. I'm not confident that the installation medium is actually OK, will try it shortly.

Details of the USB stick I used:
[12274.016048] usb 3-1.4: new high-speed USB device number 10 using xhci_hcd
[12274.142013] usb 3-1.4: New USB device found, idVendor=0951, idProduct=1665
[12274.142018] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[12274.142021] usb 3-1.4: Product: DataTraveler 2.0
[12274.142024] usb 3-1.4: Manufacturer: Kingston
[12274.142027] usb 3-1.4: SerialNumber: 50E549C20210BE8059BC09A9
[12274.167999] usb-storage 3-1.4:1.0: USB Mass Storage device detected
[12274.168534] scsi host3: usb-storage 3-1.4:1.0
[12275.275617] scsi 3:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 6
[12275.276767] sd 3:0:0:0: Attached scsi generic sg1 type 0
[12276.083697] sd 3:0:0:0: [sda] 15335424 512-byte logical blocks: (7.85 GB/7.31 GiB)
[12276.084529] sd 3:0:0:0: [sda] Write Protect is off
[12276.084547] sd 3:0:0:0: [sda] Mode Sense: 23 00 00 00
[12276.085363] sd 3:0:0:0: [sda] No Caching mode page found
[12276.085386] sd 3:0:0:0: [sda] Assuming drive cache: write through
[12276.127850] sda: sda1
[12276.131198] sd 3:0:0:0: [sda] Attached SCSI removable disk

Revision history for this message
Andreas Fritiofson (andreas-fritiofson) wrote :

By the way, this was on an up to date 17.10, kernel 4.13.0-17-generic.

Revision history for this message
Andreas Fritiofson (andreas-fritiofson) wrote :

This consistently happens when I use usb-creator. I've tried the lubuntu 17.10 image and the ubuntu 17.10 image, on several USB sticks. Usb-creator finally reports success, but the resulting USB stick FAILS verification (both in the installer and manually by comparing md5sums).

Revision history for this message
dino99 (9d9) wrote :
Changed in linux (Ubuntu):
status: Incomplete → Invalid
Changed in usb-creator (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.