From: Frank Neuber <linux-mips@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: Tue, 27 Jan 2009 13:42:40 +0100 [thread overview]
Message-ID: <1233060160.28527.497.camel@t60p> (raw)
In-Reply-To: <20090127121123.GA17132@roarinelk.homelinux.net>
Am Dienstag, den 27.01.2009, 13:11 +0100 schrieb Manuel Lauss:
> > I think somting is wrong with PCI resource management here.
> > I can't believe that nobody is using the PCI or Cardbus on the AU1550
> > with the current kernel.
>
> I'm no PCI expert, but I'm pretty sure resource assignment is done by
> generic, not mips-specific, code. Please try the linux-pci and/or
> linux-kernel lists.
At the moment I buld a matrix of working kernel versions regarding the
PCI stuff on the AU1550
For now I can say that the versions
2.6.18, 2.6.18-rc1
is crashing after showing the linux banner
2.6.18-rc2, 2.6.18-rc4, 2.6.19, 2.6.20, 2.6.23 produce this:
Skipping PCI bus scan due to resource conflict
The version 2.6.24 has the same behavior as the current git head.
I will inform you about more results
Regards,
Frank
next prev parent reply other threads:[~2009-01-27 12:42 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 [this message]
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
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=1233060160.28527.497.camel@t60p \
--to=linux-mips@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