SATA error (which should have been fixed before ...)

English Hardware
1

Hi everyone,

I’m running Suse 11 on a x86_64 Platform 512MB Ram, graphic/sound and Lan onboard

first I wonder why my /var/log/messages filled up so quickly.
It seems that this error occures (nearl) every second:

Oct 12 15:10:45 server kernel: ata4.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6
Oct 12 15:10:45 server kernel: ata4: hard resetting link
Oct 12 15:10:45 server kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 12 15:10:45 server kernel: ata4.00: configured for UDMA/33
Oct 12 15:10:45 server kernel: ata4: EH complete

First: the ata4 is wrongly detected. It’s a SATA II with 3 Gbps
Second: I got the latest kernel up and running: Linux server 2.6.27-default #1 SMP Fri Oct 10 20:46:32 CEST 2008 x86_64 x86_64 x86_64 GNU/Linux
Third: I read about a simmilar problem on the old 2.6.16 Kernel, but it should have been solved long ago.

The BIOS correctly detect’s the disk.
I tried booting with apic=no, but without any effect.

Any help would be highly appreciated !!

TIA

may

2

try press and hold Shift on the keyboard when booting the installation media. This starts the text-mode boot menu instead

3

… and then ?

4

Hello please ?!

5

what do you mean?

Tell us what happens using text mode

6

… nothing the boot process just went on …

or do you mean booting from install DVD ?

7

Try “noapic”, it works for me.

8

Yes, booting from the DVD - of course!

9

Well, ok I booted with “noacpi” and it send me to the repair menu. I did a complete check of the sys but no errors found. I tried the “rescue” option afterwords and no SATA problems were shown in the messages, but a misconfigured disk claiming to be only a SATA-I drive with 1.5 GBps instead of a SATA-II 3GBps.

I edited the /boot/grub/menu.lst and append noacpi & acpi=no to the boot command line, but the system seems to ignore them completely. Hence the error is still present in /var/log/messages.

Any ideas ?

10

No, I wrote “noapic”, please try that. “noacpi” is totally different.

11

Hi, thanks for your reply.

… yes, acpi was a typo of course. I corrected it, but still doesen’t solve the case. The error is still present:

ata4.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6
ata4: hard resetting link
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: configured for UDMA/33
ata4: EH complete
ata4.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6
ata4: hard resetting link
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: configured for UDMA/33
ata4: EH complete

I did a “dmesg |grep -i apic”:

dmesg |grep -i apic
Command line: root=/dev/disk/by-id/scsi-SATA_ST380215AS_9RX9KZY0-part3 resume=/dev/sdb2 vga=0x31a noapic
ACPI: APIC 1DFC0390, 005C (r1 A M I OEMAPIC 11000709 MSFT 97)
Detected use of extended apic ids on hypertransport bus
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x81] disabled)
ACPI: Skipping IOAPIC probe due to ‘noapic’ option.
Using ACPI for processor (LAPIC) configuration information
MPTABLE: APIC at: 0xFEE00000
I/O APIC #1 Version 20 at 0xFEC00000.
Setting APIC routing to flat
Kernel command line: root=/dev/disk/by-id/scsi-SATA_ST380215AS_9RX9KZY0-part3 resume=/dev/sdb2 vga=0x31a noapic
Using local APIC timer interrupts.
APIC timer calibration result 12500450
Detected 12.500 MHz APIC timer.

Do you know which config file holds the configuration for the sata drives ?

12

Any ideas ?