From: Jesper Krogh <jesper@krogh.cc>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.29-rc6
Date: Thu, 26 Feb 2009 12:15:52 +0100 [thread overview]
Message-ID: <49A679E8.1010301@krogh.cc> (raw)
In-Reply-To: <alpine.LFD.2.00.0902222023520.3111@localhost.localdomain>
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?
[ 21.136258] resource map sanity check conflict: 0xff000000 0xffffffff
0xff700000 0xffffffff reserved
[ 21.136267] ------------[ cut here ]------------
[ 21.136269] WARNING: at arch/x86/mm/ioremap.c:208
__ioremap_caller+0x359/0x390()
[ 21.136271] Hardware name: Sun Fire X2200 M2 with Quad Core Processor
[ 21.136273] Info: mapping multiple BARs. Your kernel is fine.Modules
linked in: ck804xrom(+) mtd chipreg pcspkr(+) shpchp button pci_hotplug
i2c_nforce2 i2c_core map_funcs evdev ext3 jbd mbcache sg sd_mod usbhid
hid amd74xx sata_nv tg3 ata_generic libphy ehci_hcd libata ohci_hcd
forcedeth scsi_mod usbcore thermal processor fan thermal_sys fuse
[ 21.136289] Pid: 3843, comm: modprobe Not tainted 2.6.29-rc6 #2
[ 21.136291] Call Trace:
[ 21.136298] [<ffffffff8023d352>] warn_slowpath+0xf2/0x130
[ 21.136301] [<ffffffff8023d62a>] __call_console_drivers+0x6a/0x90
[ 21.136304] [<ffffffff8023e1fe>] printk+0x4e/0x60
[ 21.136306] [<ffffffff8023e1fe>] printk+0x4e/0x60
[ 21.136309] [<ffffffff8036b520>] match_pci_dev_by_id+0x0/0x60
[ 21.136313] [<ffffffff8024360e>] iomem_map_sanity_check+0xbe/0xd0
[ 21.136316] [<ffffffff80229799>] __ioremap_caller+0x359/0x390
[ 21.136320] [<ffffffffa01eb1f6>] init_ck804xrom+0x1f6/0x62c [ck804xrom]
[ 21.136322] [<ffffffffa01eb1f6>] init_ck804xrom+0x1f6/0x62c [ck804xrom]
[ 21.136326] [<ffffffff80275eac>] tracepoint_update_probe_range+0x1c/0xb0
[ 21.136329] [<ffffffffa01eb000>] init_ck804xrom+0x0/0x62c [ck804xrom]
[ 21.136332] [<ffffffff8020903b>] _stext+0x3b/0x160
[ 21.136335] [<ffffffff80359141>] __up_read+0x21/0xb0
[ 21.136340] [<ffffffff80256495>]
__blocking_notifier_call_chain+0x65/0x90
[ 21.136343] [<ffffffff80265604>] sys_init_module+0xb4/0x200
[ 21.136346] [<ffffffff8020c35b>] system_call_fastpath+0x16/0x1b
[ 21.136348] ---[ end trace f807e12658961c2d ]---
System is fully operational, but I didnt get it in 2.6.26.8 (most recent
kernel tried on this hardware).
--
Jesper
next prev parent reply other threads:[~2009-02-26 11:16 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 4:31 Linux 2.6.29-rc6 Linus Torvalds
2009-02-23 14:07 ` Linux 2.6.29-rc6 - Fix oops in i915_gem_retire_requests Karsten Wiese
2009-02-26 11:15 ` Jesper Krogh [this message]
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
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
2009-02-26 19:55 ` Jesper Krogh
2009-02-26 20:33 ` Linus Torvalds
2009-02-26 20:43 ` Jesper Krogh
2009-02-26 21:19 ` john stultz
2009-02-26 21:35 ` Jesper Krogh
2009-02-26 21:46 ` john stultz
2009-02-26 21:54 ` Thomas Gleixner
2009-02-26 22:04 ` Jesper Krogh
2009-02-27 6:30 ` Jesper Krogh
2009-03-01 13:51 ` Jesper Krogh
2009-02-26 21:49 ` Linus Torvalds
2009-03-01 15:04 ` Jesper Krogh
2009-02-26 21:54 ` john stultz
2009-02-26 22:06 ` Thomas Gleixner
2009-02-26 22:24 ` Linus Torvalds
2009-02-26 22:31 ` Linus Torvalds
2009-02-26 22:31 ` john stultz
2009-02-26 22:40 ` Linus Torvalds
2009-02-26 22:59 ` john stultz
2009-02-27 7:33 ` Ingo Molnar
2009-02-27 20:50 ` john stultz
2009-02-27 6:47 ` Jesper Krogh
2009-02-27 20:35 ` john stultz
2009-03-01 20:13 ` Jesper Krogh
2009-03-02 9:53 ` Jesper Krogh
2009-03-02 21:27 ` john stultz
2009-03-03 6:04 ` Jesper Krogh
2009-03-03 19:53 ` john stultz
2009-03-03 20:19 ` Jesper Krogh
2009-03-03 22:22 ` john stultz
2009-03-04 15:30 ` Jesper Krogh
2009-03-04 18:36 ` Jesper Krogh
2009-03-04 18:57 ` John Stultz
2009-03-05 2:39 ` john stultz
2009-03-05 2:52 ` john stultz
2009-03-05 8:43 ` Ingo Molnar
2009-03-06 3:13 ` john stultz
2009-03-06 3:54 ` john stultz
2009-03-06 11:34 ` Ingo Molnar
2009-03-09 20:42 ` Jesper Krogh
2009-03-10 4:26 ` Linus Torvalds
2009-03-10 11:29 ` Thomas Gleixner
2009-03-10 19:42 ` Jesper Krogh
2009-03-10 22:22 ` Thomas Gleixner
2009-03-15 19:53 ` Jesper Krogh
2009-03-16 18:40 ` Jesper Krogh
2009-03-15 1:19 ` Linus Torvalds
2009-03-15 15:44 ` Jesper Krogh
2009-03-15 18:09 ` Linus Torvalds
2009-03-15 18:38 ` Jesper Krogh
2009-03-15 19:02 ` Linus Torvalds
2009-03-15 19:52 ` Jesper Krogh
2009-03-16 18:59 ` Jesper Krogh
2009-03-16 19:32 ` Linus Torvalds
2009-03-17 1:43 ` john stultz
2009-03-17 8:14 ` Ingo Molnar
2009-03-17 15:48 ` Linus Torvalds
2009-03-17 16:13 ` Ingo Molnar
2009-03-17 16:28 ` Linus Torvalds
2009-03-17 16:40 ` Ingo Molnar
2009-03-17 17:28 ` Olivier Galibert
2009-03-21 9:11 ` Jesper Krogh
2009-03-21 10:06 ` Ingo Molnar
2009-03-15 20:32 ` Linus Torvalds
2009-03-03 20:39 ` Jesper Krogh
2009-03-03 22:16 ` john stultz
2009-03-04 5:36 ` Jesper Krogh
2009-03-01 15:09 ` Jesper Krogh
2009-03-01 15:44 ` Linux 2.6.29-rc6 (clocksource) Sitsofe Wheeler
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=49A679E8.1010301@krogh.cc \
--to=jesper@krogh.cc \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).