public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: walt <wa1ter@myrealbox.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.22-rc4 - sata_promise regression since -rc3
Date: Tue, 05 Jun 2007 16:37:39 -0700	[thread overview]
Message-ID: <f44s49$e64$1@sea.gmane.org> (raw)
In-Reply-To: <20070605215256.GT31565@havoc.gtf.org>

Jeff Garzik wrote:
> On Tue, Jun 05, 2007 at 11:31:46PM +0200, Mikael Pettersson wrote:
>> I can easily reproduce the problem in 2.6.22-rc4. There are no
>> sata_promise changes between rc3 and rc4, but Tejun's libata
>> polling SETXFER change was included in rc4. Reverting it makes
>> sata_promise work again for me.
> 
> Ugh.

Reverting Tejun's patch also fixed my boot failure.

00:08.0 RAID bus controller: Promise Technology, Inc. PDC20376 (FastTrak 
376) (rev 02)
         Subsystem: ASUSTeK Computer Inc. A7V8X motherboard
         Flags: bus master, 66MHz, medium devsel, latency 96, IRQ 16
         I/O ports at d400 [size=64]
         I/O ports at d000 [size=16]
         I/O ports at b800 [size=128]
         Memory at f6800000 (32-bit, non-prefetchable) [size=4K]
         Memory at f6000000 (32-bit, non-prefetchable) [size=128K]
         Capabilities: [60] Power Management version 2

00:11.1 IDE interface: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if
  8a [Master SecP PriP])
         Subsystem: ASUSTeK Computer Inc. A7V8X / A7V333 motherboard
         Flags: bus master, medium devsel, latency 32, IRQ 255
         [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
         [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
         [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
         [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
         I/O ports at a400 [size=16]
         Capabilities: [c0] Power Management version 2

The problem is that the controller can't be initialized properly, so
the kernel keeps trying every 5 seconds.  I gave up after about five
failures.  If the actual boot error messages would help I'll need to
copy them by hand -- just say the word.



  reply	other threads:[~2007-06-05 23:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 21:31 Linux 2.6.22-rc4 - sata_promise regression since -rc3 Mikael Pettersson
2007-06-05 21:52 ` Jeff Garzik
2007-06-05 23:37   ` walt [this message]
2007-06-06  6:56   ` Tejun Heo
2007-06-06 10:21     ` [REPOST PATCH] sata_promise: use TF interface for polling NODATA commands Tejun Heo
2007-06-06 15:42       ` walt
2007-06-06 16:05       ` Jeff Garzik
2007-06-06 16:34         ` Alan Cox
2007-06-07 17:20         ` Chuck Ebbert
2007-06-07 17:25           ` Jeff Garzik
2007-06-07 17:30             ` Jeff Garzik
2007-06-07 15:17       ` Jeff Garzik
2007-06-07 15:45         ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2007-06-06 10:36 Linux 2.6.22-rc4 - sata_promise regression since -rc3 Mikael Pettersson
2007-06-05  3:50 Linux 2.6.22-rc4 Linus Torvalds
2007-06-05 16:14 ` Linux 2.6.22-rc4 - sata_promise regression since -rc3 David Greaves

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='f44s49$e64$1@sea.gmane.org' \
    --to=wa1ter@myrealbox.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