From: Alexey Fisher <bug-track@fisher-privat.net>
To: linux-acpi@vger.kernel.org, kernel-testers@vger.kernel.org
Subject: trouble to bisect current acpi-pm regression
Date: Sat, 03 Jul 2010 22:47:09 +0200 [thread overview]
Message-ID: <1278190029.5209.26.camel@zwerg> (raw)
Hallo all,
i have regression in current master HEAD wich i can't properly bisect,
so i need your help. Please point me if i make some mistake or you have
some other ideas.
Regression: Standby do not working with newest linus/master.git .
To reproduce i use plain: "echo mem > /sys/power/state"
After this, standby initiated, but will freeze with black screen and
cursors on the left top corner. Nothing other is working, power button
will not return it to normals state. So i need to hard reset it.
For bisect i used two points: v2.6.35-rc2 - good; and HEAD - bad.
A result i get:
commit 7c8d20d40f29e7c08332d406d7a65678dece4627
Merge: 63a07cb 9a40ac8
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Thu Jun 10 07:35:41 2010 -0700
Merge master.kernel.org:/home/rmk/linux-2.6-arm
* master.kernel.org:/home/rmk/linux-2.6-arm:
ARM: 6164/1: Add kto and kfrom to input operands list.
ARM: 6166/1: Proper prefetch abort handling on pre-ARMv6
ARM: 6165/1: trap overflows on highmem pages from kmap_atomic when
debuggi
ARM: 6152/1: ux500 make it possible to disable localtimers
[ARM] pxa/spitz: Correctly register WM8750
[ARM] pxa/palmtc: storage class should be before const qualifier
ARM: 6146/1: sa1111: Prevent deadlock in resume path
ARM: 6145/1: ux500 MTU clockrate correction
ARM: 6144/1: TCM memory bug freeing bug
ARM: VFP: Fix vfp_put_double() for d16-d31
what can't be true. I double checked it and steel get same result. This
commit, is currently first commit, where i can reproduce this
regression.
Is it possible git bisect miss some branch? Any tips to find real patch?
Regards,
Alexey
reply other threads:[~2010-07-03 20:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1278190029.5209.26.camel@zwerg \
--to=bug-track@fisher-privat.net \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-acpi@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).