linux-mips
[Top] [All Lists]

Re: AU1550 Kernel bug detected[#1] clockevents_register_device

To: Manuel Lauss <mano@roarinelk.homelinux.net>
Subject: Re: AU1550 Kernel bug detected[#1] clockevents_register_device
From: Frank Neuber <frank.neuber@kernelport.de>
Date: Wed, 28 Jan 2009 11:31:50 +0100
Cc: Florian Fainelli <florian@openwrt.org>, Linux-MIPS <linux-mips@linux-mips.org>
In-reply-to: <20090128093846.GA25402@roarinelk.homelinux.net>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <1233045842.28527.459.camel@t60p> <20090127091107.GA15890@roarinelk.homelinux.net> <1233051181.28527.485.camel@t60p> <20090127121123.GA17132@roarinelk.homelinux.net> <1233060160.28527.497.camel@t60p> <1233134374.28527.524.camel@t60p> <20090128093846.GA25402@roarinelk.homelinux.net>
Sender: linux-mips-bounce@linux-mips.org
Am Mittwoch, den 28.01.2009, 10:38 +0100 schrieb Manuel Lauss:
> > Now I think a have to look at 64 problems in the resource management of
> > th PCI subsystem
>
> Do hou have CONFIG_64BIT_PHYS_ADDR=y set in your .config?  If I remember
> correctly, __fixup_bigphys_addr() in alchemy/common/setup.c should take care
> of this 36bit problem (in the same way you did, btw).
It think it was set to no (it was EXPERIMENTAL).
Now ,after I realized what the problem is, I tested this with
CONFIG_64BIT_PHYS_ADDR=y and the kernel 2.6.19 comes up without this
patch.

But the 2.6.23 not. Neither with the patch nor with
CONFIG_64BIT_PHYS_ADDR
I can enjoy again "Skipping PCI bus scan due to resource conflict"
Ahrrr ...

I'll have a look at this.


Regards,
 Frank


<Prev in Thread] Current Thread [Next in Thread>