[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <452593AC.3000406@s5r6.in-berlin.de>
Date: Fri, 06 Oct 2006 01:22:20 +0200
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Alistair John Strachan <s0348365@....ed.ac.uk>
CC: Linus Torvalds <torvalds@...l.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
bcollins@...ian.org, linux1394-devel@...ts.sourceforge.net
Subject: Re: ohci1394 regression in 2.6.19-rc1
Alistair John Strachan wrote:
> On Thursday 05 October 2006 23:16, Stefan Richter wrote:
>> ...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.
Thanks.
> -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.)
Yes.
> http://devzero.co.uk/~alistair/ieee1394/dmesg-2.6.19-rc1-reverts.gz
One more thing you could to try if you can spare the time:
Build and boot Linux _2.6.18_ after applying this patchkit:
http://me.in-berlin.de/~s5r6/linux1394/updates/
This is only little more of 1394 stuff than what is now in 2.6.19-rc1.
This test would at least give a hint if changes sent via the linux1394
git tree are the culprit, or some change from outside.
In case you are familiar with quilt, take the quilt variant of the
patchkit instead of the collapsed patch. Short instructions on the
patchkits are on the website. The quilt patchset would allow to hunt
down the bad patch by bisection --- if the bad one is among the 1394
updates in the first place.
--
Stefan Richter
-=====-=-==- =-=- --==-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists