LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Dan Aloni <da-x@monatomic.org>,
linux-kernel-list <linux-kernel@vger.kernel.org>,
dwmw2@infradead.org
Subject: Re: e2b2rom_init_one(): Unable to register resource
Date: Sun, 18 Feb 2007 18:13:38 +0100 [thread overview]
Message-ID: <200702181813.38814.ak@suse.de> (raw)
In-Reply-To: <20070218104222.GC10865@cvg>
[adding mtd maintainer]
On Sunday 18 February 2007 11:42, Cyrill Gorcunov wrote:
> On Sat, Feb 17, 2007 at 11:29:19PM +0200, Dan Aloni wrote:
> | Hello,
> |
> | I'm running the x86_64 arch of Linux 2.6.20 on a Supermicro X6DH8-XG2
> | board and I got this during boot:
> |
> | [248660.950695] device id = 2440
> | [248660.950699] device id = 2480
> | [248660.950703] device id = 24c0
> | [248660.950706] device id = 24d0
> | [248660.950709] matched device = 24d0
> | [248660.950712] matched device id 24d0
> | [248660.950716] pci_read_config_byte : 4
> | [248660.950723] esb2rom: esb2rom_init_one(): Unable to register resource
> | 0xffffffffffc00000-0xffffffff - kernel bug?
> | [248660.950729] esb2rom: ioremap(ffffffffffc00000, 100400000) failed
> | [248660.956859] retVal = -19
> |
> | Looks like some kind of a 64-bit portability bug...
> |
> | --
> | Dan Aloni
> | XIV LTD, http://www.xivstorage.com
> | da-x (at) monatomic.org, dan (at) xiv.co.il
> | -
> | To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> | the body of a message to majordomo@vger.kernel.org
> | More majordomo info at http://vger.kernel.org/majordomo-info.html
> | Please read the FAQ at http://www.tux.org/lkml/
> |
>
> Hi,
>
> here is a patch attached to the mail. You may test it. Actually
> I have no 64bit machine to test it and I'm worried about the
> patch accuracy. So be carefull testing it. I sent a copy of the
> message to Andi Kleen (who is a maintainer of X86-64 port) may be
> we should wait for its answer ;)
Making window->phys u32 seems like a cleaner fix.
(untested)
-Andi
Fix 64bit arithmetic bug in esb2rom.c
Index: linux/drivers/mtd/maps/esb2rom.c
===================================================================
--- linux.orig/drivers/mtd/maps/esb2rom.c
+++ linux/drivers/mtd/maps/esb2rom.c
@@ -95,8 +95,8 @@
struct esb2rom_window {
void __iomem* virt;
- unsigned long phys;
- unsigned long size;
+ u32 phys;
+ u32 size;
struct list_head maps;
struct resource rsrc;
struct pci_dev *pdev;
next prev parent reply other threads:[~2007-02-18 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 21:29 Dan Aloni
2007-02-18 7:52 ` Cyrill Gorcunov
2007-02-18 8:00 ` Cyrill Gorcunov
2007-02-18 10:42 ` Cyrill Gorcunov
2007-02-18 11:29 ` Dan Aloni
2007-02-18 12:36 ` Cyrill Gorcunov
2007-02-18 17:13 ` Andi Kleen [this message]
2007-02-18 17:49 ` Dan Aloni
2007-02-18 19:36 ` Cyrill Gorcunov
2007-02-18 20:05 ` Cyrill Gorcunov
2007-02-19 15:58 ` Cyrill Gorcunov
2007-02-19 21:16 ` Dan Aloni
2007-02-20 10:15 ` Cyrill Gorcunov
2007-02-20 11:27 ` Cyrill Gorcunov
2007-02-26 17:08 ` Cyrill Gorcunov
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=200702181813.38814.ak@suse.de \
--to=ak@suse.de \
--cc=da-x@monatomic.org \
--cc=dwmw2@infradead.org \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: e2b2rom_init_one(): Unable to register resource' \
/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
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).