1180:0832 firewire - "blocked for more than 120 seconds"

Bug #728033 reported by Carl Karsten
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I have the problem in #371434 - following the advice I added acpiphp to /etc/modules, rebooted.

I think tried pugging/unplugging various firewire express cards and an esata express card. tail /var/log/syslog showed the cards coming and going. good.

Then I hooked up a dv cam to firewire, tried pugging/unplugging the same cards, various results, Then plugged in a card, nothing logged, then:

Mar 2 13:32:58 dhcp126 kernel: [ 2259.100267] firewire_ohci: failed to write phy reg
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930072] INFO: task kworker/0:0:1740 blocked for more than 120 seconds.
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930076] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Mar 2 13:35:20 dhcp126 kernel: [ 2400.930078] kworker/0:0 D 0000000000000000 0 1740 2 0x00000000
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930082] ffff880123c5d920 0000000000000046 ffff880123c5dfd8 ffff880123c5c000
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930086] 0000000000013b00 ffff88012161dea0 ffff880123c5dfd8 0000000000013b00
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930089] ffff880117958000 ffff88012161db00 ffff880123c5d900 7fffffffffffffff

Mar 2 13:35:20 dhcp126 kernel: [ 2400.930093] Call Trace:
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930101] [<ffffffff815befad>] schedule_timeout+0x26d/0x2e0
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930120] [<ffffffffa005b930>] ? report_lost_node+0x0/0x50 [firewire_core]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930125] [<ffffffff81080375>] ? queue_work_on+0x25/0x30
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930127] [<ffffffff810803bf>] ? queue_work+0x1f/0x30
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930130] [<ffffffff815bea69>] wait_for_common+0xd9/0x180
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930135] [<ffffffffa005b956>] ? report_lost_node+0x26/0x50 [firewire_core]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930138] [<ffffffff8105f0d0>] ? default_wake_function+0x0/0x20
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930143] [<ffffffff81335882>] ? acpi_os_execute_deferred+0x0/0x36
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930145] [<ffffffff815bebed>] wait_for_completion+0x1d/0x20
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930150] [<ffffffffa00554ea>] fw_core_remove_card+0x11a/0x150 [firewire_core]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930154] [<ffffffffa0055000>] ? dummy_read_phy_reg+0x0/0x10 [firewire_core]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930158] [<ffffffffa0055010>] ? dummy_update_phy_reg+0x0/0x10 [firewire_core]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930162] [<ffffffffa0055020>] ? dummy_send_request+0x0/0x20 [firewire_core]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930166] [<ffffffffa0055040>] ? dummy_send_response+0x0/0x20 [firewire_core]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930170] [<ffffffffa0055060>] ? dummy_cancel_packet+0x0/0x10 [firewire_core]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930175] [<ffffffffa0055070>] ? dummy_enable_phys_dma+0x0/0x10 [firewire_core]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930179] [<ffffffffa0055080>] ? dummy_allocate_iso_context+0x0/0x20 [firewire_core]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930184] [<ffffffffa0084790>] ? ohci_free_iso_context+0x0/0x140 [firewire_ohci]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930188] [<ffffffffa00550a0>] ? dummy_start_iso+0x0/0x10 [firewire_core]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930200] [<ffffffffa0082bf0>] ? ohci_stop_iso+0x0/0xa0 [firewire_ohci]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930204] [<ffffffffa0084c91>] pci_remove+0x41/0x1f0 [firewire_ohci]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930207] [<ffffffff812ffc02>] pci_device_remove+0x52/0x120
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930212] [<ffffffff813b8d85>] __device_release_driver+0x75/0xe0
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930214] [<ffffffff813b8e1d>] device_release_driver+0x2d/0x40
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930217] [<ffffffff813b88cb>] bus_remove_device+0x7b/0xa0
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930219] [<ffffffff813b5b67>] device_del+0x127/0x1b0
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930222] [<ffffffff813b5c06>] device_unregister+0x16/0x30
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930225] [<ffffffff812faa4c>] pci_stop_bus_device+0x8c/0xa0
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930228] [<ffffffff812fa9fb>] pci_stop_bus_device+0x3b/0xa0
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930233] [<ffffffffa00a2fb9>] disable_device+0x89/0x160 [acpiphp]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930235] [<ffffffff813361d8>] ? acpi_os_signal_semaphore+0x21/0x2c
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930239] [<ffffffffa00a3e80>] acpiphp_disable_slot+0x30/0x60 [acpiphp]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930243] [<ffffffffa00a3edd>] acpiphp_check_bridge.clone.7+0x2d/0x100 [acpiphp]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930247] [<ffffffffa00a43ca>] handle_hotplug_event_bridge+0x1ba/0x350 [acpiphp]
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930250] [<ffffffff813361d8>] ? acpi_os_signal_semaphore+0x21/0x2c
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930253] [<ffffffff8133847a>] ? acpi_bus_get_device+0x2a/0x43
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930256] [<ffffffff81345757>] acpi_ev_notify_dispatch+0x67/0x7e
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930259] [<ffffffff813358ab>] acpi_os_execute_deferred+0x29/0x36
@
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930262] [<ffffffff810815bd>] process_one_work+0x11d/0x420
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930265] [<ffffffff810822c3>] worker_thread+0x163/0x360
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930267] [<ffffffff81082160>] ? worker_thread+0x0/0x360
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930270] [<ffffffff81086fa6>] kthread+0x96/0xa0
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930273] [<ffffffff8100ce24>] kernel_thread_helper+0x4/0x10
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930276] [<ffffffff81086f10>] ? kthread+0x0/0xa0
Mar 2 13:35:20 dhcp126 kernel: [ 2400.930278] [<ffffffff8100ce20>] ? kernel_thread_helper+0x0/0x10

Mar 2 13:37:20 dhcp126 kernel: [ 2520.930071] INFO: task kworker/0:0:1740 blocked for more than 120 seconds.
Mar 2 13:37:20 dhcp126 kernel: [ 2520.930074] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar 2 13:37:20 dhcp126 kernel: [ 2520.930076] kworker/0:0 D 0000000000000000 0 1740 2 0x00000000
Mar 2 13:37:20 dhcp126 kernel: [ 2520.930080] ffff880123c5d920 0000000000000046 ffff880123c5dfd8 ffff880123c5c000
Mar 2 13:37:20 dhcp126 kernel: [ 2520.930084] 0000000000013b00 ffff88012161dea0 ffff880123c5dfd8 0000000000013b00
Mar 2 13:37:20 dhcp126 kernel: [ 2520.930087] ffff880117958000 ffff88012161db00 ffff880123c5d900 7fffffffffffffff
Mar 2 13:37:20 dhcp126 kernel: [ 2520.930091] Call Trace:
Mar 2 13:37:20 dhcp126 kernel: [ 2520.930098] [<ffffffff815befad>] schedule_timeout+0x26d/0x2e0

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-5-generic 2.6.38-5.32
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: juser 1390 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xdb320000 irq 48'
   Mixer name : 'Analog Devices AD1984A'
   Components : 'HDA:11d4194a,103c30e7,00100400 HDA:11c11040,103c1378,00100200'
   Controls : 18
   Simple ctrls : 11
Date: Wed Mar 2 14:35:56 2011
Frequency: This has only happened once.
HibernationDevice: RESUME=UUID=21392b65-30ba-4697-970b-442ceb73d2cb
MachineType: Hewlett-Packard HP EliteBook 8530w
PccardctlIdent:
 Socket 0:
   product info: "RICOH", "Bay8Controller", "", ""
   manfid: 0x0000, 0x0000
   function: 254 (unknown)
PccardctlStatus:
 Socket 0:
   3.3V 16-bit PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-5-generic root=UUID=3317761c-92b4-4446-b0b7-37aa0fd7a762 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-5-generic N/A
 linux-backports-modules-2.6.38-5-generic N/A
 linux-firmware 1.47
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/08/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PDV Ver. F.11
dmi.board.name: 30E7
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 90.26
dmi.chassis.asset.tag: uAnywhere
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDVVer.F.11:bd12/08/2009:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.11:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.26:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8530w
dmi.product.version: F.11
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Carl Karsten (carlfk) wrote :
Revision history for this message
Carl Karsten (carlfk) wrote :

bug 371434 that is. (markup mixup)

Revision history for this message
Stefan Richter (stefan-r-ubz) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Carl Karsten, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

summary: - firewire - "blocked for more than 120 seconds"
+ 1180:0832 firewire - "blocked for more than 120 seconds"
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.