Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Frank Neuber <frank.neuber@kernelport.de>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: Florian Fainelli <florian@openwrt.org>,
	Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: AU1550 Kernel bug detected[#1]  clockevents_register_device
Date: Wed, 28 Jan 2009 11:31:50 +0100	[thread overview]
Message-ID: <1233138710.28527.539.camel@t60p> (raw)
In-Reply-To: <20090128093846.GA25402@roarinelk.homelinux.net>

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

  parent reply	other threads:[~2009-01-28 10:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27  8:44 AU1550 Kernel bug detected[#1] clockevents_register_device Frank Neuber
2009-01-27  9:11 ` Manuel Lauss
2009-01-27  9:18   ` Florian Fainelli
2009-01-27  9:23     ` Florian Fainelli
2009-01-27 10:13   ` Frank Neuber
2009-01-27 12:11     ` Manuel Lauss
2009-01-27 12:42       ` Frank Neuber
2009-01-28  9:19         ` Frank Neuber
2009-01-28  9:38           ` Manuel Lauss
2009-01-28  9:45             ` Manuel Lauss
2009-01-28 10:38               ` Frank Neuber
2009-01-28 10:31             ` Frank Neuber [this message]
2009-01-29 21:35       ` Ralf Baechle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1233138710.28527.539.camel@t60p \
    --to=frank.neuber@kernelport.de \
    --cc=florian@openwrt.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mano@roarinelk.homelinux.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox