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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 12 Jun 2008 14:34:36 -0400
From:	"John Stoffel" <john@...ffel.org>
To:	linux-kernel@...r.kernel.org
CC:	i2c@...sensors.org, netdev@...r.kernel.org
Subject: 2.6.26-rc5: CFI: Found no ck804xrom @ffc00000 device at
   location zero


Hi,

I'm running a AMD X2 box with 4gb of RAM, Ubuntu 8.04 x86_64.  I just
rebooted the system and I notice the following repeated messages
(errors? warnings?) in my dmesg output.  I think this is from my
nForce ethernet chips, but I'm not sure.

[   13.268005] ck804xrom ck804xrom_init_one(): Unable to register resource 0x00000000ff000000-0x00000000ffffffff - kernel bug?
[   13.336752] i2c-adapter i2c-0: nForce2 SMBus adapter at 0x1c00
[   13.336786] i2c-adapter i2c-1: nForce2 SMBus adapter at 0x1c40
[   13.376771] CFI: Found no ck804xrom @ffc00000 device at location zero
[   13.398810] JEDEC: Found no ck804xrom @ffc00000 device at location zero
[   13.398822] CFI: Found no ck804xrom @ffc00000 device at location zero
[   13.398883] JEDEC: Found no ck804xrom @ffc00000 device at location zero
[   13.398889] CFI: Found no ck804xrom @ffc00000 device at location zero
[   13.398928] JEDEC: Found no ck804xrom @ffc00000 device at location zero
[   13.398934] CFI: Found no ck804xrom @ffc10000 device at location zero
[   13.398971] JEDEC: Found no ck804xrom @ffc10000 device at location zero
[   13.398980] CFI: Found no ck804xrom @ffc10000 device at location zero
[   13.399042] JEDEC: Found no ck804xrom @ffc10000 device at location zero
[   13.399048] CFI: Found no ck804xrom @ffc10000 device at location zero
[   13.399579] JEDEC: Found no ck804xrom @ffc10000 device at location zero
[   13.399579] CFI: Found no ck804xrom @ffc20000 device at location zero
[   13.399582] JEDEC: Found no ck804xrom @ffc20000 device at location zero
[   13.399591] CFI: Found no ck804xrom @ffc20000 device at location zero
[   13.399652] JEDEC: Found no ck804xrom @ffc20000 device at location zero
[   13.399658] CFI: Found no ck804xrom @ffc20000 device at location zero
[   13.399696] JEDEC: Found no ck804xrom @ffc20000 device at location zero
[   13.399702] CFI: Found no ck804xrom @ffc30000 device at location zero
[   13.399739] JEDEC: Found no ck804xrom @ffc30000 device at location zero
[   13.399748] CFI: Found no ck804xrom @ffc30000 device at location zero
[   13.399809] JEDEC: Found no ck804xrom @ffc30000 device at location zero
[   13.399815] CFI: Found no ck804xrom @ffc30000 device at location zero
[   13.399853] JEDEC: Found no ck804xrom @ffc30000 device at location zero
[   13.399859] CFI: Found no ck804xrom @ffc40000 device at location zero
[   13.399896] JEDEC: Found no ck804xrom @ffc40000 device at location zero
[   13.399905] CFI: Found no ck804xrom @ffc40000 device at location zero
[   13.400587] JEDEC: Found no ck804xrom @ffc40000 device at location zero
[   13.400593] CFI: Found no ck804xrom @ffc40000 device at location zero
[   13.400631] JEDEC: Found no ck804xrom @ffc40000 device at location zero
[   13.400637] CFI: Found no ck804xrom @ffc50000 device at location zero
[   13.400674] JEDEC: Found no ck804xrom @ffc50000 device at location zero
[   13.400683] CFI: Found no ck804xrom @ffc50000 device at location zero
[   13.400744] JEDEC: Found no ck804xrom @ffc50000 device at location zero
[   13.400750] CFI: Found no ck804xrom @ffc50000 device at location zero
[   13.400788] JEDEC: Found no ck804xrom @ffc50000 device at location zero
[   13.400795] CFI: Found no ck804xrom @ffc60000 device at location zero
[   13.400831] JEDEC: Found no ck804xrom @ffc60000 device at location zero
[   13.400840] CFI: Found no ck804xrom @ffc60000 device at location zero
[   13.400902] JEDEC: Found no ck804xrom @ffc60000 device at location zero
[   13.400908] CFI: Found no ck804xrom @ffc60000 device at location zero
[   13.401577] JEDEC: Found no ck804xrom @ffc60000 device at location zero
[   13.401577] CFI: Found no ck804xrom @ffc70000 device at location zero
.
.
.
.
.
.
[   13.420781] JEDEC: Found no ck804xrom @fff60000 device at location zero
[   13.420789] CFI: Found no ck804xrom @fff60000 device at location zero
[   13.420851] JEDEC: Found no ck804xrom @fff60000 device at location zero
[   13.420857] CFI: Found no ck804xrom @fff60000 device at location zero
[   13.420895] JEDEC: Found no ck804xrom @fff60000 device at location zero
[   13.420901] CFI: Found no ck804xrom @fff70000 device at location zero
[   13.421576] JEDEC: Found no ck804xrom @fff70000 device at location zero
[   13.421576] CFI: Found no ck804xrom @fff70000 device at location zero
[   13.421626] JEDEC: Found no ck804xrom @fff70000 device at location zero
[   13.421632] CFI: Found no ck804xrom @fff70000 device at location zero
[   13.421670] JEDEC: Found no ck804xrom @fff70000 device at location zero
[   13.421698] CFI: Found no ck804xrom @fff80000 device at location zero
[   13.421881] JEDEC: Found no ck804xrom @fff80000 device at location zero
[   13.421908] CFI: Found no ck804xrom @fff80000 device at location zero
[   13.422716] JEDEC: Found no ck804xrom @fff80000 device at location zero
[   13.422728] CFI: Found no ck804xrom @fff80000 device at location zero
[   13.422752] Found: PMC Pm49FL004
[   13.422775] ck804xrom @fff80000: Found 1 x8 devices at 0x0 in 8-bit bank
[   13.486876] number of JEDEC chips: 1
[   13.486897] cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.




These messages seem really damn noisy, esp since it does find a JEDEC chip eventually.  I'll try and see about bisecting this later on if I get a chance.

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