Description of problem: My firewire modules do not works, meaning no plugged firewire works, and even unplugged yield a call trace in kernel logs (see attachement). This was causing pb already for mga1, that's certainly an upstream bug I guess? Cheers, Chris.
Created attachment 1676 [details] call trace in dmesg
Created attachment 1677 [details] output of lspci
Hi, thanks for reporting this bug. Assigned to the package maintainer. (Please set the status to 'assigned' if you are working on it)
Keywords: (none) => TriagedAssignee: bugsquad => tmb
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Yes it is; with current 3.3.6-desktop-2.mga2: ----------------------------------------------------------------------- "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 240.287027] kworker/0:0 D 0000000000000000 0 4 2 0x00000000 [ 240.287033] ffff88007d3cf9d0 0000000000000046 ffffffff81bbcdc0 ffff88007ff8b700 [ 240.287038] ffff88007d3c43b0 ffff88007d3cffd8 ffff88007d3cffd8 ffff88007d3cffd8 [ 240.287044] ffff88007b18da40 ffff88007d3c43b0 ffff88007d3cfae0 ffff88007d3cfb98 [ 240.287049] Call Trace: [ 240.287058] [<ffffffff8144fa2f>] schedule+0x3f/0x60 [ 240.287064] [<ffffffff8144e0f5>] schedule_timeout+0x2a5/0x320 [ 240.287070] [<ffffffff81122d5f>] ? __inc_zone_state+0x5f/0x70 [ 240.287074] [<ffffffff81123159>] ? zone_statistics+0x99/0xc0 [ 240.287094] [<ffffffffa040baa1>] ? context_get_descriptors+0x71/0xc0 [firewire_ohci] [ 240.287100] [<ffffffff81086191>] ? update_curr+0x141/0x1f0 [ 240.287105] [<ffffffff8144f87a>] wait_for_common+0xda/0x170 [ 240.287110] [<ffffffff8107f3a0>] ? try_to_wake_up+0x2b0/0x2b0 [ 240.287114] [<ffffffff8144f9ed>] wait_for_completion+0x1d/0x20 [ 240.287124] [<ffffffffa03fbc91>] fw_run_transaction+0xf1/0x130 [firewire_core] [ 240.287133] [<ffffffffa03fb860>] ? transmit_phy_packet_callback+0x20/0x20 [firewire_core] [ 240.287142] [<ffffffffa03fb320>] ? fw_core_add_address_handler+0x160/0x160 [firewire_core] [ 240.287147] [<ffffffff8107a400>] ? __wake_up+0x10/0x70 [ 240.287154] [<ffffffffa03fbcd0>] ? fw_run_transaction+0x130/0x130 [firewire_core] [ 240.287162] [<ffffffffa03fb860>] ? transmit_phy_packet_callback+0x20/0x20 [firewire_core] [ 240.287171] [<ffffffffa03f86c8>] read_rom+0x68/0xa0 [firewire_core] [ 240.287179] [<ffffffffa03f87cd>] read_config_rom+0xcd/0x4d0 [firewire_core] [ 240.287183] [<ffffffff8108599d>] ? set_next_entity+0xad/0xd0 [ 240.287191] [<ffffffffa03f9590>] ? fw_device_refresh+0x260/0x260 [firewire_core] [ 240.287199] [<ffffffffa03f95c5>] fw_device_init+0x35/0x310 [firewire_core] [ 240.287207] [<ffffffffa03f9590>] ? fw_device_refresh+0x260/0x260 [firewire_core] [ 240.287213] [<ffffffff8106a9d3>] process_one_work+0x113/0x470 [ 240.287217] [<ffffffff8106b76f>] worker_thread+0x15f/0x350 [ 240.287222] [<ffffffff8106b610>] ? manage_workers.isra.28+0x230/0x230 [ 240.287226] [<ffffffff81070693>] kthread+0x93/0xa0 [ 240.287231] [<ffffffff81459da4>] kernel_thread_helper+0x4/0x10 [ 240.287235] [<ffffffff81070600>] ? kthread_freezable_should_stop+0x70/0x70 [ 240.287239] [<ffffffff81459da0>] ? gs_change+0x13/0x13 [ 240.287243] INFO: task kworker/0:1:10 blocked for more than 120 seconds. [ 240.287246] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 240.287249] kworker/0:1 D 0000000000000000 0 10 2 0x00000000 [ 240.287254] ffff88007d3fb9d0 0000000000000046 0000000000013140 0000000000000286 [ 240.287259] ffff88007d3eda40 ffff88007d3fbfd8 ffff88007d3fbfd8 ffff88007d3fbfd8 [ 240.287264] ffff88007d3c43b0 ffff88007d3eda40 ffff88007d3fb9f0 ffff88007d3fbb98 [ 240.287270] Call Trace:
Keywords: NEEDINFO => (none)CC: (none) => sander.lepik
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
Sorry, but this bug saw no action since over 2 yrs ago. No cauldron package has stayed the same since then. Closing as OLD Please reopen if this report is still valid for _current_ cauldron and/or fully updated Mageia 4
Status: NEW => RESOLVEDCC: (none) => marja11Resolution: (none) => OLD