From: Jarkko Lavinen <jlavi@iki.fi>
To: linux-kernel@vger.kernel.org
Subject: i82875p_edac: BAR 0 collision
Date: Fri, 7 Nov 2008 13:43:55 +0200 [thread overview]
Message-ID: <20081107114355.GA31730@piipiip.net> (raw)
When I try to load i82875p_edac module on ASUS P4C800 Deluxe in 2.6.26
or 2.6.27 it fails due to BAR 0 collision. On 2.6.25 the
i82875p_edac works just fine.
Should i82875p_setup_overfl_dev() do some additional work to fix the
missing resource of the hidden overflow device?
When I try load i82875p_edac module on 2.6.27 I get
# modprobe i82875p_edac
FATAL: Error inserting i82875p_edac
(/lib/modules/2.6.27.4/kernel/drivers/edac/i82875p_edac.ko): No such device
And dmesg shows (from 2.6.27.4):
EDAC MC: Ver: 2.1.0 Oct 30 2008
EDAC DEBUG: edac_pci_dev_parity_clear()
...
EDAC DEBUG: edac_pci_dev_parity_clear()
EDAC DEBUG: edac_sysfs_setup_mc_kset()
EDAC DEBUG: edac_sysfs_setup_mc_kset() Registered '.../edac/mc' kobject
EDAC DEBUG: i82875p_init_one()
EDAC i82875p: i82875p init one
EDAC DEBUG: i82875p_probe1()
PCI: 0000:00:06.0 reg 10 32bit mmio: [fecf0000, fecf0fff]
pci 0000:00:06.0: device not available because of BAR 0 [0xfecf0000-0xfecf0fff] collisions
EDAC i82875p: i82875p_setup_overfl_dev(): Failed to enable overflow device
EDAC DEBUG: 875p init fail
On 2.6.25.19 loading i82875p_edac works just fine and dmesg shows:
EDAC MC: Ver: 2.1.0 Nov 4 2008
EDAC i82875p: i82875p init one
EDAC MC0: Giving out device to 'i82875p_edac' 'i82875p': DEV 0000:00:00.0
EDAC PCI0: Giving out device to module 'i82875p_edac' controller 'EDAC PCI controller': DEV '0000:00:00.0' (POLLED)
Cheers
Jarkko Lavinen
next reply other threads:[~2008-11-07 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 11:43 Jarkko Lavinen [this message]
2008-11-11 8:01 ` i82875p_edac: BAR 0 collision Andrew Morton
2008-11-12 21:06 ` Jarkko Lavinen
2008-11-18 21:57 ` Jarkko Lavinen
2008-11-23 20:44 ` Jarkko Lavinen
2008-12-16 19:39 ` Jesse Barnes
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=20081107114355.GA31730@piipiip.net \
--to=jlavi@iki.fi \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.