ASL Knowledge Base - The five questions posted most recently:

Kernel reports EDAC i5000: SPD Protocol Error, Bits= 0x40000 ...

Thu, 21 Aug 2008 18:29:58 GMT

Kernel reports EDAC i5000: SPD Protocol Error, Bits= 0x40000 (117 views)

Problem:

The kernel repeatedly prints errors messages similar to the following:

EDAC i5000 MC0: NON-FATAL Errors found!!! 1st NON-FATAL Err Reg= 0x40000

EDAC i5000: SPD Protocol Error, Bits= 0x40000

Description:

This is caused by the optional IPMI card and the i5000_edac kernel module trying to access the platforms EDAC (Error Detection and Correction) information at the same time.

Solution:

The workaround for this problem is to prevent the i5000_edac module from loading.� To do this, add the following line to the /etc/modprobe.d/blacklist file:

blacklist i5000_edac

Kernel panic - not syncing: Machine check

Tue, 19 Aug 2008 15:28:04 GMT

Kernel panic - not syncing: Machine check (494 views)

Problem
The Opteron system crashes and generates the following messages:

CPU 1: Machine Check Exception: 4 Bank 4: f60c200100000813
TSC 377366e1b8aa ADDR 1fef51800
Kernel panic - not syncing: Machine check

Here is another similar machine exception check generated from the utility mcelog.

MCE 0
CPU 1 4 northbridge TSC 511338368e676
ADDR 46a9f888
Northbridge ECC error
ECC syndrome = e3
bit46 = corrected ecc error
bus error 'local node response, request didn't time out
generic read mem transaction
memory access, level generic'
STATUS 9471c00000000a13 MCGSTATUS 0

Here the Northbridge ECC error also indicates bad memory module.

Beside the kernel panic, memory error can also be flagged by the EDAC module:

EDAC k8 MC1: extended error code: ECC error
EDAC k8 MC1: general bus error: participating processor(local node
response), time-out(no timeout) memory transaction type(generic read),
mem or i/o(mem access), cache level(generic)
EDAC MC1: CE page 0xcc9db, offset 0xd38, grain 8, syndrome 0x80, row
0, channel 1, label "": k8_edac


In this example, MC1 is the equivalent of CPU 1.

Solution
The machine exception check indicates the system has a bad memory module. To locate the bad module, first we need to determine which CPU bank containing the bad module. Almost all ASL multi-processor Opteron systems have multiple CPU banks. For example, a dual processor system has two CPU banks while a quad processor system has four CPU banks. The exception is the Marquis K820 of which has only one CPU bank.

When the kernel generates the machine exception check, a CPU ID is given. In the examples above, the CPU ID is 1. To identify the CPU bank, refer to the following tables:

Opteron system configured with single-core processor(s)

CPU ID CPU Bank
0 1
1 2
2 3
3 4

Opteron system configured with dual-core processor(s)

CPU ID CPU Bank
0 1
1 1
2 2
3 2
4 3
5 3
6 4
7 4

Opteron system configured with quad-core processor(s)

CPU ID CPU Bank
0 1
1 1
2 1
3 1
4 2
5 2
6 2
7 2
8 3
9 3
10 3
11 3
12 4
13 4
14 4
15 4

Once the CPU bank number is identified, next locate that bank on the motherboard. Some motherboards such as Tyan S2885 label CPU bank 1 as CPU 0. Other motherboards such as Supermicro H8DCE label CPU bank 1 as CPU 1. Depending on the motherboard model, a CPU bank contains two, four or eight memory slots. The most common configuration is four memory slots per CPU bank.

Now that the bad CPU bank on the motherboard has been located, remove all the memory modules from that bank. Afterward, the system should boot and run properly.

The last step is to locate the bad memory module out of the group. That can be done easily by running memtest86+ on each individual module separately. This is possible because all Opteron motherboards will boot with only one memory module installed.

Memtest86+ can be downloaded here:

ftp://ftp.aslab.com/pub/utility/memtestp.img
ftp://ftp.aslab.com/pub/utility/memtestp.README

To obtain replacement memory modules, please send an Email to techsupport@aslab.com and provide the following information:

1) The serial number or the invoice number of the system
2) The shipping address
3) Brief description of the problem (bad memory)

Marvel driver disk for Windows OS

Mon, 11 Aug 2008 17:12:13 GMT

Marvel driver disk for Windows OS (177 views)

To install Windows 2000/XP/2003, a driver disk is required. The installation guide is provided on page 39.

ftp://ftp.aslab.com/pub/windows/mvSata_Windows_3_6_3/Docs/SW%20Driver%20User%20Manual%20for%20Marvell%20Serial%20ATA%20Host%20Adapters.pdf


The precompiled  binary driver can be downloaded here:

64-bit
ftp://ftp.aslab.com/pub/windows/mvSata_Windows_3_6_3/build/Windows/amd64/Free

32-bit
ftp://ftp.aslab.com/pub/windows/mvSata_Windows_3_6_3/build/Windows/i386/Free

How to download the ASL edition of the Fedora ...

Tue, 29 Jul 2008 13:40:43 GMT

How to download the ASL edition of the Fedora 8 DVD (701 views)

Fedora 8 DVD images are currently available via ftp. They can be reliably downloaded via ftp by using the wget program:

wget --no-passive-ftp -c ftp://updates.aslab.com/pub/isos/fedora/8/Fedora-8-06052008-i386-DVD.iso

wget --no-passive-ftp -c ftp://updates.aslab.com/pub/isos/fedora/8/Fedora-8-06042008-x86_64-DVD.iso

Where can I download ASL Driver CD or RHEL/CentOS ...

Thu, 24 Jul 2008 20:32:52 GMT

Where can I download ASL Driver CD or RHEL/CentOS Device Driver CD? (954 views)

The latest ASL Driver CD can be downloaded at this link. It contains the latest ASL kernel sources and add-on software such as Nvidia binary driver and 3ware RAID management utility.

http://updates.aslab.com/isos/v4.87.iso

To access the contents in the ASL Driver CD, run the following command:

# mount -o loop v4.87.iso /mnt

The latest ASL Laptop Driver CD can be downloaded at this link. This CD provides supported files for the Excalibur laptop models.

http://updates.aslab.com/isos/laptop-1.13.iso

To access the contents in the ASL Laptop Driver CD, run the following command:

# mount -o loop laptop-1.13.iso /mnt

The latest ASL Device Driver CD for RHEL3/CentOS 3.5 can be downloaded here. This CD provide updated (Intel Gigabit/e1000, Adaptec SCSI/aic79xx) or new device drivers (Marvell SATA/mv_sata, Highpoint SATA RAID/hpt_mv, 3ware SATA RAID/3w-9xxx) required during the OS installation.

http://updates.aslab.com/isos/RHEL3/

The latest ASL Device Driver CD for RHEL4/CentOS 4.x can be downloaded here. This CD provide updated (Intel Gigabit/e1000, Adaptec SCSI/aic79xx) or new device drivers (Marvell SATA/mv_sata, Highpoint SATA RAID/hpt_mv, 3ware SATA RAID/3w-9xxx) required during the OS installation.

http://updates.aslab.com/isos/RHEL4/

The latest ASL Device Driver Floppy for SuSE Linux 9.3 can be downloaded here. These floppy images provide updated (Intel Gigabit/e1000) or new device drivers (Marvell SATA/mv_sata, Highpoint SATA RAID/hpt_mv, 3ware SATA RAID/3w-9xxx) required during the OS installation.

http://updates.aslab.com/isos/SuSE93/