| View previous topic :: View next topic |
| Author |
Message |
Crimson Rider
Guru
Joined: 23 Jun 2003
Posts: 462
Location: Delft, the Netherlands
|
 Posted: Thu Jun 30, 2005 7:20 am Post subject: SATA disks keep timing out |
 |
|
I have a nice neat system running someplace, and tought I'd use it to a little experimenting.
I've got 3 spare SATA harddisks in there, and set them up in a RAID-5 array to play around with. However, for some strange reason this message keeps turning up in my logs,
| Code: | Jun 30 10:28:38 fireopal ata3: command 0x25 timeout, stat 0x50 host_stat 0x24
Jun 30 10:28:38 fireopal ata4: command 0x35 timeout, stat 0x50 host_stat 0x24
|
And indeed, every now and then the disks are dreadfully slow. This happens when I put the on the motherboards SATA controller but also on a seperate SATA controller card. Can anyone give me a clue as to what this is?
_________________
Code, justify, code - Pitr Dubovich |
|
| Back to top |
|
 |
ikaro
Advocate
Joined: 14 Jul 2003
Posts: 2527
Location: Denmark
|
| Posted: Thu Jun 30, 2005 1:33 pm Post subject: |
|
|
disable APIC in the bios.
_________________
linux: #232767 |
|
| Back to top |
|
|
Crimson Rider
Guru
Joined: 23 Jun 2003
Posts: 462
Location: Delft, the Netherlands
|
| Posted: Thu Jun 30, 2005 1:39 pm Post subject: |
|
|
ok, i'll try that. But why?
_________________
Code, justify, code - Pitr Dubovich |
|
| Back to top |
|
|
ikaro
Advocate
Joined: 14 Jul 2003
Posts: 2527
Location: Denmark
|
| Posted: Thu Jun 30, 2005 2:17 pm Post subject: |
|
|
The APIC Function BIOS feature is used to enable or disable the motherboard's APIC (Advanced Programmable Interrupt Controller).
The APIC is a new distributed set of devices that make up an interrupt controller. In current implementations, it consists of three parts - a local APIC, an I/O APIC and an APIC bus.
If your single-processor motherboard supports APIC and you are using a Win32 operating system (Windows NT, 2000 and XP), it's recommended that you enable this feature to allow faster and better IRQ handling. If you are using a multiprocessor motherboard, you must enable this feature because it's required for IRQ handling in multiprocessor systems.
However, if you are running Windows 95/98, Linux* or a DOS-based operating system on a single-processor motherboard, you must disable this feature. This is because MS-DOS drivers assume they can write directly to the 8259 PIC (APIC did not exist yet in those days!) and its associated IDT entries. Disabling this feature forces the APIC to revert to the legacy 8259 PIC mode.
* : i've added linux there.
resuming: disable APIC and you wont have those problems anymore- i know from experience.
_________________
linux: #232767 |
|
| Back to top |
|
|
Crimson Rider
Guru
Joined: 23 Jun 2003
Posts: 462
Location: Delft, the Netherlands
|
| Posted: Thu Jun 30, 2005 2:18 pm Post subject: |
|
|
Thanx, that was quite insightfull.
_________________
Code, justify, code - Pitr Dubovich |
|
| Back to top |
|
|
MankyD
n00b
Joined: 09 Jul 2003
Posts: 55
|
| Posted: Sun Mar 12, 2006 7:56 pm Post subject: |
|
|
| Any ideas for thos of us who do not have an APIC option in the bios? |
|
| Back to top |
|
|
MankyD
n00b
Joined: 09 Jul 2003
Posts: 55
|
| Posted: Sun Mar 12, 2006 8:49 pm Post subject: |
|
|
| adding 'irqpoll' to the kernel command was the key. |
|
| Back to top |
|
|
|
Kernel & Hardware
