linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Sommrey <jo@sommrey.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, "Brown, Len" <len.brown@intel.com>
Subject: Re: [SATA] libata-dev queue updated
Date: Fri, 4 Mar 2005 21:33:30 +0100	[thread overview]
Message-ID: <20050304203330.GA14557@sommrey.de> (raw)
In-Reply-To: <4228A3D4.8050906@pobox.com>

On Fri, Mar 04, 2005 at 01:07:16PM -0500, Jeff Garzik wrote:
> Joerg Sommrey wrote:
> >On Fri, Mar 04, 2005 at 02:10:14AM -0500, Jeff Garzik wrote:
> >
> >>Joerg Sommrey wrote:
> >>
> >>>On Thu, Mar 03, 2005 at 11:09:26PM -0500, Jeff Garzik wrote:
> >>>
> >>>
> >>>>Joerg Sommrey wrote:
> >>>>
> >>>>
> >>>>>On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Joerg Sommrey wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>Jeff Garzik wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>>Patch:
> >>>>>>>>http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2
> >>>>>>>
> >>>>>>>
> >>>>>>>Still not usable here.  The same errors as before when backing up:
> >>>>>>
> >>>>>>Please try 2.6.11 without any patches.
> >>>>>
> >>>>>Plain 2.6.11 doesn't work either.  All of 2.6.10-ac11, 2.6.11-rc5,
> >>>>>2.6.11-rc5 + 2.6.11-rc5-bk4-libata-dev1.patch and 2.6.11 fail with the
> >>>>>same symptoms. 
> >>>>>
> >>>>>Reverting to stable 2.6.10-ac8 :-)
> >>>>
> >>>>Does reverting the attached patch in 2.6.11 (apply with patch -R) fix 
> >>>>things?
> >>>>
> >>>
> >>>
> >>>Still the same with this patch reverted.
> >>
> >>Does reverting the attached patch in 2.6.11 fix things?  (apply with 
> >>patch -R)
> >>
> >>This patch reverts the entire libata back to 2.6.10.
> >>
> >
> >I'm confused.  Still the same with everything reverted.  What shall I do
> >now?
> 
> Well, first, thanks for your patience in narrowing this down.
> 
> This means we have eliminated libata as a problem source, but we still 
> have the rest of the kernel go to through :)
> 
> Try disabling ACPI with 'acpi=off' or 'pci=biosirq' to see if that fixes 
> things.
> 
I tried both settings with plain 2.6.11. Almost the same results, in my
impression apci=off causes the failure to appear even faster.

-jo

-- 
-rw-r--r--  1 jo users 63 2005-03-04 20:54 /home/jo/.signature

  reply	other threads:[~2005-03-04 20:45 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3Ds62-5AS-3@gated-at.bofh.it>
2005-03-02 20:34 ` [SATA] libata-dev queue updated Joerg Sommrey
2005-03-02 22:43   ` Jeff Garzik
2005-03-03 19:32     ` Joerg Sommrey
2005-03-04  4:09       ` Jeff Garzik
2005-03-04  6:37         ` Joerg Sommrey
2005-03-04  7:10           ` Jeff Garzik
2005-03-04 17:49             ` Joerg Sommrey
2005-03-04 18:07               ` Jeff Garzik
2005-03-04 20:33                 ` Joerg Sommrey [this message]
2005-03-04 20:43                   ` Jeff Garzik
2005-03-04 22:06                     ` Joerg Sommrey
2005-03-04 22:32                       ` Joerg Sommrey
2005-06-07  7:00 Bene Martin
  -- strict thread matches above, loose matches on Subject: below --
2005-06-04  6:08 Jeff Garzik
2005-06-04 15:17 ` Greg Stark
2005-06-04 17:48   ` Jeff Garzik
2005-06-04 18:50     ` Adrian Bunk
2005-06-04 19:05       ` Jeff Garzik
2005-06-04 19:15         ` Greg Stark
2005-06-04 19:19           ` Jeff Garzik
2005-06-05  2:25             ` Greg Stark
2005-06-05  2:30               ` Jeff Garzik
2005-06-05  5:30                 ` Greg Stark
2005-06-22 16:15                 ` Mark Lord
2005-06-22 20:23                   ` Jeff Garzik
2005-06-23  3:39                     ` Mark Lord
2005-06-05  2:40               ` Drew Winstel
2005-06-05  2:58               ` Jim Crilly
2005-06-06 16:01   ` Mark Lord
2005-06-07  1:57     ` Greg Stark
2005-06-07 11:20       ` Brad Campbell
2005-06-08  8:33         ` Mark Lord
2005-06-07 13:15           ` Brad Campbell
2005-06-08  8:37       ` Mark Lord
2005-06-07 13:51         ` Greg Stark
2005-06-08 10:30           ` Mark Lord
2005-06-08  8:51       ` Mark Lord
2005-06-07 13:09         ` Domenico Andreoli
2005-06-07 17:53         ` Jeff Garzik
2005-03-10  5:40 Jeff Garzik
2005-03-29  9:12 ` kern.petr
2005-03-08 11:20 Jeff Garzik
2005-03-02  2:40 Jeff Garzik
2005-02-19  8:40 Jeff Garzik
2005-02-19 16:58 ` Andre Tomt
2005-02-19 17:09   ` Jeff Garzik
2005-02-13 20:33 Jeff Garzik
2004-10-27  6:52 Jeff Garzik
2004-10-27  6:53 ` Jeff Garzik
2004-10-27 22:53 ` Rob van Nieuwkerk
2004-10-27 23:03   ` Jeff Garzik
2004-10-15  8:04 Jeff Garzik
2004-10-15 17:15 ` Jeff Garzik

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=20050304203330.GA14557@sommrey.de \
    --to=jo@sommrey.de \
    --cc=akpm@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=len.brown@intel.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;
as well as URLs for NNTP newsgroup(s).