Benjamin Herrenschmidt wrote:
> Could that be related to the fix
>
> [PATCH] libata: fix oops with sparsemem
>
> That Arnd Bergmann just posted ? I'm copying it below in case you
> haven't seen it.
Seems to be the same problem to me. I'll reply in the original thread.
Thanks.
--
tejun
-
To u
Could that be related to the fix
[PATCH] libata: fix oops with sparsemem
That Arnd Bergmann just posted ? I'm copying it below in case you
haven't seen it.
From:
Arnd Bergmann
<[EMAIL PROTECTED]>
To:
[EMAIL PROTECTED]
On Thu, 07 Dec 2006 11:56:32 +0800 Albert Lee <[EMAIL PROTECTED]> wrote:
>
> It seems the opps occurred in the ata_exec_internal(). Could you please
> try the attached patch and see if the older ata_exec_internal() works?
> This can help to narrow it down.
This worked much better:
Waiting for /de
Stephen Rothwell wrote:
> Hi all,
>
> I get an oops during initialisation of the pata_pdc2027x module on a
> POWER 285 machine. This is on a very recent Linus kernel tree
> (ff51a98799931256b555446b2f5675db08de6229) with Paulus' powerpc tree
> (that has now been merged). The oops looks like this:
On Wed, 06 Dec 2006 14:10:15 +0800 Albert Lee <[EMAIL PROTECTED]> wrote:
>
> Where could I download the patched kernel source? There are two
> POWER5 9110-51A boxes here. Maybe I could try to reproduce the problem
> on these boxes.
You can just use Linus' current tree - it exhibits the same proble
Stephen Rothwell wrote:
> Hi all,
>
> I get an oops during initialisation of the pata_pdc2027x module on a
> POWER 285 machine. This is on a very recent Linus kernel tree
> (ff51a98799931256b555446b2f5675db08de6229) with Paulus' powerpc tree
> (that has now been merged). The oops looks like this:
Hi all,
I get an oops during initialisation of the pata_pdc2027x module on a
POWER 285 machine. This is on a very recent Linus kernel tree
(ff51a98799931256b555446b2f5675db08de6229) with Paulus' powerpc tree
(that has now been merged). The oops looks like this:
--
7 matches
Mail list logo
