All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: izvekov@lps.ele.puc-rio.br
Cc: linux-kernel@vger.kernel.org
Subject: Re: libata sata_sil broken on 2.6.13.1
Date: Thu, 15 Sep 2005 01:37:23 -0400	[thread overview]
Message-ID: <43290893.7070207@pobox.com> (raw)
In-Reply-To: <60519.200.141.106.169.1126727337.squirrel@correio.lps.ele.puc-rio.br>

izvekov@lps.ele.puc-rio.br wrote:
> I managed to get a serial cable. Now follows the dmesg, from where libata
> starts until it dies.
> 
> ata1: SATA max UDMA/100 cmd 0xF881E080 ctl 0xF881E08A bmdma 0xF881E000 irq 11
> ata2: SATA max UDMA/100 cmd 0xF881E0C0 ctl 0xF881E0CA bmdma 0xF881E008 irq 11
> ata1: dev 0 ATA, max UDMA/133, 234441648 sectors: lba48
> ata1(0): applying Seagate errata fix
> ata1: dev 0 configured for UDMA/100
> scsi0 : sata_sil
> irq 11: nobody cared (try booting with the "irqpoll" option)


This one is related to libata.  Known problem:
     http://bugzilla.kernel.org/show_bug.cgi?id=3880

Silicon Image 311x throws interrupts after we told the hardware to 
disable interrupts, but only for a few certain devices and/or PATA 
bridges.  I only have theories as to the solution.

I made a failed attempt to solve it here:
     http://search.luky.org/linux-kernel.2005/msg14830.html

This patch from Albert Lee might solve it, but the patch itself needs 
bug fixes:
     http://marc.theaimsgroup.com/?t=112628285200005&r=1&w=2

Also, defining ATA_IRQ_TRAP in include/linux/libata.h may work around 
the problem.

Plenty more info available on request.  Nothing changed in this area 
with regards to 2.6.12/2.6.13, so I presume that ACPI has simply exposed 
the existing problem for you.  :(

     Jeff



  parent reply	other threads:[~2005-09-15  5:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14  1:17 libata sata_sil broken on 2.6.13.1 izvekov
2005-09-14  1:22 ` izvekov
2005-09-14 19:48 ` izvekov
2005-09-14 20:36   ` izvekov
2005-09-14 23:46     ` Andrew Morton
2005-09-15  0:19       ` izvekov
2005-09-15  5:37   ` Jeff Garzik [this message]
2005-09-15 13:27     ` Alan Cox
2005-09-15 20:13       ` izvekov
2005-09-15 22:30         ` Alan Cox
2005-09-15 22:56           ` izvekov
2005-09-16  3:42           ` izvekov
2005-09-16  6:41             ` Jeff Garzik
2005-09-16 22:10               ` Matheus Izvekov
2005-09-22  2:46                 ` Jeff Garzik
2005-09-16  0:07     ` izvekov
2005-10-22 11:55     ` problem with libata and ich6m - 2.6.14-rc5 Raphael Jacquot
2005-10-22 12:18       ` Mark Lord

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43290893.7070207@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=izvekov@lps.ele.puc-rio.br \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.