public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - FH <studium@profihost.com>
To: Stephen Evanchik <evanchsa@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SATA ahci Bug in 2.6.19.x
Date: Thu, 25 Jan 2007 22:24:28 +0100	[thread overview]
Message-ID: <45B9200C.7070808@profihost.com> (raw)
In-Reply-To: <a71293c20701220600v426f0efdyc23dd945852f71c0@mail.gmail.com>

Hello....

Nobody here who cares???

Stefan

Stephen Evanchik schrieb:
> On 1/22/07, Stefan Priebe - FH <studium@profihost.com> wrote:
> 
>> I've an Asus A8V Mainboard which works wonderful with a 2.6.18.X kernel.
>> But i cannot use the SATA Controller with a 2.6.19.x Kernel.
> 
> 
> I also have an Asus A8V motherboard that cannot boot a newer kernel
> because the SATA controller does not come up properly. I have tried
> kernels 2.6.19.2 and 2.6.20-rc5 with no luck. It looks like later
> kernels don't recognize the proper IRQ of the device as compared to
> the 2.6.18 boot logs.
> 
>> "ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI 21 (level, low) -> IRQ 21"
>> "ahci 0000:00:0f.0: AHCI 0001.0000 32 slots 4 ports 3 Gbps 0xf impl IDE
>> mode"
>> "ahci 0000:00:0f.0: flags: 64bit ncq pm led clo pmp pio slum part "
>> "ata1: SATA max UDMA/133 cmd 0xFFFFC20000004D00 ctl 0x0 bmdma 0x0 irq 
>> 1277"
>> "ata2: SATA max UDMA/133 cmd 0xFFFFC20000004D80 ctl 0x0 bmdma 0x0 irq 
>> 1277"
>> "ata3: SATA max UDMA/133 cmd 0xFFFFC20000004E00 ctl 0x0 bmdma 0x0 irq 
>> 1277"
>> "ata4: SATA max UDMA/133 cmd 0xFFFFC20000004E80 ctl 0x0 bmdma 0x0 irq 
>> 1277"
> 
> 
> Similar output as above.
> 
> 
> Does any one have any ideas?
> 
> 
> Stephen


  reply	other threads:[~2007-01-25 21:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-22  8:02 SATA ahci Bug in 2.6.19.x Stefan Priebe - FH
2007-01-22 14:00 ` Stephen Evanchik
2007-01-25 21:24   ` Stefan Priebe - FH [this message]
2007-01-26  3:25   ` Luming Yu
2007-01-26  4:46     ` Stephen Evanchik
2007-01-26  5:22       ` Luming Yu
2007-01-26  6:18         ` Stephen Evanchik
2007-01-26 10:33           ` Alan
2007-01-26  9:19         ` Stefan Priebe - FH
2007-01-30 10:44           ` Stefan Priebe - FH
     [not found] <7G2pJ-2iX-23@gated-at.bofh.it>
     [not found] ` <7G828-3zn-3@gated-at.bofh.it>
     [not found]   ` <7HpWX-3D2-5@gated-at.bofh.it>
     [not found]     ` <7Hrci-5ou-5@gated-at.bofh.it>
     [not found]       ` <7HrP4-6t8-1@gated-at.bofh.it>
     [not found]         ` <7Hvzs-3Tj-23@gated-at.bofh.it>
     [not found]           ` <7IYJ1-281-27@gated-at.bofh.it>
2007-02-14  8:57             ` Manuel Metz
2007-02-21 11:55               ` Tejun Heo
2007-02-21 16:46                 ` Manuel Metz
2007-02-24  6:25                   ` Tejun Heo
2007-02-24  7:55                     ` Jeff Garzik
2007-02-26  8:32                       ` Manuel Metz

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=45B9200C.7070808@profihost.com \
    --to=studium@profihost.com \
    --cc=evanchsa@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox