public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: "Brown, Len" <len.brown@intel.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, James.Bottomley@steeleye.com,
	linux-scsi@vger.kernel.org
Subject: Re: 2.6.13-mm1: hangs during boot ...
Date: Sun, 04 Sep 2005 08:48:52 +1000	[thread overview]
Message-ID: <431A2854.2000604@bigpond.net.au> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B30047FA090@hdsmsx401.amr.corp.intel.com>

Brown, Len wrote:
>>>>Please then try the latest ACPI patch here:
>>>
>>> > 
>>
>>http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches
>>/release/2.6.13/acpi-20050902-2.6.13.diff.gz
>>
>>> > It should apply to vanilla 2.6.13 with a reject in ia64/Kconfig
>>> > that you can ignore.
>>> > 
>>> > If this works, then we munged git-acpi.patch in 
>>
>>2.6.13-mm1 somehow.
>>
>>> There were no problems with this patch applied.  So it 
>>
>>looks like the 
>>
>>> munge theory is correct.
>>
>>That diff is significantly different from the diff I plucked from
>>master.kernel.org:/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6
>>.git#test
>>for 2.6.13-mm1.
>>
>>Doing (patch -R | grep FAILED) on 2.6.13-mm1 says:
> 
> 
> Right.
> 2.6.13/acpi-20050902-2.6.13.diff.gz
> is newers than 2.6.13-rc1's git-acpi.patch
> 
> 2.6.13/acpi-20050815-2.6.13.diff.gz
> is a closer match -- though not exact.
> 
> Peter, it might be illustrative if you have a moment
> if you can also test 2.6.13/acpi-20050815-2.6.13.diff.gz
> all by itself.
> 
> If it fails,

It does.

> then I broke -mm1
> with acpi-20050815-2.6.13.diff.gz, but fixed
> it by acpi-20050902-2.6.13.diff.gz.

So you did.

> 
> If it succeeds, then the issue lies in the relatively small delta
> between acpi-20050815-2.6.13.diff.gz 2.6.13-mm1's git-acpi.patch.
> 
> thanks,
> -Len
> 

My pleasure
Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce

  reply	other threads:[~2005-09-03 22:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-03 15:57 2.6.13-mm1: hangs during boot Brown, Len
2005-09-03 22:48 ` Peter Williams [this message]
     [not found] <fa.qs5cahs.i2khgm@ifi.uio.no>
     [not found] ` <fa.fm9i4v6.1ekchhm@ifi.uio.no>
2005-09-03 13:24   ` Reuben Farrelly
2005-09-03 13:51     ` Peter Williams
2005-09-03 16:14       ` James Bottomley
2005-09-04 16:32     ` James Bottomley
2005-09-05  8:37       ` Reuben Farrelly
  -- strict thread matches above, loose matches on Subject: below --
2005-09-03  5:37 Brown, Len
2005-09-03  6:18 ` Peter Williams
2005-09-03  7:18   ` Peter Williams
2005-09-03  8:19     ` Len Brown
2005-09-03  9:28       ` Peter Williams
2005-09-03  9:48         ` Andrew Morton
2005-09-03  4:22 Brown, Len
2005-09-03  4:58 ` Peter Williams
2005-09-03  5:25   ` Andrew Morton
2005-09-02 12:54 Peter Williams
2005-09-02 20:11 ` Andrew Morton
2005-09-03  3:51   ` Peter Williams
2005-09-03  4:16     ` Andrew Morton

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=431A2854.2000604@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=James.Bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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