From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Len Brown <lenb@kernel.org>
Cc: Len Brown <len.brown@intel.com>, Lin Ming <ming.m.lin@intel.com>,
Bob Moore <robert.moore@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: acpi_ex_system_memory_space_handler oops
Date: Thu, 13 Aug 2009 14:02:55 +0300 [thread overview]
Message-ID: <20090813110255.GA3238@localdomain.by> (raw)
In-Reply-To: <alpine.LFD.2.00.0908122009170.22946@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On (08/12/09 20:18), Len Brown wrote:
> Please find which kernel this failure starts in.
> Start by testing 2.6.30.stable so we can tell
> if this is a regression in the current RC.
>
Looks like regression in the current RC.
git bisect start 'good' '2.6.31-rc4' 'bad' '2.6.31-rc5'
# bad: [a3620f7545344f932873bf98fbdf416b49409c8e] Merge branch 'for-linus' of git://git.kernel.dk/linux-2.6-block
git bisect bad a3620f7545344f932873bf98fbdf416b49409c8e
# good: [4be3bd7849165e7efa6b0b35a23d6a3598d97465] Linux 2.6.31-rc4
git bisect good 4be3bd7849165e7efa6b0b35a23d6a3598d97465
rc4-git0
10+ successfull boots
+ + + + + + + + + +
git bisect start
git bisect bad
bisect good v2.6.31-rc5
# bad: [a3620f7545344f932873bf98fbdf416b49409c8e] Merge branch 'for-linus' of git://git.kernel.dk/linux-2.6-block
git bisect bad a3620f7545344f932873bf98fbdf416b49409c8e
# good: [ed680c4ad478d0fee9740f7d029087f181346564] Linux 2.6.31-rc5
git bisect good ed680c4ad478d0fee9740f7d029087f181346564
rc5-git0
10+ successfull boots
+ + + + + + + + +
Sergey
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 315 bytes --]
next prev parent reply other threads:[~2009-08-13 10:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 20:10 acpi_ex_system_memory_space_handler oops Sergey Senozhatsky
2009-08-12 21:46 ` Rafael J. Wysocki
2009-08-13 0:18 ` Len Brown
2009-08-13 8:34 ` Sergey Senozhatsky
2009-08-13 9:53 ` Sergey Senozhatsky
2009-08-13 11:02 ` Sergey Senozhatsky [this message]
2009-08-13 12:46 ` Sergey Senozhatsky
2009-08-14 2:34 ` Lin Ming
2009-08-14 7:40 ` Sergey Senozhatsky
2009-08-14 7:53 ` Sergey Senozhatsky
2009-08-14 9:12 ` Sergey Senozhatsky
2009-08-14 9:38 ` Sergey Senozhatsky
2009-08-14 12:48 ` Sergey Senozhatsky
2009-08-13 13:43 ` Sergey Senozhatsky
2009-08-17 8:43 ` Lin Ming
2009-08-17 11:30 ` Sergey Senozhatsky
2009-08-17 13:22 ` Lin Ming
2009-08-18 7:13 ` Sergey Senozhatsky
2009-08-18 7:18 ` Lin Ming
2009-08-18 7:45 ` Sergey Senozhatsky
2009-08-18 8:00 ` Sergey Senozhatsky
2009-08-27 7:52 ` Sergey Senozhatsky
2009-08-27 7:59 ` Lin Ming
2009-08-27 8:29 ` Sergey Senozhatsky
2009-08-27 8:44 ` Lin Ming
2009-08-27 9:05 ` Sergey Senozhatsky
2009-08-31 21:12 ` Sergey Senozhatsky
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=20090813110255.GA3238@localdomain.by \
--to=sergey.senozhatsky@gmail.com \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=robert.moore@intel.com \
/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