David Luyer wrote:
> I have a system which was working perfectly with A7V motherboard and
> kernel 2.6.13.2. After a motherboard upgrade to A7V-E SE (only other
> changes being graphics card and power supply), kernel 2.6.13.2 hung
> during initial ATA detection, so I am now attempting to get 2.6.15.1
> working (as the latest stable kernel).
>
> 2.6.15.1 can read the hard disks, just very slowly (with many timeouts,
> I am now leaving the system overnight to boot up - so far, it has
> autorun the MD arrays and detected the ReiserFS format).
>
> System summary:
> Motherboard: ASUS A7V-E SE
> BIOS: 1007; set to IDE in "SATA Mode" (IDE or RAID)
> Kernel: 2.6.15.1 with CONFIG_SCSI_SATA_VIA
> Hard disks: 2 x WDC WD2500KS-00M Rev 02.0; Linux MD RAID1
>
> Hangs are experienced followed by the following lines on the console:
> ata1: slow completion (cmd ef)
> ata2: slow completion (cmd ef)
> -- above messages occur once each per boot
> ata1: command 0x25 timeout, stat 0x50 host_stat 24
> ata2: command 0x25 timeout, stat 0x50 host_stat 24
> -- above messages occur numerous times,
> perhaps even every block read
>
> Other interesting bootup messages include numerous PCI: Via IRQ fixup
> messages (presumably one per device, definitely including the SATA
> controller).
>
> dmesg and lspci -vvx will be sent through if the boot completes,
> assuming the kernel log buffer is long enough to perform a dmesg
> with information other than all the timeouts once the boot
> completes. Or, if the boot doesn't complete by tomorrow, I'll
> look into building a kernel with significantly reduced SATA
> command timeouts (and a larger kernel log buffer if required),
> to try and get this information.
>
> Any initial suggestions in the interim? I need PCI Express
> for a graphics card to support a Dell 3007FPW, avoided nForce4
> due to excessive random corruption with the nForce4 and WD2500KS
> drives under Windows in another system, and would really prefer
> not to buy yet another motherboard, so I would really like
> to get this working.
It seems like IRQ routing problem. The driver never receives the
completion interrupts. When it times out, it finds out that the command
is actually complete, so the slow completion messages. Turning off ACPI
seems to be a popular solution.
>
> Random irrelevant evil thoughts: could Intel VT make BIOS hard
> disk access viable for Linux by proxying disk accesses through
> a second virtual machine? Or even Windows SATA driver support
> through SAMBA to a disk image on a Windows machine on a second
> virtual machine?
Oh well, it would be much easier/better to just fix the original problem.
--
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
