From: Jesper Krogh <jesper@krogh.cc>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ryan Jackson <rjackson@lnxi.com>, Dave Olsen <dolsen@lnxi.com>,
linux-mtd@lists.infradead.org,
David Woodhouse <David.Woodhouse@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.29-rc6
Date: Thu, 26 Feb 2009 20:31:35 +0100 [thread overview]
Message-ID: <49A6EE17.4070102@krogh.cc> (raw)
In-Reply-To: <alpine.LFD.2.00.0902260941090.3111@localhost.localdomain>
Linus Torvalds wrote:
> Dave Olsen <dolsen@lnxi.com>,
> Ryan Jackson <rjackson@lnxi.com>, David.Woodhouse@intel.com,
> linux-mtd@lists.infradead.org
>
>
> On Thu, 26 Feb 2009, Jesper Krogh wrote:
>>
>> Booting up 2.6.29-rc6 gave me this one in dmesg...
>>
>> [ 21.136149] ck804xrom ck804xrom_init_one(): Unable to register resource 0x00000000ff000000-0x00000000ffffffff - kernel bug?
>
> Well, it _is_ a kernel bug, but it's in that stupid driver. It does
> everything wrong, including printing out a scary message.
I've seen that before.. (even reported it before). It just "slipped"
into the cut'n'paste It was the following stuff that I intended to report.
>> [ 21.136269] WARNING: at arch/x86/mm/ioremap.c:208 __ioremap_caller+0x359/0x390()
>
> This is a different, but related warning, since the driver is doing an
> ioremap across different resources. The warning is directly related to the
> fact that the resource wasn't actually valid to begin with.
>
> What does "cat /proc/iomem" say?
http://krogh.cc/~jesper/iomem.txt
>> System is fully operational, but I didnt get it in 2.6.26.8 (most recent
>> kernel tried on this hardware).
>
> The ioremap() warning is newish, and may be what made you notice the
> previous (just one-line) crappy warning.
>
> Quite frankly, having looked at that horrible driver, I would seriously
> consider disabling it. Stuff like that should not be allowed to exist.
Being a "stupid" user, I pick the easy way to build a fresh kernel:
1) pick the distro .config
2) make oldconfig
3) Let the kernel load what it think it needs.
4) Report if I see and strange stuff (warnings / bugs / oops) or
misbehaviour.
So I dont know if I need that driver for anything vital. Should I care?
Or shouldn't it "just work"?
--
Jesper
next prev parent reply other threads:[~2009-02-26 19:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.00.0902222023520.3111@localhost.localdomain>
[not found] ` <49A679E8.1010301@krogh.cc>
2009-02-26 17:17 ` MTD_CK804XROM warning (Was: Linux 2.6.29-rc6) Marcin Slusarz
2009-02-26 17:53 ` Linux 2.6.29-rc6 Linus Torvalds
2009-02-26 19:22 ` David Woodhouse
2009-02-26 19:31 ` Jesper Krogh [this message]
2009-02-26 19:36 ` David Woodhouse
2009-02-26 19:46 ` Jesper Krogh
2009-02-26 19:49 ` David Woodhouse
2009-02-26 20:53 ` Carl-Daniel Hailfinger
2009-02-26 20:32 ` Linus Torvalds
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=49A6EE17.4070102@krogh.cc \
--to=jesper@krogh.cc \
--cc=David.Woodhouse@intel.com \
--cc=dolsen@lnxi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rjackson@lnxi.com \
--cc=torvalds@linux-foundation.org \
/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