lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 11 Nov 2008 00:01:52 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Jarkko Lavinen <jlavi@....fi>
Cc:	linux-kernel@...r.kernel.org,
	Doug Thompson <dougthompson@...ssion.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: i82875p_edac: BAR 0 collision

(cc's added)

On Fri, 7 Nov 2008 13:43:55 +0200 Jarkko Lavinen <jlavi@....fi> wrote:

> 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)
> 

Might be an EDAC driver regression.  It might also be a consequence of
PCI address space management fiddlings, but I think most of the changes
there post-date 2.6.26?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ