[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <455CEB48.5000906@s5r6.in-berlin.de>
Date: Thu, 16 Nov 2006 23:50:48 +0100
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Mattia Dongili <malattia@...ux.it>, Andrew Morton <akpm@...l.org>,
linux-kernel@...r.kernel.org,
linux1394-devel@...ts.sourceforge.net, bcollins@...ian.org
Subject: Re: 2.6.19-rc5-mm2
Mattia Dongili wrote:
> On Thu, Nov 16, 2006 at 07:29:35PM +0100, Stefan Richter wrote:
>> Could you also test one or even better both of:
>> - 2.6.19-rc5 plus
>> http://me.in-berlin.de/~s5r6/linux1394/updates/2.6.19-rc5/2.6.19-rc5_ieee1394_v204_experimental.patch.bz2
>> (these are the same FireWire drivers as in -rc5-mm2)
>
> the oops disappear
>
>> and/ or
>> - 2.6.19-rc5-mm2 minus
>> http://www.it.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc5/2.6.19-rc5-mm2/broken-out/git-ieee1394.patch
>
> the oops is there again.
> I suppose git-ieee1394 is the one then...
On the contrary, it's very likely _not_ git-ieee1394.
> dmesg:
> http://oioio.altervista.org/linux/2.6.19-rc5-test1-ok
> http://oioio.altervista.org/linux/2.6.19-rc5-mm2-1-ko
I will look at it tomorrow.
> next step (smells like bisection) if for tomorrow :)
Unless you are eager to get results faster, let me think about where
this superfluous node_entry could come from. Perhaps a run-time test of
-mm by myself is in order; I am currently on 2.6.19-rc4 plus that patch
at me.in-berlin.de. Could spare you a lot of time if I find out more. :-)
Thanks for the help,
--
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