public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Campbell <brad-UPaTOFvTz1K6c6uEtOJ/EA@public.gmane.org>
To: Jeff Garzik <jgarzik-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
Cc: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Sergey Vlasov <vsu-u2l5PoMzF/Uox3rIn2DAYQ@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: libata Promise driver regression 2.6.5->2.6.6
Date: Tue, 18 May 2004 20:22:28 +0400	[thread overview]
Message-ID: <40AA3844.9010403@wasp.net.au> (raw)
In-Reply-To: <40A91410.5040408-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>

Jeff Garzik wrote:
 > Brad Campbell wrote:
 >
 >> Err.. yeah, I'm not quite sure why but a make oldconfig on my 2.6.5
 >> config did not enable apic.
 >> Rather than boot 2.6.5 noapic, I enabled apic on 2.6.6 and the dmesg
 >> compares perfectly to the 2.6.5 one, right up until it tries to probe
 >> the 9th disk where it proceeds to dma timeout and then cease to listen
 >> to anything..
 >
 >
 >
 > Although it does sound like a non-libata problem, would you be willing
 > to do a quick test, to verify that?

If you thought it might help I'd probably be willing to hang upside down from the doorframe.

 > The attached patch, against kernel 2.6.5, updates libata to the code
 > that is found in kernel 2.6.6.

Yep, see the attached dmesg.. problem followed the libata code :p(

All I did was a cp -av on my 2.6.5 tree, applied your patch, added a -testbk to the Makefile, did a
make oldconfig && make && make modules_install && reboot

Hangs for a while at the end and then spits out a dma timeout, never to recover.

my grub entry was a direct copy of the 2.6.5 one with -test added to it.

What now batman?


Brad..


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click

  parent reply	other threads:[~2004-05-18 16:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A6974D8E5F98D511BB910002A50A6647615FB7A9@hdsmsx403.hd.intel.com>
     [not found] ` <A6974D8E5F98D511BB910002A50A6647615FB7A9-N2PTB0HCzHJviC08c4yzC1DQ4js95KgL@public.gmane.org>
2004-05-17 19:01   ` libata Promise driver regression 2.6.5->2.6.6 Len Brown
2004-05-17 19:13     ` Brad Campbell
2004-05-17 19:35       ` Jeff Garzik
     [not found]         ` <40A91410.5040408-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2004-05-18 16:22           ` Brad Campbell [this message]
     [not found]             ` <40AA3844.9010403-UPaTOFvTz1K6c6uEtOJ/EA@public.gmane.org>
2004-05-18 16:51               ` Brad Campbell
2004-05-18 17:19               ` Jeff Garzik
     [not found] <40A7A278.7010405@wasp.net.au>
2004-05-16 17:49 ` Sergey Vlasov

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=40AA3844.9010403@wasp.net.au \
    --to=brad-upatofvtz1k6c6uetoj/ea@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=jgarzik-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=vsu-u2l5PoMzF/Uox3rIn2DAYQ@public.gmane.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