public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arthur Titeica <arthur@psw.ro>
To: Greg KH <gregkh@suse.de>
Cc: Pekka Enberg <penberg@kernel.org>, <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	<torvalds@linux-foundation.org>, <stable@kernel.org>,
	<lwn@lwn.net>
Subject: Re: Linux 2.6.35.2
Date: Sat, 14 Aug 2010 17:08:54 +0300	[thread overview]
Message-ID: <59961099b1fbdb3e827d3c9f9bed3532@linux.psw.ro> (raw)
In-Reply-To: <20100814133942.GA17430@suse.de>

On Sat, 14 Aug 2010 06:39:42 -0700, Greg KH <gregkh@suse.de> wrote:
> On Sat, Aug 14, 2010 at 02:21:31PM +0300, Pekka Enberg wrote:
>> On Sat, Aug 14, 2010 at 1:35 PM, Arthur Titeica <arthur@psw.ro> wrote:
>> > On Fri, 13 Aug 2010 14:23:13 -0700, Greg KH <gregkh@suse.de> wrote:
>> >> I'm announcing the release of the 2.6.35.2 kernel.
>> >>
>> >> All users of the 2.6.35 kernel series must upgrade.
>> >>
>> >
>> > I'm not sure this is the right mailing list but this is the first
>> > kernel that fails to boot for me (since 2.6.33.x).
>> >
>> > The laptop just restarts right after "Freeing unused kernel memory:
>> > 628k freed"
>> >
>> > 2.6.35.1 is fine with the same .config.
>> >
>> > Anyone willing to help me to debug?
>>
>> You could try 'git bisect' between v2.6.35.1 and v2.6.35.2 to narrow
>> the problem down to a specific commit.
> 
> Yes, if you could please do that, it would be most appreciated.
> 
I'm trying but I'm not even close to a dev and anything beyond 'git
pull' looks tricky.

I've gotten so far:

$ git bisect start
$ git bisect bad
$ git bisect good v2.6.35.1
fatal: Needed a single revision
Bad rev input: v2.6.35.1
$ git bisect good v2.6.35
Bisecting: 3941 revisions left to test after this (roughly 12 steps)
[2192482ee5ce5d5d4a6cec0c351b2d3a744606eb] Merge branch 'for-rmk' of
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung into
devel-stable

What next? ;)


-- 
Arthur Titeica


  reply	other threads:[~2010-08-14 14:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13 21:23 Linux 2.6.35.2 Greg KH
2010-08-13 21:23 ` Greg KH
2010-08-14  6:53   ` Heinz Diehl
2010-08-14 13:40     ` Greg KH
2010-08-14 10:35 ` Arthur Titeica
2010-08-14 11:21   ` Pekka Enberg
2010-08-14 13:39     ` Greg KH
2010-08-14 14:08       ` Arthur Titeica [this message]
2010-08-14 15:10         ` Bjarke Istrup Pedersen
2010-08-14 16:56         ` Heiko Carstens
  -- strict thread matches above, loose matches on Subject: below --
2010-08-14 12:37 Sedat Dilek
2010-08-14 17:14 ` Linus Torvalds
2010-08-14 17:27   ` Sedat Dilek
2010-08-14 17:31     ` Linus Torvalds
2010-08-14 18:27       ` Ed Tomlinson
2010-08-14 18:47         ` Linus Torvalds
2010-08-14 19:01           ` wylda
2010-08-14 19:01           ` Sedat Dilek
2010-08-14 19:47           ` Ed Tomlinson
2010-08-14 21:56             ` Linus Torvalds
2010-08-14 23:39               ` Ed Tomlinson
2010-08-14 20:34           ` Sedat Dilek

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=59961099b1fbdb3e827d3c9f9bed3532@linux.psw.ro \
    --to=arthur@psw.ro \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=penberg@kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.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