Messages in this thread |  | | | From | Alistair John Strachan <> | | Subject | Re: ohci1394 regression in 2.6.19-rc1 (was Re: Merge window closed: v2.6.19-rc1) | | Date | Thu, 5 Oct 2006 23:37:17 +0100 |
On Thursday 05 October 2006 23:16, Stefan Richter wrote: [snip] > It does indeed look like the nodemgr kicked in prematurely. After some > other messages from lower levels and from different contexts, there is > also a sign of nodemgr_check_irm_capability() failing (it can only fail > this early): > > [ 40.298112] ieee1394: Current remote IRM is not 1394a-2000 compliant, > resetting... > > OK. Enough with the boring details. Maybe the following patch doesn't > work entirely as I intended: > "ieee1394: nodemgr: switch to kthread api, replace reset semaphore" > http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=comm >itdiff_plain;h=d2f119fe319528da8c76a1107459d6f478cbf28c > > I think if you revert the next patch first... > "ieee1394: nodemgr: convert nodemgr_serialize semaphore to mutex" > http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=comm >itdiff_plain;h=cab8d154e2ed43fe1495aa0e18103e747552891b > > ...you can then revert the 'switch to kthread' patch and see if the > message "Running dma failed because Node ID is not valid" disappears. > Would be nice if you could test that.
Of course. I tried reverting these two, and it has not helped.
-rw-r--r-- 1 root root 562133 2006-10-05 23:29 kernel/drivers/ieee1394/ieee1394.ko
(KBUILD only regenerated this file, I hope that's correct.)
http://devzero.co.uk/~alistair/ieee1394/dmesg-2.6.19-rc1-reverts.gz
-- Cheers, Alistair.
Final year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |