> We upgraded a Compaq Prosigna 300 to 2.2.X. 2.2.6 gives the following
> messages on bootup. What does this "CACHE INCORRECTLY CONFIGURED" mean?
> Anything dangerous for our server?
Not at all. You have configured the both sym53c8xx and ncr53c8xx drivers
and the sym53c8xx driver just misdetects your 810 as a 810A. It is in
fact a tiny bug in the sym driver (a 'continue' that should have been
a 'break'). I will make the fix available soon.
> sym53c8xx: at PCI bus 0, device 12, function 0
> sym53c8xx: 53c810a detected
> sym53c810a-0: rev=0x02, base=0x2200000, io_port=0x7100, irq=15
> sym53c810a-0: ID 7, Fast-10, Parity Checking
> CACHE TEST FAILED: script execution failed.
> start=0000bcf8, pc=0000bd04, end=0000bd18
> CACHE INCORRECTLY CONFIGURED.
> sym53c810a-0: giving up ...
The driver checks the SCRIPTS execution prior to initializing everything.
The script execution failure is due to use of LOAD/STORE SCRIPTS
instructions that are not supported by the 810 (not A) and the sym53c8xx
driver does not attach this 810 device. (The cache misconfiguration is a
spurious message in that situation since the 810 (not A) just didn't
recognise the LOAD/STORE instructions).
> ncr53c8xx: at PCI bus 0, device 12, function 0
> ncr53c8xx: 53c810 detected
> ncr53c810-0: rev=0x02, base=0x2200000, io_port=0x7100, irq=15
> ncr53c810-0: ID 7, Fast-10, Parity Checking
> ncr53c810-0: restart (scsi reset).
> scsi0 : ncr53c8xx - version 3.2
> scsi : 1 host.
The ncr53c8xx is called at its detection entry point after the sym53c8xx
and has attached the 810 normally.
If you want to get rid of the sym53c8xx messages, you can make another
kernel that does not configure this driver , or exclude your 810 device
for this driver from the boot command line: 'sym53c8xx=excl:0x7100'
Gérard.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/