Re: libata reset-seq merge broke sata_sil on sh



On Thu, May 10, 2007 at 01:28:19PM +0200, Tejun Heo wrote:
Paul Mundt wrote:
[--snip, thanks a lot for the detailed report--]
However, if I go back before any of the reset changes were introduced,
things were working fine, and there were no problems with waiting for
the reset. Ideas?

* Does your drive start spun down when it boots? Can you post dmesg
with printk timestamp turned on with kernel prior to reset-seq merge?

Yes, it's spun down at boot. I'll get the logs with the timestamps and
the results of the mdelay() incrementing in the morning when I've got the
board handy again.

On Thu, May 10, 2007 at 01:53:48PM +0200, Tejun Heo wrote:
* According to the report, things still work till 27c78b37 - commit for
the actual merge and there's no related change till the current master
from there. So, which commit actually breaks detection? Or is
detection just flaky after b8cffc6a?

The detection is simply flaky after that point, however before the
current master it never hit the 35 second point (and thus never implied
that the link was down). I'll double check the bisect log to see if there
was anything beyond that that may have caused it.

The -ENODEV at least implies that the SRST fails, so at least that's a
starting point.

One other curious thing is that it seems to misreport the IRQ. In this
case the log indicates 0, whereas it's actually on IRQ 66. When the
system is booted, /proc/interrupts reflects that sata_sil is on the
proper IRQ (even when it's reported as 0 in the boot printk()).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages

  • Re: soundcard SoundBlaster PCI128 or SoundBlaster live1024 problem
    ... > What messages are you getting from boot log and dmesg? ... ACPI tables contain no PCI IRQ routing entries ... RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize ... USB Universal Host Controller Interface driver v2.2 ...
    (comp.os.linux.hardware)
  • Enabling acpi support renders system unbootable (was: kernel: ad8: FAILURE - READ timed out LBA=
    ... Whenever I try to boot my desktop workstation with FreeBSD, it suddenly just hangs there forever. ... The hard drive is connected to an onboard Promise FastTrak (atapci1: port 0x8000-0x803f,0x7800-0x780f,0x7400-0x747f mem 0xab800000-0xab800fff,0xab000000-0xab01ffff irq 11 at device 14.0 on pci0) controller on my Asus p4s8x motherboard. ... ata1: reiniting channel .. ... So I thought that maybe, just disabling dma and write caching would let me boot my system, otherwise normally, and thereby effectively narrowing down the problem to dma and write caching. ...
    (freebsd-questions)
  • Re: Black screen on booting
    ... Check and recheck your video adapter driver and BIOS. ... Your IRQ sharing seems normal to me. ... >down overnight, but if you wait till it warms up, it will boot as follows: ...
    (microsoft.public.win2000.general)
  • Re: MCP2 on Intel 945 Mobo advice?
    ... You might try setting that and see if you can get a solitary IRQ assigned to the SBLive so that the other devices will go off and find a different IRQ. ... From other OS/2 work before, with the whole thing 'working', but with all the IRQ's the way 'it works', I thought that I would try the option during the boot run to let it examine hardware. ... So I tried Veit Kannegieser's PCIIRQ.ARJ 'force' IRQ suite off his web site both to cross research this with the PCI sniff tests as well as possibly 'fix' the IRQ for at least the SBLive 5.1 PCI add-in card. ...
    (comp.os.os2.setup.misc)
  • 5.2.1 boot-install
    ... I downloaded the 2 meg boot floppy for installing FreeBSD 5.2.1. ... wanted to burn it to a CD (I usually install via ftp, ... pci0: on pcib0 ... 0xffa80000-0xffafffff,0xf0000000-0xf7ffffff irq 11 at device 2.0 on ...
    (freebsd-questions)