Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 147724 Details for
Bug 222550
inconsistent lock state, with new firewire driver
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
Firewire dmesg output from before today's HAL update
fw-prob.txt (text/plain), 4.82 KB, created by
Michel Alexandre Salim
on 2007-02-09 03:45:48 UTC
(
hide
)
Description:
Firewire dmesg output from before today's HAL update
Filename:
MIME Type:
Creator:
Michel Alexandre Salim
Created:
2007-02-09 03:45:48 UTC
Size:
4.82 KB
patch
obsolete
>================================= >[ INFO: inconsistent lock state ] >2.6.20-1.2922.fc7 #1 >--------------------------------- >inconsistent {softirq-on-W} -> {in-softirq-W} usage. >swapper/0 [HC0[0]:SC1[1]:HE0:SE0] takes: > (&k->k_lock){-+..}, at: [<ffffffff80457ef4>] klist_next+0x24/0x8a >{softirq-on-W} state was registered at: > [<ffffffff802a51b8>] __lock_acquire+0x454/0xa50 > [<ffffffff8020b39b>] kfree+0x26c/0x27e > [<ffffffff802a5a91>] lock_acquire+0x4c/0x65 > [<ffffffff80457ef4>] klist_next+0x24/0x8a > [<ffffffff80263a05>] _spin_lock+0x25/0x31 > [<ffffffff80457ef4>] klist_next+0x24/0x8a > [<ffffffff803b0678>] __device_attach+0x0/0xb > [<ffffffff803af887>] bus_for_each_drv+0x52/0x7d > [<ffffffff803b070a>] device_attach+0x6a/0x7e > [<ffffffff803af80d>] bus_attach_device+0x24/0x4c > [<ffffffff803ae6c3>] device_add+0x3b6/0x55b > [<ffffffff8029d936>] init_waitqueue_head+0x1f/0x30 > [<ffffffff803ae881>] device_register+0x19/0x1d > [<ffffffff8067d348>] acpi_scan_init+0xda/0x1a4 > [<ffffffff80269c43>] init+0x1e7/0x3ae > [<ffffffff802a48e1>] trace_hardirqs_on+0x11a/0x13e > [<ffffffff8025cf38>] child_rip+0xa/0x12 > [<ffffffff80263cb0>] _spin_unlock_irq+0x2b/0x31 > [<ffffffff8025c6bc>] restore_args+0x0/0x30 > [<ffffffff80269a5c>] init+0x0/0x3ae > [<ffffffff8025cf2e>] child_rip+0x0/0x12 > [<ffffffffffffffff>] 0xffffffffffffffff >irq event stamp: 1991913 >hardirqs last enabled at (1991912): [<ffffffff80263d26>] _spin_unlock_irqrestore+0x3f/0x47 >hardirqs last disabled at (1991913): [<ffffffff80263d88>] _spin_lock_irqsave+0x13/0x3c >softirqs last enabled at (1991890): [<ffffffff80211c21>] __do_softirq+0xda/0xe3 >softirqs last disabled at (1991899): [<ffffffff8025d2ac>] call_softirq+0x1c/0x28 > >other info that might help us debug this: >1 lock held by swapper/0: > #0: (&card->lock){.+..}, at: [<ffffffff881d195f>] fw_core_handle_bus_reset+0x3b/0x548 [fw_core] > >stack backtrace: > >Call Trace: > <IRQ> [<ffffffff802a3bc1>] print_usage_bug+0x162/0x173 > [<ffffffff802a43db>] mark_lock+0x139/0x411 > [<ffffffff802a5139>] __lock_acquire+0x3d5/0xa50 > [<ffffffff80256a89>] klist_children_put+0x0/0xf > [<ffffffff802a5a91>] lock_acquire+0x4c/0x65 > [<ffffffff80457ef4>] klist_next+0x24/0x8a > [<ffffffff80263a05>] _spin_lock+0x25/0x31 > [<ffffffff80457ef4>] klist_next+0x24/0x8a > [<ffffffff881d349e>] :fw_core:update_unit+0x0/0x2f > [<ffffffff803adb02>] next_device+0x9/0x19 > [<ffffffff803adb80>] device_for_each_child+0x36/0x59 > [<ffffffff881d326e>] :fw_core:fw_node_event+0x110/0x17b > [<ffffffff881d18cb>] :fw_core:fw_node_create+0x2a/0x83 > [<ffffffff881d1cd9>] :fw_core:fw_core_handle_bus_reset+0x3b5/0x548 > [<ffffffff88209baf>] :fw_ohci:bus_reset_tasklet+0x1ae/0x1bb > [<ffffffff802915f7>] tasklet_action+0x5e/0xb2 > [<ffffffff80211ba6>] __do_softirq+0x5f/0xe3 > [<ffffffff8025d2ac>] call_softirq+0x1c/0x28 > [<ffffffff8026bdfc>] do_softirq+0x39/0x9f > [<ffffffff802914cd>] irq_exit+0x4e/0x50 > [<ffffffff8026bfb0>] do_IRQ+0x14e/0x170 > [<ffffffff8025c666>] ret_from_intr+0x0/0xf > <EOI> [<ffffffff80260f3e>] __sched_text_start+0xafe/0xb36 > [<ffffffff80385834>] acpi_processor_idle+0x1e7/0x4cc > [<ffffffff8038583e>] acpi_processor_idle+0x1f1/0x4cc > [<ffffffff80385834>] acpi_processor_idle+0x1e7/0x4cc > [<ffffffff8038564d>] acpi_processor_idle+0x0/0x4cc > [<ffffffff8038564d>] acpi_processor_idle+0x0/0x4cc > [<ffffffff802483dc>] cpu_idle+0xa1/0xc4 > [<ffffffff80269a3a>] rest_init+0x2b/0x2d > [<ffffffff80663810>] start_kernel+0x260/0x262 > [<ffffffff80663158>] _sinittext+0x158/0x15f > >Losing some ticks... checking if CPU frequency changed. >fw_sbp2: logged in to sbp2 unit fw0.1 >fw_sbp2: - management_agent_address: 0xfffff0030000 >fw_sbp2: - command_block_agent_address: 0xffc0fffff0100000 >fw_sbp2: - status write address: 0x000100000000 >scsi5 : SBP-2 IEEE-1394 >fw_sbp2: agent reset write rcode=0 >fw_sbp2: sbp2_scsi_abort >fw_sbp2: no command orb status, rcode=17 >scsi 5:0:0:0: Direct-Access WD 5000AAJS Externa 107a PQ: 0 ANSI: 4 >fw_sbp2: status write for unknown orb >fw_sbp2: no command orb status, rcode=17 >fw_core: Unsolicited response >fw_core: Unsolicited response >fw_sbp2: status write for unknown orb >fw_sbp2: no command orb status, rcode=17 >fw_sbp2: sbp2_scsi_abort >fw_sbp2: no command orb status, rcode=17 >fw_sbp2: sbp2_scsi_abort >fw_sbp2: no command orb status, rcode=17 >sd 5:0:0:0: scsi: Device offlined - not ready after error recovery >sd 5:0:0:0: rejecting I/O to offline device >sd 5:0:0:0: rejecting I/O to offline device >sd 5:0:0:0: rejecting I/O to offline device >sdc : READ CAPACITY failed. >sdc : status=0, message=00, host=1, driver=00 >sdc : sense not available. >sd 5:0:0:0: rejecting I/O to offline device >sdc: Write Protect is off >sdc: Mode Sense: 00 00 00 00 >sd 5:0:0:0: rejecting I/O to offline device >sdc: asking for cache data failed >sdc: assuming drive cache: write through >sd 5:0:0:0: Attached scsi disk sdc >sd 5:0:0:0: Attached scsi generic sg3 type 0 >fw_core: created new fw device fw0 (0 config rom retries)
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 222550
: 147724