From: Roberto Oppedisano <roberto.oppedisano@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Sam Ravnborg <sam@ravnborg.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.35 suspend regression (bisected)
Date: Tue, 27 Jul 2010 21:52:17 +0200 [thread overview]
Message-ID: <4C4F38F1.105@gmail.com> (raw)
In-Reply-To: <201007272103.38448.rjw@sisk.pl>
On 27/07/2010 21:03, Rafael J. Wysocki wrote:
>> I did bisect again and I did get a different result:
>>
>> c1518f12bab97a6d409a25aaccb02dc8895800f3 is the first bad commit
>>
>> Trying to revert that commit gives:
>>
>> $ git bisect reset
>> $ git revert c1518f12bab97a6d409a25aaccb02dc8895800f3
>> fatal: Commit c1518f12bab97a6d409a25aaccb02dc8895800f3 is a merge but no
>> -m option was given.
>>
>> How am I supposed to proceed now ? (sorry I'm a git newbie)
> The bisect turned up a merge, which means it probably didn't really converge
> for you.
>
> Do you use a camera driver?
Yes, this laptop has an integrated webcam.
Bus 001 Device 004: ID 04f2:b059 Chicony Electronics Co., Ltd
which i think is driven by uvcvideo.ko. I've tryed to rmmod uvcvideo,
videodev and
v4l1_compat but on current git suspend still hangs in the same way
(screen black,
backlight on, fans at full speed, no response to ping and... nothing in
the logs).
R
next prev parent reply other threads:[~2010-07-27 19:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-25 20:27 2.6.35 suspend regression (bisected) Roberto Oppedisano
2010-07-25 22:18 ` Rafael J. Wysocki
2010-07-25 22:35 ` Sam Ravnborg
2010-07-27 18:38 ` Roberto Oppedisano
2010-07-27 19:03 ` Rafael J. Wysocki
2010-07-27 19:52 ` Roberto Oppedisano [this message]
2010-07-27 22:37 ` Rafael J. Wysocki
2010-07-28 7:39 ` Roberto Oppedisano
2010-08-03 19:20 ` Maciej Rutecki
2010-08-04 6:37 ` Paul Rolland
2010-08-04 7:39 ` Roberto Oppedisano
2010-08-09 21:23 ` Tomas M.
2010-08-25 3:30 ` Roberto Oppedisano
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=4C4F38F1.105@gmail.com \
--to=roberto.oppedisano@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sam@ravnborg.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