INFO: umount blocked for more than 120 seconds
in [Kernel]
|
Prev: [PATCH] iio_trigger_find_by_name: Skip trailing newline if available
Next: x86: Do not write into VGA memory space if there is no VGA device in the system
From: Sergey Senozhatsky on 26 Apr 2010 05:10 Hello, MiniSD card mounted through the USB card reader. ..34-rc5-git6 kernel: [ 5746.170226] scsi12 : usb-storage 2-2:1.0 kernel: [ 5747.174113] scsi scan: INQUIRY result too short (5), using 36 kernel: [ 5747.174128] scsi 12:0:0:0: Direct-Access PQ: 0 ANSI: 0 kernel: [ 5747.180721] sd 12:0:0:0: Attached scsi generic sg2 type 0 kernel: [ 5747.190490] sd 12:0:0:0: [sdb] 2012160 512-byte logical blocks: (1.03 GB/982 MiB) kernel: [ 5747.193398] sd 12:0:0:0: [sdb] Write Protect is off kernel: [ 5747.193403] sd 12:0:0:0: [sdb] Mode Sense: 00 06 00 00 kernel: [ 5747.193406] sd 12:0:0:0: [sdb] Assuming drive cache: write through kernel: [ 5747.207116] sd 12:0:0:0: [sdb] Assuming drive cache: write through kernel: [ 5747.207125] sdb: sdb1 kernel: [ 5747.233099] sd 12:0:0:0: [sdb] Assuming drive cache: write through kernel: [ 5747.233112] sd 12:0:0:0: [sdb] Attached SCSI removable disk kernel: [ 5758.495211] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! kernel: [ 6360.626229] INFO: task umount:4235 blocked for more than 120 seconds. kernel: [ 6360.626237] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kernel: [ 6360.626246] umount D 0000059e 0 4235 3382 0x00000000 kernel: [ 6360.626259] f6e09e38 00000046 38aa246b 0000059e c1610cc0 c12c3880 c1610cc0 c1610cc0 kernel: [ 6360.626282] c1610cc0 c1610cc0 f6fa6cd0 c1610cc0 00002d16 00000000 38a9f755 0000059e kernel: [ 6360.626304] f6fa6a40 f6e09e40 f6e09e70 00000000 f6e09e78 f6e09e40 c10b7cf0 f6e09e5c kernel: [ 6360.626334] Call Trace: kernel: [ 6360.626345] [<c12c3880>] ? _raw_spin_unlock_irqrestore+0x36/0x5b kernel: [ 6360.626353] [<c10b7cf0>] bdi_sched_wait+0x8/0xc kernel: [ 6360.626358] [<c12c20df>] __wait_on_bit+0x34/0x5b kernel: [ 6360.626363] [<c10b7ce8>] ? bdi_sched_wait+0x0/0xc kernel: [ 6360.626368] [<c12c215d>] out_of_line_wait_on_bit+0x57/0x5f kernel: [ 6360.626373] [<c10b7ce8>] ? bdi_sched_wait+0x0/0xc kernel: [ 6360.626379] [<c103fa75>] ? wake_bit_function+0x0/0x4d kernel: [ 6360.626385] [<c10b84d4>] wait_on_bit.clone.0+0x17/0x23 kernel: [ 6360.626390] [<c10b8544>] sync_inodes_sb+0x64/0x10d kernel: [ 6360.626397] [<c10d373f>] ? vfs_quota_sync+0x0/0x1da kernel: [ 6360.626402] [<c10baef6>] __sync_filesystem+0x37/0x62 kernel: [ 6360.626407] [<c10bb062>] sync_filesystem+0x3c/0x3f kernel: [ 6360.626413] [<c10a2def>] generic_shutdown_super+0x1c/0xca kernel: [ 6360.626418] [<c10a2eba>] kill_block_super+0x1d/0x31 kernel: [ 6360.626423] [<c10a3833>] deactivate_super+0x48/0x5a kernel: [ 6360.626429] [<c10b385c>] mntput_no_expire+0x5e/0x89 kernel: [ 6360.626434] [<c10b41cf>] sys_umount+0x277/0x29b kernel: [ 6360.626440] [<c10b4200>] sys_oldumount+0xd/0xf kernel: [ 6360.626445] [<c1002813>] sysenter_do_call+0x12/0x32 kernel: [ 6360.626450] 1 lock held by umount/4235: kernel: [ 6360.626453] #0: (&type->s_umount_key#34){++++..}, at: [<c10a382e>] deactivate_super+0x43/0x5a Sergey
From: Alan Stern on 26 Apr 2010 15:40 On Mon, 26 Apr 2010, Sergey Senozhatsky wrote: > Hello, > MiniSD card mounted through the USB card reader. > > .34-rc5-git6 > > kernel: [ 5746.170226] scsi12 : usb-storage 2-2:1.0 > kernel: [ 5747.174113] scsi scan: INQUIRY result too short (5), using 36 > kernel: [ 5747.174128] scsi 12:0:0:0: Direct-Access PQ: 0 ANSI: 0 > kernel: [ 5747.180721] sd 12:0:0:0: Attached scsi generic sg2 type 0 > kernel: [ 5747.190490] sd 12:0:0:0: [sdb] 2012160 512-byte logical blocks: (1.03 GB/982 MiB) > kernel: [ 5747.193398] sd 12:0:0:0: [sdb] Write Protect is off > kernel: [ 5747.193403] sd 12:0:0:0: [sdb] Mode Sense: 00 06 00 00 > kernel: [ 5747.193406] sd 12:0:0:0: [sdb] Assuming drive cache: write through > kernel: [ 5747.207116] sd 12:0:0:0: [sdb] Assuming drive cache: write through > kernel: [ 5747.207125] sdb: sdb1 > kernel: [ 5747.233099] sd 12:0:0:0: [sdb] Assuming drive cache: write through > kernel: [ 5747.233112] sd 12:0:0:0: [sdb] Attached SCSI removable disk > kernel: [ 5758.495211] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! > kernel: [ 6360.626229] INFO: task umount:4235 blocked for more than 120 seconds. > kernel: [ 6360.626237] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Is this repeatable? Can you do this with CONFIG_USB_DEBUG enabled? And acquire a usbmon trace at the same time (see Documentation/usb/usbmon.txt)? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Robert Hancock on 26 Apr 2010 21:20 On 04/26/2010 03:01 AM, Sergey Senozhatsky wrote: > Hello, > MiniSD card mounted through the USB card reader. > > .34-rc5-git6 > > kernel: [ 5746.170226] scsi12 : usb-storage 2-2:1.0 > kernel: [ 5747.174113] scsi scan: INQUIRY result too short (5), using 36 > kernel: [ 5747.174128] scsi 12:0:0:0: Direct-Access PQ: 0 ANSI: 0 > kernel: [ 5747.180721] sd 12:0:0:0: Attached scsi generic sg2 type 0 > kernel: [ 5747.190490] sd 12:0:0:0: [sdb] 2012160 512-byte logical blocks: (1.03 GB/982 MiB) > kernel: [ 5747.193398] sd 12:0:0:0: [sdb] Write Protect is off > kernel: [ 5747.193403] sd 12:0:0:0: [sdb] Mode Sense: 00 06 00 00 > kernel: [ 5747.193406] sd 12:0:0:0: [sdb] Assuming drive cache: write through > kernel: [ 5747.207116] sd 12:0:0:0: [sdb] Assuming drive cache: write through > kernel: [ 5747.207125] sdb: sdb1 > kernel: [ 5747.233099] sd 12:0:0:0: [sdb] Assuming drive cache: write through > kernel: [ 5747.233112] sd 12:0:0:0: [sdb] Attached SCSI removable disk > kernel: [ 5758.495211] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! > kernel: [ 6360.626229] INFO: task umount:4235 blocked for more than 120 seconds. > kernel: [ 6360.626237] "echo 0> /proc/sys/kernel/hung_task_timeout_secs" disables this message. > kernel: [ 6360.626246] umount D 0000059e 0 4235 3382 0x00000000 > kernel: [ 6360.626259] f6e09e38 00000046 38aa246b 0000059e c1610cc0 c12c3880 c1610cc0 c1610cc0 > kernel: [ 6360.626282] c1610cc0 c1610cc0 f6fa6cd0 c1610cc0 00002d16 00000000 38a9f755 0000059e > kernel: [ 6360.626304] f6fa6a40 f6e09e40 f6e09e70 00000000 f6e09e78 f6e09e40 c10b7cf0 f6e09e5c > kernel: [ 6360.626334] Call Trace: > kernel: [ 6360.626345] [<c12c3880>] ? _raw_spin_unlock_irqrestore+0x36/0x5b > kernel: [ 6360.626353] [<c10b7cf0>] bdi_sched_wait+0x8/0xc > kernel: [ 6360.626358] [<c12c20df>] __wait_on_bit+0x34/0x5b > kernel: [ 6360.626363] [<c10b7ce8>] ? bdi_sched_wait+0x0/0xc > kernel: [ 6360.626368] [<c12c215d>] out_of_line_wait_on_bit+0x57/0x5f > kernel: [ 6360.626373] [<c10b7ce8>] ? bdi_sched_wait+0x0/0xc > kernel: [ 6360.626379] [<c103fa75>] ? wake_bit_function+0x0/0x4d > kernel: [ 6360.626385] [<c10b84d4>] wait_on_bit.clone.0+0x17/0x23 > kernel: [ 6360.626390] [<c10b8544>] sync_inodes_sb+0x64/0x10d > kernel: [ 6360.626397] [<c10d373f>] ? vfs_quota_sync+0x0/0x1da > kernel: [ 6360.626402] [<c10baef6>] __sync_filesystem+0x37/0x62 > kernel: [ 6360.626407] [<c10bb062>] sync_filesystem+0x3c/0x3f > kernel: [ 6360.626413] [<c10a2def>] generic_shutdown_super+0x1c/0xca > kernel: [ 6360.626418] [<c10a2eba>] kill_block_super+0x1d/0x31 > kernel: [ 6360.626423] [<c10a3833>] deactivate_super+0x48/0x5a > kernel: [ 6360.626429] [<c10b385c>] mntput_no_expire+0x5e/0x89 > kernel: [ 6360.626434] [<c10b41cf>] sys_umount+0x277/0x29b > kernel: [ 6360.626440] [<c10b4200>] sys_oldumount+0xd/0xf > kernel: [ 6360.626445] [<c1002813>] sysenter_do_call+0x12/0x32 > kernel: [ 6360.626450] 1 lock held by umount/4235: > kernel: [ 6360.626453] #0: (&type->s_umount_key#34){++++..}, at: [<c10a382e>] deactivate_super+0x43/0x5a Is this some super-slow SD card or USB reader that you just wrote a bunch of data to? It's not impossible it could take 2 minutes for the writeout of all the dirty data to complete on unmount.. did the unmount ever complete? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Sergey Senozhatsky on 27 Apr 2010 04:10 Hello, Robert Hancock added to Cc list. First of all, let me describe hw (sorry for skipping this part in prev. email). The device is ASUS p535 in a card reader mode. The card is 1Gb MiniSD (Kingston). On (04/26/10 15:36), Alan Stern wrote: > Is this repeatable? > Yes. kernel: [14980.102019] usb 2-1: new full speed USB device using uhci_hcd and address 2 kernel: [14980.270773] usb 2-1: New USB device found, idVendor=0b05, idProduct=422f kernel: [14980.270783] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 kernel: [14980.270790] usb 2-1: Product: Generic Mass Storage kernel: [14980.270797] usb 2-1: Manufacturer: ASUS kernel: [14980.270803] usb 2-1: SerialNumber: ********************************* kernel: [14980.273767] scsi3 : usb-storage 2-1:1.0 kernel: [14981.279875] scsi scan: INQUIRY result too short (5), using 36 kernel: [14981.279890] scsi 3:0:0:0: Direct-Access PQ: 0 ANSI: 0 kernel: [14981.289597] sd 3:0:0:0: Attached scsi generic sg2 type 0 kernel: [14981.301967] sd 3:0:0:0: [sdb] 2012160 512-byte logical blocks: (1.03 GB/982 MiB) kernel: [14981.304760] sd 3:0:0:0: [sdb] Write Protect is off kernel: [14981.304765] sd 3:0:0:0: [sdb] Mode Sense: 00 06 00 00 kernel: [14981.304768] sd 3:0:0:0: [sdb] Assuming drive cache: write through kernel: [14981.316864] sd 3:0:0:0: [sdb] Assuming drive cache: write through kernel: [14981.316877] sdb: sdb1 kernel: [14981.339861] sd 3:0:0:0: [sdb] Assuming drive cache: write through kernel: [14981.339873] sd 3:0:0:0: [sdb] Attached SCSI removable disk kernel: [15014.446419] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! kernel: [15360.625323] INFO: task umount:7148 blocked for more than 120 seconds. kernel: [15360.625332] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kernel: [15360.625340] umount D 00000dd9 0 7148 6292 0x00000000 kernel: [15360.625353] f38bfe38 00000046 12abbd47 00000dd9 c1610cc0 c12c3890 c1610cc0 c1610cc0 kernel: [15360.625377] c1610cc0 c1610cc0 f6fc5790 c1610cc0 00010bbe 00000000 12aab189 00000dd9 kernel: [15360.625400] f6fc5500 f38bfe40 f38bfe70 00000000 f38bfe78 f38bfe40 c10b7cf0 f38bfe5c kernel: [15360.625423] Call Trace: kernel: [15360.625442] [<c12c3890>] ? _raw_spin_unlock_irqrestore+0x36/0x5b kernel: [15360.625457] [<c10b7cf0>] bdi_sched_wait+0x8/0xc kernel: [15360.625467] [<c12c20ef>] __wait_on_bit+0x34/0x5b kernel: [15360.625477] [<c10b7ce8>] ? bdi_sched_wait+0x0/0xc kernel: [15360.625487] [<c12c216d>] out_of_line_wait_on_bit+0x57/0x5f kernel: [15360.625497] [<c10b7ce8>] ? bdi_sched_wait+0x0/0xc kernel: [15360.625510] [<c103fa75>] ? wake_bit_function+0x0/0x4d kernel: [15360.625521] [<c10b84d4>] wait_on_bit.clone.0+0x17/0x23 kernel: [15360.625531] [<c10b8544>] sync_inodes_sb+0x64/0x10d kernel: [15360.625546] [<c10d373f>] ? vfs_quota_sync+0x0/0x1da kernel: [15360.625556] [<c10baef6>] __sync_filesystem+0x37/0x62 kernel: [15360.625566] [<c10bb062>] sync_filesystem+0x3c/0x3f kernel: [15360.625578] [<c10a2def>] generic_shutdown_super+0x1c/0xca kernel: [15360.625588] [<c10a2eba>] kill_block_super+0x1d/0x31 kernel: [15360.625599] [<c10a3833>] deactivate_super+0x48/0x5a kernel: [15360.625610] [<c10b385c>] mntput_no_expire+0x5e/0x89 kernel: [15360.625620] [<c10b41cf>] sys_umount+0x277/0x29b kernel: [15360.625631] [<c10b4200>] sys_oldumount+0xd/0xf kernel: [15360.625642] [<c1002813>] sysenter_do_call+0x12/0x32 kernel: [15360.625652] 1 lock held by umount/7148: kernel: [15360.625657] #0: (&type->s_umount_key#32){++++..}, at: [<c10a382e>] deactivate_super+0x43/0x5a > Can you do this with CONFIG_USB_DEBUG enabled? And acquire a usbmon > trace at the same time (see Documentation/usb/usbmon.txt)? > Sure. Rebuilding the kernel right now. Robert Hancock wrote: > Is this some super-slow SD card or USB reader that you just wrote a bunch of data to? > It's not impossible it could take 2 minutes for the writeout of all the dirty data to > complete on unmount.. Please see above. > did the unmount ever complete? No entry in /etc/mtab. So, I guess, yes - umount complete. Sergey
From: Sergey Senozhatsky on 27 Apr 2010 05:50
Hello, On (04/26/10 15:36), Alan Stern wrote: > Can you do this with CONFIG_USB_DEBUG enabled? And acquire a usbmon > trace at the same time (see Documentation/usb/usbmon.txt)? > mount as /media/fl/ cp ./LLVM 2.0.mp4 /media/fl/ - (246M) umount /media/fl/ Please see usbmon.log attached. kernel: [ 3228.543190] usb 2-2: new full speed USB device using uhci_hcd and address 4 kernel: [ 3228.689814] usb 2-2: ep0 maxpacket = 16 kernel: [ 3228.712027] usb 2-2: default language 0x0409 kernel: [ 3228.731035] usb 2-2: udev 4, busnum 2, minor = 131 kernel: [ 3228.731043] usb 2-2: New USB device found, idVendor=0b05, idProduct=422f kernel: [ 3228.731051] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 kernel: [ 3228.731058] usb 2-2: Product: Generic Mass Storage kernel: [ 3228.731064] usb 2-2: Manufacturer: ASUS kernel: [ 3228.731070] usb 2-2: SerialNumber: 7abf5000-2268-0801-3b00-072fa733ffff kernel: [ 3228.731640] usb 2-2: usb_probe_device kernel: [ 3228.731649] usb 2-2: configuration #1 chosen from 1 choice kernel: [ 3228.733180] usb 2-2: adding 2-2:1.0 (config #1, interface 0) kernel: [ 3228.733661] usb-storage 2-2:1.0: usb_probe_interface kernel: [ 3228.733677] usb-storage 2-2:1.0: usb_probe_interface - got id kernel: [ 3228.734213] scsi4 : usb-storage 2-2:1.0 kernel: [ 3229.738138] scsi scan: INQUIRY result too short (5), using 36 kernel: [ 3229.738154] scsi 4:0:0:0: Direct-Access PQ: 0 ANSI: 0 kernel: [ 3229.746458] sd 4:0:0:0: Attached scsi generic sg2 type 0 kernel: [ 3229.750731] sd 4:0:0:0: [sdb] 2012160 512-byte logical blocks: (1.03 GB/982 MiB) kernel: [ 3229.754031] sd 4:0:0:0: [sdb] Write Protect is off kernel: [ 3229.754036] sd 4:0:0:0: [sdb] Mode Sense: 00 06 00 00 kernel: [ 3229.754039] sd 4:0:0:0: [sdb] Assuming drive cache: write through kernel: [ 3229.766121] sd 4:0:0:0: [sdb] Assuming drive cache: write through kernel: [ 3229.766134] sdb: sdb1 kernel: [ 3229.790123] sd 4:0:0:0: [sdb] Assuming drive cache: write through kernel: [ 3229.790135] sd 4:0:0:0: [sdb] Attached SCSI removable disk kernel: [ 3247.991259] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! kernel: [ 3840.643117] INFO: task umount:4902 blocked for more than 120 seconds. kernel: [ 3840.643125] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kernel: [ 3840.643133] umount D 0000034e 0 4902 3943 0x00000000 kernel: [ 3840.643146] f640de38 00000046 3715ce5d 0000034e c1610cc0 c12c3938 c1610cc0 c1610cc0 kernel: [ 3840.643170] c1610cc0 c1610cc0 f51017d0 c1610cc0 00012bf1 00000000 3714a26c 0000034e kernel: [ 3840.643193] f5101540 f640de40 f640de70 00000000 f640de78 f640de40 c10b7cf0 f640de5c kernel: [ 3840.643215] Call Trace: kernel: [ 3840.643234] [<c12c3938>] ? _raw_spin_unlock_irqrestore+0x36/0x5b kernel: [ 3840.643249] [<c10b7cf0>] bdi_sched_wait+0x8/0xc kernel: [ 3840.643259] [<c12c2197>] __wait_on_bit+0x34/0x5b kernel: [ 3840.643268] [<c10b7ce8>] ? bdi_sched_wait+0x0/0xc kernel: [ 3840.643279] [<c12c2215>] out_of_line_wait_on_bit+0x57/0x5f kernel: [ 3840.643289] [<c10b7ce8>] ? bdi_sched_wait+0x0/0xc kernel: [ 3840.643302] [<c103fa75>] ? wake_bit_function+0x0/0x4d kernel: [ 3840.643313] [<c10b84d4>] wait_on_bit.clone.0+0x17/0x23 kernel: [ 3840.643323] [<c10b8544>] sync_inodes_sb+0x64/0x10d kernel: [ 3840.643337] [<c10d373f>] ? vfs_quota_sync+0x0/0x1da kernel: [ 3840.643348] [<c10baef6>] __sync_filesystem+0x37/0x62 kernel: [ 3840.643358] [<c10bb062>] sync_filesystem+0x3c/0x3f kernel: [ 3840.643369] [<c10a2def>] generic_shutdown_super+0x1c/0xca kernel: [ 3840.643380] [<c10a2eba>] kill_block_super+0x1d/0x31 kernel: [ 3840.643390] [<c10a3833>] deactivate_super+0x48/0x5a kernel: [ 3840.643401] [<c10b385c>] mntput_no_expire+0x5e/0x89 kernel: [ 3840.643411] [<c10b41cf>] sys_umount+0x277/0x29b kernel: [ 3840.643423] [<c10b4200>] sys_oldumount+0xd/0xf kernel: [ 3840.643434] [<c1002813>] sysenter_do_call+0x12/0x32 kernel: [ 3840.643444] 1 lock held by umount/4902: kernel: [ 3840.643449] #0: (&type->s_umount_key#24){++++..}, at: [<c10a382e>] deactivate_super+0x43/0x5a Sergey |